[GEM-dev] [ pd-gem-Bugs-3177361 ] no images with FW camera

SourceForge.net noreply at sourceforge.net
Fri Feb 11 12:25:33 CET 2011


Bugs item #3177361, was opened at 2011-02-10 14:02
Message generated for change (Comment added) made by nusmuk
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3177361&group_id=64325

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Pixes (pix_ objects)
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Cyrille Henry (nusmuk)
Assigned to: Nobody/Anonymous (nobody)
Summary: no images with FW camera

Initial Comment:
hello,
with Gem svn, ubuntu 10.04 (kernell 2.6.32), and a guppy pro (from AVT) connected with FW800, i can't have images.
(same result with a stingray from AVT)
the camera create a device /dev/raw1394 and /dev/video1394/0 
i've got video plugin dv4l and dc1394.

coriender can grab images without any problem.

i don't know if it's related, but when creating pix_video object, i've got an error in the terminal : 
libdc1394 error: Error: Failed to allocate iso bandwidth
libdc1394 error: Error: Failed to setup DMA capture 


----------------------------------------------------------------------

>Comment By: Cyrille Henry (nusmuk)
Date: 2011-02-11 11:25

Message:
ok, i find the solution.
adding : 
dc1394_video_set_operation_mode(m_dccamera,DC1394_OPERATION_MODE_1394B);
before setting speed to 800 solve the problem.
so i've go an image. i don't know to make this to work with both FW400 and
FW800 device...

i still have a small problem : the device is not properly closed. after
quitting pd, i have to unpluged it if i want to use it again. (the green
led is blinking after closing pd, just like when grabbing is on).


----------------------------------------------------------------------

Comment By: Cyrille Henry (nusmuk)
Date: 2011-02-11 10:56

Message:
if i change line 269 of file videoDC1394.cpp
from   
dc1394speed_t speed=DC1394_ISO_SPEED_400;
to 
  dc1394speed_t speed=DC1394_ISO_SPEED_800;
iv've got more information about why this speed can't be allocated in the
terminal : 

libdc1394 error: An ISO speed >400Mbps was requested while the camera is
in LEGACY mode. Please set the operation mode to OPERATION_MODE_1394B
before asking for 1394b ISO speeds
libdc1394 error: Error: Failed to allocate iso bandwidth
libdc1394 error: Error: Failed to setup DMA capture

i just don't know how to do that. any help is apreciated in order to make
this work for this camera.


----------------------------------------------------------------------

Comment By: Cyrille Henry (nusmuk)
Date: 2011-02-10 15:08

Message:
well, i did not have other cam connected when i tried this, so pix_video
tried all backend at the initialization.
so, i now have a v4l device on the computer.
when creating pix_video : no messages regarding 1394.
(only a message that say pix_video open a v4l2 device).

sending driver dc1394 gives in the terminal : 
libdc1394 error: Error: Failed to allocate iso bandwidth
libdc1394 error: Error: Failed to setup DMA capture 
and in pd log : 
error videoDC1394: Generic failure: failed to enumerate

then, sending device /dev/raw1394 did not change anything.

if i do the other order : 
recreate pix_video, sending device /dev/raw1394, i've got an error that
say V4L can not open this device.
then sending driver dc1394 print nothing.

the camera is in FW800, the computer have only a FW800 port...

----------------------------------------------------------------------

Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2011-02-10 14:15

Message:
this happens as soon as you create the [pix_video] object?

Gem tries to set the bandwidth to 400 when it _open_s the device, but
should fall back to whatever the device gives, if FW400 is not supported.
but if the problem already occurs when creating [pix_video] (that is: when
initializing the dc1394 infrastructure), it will never reach that...

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=507079&aid=3177361&group_id=64325



More information about the GEM-dev mailing list