Experimental Physics and
Industrial Control System

"Pearson, Matthew R." <[email protected]> · Fri, 9 Oct 2015 14:13:52 +0000

Hi Torsten,

> 
> I can move the motor, and the e.g. IOC:m1.RBV goes away from UNDEFINED; but
> CSS does never take away the pink Disconnected.
> 

That sounds familiar. I frequently have the same issue with motor record widgets in CSS. If the record goes into alarm state, many of the widgets connected to motor record fields reflect the alarm state. When the problem is cleared, the widgets still show alarm state, even though the record STAT and SEVR are fine. Most of the time I can clear it by reloading the OPI. I’m not sure it’s particularly motor record related, but I see it most often with motors (but maybe I just have more alarm conditions with motors).

On some of the more user facing OPI screens I sometimes remove the widget alarm sensitivity so it’s not confusing.

Thinking back, I had similar issues with EDM as well, again with motors.

Cheers,
Matt

> I'm not sure if this has anything to do with the motor record.
> 
> I will put that aside that for a moment, in case somebody is interested:
> https://github.com/tboegi/cashark/commit/b367eeb6ab3861379ab558f512175ed13e9d56af
> 
> Thanks for help.
> /Torsten
> 
> 
> On 08/10/15 07:02, Johnson, Andrew N. wrote:
>> Hi Torsten,
>> 
>> I suspect you would be wasting your time using Wireshark to investigate this, so far I don't think you've shown us any evidence that can't be explained as an issue with or a misunderstanding of what's going on inside the IOC itself, which has little or nothing to do with the CA protocol and what goes over the network. The command-line tools caget, caput and camonitor and the iocsh commands dbpr, dbgf and dbpf are probably all you need to investigate what's happening inside the IOC.
>> 
>> Database records start off with an <undefined> or zero time stamp until they have been processed at least once, so you need to understand the database design and how the records are supposed to get processed. The motor record is probably the most complex type we have, so having an understanding of how it behaves and when it sets its time stamp is probably very important. If you should exhaust the subject of the record support, is your 3.14.12 IOC using autosave perhaps? If so it might be that the 3.15 version of that isn't behaving the same.
>> 
>> - Andrew
>> 
> 

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System