-
Notifications
You must be signed in to change notification settings - Fork 40
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
secondary camera file wasn't created #60
Comments
It's possible they are somehow detected as the same camera. They are both the same model. so does that mean I need to run the -noserial option? |
tried the -noserial option this didn't change anything. It didn't create the second camera file. |
What do you get with: |
SUBSYSTEM=="tty", ATTRS{serial}=="0700B016AF1E90C55AABAC1AF50020C3", SYMLINK+="o cto_EnderM3D" |
so just a few minutes ago cam2_EnderM3D showed up but I can't access it. EDIT: just did a status and noticed this..
so it has finally created the file but says access denied? |
I would just reboot the whole device. You can also try moving the USB port the camera is in. |
I have done that as well. I'll try again. I have rebooted multiple times, I have edited the udev rules, changed resolutions, modified/fixed the haproxy.cfg and changed camera names/ports. all come back to this in the end. |
It is not a problem with the script. It is doing what it is supposed to. This is a hardware issue and this is one of the reasons cameras will always be an experimental feature. |
I added a second usb camera. It never created the cam2_* file for me to use. I've done this addition a few times. Any thoughts?
/dev/cam2_* doesn't exist. I can see both of them listed by-id in the v4l folder at least. so I know they are working.
The text was updated successfully, but these errors were encountered: