| 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 <2025> | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 <2025> |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Question About ADEuresys XML File Support for the EPICS IOC |
| From: | "Kim, Kuktae via Tech-talk" <tech-talk at aps.anl.gov> |
| To: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
| Date: | Tue, 25 Mar 2025 00:03:33 +0000 |
|
Hello,
I am currently developing an EPICS IOC for the AXIS-SXRF-60 camera and the Euresys Coaxlink CXP-12 Quad Frame Grabber.
Thanks to ADGenICam and ADEuresys, I’ve been able to save a significant amount of time and effort.
Using the Euresys gentl utility, I extracted the XML files for both the camera and the frame grabber as below:
$ gentl xml
$ ls
6060CXP.xml
Euresys_Coaxlink_TLDataStream_25_02_0.xml
Euresys_Coaxlink_TLDevice_25_02_0.xml
Euresys_Coaxlink_TLInterface_25_02_0.xml
Euresys_Coaxlink_TLSystem_25_02_0.xml
Next, I used the Python scripts in ADGenICam to generate the EPICS database files and OPI screens from the camera’s XML file. These were saved in:
I’d like to know if a similar process can be applied to ADEuresys using the XML files from the Euresys frame grabber.
I created the EPICS database template and OPI screens and placed them in "/ADEuresys/EuresysApp/Db" and "/ADEuresys/EuresysApp/op/edl."
However, when I launched the GUI, most of the PVs displayed zero or N.A as below:
 
If I can use the database template and GUI in ADEuresys, it would be helpful for troubleshooting and diagnostics.
Does anyone know if ADEuresys has plans to support this in the same way as ADGenICam?
Thank you for your help!
Best regards,
Kuktae
|