You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have an IOC with array records that are written to hardware, and read back, using asyn. The setpoints are in autosave and have PINI=YES. Their values are written to hardware correctly right after iocInit (I added a debug print right after the write, in writeInt32Array/writeFloat64Array, to be sure), but the readback PVs, which are updated via doCallbacksInt32Array/doCallbacksFloat64Array, aren't updated with the value from the setpoint (and in fact are UDF/INVALID).
The readback records use SCAN=I/O Intr, and they are updated when the setpoint PV is written to during operation, or when I write 1 into setpoint.PROC. The issue seems to be exclusively with the processing during IOC initialization.
I might have observed a similar issue with asynOctet as well, but I haven't prepared a reproducer for it yet, so I don't think it's relevant here.
The text was updated successfully, but these errors were encountered:
Hi!
I have an IOC with array records that are written to hardware, and read back, using asyn. The setpoints are in autosave and have PINI=YES. Their values are written to hardware correctly right after iocInit (I added a debug print right after the write, in writeInt32Array/writeFloat64Array, to be sure), but the readback PVs, which are updated via
doCallbacksInt32Array/doCallbacksFloat64Array
, aren't updated with the value from the setpoint (and in fact are UDF/INVALID).The readback records use
SCAN=I/O Intr
, and they are updated when the setpoint PV is written to during operation, or when I write 1 intosetpoint.PROC
. The issue seems to be exclusively with the processing during IOC initialization.I might have observed a similar issue with
asynOctet
as well, but I haven't prepared a reproducer for it yet, so I don't think it's relevant here.The text was updated successfully, but these errors were encountered: