HELP - Octoprint & RPI3 GPIO bizarre response codes
Dear friends,
I'm connecting a brand new Prusa i3 MK3S printer to a raspberry pi 3B+ via GPIO. I am not able to connect it. I have checked the cables and I have followed the PRUSA tutorial but I am unable to connect them. Anyway, I do see that there's communication between the raspberry and the printer.
Here is the first log I saw when connecting:
Connecting to: /dev/ttyAMA0
Changing monitoring state from "Offline" to "Opening serial port"
Connected to: Serial<id=0x6a931bf0, open=True>(port='/dev/ttyAMA0', 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 N0125
Baudrate test retry #1
Send: N0 M110 N0125
Baudrate test retry #2
Send: N0 M110 N0125
Baudrate test retry #3
Recv: e\x00cho:Unknown command:0"<��O���������y�=�����\x7f�|�k�������[+������\x7f\x1eb?>�o_rd-u�O�ukj�:U���������;����;t'�Z���[ok
Send: N0 M110 N0125
Recv: uv{oz:M�\x7fe�u{��W)k�����1�����������������X Last Line: 0
Recv: Resend: 1
Recv: ok
Changing monitoring state from "Detecting baudrate" to "Operational"
Send: N0 M110 N0125
Communication timeout while idle, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
Send: N1 M11539
Recv: Error:No Line�������with�,�{����l����}\x7fu����]�����������{�o�����\x7f��{o��o-��>o��������o�[<�y�����_��=�X:io��o��e���������q���+�����]+����U.���� �2j�kk�ecyK��k�owo�coomqnf: "\x1a/~W.m~l\x14"()"(2)
See octoprint.log for details
Changing monitoring state from "Operational" to "Offline (Error: See octoprint.log for details)"
Connection closed, closing down monitor
And in another try I did, this is the output from serial.log:
2019-08-10 22:20:31,902 - Changing monitoring state from "Connecting" to "Offline"
2019-08-10 22:20:34,820 - Connecting to: /dev/ttyAMA0
2019-08-10 22:20:34,833 - Changing monitoring state from "Offline" to "Opening serial port"
2019-08-10 22:20:34,838 - Connected to: Serial<id=0x6977cb30, open=True>(port='/dev/ttyAMA0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=10.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
2019-08-10 22:20:34,838 - Changing monitoring state from "Opening serial port" to "Connecting"
2019-08-10 22:20:34,854 - Send: N0 M110 N0125
2019-08-10 22:20:41,022 - Recv: u��k��k�
��mX�i�"����m�-ook
esjo>U������komm\����=���".2"(2)
2019-08-10 22:20:41,025 - Recv: ok
2019-08-10 22:20:41,038 - Changing monitoring state from "Connecting" to "Operational"
2019-08-10 22:20:41,058 - Send: N0 M110 N0125
2019-08-10 22:21:33,213 - Communication timeout while idle, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
2019-08-10 22:21:33,220 - Send: N1 M11539
2019-08-10 22:22:03,242 - Communication timeout while idle, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
2019-08-10 22:22:03,253 - Send: N2 M2118
These are the software versions:
OctoPrint Version: 1.3.11
Prusa Firmware: 3.7.2-2363
Raspberry Pi OS: Octopi 0.16.0
Any help is appreciated.
Best regards.
RE: HELP - Octoprint & RPI3 GPIO bizarre response codes
I don't see this mentioned,
did you set the internal raspberry pi port to On in the Mk3 printer LCD Menu?
regards Joan
I try to make safe suggestions,You should understand the context and ensure you are happy that they are safe before attempting to apply my suggestions, what you do, is YOUR responsibility. Location Halifax UK
RE: HELP - Octoprint & RPI3 GPIO bizarre response codes
Yes I did...
If I put th eoption "off" then the terminal console goes crazy sending messages like a loop, otherwise with option to "on" it sends me those messages in the first post.
RE: HELP - Octoprint & RPI3 GPIO bizarre response codes
Hope you find an answer. I had the same idea and experienced the same problem.
RE: HELP - Octoprint & RPI3 GPIO bizarre response codes
I recall that the on-board wifi RPi models need a bit of reconfiguration to use USB serial connections. Might that be part of the problem?
and miscellaneous other tech projects
He is intelligent, but not experienced. His pattern indicates two dimensional thinking. -- Spock in Star Trek: The Wrath of Khan
RE: HELP - Octoprint & RPI3 GPIO bizarre response codes
try changing to a fixed baud rate instead of autobaud - the garbage message happened to contain the random string "ok" which octoprint saw as a valid response.
RE: HELP - Octoprint & RPI3 GPIO bizarre response codes
Well, I don't know where the problem resides. I followed al the "how to" instructions from the Prusa website
https://help.prusa3d.com/article/Loz15FAgEk-octo-print-raspberry-pi-zero-w
I modified /boot/config.txt and /boot/cmdlint.txt etc... After the changes were saved I shut down, powered off and then restarted. I have checked the wiring (cable between Rpi 4 and Eincy board) I am reasonable sure it is correct.
I also tried selecting the fixed baud rates, each one in turn. So far, nothing has worked. If anyone else has suggestions, I will give them a try.
RE: HELP - Octoprint & RPI3 GPIO bizarre response codes
Check these settings - and no - I don't know what they should be, but they look suspiciously wrong. At least one should be True.
xonxoff=False, rtscts=False, dsrdtr=False
RE: HELP - Octoprint & RPI3 GPIO bizarre response codes
@paffendorf were you able to find a solution?
RE: HELP - Octoprint & RPI3 GPIO bizarre response codes
from that log you have an autobaud problem, the pi is sending test query's and not getting a valid response back but it is getting a random "ok" in the returned garbage and thinking it has the correct speed selected. i would turn off autobaud on the pi and try using fixed speeds
RE: HELP - Octoprint & RPI3 GPIO bizarre response codes
You wrote you are using a Raspberry 4. Do you have the same problems with older version (3B, 3B+)?
Statt zu klagen, dass wir nicht alles haben, was wir wollen, sollten wir lieber dankbar sein, dass wir nicht alles bekommen, was wir verdienen.