[ros-users] Videre STOC Problem

Antons Rebguns anton at email.arizona.edu
Sat Feb 12 18:20:58 UTC 2011


Patrick,

You could also try running the ROS driver videre_stereo_cam in
ua-ros-pkg. Just run roslaunch videre_stereo_cam videre.launch to run
the camera in stoc mode. I am not sure it's going to work since
neither coriander nor svs works, but you can give it a shot.

Anton

On Sat, Feb 12, 2011 at 11:03 AM, Patrick Goebel <patrick at pirobot.org> wrote:
> It occurred to me that I have an old digital video camera that uses
> Firewire.  So I installed kino, plugged in the camera to the same
> Firewire port I've been using with the STOC camera and presto, I am able
> to control the camera and capture some video.
>
> So I'm wondering if my problem is not having the Videre driver installed
> correctly.  In fact, I'm not even sure what installing the driver might
> mean beyond what I did in the beginning which was:  I unpacked the
> original SVS tgz file into /home/patrick/bin/svs.  Then:
>
> $ export LD_LIBRARY_PATH=/home/patrick/bin/svs/bin:$LD_LIBRARY_PATH
> $ cd /usr/lib
> $ sudo ln -s libraw1394.so.11.0.1 libraw1394.so.8
> $ sudo ldconfig
>
> Is there something else I need to do to make sure the STOC driver is
> being accessed?
>
> --patrick
>
>
>
> On 02/12/2011 09:10 AM, Patrick Goebel wrote:
>> Many thanks Anton and Jack!  Changing the permissions and group (video)
>> on /dev/raw1394 got me a little further but there is still a problem.
>> Coriander now comes up and shows "VIDERE_DESIGN MDS-STH" under the
>> Camera Select menu but the window is completely unresponsive--clicking
>> on tabs and buttons has no effect.  Typing Ctrl-C in the launching
>> terminal kills the coriander window but does not return the command
>> prompt and coriander is listed as a defunct process.  Also, trying to
>> run smallv simply hangs after issuing the command--no window ever
>> appears and neither Ctrl-C nor 'pkill -9 smallv' in another terminal can
>> kill it...
>>
>> Just to summarize:
>>
>> ls -l /dev/raw1394
>> crwxrwxrwx 1 root video 171, 0 2011-02-12 08:57 /dev/raw1394
>>
>> uid=1000(patrick) gid=1000(patrick)
>> groups=4(adm),6(disk),20(dialout),24(cdrom),44(video),46(plugdev),104(lpadmin),115(admin),120(sambashare),1000(patrick)
>>
>> ls -l /dev/video1394/
>> total 0
>> crwxrwxrwx+ 1 root video 171, 16 2011-02-12 08:57 0
>> crwxrwxrwx+ 1 root video 171, 17 2011-02-12 08:57 1
>>
>> Any other thoughts?
>>
>> --patrick
>>
>>
>> On 02/12/2011 08:46 AM, Antons Rebguns wrote:
>>> What I always have to do is set RW permissions on /dev/raw1394, I
>>> never had to touch /dev/video1394. After that everything usually works
>>> just fine.
>>>
>>> Anton
>>>
>>> On Sat, Feb 12, 2011 at 9:39 AM, Jack O'Quin<jack.oquin at gmail.com>   wrote:
>>>> On Sat, Feb 12, 2011 at 10:18 AM, Patrick Goebel<patrick at pirobot.org>   wrote:
>>>>
>>>>> I made sure I am a member of both the disk and video groups and I did a
>>>>> chmod 777 on dev/video1394/* so that ls -l dev/video1394/* gives:
>>>>>
>>>>> crwxrwxrwx+ 1 root video 171, 16 2011-02-12 07:59 0
>>>>> crwxrwxrwx+ 1 root video 171, 17 2011-02-12 07:59
>>>>
>>>> You probably need to do something similar for /dev/raw1394:
>>>>
>>>>    http://www.ros.org/wiki/camera1394/Troubleshooting#No_Bus_Access_Permissions
>>>> --
>>>>    joq
>>>> _______________________________________________
>>>> ros-users mailing list
>>>> ros-users at code.ros.org
>>>> https://code.ros.org/mailman/listinfo/ros-users
>>>>
>>> _______________________________________________
>>> ros-users mailing list
>>> ros-users at code.ros.org
>>> https://code.ros.org/mailman/listinfo/ros-users
>> _______________________________________________
>> ros-users mailing list
>> ros-users at code.ros.org
>> https://code.ros.org/mailman/listinfo/ros-users
> _______________________________________________
> ros-users mailing list
> ros-users at code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
>



More information about the ros-users mailing list