Problem:" $Files/ListGcode error" codes in response UART 1 & 2 about fluidnc HOT 2 CLOSED

FluidNC is working as intended. Responses are identified by a "routing tag" like "MSG:JSON" or "MSG:ERR" or one of various other prefixes that should be used to direct the information to a specialist handler for that type of message. It is incorrect to expect that the response to $Files/ListJSON will contain only JSON messages. In order to restrict the response thusly, threads would need to blocked in a way that could cause timing or deadlock problems. The reason it appears to work with the old [FILE: response is because those responses do not participate properly in the flow control for outgoing messages; the thread that generates them just sends without regard to whether the receiver can keep up with the message rate. That often works, but is fundamentally unreliable at the edge cases.

The response to $File/ListJSON should be considered a work in progress. I am considering making some tweaks to make things more efficient for I/O expanders. People who write their own pendants should be prepared to revise their code until things settle down.

from fluidnc.

I'll have to have another look at the structure, I'm probably using a too simplistic method
Thanks

from fluidnc.