Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <20192020  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <20192020 
<== Date ==> <== Thread ==>

Subject: Re: Point Grey GigE Blackfly conflict
From: Jörn Dreyer via Tech-talk <tech-talk@aps.anl.gov>
To: tech-talk@aps.anl.gov, Nilson Pereira <nilson.pereira@helmholtz-berlin.de>
Date: Thu, 07 Feb 2019 11:27:05 +0100
Hi Nilson,

I don't have experience with the PointGrey GigE cameras, but with Basler 
cameras. These cameras have parameters to tune the network settings.

What happens if a trigger is received by a camera:

The sensor is exposed according to the settings. After this time has elapsed, 
the sensor is read out and the data streamed to the network in packages of a 
defined size. Normally 1500 Bytes (MTU) as fast as possible. As this is done 
using UDP, there is no collision detection or re-sending of lost packets.

BUT:

You can tune a delay, that the camera will wait after the exposure is finished 
until it sends its first packet

AND

you can tune a parameter defining the time between two packets send by a 
camera.

If you configure these parameters correctly, no data collisions of any amount 
of cameras (up to 24 as stated by Basler) will occur. There PYLON software can 
configure this settings aromatically. Check for the PointGrey software if it 
can do the same.

Hope this information will help you.

Regards,

Jörn

Am Donnerstag, 7. Februar 2019, 10:17:19 CET schrieb Nilson Pereira via Tech-
talk:
> Hello community,
> 
> I have 3 cameras (Point Grey GigE Blackfly) that I want to use
> simultaneously at a very low framerate (1fps) for BPM purposes.
> 
> Each camera has its own IOC and they run perfectly one at a time.
> However, when running simultaneously, always 2 cameras conflict with
> each other and not necessary the same two cameras. During conflict, the
> IOC shows an error about frame inconsistency on both affected cameras. I
> have a gigabit network port on both switch and server, and the port is
> far from saturation.
> 
> Does anyone have experience with GigE cameras and have seem this type of
> problem? Is this a protocol issue since it happens even with the
> original (Flycap2) software ?
> 
> I appreciate any shared experience with problems with GigE cameras that
> could give a hint on why this is happening.
> 
> Best,
> 
> Nilson
> 
> 
> ________________________________
> 
> Helmholtz-Zentrum Berlin für Materialien und Energie GmbH
> 
> Mitglied der Hermann von Helmholtz-Gemeinschaft Deutscher Forschungszentren
> e.V.
> 
> Aufsichtsrat: Vorsitzender Dr. Karl Eugen Huthmacher, stv. Vorsitzende Dr.
> Jutta Koch-Unterseher Geschäftsführung: Prof. Dr. Bernd Rech
> (kommissarisch), Thomas Frederking
> 
> Sitz Berlin, AG Charlottenburg, 89 HRB 5583
> 
> Postadresse:
> Hahn-Meitner-Platz 1
> D-14109 Berlin




Replies:
Re: Point Grey GigE Blackfly conflict Mark Rivers via Tech-talk
References:
Point Grey GigE Blackfly conflict Nilson Pereira via Tech-talk

Navigate by Date:
Prev: Re: Point Grey GigE Blackfly conflict Wayne Lewis via Tech-talk
Next: How to read and Write PVs in C# shakeel ahmad via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <20192020 
Navigate by Thread:
Prev: Re: Point Grey GigE Blackfly conflict Wayne Lewis via Tech-talk
Next: Re: Point Grey GigE Blackfly conflict Mark Rivers via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <20192020 
ANJ, 07 Feb 2019 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·