IEC_BACNET_CLI_INIT (STRUCT)¶

TYPE IEC_BACNET_CLI_INIT : STRUCT

Structure which contains the data for initialization of the BACnet client API.

This structure contains the data for initialization of the BACnet client API. It carries information about the process which is needed to register to the BACnet stack service successfully.

InOut:

Name	Type	Comment
`appName`	POINTER TO BYTE	Name of the application process which registers to the BACnet stack. Only alphanumeric chars are allowed here. No special chars linke slashes, hypen or backslashes, questionmarks, dots or anything else are permitted here. If the application uses such chars in this string it will have propblems registering correctly. The name has to be unique too if more than one process tries to register to the BACnet stack.
`procToStart`	POINTER TO BYTE	Commandline with arguments to start subprocess BACnet stack service. Commandline arguments which are used if the BACnet stack service needs to be started. If the service is already running this arguments given aren’t used.
`localDevice`	POINTER TO IEC_BACNET_TEMPLATE_DEVICE	A pointer to the local device template which will be created. This structure contains the data which is used to initialize the device object of this BACnet client application process. This can be NULL if the client application needs to create its device at some later point.
`bPassiveDevice`	IEC_BACNET_BOOLEAN	If set to True the device template will not be accessable over BACnet. A value of True makes the device unaccessable over BACnet. This option needs to be used only if you have two processes running, one BACnet client process and one BACnet server process which both connect to the BACnet service but you do not want to have two device objects in BACnet. In such an case the client process should set this option to True so it can register to the BACnet service.
`nCovIntProcId`	IEC_BACNET_UINT	Unique process identifier which is needed to register to the BACnet service. Some BACnet service requests, such as the COV or intrinsic reporting services, need an unique process identifier to work. This identifier is used to direct such requests to the right BACnet application process that requested it. This identifier has to be unique by registering with the BACnet stack.The enhanced BACnet API functions for registering remote objects for data and event-notifications will use this value for their subscriptions. A value of 0 is not permitted because it is used to indicate broadcast COV and intrinsic notifications. The users application may use other process ID’s to implement processing of COV and intrinsic reporting.
`nMaxIpcSizeSupported`	IEC_BACNET_UINT	Size of memory used for building up async replies in service hooks.
`apduProps`	IEC_BACNET_APDU_PROPERTIES	A structure containing the default APDU communication parameters. These default set of APDU parameters is used for communication only if the client process has no device constructed yet and the pointer for APDU parameters in functions for service initiation is NULL.