Topics created by LindsayC

@LindsayC the reason is that the P parameter of M569 expects a driver ID, which looks like a float but is different. To make it easier to generate the P parameter in a macro, in recent versions of RRF we allow a float with a fractional part that is very close to a multiple of 0.1 to be converted to a driver ID. We can't say that it has to be exactly a multiple of 0.1 because 0.1 cannot be represented exactly as a binary float.

Expressions of any type can be converted to string.

@LindsayC Just an update on what I've ended up doing. As we wanted to use the ethernet connection as our main comms, we've implemented the DuetHTTPclient and telnet connection together.

The DuetHTTPclient has the full object model updating in the background that can be queried regularly with less time-critical stuff like reporting in the UI things like temperatures of chambers etc.

The telnet allows more time-critical comms without the overhead of the DuetHTTPClient like needing to wait for update of the object model.

Single cable solution with a lot of flexibility.

@T3P3Tony It's is sort of round about, but it works reliably.