I had the Pi0 and replaced it with a Pi3b+ but in doing so I hooked the block cable up 1 row to high. /sigh. I don't know if I blew up the data ports on the PI or the Einsy but my Pi0 doesn't work either, but I was moving around SD cards and reformatting and Puttying all over and I'm not a Linux person... so.
Anyone know of a way to tell if I blew my PI or Einsy or maybe some odd config I'm missing? Power to the PI and USB work fine when I revert back to OctoPi defaults.
To clarify, I'm up and running (and powered) with the PI and Einsy, but have to use USB like in the pic below (=
I put a red box on the screenshot where I put the block connector on wrong.
- Edited: /boot/cmdline.txt -add: dtoverlay=pi3-miniuart-bt
- Edited: /boot/config.txt -remove: console=serial0,115200
- Turned on RPI port on MK3S
- Added /dev/ttyAMA0 to OctoPrint
Connecting to: /dev/ttyAMA0 Changing monitoring state from "Offline" to "Opening serial port" Connected to: Serial<id=0x6721cd90, open=True>(port='/dev/ttyAMA0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=10.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor Changing monitoring state from "Opening serial port" to "Connecting" Send: N0 M110 N0*125 No answer from the printer within the connection timeout, trying another hello Send: N0 M110 N0*125 There was a timeout while trying to connect to the printer Changing monitoring state from "Connecting" to "Offline" Connection closed, closing down monitor
2020-03-23 20:14:35,859 - octoprint.util.comm - INFO - Could not enter programming mode on /dev/ttyAMA0: u'Timeout'