› ›

Detecting MK3 Error messages

ZephrantZephrant
in Questions & Answers
Last night I had a failed print, that caused these messages to show in the log: < 3:53:43.475: N382699 G1 X74.034 Y107.238 E0.10559 > 3:53:43.504: ok < 3:53:43.504: N382700 G1 X73.975 Y106.646 E0.02079 > 3:53:43.590: ok < 3:53:43.590: N382701 G1 X71.802 Y108.819 E0.10742 > 3:53:43.618: ok < 3:53:43.618: N382702 G1 X71.735 Y108.431 E0.01377 > 3:53:43.639: // action:pause > 3:53:43.643: Extruder fan speed is lower then expected > 3:53:43.803: ok > 3:53:50.521: // action:pause > 3:53:50.525: Extruder fan speed is lower then expected > 3:53:53.167: fsensor_autoload_check_start - autoload ENABLED > 3:53:57.402: // action:pause > 3:53:57.406: Extruder fan speed is lower then expected > 3:54:04.284: // action:pause > 3:54:04.288: Extruder fan speed is lower then expected > 3:54:11.165: // action:pause > 3:54:11.169: Extruder fan speed is lower then expected The messages continued for a half hour, then I got this: > 4:04:39.213: Extruder fan speed is lower then expected > 4:23:55.094: echo:busy: paused for user > 4:23:57.122: echo:busy: paused for user Until I manually intervened. I did eventually get a push notification that the print had failed, but it happened much later than the actual error. Is there a way I can add filters that can be trapped to send push notifications? I thought I read something about that, but can't find that info this morning. I'd like to add traps for filament sensor, fan failure, and other common errors I see. I don't mind working in the code and submitting a patch, if you could point me to the correct file. Thank you-

Comments

  • ZephrantZephrant
    Sorry for the loss of all formatting above, can that be turned off somehow? Makes it completely unreadable.
  • ZephrantZephrant
    My fault for formatting issues- script blocker caused me problems. Re-posted with formatting: Last night I had a failed print, that caused these messages to show in the log: < 3:53:43.475: N382699 G1 X74.034 Y107.238 E0.10559 > 3:53:43.504: ok < 3:53:43.504: N382700 G1 X73.975 Y106.646 E0.02079 > 3:53:43.590: ok < 3:53:43.590: N382701 G1 X71.802 Y108.819 E0.10742 > 3:53:43.618: ok < 3:53:43.618: N382702 G1 X71.735 Y108.431 E0.01377 > 3:53:43.639: // action:pause > 3:53:43.643: Extruder fan speed is lower then expected > 3:53:43.803: ok > 3:53:50.521: // action:pause > 3:53:50.525: Extruder fan speed is lower then expected > 3:53:53.167: fsensor_autoload_check_start - autoload ENABLED > 3:53:57.402: // action:pause > 3:53:57.406: Extruder fan speed is lower then expected > 3:54:04.284: // action:pause > 3:54:04.288: Extruder fan speed is lower then expected > 3:54:11.165: // action:pause > 3:54:11.169: Extruder fan speed is lower then expected The messages continued for a half hour, then I got this: > 4:04:39.213: Extruder fan speed is lower then expected > 4:23:55.094: echo:busy: paused for user > 4:23:57.122: echo:busy: paused for user Until I manually intervened. I did eventually get a push notification that the print had failed, but it happened much later than the actual error. Is there a way I can add filters that can be trapped to send push notifications? I thought I read something about that, but can't find that info this morning. I'd like to add traps for filament sensor, fan failure, and other common errors I see. I don't mind working in the code and submitting a patch, if you could point me to the correct file. Thank you-
  • ZephrantZephrant
    I give up-  Not sure why I'm losing all formatting in Firefox.
  • ZephrantZephrant
    >  4:04:25.417: Extruder fan speed is lower then expected
    >  4:04:32.328: // action:pause
    >  4:04:32.331: Extruder fan speed is lower then expected
    >  4:04:39.209: // action:pause
    >  4:04:39.213: Extruder fan speed is lower then expected
    >  4:23:55.094: echo:busy: paused for user
    >  4:23:57.122: echo:busy: paused for user
    > 

  • RepetierRepetier
    That is not really a failed print until that point. Sounds like the firmware/printer has a jam detection that triggered and put firmware in wait for user action state.
    // action:pause
    tells server to stop sending gcode.

    echo:busy: paused for user
    is a hint that firmware is still waiting for user interaction. Once you fix the problem on your printer and tell it to continue it should tell server
    // action:resume

    and server would continue to print. You need to fix the problem using the printers lcd where the printer waits for user interaction.
  • ZephrantZephrant
    Ok, that helps, thank you.

    I'm mostly looking for a notification from RS that the printer is in that state. With multiple printers, it's almost a daily issue for me where I have one printer paused due to a crash or out of filament, and don't realize it until I go check them.

    It would be a very useful feature to me to get push notifications on those pauses.
Sign In or Register to comment.