Experimental Physics and
Industrial Control System

Maren Purves <[email protected]> · Thu, 04 Sep 2008 12:00:02 -1000

Emma,
could that be a scanOnce problem rather than a sseq problem?
HTH,
Maren
Shepherd, EL (Emma) wrote:

Hi Andrew,
Thanks for the reply; yes sseq is part of the synApps package (we use it
so regularly I sometimes forget it isn't in base!).
Actually the link is listed as being connected, and in fact it does
update properly when the record is processed or when the value of the
linked record changes.  The difference in behaviour between vxWorks and
Linux is just concerning initialisation - on vxWorks the link gets
processed when the IOC first boots up but on Linux it doesn't.
Emma
-----Original Message-----

From: Andrew Johnson [mailto:[email protected]]
Sent: 04 September 2008 21:04

To: [email protected]

Cc: Shepherd, EL (Emma)

Subject: Re: sseq link problem on Linux

Hi Emma,
On Thursday 04 September 2008 13:46:58 Shepherd, EL (Emma) wrote:

I recently encountered an interesting problem when moving

an IOC from

vxWorks to Linux (RedHat). The database contains a number of sseq
records with CP input links to pull across some data from

another IOC.

This happens whenever one of the links changes, but also

when the IOC

boots up for the first time. This worked fine on vxWorks, but on
Linux the links do not get updated when the IOC boots up. It's not
just an occasional failure, it just never worked. I

changed the sseq

records to transforms and it now works fine. In both cases I had
PINI=YES.

Hmm, I would guess the the sseq record type is from synApps.
However assuming
that it's just using a standard dbCa link, what does "dbcar
'', 1" show from
one of the Linux IOCs where the link is not being updated?
Does it list that
record link as disconnected?
- Andrew
--
Talk is cheap. Show me the code. -- Linus Torvalds

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System