Geoff,
We noticed some changed behaviour in calc and calcout records from
v3.13.4 to v3.14.6 and were unable to identify the cause. Take a
simple
calc record, maybe too simple:
record(calc,"CTL_TEST_66/CALC") {
field(CALC, "1=0")
field(SCAN, "1 second")
}
In v3.13.4 VAL is the expected value of zero. In v3.14.6 VAL is one.
The same applies for the calcout record.
I am unable to reproduce your problem. I put your .CALC and .SCAN
fields into a calc record in one of my databases. VAL=0 as expected.
This is 3.14.6 on Linux.
epics> coreRelease
########################################################################
####
### EPICS IOC CORE built on Oct 1 2004
### EPICS R3.14.6 $R3-14-6$ $2004/05/28 19:27:47$
########################################################################
####
epics> dbpr testClient1_PA_A0_calc,5
A: 0 ACKS: NO_ALARM ACKT: YES ADEL: 0
ALST: 0 ASG: ASP: 0x00000000 B: 0
BKPT: 0x00 C: 0 CALC: 1=0 D: 0
DESC: Counter DISA: 0 DISP: 0 DISS:
NO_ALARM
DISV: 1 DPVT: 0x00000000 DSET: 0x00000000 DTYP: <nil>
E: 0 EGU: Counts EVNT: 0 F: 0
FLNK:CONSTANT 0 G: 0 H: 0 HHSV:
NO_ALARM
HIGH: 0 HIHI: 0 HOPR: 10 HSV:
NO_ALARM
HYST: 0 I: 0 INPA:CONSTANT
INPB:CONSTANT
INPC:CONSTANT INPD:CONSTANT INPE:CONSTANT
INPF:CONSTANT
INPG:CONSTANT INPH:CONSTANT INPI:CONSTANT
INPJ:CONSTANT
INPK:CONSTANT INPL:CONSTANT J: 0 K: 0
L: 0 LA: 0 LALM: 0 LB: 0
LC: 0 LCNT: 0 LD: 0 LE: 0
LF: 0 LG: 0 LH: 0 LI: 0
LJ: 0 LK: 0 LL: 0 LLSV:
NO_ALARM
LOLO: 0 LOPR: 0 LOW: 0 LSET:
0x90780a08
LSV: NO_ALARM MDEL: 0 MLIS: 0x000000000000000000000000
MLOK: 0xd0120a08 MLST: 0 NAME: testClient1_PA_A0_calc
NSEV: NO_ALARM NSTA: NO_ALARM PACT: 0 PHAS: 0
PINI: NO PPN: 0x00000000 PPNR: 0x00000000 PREC: 0
PRIO: LOW PROC: 0 PUTF: 0 RDES:
0x70120608
RPCL: 0x48000000000000f03f4800000000000000003d7f RPRO: 0
RSET: 0x60070740 SCAN: 1 second SDIS:CONSTANT SEVR:
NO_ALARM
SPVT: 0xe0760c08 STAT: NO_ALARM TIME: 0x75dcfa1b20475020
TPRO: 0 TSE: 0 TSEL:CONSTANT UDF: 0
VAL: 0
Mark
