Runtime Return Codes
Errors that occur during: initialization of the ADS client; establishing the connection; sending requests or receiving data packets; converting the LabVIEW™ data type to TC3 data type or vice versa are described as runtime errors.
error value | symbol | Error description | Remedy option |
|---|---|---|---|
16#00001464 | 5220 | TF3710_ERR_E_POINTER | Invalid pointer 0 (null). |
16#00001465 | 5221 | TF3710_ERR_E_OUT_OF_RANGE | The value is not in the range |
16#00001466 | 5222 | TF3710_ERR_E_INVALID_ARG | The parameters are invalid |
16#00001467 | 5223 | TF3710_ERR_E_OUT_OF_MEMORY | The memory is full |
16#00001468 | 5224 | TF3710_ERR_E_NOT_A_NUMBER | Is not a number |
16#00001469 | 5225 | TF3710_ERR_E_BAD_ALLOCATION | Wrong allocation |
16#0000146A | 5226 | TF3710_ERR_E_NOT_A_STRING | Is not a string |
16#0000146B | 5227 | TF3710_ERR_E_UNINITIALIZED_TIMESTAMP | Timestamp is not initialized |
16#0000146D | 5229 | TF3710_ERR_E_CONFIGURATION_NON_EXISTENT | The configuration was not found |
16#0000146E | 5230 | TF3710_ERR_E_FLOATING_OBJECT | Floating/Non-saved object (VI, Project, ...) |
16#0000146F | 5231 | TF3710_ERR_E_INVALID_CONFIGURATION | The configuration is incorrect |
16#0000146C | 5228 | TF3710_ERR_E_LOCKFAILED | Lock has failed |
16#00001479 | 5241 | TF3710_ERR_FAILED_WAIT_ON_A_REQUEST | Waiting for the request has failed |
16#00001483 | 5251 | TF3710_ERR_INVALID_PORT_GROUP | Invalid ADS port type |
16#00001484 | 5252 | TF3710_ERR_NEW_NODE_FAILED | The new node has failed |
16#00001485 | 5253 | TF3710_ERR_APPEND_BUFFER_FAILED | Writing to the node has failed |
16#00001486 | 5254 | TF3710_ERR_MISSING_NODE | Node missing |
16#00001487 | 5255 | TF3710_ERR_PARSE_ERROR | Parsing has failed |
16#0000148D | 5261 | TF3710_ERR_PORT_ALREADY_EXIST | ADS port is still present |
16#0000148E | 5262 | TF3710_ERR_PORT_OPEN_FAILED | Opening the ADS port has failed |
16#0000148F | 5263 | TF3710_ERR_INVALID_TARGET_ID | AmsNetID of the target system is invalid |
16#00001490 | 5264 | TF3710_ERR_UNDEFINED_TARGET_PORT | ADS port of the target system is invalid |
16#00001491 | 5265 | TF3710_ERR_CONNECTION_FAILED | Failed to connect to the router |
16#00001492 | 5266 | TF3710_ERR_NO_PORT_OPENED | Port is not open |
16#00001493 | 5267 | TF3710_ERR_DISCONNECT_FAILED | Disconnect from router has failed |
16#00001494 | 5268 | TF3710_ERR_READ_STATE_REQUEST_FAILED | Read state request has failed |
16#00001495 | 5269 | TF3710_ERR_VARHANDLE_FAILED | Loading var handler has failed |
16#00001496 | 5270 | TF3710_ERR_VARHANDLE_ALREADY_EXIST | Var handler is already present |
16#00001497 | 5271 | TF3710_ERR_VARHANDLE_RELEASE_FAILED | Releasing var handler has failed |
16#00001498 | 5272 | TF3710_ERR_VARHANDLE_ALREADY_RELEASED | Var handler has already been released |
16#00001499 | 5273 | TF3710_ERR_INVALID_VAR_HANDLER | Var handler is invalid |
16#0000149A | 5274 | TF3710_ERR_MISSING_ROUTE | ADS route is not available |
16#0000149B | 5275 | TF3710_ERR_CONNECTION_ALREADY_EXISTS | The connection is already established |
16#000014A6 | 5286 | TF3710_ERR_EMPTY_SYMBOL_TABLE | Currently no symbols available in table |
16#000014A7 | 5287 | TF3710_ERR_MISSING_TARGETS | Target systems are missing |
16#000014A8 | 5288 | TF3710_ERR_TYPESYSTEM_PROVIDER_FAILED | The TypeSystem provider has failed |
16#000014A9 | 5289 | TF3710_ERR_TYPERESOLVERPROXY_FAILED | The TypeResolverProxy has failed |
16#000014AA | 5290 | TF3710_ERR_TYPERESOLVERPROXY_LOAD_GUID_FAILED | Loading of TC-GUID has failed. |
16#000014AB | 5291 | TF3710_ERR_TYPERESOLVERPROXY_LOAD_TYPE_COLLECTION_FAILED | Loading of TypeCollection has failed. |
16#000014AC | 5292 | TF3710_ERR_TYPERESOLVERPROXY_SYMBOL_GUID_ERROR | GUID is invalid |
16#000014AD | 5293 | TF3710_ERR_LVTYPEDESCRIPTOR_INVALID_ELEMENT_RANGE | Number of elements in the TypeResolver do not match. |
16#000014AE | 5294 | TF3710_ERR_LVTYPEDESCRIPTOR_TYPE_NOT_SUPPORTED | Data type is not currently supported |
16#000014AF | 5295 | TF3710_ERR_LVTYPEDESCRIPTOR_INVALID_ARRAY_SYMBOLINFO | Elements are missing in the array data type |
16#000014B0 | 5296 | TF3710_ERR_LVTYPEDESCRIPTOR_MISSING_ARRAY_SYMBOLINFO_ELEMENTS | Symbol info for array data type is invalid |
16#000014B1 | 5297 | TF3710_ERR_LVTYPEDESCRIPTOR_MISSING_ARRAY_BASE_TYPE | Array data type has no base type |
16#000014B2 | 5298 | TF3710_ERR_LVTYPEDESCRIPTOR_LOAD_FAILDED | Loading of TypeResolver has failed |
16#000014B3 | 5299 | TF3710_ERR_LVTYPEDESCRIPTOR_INVALID_PRIMARY_TYPE | The primary data type is invalid |
16#000014B4 | 5300 | TF3710_ERR_LVTYPEDESCRIPTOR_TYPE_UNINITIALIZED | TypeResolver is not initialized |
16#000014C4 | 5316 | TF3710_ERR_LVTYPEDESCRIPTOR_INVALID_CLUSTER_SYMBOLINFO | Symbol info for cluster data type is invalid |
16#000014C5 | 5317 | TF3710_ERR_LVTYPEDESCRIPTOR_NON_CLUSTER_TYPE | Data type is not of the LabVIEW™ cluster data type |
16#000014C6 | 5318 | TF3710_ERR_LVTYPEDESCRIPTOR_INVALID_CLUSTER_SYMBOLPOSITION | Elements are missing in the cluster data type |
16#000014D4 | 5331 | TF3710_ERR_LVTYPEDESCRIPTOR_INVALID_TIMESTAMP_VALUE | Invalid TC timestamp value |
16#000014D5 | 5332 | TF3710_ERR_LVTYPEDESCRIPTOR_UNSUPORTED_TIMESTAMP | This TC timestamp data type is currently not supported |
16#000014D9 | 5337 | TF3710_ERR_LVTYPEDESCRIPTOR_TYPE_SIZE_MISMATCH | Data types are not identical |
16#000014DA | 5338 | TF3710_ERR_LVTYPEDESCRIPTOR_TYPE_MISMATCH | Data types are not identical |
16#000014DB | 5339 | TF3710_ERR_LVTYPEDESCRIPTOR_DATA_SIZE_MISMATCH | Data type content does not match |
16#00001504 | 5380 | TF3710_ERR_TYPEGENERATOR_SUBTYPE_NOT_FOUND | TypeGenerator cannot find the SubType or the BaseType |
16#00001519 | 5401 | TF3710_ERR_READ_REQUEST_FAILED | Read request has failed |
16#0000151A | 5402 | TF3710_ERR_INVALID_READ_BUFFER | ADS raw data incorrectly packed |
16#0000151B | 5403 | TF3710_ERR_INVALID_READ_DATA_FORMAT | ADS raw data invalid |
16#0000151C | 5404 | TF3710_ERR_NOTIFICATION_HANDLER_FAILED | Notification handler has failed |
16#0000151D | 5405 | TF3710_ERR_ATLEAST_ONE_MISSED_NOTIFICATION | At least one/several notifications is/are not received correctly |
16#0000151E | 5406 | TF3710_ERR_NOTIFICATION_REQUEST_FAILED | Notification request has failed |
16#0000151F | 5407 | TF3710_ERR_UNSUPPORTED_NOTIFICATION_MODE | Notification mode is currently not supported |
16#00001520 | 5408 | TF3710_ERR_NOTIFICATION_BUFFER_FAILED | Buffered notification has failed |
16#00001534 | 5428 | TF3710_ERR_WRITE_REQUEST_FAILED | Write request has failed |
16#00001565 | 5429 | TF3710_ERR_WRITE_BUFFER | Write buffer invalid |
16#FFFFE05C | -8100 | TF3710_ERR_INVALID_HANDLE | Invalid handle |
16#FFFFE05B | -8101 | TF3710_ERR_HANDLE_IN_USE | The handle is still in use |
16#FFFFE052 | -8110 | TF3710_ERR_INVALID_ARRAY | Invalid array |
0xFFFFE051 | -8111 | TF3710_ERR_INVALID_ARRAY_SIZE | Array size invalid |
0xFFFFE050 | -8112 | TF3710_ERR_SYMBOL_NOT_FOUND | Symbol not found |
0xFFFFE04F | -8113 | TF3710_ERR_LVBUFFER_NOT_REGISTERED | LVBuffer was not registered |