Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    Print pause annoyance

    Scheduled Pinned Locked Moved
    Filament Monitor
    2
    3
    179
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Garfieldundefined
      Garfield
      last edited by Garfield

      Running RRF3, DWC 2.0.7, magnetic filament sensor, DCF 1.2.5, RPi 4

      Halfway into a 17 hour print the printer stops - printing paused because the filament sensor detected a non existent problem - now I can deal with the pause providing the printer doesn't refuse to start again - which is exactly what just happened.

      The system was sitting there with 'PAUSING' displayed as a current status (in red at top of dashboard), no amount of 'RESUME' clicking would resume printing, couldn't even cancel - must pause before you can cancel.

      There is something seriously wrong with the manner in which DWC and RRF3 are handling the communication of status between them.

      The print was NOT pausing it was paused, sitting there with temperatures full on, the extruder did NOT move to a safe place. I was forced to emergency stop the printer to get control back.

      This is not a magnetic sensor problem - this is a problem in the communication between DWC and RRF3.

      Has anyone experienced this ? how did you get control back ?

      I have deleted the filament sensor for now from my system and resumed printing - from the beginning - 😠 .

      The M291 P1 acknowledge @16:56 or so can be seen here, as can many M24 attempts to resume and my attempts to remove the filament sensor - all of which did nothing - the printer did not resume. I can find no reference to pause.g so how the pause works on filament events I have no clue currently.

      
