Menu
▾
▴
#319 Conflict between event-type and event-parameters
When trying to load an EPICS file into VTS, there is an issue trying to load event-enrollments with an event-type of 'floating-limit'.
Steps to reproduce (use 'alltestEpics.tpi')
1) locate event-enrollment, 1 in the alltestEpics file
2) delete (or comment out) the existing event-parameters and remove the '--' for the floating-limit event parameters (Choice=4).
3) change [4] to (4)
3) Load the EPICS file into VTS - observe that it is consumed properly.
4) in the alltestEPICS file, change the event-type for event-enrollment,1 from 'change-of-state' to 'floating-limit'
5) Load the EPICS file into VTS - observe that an error is generated
'Line XX: Expected ( before (objecttype, instance) here !: event-parameters: (4){3<,>{(analog-input,1),present-value,,}, 4.4., 5.5, 6.6}'
Currently, VTS parsing of event-parameters EPICS doesn't use the context tags called for by 135.1 clause 4.4. Instead, it derives the CHOICE from the value of the event-type property. That is one reason why the item with [4] is commented out in allTestEpics.tpi. You change of [4] to (3) confuses matters even more: VTS reads the 4 as the delay, and then fails trying to read the object ID.
You need something like:
event-type: floating-limit
event-parameters: {3, {(analog-input,1),present-value,,}, 4.4, 5.5, 6.6}
VTS 3.6.1 beta will read this correctly