Strange, OctoPi would not auto connect either, Prusa MK2S 3.0.14 firmware. Manually connected at a lower baud rate, but how do I do that in AstroPrint?
It just does not see the printer.
Nick
You can change that in your settings. But that is not working @ the moment. The devs are busy with something else. My two prusa mk2s is not working.
@Mike_Nanninga This is a problem that’s being addressed just to be clear. Something in the Prusa changed perhaps their new board or firmware. It is the ONLY printer currently showing this problem. The problem is that the serial port does not advertise itself as a “standard serial”. I’m going to guess that at the end the problem is on the prusa firmware or board BTW.
Nonetheless, we’re working on it. The printer works just fine once you manually set the port, which is BTW why it works in Octoprint because, Octo, shows you ALL ports not only the ones that could have a printer connected.
Our software has always tried to be more friendly so we would only show you ports that are detected to have a printer connected to it, instead of showing you all and let you figure out which one your printer is connected to. In the new Mk2, the rug has been pulled from under our feet, and the port is not behaving properly so it’s not shown at all.
I’m going to put here the temporary solution to get your MK2s working until we ( or prusa ) can figure out how to make the port show up.
-
SSH into your AstroBox OR connect an HDMI monitor and USB keyboard to the box (restart is necessary after connection)
-
Stop the AstroBox service by typing this in the command line
sudo service astrobox stop
- Edit the
/etc/astrobox/config.yamlfile and add the following block (note that the “serial” block might already be there in your config, if so, simply add what’s missing). Use proper indentation, 2 spaces per indent (not tab)
serial:
baudrate: 115200
port: /dev/ttyACM0
timeout:
connection: 25
- Start the AstroBox service again
sudo service astrobox start
The printer should now connect (don’t use the connection settings screen, simply use the printer icon in the top right portion of the screen. If the service doesn’t start, it’s likely that you incorrectly typed some property or didn’t use the correct indentation.
It will show connected but doesn’t stay connect. Print jobs still fail with disconnection and the Pi locking up. Same results with firmware v0.10(9)
Could you enable serial logs and sent to us via advanced settings?
Did this ever get fixed? I could never get mine to work either, so I’ve been using octoprint.
-Brad
Serial logs enabled and sent via the UI. I can ssh and pull it as well if needed. OctoPrint by the way works just fine same machine and cables.
I fixed mine by hard coding the serial port and baud rate in the config.
But I am seeing some feature lacking between Astro and Repetier Server, which runs both my Prusa and my MPCNC on the same Pi at the same time.
I’m sure CNC systems are out of scope for AstroPrint though.
Some interesting errors in the log I don’t get with OctoPrint same setup.
2017-09-12 21:52:44,366 - SERIAL - DEBUG - Send: N10 M10522
2017-09-12 21:52:44,378 - SERIAL - DEBUG - Recv: ok T:216.0 /215.0 B:60.3 /60.0 T0:216.0 /215.0 @:38 B@:0
2017-09-12 21:52:44,380 - SERIAL - DEBUG - Send: N11 G28 W84
2017-09-12 21:53:09,406 - SERIAL - DEBUG - Read communication timeout during printing, listen again
2017-09-12 21:53:09,580 - SERIAL - DEBUG - Recv: ok
2017-09-12 21:53:09,582 - SERIAL - DEBUG - Send: N12 M10520
2017-09-12 21:53:09,609 - SERIAL - DEBUG - Recv: ok T:214.0 /215.0 B:60.6 /60.0 T0:214.0 /215.0 @:90 B@:0
2017-09-12 21:53:09,611 - SERIAL - DEBUG - Send: N13 G8035
2017-09-12 21:53:30,495 - SERIAL - DEBUG - Recv: clean up finished
2017-09-12 21:53:30,555 - SERIAL - DEBUG - Recv: babystep applied
2017-09-12 21:53:30,560 - SERIAL - DEBUG - Recv: Bed leveling correction finished
2017-09-12 21:53:30,569 - SERIAL - DEBUG - Recv: Upsample finished
2017-09-12 21:53:30,572 - SERIAL - DEBUG - Recv: Mesh bed leveling activated
2017-09-12 21:53:36,977 - SERIAL - DEBUG - Recv: Go home finished
2017-09-12 21:53:36,979 - SERIAL - DEBUG - Recv: ok
2017-09-12 21:53:36,980 - SERIAL - DEBUG - Send: N14 M104 S215.000000120
2017-09-12 21:53:36,989 - SERIAL - DEBUG - Recv: ok
2017-09-12 21:53:36,990 - SERIAL - DEBUG - Send: N15 M10519
Later on that print
2017-09-12 22:08:31,807 - SERIAL - DEBUG - Unexpected error while reading serial port: SerialException: ‘device reports readiness to read but returned no data (device disconnected or multiple access on port?)’ @ comm.py:_readline:1126
2017-09-12 22:08:31,810 - SERIAL - DEBUG - Changing monitoring state from ‘Printing’ to 'Error: SerialException: ‘device reports readiness to read…’
2017-09-12 22:08:34,464 - SERIAL - DEBUG - Connection closed, closing down monitor
Printing stops