Duet 2 wifi and duex5 bltouch not working

tsxfire

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

tsxfire

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

JoergS5

@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"

JoergS5

@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...)

droftarts

@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

Phaedrux

@droftarts said in Duet 2 wifi and duex5 bltouch not working:

'FileMaster' from AppStore

Thanks. I hadn't heard of that one before.

Phaedrux

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

tsxfire

@Phaedrux I will give that a try, I wasn't seeing where could specify the pt1000 in configurator

Phaedrux

It's in the sensor drop down for the heater.

tsxfire

It appears to be working after going back through and remaking the configuration in the configurator, maybe something didn't like transferring over from 2.0 firmware with the updates but it's working now! thank you for the help!

beachtec

This post is deleted!