New firmware 3.01-RC2 available
-
Would have another question
Should you invert the pin on M950 or with M581 S1?What happens to the following constellation:
M950 J1 C"!e0stop" M581 P1 T0 S1 C0Board: Duet WiFi 1.03 | Firmware Version: 3.1.1 | WiFi Server Version: 1.23 | Web Interface Version: 3.1.1
-
@dc42 I came across a minor issue in 3.01RC2 (tested on DuetWifi). The gcode line numbers do not reset each time M32 is run, so a gcode file that contains conditional gcode errors will display the incorrect line number if it's not the first one run since reset.
-
@sdavi said in New firmware 3.01-RC2 available:
@dc42 I came across a minor issue in 3.01RC2 (tested on DuetWifi). The gcode line numbers do not reset each time M32 is run, so a gcode file that contains conditional gcode errors will display the incorrect line number if it's not the first one run since reset.
Thanks for reporting that, I'll fix it in RC3.
-
@zerspaner_gerd said in New firmware 3.01-RC2 available:
For me, two sensor inputs are created?
Where does the numbering start?The numbering starts at 0. The OM will report "sensors.inputs" up to the highest one you have configured. So when you create sensor 1, it reports inputs 0 and 1, and it reports that sensor 0 is not configured.
-
@zerspaner_gerd said in New firmware 3.01-RC2 available:
Would have another question
Should you invert the pin on M950 or with M581 S1?You can do either. I left the S0/S1 parameter options so that you can trigger on both the rising and falling edges of an input.
What happens to the following constellation:
M950 J1 C"!e0stop" M581 P1 T0 S1 C0S1 triggers on an inactive-to-active transition, which for an inverted pin is a high-to-low transition.
