New Octoprint build - Cant connect to printer

Problem: No matter what serial settings, the web page just shows connecting and then goes to offline. Getting ( Offline (Error: No more baudrates to test, and no suitable baudrate found.))

Tried: Changing the USB cable and rebooting the pi. tried changing to all different Baud rates, as well as auto.

Serial log below.

Additional information about your setup (OctoPrint 1.3.11 running on OctoPi 0.15.1, Monoprice Select Mini v2,Firmware: 35.110.2, Firefox, Mac)

2019-09-03 16:36:31,264 - serial.log is currently not enabled, you can enable it via Settings > Serial Connection > Log communication to serial.log
2019-09-03 16:36:33,188 - serial.log is currently not enabled, you can enable it via Settings > Serial Connection > Log communication to serial.log
2019-09-03 16:36:43,651 - serial.log is currently not enabled, you can enable it via Settings > Serial Connection > Log communication to serial.log
2019-09-03 16:37:21,542 - serial.log is currently not enabled, you can enable it via Settings > Serial Connection > Log communication to serial.log
2019-09-03 16:42:11,804 - serial.log is currently not enabled, you can enable it via Settings > Serial Connection > Log communication to serial.log
2019-09-03 16:45:07,897 - Enabling serial logging
2019-09-03 16:45:11,346 - Changing monitoring state from "Offline" to "Detecting serial port"
2019-09-03 16:45:11,373 - Serial port list: ['/dev/ttyACM0']
2019-09-03 16:45:11,374 - Connecting to: /dev/ttyACM0
2019-09-03 16:45:11,378 - Changing monitoring state from "Detecting serial port" to "Opening serial port"
2019-09-03 16:45:11,382 - Connected to: Serial<id=0x6a7e88d0, open=True>(port='/dev/ttyACM0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=10.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
2019-09-03 16:45:11,383 - Changing monitoring state from "Opening serial port" to "Connecting"
2019-09-03 16:45:11,395 - Send: N0 M110 N0125
2019-09-03 16:45:41,435 - There was a timeout while trying to connect to the printer
2019-09-03 16:45:41,449 - Changing monitoring state from "Connecting" to "Offline"
2019-09-03 16:45:41,463 - Connection closed, closing down monitor
2019-09-03 16:54:58,569 - Changing monitoring state from "Offline" to "Detecting serial port"
2019-09-03 16:54:58,597 - Serial port list: ['/dev/ttyACM0']
2019-09-03 16:54:58,598 - Connecting to: /dev/ttyACM0
2019-09-03 16:54:58,603 - Changing monitoring state from "Detecting serial port" to "Opening serial port"
2019-09-03 16:54:58,607 - Connected to: Serial<id=0x6a7e8250, open=True>(port='/dev/ttyACM0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=10.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
2019-09-03 16:54:58,608 - Starting baud rate detection...
2019-09-03 16:54:58,612 - Changing monitoring state from "Opening serial port" to "Detecting baudrate"
2019-09-03 16:54:59,622 - Trying baudrate: 115200
2019-09-03 16:54:59,637 - Send: N0 M110 N0
125
2019-09-03 16:55:09,646 - Baudrate test retry #1
2019-09-03 16:55:09,660 - Send: N0 M110 N0125
2019-09-03 16:55:10,660 - Baudrate test retry #2
2019-09-03 16:55:10,671 - Send: N0 M110 N0
125
2019-09-03 16:55:11,670 - Baudrate test retry #3
2019-09-03 16:55:11,676 - Send: N0 M110 N0125
2019-09-03 16:55:12,687 - Baudrate test retry #4
2019-09-03 16:55:12,701 - Send: N0 M110 N0
125
2019-09-03 16:55:13,696 - Trying baudrate: 250000
2019-09-03 16:55:13,703 - Send: N0 M110 N0125
2019-09-03 16:55:14,703 - Baudrate test retry #1
2019-09-03 16:55:14,716 - Send: N0 M110 N0
125
2019-09-03 16:55:15,709 - Baudrate test retry #2
2019-09-03 16:55:15,723 - Send: N0 M110 N0125
2019-09-03 16:55:16,720 - Baudrate test retry #3
2019-09-03 16:55:16,727 - Send: N0 M110 N0
125
2019-09-03 16:55:17,727 - Baudrate test retry #4
2019-09-03 16:55:17,739 - Send: N0 M110 N0125
2019-09-03 16:55:18,738 - Trying baudrate: 230400
2019-09-03 16:55:18,753 - Send: N0 M110 N0
125
2019-09-03 16:55:19,752 - Baudrate test retry #1
2019-09-03 16:55:19,767 - Send: N0 M110 N0125
2019-09-03 16:55:20,765 - Baudrate test retry #2
2019-09-03 16:55:20,780 - Send: N0 M110 N0
125
2019-09-03 16:55:21,776 - Baudrate test retry #3
2019-09-03 16:55:21,783 - Send: N0 M110 N0125
2019-09-03 16:55:22,790 - Baudrate test retry #4
2019-09-03 16:55:22,799 - Send: N0 M110 N0
125
2019-09-03 16:55:23,801 - Trying baudrate: 57600
2019-09-03 16:55:23,810 - Send: N0 M110 N0125
2019-09-03 16:55:24,815 - Baudrate test retry #1
2019-09-03 16:55:24,820 - Send: N0 M110 N0
125
2019-09-03 16:55:25,820 - Baudrate test retry #2
2019-09-03 16:55:25,835 - Send: N0 M110 N0125
2019-09-03 16:55:26,833 - Baudrate test retry #3
2019-09-03 16:55:26,848 - Send: N0 M110 N0
125
2019-09-03 16:55:27,840 - Baudrate test retry #4
2019-09-03 16:55:27,847 - Send: N0 M110 N0125
2019-09-03 16:55:28,848 - Trying baudrate: 38400
2019-09-03 16:55:28,854 - Send: N0 M110 N0
125
2019-09-03 16:55:29,867 - Baudrate test retry #1
2019-09-03 16:55:29,874 - Send: N0 M110 N0125
2019-09-03 16:55:30,874 - Baudrate test retry #2
2019-09-03 16:55:30,887 - Send: N0 M110 N0
125
2019-09-03 16:55:31,891 - Baudrate test retry #3
2019-09-03 16:55:31,897 - Send: N0 M110 N0125
2019-09-03 16:55:32,899 - Baudrate test retry #4
2019-09-03 16:55:32,912 - Send: N0 M110 N0
125
2019-09-03 16:55:33,919 - Trying baudrate: 19200
2019-09-03 16:55:33,928 - Send: N0 M110 N0125
2019-09-03 16:55:34,928 - Baudrate test retry #1
2019-09-03 16:55:34,941 - Send: N0 M110 N0
125
2019-09-03 16:55:35,935 - Baudrate test retry #2
2019-09-03 16:55:35,947 - Send: N0 M110 N0125
2019-09-03 16:55:36,946 - Baudrate test retry #3
2019-09-03 16:55:36,960 - Send: N0 M110 N0
125
2019-09-03 16:55:37,959 - Baudrate test retry #4
2019-09-03 16:55:37,970 - Send: N0 M110 N0125
2019-09-03 16:55:38,972 - Trying baudrate: 9600
2019-09-03 16:55:38,985 - Send: N0 M110 N0
125
2019-09-03 16:55:39,986 - Baudrate test retry #1
2019-09-03 16:55:39,998 - Send: N0 M110 N0125
2019-09-03 16:55:40,999 - Baudrate test retry #2
2019-09-03 16:55:41,011 - Send: N0 M110 N0
125
2019-09-03 16:55:42,014 - Baudrate test retry #3
2019-09-03 16:55:42,023 - Send: N0 M110 N0125
2019-09-03 16:55:43,024 - Baudrate test retry #4
2019-09-03 16:55:43,036 - Send: N0 M110 N0
125
2019-09-03 16:55:44,032 - Changing monitoring state from "Detecting baudrate" to "Error: No more baudrates to test, and no suitable baudrate found."
2019-09-03 16:55:44,050 - Changing monitoring state from "Error: No more baudrates to test, and no suitable baudrate found." to "Offline (Error: No more baudrates to test, and no suitable baudrate found.)"
2019-09-03 16:55:44,065 - Connection closed, closing down monitor

You might want to disconnect the printer, run dmesg > ~/before.txt, connect the printer, run dmesg > ~/after.txt then run a diff ~/before.txt ~/after.txt to see if you can determine your printer's port.

Im sorry, but could you simplify this in beginners terms. Ive been using octoprint for 4 years, but I don't know what your saying here.

Should have mentiend that this was a running system prior to last week but had to rebuild the octopi as it just stopped connecting. Seems like the SD went bad. But now this problem. Serial port used to be /DEV/ttyACM0. But that doesnt work now.

I'm referring to commands that you'd run while remoted into the Pi itself from the command line terminal.

  • dmesg is a command that will list the messages related to the devices which are installed within the operating system itself. It might look something like this:
[   38.199364] Adding 163836k swap on /var/swap.  Priority:-2 extents:3 across:393212k SSFS
[   38.446287] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   38.446487] brcmfmac: power management disabled
[   38.964496] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[   38.964824] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   39.902495] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  • Running something like dmesg > ~/before.txt would run that as before but it would redirect its output to a file in your home directory. Similarly, the next command would do the same but with a different file name.
  • The diff—related command would attempt to show you the difference between the contents of two files. It's that difference that we're interested in. In theory, there may be perhaps three lines added to that dmesg content when you plug the printer cable back in. This then might confirm or deny the assertion that your printer is seen on /dev/ttyACM0.
