Experimental Physics and
Industrial Control System

Hi Mark,

my epicsPrtEnvParams output

epicsPrtEnvParams
EPICS_CA_ADDR_LIST is undefined
EPICS_CA_CONN_TMO: 30.0
EPICS_CA_AUTO_ADDR_LIST: YES
EPICS_CA_REPEATER_PORT: 5065
EPICS_CA_SERVER_PORT: 5064
EPICS_CA_MAX_ARRAY_BYTES: 9999999999
EPICS_CA_MAX_SEARCH_PERIOD: 300.0
EPICS_CA_NAME_SERVERS is undefined
EPICS_CAS_INTF_ADDR_LIST is undefined
EPICS_CAS_IGNORE_ADDR_LIST is undefined
EPICS_CAS_AUTO_BEACON_ADDR_LIST is undefined
EPICS_CAS_BEACON_ADDR_LIST is undefined
EPICS_CAS_SERVER_PORT is undefined
EPICS_CA_BEACON_PERIOD: 15.0
EPICS_CAS_BEACON_PERIOD is undefined
EPICS_CAS_BEACON_PORT is undefined
EPICS_BUILD_COMPILER_CLASS: gcc
EPICS_BUILD_OS_CLASS: Linux
EPICS_BUILD_TARGET_ARCH: linux-x86_64
EPICS_TIMEZONE: CUS::360:031102:110402
EPICS_TS_NTP_INET is undefined
EPICS_IOC_LOG_PORT: 7004
EPICS_IOC_LOG_INET is undefined
EPICS_IOC_LOG_FILE_LIMIT: 1000000
EPICS_IOC_LOG_FILE_NAME is undefined
EPICS_IOC_LOG_FILE_COMMAND is undefined
EPICS_CMD_PROTO_PORT is undefined
EPICS_AR_PORT: 7002
IOCSH_PS1: epics>
IOCSH_HISTSIZE: 50

Now I put the addr list in the ioc boot file, and works fine...

One question, when the value is undefined (same condition was before), shouldn't IOC use the EPICS_CA_ADDR_LIST set in the bash?

Thanks

Regards

One possibility is that one of the scripts that is starting your areaDetector IOC is setting EPICS_CA_ADDR_LIST in such a way that the remote IOC is not reachable for that areaDetector IOC process.  That could explain why caget works for another process but not for the areaDetector IOC.

 

At the areaDetector IOC prompt type this command to see all of the CA settings:

 

epicsPrtEnvParams

 

areaDetector can read PVs from other IOCs with no problem.  The attribute files for my detectors are getting PVs from many IOCs.

 

Mark

 

 

 

From: Tech-talk <tech-talk-bounces at aps.anl.gov> On Behalf Of Douglas Araujo via Tech-talk
Sent: Monday, October 26, 2020 6:37 PM
To: tech-talk at aps.anl.gov
Subject: Read PV value Attributes XML

 

Hi,

I'm trying to set some attributes using XML, and I am had problem with some pvs.
Example XML file:

<?xml version="1.0" standalone="no" ?>

<!-- Attributes -->

<Attributes

    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";

    xsi:noNamespaceSchemaLocation="../../../../../ADCore/XML_schema/NDAttributes.xsd"

   >

    <Attribute name="NumExposures"       type="EPICS_PV"    source="CAT:S:cam1:NumExposures_RBV"       datatype="DBR_NATIVE"     description="Number of exposures manufacturer"/>

    <Attribute name="m1_velocity"        type="EPICS_PV"    source="CAT:S:m1.VELO"                 datatype="DBR_NATIVE"     description="Motor 1 Velocity"/>

    <Attribute name="photodiode"         type="EPICS_PV"    source="CAT:C:RIO03:0215B:ai1          datatype="DBR_NATIVE"     description="BIM01 - Photodiode"/>

</Attributes>

The two first lines and works fine. The first is a PV from simDetector IOC, (The same IOC where I'm using the HDF5Plugin  and using the XML file). The second is a motorRecord Simulated IOC, that is running in the same host that first ioc.
But, the last one, is returning the value "nan". This specific IOC that provide this PV is running in another host. However, I can read the value using caget:

douglas.araujo@cat-gui:/usr/local/epics/apps/config$ caget CAT:C:RIO03:9215B:ai1
CAT:C:RIO03:9215B:ai1          0.000247466

douglas.araujo@cat-gui:/usr/local/epics/apps/config$ cainfo CAT:C:RIO03:9215B:ai1
CAT:C:RIO03:9215B:ai1
    State:            connected
    Host:             s-cat-c-rio03.abtlus.org.br:5064
    Access:           read, write
    Native data type: DBF_DOUBLE
    Request type:     DBR_DOUBLE
    Element count:    1

I'm using the 3.3.1 ADCore Version.
I read the documentation and saw that this is a behavior when the pv is not connected. But my pv is connected. Need I set some parameter on ioc to get PV from another host ? Or someone have any ideas about this behaivor ??

Regards.

 

Aviso Legal: Esta mensagem e seus anexos podem conter informações confidenciais e/ou de uso restrito. Observe atentamente seu conteúdo e considere eventual consulta ao remetente antes de copiá-la, divulgá-la ou distribuí-la. Se você recebeu esta mensagem por engano, por favor avise o remetente e apague-a imediatamente.

Disclaimer: This email and its attachments may contain confidential and/or privileged information. Observe its content carefully and consider possible querying to the sender before copying, disclosing or distributing it. If you have received this email by mistake, please notify the sender and delete it immediately.

Replies:

RE: Read PV value Attributes XML Mark Rivers via Tech-talk

Re: Read PV value Attributes XML Johnson, Andrew N. via Tech-talk

References:

Read PV value Attributes XML Douglas Araujo via Tech-talk

RE: Read PV value Attributes XML Mark Rivers via Tech-talk

Navigate by Date:

Prev: Reg multi monitor GUI in CSS Himanshu Tyagi via Tech-talk

Next: RE: Read PV value Attributes XML Mark Rivers via Tech-talk

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 

Navigate by Thread:

Prev: RE: Read PV value Attributes XML Mark Rivers via Tech-talk

Next: RE: Read PV value Attributes XML Mark Rivers via Tech-talk

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