Octo4A setup not quite working

What is the problem?

I have an Ender 3 Pro and picked up a Kindle Fire HD 8 to run Octo4a on to run Octoprint on my printer. However, when I connect, I get the following error:

image

What did you already try to solve it?

I've tried safe mode and restarting all devices.

Have you tried running in safe mode?

Yes

Did running in safe mode solve the problem?

No

Systeminfo Bundle

You can download this in OctoPrint's System Information dialog ... no bundle, no support!)

WRITE HERE

Additional information about your setup

OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible

Here are the logs from the most recent restart of everything:

Changing monitoring state from "Offline" to "Detecting serial connection"
Performing autodetection with 7 port/baudrate candidates: /dev/ttyOcto4a@115200, /dev/ttyOcto4a@250000, /dev/ttyOcto4a@230400, /dev/ttyOcto4a@57600, /dev/ttyOcto4a@38400, /dev/ttyOcto4a@19200, /dev/ttyOcto4a@9600
Trying port /dev/ttyOcto4a, baudrate 115200
Connecting to port /dev/ttyOcto4a, baudrate 115200
Handshake attempt #1 with timeout 2.0s
Connected to: Serial<id=0xf05a9568, open=True>(port='/dev/ttyOcto4a', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=2.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
Send: N0 M110 N0*125
Handshake attempt #2 with timeout 2.0s
Send: N0 M110 N0*125
Handshake attempt #3 with timeout 2.0s
Send: N0 M110 N0*125
Trying port /dev/ttyOcto4a, baudrate 250000
Handshake attempt #1 with timeout 2.0s
Send: N0 M110 N0*125
Handshake attempt #2 with timeout 2.0s
Send: N0 M110 N0*125
Handshake attempt #3 with timeout 2.0s
Send: N0 M110 N0*125
Trying port /dev/ttyOcto4a, baudrate 230400
Handshake attempt #1 with timeout 2.0s
Send: N0 M110 N0*125
Handshake attempt #2 with timeout 2.0s
Send: N0 M110 N0*125
Handshake attempt #3 with timeout 2.0s
Send: N0 M110 N0*125
Trying port /dev/ttyOcto4a, baudrate 57600
Handshake attempt #1 with timeout 2.0s
Send: N0 M110 N0*125
Handshake attempt #2 with timeout 2.0s
Send: N0 M110 N0*125
Handshake attempt #3 with timeout 2.0s
Send: N0 M110 N0*125
Trying port /dev/ttyOcto4a, baudrate 38400
Handshake attempt #1 with timeout 2.0s
Send: N0 M110 N0*125
Handshake attempt #2 with timeout 2.0s
Send: N0 M110 N0*125
Handshake attempt #3 with timeout 2.0s
Send: N0 M110 N0*125
Trying port /dev/ttyOcto4a, baudrate 19200
Handshake attempt #1 with timeout 2.0s
Send: N0 M110 N0*125
Handshake attempt #2 with timeout 2.0s
Send: N0 M110 N0*125
Handshake attempt #3 with timeout 2.0s
Send: N0 M110 N0*125
Trying port /dev/ttyOcto4a, baudrate 9600
Handshake attempt #1 with timeout 2.0s
Send: N0 M110 N0*125
Handshake attempt #2 with timeout 2.0s
Send: N0 M110 N0*125
Handshake attempt #3 with timeout 2.0s
Send: N0 M110 N0*125
Changing monitoring state from "Detecting serial connection" to "Error"
Changing monitoring state from "Error" to "Offline after error"
Connection closed, closing down monitor
Changing monitoring state from "Offline" to "Detecting serial connection"
Performing autodetection with 7 port/baudrate candidates: /dev/ttyOcto4a@115200, /dev/ttyOcto4a@250000, /dev/ttyOcto4a@230400, /dev/ttyOcto4a@57600, /dev/ttyOcto4a@38400, /dev/ttyOcto4a@19200, /dev/ttyOcto4a@9600
Trying port /dev/ttyOcto4a, baudrate 115200
Connecting to port /dev/ttyOcto4a, baudrate 115200
Handshake attempt #1 with timeout 2.0s
Connected to: Serial<id=0xf0a5f148, open=True>(port='/dev/ttyOcto4a', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=2.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
Send: N0 M110 N0*125
Handshake attempt #2 with timeout 2.0s
Send: N0 M110 N0*125
Handshake attempt #3 with timeout 2.0s
Send: N0 M110 N0*125
Trying port /dev/ttyOcto4a, baudrate 250000
Handshake attempt #1 with timeout 2.0s
Send: N0 M110 N0*125
Handshake attempt #2 with timeout 2.0s
Send: N0 M110 N0*125
Handshake attempt #3 with timeout 2.0s
Send: N0 M110 N0*125
Trying port /dev/ttyOcto4a, baudrate 230400
Handshake attempt #1 with timeout 2.0s
Send: N0 M110 N0*125
Handshake attempt #2 with timeout 2.0s
Send: N0 M110 N0*125
Handshake attempt #3 with timeout 2.0s
Send: N0 M110 N0*125
Trying port /dev/ttyOcto4a, baudrate 57600
Handshake attempt #1 with timeout 2.0s
Send: N0 M110 N0*125
Handshake attempt #2 with timeout 2.0s
Send: N0 M110 N0*125
Handshake attempt #3 with timeout 2.0s
Send: N0 M110 N0*125
Trying port /dev/ttyOcto4a, baudrate 38400
Handshake attempt #1 with timeout 2.0s
Send: N0 M110 N0*125
Handshake attempt #2 with timeout 2.0s
Send: N0 M110 N0*125
Handshake attempt #3 with timeout 2.0s
Send: N0 M110 N0*125
Trying port /dev/ttyOcto4a, baudrate 19200
Handshake attempt #1 with timeout 2.0s
Send: N0 M110 N0*125
Handshake attempt #2 with timeout 2.0s
Send: N0 M110 N0*125
Handshake attempt #3 with timeout 2.0s
Send: N0 M110 N0*125
Trying port /dev/ttyOcto4a, baudrate 9600
Handshake attempt #1 with timeout 2.0s
Send: N0 M110 N0*125
Handshake attempt #2 with timeout 2.0s
Send: N0 M110 N0*125
Handshake attempt #3 with timeout 2.0s
Send: N0 M110 N0*125
Changing monitoring state from "Detecting serial connection" to "Error"
Changing monitoring state from "Error" to "Offline after error"
Connection closed, closing down monitor

I never used Octo4A so I can't really help you with a specific issue but here are some general tips:

  • Make sure that the usb cable is a data cable. Test if you can connect your printer to your pc to rule out a bad cable. You can test it for example with Pronterface.

  • Either turn the printer on before connecting it to the tablet or use the 5V pin mod to prevent the usb port from being overloaded.

I have a print running now but I'll try the first point tomorrow.

I did the electrical tape bit earlier tonight. But very good idea.

This sounds like you may not be using the correct serial driver in Octo4a. Do you have a screenshot of the Octo4a app? You should see your printer listed with a checkmark next to it.

I think that looks correct.

I grabbed Pronterface, but am not getting anything past "Connecting..." - I'll try another cable after bit.

Looks like Octo4a can at least see the printer. The volume slider on the right is blocking the checkbox, so I can't tell if that's actually the correct driver, though. Try cycling between the different available drivers and see if any of them work.

Sorry about that, there is a check box and it is checked. Tapping on the check just leaves it checked.

How does one cycle through the drivers? I'm not sure that's clicking with me.

Tried a different cable, still only seeing "Connecting..." in Pronterface.

Tap on the "USB Serial", and a couple of options will show up. In your case, you have CH341 selected. When I set up Octo4a for my Prusa MINI, I had to manually change the driver to CDC/ACM.

1 Like

I got Pronterface working - almost yelled like Dr. Frankenstein. It's alive!!!

When I tap on it, nothing happens. I tried stopping the server, restarting the app on the kindle, and restarting the kindle. It still doesn't do anything.

I've attached a screen recording of what I'm describing. You don't get the same pop up to select the driver? What printer is this?

I can upload the recording, but tapping it doesn't do anything. It's like tapping the text of "OctoPrint is running" or the white space below "Camera server is running".

Sorry - Ender 3 Pro.

What is going on? I found this thread and figured what could it hurt. It worked. I'm getting the following error:

Warning: Firmware Broken
Your printer's firmware is known to have a broken implementation of the communication protocol. This may cause print failures or other annoyances. You'll need to take additional steps for OctoPrint to fully work with it.

But I'm connected and able to move the extruder around. Now to try a print.

I'm going to leave this open for now in case this decides to stop working.

You can solve that error with the link provided in the message.

Yes, I've installed that. But now I'm getting this error again.

State: **Offline after error**
Too many consecutive timeouts, printer still connected and alive?

Going to try a full shutdown and go from square one.

Communication error

There was a communication error while talking to your printer. Please consult the terminal output and octoprint.log for details. Error: Too many consecutive timeouts, printer still connected and alive?

I disabled the TF / SD plug in and it's working again... what the hell???

So it seems I can basically use it as long as I don't use the local SD card. I can manage without it. Thank you all for your help.