2 Likes

ok so, I tried this. But the Tilda ~ doesnt look like that. in the Pi's terminal. and I get an error that there is no such file or directory. In the photo you can see above that running dmesg worked, but running it with the extra text to export to a text file is not working.

Any thoughts?

If you paste and copy, it may change on the OS you are using

If this is happening locally to the Pi (and that looks like a 10" TFT screen) then you'd be using a local keyboard and this would need to be configured for your country.

sudo raspi-config
# Localisation

Having adjusted things for your country/language/keyboard/timezone/wifi country then it will reboot and probably behave a little better.

1 Like

I have tried maybe 20 of the keyboard layouts, different locals. Nothing seems to get the ~ to show up. Anyone know why I would be having this issue using the same build IMG file as all my other Pi's? And this Pi was working a week ago as well.

Also when I try to just terminal from my mac at SSH 172.18.21.XXX and it asks for the password. the password I used to access the PI though the HDMI output of the Pi does not work. so I cannot try to use terminal on my mac to do this either.

Weird stuff...

Jamie

So login with your local keyboard and at the command prompt type your password and see what it is. It may not be what you think it is. Then use that password for the remote ssh session.

That is the password I am trying to use. The password that works with the Pi username on the terminal, but that same password does not work on my Mac when I use OSX terminal. On the Mac I lunch terminal and then type “ssh 191.168.1.X”
and it asks for a password. But the password does not work.

Okay, so on the local keyboard run:

sudo passwd pi

...and change the password to something simple while you're setting this up. Just use lowercase letters, for example.

I think I know what you are saying about using the local keyboard because the keys might not be the same as the mac, but the password is just lowercase letters and Im pretty sure the regular alphabet characters are fine, because I have no issues with commands like sudo raspi-config.

Change the password to "a" on the local keyboard and see if the Mac can now login.

I will try that in the morning, its at my office.

I've had the same issue with both of my pi's (both 3b+). I'm getting pretty frustrated. I hope you respond once you find out.
On mine I can control everything fine, Home, control temperatures everything until I try to load a gcode then it locks up and the printer go to 0 temps. multiple reboots, powersupplies. I was getting ready to reflash octopi (one is 6 months old the other only a month). There has to be acommon thread here.

Please help.

Some logs would be quite helpful - especially the serial.log.

1 Like

Curious, what printer are you connecting to?

Edit: Nvm, I missed it in your post. I was going to suggest, if it's a printer that uses binary form of gcode, x3g file, you need to make sure to have GPX installed. I ran into this headache wondering why my printer won't connect after a rebuild and it was that. The printer had no idea what it was being sent.

1 Like

Ok, IM back at it this week. Did a fresh flash of the SD and octoprint. Same connection issue. Right now with the pport set how it should be with the port name and baud rate from before, it just says connecting for 60second and then says offline. here are the logs.
And by judging from the before and after log, my port is correct.

![31%20AM|596x500]
serial(2).log (740 Bytes) octoprint(1).log (11.7 KB)![IMG_2672|666x500]

Your serial.log is trying to tell you something...

2019-09-16 19:23:09,942 - serial.log is currently not enabled, you can enable it via Settings > Serial Connection > Log communication to serial.log

And don't forget someone's advice.

So Im getting this when searching for GPX plugin. But IM pretty sure the unit has internet.