-
Notifications
You must be signed in to change notification settings - Fork 19
Description
Has anyone else noticed that the CPT field sometimes is not posted, and posted in bunch of two?
I do think that it is incremented correctly it is just that it is posted irregularly, and to the user it looks like it might take two data points one some steps, and zero on some.
Example monitoring the CPT field and FAZE field, note that I run the positioner very slow so there several seconds when the positioner is moving. The following example are camonitors of what happens at each step. This is continuous sequence were the motors moves for several seconds when I comment.
# Sequence when when CPT is not posted:
SCANNING:GRID.FAZE 2016-11-25 16:04:50.931012 TRIG_DETCTRS
SCANNING:GRID.FAZE 2016-11-25 16:04:50.931012 WAIT:DETCTRS
SCANNING:GRID.FAZE 2016-11-25 16:04:50.931012 RECORD SCALAR DATA
SCANNING:GRID.FAZE 2016-11-25 16:04:50.931012 MOVE_MOTORS
SCANNING:GRID.FAZE 2016-11-25 16:04:50.931012 WAIT:MOTORS
# Sequence when when CPT is posted only once:
SCANNING:GRID.FAZE 2016-11-25 16:04:50.931012 TRIG_DETCTRS
SCANNING:GRID.FAZE 2016-11-25 16:04:50.931012 WAIT:DETCTRS
SCANNING:GRID.CPT 2016-11-25 16:04:50.931012 1
SCANNING:GRID.FAZE 2016-11-25 16:04:50.931012 RECORD SCALAR DATA
SCANNING:GRID.FAZE 2016-11-25 16:04:50.931012 MOVE_MOTORS
SCANNING:GRID.FAZE 2016-11-25 16:04:50.931012 WAIT:MOTORS
# Sequence when when CPT is posted twice:
SCANNING:GRID.FAZE 2016-11-25 16:04:50.931012 TRIG_DETCTRS
SCANNING:GRID.FAZE 2016-11-25 16:04:50.931012 WAIT:DETCTRS
SCANNING:GRID.CPT 2016-11-25 16:04:50.931012 2
SCANNING:GRID.FAZE 2016-11-25 16:04:50.931012 RECORD SCALAR DATA
SCANNING:GRID.FAZE 2016-11-25 16:04:50.931012 MOVE_MOTORS
SCANNING:GRID.FAZE 2016-11-25 16:04:50.931012 WAIT:MOTORS
SCANNING:GRID.CPT 2016-11-25 16:04:50.931012 3
It seems like it it sometimes misses to post CPT and then post it two times.
Build Environment
Architecture: x86_64 CentOS7
Epics Base Version: 3.14.12.5, 3.15.4
sscan version: https://github.com/epics-modules/sscan/tree/e543806b6405311aa03a5ecbeb7a4dc2037326ce
But there are no changes to sscanRecord.c after that.