Error Codes (Simulation Interface Toolkit)
- Updated2023-02-21
- 4 minute(s) read
The Simulation Interface VIs and dialog boxes can return the following error codes. Refer to the KnowledgeBase for more information about correcting errors in LabVIEW.
| Code | Description |
|---|---|
| 14104 | The model DLL failed to load. The specified path might be invalid, or the specified file is not a valid model DLL. Select Tools»SIT Connection Manager from the pull-down menu to launch the SIT Connection Manager dialog box and specify a valid model DLL. |
| 14105 | The model DLL is not compatible with the current version of SIT. You must rebuild the model DLL with the current version of SIT before you can use the model DLL. |
| 14106 | The execution host reported an error. |
| 14107 | Could not create the data logging file. The specified filename might be invalid. Select Tools»SIT Connection Manager to display the SIT Connection Manager dialog box. Under Data Logging, select the data log configuration page and enter a valid filename in the Data Log Filename field . |
| 14108 | Cannot probe some signals. The signals might not exist in the model. |
| 14109 | The model failed to receive expected model input data in time. |
| 14110 | TDMS data logging only supports fixed-step solvers. Switch to a fixed-step solver, disable data logging, or log data as text to resolve this error. |
| 14112 | The TDMS playback file could not be found at the specified location. Select Tools»SIT Connection Manager to launch the SIT Connection Manager dialog box and specify a valid TDMS playback file path on the File Playback configuration page. |
| 14113 | The version of the SIT Server and the version of the client are not compatible. |
| 14119 | An error occurred in the model DLL. |
| 14120 | The base rate loop did not finish in time. The combined time of computing the model and performing input and output is too long. Increase the model time step, switch to a simpler solver, or reduce the number of inputs and outputs used. |
| 14121 | One or more simulation model tasks did not finish in time. The combined time of computing the task and higher priority tasks in the model, together with performing input and output, is too long. Increase the model time step, switch to a simpler solver, or reduce the number of inputs and outputs used. |
| 14131 | Data loss occurred while logging data. The background loop did not have enough time to process the data in the logging buffer. To help avoid future data loss, try reducing the number of signals to log or increasing the logging decimation for these channels. You also can choose to log only the last N samples to achieve lossless data logging. |
| 14132 | The logging configuration data does not match the logging configuration data used to create the log file. The specified channel is new, but belongs to a channel group that already contains time channel data. The time channel values will not correspond to the specified channel. To avoid this issue, use unique filenames for each data log configuration, or do not use the same channel group name in separate data log configurations that share a file. |
| 14151 | Microsecond timing is not enabled. Microsecond timing allows the National Instruments Scheduler to take advantage of the microsecond timing source. Complete the following steps to enable microsecond timing. 1. Open an FTP connection to the real-time (RT) target and download the c:\ni-rt.ini file to the host. 2. Edit the ni-rt.ini file and locate the MicrosecondTimingMode key under the [SYSTEMSETTINGS] section. Change the value of this key from 0 to 1. 3. Save ni-rt.ini to the host, upload the saved file back to the RT target, and reboot the RT target. |
| 14152 | File transfer failed for model DLL. An error occurred in the attempt to FTP the model DLL to the RT target. A possible reason for this is a permissions conflict on the target. |
| 14153 | An error occurred while attempting to deploy the driver project and VI, or the operation was cancelled by the user. Verify that you are using the correct IP address, the target is turned on, and the Target Access permissions are set correctly. |
| 14154 | The server type specified by the client and the server type of the SIT Server do not match. For example, the client VI might be expecting a SIT driver VI, but the server is already running in the simulation environment with the same port number. If the intended execution host is the simulation environment, ensure there are no SIT driver VIs running. If the intended server is a driver VI on Localhost, ensure that the SIT Server is not running in the simulation environment on the local machine. If the intended server is a RT target, ensure that the IP address specifies a LabVIEW Real-Time Target. You can either stop the other SIT Server or use a different port number. |
| 14155 | Data loss occurred between the SIT Server and the host VI. Refer to the Halting Simulations on Data Loss topic of the LabVIEW Help for information about reducing the possibility of data loss. |
| 14156 | The specified driver VI name does not match the SIT naming conventions. Driver VIs must be named modelname_Driver.vi, where modelname is the name of the model the driver VI is configured to run. |
| 14160 | The driver VI was created in a previous version of SIT. You must update the driver VI before it can be rebuilt. |
| 14161 | An I/O plugin attempted to add an invalid channel name. Channel names within a device cannot be duplicated, and should not start or end with whitespace. |
| 14198 | The communication settings in the configured host VI are invalid. You have specified to not launch the SIT Connection Manager dialog box to modify these settings. |
| 14199 | The communication settings in the configured host VI are invalid. You have specified to launch the SIT Connection Manager dialog box to modify these settings. |