Experimental Physics and
Industrial Control System

"Johnson, Andrew N." <[email protected]> · Thu, 8 Oct 2015 05:02:10 +0000

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

-- 
Sent from my iPad

> On Oct 7, 2015, at 9:53 PM, Torsten Bögershausen <[email protected]> wrote:
> 
> Is this what you are asking for ?
> dbpr IOC:m1
> ASG:                ATHM: 0             CDIR: 0             CNEN: Enable
> DESC: m1            DHLM: 170           DIFF: 0             DISA: 0
> DISP: 0             DISV: 1             DLLM: 0             DMOV: 1
> DRBV: 0             DVAL: 0             HLM: 170            HLS: 0
> LDMV: 1             LLM: 0              LLS: 0              LVIO: 0
> MOVN: 0             NAME: IOC:m1        OFF: 0              RBV: 0
> RDIF: 0             REP: 1              RHLS: 0             RLLS: 0
> RLV: 0              RMP: 0              RRBV: 0             RVAL: 0
> SEVR: NO_ALARM      STAT: NO_ALARM      TDIR: 0             TPRO: 0
> VAL: 0              VERS: 6.81
> 
> Beside that, caget mebtions "undefined" in both bases:
> 
> caget -a   IOC:m1.RBV
> IOC:m1.RBV                     <undefined> 0
> 
> -------------------
> And camonitor shows this:
> IOC:m1.RBV                     <undefined> 0
> IOC:m1.VAL                     <undefined> 0
> -----------------------------------
> 
> Did I mention that I use the motor record ?
> 
> Does this smell like a timig problem ?
> I remember that even in the codac version of everything (base, motor 6.81, CSS) sometimes the fields
> stayed pink all the time. But only sometimes.
> 
> I will do some wiresharking on Friday.
> Thanks for the help.
> 
> 
> 
>> On 07/10/15 14:52, Michael Davidsaver wrote:
>>> On 10/07/2015 08:45 AM, Torsten Bögershausen wrote:
>>> 
>>> camonitor is fine, the PV IOC:m1.RBV) goes from <undefied> to 0.
>> 
>> What is the alarm severity of the record "IOC:m1"?
>> 

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System