Octoprint not working Original Prusa i3 MK3 via GPIO #2293
Comments
|
Hi @KissmanCZ, It looks like there is some information missing from your bug report that will be needed in order to solve the problem. Read the Contribution Guidelines which will provide you with a template to fill out here so that your bug report is ready to be investigated (I promise I'll go away then too!). If you did not intend to report a bug but wanted to request a feature or brain storm about some kind of development, please take special note of the title format to use as described in the Contribution Guidelines. Please do not abuse the bug tracker as a support forum - if you have a question or otherwise need some kind of help or support refer to the Mailinglist or the G+ Community instead of here. Also make sure you are at the right place - this is the bug tracker of the official version of OctoPrint, not the Raspberry Pi image OctoPi nor any unbundled third party OctoPrint plugins or unofficial versions. Make sure too that you have read through the Frequently Asked Questions and searched the existing tickets for your problem - try multiple search terms please. I'm marking this one now as needing some more information. Please understand that if you do not provide that information within the next two weeks (until 2017-12-29 23:10 UTC) I'll close this ticket so it doesn't clutter the bug tracker. This is nothing personal, so please just be considerate and help the maintainers solve this problem quickly by following the guidelines linked above. Remember, the less time the devs have to spend running after information on tickets, the more time they have to actually solve problems and add awesome new features. Thank you! Best regards, PS: I'm just an automated script, not a human being, so don't expect any replies from me :) Your ticket is read by humans too, I'm just not one of them. |
GitIssueBot
added
the
incomplete
|
It works flawlessly over USB (I just tried), so that's not a general compatibility issue. It doesn't look like there's a printer on the other end of your Make sure you've enabled GPIO serial and are trying to connect to the correct port. Then please report back. |
foosel
added
needs information
|
I disabled bluetooth from ttyAMA0 and console login from UART first of course :) tested with diferent speeds and still not working (UART is enabled and getty service stopped and disabled):
|
|
Tested to open serial on Rpi with sudo screen /dev/ttyAMA0, so I know, my port is right and not busy with another service or app. OctoPrint reports this when I open port on Rpi screen - port busy :)
And when I close screen /dev/ttyAMA0, i get
and again, no M110 respond :( |
|
Does you octoprint user even have access rights to /dev/ttyAMA0 ?
…On Sat, Dec 16, 2017 at 8:09 PM, Jan Pichrt ***@***.***> wrote:
Tested to open serial on Rpi with sudo screen /dev/ttyAMA0, so I know, my
port is right and not busy with another service or app.
OctoPrint reports this when I open port on Rpi screen - port busy :)
Connecting to: /dev/ttyAMA0Changing monitoring state from 'Offline' to
'Error: Connection error, see Terminal tab'Unexpected error while
connecting to serial port: /dev/ttyAMA0 OSError: '[Errno 16] Device or
resource busy: '/dev/ttyAMA0'' @ comm.py:_openSerial:1931 (hook default)
And when I close screen /dev/ttyAMA0, i get
Connecting to: /dev/ttyAMA0Changing monitoring state from 'Offline' to
'Opening serial port'Connected to: Serial<id=0xac95c730,
open=True>(port='/dev/ttyAMA0', baudrate=115200, bytesize=8, parity='N',
stopbits=1, timeout=10.0, xonxoff=False, rtscts=False, dsrdtr=False)
and again, no M110 respond :(
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#2293 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA5ZMK1f-Is784U0cz58UXHEzVpl_C0Cks5tBBVcgaJpZM4REGZz>
.
|
|
Yup... added "Pi" user under which service OctoPrint running to group "dialout"
|
|
and rebooted the pi? (or fully restarted all relevant processes?)
…On Sat, Dec 16, 2017 at 8:51 PM, Jan Pichrt ***@***.***> wrote:
Yup... added "Pi" user under which service OctoPrint running to group
"dialout"
***@***.***:~ $ ls -l /dev/ttyAMA0
crw-rw---- 1 root dialout 204, 64 Dec 16 19:23 /dev/ttyAMA0
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#2293 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA5ZMOBq7g2FzZn-2u2ieyVJOfyWkPQpks5tBB8tgaJpZM4REGZz>
.
|
|
Of course :) rebooted |
|
Maybe this is related? prusa3d/Prusa-Firmware#297 |
|
Well, I can certainly tell you that I also don't get any reply or even output at all using minicom, so whatever it is, it's not the fault of OctoPrint. My money would be on the firmware not being ready yet. Comparison... minicom via USB, printer resets and firmware says hello: minicom via |
foosel
added
not octoprint
|
so looks like nothing is connected to AMA0 ... tried swapping tx and rx
yet? :D
…On Sat, Dec 16, 2017 at 10:05 PM, Gina Häußge ***@***.***> wrote:
Well, I can certainly tell you that I also don't get any reply or even
output at all using minicom, so whatever it is, it's not the fault of
OctoPrint. My money would be on the firmware not being ready yet.
Comparison... minicom via USB, printer resets and firmware says hello:
Welcome to minicom 2.7
OPTIONS: I18n
Compiled on May 7 2017, 05:18:49.
Port /dev/ttyACM0, 21:01:11
Press CTRL-A Z for help on special keys
start
echo:echo: Last Updated: Nov 29 2017 02:01:00 | Author: (none, default config)
Compiled: Nov 29 2017
echo: Free Memory: 1522 PlannerBufferBytes: 1392
echo:Hardcoded Default Settings Loaded
crashdet_enable
CrashDetect ENABLED!
PAT9125_init:1
FSensor
ENABLED
fsensor_enable
PAT9125_init:1
tmc2130_init mode=0
initial zsteps on power up: 1016
initial zsteps after reset: 1016
echo:SD card ok
minicom via /dev/ttyAMA0 after disabling bluetooth and getty, nothing at
all happens:
Welcome to minicom 2.7
OPTIONS: I18n
Compiled on May 7 2017, 05:18:49.
Port /dev/ttyAMA0, 20:59:08
Press CTRL-A Z for help on special keys
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#2293 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA5ZMCTJC8v6kXXyIuaYh27DH5tSuDgKks5tBDCkgaJpZM4REGZz>
.
|
|
Heh, good idea, but nope, that's not it either. |
|
So, we must wait for Prusa EINSY firmware fix as I understand? |
|
Based on my own observations so far: yes. If it wasn't late and I wasn't also fighting off the start of another cold I'd give it a try to simply compile a new firmware including the PR you linked and see where that gets us. But maybe someone else wants to try that ;) In any case - closing because this doesn't look too be an OctoPrint problem at all but rather a MK3 problem. Happy to reopen should new information come in that proofs the contrary. Comments are still open though. |
|
Ok... fast chat with Prusa support :( `Já22:49 Shane22:51 Shane22:51 |
|
Thanks for your time Gina! ;) |
|
Ah, that at least confirms it then 👍 |
|
There is a mention on Prusa forum before few minutes...
|
|
New firmware is up ;) 3_1_1_rc2_b137 going to test. |
|
Did you get it work? and when how? |
|
Just want to put this here in case anyone else runs into problems: there are additional settings that must be made to the octoprint software before it will work with the MK3 and the Raspberry Pi Zero W https://help.prusa3d.com/l/en/article/Loz15FAgEk-octo-print-raspberry-pi-zero-w In theory, running sudo apt-get update and sudo apt-get upgrade (maybe even apt update and apt upgrade, or apt dist-upgrade) should upgrade all the binaries on the Pi and possible speed some things up for you too. |
|
As a side note, contrary to Prusa, I do not recommend the RPi0W. It's WIFI interface has some serious issues and utilizing it causes severe CPU load. And it's overall rather slow. |
|
Just to clarify: Is this solely because of the video streaming? I'm not having a bad time using mine to print so far. See top here: https://i.imgur.com/jZtyc1o.png I'm going to try using the camera module in a couple days. I don't plan on utilizing streaming, though, I just want timelapses. I feel like the RPiZW should have enough power to at least run serve the http and take a picture every every few minutes or so. Is the streaming only "turned on" when a user tries to connect to it, or can disable it? By the way, thank you for all your hard development work! |
|
Video streaming, or any kind of network utilization really. I got reproductions without running OctoPrint or a webcam at all by just copying a file from or to a location on my local network via the Pi0W. I'd also strongly advise against uploading (or downloading, e.g. by switching to the GCODE viewer) large files while printing. Anything that produces traffic on the network interface causes load and can cause stuttering. Same load issue on the Pi3, but with its four course it simply doesn't have a noticeable impact on print performance. For some shots of Just leaving the stream URL unconfigured and only limiting yourself to snapshots could work. Or using the SnapStream plugin (a good interval would need to be tested). But sorry, I really can't recommend it. |
|
I'm tempted to attach an Ethernet NIC to RPi0 (via SPI) and give it a try. If the CPU utilization wasn't that scary it could be a good compromise for Octoprint. |
I bought a PI Zero W without making sure it would work 100%. My bad for trusting Prusa. I want to use this card so that I can perform bed leveling using one of the add-ins. If I disable the WiFi component, will this card be able to perform this basic function? Would I just add a USB WiFi or ethernet dongle to this device? |
Should be. It's not a board you wanna use to print from but octoprint without any serious plugins (the bed level visualiser etc will not be a problem) it will work... so you setup the rpi0w with octoprint, just make sure you do not print from the octoprint but you print from the printer's sd card, so even if rpi0w cpu crap out it's not affecting the printer... this will make bunch of plugins unusable (you cannot do octolapse for e.g.) but it will still allow you to monitor the printer and use few interesting plugins... just don't print from it as it will ruin your prints |
Thanks for the advice regarding printing, I never planned on using it as a print server. Good to know. |
What did you expect to happen?
Working Octoprint on Rpi Zero via GPIO with EINSY Rambo in Prusa MK3
What happened instead?
Nothing, is not possible to connect MK3 to Octoprint via GPIO
Did the same happen when running OctoPrint in safe mode?
Yes
Version of OctoPrint
1.3.6
Operating System running OctoPrint
OctoPi 0.14.0
Printer model & used firmware incl. version
Original Prusa MK3, fw. 3.1.1 RC1 b122
Link to octoprint.log
https://pastebin.com/uKhXcJLJ
Link to contents of terminal tab or serial.log
https://pastebin.com/MvKm0gQL
The text was updated successfully, but these errors were encountered: