Print cancels at the start of a new print



  • For some reason I've come across a weird error after installing the new firmware.

    My prints often cancel themselves before they have even started, weirdly though, this only happens on about half of the prints and is more likely to happen after I've already done a print, but it has also done it on the first print.

    my routine: I set temps manually, slice file and then upload it to the web interface. The homing process then starts and the print will cancel after the X axis homes and then it will turn the heaters off etc, just like ending a print. My starting script in the slic3r is just G28.

    my Homeall file:
    M84 E0:1 ; Extruder motor off
    G91 ; Relative positioning
    ;G1 Z5 F6000 S2 ; Lift Z
    G1 Y-195 F1800 S1
    G1 X-195 F1800 S1 ; Move towards X and Y axis endstops (first pass)
    G1 X5 Y5 F6000 ; Go back a few mm
    G1 X-195 Y-195 F360 S1 ; Move slowly to axis endstops once more (second pass)

    G1 Z-200 S1 F100 ; move Z down until the switch triggers
    G1 Z20 S1 F100 ; Move Z up 20mm
    G92 Z0.10 ; tell the firmware that we are at Z=0.10mm
    G90 ; absolute mode

    My homeX file:
    G91
    G1 Z5 F6000 S2
    G90
    G91
    G1 X5 F6000
    G90
    G1 X-250 F360 S1
    G91
    G1 Z-5 F6000 S2
    G90

    Any help appreciated.. I have checked the forums and this is a head scratcher


  • administrators

    It could mean that the Duet is resetting. Next time it happens, please run M122 and post the report here.



  • 0_1525971624593_Untitled.png

    M122 just tells me that a file was selected for printing. nothing else happens.

    using USB and S3D yields this:

    SENT: M122
    READ: === Diagnostics ===
    READ: Used output buffers: 5 of 32 (11 max)
    READ: === Platform ===
    READ: RepRapFirmware for Duet 2 WiFi/Ethernet version 1.21 running on Duet WiFi 1.0 or 1.01
    READ: Board ID: 08DAM-999TL-MQ4S8-6JTDJ-3SJ6N-16BBW
    READ: Static ram used: 16152
    READ: Dynamic ram used: 100504
    READ: Recycled dynamic ram: 2128
    READ: Stack ram used: 3576 current, 6632 maximum
    READ: Never used ram: 5656
    READ: Last reset 55:12:08 ago, cause: power up
    READ: Last software reset at 2018-04-22 18:17, reason: User, spinning module GCodes, available RAM 5784 bytes (slot 0)
    READ: Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0441f000, BFAR 0xe000ed38, SP 0xffffffff
    READ: Error status: 8
    READ: Free file entries: 10
    READ: SD card 0 detected, interface speed: 20.0MBytes/sec
    READ: SD card longest block write time: 0.0ms
    READ: MCU temperature: min 35.6, current 35.8, max 36.7
    READ: Supply voltage: min 11.9, current 12.0, max 12.2, under voltage events: 0, over voltage events: 0
    READ: Driver 0: standstill, SG min/max not available
    READ: Driver 1: standstill, SG min/max not available
    READ: Driver 2: standstill, SG min/max not available
    READ: Driver 3: standstill, SG min/max not available
    READ: Driver 4: standstill, SG min/max not available
    READ: Date/time: 2018-05-10 18:04:05
    READ: Slowest main loop (seconds): 0.179110; fastest: 0.000112
    READ: === Move ===
    READ: MaxReps: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0
    READ: Scheduled moves: 0, completed moves: 0
    READ: Bed compensation in use: none
    READ: Bed probe heights: 0.000 0.000 0.000 0.000 0.000
    READ: === Heat ===
    READ: Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
    READ: Heater 0 is on, I-accum = 0.0
    READ: Heater 1 is on, I-accum = 0.4
    READ: === GCodes ===
    READ: Segments left: 0
    READ: Stack records: 1 allocated, 0 in use
    READ: Movement lock held by null
    READ: http is idle in state(s) 0
    READ: telnet is idle in state(s) 0
    READ: file is idle in state(s) 0
    READ: serial is ready with "M122" in state(s) 0
    READ: aux is idle in state(s) 0
    READ: daemon is idle in state(s) 0
    READ: queue is idle in state(s) 0
    READ: autopause is idle in state(s) 0
    READ: Code queue is empty.
    READ: === Network ===
    READ: Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
    READ: HTTP sessions: 2 of 8
    READ: - WiFi -
    READ: Network state is running
    READ: WiFi module is connected to access point
    READ: Failed messages: pending 0, notready 0, noresp 0
    READ: WiFi firmware version 1.21
    READ: WiFi MAC address 5c:cf:7f:2c:27:94
    READ: WiFi Vcc 3.38, reset reason Turned on by main processor
    READ: WiFi flash size 4194304, free heap 15992
    READ: WiFi IP address 192.168.1.147
    READ: WiFi signal strength -63dBm, reconnections 0, sleep mode modem
    READ: Socket states: 0 0 0 0 0 0 0 0
    READ: === Expansion ===



  • What’s your bed size?



  • @stealthy_tt

    195mm^2



  • Try adding more bed size in the Homeall.g for example here is a modified section of yours.

    G1 Y-220 F1800 S1
    G1 X-220 F1800 S1 ; Move towards X and Y axis endstops (first pass)
    G1 X5 Y5 F6000 ; Go back a few mm
    G1 X-220 Y-220 F360 S1 ; Move slowly to axis endstops once more (second pass)

    Even though your bed size is 195mm in some conditions it may take more than 195mm of travel to make it to the endstop while homing.

    I noticed that in your homex.g you gave the X position 250mm of travel during homing of just X, you can use that number in homeall also if you feel like it.


 

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