two "Protocol errors"

251 views
Skip to first unread message

Adam

unread,
Jan 27, 2014, 8:06:10 PM1/27/14
to pupil-...@googlegroups.com
Hi,

last week i made the first recordings with pupil.
but now, there appeared some problems. When i try to find the cams, the second cam won't be found.

the message is the following:

Code hier eingeben...esm@esm:~/pupil/pupil_src/capture$ python find_cameras.py
VIDIOC_QUERYMENU
: Invalid argument
VIDIOC_QUERYMENU
: Invalid argument
VIDIOC_QUERYMENU
: Invalid argument
VIDIOC_QUERYMENU
: Invalid argument
VIDIOC_QUERYMENU
: Invalid argument
VIDIOC_QUERYMENU
: Invalid argument
VIDIOC_QUERYMENU
: Invalid argument
VIDIOC_QUERYMENU
: Invalid argument
VIDIOC_QUERYMENU
: Invalid argument
VIDIOC_QUERYMENU
: Invalid argument
VIDIOC_QUERYMENU
: Invalid argument
VIDIOC_QUERYMENU
: Invalid argument
VIDIOC_QUERYMENU
: Invalid argument
VIDIOC_QUERYMENU
: Invalid argument
init
done
opengl support available
VIDIOC_QUERYMENU
: Invalid argument
VIDIOC_QUERYMENU
: Invalid argument
VIDIOC_QUERYMENU
: Invalid argument
VIDIOC_QUERYMENU
: Invalid argument
VIDIOC_QUERYMENU
: Invalid argument
VIDIOC_QUERYMENU
: Invalid argument
VIDIOC_QUERYMENU
: Invalid argument
VIDIOC_QUERYMENU
: Invalid argument
VIDIOC_QUERYMENU
: Invalid argument
VIDIOC_QUERYMENU
: Invalid argument
VIDIOC_QUERYMENU
: Invalid argument
VIDIOC_QUERYMENU
: Invalid argument
VIDIOC_QUERYMENU
: Invalid argument
VIDIOC_QUERYMENU
: Invalid argument
libv4l2
: error turning on stream: Protocol error
VIDIOC_STREAMON
: Protocol error


any idea how to fix it?? and why suddenly this appears?

greetings, and thanks for your efforts!!

adam

Adam

unread,
Jan 27, 2014, 8:07:30 PM1/27/14
to pupil-...@googlegroups.com
perhaps i should mention that pupil is running on ubuntu 12.10 64bit...

Moritz Kassner

unread,
Jan 28, 2014, 2:00:42 AM1/28/14
to pupil-...@googlegroups.com
Hi Adam,

I see you are using find_cameras.py. If this does not work for you with one camera, something with your version of opencv, v4l2 or the actual hardware must be wrong. 
find_cameras.py is such a simple script that I doubt the error lies there. 

"libv4l2: error turning on stream: Protocol error" is not the error associated with to little bandwidth. I m assuming that the problem lies somewhere else. 

I guess you already went though the ususal...

 - try pupil capture instead of find cameras.
 - reboot
- try different usb ports.
- try just the non working camera first.

let me know if any of this helps.

best,

m





--
You received this message because you are subscribed to the Google Groups "pupil-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pupil-discus...@googlegroups.com.
To post to this group, send email to pupil-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pupil-discuss/e31e4e6a-8596-4f23-8b03-7d0690880ec9%40googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

Adam

unread,
Feb 18, 2014, 5:33:03 PM2/18/14
to pupil-...@googlegroups.com, moritz...@googlemail.com
hi,

yep, i tried a lot of stuff...
well, reboot and using different usb ports doesn't help.

what can i do about

but now there is another error message when trying find_cameras.py:
HIGHGUI ERROR: V4L: index 1 is not correct!

and when running main.py this is the log:

Traceback (most recent call last):
 
File "main.py", line 139, in <module>
    main
()
 
File "main.py", line 132, in main
    world
(g_pool,world_src,world_size)
 
File "/home/esm/pupil/pupil_src/capture/world.py", line 106, in world
    cap
= autoCreateCapture(cap_src, cap_size,24)
 
File "/home/esm/pupil/pupil_src/shared_modules/uvc_capture/__init__.py", line 142, in autoCreateCapture
    cap
= Camera_Capture(src,size,fps)
 
File "/home/esm/pupil/pupil_src/shared_modules/uvc_capture/linux_video/__init__.py", line 13, in __init__
   
self.src_id = cam.src_id
AttributeError: 'int' object has no attribute 'src_id'


thank you for your help!!

best regards,
adam

Adam

unread,
Apr 28, 2014, 7:00:27 AM4/28/14
to pupil-...@googlegroups.com
hi,
for the case others have to deal with this error messages, just wanted to report my solution: use another pc...
it was a hardware problem, not a clue what exactly....

greetings,
adam

Am Dienstag, 28. Januar 2014 02:06:10 UTC+1 schrieb Adam:
Reply all
Reply to author
Forward
0 new messages