Experimental Physics and
Industrial Control System

Zenon Szalata <[email protected]> · Fri, 10 May 2013 08:57:03 -0700

Hi Mark,
Well,

zms@esaanal2 $ caput ESA:LO:SC:2531-21:CH1:MAXV-WR:DATA 100
Old : ESA:LO:SC:2531-21:CH1:MAXV-WR:DATA 50
New : ESA:LO:SC:2531-21:CH1:MAXV-WR:DATA 100

and the Text Control immediately showed the new value. From now on it

will work just fine until the IOC is restarted.

I suspect that part of the problem is how I am initializing these Text

Control widgets. At this point I am still struggling with the fact that

after the IOC is started, the PV in question has the correct value which

comes from a register in the hardware and is represented incorrectly in

the EDM Text Control widget.

Up till now, I was relaunching the EDM screen (after the IOC was fully

up), which has the Text Control in question, from a main EDM screen via

a related display button. I was thinking that doing that would result

in EDM establishing a new connection with the PV and display the correct

value. That was not working correctly. Just now, I actually restarted

the EDM session and the problem seems to have gone away.

You may be interested to know what this is all about. Well, I am

implementing a motor driver for the Beckhoff KL2531 and KL2541 stepper

motor controllers. My IOC is based on your Modbus support module and I

am implementing the motor driver itself entirely on the EPICS record

level, which I find an incredible challenge; implementing complex

solution this way is definitely my weakness. At this point I am nearly

done and it seems to be working well except for these kind "small" problems.

Thanks Mark,
Zen

On 05/10/13 05:46, Mark Rivers wrote:

What happens if you change the value of the PV, either from a caput from the Linux shell.  Does ADM then display the correct value?  What if you change it from EDM itself?

Mark

________________________________________
From: [email protected] [[email protected]] on behalf of Zenon Szalata [[email protected]]
Sent: Friday, May 10, 2013 12:05 AM
To: [email protected]
Subject: EDM

I have a peculiar problem which I fail to understand.
I am using EPICS R3.14.12.2, EDM 1-12-56.
I have a few longout records which are created from the same template.
After the IOC is initialized, these longout records have non zero
values.  The records are controlled via EDM Text Control widgets.  At
this point, no user entries were made.  I could explain how these
records got the initial values, but that is probably not relevant.  When
I start an EDM screen which has the Text Controls, one of the controls
shows value of zero.  caget on this record shows a non zero value. I got
the PV name for the caget command by middle clicking on the Text
Control. Yet, all the other Text Controls show the correct non zero
values which are the values that I verified with both caget and dbpr
commands.   The Text Controls were created by copy and paste, all the
records were created from the same template.
Restarting EDM does not help.  Putting EDM in edit mode and back in
execute mode does not help; the value zero is stubbornly displayed and
just for this one PV.

Here is dbpr output for the record in question:

epics> dbpr ESA:LO:SC:2531-21:CH1:MAXV-WR:DATA,5
ACKS: NO_ALARM      ACKT: YES           ADEL: 0             ALST: 0
ASG:                ASP: (nil)          BKPT: 00            DESC:
MaxVelocity:
DISA: 0             DISP: 0             DISS: NO_ALARM      DISV: 1
DOL:CONSTANT        DPVT: (nil)         DRVH: 0             DRVL: 0
DSET: 0x7f8994126760                    DTYP: Soft Channel EGU:
EVNT: 0             FLNK:DB_LINK ESA:LO:2531-21:CH1:MAXV-WR:REG
HHSV: NO_ALARM      HIGH: 0             HIHI: 0             HOPR: 0
HSV: NO_ALARM       HYST: 0             IVOA: Continue normally
IVOV: 0             LALM: 0             LCNT: 0             LLSV: NO_ALARM
LOLO: 0             LOPR: 0             LOW: 0              LSET: 0x136f8c0
LSV: NO_ALARM       MDEL: 0
MLIS: c0 69 02 20 89 7f 00 00 30 5e 02 20 89 7f 00 00 02 00 00 00
MLOK: 50 64 29 01 00 00 00 00           MLST: 0
NAME: ESA:LO:SC:2531-21:CH1:MAXV-WR:DATA                    NSEV: NO_ALARM
NSTA: NO_ALARM      OMSL: supervisory   OUT:CONSTANT        PACT: 0
PHAS: 0             PINI: NO            PPN: (nil)          PPNR: (nil)
PRIO: LOW           PROC: 0             PUTF: 0             RDES: 0x10b1220
RPRO: 0             RSET: 0x7f8994362180                    SCAN: Passive
SDIS:CONSTANT       SEVR: INVALID       SIML:CONSTANT       SIMM: NO
SIMS: NO_ALARM      SIOL:CONSTANT       SPVT: (nil)         STAT: UDF
TIME: <undefined>   TPRO: 0             TSE: 0 TSEL:CONSTANT
UDF: 0              VAL: 50

dbpr output for the other records (which don't show this problem) looks
identical for all practical purposes.
Any suggestion as to the nature of the problem and how to over come it,
would be much appreciated.
Zen

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System