`BACnetIPdatalink` (FB)

FUNCTION_BLOCK BACnetIPdatalink IMPLEMENTS IBACnetDatalink

BACnet IP datalink. A BACnet IP datalink (device) can be placed underneath a ETH device. In this case BACnetIPdatalink obtains the IP address from the ETH device and checks the ETH device network settings for consistency.

In case this BACnet IP datalink (device) has been placed underneath another node we rely on ETH autodetect of the BACstack (using first ETH adapter found) or the IP address has to be set by the application.

Information configured in BACnetIPdatalink (including the IP address) is used to generate the BACstack configuration file (bacstac.ini) on the PLC. Please note the BACnetServer configuration AutoGenerateBACstackConfig, you can control if the BACstack configuration file is generated during BACnetServer.StartBACnetStack. Otherwise you can call BACnetServer.GenerateBACstackConfig. BBMD broadcast distribution table entries as well as foreign device table entries added from clients requests are stored in the BACstack configuration file. Take care to re-generate the BACstack configuration file only if needed, to ensure keeping tbose entries.

CODESYSControl.cfg contains a setting:

[CmpBACnet] IniFile=bacstac.ini

to define where the BACstack ini file is to be found. Because the BACstack ini file is written using the information from BACnetIPdatalink, it is accessed from either the runtime system (component) CmpBACnet and the IEC application. So an absolute path has to be used for this setting, for example:

[CmpBACnet] IniFile=/tmp/bacstac.ini

If sandboxing the runtime system filesystem is chosen, the setting [SysFile] ForceFilePath= has to be used to allow access for the absolute path of the BACstack ini file.

BACnetIPdatalink (FB)

`BACnetIPdatalink` (FB)