Troodon 400 bltouch trouble
-
Hi everyone,
I recently got a Troodon 400. I swapped the stock hotend for a Dragon high flow as I intend to print large items with large nozzles with the printer a fair amount.
I was having a persistent problem setting my z offset on the stock firmware (it was 2 something). I did some reading and saw it suggested to update the firmware. RRF3 was described as better for easily setting the z offset, so I updated to RRF3.
Now my bltouch won't work. It cycles itself when I power the printer off and on, but I can't get it to deploy via the panelDue or the web control.
I suspect that my config is off but I don't have any idea what I'm looking for. If someone could be so kind as to give me some help I'd be most grateful. This printer is a large expensive brick until I can get the bltouch working. I'll include the section of my config.g file below. If I've not included the relevant section please advise which to supply. Thanks!
; Z-Probe
; Original 2.20 bltouch
;M574 Z1 S0 ; Set endstops controlled by probe
;M307 H7 A-1 C-1 D-1 ; Disable heater on PWM channel for BLTouch
;M558 P5 X0 Y0 Z1 H5 F300 T6000 ; Set Z probe type to bltouch and the dive height + speedsNew 3.0 bltouch
;M574 Z0 P"nil" ; no Z endstop switch, free up Z endstop input
M558 P9 C"^zprobe.in" H5 R1 F120 T6000 A5 S0.02 ;BLTouch connected to Z probe IN pin
M950 S0 C"duex.pwm5"M574 Z1 S0 ; Set endstops controlled by probe
G31 P50 X0 Y21 Z3.0 ; Set Z probe trigger value, offset and trigger height
M557 X15:285 Y15:285 S50 ; Define mesh grid; Z-Probe
M574 Z0 P"nil" ; no Z endstop switch, free up Z endstop input
M558 P9 C"^zprobe.in" H5 R1 F120 T6000 A5 S0.02 ;BLTouch connected to Z probe IN pin
M950 S0 C"duex.pwm5"M574 Z1 S0 ; Set endstops controlled by probe
G31 P50 X0 Y21 Z3.0 ; Set Z probe trigger value, offset and trigger height
M557 X15:285 Y15:285 S50 ; Define mesh grid -
It looks like you're duplicating the probe configuration. Tidy that up.
Check out this config for reference.
https://github.com/Duet3D/RRF-machine-config-files/blob/master/Vivedino Troodon 300/sys/config.g
When you updated to RRF did you also change your deployprobe.g and retractprobe.g files? The command syntax has changed.
-
@phaedrux Thanks for that. I've removed the duplicate lines but still no functional bltouch.
I don't know what the syntax should be like for the deployprobe.g and retractprobe.g, here is what I've got currently with RRF3. Is there any difference between RRF 3 and RRF3.4? If they're the same I'll just copy and paste them.
; deployprobe.g
; called to deploy a physical Z probe
;
; generated by RepRapFirmware Configuration Tool v2 on Wed Apr 24 2019 22:25:27 GMT+0800 (中国标准时间)
M280 P7 S10; retractprobe.g
; called to retract a physical Z probe
;
; generated by RepRapFirmware Configuration Tool v2 on Wed Apr 24 2019 22:25:27 GMT+0800 (中国标准时间)
M280 P7 S90I'm a genuine noob when it comes to working with RRF. Would it make sense to simply upload the Troodon 300 config files you linked to and then adjust the parameters to fit the 400?
Thanks again.
-
I've changed the deploy and retract to the RRF3 syntax and cleaned up the config.g file as you suggested but still not getting any control of the probe via web control or hardware.
Perhaps I'll have to contact the manufacturer for their version of the older firmware if that's possible.
-
@bubblehead you've specified M950 SO when creating servo channel 0 on duex.pwm5, but then used M280 P7. I think you should be using M280 PO. Give it a go?
-
The entire set of example files are there: https://github.com/Duet3D/RRF-machine-config-files/tree/master/Vivedino Troodon 300/sys
The syntax in RRF3 is
M280 P0to match theM950 S0 -
@lo-fi Thanks. I updated to 3.4 and the deploy and retract are now as follows:
; deployprobe.g
; called to deploy a physical Z probe
;
; generated by RepRapFirmware Configuration Tool v2 on Wed Apr 24 2019 22:25:27 GMT+0800 (中国标准时间)
M280 P0 S10; retractprobe.g
; called to retract a physical Z probe
;
; generated by RepRapFirmware Configuration Tool v2 on Wed Apr 24 2019 22:25:27 GMT+0800 (中国标准时间)
M280 P0 S90The bltouch is still not responding.
I'll try uploading the files that Phaedrux shared and see if that fixes it. I'll obviously change the parts that are specific to the 400 troodon.
-
Probably helpful at this point to post your full config.g, plus the results of sending M98 P"config.g" and M122
I take it you've not changed the wiring since it was working on RRFv2?
Which Duet board is in the Troodon?
-
@lo-fi said in Troodon 400 bltouch trouble:
Which Duet board is in the Troodon?
They use a unique modified clone/derivative of the Duet.
-
@lo-fi The only changes I've made are switching the stock hotend to a Dragon high flow. Didn't mess with any wiring. The stock board is as Phaedrux mentioned a Duet-ish board. It's been described as a Duet 2 wifi with an extension built in or something like that.
Here's the info you suggested posting;
config.g:
; Configuration file for Duet WiFi (firmware version 1.20 or newer) ; executed by the firmware on start-up ; --- general preferences --- M111 S0 ; debugging off G21 ; work in millimetres G90 ; send absolute coordinates M83 ; relative extruder moves M555 P2 ; set firmware compatibility to look like Marlin M667 S1 ; select CoreXY mode M208 X5 Y0 Z0 S1 ; set axis minima to end of safe travel. M208 X410 Y408 Z510 S0 ; set axis maxima to match endstop location. ; ---filament sensing--- M591 D0 P1 C"e0_stop" S1 ; Automatic power saving M911 S21 R23 P"M913 X0 Y0 G91 M83 G1 Z0 E-3 F1000" ; Set voltage thresholds and actions to run on power loss ; --- endstops --- M574 X2 S1 P"^xstop" M574 Y2 S1 P"^ystop" M574 Z1 S0 ; Z-Probe M950 S0 C"duex.pwm5" M558 P9 C"^zprobe.in" H5 F120 T6000 ; Duet 2 WiFi/Ethernet, DueX2/5 G31 X20 Y0 Z3.3 P25 ; Set Z probe trigger value, offset and trigger height M557 X15:285 Y15:285 S50 ; Define mesh grid ; --- drives --- M569 P0 S1 ; X M569 P1 S1 ; Y ;M569 P2 S0 ; Z M569 P3 S1 ; E0 ;M569 P4 S1 ; E1 ; -- duex -- M569 P5 S1 ; Z5 M569 P6 S0 ; Z6 M569 P7 S1 ; Z7 M569 P8 S0 ; Z8 M569 P2 R-1 M569 P4 R-1 M569 P9 R-1 ; --- z-axis stepper leveling configuration --- M584 X0 Y1 E3 Z6:5:8:7 ; four motors, at 5, 6, 7, and 8 M671 X-100:-100:420:420 Y380:-115:-115:380 S20 ; Z belts at 4 corners ; --- drive map --- ; _______ ; | 6 | 7 | ; | ----- | ; | 5 | 8 | ; ------- ; front M350 X16 Y16 Z16 E16 I1 ; microstepping with interpolation (I1) M92 X80 Y80 Z400 E400 ; steps per mm - with bt M566 X2000 Y2000 Z602.65 E1000 ; maximum instantaneous speed changes (mm/min) (jerk) M203 X20000 Y20000 Z1500 E10000 ; maximum speeds (mm/min) M201 X1500 Y1500 Z500 E10000 ; accelerations M906 X1200 Y1200 Z1200 E1250 I60 ; motor currents (mA) and motor idle factor in per cent M84 S60 ; set idle timeout ; Network M550 P"VIVEDINO" ; Set machine name M552 S1 ; Enable network M587 S"FORMBOT" P"zxcv555578" ; Configure access point. You can delete this line once connected M586 P0 S1 ; Enable HTTP M586 P1 S0 ; Disable FTP M586 P2 S0 ; Disable Telnet ; --- firmware retraction --- ;M207 S2.5 R0 F6500 T4500 Z0 ; [ Snnn positive length to retract, in mm ] ; [ Rnnn positive or negative additional length to un-retract, in mm ] ; [ Fnnn retraction feedrate, in mm/min ] ; [ Tnnn feedrate for un-retraction if different from retraction, mm/min ] ; [ Znnn additional zlift/hop ] ; --- heaters --- M308 S0 P"bed_temp" Y"thermistor" T100000 B4138 C0 R4700 ; define bed temperature sensor M308 S1 P"e0_temp" Y"thermistor" T100000 B4138 C0 R4700 ; define E0 temperature sensor M950 H0 C"bed_heat" T0 ; heater 0 uses the bed_heat pin, sensor 0 M950 H1 C"e0_heat" T1 ; heater 1 uses the e0_heat pin and sensor 1 M140H0 ;M305 P0 T100000 B4138 C0 R4700 ; set thermistor + ADC parameters for heater 0 M307 H3 A-1 C-1 D-1 ; set PID tuned settings for heater 0 M143 H0 S125 ; set temperature limit for heater 0 to 120C ;M305 P1 T100000 B4138 C0 R4700 ; set thermistor + ADC parameters for heater 1 M307 H1 A517.3 C213.3 D11.1 V24.3 B0 ; set PID tuned settings for heater 1 M143 H1 S280 ; set temperature limit for heater 1 to 280C ; --- tools --- M563 P0 D0 H1 ; 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 ; --- fans --- M950 F0 C"fan0" ; Fan 0 uses the Fan0 output M950 F1 C"fan1" ; Fan 1 uses the Fan1 output M950 F2 C"fan2" ; Fan 2 uses the Fan2 output M106 P0 S0 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off M106 P1 S0.9 I0 F500 H1 T50 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on M106 P2 S1 I0 F500 H1 T50 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on M572 D0 S.15 ;M572 D0 S.4 ; Linear Advance ;M592 D0 A0.01 B0.0005 ;nonlinear extrusion ; --- Set or report heating process parameters--- M106 P3 I-1 M106 P4 I-1 M106 P5 I-1 M106 P6 I-1 M106 P7 I-1 M106 P8 I-1 ; --- RGB leds - White --- M950 P1 C"duex.fan4" M950 P2 C"duex.fan5" M950 P3 C"duex.fan6" M42 P1 S1.0 ; R- M42 P2 S1.0 ; G- M42 P3 S1.0 ; B- ; --- Case Fan --- M950 P5 C"duex.fan7" M42 P5 S0.0 ; ; --- Controller Fan --- M950 P4 C"duex.fan8" M42 P4 S0.5 ; M501M98 P"config.g" results:
M98 P"config.g"
Error: endstop type 0 is no longer supported. Use type 1 and invert the input pin instead.
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Error: Heater 3 not found
Error: Fan number 3 not found
Error: Fan number 4 not found
Error: Fan number 5 not found
Error: Fan number 6 not found
Error: Fan number 7 not found
Error: Fan number 8 not foundM122 results:
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.0 (2022-03-15 18:58:31) running on Duet WiFi 1.02 or later + DueX5
Board ID: 0JD2M-958DA-F6NSW-6J9FA-3S06P-TQJ70
Used output buffers: 3 of 24 (16 max)
=== RTOS ===
Static ram: 23868
Dynamic ram: 75248 of which 64 recycled
Never used RAM 12900, free system stack 182 words
Tasks: NETWORK(ready,13.1%,228) HEAT(notifyWait,0.0%,328) Move(notifyWait,0.0%,364) DUEX(notifyWait,0.0%,24) MAIN(running,86.5%,412) IDLE(ready,0.3%,30), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:04:17 ago, cause: power up
Last software reset at 2022-04-13 18:52, reason: User, GCodes spinning, available RAM 12708, 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
Step timer max interval 0
MCU temperature: min 18.6, current 25.0, max 25.3
Supply voltage: min 24.2, current 24.4, max 24.6, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 3 queued, 3 completed
Driver 0: standstill, SG min n/a
Driver 1: standstill, SG min n/a
Driver 2: over temperature warning, over temperature shutdown, phase A short to ground, phase B short to ground, standstill, SG min n/a
Driver 3: standstill, SG min n/a
Driver 4: over temperature warning, over temperature shutdown, phase A short to ground, phase B short to ground, standstill, SG min n/a
Driver 5: standstill, SG min n/a
Driver 6: standstill, SG min n/a
Driver 7: standstill, SG min n/a
Driver 8: standstill, SG min n/a
Driver 9: over temperature warning, over temperature shutdown, phase A short to ground, phase B short to ground, standstill, SG min n/a
Driver 10:
Driver 11:
Date/time: 2022-04-14 16:39:04
Cache data hit count 4294967295
Slowest loop: 7.86ms; fastest: 0.19ms
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.9ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== 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
=== Filament sensors ===
Extruder 0 sensor: ok
=== DueX ===
Read count 1, 0.23 reads/min
=== Network ===
Slowest loop: 16.77ms; 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.26
WiFi MAC address 98
ac:13:09:01
WiFi Vcc 3.36, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 24640
WiFi IP address 192.168.1.20
WiFi signal strength -45dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 4 0 0 0 0 0 0 0
- WiFi -
-
@bubblehead said in Troodon 400 bltouch trouble:
M574 Z1 S0
This immediately jumps out at me. It's the cause of the "Error: endstop type 0 is no longer supported. Use type 1 and invert the input pin instead." message. I'm not 100% that's why the servo pin isn't responding, but it's a good place to start.
You need to use S2 for a Z probe. I'm assuming there's no Z end stop as well as the BLTouch?
-
Thanks, I'll switch that value and see what happens.
That's correct, there is no z end stop other than the bltouch.
-
Sad to say changing the S0 to S2 didn't fix it.
-
@bubblehead concentrate on getting the BLTouch to deploy and retract when you send M401 and M402.
We have one other report that BLTouch doesn't work when connected to duex.pwm4 or duex.pwm5 and using RRF 3.4. I will test this next week when I am back in the office. Meanwhile you could try using port duex.pwm3 instead, or use firmware 3.3 instead of 3.4.
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 -
After changing the M574 Z1 S0 to M574 Z1 S2 the probe will deploy and retract via M401 and M402.
That's a relief. I'll see if I can get back to 3.3. Fingers crossed. Thanks for stopping in to offer help.
-
The bltouch is working as it should now. Not sure what the issue was. I am having a new issue where the gantry is crashing when I run a G32. It seems my configuration is off. I don't know where to look for problems with that.
The setup on the Troodon is very much like a Voron 2.4. The Z axis is controlled by four steppers and it uses the bltouch to tram the gantry.
The specific issue is that the Y and X axes are overshooting and the bltouch is attempting to probe outside the bed.
-
@bubblehead said in Troodon 400 bltouch trouble:
The specific issue is that the Y and X axes are overshooting and the bltouch is attempting to probe outside the bed.
You define the points to probe in bed.g
-
@bubblehead said in Troodon 400 bltouch trouble:
The bltouch is working as it should now.
Is this with firmware 3.4 ?
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 -
I've reverted back to the firmware that the printer shipped with and the bltouch is working as it should. That's RRF2.03
Everything seems to be working as it should now, except that the gantry and printhead crash during the tramming sequence. I'm in contact with the manufacturer who's been pretty responsive so far. I've got my fingers crossed I can get it sorted before too much longer.
-
I'm going to consider this resolved and create a new thread with my new problem where my gantry and printhead are crashing on the tramming sequence.
Thanks to all that offered help.
