<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">El 25/03/15 a las 03:26, Lihang Li
escribió:<br>
</div>
<blockquote
cite="mid:CAFBPn+O1NBu8tJWuPE62WxnCsVUfgH9FMv1RmrEvsa9hjt1Qrw@mail.gmail.com"
type="cite">
<div dir="ltr">So probably you should figure out, which camera
model are you using? Like UVC, IEEE-1394 or DV? Thus you can try
if it can fetch images using normal applications like `UVC
Viewer`.</div>
</blockquote>
<br>
<br>
As you can see in his posts is a UVC webcam:<br>
<br>
<br>
<div class="moz-cite-prefix">El 23/03/15 a las 22:42, shahsahil
escribió:<br>
</div>
<blockquote cite="mid:1427146961549-4642547.post@n4.nabble.com"
type="cite">
<pre wrap="">The output for sudo lsusb -v
screen.log
<a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="http://jderobot-developer-list.2315034.n4.nabble.com/file/n4642547/screen.log">http://jderobot-developer-list.2315034.n4.nabble.com/file/n4642547/screen.log</a>
The output for lsmod
screen1.log
<a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="http://jderobot-developer-list.2315034.n4.nabble.com/file/n4642547/screen1.log">http://jderobot-developer-list.2315034.n4.nabble.com/file/n4642547/screen1.log</a>
</pre>
</blockquote>
<br>
<br>
It's a good idea trying uvc viewer, but it's possible that the
problem is virtualization layer. The only way to prove this problem
is (we known that other applications shows a blank screen too)
trying with a native ubuntu install.<br>
<br>
<br>
<br>
<blockquote
cite="mid:CAFBPn+O1NBu8tJWuPE62WxnCsVUfgH9FMv1RmrEvsa9hjt1Qrw@mail.gmail.com"
type="cite">
<div dir="ltr"> Make sure you got a device in /dev/ and it is
working. Then pay attention to the config file you pass to
CameraServer, select the right device according to your camera
model.<br>
</div>
</blockquote>
<br>
<br>
If there is not a camera on 0 (/dev/video0) or another index
cameraserver will throw this error:<br>
<br>
redstar@oczstar:~/Documentos/jderobot/temp/JdeRobot/src/stable/components/cameraserver$
./cameraserver --Ice.Config=cameraserver.cfg<br>
Constructor CameraI -> CameraSrv.Camera.0.<br>
URI: 0<br>
HIGHGUI ERROR: V4L: index 0 is not correct!<br>
<br>
Sahil Shah didn't answer me about the dots... I don't know if the
server was printing the dots with the debug code that I suggested
him. That is a important point to know what would be the problem.<br>
<br>
I think that is very possible that the key are these lines:<br>
<div>select timeout</div>
<div>select timeout</div>
<div>select timeout</div>
<div>select timeout</div>
<br>
I think that the device is not serving frames as expected. My first
thought was (in my second post[1]) about interference with audio
layer, because it could be a composed USB device (video + audio).<br>
<br>
If it is the problem it could be solved disabling USB audio and/or
avoid bandwith (because virtualization) related problems [2]:<br>
<br>
echo -e "blacklist snd_usb_audio\n
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
uvcvideo timeout=10000 quirks=0x80 nodrop=1" >
/etc/modprobe.d/jderobot_workarround.conf<br>
<br>
This will disable audio and let the camera 10 seconds to initialize
(virtualized devices could take more time to start) and solve
bandwitd issues (UVC_QUIRK_FIX_BANDWIDTH quirk). You will need to
restart or type this:<br>
<br>
rmmod snd_usb_audio<br>
rmmod uvcvideo<br>
modprobe uvcvideo timeout=10000 quirks=0x80 nodrop=1<br>
<br>
Please Sahil, try this and tell me about it.<br>
<br>
Best regards.<br>
<br>
<br>
[1]:
<a class="moz-txt-link-freetext" href="http://gsyc.escet.urjc.es/pipermail/jde-developers/2015-March/003683.html">http://gsyc.escet.urjc.es/pipermail/jde-developers/2015-March/003683.html</a><br>
[2]: <a class="moz-txt-link-freetext" href="http://www.ideasonboard.org/uvc/faq/#faq7">http://www.ideasonboard.org/uvc/faq/#faq7</a><br>
</body>
</html>