Folgertech Prusa i3 + Octopi

I got my printer built and it works pretty smoothly... But the software side of things is being an issue, but I figure screw it, I intend to run it from the Raspberry Pi B+ I bought just for this. Octopi is loaded and running. I can connect to it via my web browser... I've set the port to the autopopulated /dev/ttyAMA0 and the baudrate to 115200 (how it was working from my Ubuntu desktop) and click connect....

The terminal says

Connecting to: /dev/ttyAMA0
Connected to: Serial(port='/dev/ttyAMA0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=60.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
Changing monitoring state from 'Opening serial port' to 'Connecting'
Send: M105
Send: M105
Send: M105
Send: M105
Send: M105
Send: M105
Send: M105

It never gets a reply from the printer to the M105 code and it never says anything else. The light on the RAMPs isn't lit and the controls for moving the print head around remain greyed out... I've set both time-outs to a minute. Any suggestions?

I intend to run it from the Raspberry Pi so that I can put it on the other side of the room where there is less air flow (I have both a fan and the AC pointed at where my desktop is) and I can share it with a friend, so this is crucial to me.

USB-Serial is not working, possibly your printer was assigned to /dev/tty_somethingelse_
Disconnect printer, dmesg, reconnect printer, dmesg again and check what it says.
Check the permissions on /dev/ttyAMA0 on the RPi and set the baud rate to Auto in OctoPrint.

Quote
AndrewBCN
USB-Serial is not working, possibly your printer was assigned to /dev/tty_somethingelse_
Disconnect printer, dmesg, reconnect printer, dmesg again and check what it says.
Check the permissions on /dev/ttyAMA0 on the RPi and set the baud rate to Auto in OctoPrint.

You're right, it ended up being assigned /dev/ttyACM0

[ 3.446619] usb 1-1.5: new full-speed USB device number 4 using dwc_otg
[ 3.572769] usb 1-1.5: New USB device found, idVendor=2341, idProduct=0042
[ 3.584236] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=220
[ 3.596236] usb 1-1.5: Manufacturer: Arduino (www.arduino.cc)
[ 3.613155] usb 1-1.5: SerialNumber: 75438313633351A051F0
[ 4.614143] udevd[159]: starting version 175
[ 6.060962] cdc_acm 1-1.5:1.0: ttyACM0: USB ACM device
[ 6.158173] usbcore: registered new interface driver cdc_acm
[ 6.166067] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters

Following your instructions it's still not connecting successfully. I even increased the autodection timeout to 2 minutes.


---------- Update

It finally connected... at 115200 after a lot of waiting for autodetect to get there. Thanks for the help.

Trying baudrate: 115200
Recv: echo:Unknown command: "?????H??W.?W/?W/?????V/?????"
Recv: ok
Baudrate test ok: 1
Baudrate test ok: 2
Baudrate test ok: 3
Baudrate test ok: 4
Baudrate test ok: 5
Baudrate test ok: 6
Baudrate test ok: 7
Baudrate test ok: 8
Baudrate test ok: 9
Send: M999
Changing monitoring state from 'Detecting baudrate' to 'Operational'

Edited 1 time(s). Last edit at 03/27/2015 07:01PM by hathalud.

Did you configure OctoPrint for ttyACM0?

Did you configure the baud rate to Auto?

Did you check the permissions for /dev/ttyACM0 (just do an ls -la /dev/tty*).

Does the user pi have the permissions to write to /dev/ttyACM0?

The communication, connection and autodetection timeouts need to be at least 120 seconds and the baudrate being set to 115200. It takes several minutes to successfully connect, but it eventually does.

Try setting the baud rate to 250000 both in OctoPrint and the firmware, that should speed up things considerably.