Hey again,
I found the issue. All records have a db-link in their SDIS field to a
bo record.
This bo record switches on/off the power supply of the device, so if
this is set to 0 communication with the device does not work.
The record was set to 1 during initialization but still in UDF_ALARM
state which was causing the LINK_ALARM for all other records.
Cheers,
Florian
On 7/14/23 10:27, Florian Feldbauer via Tech-talk wrote:
Hey all,
I have a strange behaviour I haven't seen before.
In my IOC all records are set to STAT = LINK_ALARM and SEVR = INVALID.
I checked the code of the device support, that is used, but there are
only conditions when a record is set to READ_ALARM or WRITE_ALARM.
Is there any condition in the record processing itself, where a record
can be set to LINK_ALARM?
Base 7.0.4.1 is used.
The records have a DB_LINK in their SDIS field and some have a FLNK.
Cheers,
Florian
--
Ruhr-Universität Bochum
AG der Experimentalphysik I
Dr. Florian Feldbauer
NB 2/131 / Fach 125
Universitätsstr. 150
D-44801 Bochum
Office: NB 2/134
Phone: (+49)234 / 32-23563
Fax: (+49)234 / 32-14170
https://paluma.ruhr-uni-bochum.de
- References:
- LINK_ALARM in records Florian Feldbauer via Tech-talk
- Navigate by Date:
- Prev:
LINK_ALARM in records Florian Feldbauer via Tech-talk
- Next:
multicomp pro mp710256 Pierrick M Hanlet 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:
LINK_ALARM in records Florian Feldbauer via Tech-talk
- Next:
multicomp pro mp710256 Pierrick M Hanlet 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
|