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

The sensor is powered by the Vin of the Duet.
The signal from the sensor is wired to io2.in.
I configured the sensor as a NPN by wiring it the the IO_2 ground pin.

To sum up:
2 wires for the power - POWER IN Vin & GND
1 signal wire - io2.in
1 config wire - IO_2 GND

@fcwilt in my case, the config wire is connected to +24V : When the laser does not see an object the output is 24V, else it is 0V.

@fcwilt Sorry for my late response.

When the probe is activated, the voltage is 24V. When it is not, the voltage is 0V.
The datasheet shows that the sensor generates a current <= 100 mA, which might not be enough for the Duet to read.

I have designed a small PCB and used a relay in order to use the sensor as intended.

I don't know yet how I am going to mount it, the best option would be to 3d print something.

The sensor is powered by the Vin of the Duet.
The signal from the sensor is wired to io2.in.
I configured the sensor as a NPN by wiring it the the IO_2 ground pin.

To sum up:
2 wires for the power - POWER IN Vin & GND
1 signal wire - io2.in
1 config wire - IO_2 GND

Hi, I've been trying to install this sensor as an endstop (link at the end) on the OI_2 port configured as an input (M574 Y1 S1 P"!io2.in").

Even though I have the correct voltage on the input pin, the Duet 3 6HC always read the input as "no".

Any idea why?

Thanks.

Link to sensor : reference 729-5107 on https://fr.rs-online.com/

Great, thanks for your advices. My goal here is to remote control the Duet without using any browser, I'll reply here to give a feedback on how things went!

Okay good to know. I've been thinking about something. Would it be possible to send ethernet frames to the Duet and expect it to react as if you used DWC? So basically, trigger macros on the Duet without using DWC.

Hi,

I would like to know if there was any way to control the Duet 3 (ethernet) with my phone.

Even though it is an ethernet Duet, is it possible to use a "Wifi/Ethernet adaptor"?

Hi,

I wanted to know if it was already planned to create an app so people could control the Duet 3 with a smartphone ? Or maybe it has already been done?

@deckingman the "P" parameter is used to trigger an output for the whole movement.

The pause might be a "G4 P0" (wait the end of previous movement). When multiples movements are used in a row, there's no stop between every move. The acceleration occurs on the first G1 command, the deceleration only occurs on the last.

I feel like this pause is specific to the while loop, when iteration goes from 0 to 1. Though I have not tried to start the loop at iteration = 1, instead of 0 (if that's possible).

Hi,

I've noticed something strange when using a while loop. After the first iteration, there's is a small waiting time. Is it normal ? Here's the code I used :

while iterations < 4
G1 X150 F10000 P0