You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is not a duplicate. Before opening a new issue, please search existing issues.
This issue is not a question, feature request, or anything other than a bug report directly related to this project.
Description
Hi,
Does anyone have an issue where the ZED camera is not recognized until the camera is unplugged and plugged back in when you turn on the jetson nano 2gb, this is making it difficult to create daemons to run the camera as soon as the jetson nano starts, I also have to run the explorer sometimes first.. At first I thought it was perhaps the USB power management, but I'm not sure any ideas?
This seems to be recurring every time I start the Nano.
Thanks for any advice.
Steps to Reproduce
...
Expected Result
It to work as soon as you plug it in
Actual Result
it dont unless replugged in
ZED Camera model
ZED
Environment
Ubuntu 20
Jetson Nano 2gb
Anything else?
No response
The text was updated successfully, but these errors were encountered:
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment otherwise it will be automatically closed in 5 days
Preliminary Checks
Description
Hi,
Does anyone have an issue where the ZED camera is not recognized until the camera is unplugged and plugged back in when you turn on the jetson nano 2gb, this is making it difficult to create daemons to run the camera as soon as the jetson nano starts, I also have to run the explorer sometimes first.. At first I thought it was perhaps the USB power management, but I'm not sure any ideas?
This seems to be recurring every time I start the Nano.
Thanks for any advice.
Steps to Reproduce
...
Expected Result
It to work as soon as you plug it in
Actual Result
it dont unless replugged in
ZED Camera model
ZED
Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: