headers
Schorsch Stefan Thomas | 1 Feb 2010 12:03
Picon

Re: Camera not recognized

Hi everybody,

first I would like to thank you for your support and hints (and special
thanks to Vadim Frolov from KIT!).
Just for the future in the case that somebody has a similar problem:
Using gscanbus I figured out that the
Leica camera DFC290 is not IIDC compatible.
There is a windows API available, however it is already compiled (-->
closed source) so the interface commands are not visible.
Funny by the way: Even the official TWAIN driver has no "set flash
option" etc, so you have to write the code by yourself or stick to
closed third party software (in our case the software has some major
issues as well). We now ended up using "AutoHotKey" to simulate
userinput...
If I find the time to modify libdc manually, I will of course let you
know (I wonder if there are any other Leica DFC-users out there?)

Best wishes,

Stefan

-----Original Message-----
From: Nico Stuurman [mailto:nico@...] 
Sent: Mittwoch, 27. Januar 2010 16:40
To: libdc1394-devel
Subject: Re: [libdc] Camera not recognized

>  My name is Stefan and I am currently trying, within the scope of my 
> PhD project, to install a Leica camera to work with a Linux server.
>
(Continue reading)

Permalink | Reply | 3 comments |
headers
Peter Antoniac | 2 Feb 2010 13:22
X-Face
Picon

Re: Camera not recognized

On Monday 01 February 2010 13:03:55 Schorsch Stefan Thomas wrote:
[CUT]
> Leica camera DFC290 is not IIDC compatible.
[CUT]
> If I find the time to modify libdc manually, I will of course let you
> know (I wonder if there are any other Leica DFC-users out there?)

Well, although we like contributions to the code, please be advised that 
libdc1394 is only for IIDC capable cameras.

Cheers,
Peter

------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
Permalink | Reply | 0 comments |
headers
Damir Anicic | 10 Feb 2010 08:53
Picon
Favicon

Re: Dual- & Quad-Core problems

Hi again,

It seems that I have the solution for my Dual/Quad- core problems.

I followed the suggestion of one of you (Balazs, vagvoba@...)
and obtained better PCIe card.
Now I have a Point Grey card
      FirePRO OHCI IEEE-1394b PCI Express x1 host adapter, dual 
bus/chip, 2 port

lspci reports it as 2 cards:

     04:00.0 FireWire (IEEE 1394): Agere Systems FW643 PCI Express1394b 
Controller (PHY/Link) (rev 06)
     05:00.0 FireWire (IEEE 1394): Agere Systems FW643 PCI Express1394b 
Controller (PHY/Link) (rev 06)

The images are not garbled any more, I get over 60 MB/s.

! But, there seems to be another problem:

After shutting down and booting the PC again (not reboot, but power-off, 
power-on)
everything gets initialized without a single error reported, the image 
acquisition runs
with expected frame rate, but I see only completely black images.
The coriander sees only black images, too.
If I stop my 1394-application, disconnect the camera, connect it again, 
start the 1394-application,
then it works again ???
(Continue reading)

Permalink | Reply | 7 comments |
headers
Samuel Audet | 10 Feb 2010 10:10
Picon

Re: Dual- & Quad-Core problems

On 2010-02-10 16:53, Damir Anicic wrote:
> After shutting down and booting the PC again (not reboot, but power-off,
> power-on)
> everything gets initialized without a single error reported, the image
> acquisition runs
> with expected frame rate, but I see only completely black images.
> The coriander sees only black images, too.
> If I stop my 1394-application, disconnect the camera, connect it again,
> start the 1394-application,
> then it works again ???

What happens if you do a camera reset in Coriander? It should have the 
same effect as repluging the device...

Samuel

------------------------------------------------------------------------------
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
Permalink | Reply | 6 comments |
headers
Damir Anicic | 10 Feb 2010 16:22
Picon
Favicon

Re: Dual- & Quad-Core problems

Small correction, black images do not happen in 100% cases after power-off.
Sometimes it works fine (but rare).

Black images can not be reset with coriander->Reset,
neither with dc1394_camera_reset() from my application (I do that on 
program start-up)

