Hi Mark,
XML configuration file generated from Vimba viewer has different format compared to XML file generated from arv-tool. Anyhow, I will give it a try by editing one of the existing template files & see how it goes.
Thanks
Sandeep
From: Mark Rivers <rivers at cars.uchicago.edu>
Sent: 29 January 2021 19:12
To: Malu, Sandeep Kumar (-,RAL,CLF) <sandeep-kumar.malu at stfc.ac.uk>
Cc: tech-talk at aps.anl.gov <tech-talk at aps.anl.gov>
Subject: RE: Areadetector driver for AVT-Marlin Firewire Camera on Windows
Hi Sandeep,
I thought a little harder about using ADVimba. So far ADVimba has only been used with GenICam cameras, which contain the XML file you mentioned. However, I don’t think the Firewire cameras (IEEE 1394a or 1394b) are GenICam compliant,
so they probably don’t have an XML file you can download. Firewire cameras have a fixed set of feature names that are specified in the IEEE standard. The Vimba SDK says it is supports IEEE 1394, so they are presumably using the same calls to write/read features
that they use for GenICam. That means you probably can use ADVimba, but you will need to manually create the .template file using the correct feature names, and manually create the OPI screens. This seems possible, but as I said previously it may be cheaper,
considering the developer’s time to do that, to just buy a new camera.
Mark
From: Tech-talk <tech-talk-bounces at aps.anl.gov>
On Behalf Of Mark Rivers via Tech-talk
Sent: Friday, January 29, 2021 7:28 AM
To: 'Malu, Sandeep Kumar (-,RAL,CLF)' <sandeep-kumar.malu at stfc.ac.uk>
Cc: tech-talk at aps.anl.gov
Subject: RE: Areadetector driver for AVT-Marlin Firewire Camera on Windows
Hi Sandeep,
- ADProsilica - Apparently, when I use "prosilicaConfig("$(PORT)",
5000698, 50, 0)" in st.cmd; the IOC crash. Somewhere I read ADprosilica has been tested only with gigE cameras.
ADProsilica only works with GigE cameras because the PvApi SDK that it uses only supports GigE.
- ADVimba - The IOC runs with "ADVimbaConfig("$(PORT)", "$(CAMERA_ID)", 0, 0, 0)" . But the template files it uses "dbLoadRecords("$(GENICAM_DB_FILE)",
"P=$(PREFIX),R=cam1:,PORT=$(PORT)")" can only be generated using arv-tools on Linux. (Downloading the XML files -
https://areadetector.github.io/master/ADGenICam/ADGenICam.html). Does someone has the XML configuration files for the said model?
I don’t think that aravis supports Firewire so I am not sure how you can get the XML file. You could ask Allied Vision to send it to you.
- ADFireWireWin - Not tried yet. Does this works with the above model?
That might work. As far as I know that driver has not been used in many years, so it may need some work. It relies on a library from Carnegie Mellon, and I don’t know if they support that anymore. Their Web page seems to have been
updated last in 2011, and only mentions Windows 7 not Windows 10.
It might be less expensive to replace that obsolete camera with a modern one with the same physical form factor if that is an option.
Mark
Hi
Which areadetector driver should be used to interface AVT(Allied Vision)-Marlin F033B
Firewire camera on Windows OS? I tried a few of them and below are my observations.
- ADProsilica - Apparently, when I use "prosilicaConfig("$(PORT)",
5000698, 50, 0)" in st.cmd; the IOC crash. Somewhere I read ADprosilica has been tested only with gigE cameras.
- ADVimba - The IOC runs with "ADVimbaConfig("$(PORT)", "$(CAMERA_ID)", 0, 0, 0)" . But the template files it uses "dbLoadRecords("$(GENICAM_DB_FILE)",
"P=$(PREFIX),R=cam1:,PORT=$(PORT)")" can only be generated using arv-tools on Linux. (Downloading the XML files -
https://areadetector.github.io/master/ADGenICam/ADGenICam.html). Does someone has the XML configuration files for the said model?
- ADFireWireWin - Not tried yet. Does this works with the above model?
Sandeep
This email and any attachments are intended solely for the use of the named recipients. If you are not the intended recipient you must not use, disclose, copy or distribute this email or any of its attachments and should notify
the sender immediately and delete this email from your system. UK Research and Innovation (UKRI) has taken every reasonable precaution to minimise risk of this email or any attachments containing viruses or malware but the recipient should carry out its own
virus and malware checks before opening the attachments. UKRI does not accept any liability for any losses or damages which the recipient may sustain due to presence of any viruses. Opinions, conclusions or other information in this message and attachments
that are not related directly to UKRI business are solely those of the author and do not represent the views of UKRI.
|