-
Notifications
You must be signed in to change notification settings - Fork 369
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OctoPi 0.14.0 RC1 status #332
Comments
Print jobs crash with USB mouse and keyboard attached. This should be notated in description. I have disconnected mouse and keyboard from Pi Zero W and all seems well... |
@dbvandy Ok please dont spam the thread, If you have new information please edit an existing thread and type "update:" with the new information you want to add. |
@dbvandy What kind of mouse and keyboard and what kind of printer? I have not seen this behaviour in my own tests. Power issue? What does "Print jobs crash" mean, what happens exactly? @guysoft #336 at least sounds like we need some kind of workaround for the current |
Standard usb keyboard, Logitech m510 wireless mouse, delta kossel 180x280
printer running marlin.
The 16 command buffer ran down frequently and then finally ran out causing
the printer to quit.
After removing the keyboard and mouse from the passive usb hub, the printer
did not hit the buffer much if at all.
I would assume that the limited memory and processing power of the zero w
cause the processor to get overwhelmed with the multiple usb devices. I am
not aware of a way to monitor the cpu processes on the pi to verify that it
is bogging.
I can reproduce this effect by reconnecting the keyboard and mouse to the
hub.
This is some of the output when the printer is buffering and stuttering:
Send: N1429 G1 X19.316 Y16.397 E112.78947*93
Recv: T:224.26 /225 @:157
Recv: ok 1429
Send: N1430 G1 X19.215 Y16.773 E112.80242*80
Recv: Error:Wrong checksum
Recv:
Recv: Resend:1430
Recv: ok
Send: N1430 G1 X19.215 Y16.773 E112.80242*80
Recv: Error:Format error
Recv:
Recv: Resend:1430
Recv: ok
Send: N1430 G1 X19.215 Y16.773 E112.80242*80
Recv: Error:Format error
Recv:
Recv: Resend:1430
Recv: ok
Send: N1430 G1 X19.215 Y16.773 E112.80242*80
Recv: Error:Format error
Recv: ok 1429
Send: N1431 G1 X19.087 Y17.098 E112.81403*89
Recv: Error:Format error
Recv: ok 1429
Send: N1432 G1 X18.919 Y17.422 E112.82617*84
Recv: Unknown command:
Recv:
Recv: Resend:1430
Recv: ok
Send: N1430 G1 X19.215 Y16.773 E112.80242*80
Recv: Unknown command:
Recv: Error:Wrong checksum
Recv:
Recv: Resend:1430
Recv: ok
Send: N1431 G1 X19.087 Y17.098 E112.81403*89
Recv: ok 1430
Send: N1432 G1 X18.919 Y17.422 E112.82617*84
Recv: ok 1431
Send: N1433 G1 X18.727 Y17.712 E112.83774*83
Recv: ok 1432
Send: N1434 G1 X18.493 Y17.997 E112.85001*88
Recv: ok 1433
Send: N1435 G1 X18.251 Y18.235 E112.86129*85
Recv: ok 1434
Send: N1436 G1 X17.696 Y18.638 E112.88411*95
Recv: ok 1435
Send: N1437 G1 X17.381 Y18.798 E112.89586*88
Recv: ok 1436
Send: N1438 G1 X17.022 Y18.933 E112.90861*94
Recv: ok 1437
Send: N1439 G1 X16.362 Y19.074 E112.93106*89
Recv: ok 1438
Send: N1440 G1 X-15.709 Y19.094 E113.99775*119
Recv: ok 1439
Send: N1441 G1 X-16.338 Y19.076 E114.01868*122
Recv: ok 1440
Send: N1442 G1 X-16.691 Y19.022 E114.03055*122
Recv: ok 1441
Send: N1443 G1 X-17.067 Y18.921 E114.04350*127
Recv: ok 1442
Send: N1444 G1 X-17.392 Y18.793 E114.05512*119
Recv: ok 1443
Send: N1445 G1 X-17.717 Y18.625 E114.06729*122
Recv: ok 1444
Send: N1446 G1 X-18.013 Y18.429 E114.07910*126
Recv: ok 1445
Send: N1447 G1 X-18.286 Y18.204 E114.09086*112
Recv: ok 1446
Send: N1448 G1 X-18.530 Y17.956 E114.10244*114
Recv: ok 1447
Send: N1449 G1 X-18.752 Y17.677 E114.11429*117
Recv: ok 1448
Send: N1450 G1 X-18.952 Y17.363 E114.12668*119
Recv: ok 1449
Send: N1451 G1 X-19.102 Y17.061 E114.13789*116
Recv: ok 1450
Send: N1452 G1 X-19.229 Y16.720 E114.14999*118
Recv: ok 1451
Send: N1453 G1 X-19.320 Y16.366 E114.16215*116
Recv: ok 1452
Send: N1454 G1 X-19.368 Y16.066 E114.17226*125
Recv: ok 1453
Send: N1455 G1 X-19.388 Y15.452 E114.19269*119
--- too many lines to buffer, cut off ---
State: Error: Printer requested line 13598 but no sufficient history is available, can't resend
File: Laser_blast_shield_1_0_a.gcode
Timelapse: -
Filament (Tool 0): 7.72m
Approx. Total Print Time: 2 hours
Print Time: 00:12:54
Print Time Left: 2 hours ●
Printed: 420.3KB / 4.3MB
[Laser_blast_shield_1_0_a.zip](https://github.com/guysoft/OctoPi/files/889580/Laser_blast_shield_1_0_a.zip)
[Laser_blast_shield_1_0_a gcode.zip](https://github.com/guysoft/OctoPi/files/889582/Laser_blast_shield_1_0_a.gcode.zip)
The stl is sliced with Cura externally and then the gcode is dropped onto octopi server page.
Doug Vanderbilt
Senior Trainer / Consultant
Knowledge Tree Consulting
cell: 404.630.9840 <(404)%20630-9840>
…On Apr 3, 2017 4:50 AM, "Gina Häußge" ***@***.***> wrote:
@dbvandy <https://github.com/dbvandy> What kind of mouse and keyboard and
what kind of printer? I have not seen this behaviour in my own tests. Power
issue? What does "Print jobs crash" mean, what happens exactly?
@guysoft <https://github.com/guysoft> #336
<#336> at least sounds like we
need some kind of workaround for the current raspi-config behaviour,
otherwise IMHO no-go. Will comment there.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#332 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AZmmWnjc2Cq6ysHKPet6AGGmLAIUjgqWks5rsLLggaJpZM4Mv453>
.
|
Looks like some serious communication issues causing the stuttering, printer keeps requesting lines that look like they are sent ok. So either they become garbage on the line or when they arrive at the printer. So probably less of a CPU issue and more of a power issue (make sure the power supply provides 5V, 2.5A), or an overloaded bus maybe. Considering it's a wireless mouse, I wouldn't be too surprised actually if it's power and the dongle of the mouse is demanding too much, causing brown outs. Try leaving the mouse out of the equation. Currently running a test print against the image on a ZeroW, have a wireless keyboard-mouse-combo AND a mouse connected, as well as a pi camera and the printer itself. No communication errors. Power supply is this one, 5V, 2.5A.
I'd recommend Side note: I'm still seeing the abysmal performance with regards to CPU load when the webcam tab is opened as already mentioned in #318. @guysoft Should we maybe add a "but not recommended" to the bit about support for the Zero W? I really have a bad feeling recommending this thing for running prints when the built-in wifi is used. Even a timelapse download could nuke prints with this kind of performance. Currently seeing 25% for |
I hope Guysoft's question "Is that a no-go for the feature?" #336 does not result in removal of the octopi-wpa-supplicant.txt feature. That feature is a major plus for those of us who need a pi to run on multiple networks and need to add new networks easily. |
If we can't find a solution for the raspi-config issue though we'll at least need a big fat disclaimer in that file or we'll never hear the end of this issue (endless stream of tickets). |
Considering this and
I guess we should also make sure that RC2 has a newer kernel - if one is available. |
Is there a way to check if one is available?
|
https://www.raspberrypi.org/documentation/linux/kernel/updating.md Tried both, official package is still <4.5, what you get via rpi-update is 4.9 but not recommended according to the link above. Let's see what will be the state after the weekend. |
New image is out, short summary of findings:
I suggest building RC2 against that new image. |
@foosel Nighties are back, with the new image: https://storage.googleapis.com/octoprint/2017-04-22_2017-04-10-octopi-jessie-lite-0.14.0.zip Should we make RC2 out of this? |
When RC2 comes out, is it possible to update to this from within OctoPrint, or do I need to start fresh from that image? (I do have my OctoPrint update channel set to Devel RC). |
@John-Mc Fresh image. You can move most of your OctoPrint preferences between images. |
@guysoft don't see why not. Also sorry, currently out of commission (wisdom teeth extraction + cold or something, lovely combination), hence the delay in replying to this. |
Hello, Im having an issue getting the PI v2 camera to work with this build. Not sure if its something Im missing or another issue all together. I have already tried the get update and get upgrade and my GPU memory is over the 128 min. It is a new camera and cable (which is installed correctly) but I believe its has to be a setting somewhere im missing. Any help would be greatly appreciated. pi@octopi:~` $ raspistill -v -o test.jpg |
I think you will always get that error with raspistill on OctoPi because the camera will be already used by mjpg-streamer. |
The release from a week ago is working great on my RPi 3 with my D300VS printer and the obligatory Logitech C270. |
Did an OctoPi 0.14rc2 ever come out? I thought I had seen mention of it, but can't find it - and the link to the nightly builds is not working for me. |
You could always force the update in advanced settings
…Sent from my iPhone
On 2 Jun 2017, at 16:49, John-Mc <notifications@github.com<mailto:notifications@github.com>> wrote:
Did an OctoPi 0.14rc2 ever come out? I thought I had seen mention of it, but can't find it - and the link to the nightly builds is not working for me.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#332 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AbON6IRPeKD2Bhs9TbGj7EbAMot0W2ggks5sAC8EgaJpZM4Mv453>.
|
I could force an OctoPrint update. Not sure you can do an OctoPi update that way. Pretty sure you have to install that from the new image. |
Please use RC2 at #367 |
Please try the release candidate.
Download it at:
https://storage.googleapis.com/octoprint/2017-03-31_2017-03-02-octopi-jessie-lite-0.14.0.zip
md5:
https://storage.googleapis.com/octoprint/2017-03-31_2017-03-02-octopi-jessie-lite-0.14.0.zip.md5
It is built against Raspbian 2017-03-02 (Release Notes)
Changes in the image
/root/bin/webcamd
to useoctopi.txt
for configurationoctopi-network.txt
for Mac OS X users to not use Textedit/properly configure Texteditoctopi-wpa-supplicant.txt
config.yaml
and init script for OctoPrint to 1.3.0+install-desktop
script to only pull in needed packagespip
versions and pyasn1 (New pip 9 breaks install of pyasn1 #276)Note:
In 0.13.0 we promised new variant for more arm devices support. The has been a achieved with the new Armbian variant. With it, all the devices listed here support OctoPi, but since we didn't get a call for a specific device, we are not maintaining a build at the moment.
The text was updated successfully, but these errors were encountered: