Printerboard reboots when trying to print a file



  • So I set up my Duet Maestro on a a printer recently and had no issues (that I couldn't easily fix myself).

    However today when I go to print a file, as soon as it starts the file, the board appears to reboot and I get a pop-up with the following error message:

    The connection between the browser and your machine has been interrupted.
    
    Reason: Request Timeout
    
    Please wait while a new connection is being established..."
    

    There appears to be no issues up to the point of trying to print a file, I can upload files, move axis, control heaters but as soon as I go to print any file, even those that had previously worked flawlessly, I encounter this problem.

    Here is the output from the M122 command

    4:35:59 PMM32 "Geckooooo.gcode"
    
    File Geckooooo.gcode selected for printing
    
    4:32:23 PMM122
    
    === Diagnostics ===
    
    RepRapFirmware for Duet 2 Maestro version 2.02RC5(RTOS) running on Duet Maestro 1.0
    
    Board ID: 08DAM-9F9DA-MWNS8-6J9DA-3SW6R-141UW
    
    Used output buffers: 3 of 20 (8 max)
    
    === RTOS ===
    
    Static ram: 21236
    
    Dynamic ram: 96672 of which 0 recycled
    
    Exception stack ram used: 188
    
    Never used ram: 12976
    
    Tasks: NETWORK(ready,456) HEAT(blocked,1356) MAIN(running,3672) IDLE(ready,200)
    
    Owned mutexes:
    
    === Platform ===
    
    Last reset 00:00:26 ago, cause: power up
    
    Last software reset at 2018-12-02 15:12, reason: User, spinning module GCodes, available RAM 13596 bytes (slot 0)
    
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0400f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
    
    Error status: 0
    
    Free file entries: 10
    
    SD card 0 detected, interface speed: 15.0MBytes/sec
    
    SD card longest block write time: 0.0ms, max retries 0
    
    MCU temperature: min 24.5, current 25.7, max 26.0
    
    Supply voltage: min 24.1, current 24.2, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
    
    Driver 0: standstill, read errors 0, write errors 0, ifcount 6, reads 1039, timeouts 0
    
    Driver 1: standstill, read errors 0, write errors 0, ifcount 6, reads 1039, timeouts 0
    
    Driver 2: standstill, read errors 0, write errors 0, ifcount 6, reads 1039, timeouts 0
    
    Driver 3: standstill, read errors 0, write errors 0, ifcount 6, reads 1039, timeouts 0
    
    Driver 4: standstill, read errors 0, write errors 0, ifcount 6, reads 1039, timeouts 0
    
    Driver 5: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 1044
    
    Driver 6: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 1044
    
    Date/time: 2018-12-02 16:32:22
    
    Slowest loop: 69.98ms; fastest: 0.06ms
    
    I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
    
    === Move ===
    
    Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 240, MaxWait: 0ms, Underruns: 0, 0
    
    Scheduled moves: 0, completed moves: 0
    
    Bed compensation in use: none
    
    Bed probe heights: 0.000 0.000 0.000 0.000 0.000
    
    === Heat ===
    
    Bed heaters = 0, chamberHeaters = -1 -1
    
    === GCodes ===
    
    Segments left: 0
    
    Stack records: 1 allocated, 0 in use
    
    Movement lock held by null
    
    http is idle in state(s) 0
    
    telnet is idle in state(s) 0
    
    file is idle in state(s) 0
    
    serial is idle in state(s) 0
    
    aux is idle in state(s) 0
    
    daemon is idle in state(s) 0
    
    queue is idle in state(s) 0
    
    lcd is idle in state(s) 0
    
    autopause is idle in state(s) 0
    
    Code queue is empty.
    
    === Network ===
    
    Slowest loop: 5.40ms; fastest: 0.02ms
    
    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
    
    HTTP sessions: 1 of 8
    
    Interface state 5, link 100Mbps full duplex
    
    4:32:11 PMConnection established!
    
    4:32:03 PMDisconnected.
    
    4:31:55 PMM32 "Geckooooo.gcode"
    
    File Geckooooo.gcode selected for printing
    
    4:31:30 PMConnection established!
    
    4:31:27 PMPage Load complete!
    

    Any help or advice would be greatly appreciated, I have tried re-uploading the firmware and the web Interface zip with no luck and haven't found anyone with a similar problem on the forums yet.


  • administrators

    The M122 report includes:

    Last reset 00:00:26 ago, cause: power up
    Last software reset at 2018-12-02 15:12, reason: User, spinning module GCodes, available RAM 13596 bytes (slot 0)

    This indicates that the reboot was caused by loss of power. Did you run the M122 command immediately after the problem occurred? If so then some command in the print file is causing your PSU to be overloaded and cut out. I suggest you test the heaters, and motors again, first individually, then run them all at the same time.

    Another possibility is that you have wired the endstop switches incorrectly and they are shorting +3.3V to ground; but if that is the case then you will get resets when you try to home the printer.



Looks like your connection to Duet3D was lost, please wait while we try to reconnect.