Error Codes
Error Code (dec) | Error Code (hex) | Description | Hints |
---|---|---|---|
0 | 0000 | Operation successful | - |
-1 | FFFF | ML server timeout | Increase the timeout argument of your request. Check, that the TcMlServer service is running. |
-3 | FFFD | ML server malformed data | - |
-5 | FFFB | PLC protocol error | Make sure to call the methods of the FB in a canonical order, i.e. make sure the FB is configured before making inference calls. |
-8 | FFF8 | Invalid AMS Net ID | Check the syntactical correctness of the provided AmsNetId. |
-9 | FFF7 | Input pointer is null | Check the validity of the input data pointer provided to the predict methods. |
-11 | FFF5 | Output pointer is null | Check the validity of the output data pointer provided to the predict methods. |
-13 | FFF3 | Batch size is zero | Provide a valid batch size (>= 1). |
-15 | FFF1 | Input size is zero | Provide a valid input data size (>0). |
-17 | FFEF | Output size is zero | Check your installation of TF3830. |
-18 | FFEE | Driver instantiation failed | Check your installation of TF3830. |
-20 | FFEC | Driver state propagation to state OP failed | Check the validity and integrity of your model file (existing path, valid file format). |
-22 | FFEA | Driver loading failed | Check your installation of TF3830. |
-24 | FFE8 | Driver state depropagation failed | Check your installation of TF3830. |
-26 | FFE6 | Driver parameter configuration failed | TwinCAT-internal error |
-28 | FFE4 | Could not instantiate file accessor | TwinCAT-internal error |
-30 | FFE2 | Could not propagate file accessor state | TwinCAT-internal error |
-32 | FFE0 | Could not access model file | Check the validity of your model file (existing path, valid file format). |
-34 | FFDE | Mismatch in read model file bytes | TwinCAT-internal error |
-36 | FFDC | Could not parse model file | Check the integrity of your model file. |
-38 | FFDA | String buffer overflow | Check the integrity of your model file, especially the length of the contained model hash. |
-40 | FFD8 | Could not find model config in file | Check the integrity of your model file, especially the defined model configuration. |
-42 | FFD6 | Could not retrieve model attributes | Check the integrity of your model file, especially the availability of a model hash. |
-43 | FFD5 | ADS server connection error | ADS messages could not be sent. Check integrity of AmsRouter. |
-44 | FFD4 | Engine mismatch | The model file you intended to load is not designated for the TcMlServer. |
-45 | FFD3 | Invalid CST attribute name | Check the name of the attribute in your model file or your query. The name must not be empty. |
-47 | FFD1 | CST attribute retrieval failed | The queried attribute could not be found. Check the queried attribute name in query and model file. |
-49 | FFCF | CST attribute invalid buffer | Check the destination pointer provided to the retrieval function. Must not be a null pointer. |
-50 | FFCE | Versioned model could not be resolved | Check the valditiy of the model version you are querying. |
-51 | FFCD | If a PLC online change is detected, a running predict is discarded with the error |
|
-101 | FF9B | Invalid PLC request variant | Internal error |
-102 | FF9A | Invalid device index | Verify the device index provided in prediction parameters of the FB. |
-103 | FF99 | Invalid request data | Internal error |
-201 | FF37 | Invalid data | Internal error |
-202 | FF36 | Invalid model type | Requested tensor of unsupported datatype. See log files. |
-206 | FF32 | Invalid model | The provided model file is not supported. check especially, that no dimension parameters are left except for an optional batch dimension. |
-300 | FED4 | Invalid execution provider | The requested execution provider is invalid. Make sure to select an EP from the enum E_ExecultionProvider. |
-302 | FED2 | Unsupported execution provider | The requested execution provder is valid but not supported on your system (for instance due to a lack of GPU support). |
-400 | FE70 | Session config file not found | Internal error |
-402 | FE6E | Environment config file not found | Internal error |
-404 | FE6C | Run config file not found | Internal error |
-406 | FE6A | Server config file not found | Internal error |
-408 | FE68 | Device config files not found | Internal error |
-500 | FE0C | Invalid session config file | Internal error |
-502 | FE0A | Invalid environment config file | Internal error |
-504 | FE08 | Invalid run config file | Internal error |
-506 | FE06 | Invalid server config file | Internal error |
-508 | FE04 | Invalid device config files | Internal error |
-600 | FDA8 | Targeted inference provider unavailable | Internal error |
-602 | FDA6 | Inference provider session timeout | Increase the session timeout in the prediction parameters. |
-701 | FD43 | Dynamic loaded library not found | Internal error |
-703 | FD41 | Symbol not loadable from dynamic library | Internal error |
-801 | FCDF | Unknown job execution error | Internal error |
-803 | FCDD | Unknown error | Internal error |
-901 | FC7B | Failed backend execution | Internal error |
-1100 | FBB4 | License server connection error | Internal licensing error |
-1102 | FBB2 | License server ADS error | Internal licensing error |
-1104 | FBB0 | License ADS error | Internal licensing error |
-1106 | FBAE | License invalid | Make sure, that a license TF3820 is available. |
-1108 | FBAC | License invalid unknown | Internal licensing error |
-1201 | FB4F | Expected tensor collection type | Make sure, that only types defined in the PLCopen files generated by the Beckhoff model management products is used. Do not manipulate the contained header |
-1203 | FB4D | Mismatching tensor collection hashes | Make sure, that only types defined in the PLCopen files generated by the Beckhoff model management products is used. Do not manipulate the contained header |
-1205 | FB4B | Invalid tensor collection header | Make sure, that only types defined in the PLCopen files generated by the Beckhoff model management products is used. Do not manipulate the contained header |
-1207 | FB49 | Tensor collection offset feature not supported | Make sure, that only types defined in the PLCopen files generated by the Beckhoff model management products is used. Do not manipulate the contained header |
-1209 | FB47 | Internal allocation special type header | Internal error |
-1300 | FAEC | Server startup cannot build log directory | No Logs directory available and could not be generated. |
-1801 | F8F7 | NVIDIA NVML library function failure | Make sure the Nvidia nvml.dll is avilable. |
-1803 | F8F5 | NVIDIA NVML library extraction failure | Make sure the Nvidia nvml.dll is avilable. |
-1901 | F893 | NVIDIA CUDA library function failure | Make sure the Nvidia cuda.dll is available. |
-1903 | F891 | NVIDIA CUDA library extraction failure | Make sure the Nvidia cuda.dll is available. |
-2000 | F830 | Model registry file storage error | Internal error |
-2002 | F82E | Model registry file deletion error | Internal error |
-2003 | F82D | Model registry invalid reference | Internal error |
-2004 | F82C | Model registry entry failed to load model | Internal error |
-2006 | F82A | Model registry inconsistent model hashes | Internal error |
-2008 | F828 | ADS could not open remote file | Make sure, that an .onnx file with the same name as your .json model description file is located in the same directory. |
-2010 | F826 | ADS could not retrieve size of remote file | Internal error |
-2012 | F824 | ADS could not load remote file | Make sure, that your AMS router has sufficient memory for your .onnx file. |
-2014 | F822 | ADS could not close remote file | Internal error |
-2018 | F81E | ADS could not open client port | Make sure your TwinCAT installation is valid. |
-2201 | F767 | Buffer base is null | Internal error |
-2203 | F765 | Not enough memory for head | Internal error |
-2205 | F763 | Buffer out of memory | Internal error |
-2207 | F761 | Buffer cannot read from null | Internal error |
-2209 | F75F | Buffer cannot write to null | Internal error |
-2211 | F75D | Buffer corrupted with invalid string | Internal error |
-2020 | F81C | Insufficient AMS Router Memory on Client | Increase Router Memory on the Client system |
-2022 | F81A | Insufficient AMS Router Memory on Server | Increase Router Memory on the Server system |
-2024 | F818 | Could not read router memory on client | Internal error |
-2026 | F816 | Could not read router memory on server | Internal error |
-2301 | F703 | Invalid CUDA setup detected | Check your CUDA and cuDNN installation. |