Experimental Physics and
Industrial Control System

<[email protected]> · Thu, 21 Jul 2016 08:57:25 +0000

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
> 

-- 
This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. 
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System