------------------------------------------------------------------------------
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
Permalink | Reply | 5 comments |
headers
Stefan Richter | 10 Feb 2010 17:52
Picon

Re: Dual- & Quad-Core problems

Damir Anicic wrote:
> Small correction, black images do not happen in 100% cases after power-off.
> Sometimes it works fine (but rare).
> 
> Black images can not be reset with coriander->Reset,
> neither with dc1394_camera_reset() from my application (I do that on 
> program start-up)

What if you cold-boot with mem=2G added as argument on the boot loader's
kernel command line?
--

-- 
Stefan Richter
-=====-==-=- --=- -=-=-
http://arcgraph.de/sr/

------------------------------------------------------------------------------
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
Permalink | Reply | 4 comments |
headers
Damir Anicic | 11 Feb 2010 12:27
Picon
Favicon

Re: Dual- & Quad-Core problems

Well, I did not try with mem=2G boot option,
but swapped the firewire cables .

I have presently 2 cameras, one COLOR and one B&W, both from Point Grey.

The COLOR one was connected with 3m cable,
B&W one with 0.5m cable,
and I got that black-images trouble, on COLOR camera only.
Camera-rest (with coriander or in my app) or dc1394_reset_bus did not help,
but disconnecting/reconnecting camera always helped.

Now, the COLOR one is on shorter cable,
B&W on longer,
and I did not get any problems (cold-booted 7 times - allways works).

It must be a combination of cable length + camera type.

It seems that firewire cabling is quite sensitive.

Sorry for troubling you.

Damir

------------------------------------------------------------------------------
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
Permalink | Reply | 3 comments |
headers
Andrew Roth | 11 Feb 2010 15:31
Picon

Ladybug2: Bus Error

libdc1394-2.1.2 compiled and installed correctly on Mac OS X 10.5.8  
(13" MBPro), when I run ./ladybug, it detects the camera/compressor,  
but then after throwing what appears to be a standard libdc warning  
(packets/515) it just says "Bus error" and exits.  There's also a  
Crashlog printed to the console.  I'm only posting the most relevant  
information.  At first glance it looks to be a problem with writing a  
file.

Exception Type:  EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000038
Crashed Thread:  0

Thread 0 Crashed:
0   libSystem.B.dylib             	0x9479bc03 flockfile + 22
1   libSystem.B.dylib             	0x947b881e fwrite$UNIX2003 + 86
2   ladybug                       	0x00001d79 main + 1593 (ladybug.c: 
132)
3   ladybug                       	0x00001706 start + 54

Could use some insight as to why this is happening.  I can't track  
down where the error is coming from.

Andrew

------------------------------------------------------------------------------
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
Permalink | Reply | 0 comments |
headers
Stefan Richter | 11 Feb 2010 17:56
Picon

Re: Dual- & Quad-Core problems

Damir Anicic wrote:
> The COLOR one was connected with 3m cable,
> B&W one with 0.5m cable,
> and I got that black-images trouble, on COLOR camera only.
> Camera-rest (with coriander or in my app) or dc1394_reset_bus did not help,
> but disconnecting/reconnecting camera always helped.
> 
> 
> Now, the COLOR one is on shorter cable,
> B&W on longer,
> and I did not get any problems (cold-booted 7 times - allways works).
> 
> It must be a combination of cable length + camera type.
> 
> It seems that firewire cabling is quite sensitive.

Cables with the usual 4- or 6- or 9-pin FireWire plugs can be 4.5 meters
(15 feet) long if they are properly built.  But the devices and
controller boards also should have a sane PCB layout, with short traces
of equal length between PHY chip and each connector pin, otherwise even
the best cables might give underwhelming results.  In these regards,
even FireWire 400 seems less forgiving than e.g. USB 2.0.  (Or maybe
it's just that people are more used to stability issues with USB than
they are with FireWire.)
--

-- 
Stefan Richter
-=====-==-=- --=- -=-==
http://arcgraph.de/sr/

------------------------------------------------------------------------------
(Continue reading)

Permalink | Reply | 2 comments |

Gmane