Duet wifi 2 reset when trying to home printer w smart effector
-
I have a 12v delta running 0.9 degree stepper motors each with 2 amps and a 25 amp psu and when i home printer get watchdog timeout error i am using duet smart effector. @dc42 any thoughts cheers.
=== Diagnostics ===<LF>RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05RC2 running on Duet WiFi 1.02 or later<LF>Board ID: 08DGM-9T6BU-FG3SN-6J1DD-3S86J-TBZRF<LF>Used output buffers: 1 of 24 (1 max)<LF>=== RTOS ===<LF>Static ram: 25688<LF>Dynamic ram: 92652 of which 348 recycled<LF>Exception stack ram used: 296<LF>Never used ram: 12088<LF>Tasks: NETWORK(ready,1280) HEAT(blocked,872) MAIN(running,3800) IDLE(ready,200)<LF>Owned mutexes:<LF>=== Platform ===<LF>Last reset 00:00:55 ago, cause: software<LF>Last software reset time unknown, reason: Watchdog timeout, spinning module Platform, available RAM 11396 bytes (slot 1)<LF>Software reset code 0x0050 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x14433014 BFAR 0xe000ed38 SP 0x2001fe64 Task 0x5754454e<LF>Stack: 0040d3db 0040d4dc 6100001f 20012c10 00000000 2000c960 0002f59e 2000c870 fffffff1 2000c960 00000000 0002f59e 20012bb0 00000007 0041922d 00419322 21000027 2000ba7c 2000c870 20007fc0 20007fc0 40090000 03e38406<LF>Error status: 0<LF>Free file entries: 10<LF>SD card 0 detected, interface speed:[Warning: Maximal number of bytes per line exceeded! Check the EOL (end-of-line) settings or increase the limit in the advanced terminal settings.]
-
Upgrade to 2.05.1 and change your YAT end of line settings so that we can see the full M122
-
end of line setting not used yat before so not sure how to
-
It's in the text terminal settings of YAT
Setup YAT to use <LF> as the end of line character. Go to "Terminal" Menu -> "Settings" -> "Text Settings" -> "EOL sequence:" set to <LF>
-
@Phaedrux said in Duet wifi 2 reset when trying to home printer:
2.05.1
is it combined firmware "https://github.com/dc42/RepRapFirmware/releases/download/2.05.1/Duet2CombinedFirmware.bin2" ?
-
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later
Board ID: 08DGM-9T6BU-FG3SN-6J1DD-3S86J-TBZRF
Used output buffers: 1 of 24 (13 max)
=== RTOS ===
Static ram: 25712
Dynamic ram: 92696 of which 304 recycled
Exception stack ram used: 328
Never used ram: 12032
Tasks: NETWORK(ready,676) HEAT(blocked,848) MAIN(running,3816) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:04:19 ago, cause: software
Last software reset at 2020-04-30 22:17, reason: Watchdog timeout, spinning module Platform, available RAM 11556 bytes (slot 2)
Software reset code 0x4050 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f014 BFAR 0xe000ed38 SP 0x2001ff04 Task 0x4e49414d
Stack: 0041922d 004192f6 21000027 2000ba7c 2000c870 20007fc0 20007fc0 40090000 0964e770 20000660 00419979 09622875 2000ba78 2000ba7c 0041ba45 0964e770 00419001 20007fc0 00000004 20017698 2000065c 00000006 00000007
Error status: 10
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 366.0ms, max retries 0
MCU temperature: min 31.0, current 31.4, max 31.8
Supply voltage: min 12.6, current 12.9, max 13.0, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 2020-04-30 22:36:21
Cache data hit count 774859868
Slowest loop: 51.68ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Stack records: 2 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 ready with "M122" 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
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 367.54ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 0 of 8- WiFi -
Network state is running
WiFi module is providing access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.23
WiFi MAC address 86:f3:eb:83:4d:bc
WiFi Vcc 3.44, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 24776
WiFi IP address 192.168.102.60
Connected clients 0
Socket states: 0 0 0 0 0 0 0 0
- WiFi -
-
What LEDs are lit on the smart effector?
What gcode are you running when this happens?
-
no lights on smart effector only green when tapped , not fully wires smart effector up just testing printer homing before, tried unplugging but still get same issue.
-
When you first power up, does the green led on the smart effector flash, and if so, how many times?
-
@Danal , just flashes green twice then stops.
-
do u think worth just resetting duet 2 board
-
Does it home the printer and then reset; or reset without moving the carriages at all?
Please post your homedelta.g file.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@Phaedrux G28
-
@dc42 nope tries to move carriages home then trips
-
@chris said in Duet wifi 2 reset when trying to home printer w smart effector:
@dc42 nope tries to move carriages home then trips
Are sure you have the endstop switches connected to the right pins on the connectors on the Duet?
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42, here is homedelta.g
; homedelta.g
; called to home all towers on a delta printer
;
; generated by RepRapFirmware Configuration Tool on Sat Oct 27 2018 13:30:24 GMT+0100 (British Summer Time)
G91 ; relative positioning
;*** Slow homing has been configured. Change F480 to F4800 below when your configuration is working
G1 S1 X625 Y625 Z625 F4800 ; move all towers to the high end stopping at the endstops (first pass)
G1 X-5 Y-5 Z-5 F4800 S2 ; go down a few mm
G1 S1 X10 Y10 Z10 F480 ; move all towers up once more (second pass)
G1 Z-5 F4800 ; move down a few mm so that the nozzle can be centred
G90 ; absolute positioning
G1 X0 Y0 F4800 ; move X+Y to the centre -
@dc42 yes, x stop, y stop and z stop. on duet web says endstop 0 , 1 , 2 not triggered and endstop 3 is triggered.
-
Even disconnecting everything a part from endstops and trying each moter cause board to reset
-
re uploading replicator configuration seemed to have solved it but not sure why in first place
