Duet 2 wifi and duex5 bltouch not working
-
here are some images of how I have it wired in, and here is how I have it configured config.g based on just the configurator just updated to v3.11 per your reccomendation -
second update - after looking back over the wiring diagram again I found another jumper pin I missed, bltouch is now probing and onto figuring out the Z haha
-
@tsxfire looks like you’ve got a cloned Duet, in case you’re not aware.
Ian
Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth
-
@droftarts I'm aware, I wanted to dip my toes in the water with reprap and stuff before spending the premium for the nicer ones with higher quality and a friend had this to loan to me while I test and compare to my klipper/marlin experience, not sure why but after updating to reprap 3.11 it no longer detects my pt1000 thermistor
-
@tsxfire said in Duet 2 wifi and duex5 bltouch not working:
after updating to reprap 3.11 it no longer detects my pt1000 thermistor
It's time to upload your config.g
-
This post is deleted! -
I see it now. Could you copy and paste it into a post? It's not possible to view gcode files on mobile unfortunately.
-
; Configuration file for Duet WiFi (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.1.4 on Wed Jul 15 2020 11:55:59 GMT-0500 (Central Daylight Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"My Printer" ; set printer name M669 K1 ; select CoreXY mode ; Network 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 backwards M569 P3 S1 ; physical drive 3 goes forwards M569 P4 S1 ; physical drive 4 goes forwards M569 P5 S1 ; physical drive 5 goes forwards M584 X0 Y1 Z2:5 E3:4 ; set drive mapping m671 x-20:370 y48.5:48.5 s0.5 m208 x0:350 y-168:267 M350 X16 Y16 Z16:16 E16:16 I1 ; configure microstepping with interpolation M92 X100.00 Y100.00 Z400.00:200 E436.54:436.54 ; set steps per mm M566 X1500.00 Y1500.00 Z12.00:12 E120.00:120.00 ; set maximum instantaneous speed changes (mm/min) M203 X6000.00 Y6000.00 Z180:180 E12000.00:12000.00 ; set maximum speeds (mm/min) M201 X500.00 Y500.00 Z20.00:20 E1000.00:1000.00 ; set accelerations (mm/s^2) M906 X1500 Y1500 Z1500:1500 E1000:1000 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 X0 Y-163 Z0 S1 ; set axis minima M208 X350 Y260 Z400 S0 ; set axis maxima ; 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 S2 ; configure Z-probe endstop for low end on Z ; Z-Probe M950 S0 C"duex.pwm5" ; create servo pin 0 for BLTouch M558 P9 C"^zprobe.in" H0 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 X15:215 Y-148:195 S20 ; 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 M308 S2 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 2 as thermistor on pin e0temp M950 H2 C"e1heat" T2 ; create nozzle heater output on e1heat and map it to sensor 2 M307 H2 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit ; 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 M950 F2 C"fan2" Q500 ; create fan 2 on pin fan2 and set its frequency M106 P2 S1 H2 T45 ; set fan 2 value. Thermostatic control is turned on ; Tools ; Custom settings are not defined ; Miscellaneous M575 P1 S1 B57600 ; enable support for PanelDue -
just changed m308 "thermistor" over to "pt1000" and still not coming up for some reason
-
@tsxfire the M350, M92, M566, M203, M201, M906 may have only one value for Z, because XYZ are axis defined, so only one value each, E may have multiple values. The two Z actuators must have the same properties, M92 different steps per mm is not possible.
m208 x0:350 y-168:267
can be removed, because you define M208 some lines lower.G31 in most cases for BLTouch the P should be 25. The X and Y values must be set, otherwise mesh compensation will compensate at the wrong XY coordinates.
You have the same name e0temp for two termistors. For termistors P is used for the pin name: https://duet3d.dozuki.com/Wiki/Gcode#Section_M308_Set_or_report_sensor_parameters "P"pin_name" The name of the control board pin that this sensor uses. For thermistors it is the thermistor input pin name." There are examples at the end of the M308 documentation.
-
I left the g31 value as it was, and the z is actually working fine now, it's going up and down on the z without issues as well as probing with the settings listed above, but still haven't figured out why my pt1000s disappeared, they show up for half a second when initially booting but then it goes away for some reason....
-
@tsxfire it doesn't work like explained you define M308 wrong and double.
I would not let the wrong settings wrong, may have unexpected side effects.Please don't forget to set X and Y for G31 later, because often correcting at the wrong positions is worse than not using the G31 at all.
-
I just used configurator tool for that part, I have dual hotends which is why there is double. I'll adjust the g31 later but focusing on the little things functioning in general before I focus on offsets necessarily
-
also, the z having different variables is because I have 2 different motors - independent z - and one has a 16:20 tooth pulley setup while other has a 20:20 tooth pulley setup going into a t8 leadscrew, the settings I have set make it accurate to the mm for the z on that front from testing
-
@tsxfire as the documentation for M92 says, the second parameter is ignored:
https://duet3d.dozuki.com/Wiki/Gcode#Section_M92_Set_axis_steps_per_unit
"RepRapFirmware does not support individual motor settings where an axis has multiple motors connected to different stepper drivers. The first parameter specified will be used for all motors on the axis. You should use identical motors on any axis that has more than one motor to avoid unexpected behaviour.Example: If you have two motors on your Z axis, physically connected to Z and E0 stepper drivers, configured with M584 Z2:3, set M92 Z80, not M92 Z80:80"
-
@tsxfire said in Duet 2 wifi and duex5 bltouch not working:
I just used configurator tool for that part, I have dual hotends which is why there is double. I'll adjust the g31 later but focusing on the little things functioning in general before I focus on offsets necessarily
The problem is not that you use two thermistors, but that you configure both with the same P parameter, which is used for the pin names (please see the documentation of the link I posted). Your config file says that both therminators are connected to one pin together, and the pin name is IMHO not correct. If you change the P parameters to the correct pin names and make the thermistor wiring to those pins, I expect it's working. Please use two pin connections, one for each thermistor.
The pin names are documented here:
https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview#Section_Pin_names_for_Duet_2_WiFi_Ethernet
So bedtemp, e0temp and e1temp in your case for the P parameter. Only the
M308 S2 P"e0temp" Y"thermistor" T100000 B4138
needs to be renamed to
M308 S2 P"e1temp" Y"thermistor" T100000 B4138
then it should work. (But check that this thermistor is connected to the correct hotend...) -
@Phaedrux said in Duet 2 wifi and duex5 bltouch not working:
I see it now. Could you copy and paste it into a post? It's not possible to view gcode files on mobile unfortunately.
It's possible, just a hassle, and an extra step that gets in the way of supporting people. I don't know about on Android, but on iOS I had to install a file manager (I used 'FileMaster' from AppStore). Then I can download a config.g file, send it to the file manager, then open it there.
Ian
Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth
-
@droftarts said in Duet 2 wifi and duex5 bltouch not working:
'FileMaster' from AppStore
Thanks. I hadn't heard of that one before.
-
I went through the configurator and chose 2 hotends with PT1000 and got this for the heater block
; 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"pt1000" R4700 ; configure sensor 1 as PT1000 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 M308 S2 P"e1temp" Y"pt1000" R4700 ; configure sensor 2 as PT1000 on pin e1temp M950 H2 C"e1heat" T2 ; create nozzle heater output on e1heat and map it to sensor 2 M307 H2 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit -
@Phaedrux I will give that a try, I wasn't seeing where could specify the pt1000 in configurator
