Tevo Little monster crashes at enstop
-
I just finished wiring up the Duet 2 wifi on my TLM, im having a problem where the printer doesnt stop and the enstop and continues to travel until i emergency stop. with the M119 commend it shoes all three endstops triggered, but still crashed with the G28 command. Im very new to RR firmware as i just switched from marlin. Any help is appriciated!
; homedelta.g
; called to home all towers on a delta printer
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Wed Mar 03 2021 12:58:55 GMT-0800 (Pacific Standard Time)
G91 ; relative positioning
G1 H1 X705 Y705 Z705 F1800 ; move all towers to the high end stopping at the endstops (first pass)
G1 H2 X-5 Y-5 Z-5 F1800 ; go down a few mm
G1 H1 X10 Y10 Z10 F360 ; move all towers up once more (second pass)
G1 Z-5 F6000 ; move down a few mm so that the nozzle can be centred
G90 ; absolute positioning
G1 X0 Y0 F6000 ; move X+Y to the centre; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Wed Mar 03 2021 12:58:55 GMT-0800 (Pacific Standard Time); General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"My Printer" ; set printer name
M665 R155 L397.19 B85 H515 ; Set delta radius, diagonal rod length, printable radius and homed height
M666 X0 Y0 Z0 ; put your endstop adjustments here, or let auto calibration find them; Network
M551 P"password" ; set password
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S1 ; enable FTP
M586 P2 S1 ; enable Telnet; Drives
M569 P0 S1 ; physical drive 0 goes forwards
M569 P1 S1 ; physical drive 1 goes forwards
M569 P2 S1 ; physical drive 2 goes forwards
M569 P3 S1 ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z80.00 E663.00 ; set steps per mm
M566 X1200.00 Y1200.00 Z1200.00 E1200.00 ; set maximum instantaneous speed changes (mm/min)
M203 X18000.00 Y18000.00 Z18000.00 E1200.00 ; set maximum speeds (mm/min)
M201 X1000.00 Y1000.00 Z1000.00 E1000.00 ; set accelerations (mm/s^2)
M906 X1000 Y1000 Z1000 E800 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Axis Limits
M208 Z0 S1 ; set minimum Z; Endstops
M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop
M574 Z1 S1 P"zstop" ; configure active-high endstop for low end on Z via pin zstop; Z-Probe
M950 S0 C"exp.heater7" ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X0 Y0 Z2.5 ; set Z probe trigger value, offset and trigger height
M557 R150 S45 ; define mesh grid; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S280 ; set temperature limit for heater 1 to 280C; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on; Tools
M563 P0 D0 H1 F0 ; define tool 0
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C; Custom settings are not defined
-
Does M119 show not triggered when the endstops are not pressed and triggered when they are pressed?
Are you sure you've go the endstops connected to the right terminals to match the motors? See here: https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareDeltaPrinter#Section_Testing_the_motors_and_endstops_individually
Also, these links will be handy in case you haven't seen them yet
-
3/3/2021, 2:14:31 PM m119
Endstops - X: at min stop, Y: at min stop, Z: at min stop, Z probe: not stoppedI verfied my wireing. Then i manually triggered each endstop and the corresponding LED turns off. Its my y axis this is actuing strange. when i have the x and z stop without issue, but then the y stepper starts jamming before it gets to the endstop. In frustration i pushed it the rest of the way and it counted as home. If i use home all again after it had been shoved to the endstop it acts fine. I am following the wiki for calibration but im stuck at homing right now.
-
@Phaedrux If i hold the printer home before start it will home fine. I can move it down to the bed and when i bring it to the max it stops and the endstops properly. but as soon as i send a G28 its comes up and crashes.
-
Can you provide the results of sending M122 and M98 P"config.g"?
-
You've gone through this part?
Testing the motors and endstops individually
You can test the three tower motors individually by putting the printer in relative mode (G91 command) and then using the G1 command with H2 parameter. For example, sending G1 S2 X10 should move the X carriage up 10mm, and sending G1 H2 X-10 should move the X carriage down 10mm. Similarly for Y and Z. If a motor moves the wrong way, you can reverse it by changing the corresponding M569 command in config.g. For example, if the X motor moves the wrong way, change M569 P0 S1 to M569 P0 S0.When you have the motors moving the right way, test the endstops. See Connecting endstop switches.
It is essential that the endstop switch connected to the X endstop input is on the same tower as the motor connected to the X motor output that drives the carriage on the X tower. A common mistake is to have endstop or motor connections swapped. So check this carefully. Make sure that the carriage that moves when you send a G1 S2 X command is on the same tower as the endstop that when triggered shows as X triggered in M119 or in the Machine Properties page of DWC.
After that you can check the combined effects of endstop switches and motors. Send G91 as before, but use H1 instead of H2 in the G1 commands. Each motor should stop early when you trigger the corresponding endstop.
-
@Phaedrux said in Tevo Little monster crashes at enstop:
M122
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05 running on Duet WiFi 1.02 or later
Board ID: 0JD0M-9P6B2-NJ4S8-6JKDJ-3S46K-TS6QM
Used output buffers: 1 of 24 (8 max)
=== RTOS ===
Static ram: 25712
Dynamic ram: 92464 of which 536 recycled
Exception stack ram used: 480
Never used ram: 11880
Tasks: NETWORK(ready,744) HEAT(blocked,808) MAIN(running,3824) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:52:07 ago, cause: power up
Last software reset at 2021-03-03 15:21, reason: User, spinning module GCodes, available RAM 11944 bytes (slot 0)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 23.4, current 23.8, max 27.4
Supply voltage: min 0.3, current 24.1, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max 78/345
Driver 1: standstill, SG min/max 96/337
Driver 2: standstill, SG min/max 49/325
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 2021-03-03 16:45:29
Cache data hit count 4294967295
Slowest loop: 5.07ms; fastest: 0.05ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 160, MinFreeDm: 154, MaxWait: 361900ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 141, completed moves: 141, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 0 in use
Movement lock held by null
http is ready with "M122 " 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
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 80.14ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8- WiFi -
Network state is running
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.23
WiFi MAC address 48:3f:da:88:8a:06
WiFi Vcc 3.36, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 22832
WiFi IP address 10.0.0.33
WiFi signal strength -40dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0
3/3/2021, 4:46:53 PM M98 P"config.g"
HTTP is enabled on port 80
FTP is enabled on port 21
TELNET is enabled on port 23
Warning: M950 command is not supported
Warning: M308 command is not supported
Warning: M950 command is not supported
Warning: M308 command is not supported
Warning: M950 command is not supported
Warning: M950 command is not supported
Warning: M950 command is not supported
Error: G29: Must home printer before bed probing - WiFi -
-
Ok, so your config.g is formatted for RRF3, but your duet only has RRF2 installed. Updating your firmware should help get things back on track.
If you still have access to DWC. Upload these 3 zip files, one at a time in the system tab. Don't extract them. Reboot after each. Use M115 to verify the firmware has been applied.
https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/Duet2Firmware-2.05.1.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.0/Duet2and3Firmware-3.0.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.2.2/Duet2and3Firmware-3.2.2.zip
That will get your firmware and DWC up to date.After that's done, send M122 and M98 P"config.g" again and report the response. Homing will likely work better then as well.
-
@Phaedrux said in Tevo Little monster crashes at enstop:
G1 H2 X-10
3/3/2021, 5:18:33 PM m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet WiFi 1.02 or later
Board ID: 0JD0M-9P6B2-NJ4S8-6JKDJ-3S46K-TS6QM
Used output buffers: 3 of 24 (13 max)
=== RTOS ===
Static ram: 23460
Dynamic ram: 72436 of which 24 recycled
Never used RAM 16160, free system stack 191 words
Tasks: NETWORK(ready,169) HEAT(blocked,308) MAIN(running,451) IDLE(ready,20)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:00:19 ago, cause: software
Last software reset at 2021-03-03 17:18, reason: User, GCodes spinning, available RAM 16124, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 24.9, current 25.4, max 25.9
Supply voltage: min 24.0, current 24.2, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 70856, standstill, SG min/max not available
Driver 1: position 70856, standstill, SG min/max not available
Driver 2: position 70856, standstill, SG min/max not available
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 2021-03-03 17:18:32
Cache data hit count 22939044
Slowest loop: 5.47ms; fastest: 0.21ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 3.4ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
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
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 16.17ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8- WiFi -
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.25
WiFi MAC address 48:3f:da:88:8a:06
WiFi Vcc 3.36, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 24400
WiFi IP address 10.0.0.33
WiFi signal strength -44dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
3/3/2021, 5:19:04 PM M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabledAwesome! ok i am homing properly now. Thank you for your time and help im going to follow the Delta calibration you sent me and hope all goes well from here. Thanks again!
- WiFi -
