Jump to content

Post processing script logs


Darinth

Recommended Posts

Posted · Post processing script logs

I've been trying to write a post-processing script (trying to see if I can get the problem I outlined here fixed) and as part of this I started off just trying to learn generally how they work. I've been able to make changes to the script, but I can't get the any kind of logging to work which makes debugging a pain. All of the scripts I've seen thus far use UM.logger, but I've not actually been able to figure out where these log messages show up. They don't show up in the normal cura.log file and they don't show up in the actual console (I've got cygwin and ran cura from a cygwin bash prompt with the --debug flag). I'm running cura 5. Am I missing something obvious? Is there potentially a bug with the logger not working correctly in Cura 5?

  • Link to post
    Share on other sites

    • 1 year later...
    Posted · Post processing script logs

    I didn't think I was condescending.  I was just remarking that it would be a good idea to start a new topic.  And I said "please". 🙂

     

    Please assume all people are smiling when you only see their text.  🙂  With text only it's difficult to know their emotion so please assume people are neutral or happy and if they seem condescending or angry assume you are wrong.

  • Link to post
    Share on other sites

    Posted · Post processing script logs

    To answer @Darinth's question, for the benefit of other people finding this thread, messages from UM.Logger should end up in Cura.log and the console output (with the --debug flag). If it does not, then the most likely reason is that the code is not getting executed.

    • Like 1
    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

      • 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
      • Ultimaker Cura 5.6 stable released
        Cura now supports Method series printers!
         
        A year after the merger of Ultimaker and MakerBotQQ, we have unlocked the ability for users of our Method series printers to slice files using UltiMaker Cura. As of this release, users can find profiles for our Method and Method XL printers, as well as material profiles for ABS-R, ABS-CF, and RapidRinse. Meaning it’s now possible to use either Cura or the existing cloud-slicing software CloudPrint when printing with these printers or materials
        • 48 replies
    ×
    ×
    • Create New...