Connection Problems from Astrobox to Prusa i3 MK3

AstroBox Troubleshooting
#13

Do you have the latest firmware on the printer?

#14

No, I have skipped the last update from Prusa. The problem appears only on the last version?

#15

This is our current assumption.

#16

Will check it today after work

#17

So, i updated my Prusa yesterday to 3.5.1-1778 version and my connection between Raspberry Pi zero W is still working fine.
I am running astrobox 0.14(0)

1 Like
#18

Ok. Just like for us here. I wonder if those having problems have some mods or perhaps SD Cards inserted with a lot of files (which can make boot up slow)

#19

Also Prusa had 2 versions of Einsy board, I have the newest one. Maybe the problem appears on the older boards?

#20

Is there a way to visually see which board we have?

#21

Previous one doesn’t have flash memory and you had to attach additional board.
At Prusa assembly page you can see images of both:
https://manual.prusa3d.com/Guide/8.+Electronics+assembly+(B3-R2+design)/513?lang=en

#22

witch Board do you have : Version A oder B?

#23

I have:
Version A: LCD connectors are used directly on the EINSY RAMBo board.

#24

ok, thank you. Tonight, I’m gonna check out which board I have.

#25

i also have the version A.
unfortunately the problem with the connection to the printer persists.

astrobox-mk3%20-%20AstroBox%202019-01-24%2021-19-07
astrobox-mk3 - AstroBox 2019-01-24 21-19-07.png1302×862 64 KB

#26

I don’t understand where the problem is.

#27

@daniel: I send the logfiles to you

#28

@Brainson. I see this in the logs:

2019-01-24 20:22:53,986 - astroprint.printer.marlin.comm - INFO - Changing printer state from [Offline] to [Connecting]
2019-01-24 20:22:53,987 - astroprint.printer - INFO - Connected to serial port [/dev/ttyACM0] with baudrate [115200]
2019-01-24 20:23:39,138 - astroprint.printer.marlin.comm - INFO - Changing printer state from [Closed] to [Closed with Error: TypeError: 'an integer is required' @ comm.py:_rea...]
2019-01-24 20:23:39,142 - astroprint.printer.marlin.comm - INFO - Changing printer state from [Connecting] to [Closed]

Unfortunately it’s not enough information to know what’s happening. If you enable serial logs, we will get more info. In the same screen where you sent me logs you can do the following:

  1. Clear logs
  2. Enable Serial Logs
  3. Try connecting a couple of times to log the sequence.
  4. Send logs to us again

Thanks for your help.

#29

Okay thank you, I’ll do that tonight… hear you :wink:

1 Like
#30

logs are on their way…

#31

Got the logs. The printer is not responding at all. We send our probe M105 commands and nothing comes back, eventually we give up.

Are you able to connect to this printer with any other host software?

#32

octoprint works well