Bacnet Vs Bacnet Ip
Ling Baus
Any update on bacnet driver for Maker addition? Have a home HVAC system like to monitor and it requires bacnet communication.
Are there any other ways to get the info from bacnet to Maker edition? Other software to convert to something Maker will accept?
Downloaded the ConnectorIO 3.X binding and copied org.connectorio.addons.feature.bacnet-3.0.0-20210402.kar into the addons directory. The BACnet Binding appears when I search under settings/Bindings/AddOns in the UI.
Hello Asher,
Version you downloaded is compatible with openHAB 3.x but not 3.4.x. Most accurate way to get binding for your version is building it from sources. Instructions are provided in several posts from other topic:
Error you have should get gone after getting binding build valid for your OH release. One advice - if you start with T3000 my general advice would be to go with bacnet/ip as binding currently works with polling (just like modbus) so getting larger controller I/O status via serial connection will quickly exceed mstp link capability.
Definitely using the bacnet/ip mode. One detail: my T3000 and my OH are on different IP subnets. I will move them to the same LAN, but in the meantime any advice how to configure addresses in the bridge and IP bindings? My OH is 192.168.3.41 and TB3000 is 192.168.1.35
BACnet/IP communication rely on broadcast address hence bridge definition for sure will require address which can reach both ends. If you plan changes to network layout simply re-run discovery once you are done. By default first step of discovery is to make an advice about bacnet/ip interfaces based on operating system configuration.
Have the binding talking to the T3-TB and populating channels. How do I configure the binding to see the RS485/MSTP devices connected to the T3-TB? Still on the test bench, but want to connect MSTP devices like thermostats to the T3-TB.
It really depends on how it is visible in BACnet - are thermostats becoming analog/commendable objects to T3-TB or they become separate devices? If later then you need to add them just like you did with T3-TB using same IP address but use appropriate device id.
The official BACnet specification "ANSI/ASHRAE Standard 135-2001 BACnet A Data Communication Protocol for Building Automation and Control Networks" describes all aspects of the BACnet protocol. When using Kepware's BACnet/IP device driver, it is recommended that users be familiar with the standard BACnet objects and properties discussed in Clause 12 and the BACnet/IP particulars outlined in Annex J. The specification is available along with many other useful resources through the American Society of Heating, Refrigerating and Air-Conditioning Engineers, Inc. (ASHRAE) or the official BACnet website at www.bacnet.org.
min_priority - (Optional) Minimum priority value allowed for this device whether specifying the prioritymanually or via the registry config. Violating this parameter either in the configuration or when writing to thepoint will result in an error. Defaults to 8
max_per_request - (Optional) Configure driver to manually segment read requests. The driver will only grab upto the number of objects specified in this setting at most per request. This setting is primarily for scrapingmany points off of low resource devices that do not support segmentation. Defaults to 10000
proxy_address - (Optional) VIP address of the BACnet proxy. Defaults to platform.bacnet_proxy. SeeCommunicating With Multiple BACnet Networks for details. Unless your BACnet network has special needs you should notchange this value
ping_retry_interval - (Optional) The driver will ping the device to establish a route at startup. If theBACnet proxy is not available the driver will retry the ping at this interval until it succeeds. Defaults to 5
use_read_multiple - (Optional) During a scrape the driver will tell the proxy to use aReadPropertyMultipleRequest to get data from the device. Otherwise the proxy will use multiple ReadPropertyRequestcalls. If the BACnet proxy is reporting a device is rejecting requests try changing this to false for that device.Be aware that setting this to false will cause scrapes for that device to take much longer. Only change if needed.Defaults to true
cov_lifetime - (Optional) When a device establishes a change of value subscription for a point, this argumentwill be used to determine the lifetime and renewal period for the subscription, in seconds. Defaults to 180(Added to Platform Driver version 3.2)
Volttron Point Name - The name by which the platform and agents running on the platform will refer to thispoint. For instance, if the Volttron Point Name is HeatCall1 (and using the example device configuration above)then an agent would use pnnl/isb2/hvac1/HeatCall1 to refer to the point when using the RPC interface of theActuator agent
Writable - Either TRUE or FALSE. Determines if the point can be written to. Only points labeled TRUEcan be written to through the Actuator Agent. Points labeled TRUE incorrectly will cause an error to bereturned when an agent attempts to write to the point
COV Flag - Either True or False. Determines if a BACnet Change-of-Value subscription should beestablished for this point. Missing this column or leaving the column blank will result in no change of valuesubscriptions being established. (Added to Platform Driver version 3.2)