Web UI not showing connection to Prusa i3 MK2S

AstroBox Troubleshooting
#1

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:

Printer connected or not connected.png950×276 22.4 KB

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 http://shop.prusa3d.com/forum/original-prusa-i3-mk2-f23/compatibility-issue-between-astroprint-and-mk2s-t5500.html just in case both posts together help others and maybe even get the Astroprint bug fixed.

#2

I am experiencing identical problem. AstroPrint won’t connect to an Original Prusa i3 MK2. After I followed your guide system keeps blinking in the top right corner “Connecting to the printer”. Any suggestions?

#3

I would suggest using Octoprint instead. At the moment it is only affecting people with the newest Prusas (MK2S) and the devs don’t seem to care.

Over the next few months as tens of thousands of people buy new Prusas it will be sure to get their attention.

#4

Thank you Mike for the response and suggestions.
I am getting used to the OctoPi but at the beginning difference between two interfaces is what attracted me. Plus an opportunity of having access to cloud slicer. Maybe I have very high and ambitious expectations but with cloud based slicer people could have shared database of (printers, configs, materials and etc.) there could be added a kind of ranking system continuously improving the project and user experience.

#5

@Mike_Ratcliffe: It’s easy to blurt out “Oh Noez! The Devs Don’t Care!” whenever a specific issue is not resolved.

But, I assure you that the Devs DO CARE.

What you have to understand is that we are a small team with limited resources.

This means that, we have to be VERY diligent about how we allocate those resources.

At the moment, most of our energy is focused on ironing out bugs in our beta software (Astroprint Desktop & Mobile) and delivering product(s) to our recent 600+ Kickstarter backers.

If using another solution helps you 3D Print without any issues, please feel free to try it out :wink:

We are planning on fixing these things, but the reality is that, I don’t have a specific ETA.

@Dmitri_Passaita: Apologies! I hope you can be a bit more patient. Also, feel free to browse some of the issues we are working on, and even submit an issue (via Github) so our devs are guaranteed to see it.

Thanks buddy! :innocent:

#6

Hi Dilanka,

Being directly involved in software development I completely understand both points of view.
You need to prioritise limited human / intellectual resources but users may see no progress during the process and it frustrates them /us.
I have already chatted with Daniel and offered my help in testing when at some point there will be something to test.
There is a commitment made through Kickstarter and it’s fair to put the rest aside but I would also second Mike on urgency to re-obtain Prusa compatibility due to the volumes of these printers being sold worldwide. Once Astro is compatible you can be sure people will buy Astro box to eliminate the hassle of installation and dealing with unreliable SD card in the Raspberry PI.
You can be sure you will see a number of tickets from me once I start using Astro and as I already mentioned I have a lot of ideas you and your team will get tired to implement :slight_smile:
Take care, focus on those things that you really need to and don’t take our complains personal. This is our way to attract your attention.

1 Like
#7

It doesnt matter whats so ever. Is there is a printer not working. And alot of users here and on kickstarter have a prusa mk2s. And also 3 weeks and still no quick fix. I stay by my statement. I have 2 printers and 4 other printers i pay for this and 2 of my printers dont work. Whats the point to pay!!! if your treated like a non paying customer

#8

@Mike_Ratcliffe / @Dmitri_Passaita / @Mike_Nanninga:

Just FYI, did you all see Daniel’s reply on this post?

Perhaps that should help you all.

If not, we are working on an update for the next release.

Sit tight :wink:

#9

Sweet. I just got an MK2S and I am having the same problems. Looking forward to a fix!

#10

I am sorry, I shouldn’t have said that you don’t care. I work full time in the open source world myself so I totally get it and I completely understand that you need to prioritize your work.

I am a bit embarrassed that I said that to be honest because I know it is not true… I suppose I was just frustrated with the issue.

So again, sorry, I didn’t mean it.

#11

No worries @Mike_Ratcliffe :slight_smile:

Frustration can cause misunderstandings.

@Daniel is working hard on this – trust me.

Stay tuned!

#12

I was a developer and a sysadmin for years (now wanting to just be an user in my retired state). IMHO, lack of communications, regular communications, of the current state, good or bad, causes more user frustration than even ‘the dog ate my listing’ excuse, but for open software, ‘I had to attend a little league game for my kid’ type of thing, goes a long way. Folks that have done even small development projects will understand.

And yes, I have a MK2S and want Astroprint to work with it. So please keep us informed!

BTW, what is the latest update or ETA to get a version that works? - Yes, I ordered a kickstarter box too, and really hope it works. The Astroprint box I am doing now will be relegated to another machine.

#13

@Jack1, I believe to have found the fix for this: https://github.com/AstroPrint/AstroBox/commit/74a79cf88cf6649f681ae61ec774297908b27b92

This will go out in the upcoming 0.10(10) maintenance release which should be out next week.

1 Like
Printer freezes up after starting print