GEEETECH I3 PRO C Connecting but not heating/printing

What is the problem?
Connected to a GEEETECH i3 Pro C via OctoPrint using a RASPI PI 1 through ethernet.
i can set preheat temps which change on the screen but the printer does not heat. Also manual control does not seem to work either but i have definitely have a connection to the printer
What did you already try to solve it?
yes i did try turn it off and on again
multiple reboots and fireware checks
disconnecting and reconnecting printer

Logs (octoprint.log, serial.log or output on terminal tab, ...)

Changing monitoring state from "Offline" to "Detecting serial port"
Serial port list: ['/dev/ttyUSB0']
Connecting to: /dev/ttyUSB0
Changing monitoring state from "Detecting serial port" to "Opening serial port"
Connected to: Serial<id=0xb2e486b0, open=True>(port='/dev/ttyUSB0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=10.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
Starting baud rate detection...
Changing monitoring state from "Opening serial port" to "Detecting baudrate"
Trying baudrate: 115200
Send: N0 M110 N0*125
Baudrate test retry #1
Send: N0 M110 N0*125
Baudrate test retry #2
Send: N0 M110 N0*125
Baudrate test retry #3
Send: N0 M110 N0*125
Recv: �Np|xF�6~i *6�If�BpON&�HOY�-�J=\x1aG"pYt\x17Oa8�U.6f�HGI�-p|HF\x03�~�Y\x08\x086�M�'��-Q�\x17\x12F�\x1b>\x17jW&��\x17\x12\x03aH>�\x07
Baudrate test retry #4
Send: N0 M110 N0*125
Trying baudrate: 250000
Recv: }M�6\x1b�8�echo:Unknown command: "\x18"
Recv: ok
Send: N0 M110 N0*125
Changing monitoring state from "Detecting baudrate" to "Operational"
Send: N0 M110 N0*125
Recv: ok
Send: N1 M115*39
Recv: ok
Send: N2 M21*18
Recv: FIRMWARE_NAME:V1.0.04 Sprinter/grbl mashup for gen6 FIRMWARE_URL: PROTOCOL_VERSION:1.0 MACHINE_TYPE:I3proC EXTRUDER_COUNT:2 UUID:00000000-0000-0000-0000-000000000000
Recv: 0123456789abcdef
Recv:  hardware:v1.05
Recv: ok
Recv: echo:SD init fail
Recv: ok
Send: M140 S60.0
Recv: ok
Send: M104 T0 S210.0
Recv: ok

Additional information about your setup (OctoPrint version, OctoPi version, printer, firmware, ...)
octoprint version: 1.3.11
OctoPi version 0.16.0

OctoPrint is definitely sending the heatup commands to your printer, so whatever is going wrong here, it's going wrong in your printer's firmware, not OctoPrint.

... and when I see this, I'm quite concerned about the USB connection...

Those words "through ethernet" in the description through me off a little. But I see the /dev/ttyUSB0 in the log. I would guess that the appropriate baudrate should be 250000 and probably should be selected manually versus AUTO. But as suggested, this is throwing a lot of junk back to OctoPrint. I'd verify that the serial cable is internally shielded or it has a ferrite core.

sorry i meant the OctoPrint internet connection was through ethernet not the printer

It's part of a baudrate auto detection and the tested baudrate doesn't match. This is probably a red herring and not an actual communication issue.

1 Like