Experimental Physics and
Industrial Control System

"Gillingham, IJ \(Ian\)" <[email protected]> · Fri, 9 Nov 2007 09:46:18 -0000

This thread has come at a very timely moment, as I have been stumped for
a couple of days as to why a some of my waveform records have had their
INDX fields set to zero for no apparent reason.  My waveforms in
question contain status and interlock information from PLCs, which is
populated via streams/RS232. This has caused some of our interlock
tables to be referencing the wrong interlocks (those allocated to the
word at INDX = 0) and causing some confusion!  Having discussed this
thread with Pete Leicester, it transpires that this issue is more
widespread than realised. A fix would be much appreciated. In the mean
time, I shall probably have to monitor these INDX values and correct
them if/when they get reset to zero.

Ian Gillingham
Diamond Light Source

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Carl Lionberger
Sent: 09 November 2007 01:01
To: Andrew Johnson
Cc: [email protected]
Subject: Re: subArray INDX field set to 0 if NORD <= 0

I'm pretty sure that the reason I put this in is the poor way the 
waveform record, on which subarray  was based, posts invalid status. 
Certainly the subarray record support does not ever set INVALID and the 
waveform record does it only in a part that looks  unreachable to me. 
The readValue() returns bad status but the process routine ignores it.  
It seems to me that the record should go invalid if it can't obtain
input.

Although I think Lewis' argument is compelling, I also think more needs 
to be done than just eliminating the assignment of indx to zero.

Carl

Andrew Johnson wrote:

> Hi Lewis,
>
> J. Lewis Muir wrote:
>
>> I have found that if a subArray record reads 0 elements into its 
>> array, it sets its INDX field to 0.  Is this behavior intended?  I 
>> would rather it not change its INDX field in this situation.
>
>
> I agree that this behavior seems a little strange and I'm inclined to 
> apply your patch (there's nothing mentioned in the Record Reference 
> Manual about what should happen).  The record's author is listed as 
> Carl Lionberger who is still a member of this community - Carl, do you

> have any comments on this change?
>
> - Andrew

-- 
Carl Lionberger 
510 486 7503
Software Developer, Engineering Division
Lawrence Berkeley National Laboratory
<DIV><FONT size="1" color="gray">This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. 
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
</FONT></DIV> 

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System