Emmanuel Pacaud

> also: as I was looking around the arv_gc_port_write code, I was wondering if line 177 of the write register section --value = GUINT32_FROM_BE (value); -- should be GUINT32_TO_BE? Seems...

There is no reason for access to DeviceLinkThroughput feature to be limited to USB3 device, and even less to Ximea devices. We should implement some helpers around this features, and...

Hi Joris, Thanks a lot for the detailed analysis of the issue. > It seems like this is a bug in the PtGrey firmware, not in Aravis. However, I can't...

Hi Joris. I have pushed your fix to master. As I've said in the commit entry, it seems not only the resent packets may have wrong packet id, but also...

For the record, here are the commands I'm using in order to generate traffic on the ethernet link: Aravis host: ``` iperf -s ``` Second host: ``` iperf -t 3600...

It looks like https://github.com/AravisProject/aravis/commit/a31df1206d34a30ad4ef5e5a1bfc027ee4e23728 doesn't fix the issue, so my guess about a bogus frame id is probably wrong, unless the fix itself is wrong.

Hi Ryan, Aravis being developed by reverse engineering, there is surely part of the code that is not correct with respect to the standard. The different transfer sizes set by...

> Aravis being developed by reverse engineering More correctly, Aravis is developed without using the A3 standard documents. But we use other sources of informations, like the wireshark dissector code,...

Hi, > Failed to read the current device configuration: GigEVision read_memory error (invalid-access) Aravis tried to read a feature not available on your device. Could you rerun `arv-camera-test` with `--debug=3`...

> `--debug=3` throws `Invalid debug selection`. Sorry, it is `--debug=all:3`