Topics created by Anthoval

@anthoval it looks like the model you have is a PNP sensor:
017a0361-e34f-47ce-9e35-81aa0d7271e4-image.png

The documentation suggests using a resistive voltage divider to connect a PNP sensor:
https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_PNP_output_normally_open_inductive_or_capacitive_sensor

For Duet 3 and 3 Mini: all IOx.in inputs have a 27K pullup resistor to +3.3V, therefore the value of R2 must be low enough to defeat this. We suggest R2 = 2.2K. Then the value of R1 should be 4.7K to 6.8K if the sensor is powered from +12V; or use 10K to 15K if the sensor is powered from +24V.

100mA is far more current than can be sourced/sunk from the IOn.IN pins so that is not the issue.

@chrishamm, I had lost track of those! Still missing rr_model though.

You can reach the web control from your phone browser.

Otherwise may you'd find this interesting?

https://forum.duet3d.com/topic/19673/native-app-for-duet3d-rrf-wishlist/44

I thought the P parameter for G1 commands was documented, but it seems not to be. I have just [re-]added it.

After running multiples tests at a reasonnable speed (Feedrate : 15000 mm/min), I can tell that the motion is continuous between multiple G0/G1 commands!

By the way, I don't understand how the "T" parameter from the M670 works (when using the "P" parameter in a G1 command). I thought at first that is was the delay between the beginning of the movement and the beginning of the output being set to '1'. But when testing with multiple values for "T", the output was always set to '1' immediatly after the beginning of the G1 command.

Edit : The "T" parameter appears to be important when using the P1 parameter with a G1 command on a very short distance. Reduce the "T" value if you're looking to trigger an output to '1' on a short distance and high speed (30 mm and 15000 mm/min).