| << Click to Display Table of Contents >> Navigation: NmxDLL Referenz > API (programming interface) > Function Return Codes (NMX_STATUS) | 
The function calls of the NMX DLL almost all have the same return value of the type NMX_STATUS. Most of the return values will rarely occur. The most common ones are shown in bold in the following table.
Note for the .Net DLL: In the .Net DLL, the return values are represented by the enum type NMX_MSTATUS instead by a binary value. Therefore NST_SUCCESS is for example NMX_MSTATUS.SUCCESS.
The return values are defined as follows:
| Return value | Hex representation | Description | Possible reasons (excerpt) | 
|---|---|---|---|
| NST_SUCCESS | 0x00000000 | Everything OK. | |
| NST_HANDLE_INVALID | 0xF0000000 | Invalid handle. | •Connection has not been established yet. •Connection has already been closed. | 
| NST_HANDLE_TOO_MANY | 0xF0000001 | Too many handles exists. | Too many connections have been opened. The limit is 8. | 
| NST_CONNECT_OPEN_FAILED | 0xF0000010 | Failed connecting to a device. | •Device is not connected to the PC. •Network settings (IP address & Port numbers) are invalid. | 
| NST_NOT_CONNECTED | 0xF0000011 | No connection established. | |
| NST_NOT_AVAILABLE | 0xF000001F | The requested data is not available. | No connection established or invalid data received from the device. | 
| NST_SEND_SIZE_TOO_LARGE | 0xF0000020 | Too much data to send. | |
| NST_DX_TIMEOUT_1 | 0xF0000021 | A data exchange timeout occurred. | •The network connection has been interrupted shortly or permanently. •PC timing is too slow, e.g. due to an application causing 100% CPU load or a virtual machine is used. | 
| NST_DX_TIMEOUT_2 | 0xF0000022 | ||
| NST_DX_TIMEOUT_COMMON | 0xF0000023 | ||
| NST_INV_RESP | 0xF0000030 | Response from the device is invalid. | •Device firmware is outdated. •Device type not supported. | 
| NST_RESP_ERR | 0xF0000031 | Response from the device contained an error code. | •Device firmware is outdated. •Newer DLL version available. | 
| NST_REQ_VERS_NOSUPPORT | 0xF0000032 | Request not supported by the device. | •Device does not support this functionality. •Device firmware is outdated. | 
| NST_BOXNO_INVALID | 0xF0000040 | The box number provided in the parameters list is invalid. | Invalid box number used. Box numbering starts at 0. E.g. 5 Boxes -> Box numbers 0..4. | 
| NST_CHANNEL_INVALID | 0xF0000041 | The measurement channel number provided in the parameters list is invalid. | Invalid measurement channel number used. Channel numbering starts at 0. E.g. 8 Channels -> Channel numbers 0..7. | 
| NST_DIGIIN_INVALID | 0xF0000042 | The digital I/O byte number is invalid. | Invalid I/O byte number used. Byte numbering starts at 0. E.g. 2 I/O Bytes -> Byte numbers 0..1. Note that I/Os are counted byte-wise. E.g. 16 digital inputs are 2 bytes. | 
| NST_DIGIOUT_INVALID | 0xF0000043 | ||
| NST_STRING_INVALID | 0xF0000048 | String invalid | The string provided in the parameters is invalid, e.g. too short. | 
| NST_DATA_TOOLARGE | 0xF0000048 | Data is too large. | •Data provided in the parameters list is too large. •Internal DLL error. Check for newer DLL version. | 
| NST_NOTIFICATION_UNKNOWN | 0xF0000050 | Unknown notification type. | Check for valid notification types. | 
| NST_SAMPLING_TOOMANY_ELEMENTS | 0xF0000100 | Too many sampling elements defined. | Too many sampling elements have been added. See limitations. | 
| NST_SAMPLING_GUID_INVALID | 0xF0000101 | The internal sampling GUID is invalid. | Sampling configured in parallel by other software or instance. | 
| NST_SAMPLING_NO_ELEMENTS | 0xF0000102 | No sampling elements have been added. | No sampling elements have been added prior to preparing / starting the sampling. | 
| NST_SAMPLING_DOUBLE_ELEMENT | 0xF0000103 | Sampling element has already been added. | One or more of the sampling element, which shall be added, is already in the sampling element list. Each element must only be added once. | 
| NST_SAMPLING_INVALID_CHANNELNO | 0xF0000104 | The channel number to be added is invalid. | Invalid measurement channel number used. Channel numbering starts at 0. E.g. 8 Channels -> Channel numbers 0..7. | 
| NST_SAMPLING_INVALID_ELEMENTNO | 0xF0000105 | The sampling element number is invalid. | Not enough sampling elements have been added before. Element numbering starts at 0. | 
| NST_SAMPLING_ALREADY_STARTED | 0xF0000106 | Sampling has already been started. | Sampling has already been prepared / started before. Stop and reset current sampling. | 
| NST_SAMPLING_ELEMENTS_NOACCEPT | 0xF0000120 | The list of sampling elements has not been accepted by the device. | Measurement system setup has been changed without reconnecting manually (e.g. number of measurement channels is different). | 
| NST_SAMPLING_INVALID_PERIOD | 0xF0000121 | Invalid sampling period. | The sampling period requested is not supported by the measurement system. The maximum speed can be requested from the device. See also users manual. | 
| NST_SAMPLING_INVALID_MAXSAMPLES | 0xF0000122 | Invalid maximum number of measurements samples. | •Sampling has been prepared with 0 samples. •Error from device. | 
| NST_SAMPLING_START_FAILED | 0xF0000130 | Starting sampling failed. | Error code from device. | 
| NST_SAMPLING_START_CONFIG | 0xF0000131 | Sampling configuration invalid. | •Sampling has not been prepared. •Device has been reset. | 
| NST_SAMPLING_START_NOTPREPARED | 0xF0000132 | Sampling has not been prepared. | Sampling has not been prepared. | 
| NST_SAMPLING_NO_DATA_AVAILABLE | 0xF0000140 | No data is available for readout. | No new sampling data available. | 
| NST_SAMPLING_READ_DATA_ERROR | 0xF0000141 | Error reading sampling data. | |
| NST_SAMPLING_NOTENOUGH_MEMORY | 0xF00001F8 | Not enough memory for allocating sampling buffers. | •Buffer size too large. •Heap memory too small. | 
| NST_SAMPLING_INTERNAL | 0xF00001FF | Internal sampling error. | |
| NST_HLSAMPLING_INVALID_FILTPERIOD | 0xF0000200 | Invalid filter period. | |
| NST_INTERNAL_SEQ | 0xF0001000 | Internal sequence error. | |
| NST_INVALID_EVENT | 0xF0001001 | Invalid internal event. |