Appendix D: Bacnet Expanded Schema Configuration in the Tridium Jace
PreviousAppendix C: Modbus Expanded Schema Configuration in the Tridium JaceNextAppendix E: History Schema Configuration in the Tridium Jace
Last updated
Last updated
This section has the Tridium Jace slot configurations for the Bacnet Expanded Schema. The structure of the JSON message is shown below.
{ } root has children $schema, gatewayName, gatewayModel, gatewaySoftwareVersion, siteName, buildingName, Point.
The string and value bindings are:
gatewayName: Binding station:|slot:/Services/PlatformServices/SystemService/stationName
gatewayModel: Binding station:|slot:/Services/PlatformServices/SystemService/product
gatewaySoftwareVersion: Binding station:|slot:/Services/PlatformServices/SystemService/niagaraVersion
siteName: String Value The site name as applicable
buildingName: String Value The building name as applicable
{ } Point has children, pointName, timestamp, currentValue, status, ord, parentName, facets, proxyExtProperties, bacnetProperties, tags.
NOTE: parentName requires the creation of Bacnet point folders and the organisation of points into these folders. If this is not done, parentName for all points will be “Points”.
proxyExtProperties:
bacnetProperties and tags:
$schema: String Value
