Skip to content
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

Closed
guysoft opened this issue Mar 31, 2017 · 23 comments
Closed

OctoPi 0.14.0 RC1 status #332

guysoft opened this issue Mar 31, 2017 · 23 comments

Comments

@guysoft
Copy link
Owner

guysoft commented Mar 31, 2017

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

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.

@dbvandy
Copy link

dbvandy commented Apr 2, 2017

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...

@guysoft
Copy link
Owner Author

guysoft commented Apr 2, 2017

@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.
I am editing your messages to make them readable.

@guysoft
Copy link
Owner Author

guysoft commented Apr 3, 2017

@foosel Is this a no-go for the feature?
#336

@foosel
Copy link
Collaborator

foosel commented Apr 3, 2017

@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 raspi-config behaviour, otherwise IMHO no-go. Will comment there.

@dbvandy
Copy link

dbvandy commented Apr 3, 2017 via email

@foosel
Copy link
Collaborator

foosel commented Apr 3, 2017

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 am not aware of a way to monitor the cpu processes on the pi

I'd recommend top, it's is already installed.


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 kworker and 18% for irq/86-mmc1 (wifi handling) with traffic, and THAT certainly will cause stuttering.

@John-Mc
Copy link

John-Mc commented Apr 3, 2017

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.

@foosel
Copy link
Collaborator

foosel commented Apr 3, 2017

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).

@foosel
Copy link
Collaborator

foosel commented Apr 13, 2017

Considering this and

OctoPi version    : 0.14.0
------------------------------------------------------------------------------

pi@octopi:~ $ uname -a
Linux octopi 4.4.50-v7+ #970 SMP Mon Feb 20 19:18:29 GMT 2017 armv7l GNU/Linux

I guess we should also make sure that RC2 has a newer kernel - if one is available.

@guysoft
Copy link
Owner Author

guysoft commented Apr 13, 2017 via email

@foosel
Copy link
Collaborator

foosel commented Apr 13, 2017

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.

@foosel
Copy link
Collaborator

foosel commented Apr 18, 2017

New image is out, short summary of findings:

I suggest building RC2 against that new image.

@guysoft
Copy link
Owner Author

guysoft commented Apr 22, 2017

@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
MD5 - 0bb3aa2033e09fb0e59764fdb57f9d8b

Should we make RC2 out of this?

@John-Mc
Copy link

John-Mc commented Apr 22, 2017

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).

@guysoft
Copy link
Owner Author

guysoft commented Apr 22, 2017

@John-Mc Fresh image. You can move most of your OctoPrint preferences between images.

@foosel
Copy link
Collaborator

foosel commented Apr 27, 2017

@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.

@shane84948
Copy link

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
raspistill Camera App v1.3.11
Width 3280, Height 2464, quality 85, filename test.jpg
Time delay 5000, Raw no
Thumbnail enabled Yes, width 64, height 48, quality 35
Link to latest frame enabled no
Full resolution preview No
Capture method : Single capture
Preview Yes, Full screen Yes
Preview window 0,0,1024,768
Opacity 255
Sharpness 0, Contrast 0, Brightness 50
Saturation 0, ISO 0, Video Stabilisation No, Exposure compensation 0
Exposure Mode 'auto', AWB Mode 'auto', Image Effect 'none'
Metering Mode 'average', Colour Effect Enabled No with U = 128, V = 128
Rotation 0, hflip No, vflip No
ROI x 0.000000, y 0.000000, w 1.000000 h 1.000000
mmal: mmal_vc_component_enable: failed to enable component: ENOSPC
mmal: camera component couldn't be enabled
mmal: main: Failed to create camera component
mmal: Failed to run camera app. Please check for firmware ``updates

@nophead
Copy link

nophead commented Apr 29, 2017

I think you will always get that error with raspistill on OctoPi because the camera will be already used by mjpg-streamer.

@dookie2000ca
Copy link

The release from a week ago is working great on my RPi 3 with my D300VS printer and the obligatory Logitech C270.
Wireless performance is much improved.

@John-Mc
Copy link

John-Mc commented Jun 2, 2017

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.

@Penfold81
Copy link

Penfold81 commented Jun 2, 2017 via email

@John-Mc
Copy link

John-Mc commented Jun 2, 2017

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.

@guysoft
Copy link
Owner Author

guysoft commented Jun 18, 2017

Please use RC2 at #367

@guysoft guysoft closed this as completed Jun 18, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants