Compatibility issue between Astroprint and MK2S  

Compatibility issue between Astroprint and MK2S

I am trying to connect my Prusa i3 MK2S (original) to Astroprint on a Raspberry Pi 2 Model B v1.1. Unfortunately, when the printer is plugged in via USB it is not detected.

To be clear, the same Raspberry Pi, USB cable, SD Card and printer work just fine with Octoprint.

My Astrobox version is v0.10(8) (b306e2c1bc1fc035c90933ef6476250641b9c60d).

To try to solve this I took the following steps by SSH:

Find out which USB port the printer is connected to

$ dmesg | grep Prusa
[ 2.438262] usb 1-1.5: Product: Original Prusa i3 MK2
[ 2.446526] usb 1-1.5: Manufacturer: Prusa Research (prusa3d.com)

Get the tty port name

$ dmesg | grep 1-1.5
[ 2.260595] usb 1-1.5: new full-speed USB device number 4 using dwc_otg
[ 2.417475] usb 1-1.5: New USB device found, idVendor=2c99, idProduct=0001
[ 2.427700] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2.438262] usb 1-1.5: Product: Original Prusa i3 MK2
[ 2.446526] usb 1-1.5: Manufacturer: Prusa Research (prusa3d.com)
[ 2.455808] usb 1-1.5: SerialNumber: CZPX3017X003XK29042
[ 4.825279] cdc_acm 1-1.5:1.0: ttyACM0: USB ACM device

Add the following to /etc/astrobox/config.yaml

serial:
baudrate: 115200
log: true
port: /dev/ttyACM0
timeout:
connection: 25

Restart Astrobox

$ sudo service astrobox restart

Check serial log

cat serial.log
2017-08-11 21:26:56,363 - SERIAL - DEBUG - Enabling serial logging
2017-08-11 21:26:56,520 - SERIAL - DEBUG - Changing monitoring state from 'Offline' to 'Opening serial port'
2017-08-11 21:26:56,533 - SERIAL - DEBUG - Connecting to: /dev/ttyACM0
2017-08-11 21:26:56,543 - SERIAL - DEBUG - Connected to: Serial<id=0x73889f70, open=True>(port='/dev/ttyACM0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=25.0, xonxoff=True, rtscts=False, dsrdtr=False), starting monitor
2017-08-11 21:26:56,547 - SERIAL - DEBUG - Changing monitoring state from 'Opening serial port' to 'Connecting'
2017-08-11 21:26:56,550 - SERIAL - DEBUG - Send: M105
2017-08-11 21:26:57,464 - SERIAL - DEBUG - Recv: start
2017-08-11 21:26:57,474 - SERIAL - DEBUG - Recv: echo:echo: Last Updated: Jul 11 2017 16:36:40 | Author: (none, default config)
2017-08-11 21:26:57,486 - SERIAL - DEBUG - Recv: Compiled: Jul 11 2017
2017-08-11 21:26:57,492 - SERIAL - DEBUG - Recv: echo: Free Memory: 2370 PlannerBufferBytes: 1280
2017-08-11 21:26:57,497 - SERIAL - DEBUG - Recv: echo:Hardcoded Default Settings Loaded
2017-08-11 21:26:58,875 - SERIAL - DEBUG - Recv: echo:SD card ok
2017-08-11 21:26:58,876 - SERIAL - DEBUG - Changing monitoring state from 'Connecting' to 'Operational'
2017-08-11 21:27:23,903 - SERIAL - DEBUG - Send: M105
2017-08-11 21:27:23,917 - SERIAL - DEBUG - Recv: ok T:31.4 /0.0 B:30.0 /0.0 T0:31.4 /0.0 @:0 B@:0
2017-08-11 21:27:49,274 - SERIAL - DEBUG - Send: M105
2017-08-11 21:27:49,288 - SERIAL - DEBUG - Recv: ok T:31.4 /0.0 B:30.0 /0.0 T0:31.4 /0.0 @:0 B@:0

So the printer appears to be connected but if I go to http://astrobox.local/#settings/printer-connection in the web UI I am presented with the following:

I guess it is connected but it seems like something should be done to make the Astroprint more compatible with the printer.

Also, strangely, if I restart Astrobox the printer does not connect (no error in serial.log but I get the following in my browser's console "device reports readiness to read but returned no data (device disconnected?)")... it does connect when I run:

$ sudo service astrobox restart

I have also posted this at https://forum.astroprint.com/t/web-ui-not-showing-connection-to-prusa-i3-mk2s/2398 just in case both posts together help others and maybe even get the Astroprint bug fixed.