Need some clarification about "which tag to be used for mapping with BACnet device or some other protocol device".
I had used custom tag like mappedWith to map Haystack equipment with BACnet device. But when I run nav operation this tag is not displayed in nav response.
But when I use mappedRef also a custom tag, it's displayed in nav operation response.
Queries :
1.Is there any validation for tags internally in reference implementation ?
2.And is there any specific tag which we can use for this usecase where we can map equipment id with device id ?
Thanks!
Brian FrankWed 4 Apr 2018
But when I run nav operation this tag is not displayed in nav response.
That would probably be system specific - what are you using? The Java Toolkit?
1.Is there any validation for tags internally in reference implementation
I assume you mean the Java Toolkit here? Then no
And is there any specific tag which we can use for this usecase
There is no Haystack standard for this. In SkySpark we use the convention bacnetCur, bacnetWrite, and bacnetHis for the addresses used for current value, writing, and history synchronization respectively
Hareesh Reddy G.M Tue 3 Apr 2018
Hi,
Need some clarification about "which tag to be used for mapping with BACnet device or some other protocol device".
I had used custom tag like
mappedWith
to map Haystack equipment with BACnet device. But when I runnav
operation this tag is not displayed innav
response.But when I use
mappedRef
also a custom tag, it's displayed innav
operation response.Queries :
1.Is there any validation for tags internally in reference implementation ?
2.And is there any specific tag which we can use for this usecase where we can map equipment id with device id ?
Thanks!
Brian Frank Wed 4 Apr 2018
That would probably be system specific - what are you using? The Java Toolkit?
I assume you mean the Java Toolkit here? Then no
There is no Haystack standard for this. In SkySpark we use the convention bacnetCur, bacnetWrite, and bacnetHis for the addresses used for current value, writing, and history synchronization respectively