Topics created by Gabriel

@dc42 Thanks for the explanation. I was suggesting that @Gabriel implements this for his peculiar use case. I agree it is not really necessary for most of us.

@Phaedrux So, the P4 can't solve our problem. The Z-axis is still on the PanelDue. Doesn't matter how we use the M584. 😞

We could add "current F parameter" to the object model. Then, when the OM is fully implemented in RRF3, Duet 2 users will be able to retrieve it using M408 P1.

There have been some updates to those commands since that was published. In particular:

rr_upload takes an optional "crc" parameter, which is the CRC-32 of the file in hex format rr_filelist takes an optional "first" parameter, which is the number of the first file required. It also returns a value "next" which is the file number of the first file not returned, or 0 if info for the last file has been returned. So you can make multiple rr_filelist calls, with "first" set to 0 for the first call and subsequently set to the returned "next" value, until "next is 0.

If no requests are received for a period of 8 seconds, thew session will be terminated automatically and a new rr_connect request is needed to start a new one.

@Gabriel said in Z-Probe direction changes:

It works now as expected. Perfect!

Thanks for confirming this

Thanks 3ddevil for your fast reply. I'll try one of your solutions. As long as the voltage is in the range between trigger value 0 and 1000 it shouldn't be dangerous, right?

Thanks a lot in advance.

Perfect, thanks a lot! It works as expected. 🙂