aravis icon indicating copy to clipboard operation
aravis copied to clipboard

New Infrared Technologies Ltd device support

Open multiflexi opened this issue 7 years ago • 11 comments

Hi, I am testing infrared camera Tachyon 16k from NIT. I tried latest Aravis release and also master branch but without success. I am attaching output of arv-test and camera features and screenshots or viewer and QArv. I was able to acquire image in 3rd party viewer. I think the issue is that Aravis does not figure out the resolution which is 128x128 and shows just 0 in arv-test. Any ideas?

arv-test.log cam_features.txt screenshot from 2018-05-31 12-18-02 screenshot from 2018-05-31 12-18-40

multiflexi avatar May 31 '18 10:05 multiflexi

Please attach the output of arv-camera-test -d all:3.

EmmanuelP avatar Jun 01 '18 18:06 EmmanuelP

I let it run for 30 min, I hope it is enough. arv-camera-test.log

multiflexi avatar Jun 04 '18 08:06 multiflexi

Is the issue evident from the log?

multiflexi avatar Jun 05 '18 16:06 multiflexi

Nope. The region seems to be correctly returned by arv-camera-test. Could you attach the output of:

arv-tool-0.6 control SensorHeight SensorWidth Width Height -d device:3,evaluator:3

EmmanuelP avatar Jun 06 '18 06:06 EmmanuelP

arv-tool.log Here you go.

multiflexi avatar Jun 06 '18 08:06 multiflexi

And the output of: arv-tool-0.6 features ?

EmmanuelP avatar Jun 06 '18 12:06 EmmanuelP

Sorry, I don't know what goes wrong. It will be hard for me to debug this issue without the device at hand. The reading of the acquisition region seems to work fine. May be the acquisition setup is not standard and should be adapted. The related code is in arvcamera.c.

EmmanuelP avatar Jun 06 '18 13:06 EmmanuelP

iport_ntx_gige_pt01_pb3ip01_128xg.xml.txt

I am now investigating what is wrong. Does Aravis require variables SensorWidth and SensorHeight in the XML file? According to Genicam SFNC they are recommended but not mandatory. When I compare the XML from camera and simulator which works, this is the difference I see: the camera XML is missing those 2 variables and has only WidthMax and HeightMax.

multiflexi avatar Jun 06 '18 15:06 multiflexi

Thanks for investigating this issue. SensorHeight and SensorWidth are not used by the viewer. I would recommend to try to debug with tests/arv-camera-test first. It is much more simpler to understand than arv-viewer with all that UI related code. As I said previously, my first bet would be a non standard acquisition setup sequence. In order to set a fixed framerate acquisition, a number of features must be set, and this is most of the time vendor dependent. Have a look at the camera documentation.

EmmanuelP avatar Jun 06 '18 16:06 EmmanuelP

It is a bit strange there is no TriggerMode and TriggerSelector features.

EmmanuelP avatar Jun 06 '18 16:06 EmmanuelP