As has happened before, the syntax defined by the 135.1 for the EPICS is in conflict with the syntax of the VTS scripting language.
I have made a change that SEEMS to be OK. But if you find a case where it isn't, please let me know.
The change is in BACnetObjectIdentifier::Encode.
// - EPICS format says to wrap objectID in parenthesis.
// - But the script parser takes the parenthesis as tokens, and won't accept and objectID in parenthesis.
// - This also means a script can't use >> to set a variable with an objectID read from a target device.
// - The code here has changed back and forth: with and without:
// "changed this back (with parenthesis) because it broke the Send Dialog VTSANY entry of ObjId 3/10/2006"
// But, as of Sept 29, 2010, VTSANY and other send dialogs DON'T seem to require the parenthesis,
// so I have removed them again so that scripting will work.
// If you find something that NEEDS the parenthesis, please let me know. johnhartman.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As has happened before, the syntax defined by the 135.1 for the EPICS is in conflict with the syntax of the VTS scripting language.
I have made a change that SEEMS to be OK. But if you find a case where it isn't, please let me know.
The change is in BACnetObjectIdentifier::Encode.
// - EPICS format says to wrap objectID in parenthesis.
// - But the script parser takes the parenthesis as tokens, and won't accept and objectID in parenthesis.
// - This also means a script can't use >> to set a variable with an objectID read from a target device.
// - The code here has changed back and forth: with and without:
// "changed this back (with parenthesis) because it broke the Send Dialog VTSANY entry of ObjId 3/10/2006"
// But, as of Sept 29, 2010, VTSANY and other send dialogs DON'T seem to require the parenthesis,
// so I have removed them again so that scripting will work.
// If you find something that NEEDS the parenthesis, please let me know. johnhartman.