Skip to main content

i4SCADA Knowledge Base

BACnet Connector Error Codes

Abstract

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

Init

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.

-4

Configuration XML string received in Init method does not contain any BACnet object properties. So the number of signals would be zero.

-5

Initialization of Cimetrics BACnet toolkit failed.

ActivateSignals

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 flags 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 flags parameter cannot be successfully converted to list of flags.

-3

Number of signals names differs from 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.

WriteSignalsAsync

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.

WriteSignalsSync

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.

List of the Method prototypes

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)