EPICS Home

Experimental Physics and Industrial Control System


 
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  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 
<== Date ==> <== Thread ==>
Subject: RE: How to deal with LINK_ALARM
From: Mark Rivers <[email protected]>
To: Pilar <[email protected]>, "[email protected]" <[email protected]>
Date: Tue, 6 Jun 2017 10:47:06 +0000 
In both of the records you listed OUT and INP links using asyn syntax but you have not set the DTYP to an asyn device support type.

Is this actually how your database is configured?  If so that would explain the link errors, because presumably EPICS would think this is soft device support and those are Channel Access links, i.e. PV names.

Mark

________________________________________
From: [email protected] [[email protected]] on behalf of Pilar [[email protected]]
Sent: Tuesday, June 06, 2017 4:24 AM
To: [email protected]
Subject: How to deal with LINK_ALARM

Hello,

I have a question related to the alarm LINK_ALARM.
I have been reading the documentation but I m not able to really
understand what that means and my system works in the right way. But I
have always a pink outline around the box with the indication
INVALID(LINK_ALARM).

For more information, attached above is an example about how is one of
this PV defined in my database.
Thank you for the information!
Pilar

record(ao, "$(user):CavMilliVLimitSet")
{
field(DESC, "Limit to CavMilliVSet Record")
field(OUT ,"@asyn($(PORT),$(ADDR),$(TIMEOUT))CavMilliVLimitSet")
field(EGU, "mV")
field(VAL, "1400")
field(LOPR, "0")
field(HOPR, "1412.5")
field(HIHI, "1500")
field(HIGH, "1000")
field(LOW, "10")
field(LOLO, "-1")
field(HHSV, "MAJOR")
field(HSV, "MINOR")
field(LSV, "MINOR")
field(LLSV, "MAJOR")
field(PREC, "2")
info(autosaveFields, "VAL")
field(PINI, "YES")
}

record(ai, "$(user):CavMilliVLimitRdbk")
{
field(DESC, "Limit to CavMilliVSet Record")
field(INP ,"@asyn($(PORT),$(ADDR),$(TIMEOUT))CavMilliVLimitSet")
field(SCAN ,"I/O Intr")
}

The field CavMilliVLimitRdbk is not used at all, because is an intern
parameter use for other calculations. That means...CavMilliVLimitSet is
used as input for some calc blocks.
Replies:
Re: How to deal with LINK_ALARM Pilar
Re: How to deal with LINK_ALARM Pilar
Navigate by Date:
Prev: epicsQt release 3.4.3 - at GitHub Andrew C. Starritt
Next: Re: How to deal with LINK_ALARM Pilar
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: epicsQt release 3.4.3 - at GitHub Andrew C. Starritt
Next: Re: How to deal with LINK_ALARM Pilar
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