Endstops not working after FW upgrade to 3.01-RC4
-
I updated from RC3 to RC4 and then I get this error in the picture.
M119
Endstops - X: no endstop, Y: no endstop, Z: no endstop, Z probe: not stoppedOptical endstops set active high
; Endstops
M574 X1 Y1 S1 ; Set active high endstops
-
Solved
M574 X1 S1 P"xstop" ; X min active high endstop switch
M574 Y1 S1 P"ystop" ; Y min active high endstop switch
-
Now suddenly my layerfan does not work....
-
please post your config.g file
-
I sorted it out after reading a lot of Gcode
There are so many changes from RRF2 to RRF3-RC4 so the config.g file was no longer usable
- I thought upgrading FW took care of all this stuff
-
@pro3d Are you sure you were on 3.01-RC3 before? Maybe it was one of the 3.0 betas or 3.0 RC2? Because the change that would cause this was introduced with 3.01 beta1, and that was:
If upgrading a Duet WiFi/Ethernet/Maestro from the 3.0 release, note that default fans are no longer created. Unless your config.g file already used M950 to create the fans explicitly, add commands M950 F0 C"fan0", M950 F1 C"fan1" and M950 F2 C"fan2" to config.g before your M106 commands. Likewise, default endstop switches are not set up, so you will need to set up X and Y endstops (and Z if needed) explicitly, using one M574 line for each, and specifying the port name. Example: M574 X1 S1 P"xstop".
https://github.com/dc42/RepRapFirmware/blob/v3-dev/WHATS_NEW_RRF3.md#reprapfirmware-301beta1
Always a good idea to read the update notes, particularly on new, rapidly developing firmware! This decision was taken as a result of this thread: https://forum.duet3d.com/topic/13720/sequence-definition-fan-pins
The RRF config tool has been updated to generate all pin assignments, so you could always use that: https://configtool.reprapfirmware.org/
Also, this page explains the differences between RRF 2 and 3: https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview
Ian
-
@pro3d said in Endstops not working after FW upgrade to 3.01-RC4:
I thought upgrading FW took care of all this stuff
Never.
Upgrading firmware never changes your config.g. If the newer firmware needs something different, you must make that update yourself.
-
@pro3d said in Endstops not working after FW upgrade to 3.01-RC4:
I updated from RC3 to RC4
@pro3d said in Endstops not working after FW upgrade to 3.01-RC4:
from RRF2 to RRF3-RC4
Not sure which you meant to say, or what actually happened... but if you were truly move from 2.anything to 3.anything, that does indeed require quite a bit of change to config.g.
-
I am sure I was on RRF 3-RC3 stable so it was very weird. I did now do the config tool to get all the latest parameters and everything should be good - except temp issue somehow out of order. I made a new fan shroud and will do more testing
Thanks for the follow up
-
I now just wonder how to probe bl touch multiple times as before?
OLD CODE
; M558 P9 C"zprobe.in" H5 F120 T6000 A30 S0.02 ; Set Z probe type to bltouch and the dive height + speedsNEW CODE:
M558 P9 C"zprobe.in+zprobe.mod" H5 F120 T18000 ; set Z probe type to bltouch and the dive height + speeds
-
@pro3d said in Endstops not working after FW upgrade to 3.01-RC4:
A30 S0.02
Add this from your old code to your new code.
-
@pro3d said in Endstops not working after FW upgrade to 3.01-RC4:
I am sure I was on RRF 3-RC3 stable so it was very weird. I did now do the config tool to get all the latest parameters and everything should be good - except temp issue somehow out of order. I made a new fan shroud and will do more testing
RRF 3.0 created some default endstops and fans, to try to smooth the upgrade path from RRF2. But that caused issue for some users. So as described in the upgrade notes for 3.01beta1, in RRF 3.01 no default devices are created:
If upgrading a Duet WiFi/Ethernet/Maestro from the 3.0 release, note that default fans are no longer created. Unless your config.g file already used M950 to create the fans explicitly, add commands M950 F0 C"fan0", M950 F1 C"fan1" and M950 F2 C"fan2" to config.g before your M106 commands. Likewise, default endstop switches are not set up, so you will need to set up X and Y endstops (and Z if needed) explicitly, using one M574 line for each, and specifying the port name. Example: M574 X1 S1 P"xstop".
