BACnetIPdatalink.Bbmd3 (PROP) ¶ PROPERTY Bbmd3 : BBMD_Info BBMD 3

BACnetIPdatalink.Bbmd4 (PROP) ¶ PROPERTY Bbmd4 : BBMD_Info BBMD 4

BACnetIPdatalink.Bbmd5 (PROP) ¶ PROPERTY Bbmd5 : BBMD_Info BBMD 5

BACnetIPdatalink.Bbmd6 (PROP) ¶ PROPERTY Bbmd6 : BBMD_Info BBMD 6

BACnetIPdatalink.Bbmd1 (PROP) ¶ PROPERTY Bbmd1 : BBMD_Info BBMD 1

BACnetIPdatalink.Bbmd2 (PROP) ¶ PROPERTY Bbmd2 : BBMD_Info BBMD 2

BACnetMSTPdatalink (FB) ¶ FUNCTION_BLOCK BACnetMSTPdatalink IMPLEMENTS IBACnetDatalink BACnet MS/TP datalink. Information configured in BACnetMSTPdatalink (including the serial configuration) is used to generate the BACstack configuration file (bacstac.ini) on the PLC. CODESYSControl.cfg contains a setting: [CmpBACnet] IniFile=bacstac.ini to define where the BACstack configuration file is to be found. Because the BACstack configuration file is written using the information from BACnetMSTPdatalink, it is accessed from either the runtime system (component) CmpBACnet and the IEC application. So an absolute path or placeholders 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. Runtime changes of broadcast distribution table entries as well as foreign device table ¶ The BACnetServer configuration AutoGenerateBACstackConfig allows to control if the BACstack configuration file is generated during BACnetServer.StartBACnetStack. If AutoGenerateBACstackConfig is set to FALSE, BACnetServer.GenerateBACstackConfig can be used to generate the BACstack configuration file on demand. BBMD broadcast distribution table (BDT) entries as well as foreign device table (FDT) entries added by clients requests are stored in the BACstack configuration file. This happens at runtime of your application and is not reflected in the configuration parameters of the BACnetMSTPdatalink. Re-generating the BACstack configuration file each time at application start would eliminate the entries written at application runtime. So take care to generate the BACstack configuration file only if needed (most likely at initial setup, or at changes in network structure) to ensure keeping those entries. In case you’r using the BACnet device with BBMD functionality and clients requests are to be expected to add/change/remove BDT/FDT entries, you need to set AutoGenerateBACstackConfig := FALSE to keep them persistent. Properties: Baudrate Connection DeviceName MSTPaddr MaxInfoFrames MaxMaster MaxMsgReq NetworkNumber ReplyTimeout TokenTimeout Methods: CheckMstpDeviceDriverReady Structure: Baudrate (Property) Connection (Property) DeviceName (Property) MSTPaddr (Property) MaxInfoFrames (Property) MaxMaster (Property) MaxMsgReq (Property) NetworkNumber (Property) ReplyTimeout (Property) TokenTimeout (Property) protected CheckMstpDeviceDriverReady (Method)

BACnetMSTPdatalink.Baudrate (PROP) ¶ PROPERTY Baudrate : UDINT MS/TP Baud rate

BACnetIPdatalink.CheckNetworkSettings (METH) ¶ METHOD PROTECTED CheckNetworkSettings : BOOL Checks, if parent ETH device is configured properly. Returns TRUE if the network settings are valid. In case FALSE is returned the BACnetServer will not start. In case there is nothing to check (BACnetIPdatalink underneath BACnetServer or PLC) simply return TRUE. InOut: Scope Name Type Comment Return CheckNetworkSettings BOOL Input pConnector POINTER TO IoConfigConnector “child” connector to parent device, parent device could be “Common.Ethernet” (Ethernet), “Common.BACnet” (BACnetServer) or “Common.PCI” (PLC).

BACnetIPdatalink.GetIPaddrFromETH (METH) ¶ METHOD PROTECTED GetIPaddrFromETH : BOOL Gets IP-address from parent ETH device, returns TRUE, if valid IP-address was obtained. InOut: Scope Name Type Comment Return GetIPaddrFromETH BOOL Input pConnector POINTER TO IoConfigConnector “child” connector to parent device, parent device could be “Common.Ethernet” (Ethernet), “Common.BACnet” (BACnetServer) or “Common.PCI” (PLC).