Weird issue after 2.x -> 3.0 -> 3.2.2 upgrade on Duet2 Wifi...
-
@jay_s_uk Here you go: (I copied it from the web interface editor)
; RostockMAX v3.2 SeeMeCNC 3D Printers
; General preferences
G90 ; absolute coordinates
M83 ; relative extruder moves
M550 P"Centurion" ; set printer name
;M665 R150 L339.47 B145 H530 ; Carbon Fiber ARMS Set delta radius, diagonal rod length, printable radius and homed height
;M665 R150 L351.1 B145 H530 ; Injection Molded ARMS Set delta radius, diagonal rod length, printable radius and homed height
M665 R144 L291.06 B135 H400 X0 Y0 Z0 ; Rostock MAX v3.2, stock arms
M666 X0 Y0 Z0 ; put your endstop adjustments here, or let auto calibration find them; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet; Drives
M569 P0 S0 ; physical drive 0
M569 P1 S0 ; physical drive 1
M569 P2 S0 ; physical drive 2
M569 P3 S1 ; physical drive 3
M569 P4 S1 ; physical drive 4
M584 X0 Y1 Z2 E3:4 ; set drive mapping
M350 X16 Y16 Z16 E16:16 I1 ; configure micro stepping with interpolation
M92 X200.00 Y200.00 Z200.00 E182.00:182.00 ; set steps per mm
M566 X700.00 Y700.00 Z700.00 E2000.00:2000.00 ; set maximum instantaneous speed changes (mm/min)
M203 X10000.00 Y10000.00 Z10000.00 E9000.00:9000.00 ; set maximum speeds (mm/min)
M201 X1400.00 Y1400.00 Z1400.00 E5000.00:5000.00 ; set accelerations (mm/s^2)
M906 X1500 Y1500 Z1500 E1600:1600 I40 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Axis Limits
M208 Z0 S1 ; set minimum Z; End-stops
M574 X2 S1 P"xstop" ; configure active-high endstop for high end on X via pin xstop
M574 Y2 S1 P"ystop" ; configure active-high endstop for high end on Y via pin ystop
M574 Z2 S1 P"zstop" ; configure active-high endstop for high end on Z via pin zstop; Z-Probe
M558 P5 I0 A2 R0.4 C"zprobe.in" H20 F1500 T9000 ; set Z probe type to switch and the dive height + speeds
;M558 P5 I1 A2 R0.4 C"!^zprobe.in" H20 F200 T9000 ; set Z probe type to switch and the dive height + speeds
G31 P500 X0 Y0 Z-0.2 ; set Z probe trigger value, offset and trigger height
M557 R145 S30 ; define mesh grid; Bed Heater
M308 S0 P"bedtemp" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 0 as thermistor on pin bed temp
M950 H0 C"bedheat" T0 ; create bed heater output on bed heat and map it to sensor 0
M307 H0 R0.245 C774.3 D25.92 S1.00 V12.9 ; Bed Heater Process Parameters
M140 H0 ; map heated bed to heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C; Hotend Heater
M308 S1 P"e0temp" Y"thermistor" T100000 B4725 C7.06e-8 ; 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 R2.800 C109.1 D5.12 S1.00 V13.0 ; Hotend Heater Process Parameters
M143 H1 S280 ; Hotend Max Temp; 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"fan2" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 S0.80 H1 T45 ; set fan 1 value. Thermostatic control is turned on; Tool Extruder 1
M563 P0 D0 H1 F0
G10 P0 X0 Y0 Z0
G10 P0 S0 R0; Tool Extruder 2
M563 P1 D1 H1 F0
G10 P1 X0 Y0 Z0
G10 P1 S0 R0;Filament Runout Sensor
M950 J0 C"!^e0Stop" ; create switch pin
M950 J1 C"!^e1stop" ; create switch pin
M581 P0:1 T2 S1 R1 ; run trigger2.g to pause if filament has run out during SD card printing; Miscellaneous
M575 P1 S1 B57600 ; enable support for PanelDue
M501 ; load saved parameters from non-volatile memory
T0 ; select Tool 0
M911 S10.5 R11.2 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss -
Can you run M98 P"config.g" and post any error messages it reports?
@geneb said in Weird issue after 2.x -> 3.0 -> 3.2.2 upgrade on Duet2 Wifi...:
I've tried swapping the X & Y wiring and the problem remains.
Meaning that the X wiring and switch works when on Y endstop?
And the Y wiring and switch doesn't work when connected to the X endstop?What does M119 report?
-
@phaedrux said in Weird issue after 2.x -> 3.0 -> 3.2.2 upgrade on Duet2 Wifi...:
Can you run M98 P"config.g" and post any error messages it reports?
My apologies - I made an incorrect assumption about what that did.
M98 output:
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Warning: Macro file config-override.g not found@geneb said in Weird issue after 2.x -> 3.0 -> 3.2.2 upgrade on Duet2 Wifi...:
I've tried swapping the X & Y wiring and the problem remains.
Meaning that the X wiring and switch works when on Y endstop?
And the Y wiring and switch doesn't work when connected to the X endstop?That is correct.
What does M119 report?
Endstops - X: not stopped, Y: not stopped, Z: not stopped, Z probe: not stopped
The LED on the X axis isn't lit, whereas the LED on the Z and Y axes ARE lit, and they go out when those switches are hit.
tnx.
g.
-
Is this a new DuetWifi? When and where was it purchased?
If you have a free endstop position you could use that instead of xstop, though from your config it looks like you are using e0stop and e1stop as triggers already.
@geneb said in Weird issue after 2.x -> 3.0 -> 3.2.2 upgrade on Duet2 Wifi...:
The LED on the X axis isn't lit
And it never lights up even when depressing the switch? Even faintly?
-
@phaedrux said in Weird issue after 2.x -> 3.0 -> 3.2.2 upgrade on Duet2 Wifi...:
Is this a new DuetWifi? When and where was it purchased?
No, it's an older Duet2Wifi. The printer itself is a Rostock MAX v3.2 and was obtained in 2018. As mentioned previously, it worked fine prior to the upgrade, but that was over a year ago.
The LED on the X axis isn't lit
And it never lights up even when depressing the switch? Even faintly?
It doesn't light at all. Based on the behavior of the Y and Z axis LEDs, it should be lit at all times and go out when the switch is opened.
tnx.
g.
-
You can try using the expansion header pins as an additional endstop.
https://duet3d.dozuki.com/Wiki/Connecting_endstop_switches#Section_Endstop_Mapping
-
@phaedrux said in Weird issue after 2.x -> 3.0 -> 3.2.2 upgrade on Duet2 Wifi...:
You can try using the expansion header pins as an additional endstop.
https://duet3d.dozuki.com/Wiki/Connecting_endstop_switches#Section_Endstop_Mapping
I could, but I don't want a work around. If the config is somehow involved, I need to know how to resolve it. If the x end stop as packed it in, fine - I'll just replace the board.
g.
-
It's not really a work around. It's just using another available pin as an endstop same way as you would E0 or E1. The only difference is that the expansion header pins would normally go to a Duex and you'd use them as endstop pins there. You just get to use them without the duex is all.
It does seem like the endstop is no longer working. I'll see what DC42 thinks, but I don't think it's config related as your config is correct.
-
@geneb this may be one of those odd occasions when downloading the firmware afresh (same version) and reflashing the Duet helps.
Ian
TronXY X5S with Duet 3 MB6HC and Roto toolboard : Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : Polargraph with Duet 2 WiFi
-
@droftarts said in Weird issue after 2.x -> 3.0 -> 3.2.2 upgrade on Duet2 Wifi...:
@geneb this may be one of those odd occasions when downloading the firmware afresh (same version) and reflashing the Duet helps.
Ian
I tried reloading Duet2CombinedFirmware.bin again and while the flash process went without issue, the problem remains.
Fingers crossed that dc42 has some insight.
tnx.
g.
-
Are you sure the endstop stopped working exactly along with the update to RRF3? And you're 100% sure it's not wiring/crimp/switch?
You could go back to 2.05.1 if you have your old config and see if it magically starts working again.
Upload the 2.05.1 zip file to the system tab along with your old config.g
https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/Duet2Firmware-2.05.1.zip
-
@phaedrux said in Weird issue after 2.x -> 3.0 -> 3.2.2 upgrade on Duet2 Wifi...:
Are you sure the endstop stopped working exactly along with the update to RRF3? And you're 100% sure it's not wiring/crimp/switch?
I noticed the issue after the update. I've already stated that the machine had been unused for quite some time prior to the update.
You could go back to 2.05.1 if you have your old config and see if it magically starts working again.
Upload the 2.05.1 zip file to the system tab along with your old config.g
https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/Duet2Firmware-2.05.1.zip
Same issue - X end stop LED remains unlit. No response seen when opening the switch, either vie LED or via M119.
g.
-
@geneb said in Weird issue after 2.x -> 3.0 -> 3.2.2 upgrade on Duet2 Wifi...:
Same issue - X end stop LED remains unlit. No response seen when opening the switch, either vie LED or via M119.
If you disconnect the X endstop and use a jumper wire to connect the two outer pins of the X endstop connector together (taking care not to touch the centre pin), does the LED light?
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 said in Weird issue after 2.x -> 3.0 -> 3.2.2 upgrade on Duet2 Wifi...:
@geneb said in Weird issue after 2.x -> 3.0 -> 3.2.2 upgrade on Duet2 Wifi...:
Same issue - X end stop LED remains unlit. No response seen when opening the switch, either vie LED or via M119.
If you disconnect the X endstop and use a jumper wire to connect the two outer pins of the X endstop connector together (taking care not to touch the centre pin), does the LED light?
No.
-
@geneb said in Weird issue after 2.x -> 3.0 -> 3.2.2 upgrade on Duet2 Wifi...:
@dc42 said in Weird issue after 2.x -> 3.0 -> 3.2.2 upgrade on Duet2 Wifi...:
@geneb said in Weird issue after 2.x -> 3.0 -> 3.2.2 upgrade on Duet2 Wifi...:
Same issue - X end stop LED remains unlit. No response seen when opening the switch, either vie LED or via M119.
If you disconnect the X endstop and use a jumper wire to connect the two outer pins of the X endstop connector together (taking care not to touch the centre pin), does the LED light?
No.
In that case, I suspect that either the endstop LED or its series resistor has gone open circuit, or is not properly soldered to the PCB.
You could try enabling the internal pullup, although this would reduce the noise margin:
M574 X2 S1 P"^xstop" ; configure active-high endstop for high end on X via pin xstopNote the extra ^ character.
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 said in Weird issue after 2.x -> 3.0 -> 3.2.2 upgrade on Duet2 Wifi...:
M574 X2 S1 P"^xstop" ; configure active-high endstop for high end on X via pin xstopNote the extra ^ character.
That's one of the first things I'd tried when trying to work out if I had a configuration error. The behavior didn't change.
Is there a repair service for these, or should I just order a replacement?
tnx.
g.
-
Depends where you are located.
https://forum.duet3d.com/topic/13875/community-repairs?_=1623423266311
If you're not near any of the ones listed there or not in the UK you might be able to find a local electronics repair or cell phone/laptop repair shop.
Or you could use one of the other endstop pins on the expansion header.
-
@phaedrux said in Weird issue after 2.x -> 3.0 -> 3.2.2 upgrade on Duet2 Wifi...:
Depends where you are located.
https://forum.duet3d.com/topic/13875/community-repairs?_=1623423266311
If you're not near any of the ones listed there or not in the UK you might be able to find a local electronics repair or cell phone/laptop repair shop.
So that would be, "no".
Or you could use one of the other endstop pins on the expansion header.
What part of "I don't want a work-around" is unclear? Stuffing a wire into the expansion header cures the symptom and not the problem. It also prevents future use of the expansion header.
I'll just replace the board.
-
@geneb said in Weird issue after 2.x -> 3.0 -> 3.2.2 upgrade on Duet2 Wifi...:
What part of "I don't want a work-around" is unclear?
You're welcome for the helpful suggestion by the way.
