Topics created by cjm

@dc42 Thanks for clarifying the M669 reporting of S and T.

There has been some discussion of setting S and T to small values, so that the time delay and distance moved after a pause command can be reduced.

I wondered whether you be able to explain a little more about any trade offs as S and T are reduced ?

@maxgyver it has not

@cncmodeller
I think it’s definitely worth trying and I’d be interested to hear the outcome as it would give a direct measurement of spindle RPM.

However, from what I’ve seen, I believe the Duet fan rpm input expects two pulses per revolution, so perhaps try a two pulse encoder wheel?

A point to check is whether the optical end stop has any electrical filtering, as this might need to be adjusted to avoid limiting the maximum rpm that can be measured.

@kazolar said in VFD integration: M3, M4, M5 Macros and RPM measurement:

@dc42 just found that you added the pin assignments -- will definitely try that out -- any thought to the dwell time option -- the dwell would apply to M3, M4, M5 -- do the task, then wait dwell time to move to next line. Basically combining M# with G4. Also if M6 just runs a macro, that would also be really useful. I added that in my code since I added a tool height probe, so M6 runs a macro to doing an assisted toolchange with a tool height probe.

Yes, adding a dwell time in seconds would be the icing on the cake...

@dc42

As the ConnLCD pins appeared to be straightforward 3.3V logic level signals direct from the processor, I'd hoped they could be redefined in RRF3.

Anyhow, thanks for the replies which fully address my question.

@cjm said in Aux Comms Issue:

So, it looks as though via the Aux channel, the Maestro is only responding to commands that request a JSON format response.

That's correct. Responses to other commands are saved until you ask for them using M408.