Problems when trying to use the Mini+ over a socat connection
I do encounter problems when trying to use the Mini over a socat connection in order to use a containerized version of Octoprint. When I set the whole thing up it worked perfectly for a while. Then this particular setup stopped working (without changing anything). I was able to print several objects with this setup.
I could fix it once by replugging the wires from the Raspberry Pi 4 (running Raspberry Pi OS Bullseye) but then it stopped working again.
Another hint I found on the web was unloading the cdc_acm kernel module and reloading it (modprobe -r cdc_acm followed by modprobe cdc_acm). This also worked only once.
Any ideas why this is happening? Or even better how to fix that?
socat on the printer's host (RPi 4, RPi OS Bullseye) looks like:
/usr/bin/socat -d -d -d TCP4-LISTEN:4000,fork,reuseaddr /dev/ttyACM0,raw,echo=1,b115200
In the container I also tried socat and even the OctoPrint-Network-Printing plugin.
RE:
Can you provide more details about container runtime and image used (dockerfile)?
Also some things to try:
- try mounting and accessing device directly in the container, it is doable
- would auto restart using docker HEALTHCHECK help in that case?
- usually things work better if underlying distro is the same as host (I wasted too much of my life at work fighting issues due to alpine Linux...)
- really try to upgrade to the latest packages/kernel people forget about it, especially in containers
- sometimes just running with --network=host is enough
See my GitHub and printables.com for some 3d stuff that you may like.