Hello Mark,
You are right one more time.
I changed the system buffer settings to:
net.core.rmem_max=12582912
net.core.rmem_default=12582912
and also changed RX Ring parameters to:
Pre-set maximums:
RX: 4096
RX Mini: 0
RX Jumbo: 2048
TX: 4096
Current hardware settings:
RX: 4096
RX Mini: 0
RX Jumbo: 128
TX: 512
Now I can ran 4 cameras simultaneously at full frame (1288x964) with
package delay of 400 us at 1 fps ( that is enough for us). As you have
mentioned, this is a better setup.
Thank you.
Nilson
On 21.02.19 13:44, Mark Rivers wrote:
I'm just curious if you tried changing the Linux system buffer settings? If you do that then I think you should be able to run all 3 cameras with the default 400 microsecond packet delay, and not have to worry about frame rates in the future (limited of course by the total shared GigE bandwidth available).
Mark
________________________________
From: [email protected] <[email protected]> on behalf of Nilson Pereira via Tech-talk <[email protected]>
Sent: Thursday, February 21, 2019 2:20 AM
To: [email protected]
Subject: Re: Point Grey GigE Blackfly conflict
Hello there,
I finally had the time to test different settings for the multiple GigE cameras and what really made the difference was the "GigE Packet Delay" settings. Since our frame rate is around 1 fps, I could push the packet delay to 5000 (in microseconds I believe) on all 3 cameras and now all cameras work simultaneously.
If I have to push a higher frame rate, I believe this delay have to be better calculated, but for now it fulfills my requirements.
Thank you all for the support.
Best,
Nilson
On 08.02.19 09:16, Nilson Pereira via Tech-talk wrote:
Hi,
Answering Kazimierz question, I am running IOCs on a Linux Ubuntu 16.04 virtual machine on our server.
The cameras are being used right now and I cannot test the suggest tuning of the network and camera parameters. I will post my results as soon as I get them done.
For now, moving one of the cameras IOC to another virtual machine did the trick, but now I am interested to find out If I can make them work from a single machine. I will report back.
Thank you all for suggestions and shared info.
Nilson
On 07.02.19 18:15, Gofron, Kazimierz wrote:
Hi Nilson,
What OS are you running Point Gray camera on? If it is Windows, then it is an intrinsic issue of the OS to run more than 1 camera, not related to network tuning, but Windows itself.
Kazimierz
Date: Thu, 7 Feb 2019 10:17:19 +0100
From: Nilson Pereira <[email protected]<mailto:[email protected]>>
To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>
Subject: Point Grey GigE Blackfly conflict
Message-ID: <[email protected]<[email protected]">mailto:[email protected]>>
Content-Type: text/plain; charset="utf-8"; format=flowed
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
________________________________
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
________________________________
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
________________________________
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
- References:
- RE: Point Grey GigE Blackfly conflict Gofron, Kazimierz via Tech-talk
- Re: Point Grey GigE Blackfly conflict Nilson Pereira via Tech-talk
- Re: Point Grey GigE Blackfly conflict Nilson Pereira via Tech-talk
- Re: Point Grey GigE Blackfly conflict Mark Rivers via Tech-talk
- Navigate by Date:
- Prev:
Re: Pro-Dex Oregon Micro Systems EPICS hardware support Heinz Junkes via Tech-talk
- Next:
Re: GNU Screen or procServ on ARM? 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
<2019>
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: Point Grey GigE Blackfly conflict Mark Rivers 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
<2019>
2020
2021
2022
2023
2024
|