Mar 23 16:56:15 duet3 DuetWebServer[427]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Mar 23 16:56:15 duet3 DuetWebServer[427]:       Request starting HTTP/1.1 POST http://10.100.2.225/machine/code text/plain;charset=UTF-8 7
Mar 23 16:56:15 duet3 DuetWebServer[427]: info: Microsoft.AspNetCore.Cors.Infrastructure.CorsService[4]
Mar 23 16:56:15 duet3 DuetWebServer[427]:       CORS policy execution successful.
Mar 23 16:56:15 duet3 DuetWebServer[427]: info: Microsoft.AspNetCore.Routing.EndpointMiddleware[0]
Mar 23 16:56:15 duet3 DuetWebServer[427]:       Executing endpoint 'DuetWebServer.Controllers.MachineController.DoCode (DuetWebServer)'
Mar 23 16:56:15 duet3 DuetWebServer[427]: info: Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker[3]
Mar 23 16:56:15 duet3 DuetWebServer[427]:       Route matched with {action = "DoCode", controller = "Machine"}. Executing controller action with signature System.Threading.Tasks.Task`1[Microsoft.AspNetCore.Mvc.IActionResult] DoCode() 
Mar 23 16:56:15 duet3 DuetWebServer[427]: info: DuetWebServer.Controllers.MachineController[0]
Mar 23 16:56:15 duet3 DuetWebServer[427]:       [DoCode] Executing code 'M292 P1'
Mar 23 16:56:15 duet3 DuetWebServer[427]: info: Microsoft.AspNetCore.Mvc.Infrastructure.ContentResultExecutor[1]
Mar 23 16:56:15 duet3 DuetWebServer[427]:       Executing ContentResult with HTTP Response ContentType of text/plain; charset=utf-8
Mar 23 16:56:15 duet3 DuetWebServer[427]: info: Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker[2]
Mar 23 16:56:15 duet3 DuetWebServer[427]:       Executed action DuetWebServer.Controllers.MachineController.DoCode (DuetWebServer) in 139.3548ms
Mar 23 16:56:15 duet3 DuetWebServer[427]: info: Microsoft.AspNetCore.Routing.EndpointMiddleware[1]
Mar 23 16:56:15 duet3 DuetWebServer[427]:       Executed endpoint 'DuetWebServer.Controllers.MachineController.DoCode (DuetWebServer)'
Mar 23 16:56:15 duet3 DuetWebServer[427]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Mar 23 16:56:15 duet3 DuetWebServer[427]:       Request finished in 144.1051ms 200 text/plain; charset=utf-8
Mar 23 16:56:16 duet3 DuetWebServer[427]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Mar 23 16:56:16 duet3 DuetWebServer[427]:       Request starting HTTP/1.1 POST http://10.100.2.225/machine/code text/plain;charset=UTF-8 3
Mar 23 16:56:16 duet3 DuetWebServer[427]: info: Microsoft.AspNetCore.Cors.Infrastructure.CorsService[4]
Mar 23 16:56:16 duet3 DuetWebServer[427]:       CORS policy execution successful.
Mar 23 16:56:16 duet3 DuetWebServer[427]: info: Microsoft.AspNetCore.Routing.EndpointMiddleware[0]
Mar 23 16:56:16 duet3 DuetWebServer[427]:       Executing endpoint 'DuetWebServer.Controllers.MachineController.DoCode (DuetWebServer)'
Mar 23 16:56:16 duet3 DuetWebServer[427]: info: Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker[3]
Mar 23 16:56:16 duet3 DuetWebServer[427]:       Route matched with {action = "DoCode", controller = "Machine"}. Executing controller action with signature System.Threading.Tasks.Task`1[Microsoft.AspNetCore.Mvc.IActionResult] DoCode() 
Mar 23 16:56:16 duet3 DuetWebServer[427]: info: DuetWebServer.Controllers.MachineController[0]
Mar 23 16:56:16 duet3 DuetWebServer[427]:       [DoCode] Executing code 'M24'
Mar 23 16:56:16 duet3 DuetWebServer[427]: info: Microsoft.AspNetCore.Mvc.Infrastructure.ContentResultExecutor[1]
Mar 23 16:56:16 duet3 DuetWebServer[427]:       Executing ContentResult with HTTP Response ContentType of text/plain; charset=utf-8
Mar 23 16:56:16 duet3 DuetWebServer[427]: info: Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker[2]
Mar 23 16:56:16 duet3 DuetWebServer[427]:       Executed action DuetWebServer.Controllers.MachineController.DoCode (DuetWebServer) in 169.0471ms
Mar 23 16:56:16 duet3 DuetWebServer[427]: info: Microsoft.AspNetCore.Routing.EndpointMiddleware[1]
Mar 23 16:56:16 duet3 DuetWebServer[427]:       Executed endpoint 'DuetWebServer.Controllers.MachineController.DoCode (DuetWebServer)'
Mar 23 16:56:16 duet3 DuetWebServer[427]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Mar 23 16:56:16 duet3 DuetWebServer[427]:       Request finished in 174.0729ms 200 text/plain; charset=utf-8
      1 Reply Last reply Reply Quote 0
      • TeddyFluffkinsundefined
        TeddyFluffkins
        last edited by

        I have had the same problem. I suspect a incorrect pause.g file, haven't dug deeper yet.

        1 Reply Last reply Reply Quote 0
        • Garfieldundefined
          Garfield
          last edited by

          I haven't re-enabled my filament sensor - flat out don't trust the printers behaviour.

          This isn't the Pause.g - I can deliberately pause and resume with no problems whatsoever.

          That the hot end did not move to a safe location as defined in the pause.g tells me that it isn't even executed, the message 'pausing' will never go away, there is no error indicated and I have a lot more confidence in my Hemera than I do the filament sensor currently.

          At the point the print paused there were zero extrusion problems. As I mentioned I have no problem with the filament sensor being unreliable if I can resume with no problems - the big word here is IF ...

          I've had numerous 'communication lost' reports so my belief is that the problem lies in how the Raspberry Pi and the Duet3 communicate - the communications is not resilient, it has been reported that the Duet framework crashes but it does not, it is still reported as running.

          Part of the problem is that the console will lock you out whilst it executes some commands, if those commands never report complete then it appears frozen, it also doesn't seem to like messages being received that weren't solicited. There needs to be some improvement in the error handling and certainly a timeout on task execution cycles, I'm busy with other stuff or I'd look deeper.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Unless otherwise noted, all forum content is licensed under CC-BY-SA