Hi,
I have just looked into this... thank you for posting about ethernet support!
Some findings from me:
- At least with the latest firmware, it seems like the UI firmware file is the only one that is needed (edit: I forgot that this is also in the READ ME file, but I wanted to point that out anyway)
- The settings gcode file is also not necessary... it doesn't seem to change anything network related
- To get ChiTuBox to use network support, the only relevant setting in the profile is "machineType". It must be changed from "ELEGOO MARS" to "default".
You can export an existing/default ELEGOO MARS Profile, change that value and import it again after adding a new "default" printer.
It looks like ChitTuBox simply communicates with the printer by G codes over UDP.
And it searches the printer by sending a broadcast to UDP port 3000 with the G code M99999.
For example with Linux, you can do the same this way:
(of course, you have to change the broadcast address so it matches your network)
And you can get the print status from the known printer IP via:
(broadcast like above also works...)
I have also found this with more G codes (that's where I got M27 from):
https://github.com/Photonsters/anycubic-...via-serial
I have just looked into this... thank you for posting about ethernet support!
Some findings from me:
- At least with the latest firmware, it seems like the UI firmware file is the only one that is needed (edit: I forgot that this is also in the READ ME file, but I wanted to point that out anyway)
- The settings gcode file is also not necessary... it doesn't seem to change anything network related
- To get ChiTuBox to use network support, the only relevant setting in the profile is "machineType". It must be changed from "ELEGOO MARS" to "default".
You can export an existing/default ELEGOO MARS Profile, change that value and import it again after adding a new "default" printer.
(08-12-2019, 12:21 AM)davipet Wrote: Is there any known api to check printers status, progress, error etc. via Network?
It looks like ChitTuBox simply communicates with the printer by G codes over UDP.
And it searches the printer by sending a broadcast to UDP port 3000 with the G code M99999.
For example with Linux, you can do the same this way:
Code:
echo -n M99999 | socat - UDP4-DATAGRAM:192.168.1.255:3000,so-broadcast
And you can get the print status from the known printer IP via:
Code:
echo -n M27 | nc -w 1 -u 192.168.1.123 3000
I have also found this with more G codes (that's where I got M27 from):
https://github.com/Photonsters/anycubic-...via-serial