RE: Areadetector driver for AVT-Marlin Firewire Camera on Windows

[Mark Rivers via Tech-talk <tech-talk at aps.anl.gov>]

Hi Sandeep,

 

Ø  XML files generated from Vimba viewer is incompatible.

 

Can you explain what you mean by that? 

-          Is the Vimba Viewer capable of saving the XML file from the camera?

-          Did that Firewire camera actually contain an XML file?

-          What do you mean by “incompatible”?  Did you get an error when you tried to use it with the Python scripts?

 

Mark

 

 

 

From: Malu, Sandeep Kumar (-,RAL,CLF) <sandeep-kumar.malu at stfc.ac.uk>
Sent: Friday, January 29, 2021 7:38 AM
To: Mark Rivers <rivers at cars.uchicago.edu>
Cc: tech-talk at aps.anl.gov
Subject: Re: Areadetector driver for AVT-Marlin Firewire Camera on Windows

 

Thanks Mark.

 

XML files generated from Vimba viewer is incompatible. I would give a quick try to ADFireWireWin to see if it still works.

 

Many Thanks 

Sandeep

 

Get Outlook for Android

---

From: Mark Rivers <rivers at cars.uchicago.edu>
Sent: Friday, January 29, 2021 6:58:26 PM
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,

1. 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.

2. 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.

3. 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

 

 

From: Tech-talk <tech-talk-bounces at aps.anl.gov> On Behalf Of Malu, Sandeep Kumar (-, RAL, CLF) via Tech-talk
Sent: Friday, January 29, 2021 7:13 AM
To: tech-talk at aps.anl.gov
Subject: Areadetector driver for AVT-Marlin Firewire Camera on Windows

 

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.

1. 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.
2. 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?
3. ADFireWireWin - Not tried yet. Does this works with the above model?

Many Thanks

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.