Jump to content

We made it, the New Cura


SandervG

Recommended Posts

Posted · We made it, the New Cura

 

 

Okay tried it out....despite the settings being Ultimaker Original and No Heated Bed, if you go to use this, the Ultimaker Original sits at "Heating bed".

Umm, you guys test this stuff, right?  ;)

 

We did test, quite a bit. But... well, all our originals where upgraded to + or heated bed upgrade status. So that was missed.

There is a workaround, you can enable the heated bed setting and set that to 0, that will work around this problem till we have a fix out.

 

Well, some time has passed. Is it safe for a newbie with an ultimaker original to try it yet?

 

1.99 is pretty stable and I have been using it for quite a few weeks now with few problems.

  • Link to post
    Share on other sites

    • Replies 238
    • Created
    • Last Reply

    Top Posters In This Topic

    Top Posters In This Topic

    Posted Images

    Posted · We made it, the New Cura

    While I have found 1.99 stable, the layer view stutters quite badly, in that when dragging the layer slider up and down, it's really not smooth, whereas 15.04 (which I still use for production) is much smoother on layer view.

  • Link to post
    Share on other sites

    Posted · We made it, the New Cura

     

    1.99 is pretty stable and I have been using it for quite a few weeks now with few problems.

     

    Same here.

     

    I'm new to GitHub but would this be the place for end users to look to find out if the current version is "stable" enough for their personal sense of adventure level?

    https://github.com/Ultimaker/Cura/labels/bug

    Also since depending on use and feature expectations..... one man's "pretty stable" is another man's "totally unusable". :)

  • Link to post
    Share on other sites

    Posted · We made it, the New Cura

    I'm new to GitHub but would this be the place for end users to look to find out if the current version is "stable" enough for their personal sense of adventure level?

     

    No. We actually only do public tracking there. Most of the (bug) tracking is done on a private tracker that can do a whole lot more than the shitty one github provides.

    The best way to see if there is a stable release is to wait for the release. Inbetween releases tend to be somewhat stable and nightly tend to be unstable (although nightlies can be stable...)

  • Link to post
    Share on other sites

    Posted · We made it, the New Cura
    On 9/20/2015 at 1:36 PM, ivan-lipunov said:

    After the comment about the limitations of multithreading in Python some time I googled this question and found here some interesting option: https://docs.python.org/2/library/multiprocessing.html

    This method has its limitations in terms of platform dependence, but the execution speed is obviously higher than when using GIL. @nallath, you have not considered the possibility of changes in this way?

    Have been able to do multi threading in a post procesing script in Cura ? I try myself and it always won't work

  • Link to post
    Share on other sites

    Posted · We made it, the New Cura
    On 8/10/2023 at 1:46 PM, VictorMic said:

    it always won't work

    There is no information in this statement that enables anyone to give you any help or advice.

     

    What are you doing? How are you doing that (post a link to code you are using). What happens when you run the code? How does it "not work"? Do you get specific error messages?

  • Link to post
    Share on other sites

    Posted · We made it, the New Cura
    Just now, ahoeben said:

    There is no information in this statement that enables anyone to give you any help or advice.

     

    What are you doing? How are you doing that (post a link to code you are using). What happens when you run the code? How does it "not work"? Do you get specific error messages?

    hello,

    Thank you for your answer. So the goal of my company is to create a new way to create industrial metal pieces by using 3d printing firstly to create the piece in plastic and with this plastic piece create a mold in which aluminium is poured and melt the plastic (so we need a 3d printing with the lowest density, so all the plastic will be burn by the aluminium.  I am currently creating a post processing python script for Cura, of which the goal is to increment the E value of the gcode to compensate for the loss of materials, that occur when the extruder of the 3d printer is moving without printing. We need to compensate these loss because otherwise it create holes in the printing. But the size of the pieces are great (millions of gcodes lines), so to be able to modify the gcode in a correct amount of time I used the Multiprocessing of python. I had to work on windows so to use multiprocessing i need to have this line :

    if __name__ == '__main__':  # MultiProcessing
            with Pool() as p:
                resultat = p.map(traitement_gcode_lineaire,liste_traitement)
        if len(resultat)!=0 :
            for result in resultat :
                fichier += result

    When launch by myself (like in VS code) without Cura all is good. But the issue here is that it can't enter the loop because __name__ will never be equal to '__main__', but it always equal to :

    'PostProcessingPlugin.PostProcessingPlugin.ModificationGcodeMultiProcessing'

    where 'ModificationGcodeMultiProcessing' is the name of my postprocessing script and i never found any other script that was using multiprocessing so i was wandering if anybody has any clue for me.

    "Do you get specific error messages" I don t have any error message but at the end 'Fichier' (which should contain the gcode that i modify) is empty.

    I attach my code. But the issue is located in the function improve_extrusion (the other work perfectly)

    ModificationGcodeMultiProcessing.zip

  • Link to post
    Share on other sites

    Posted (edited) · We made it, the New Cura

    In your code, the actual processing is only executed if the script is run outside of Cura. That is what that line "if __name__ == '__main__':" does. The "# Multiprocessing" is just a comment and does nothing.

     

    Change this:

        if __name__ == '__main__':  # MultiProcessing
    
            with Pool() as p:
                resultat = p.map(traitement_gcode_lineaire,liste_traitement)

     

    To this:

        with Pool() as p:
            resultat = p.map(traitement_gcode_lineaire,liste_traitement)

    Note that I changed the indentation of those two lines. This is important in Python.

     

    It would be better if you change the functions you define into methods of the class, but that takes more modifications than I care to do right now.

     

    I have not tested your code, but at least this way Cura should try to run it.

     

    For further questions, it is probably better to start a new thread than to tack onto a non-related 6 year old thread.

    Edited by ahoeben
  • Link to post
    Share on other sites

    Posted · We made it, the New Cura

    In fact please start a new topic and then link to it from this topic.  Just in case there is more discussion.

  • Link to post
    Share on other sites

    Posted · We made it, the New Cura
    Just now, ahoeben said:

    In your code, the actual processing is only executed if the script is run outside of Cura. That is what that line "if __name__ == '__main__':" does. The "# Multiprocessing" is just a comment and does nothing.

     

    Change this:

        if __name__ == '__main__':  # MultiProcessing
    
            with Pool() as p:
                resultat = p.map(traitement_gcode_lineaire,liste_traitement)

     

    To this:

        with Pool() as p:
            resultat = p.map(traitement_gcode_lineaire,liste_traitement)

    Note that I changed the indentation of those two lines. This is important in Python.

     

    It would be better if you change the functions you define into methods of the class, but that takes more modifications than I care to do right now.

     

    I have not tested your code, but at least this way Cura should try to run it.

     

    For further questions, it is probably better to start a new thread than to tack onto a non-related 6 year old thread.

    Thank you for the answer, i didn t before sending my fisrt message that this thread was dead since 7 years, but pls don t be condescending :

    _"The "# Multiprocessing" is just a comment and does nothing" i write for you just to be sure. yes i know how to comment on python don t worry

    _"if the script is run outside of Cura. That is what that line "if __name__ == '__main__':" does." I know that like i mentionned but the problem is that on windows i didn't fin any means to do without this "if", because your changement will just create an infinite loop

    _"Note that I changed the indentation of those two lines. This is important in Python" No i didn t know !

    _i have already create another topic : https://community.ultimaker.com/topic/40911-post-processing-script-logs/

     

  • Link to post
    Share on other sites

    Posted · We made it, the New Cura
    Just now, VictorMic said:

    Thank you for the answer, i didn t before sending my fisrt message that this thread was dead since 7 years, but pls don t be condescending :

    _"The "# Multiprocessing" is just a comment and does nothing" i write for you just to be sure. yes i know how to comment on python don t worry

    _"if the script is run outside of Cura. That is what that line "if __name__ == '__main__':" does." I know that like i mentionned but the problem is that on windows i didn't fin any means to do without this "if", because your changement will just create an infinite loop

    _"Note that I changed the indentation of those two lines. This is important in Python" No i didn t know !

    _i have already create another topic : https://community.ultimaker.com/topic/40911-post-processing-script-logs/

     

    wrong link : https://community.ultimaker.com/topic/44004-multithreading-and-multi-processing-for-python-script-in-cura/

     

  • Link to post
    Share on other sites

    Posted · We made it, the New Cura

    I am sorry I made you feel condescended, I will stop wasting my time by further trying to help you. Good luck with your endeavors!

  • Link to post
    Share on other sites

    Posted · We made it, the New Cura

    ok 👍

  • Link to post
    Share on other sites

    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now

    • Our picks

      • Introducing Universal Cura Projects in the UltiMaker Cura 5.7 beta
        Strap in for the first Cura release of 2024! This 5.7 beta release brings new material profiles as well as cloud printing for Method series printers, and introduces a powerful new way of sharing print settings using printer-agnostic project files! Also, if you want to download the cute dinosaur card holder featured below, it was specially designed for this release and can be found on Thingiverse! 
          • Like
        • 10 replies
      • S-Line Firmware 8.3.0 was released Nov. 20th on the "Latest" firmware branch.
        (Sorry, was out of office when this released)

        This update is for...
        All UltiMaker S series  
        New features
         
        Temperature status. During print preparation, the temperatures of the print cores and build plate will be shown on the display. This gives a better indication of the progress and remaining wait time. Save log files in paused state. It is now possible to save the printer's log files to USB if the currently active print job is paused. Previously, the Dump logs to USB option was only enabled if the printer was in idle state. Confirm print removal via Digital Factory. If the printer is connected to the Digital Factory, it is now possible to confirm the removal of a previous print job via the Digital Factory interface. This is useful in situations where the build plate is clear, but the operator forgot to select Confirm removal on the printer’s display. Visit this page for more information about this feature.
          • Like
        • 0 replies
    ×
    ×
    • Create New...