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
Jupyter fails to initialize camera...most of the times #35
Comments
I also have this problem,hope someone can solve this problem. |
Hi All, As a quick check, could you try calling the following from a terminal before executing the code? sudo systemctl restart nvargus-daemon We believe occasionally the camera daemon enters a bad state from not shutting down properly. Please let me know if this resolves your issue. We would also like to better understand the context that this occurs in. Could you all share the steps (from power on) that may be taken to reproduce the issue? For example,
This will help me reproduce the issue. Also, when you run into the issue, it's possible the error is contained in the camera daemon or jupyter service log files. Could you call the following after you encounter the error. journalctl -u jetbot_jupyter >> jetbot_jupyter_log.txt
journalctl -u nvargus-daemon >> nvargus_daemon_log.txt This will store the logs in Please let me know if you have any questions! Sorry for the trouble, I will also work on reproducing myself, but any additional information you can provide will be very helpful to us and other JetBot users! Best, |
I'm getting these errors especially when attempting to run the object_following/live_demp.ipynb I've followed your directions and have created the log files in the attached zip file. |
I have the same problem. |
same here |
Same here as well. The logs look identical. |
|
Hi walros007, glad to hear you've got that part working! Please let me know if you encounter further issues. Still, since multiple people have encountered this, there may be another underlying issue (or we should clarify the Camera connection in hardware setup). We're looking into it and hope to get back ASAP. Any additional information is helpful and appreciated! Thanks! |
I dug a little more into this. While I always get the logs indicating an array access out of bounds from the nvargus_daemon(see gizmohd logs), the camera sometimes works. If it does not, then I restart the netbook kernel and the daemon until it works. |
I didn't see camera working with attach log. Any idea? |
Hi John,
many thanks for your reply.
i have one more question: How can i install OpenCV 3.4 on my nano?
Many thanks,
Walter
…On Fri, 26 Apr 2019 at 18:30, John ***@***.***> wrote:
Hi walros007, glad to hear you've got that part working! Please let me
know if you encounter further issues.
Still, since multiple people have encountered this, there may be another
underlying issue (or we should clarify the Camera connection in hardware
setup). We're looking into it and hope to get back ASAP.
Any additional information is helpful and appreciated!
Thanks!
John
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#35 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ALNXDOETZ37LQTQ4H4QGUD3PSOUBVANCNFSM4HF3R63Q>
.
|
Any luck with this issue? |
I replaced the camera and it works ok so it seems in my case something was wrong with the camera (or the connection cable.) |
solved by running the cmd:
|
I tried doing the daemon restart and it's still not working for me....however, I tested the camera directly on the nano and it does work. |
I have assembled my jetbot with all the recommended hardware, including a Raspberry Pi Camera V2.
The jetbot works and I have been able to follow the examples provided. Unfortunately, most of the times the camera is needed, the notebook fails to activate it. The instruction that creates trouble is "camera = Camera.instance()". When I try to run this cell, jupyter enters Busy mode and never proceeds. This is true most of the times. Sometimes the instance is created successfully and I am able to proceed. This is also true after a fresh reboot.
Any suggestions as to what might be wrong?
The text was updated successfully, but these errors were encountered: