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: tech-talk-bounces@aps.anl.gov [tech-talk-bounces@aps.anl.gov] on behalf of Pilar [pilar.gil@sevensols.com]
Sent: Tuesday, June 06, 2017 4:24 AM
To: tech-talk@aps.anl.gov
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.