BACnet Connector Error Codes

i4scada Knowledge Base

Abstract

Check out this article and learn more details about the i4scada BACnet Connector error codes.

Error Code	Details
0	Success.
-666	License check fails ( no license ).
-2	Configuration XML string received in Init method is not correctly formatted on the syntax level.
-3	Configuration XML string received in Init method does not contain configuration that would be valid for BACnet connector. Read more The XML configuration string for the BACnet connector, as for any other connector, is used to transport information between Configuration Software Modules and Communication Software Modules. Error code of -3 is, in this sense, an error code signaling internal errors and/or incompatibility. It may also mean that the configuration was created with older configuration software and read by a new version of the connector - though connectors are usually made to be backward compatible. In this particular case, error code -3 means that the XML-formatted string does not contain correct configuration information. For example, the <Devices> section might be missing, or it does not contain the Network parameter or other parameters. There are many correctness checks when retrieving information from XML-formatted configuration strings.
-4	Configuration XML string received in the Init method does not contain any BACnet object properties. So the number of signals would be zero.
-5	Initialization of the Cimetrics BACnet toolkit failed.

Error Code	Details
0	Success.
-99	Connector was not properly initialized by the Init method.
-11	Signal names parameter of the method does not have the correct automation data type.
-12	Status flags parameter of the method does not have the correct automation data type.
-1	Signal names parameter cannot be successfully converted to a list of names.
-2	Status flags parameter cannot be successfully converted to a list of flags.
-3	Number of signals names differs from a number of flags specified in ActivateSignals method.
-4	Count of signals / status flags to activate is zero.

Individual results array error codes are:

Error Code	Details
0	Success.
-1	Signal with corresponding signal name is not valid.

Error Code	Details
0	Success.
-99	Connector was not properly initialized by Init method.
-11	Signal names parameter of the method does not have correct automation data type.
-12	Status values parameter of the method does not have correct automation data type.
-1	Signal names parameter cannot be successfully converted to list of names.
-2	Status values parameter cannot be successfully converted to list of values.
-21	Number of signals names differs from number of values specified in WriteSignalsAsync method.
-24	Count of signals / signal values to write is zero.
-5	There are no signals to write, because no signal have both correct name and correct value.

Individual results array error codes are:

Error Code	Details
0	Success.
-1	Signal with corresponding signal name is not valid.
-22	Value to write to signal does not have correct data type for Visual Basic 6 compatibility mode.
-2	Value to write to signal does not have corrected data type and it cannot be converted to correct data type.

Error Code	Details
0	Success.
-99	Connector was not properly initialized by Init method.
-11	Signal names parameter of the method does not have correct automation data type.
-12	Status values parameter of the method does not have correct automation data type.
-1	Signal names parameter cannot be successfully converted to list of names.
-2	Status values parameter cannot be successfully converted to list of values.
-21	Number of signals names differs from number of values specified in WriteSignalsAsync method.
-24	Count of signals / signal values to write is zero.
-5	There are no signals to write, because no signal have both correct name and correct value.

Individual results array error codes are:

Error Code	Details
0	Success.
-1	Signal with corresponding signal name is not valid.
-22	Value to write to signal does not have correct data type for Visual Basic 6 compatibility mode.
-2	Value to write to signal does not have corrected data type and it cannot be converted to correct data type.

STDMETHODIMP CWFClient::GetDriverVersion(LONG* versionBuild, LONG* returnValue)

STDMETHODIMP CWFClient::Init(BSTR configXML, VARIANT* signalNames, VARIANT* dataTypes, LONG startCommunication, LONG* returnValue)

STDMETHODIMP CWFClient::Reset(LONG* returnValue)

Name, BSTR furtherDefinition, LONG* dataType, LONG* returnValue)

STDMETHODIMP CWFClient::ActivateSignals(VARIANT signalNames, VARIANT statusFlags, VARIANT* results, LONG* returnValue)

STDMETHODIMP CWFClient::WriteSignalsAsync(VARIANT signalNames, VARIANT signalValues, VARIANT* results, BSTR* guidAsync, LONG* returnValue)

STDMETHODIMP CWFClient::WriteSignalsSync(VARIANT signalNames, VARIANT signalValues, VARIANT* results, LONG* returnValue)

In this section:

i4scada Knowledge Base