Hi Tom,
After uncommenting the line 394 I can use jumbo frames from aravisGigE.
Thank you for the prompt reply!
Cheers,
Hinko
On 07/21/2016 10:57 AM, [email protected] wrote:
Hi,
That is a bit odd, I would have expected setting the packet size with the generic parameter set to work. I'm not sure if it needs to be done before the arvStream is created though. I haven't tested the driver with jumbo frames, but I did leave some commented out code in there that sets it up.
in aravisGigE/aravisGigEApp/src/araviscamera.cpp:
391 // Make standard size packets
392 arv_gv_device_set_packet_size(ARV_GV_DEVICE(this->device), ARV_GV_DEVICE_GVSP_PACKET_SIZE_DEFAULT);
393 // Uncomment this line to set jumbo packets
394 // arv_gv_device_set_packet_size(ARV_GV_DEVICE(this->device), 9000);
Comment out line 392 and uncomment line 394 and see if that helps...
Thanks,
Tom Cobb
-----Original Message-----
From: [email protected] [mailto:tech-talk-
[email protected]] On Behalf Of Hinxx
Sent: 21 July 2016 09:49
To: EPICS Tech-Talk
Subject: aravisGigE jumbo frame support
Hi all,
I'm trying to set MTU to 9000 (jumbo frames) when using Basler acA2000
GigE camera with aravigGigE AD module in GIT.
Under Linux I've set network MTU to 9000. Then I used the arv-tool-0.4
tool to set the camera MTU to 9000.
hinkokocevar@hinkocmbp:~$ arv-tool-0.4 control GevSCPSPacketSize
Basler-21729661
GevSCPSPacketSize = 1500 (min:220;max:16404)
hinkokocevar@hinkocmbp:~$ arv-tool-0.4 control GevSCPSPacketSize=9000
Basler-21729661
GevSCPSPacketSize = 9000 (min:220;max:16404)
hinkokocevar@hinkocmbp:~$ arv-tool-0.4 control GevSCPSPacketSize
Basler-21729661
GevSCPSPacketSize = 9000 (min:220;max:16404)
I can acquire images using arv-camera-test from the aravis package and
the output suggests that MTU 9000 is respected:
hinkokocevar@hinkocmbp:~$ arv-camera-test
Looking for the first available camera
(lt-arv-camera-test:13489): GLib-GIO-CRITICAL **:
g_inet_address_new_from_string: assertion 'string != NULL' failed
vendor name = Basler
model name = acA2000-50gmNIR
device id = 21729661
image width = 2048
image height = 1080
horizontal binning = 1
vertical binning = 1
payload = 2211840 bytes
exposure = 0 µs
gain = 36 dB
gv n_stream channels = 1
gv current channel = 0
gv packet delay = 0 ns
gv packet size = 9000 bytes
Frame rate = 40 Hz
Frame rate = 24 Hz
Frame rate = 24 Hz
Frame rate = 24 Hz
Frame rate = 25 Hz
Under aravisGigE I'm using generated feature OPI to access the
13ARV1:cam1:GevSCPSPacketSiz PV that initially holds 1500. Setting it to
9000 works, and I can confirm with arv-tool-0.4 at this point that
camera is using MTU 9000.
When stating the acquisition IOC console is flooded with messages:
Bad frame status: 2 size: 2211840
Bad frame status: 2 size: 2211840
Bad frame status: 2 size: 2211840
Bad frame status: 2 size: 2211840
Bad frame status: 2 size: 2211840
Bad frame status: 2 size: 2211840
Any hints on what might be the problem?
Thank you,
Hinko
- Replies:
- Re: aravisGigE jumbo frame support Hinxx
- References:
- aravisGigE jumbo frame support Hinxx
- RE: aravisGigE jumbo frame support tom.cobb
- Navigate by Date:
- Prev:
Re: How to configurate MCA for Octave Eric Norum
- Next:
RE: CARS:Modbus - function 06 (write single register) issue Nick Levchenko
- 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: aravisGigE jumbo frame support tom.cobb
- Next:
Re: aravisGigE jumbo frame support Hinxx
- 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
|