RF and MI Shared Errors Error Code Family
Below are all of the Error Codes that belong to the RF and MI Shared Errors Error Code Family (see Error List for list of Families).
| Code | Description |
|---|---|
| -1074100304 | Unable to import the attribute configuration. The channels specified by the attribute configuration that you requested to import are not compatible with this session. The configuration must have the same number of channels as the session. |
| -1074100303 | Unable to import the attribute configuration. The attribute configuration that you requested to import is not supported with this instrument or instruments. |
| -1074100302 | Unable to import the attribute configuration. The input data is invalid. |
| -1074100301 | Unable to import the attribute configuration. You requested to import an attribute configuration that is newer than the driver version. |
| -1074100300 | Unable to import the attribute configuration. The specified attribute configuration is not compatible with this combination of instrument(s) and channel(s). |
| -1074100299 | Unable to import the attribute configuration. The buffer is too small. |
| -1074100298 | Unable to import the attribute configuration. The input data is invalid. |
| -1074100297 | Unable to import the attribute configuration. The input data is invalid. |
| -1074100296 | Unable to import the attribute configuration because doing so would require setting conflicting attribute values. |
| -1074099264 | The specified pin or pin group name was not found in the pin map. |
| -1074099263 | Pin or pin group name contains an invalid character. Only alphanumeric characters and underscores are allowed in pin and pin group names. The first character must be a letter or underscore. |
| -1074099262 | The specified pin or pin group name already exists. |
| -1074099261 | The channel map has already been configured. |
| -1074099260 | The specified pin and site combination has already been mapped to a channel. |
| -1074099259 | The pin list specifies a site number on a system pin or on a pin group that contains a system pin. Ensure that you specify only DUT pins by using a specific site number in pin lists. |
| -1074099258 | Invalid pin index. |
| -1074099257 | The pin map has already been configured. |
| -1074099256 | The channel map configuration is not complete. Ensure that you call niDigital End Channel Map after you call niDigital Map Pin to Channel to map pins and sites to instrument channels. Additionally, ensure that you specify the number of sites before you call niDigital Create Channel Map to map pins and sites. |
| -1074099255 | The specified channel has already been mapped to a pin. |
| -1074099254 | The pin group includes the same pin multiple times. Ensure that the pin group includes a pin only once. |
| -1074099253 | The channel list includes the same pin multiple times. Ensure that the channel list includes a pin only once. |
| -1074099252 | The specified pin map file does not list the device alias used to create the niDigital session. Ensure the pin map file includes the device alias in the instrument list section. |
| -1074099251 | The number of sites mapped to the instrument exceeds the maximum number of sites the instrument allows. Ensure that the pin map does not assign more than the maximum allowed number of sites to a single digital pattern instrument. |
| -1074099250 | The site list contains an invalid site name. |
| -1074099249 | The site list specifies the same site multiple times. Ensure that the site list specifies a site only once. |
| -1074099248 | The site numbers in the pin map are not valid. Site numbers must be unique and contiguous starting at 0. |
| -1074099247 | The channel number is invalid. |
| -1074099246 | Instruments have already been added to the pin map. Instruments can only be added to a pin map once. |
| -1074099245 | The specified instruments and channels are invalid. Ensure a number of channels is specified for each instrument. |
| -1074099244 | Duplicate instrument names exist in the specified instruments. Ensure all specified instrument names are unique. |
| -1074099243 | The specified instrument index is invalid. |
| -1074099242 | Invalid pin group index. |
| -1074099241 | This operation is not supported when there are multiple selected instruments in the pin map. |
| -1074099216 | The Debug Session settings must be identical for all instruments in a session. Verify and/or change the Debug Session configuration settings using InstrumentStudio, the Digital Pattern Editor, or the System Configuration API. |
| -1074099215 | The driver does not support multi-instrument sessions that use instruments of different models. Ensure that all instruments in the multi-instrument session are identical models. |
| -1074099214 | Specified pin list or channel list is invalid. Ensure that the pin list references valid pins from the pin map or that the channel list references valid channels on instruments included in this session. |
| -1074099213 | Function or method not supported when using multi-instrument sessions. |
| -1074099212 | Attribute or property not supported when using multi-instrument sessions. |
| -1074099211 | The specified channel string refers to more than one channel. Specify only one channel at a time. |
| -1074099210 | Cannot use the specified terminal name because multiple instruments in the session could contain a terminal with that name. Specify the terminal name in its fully qualified form using the supported syntax (for example, "/PXI1Slot2/PXI_Trig0"). |
| -1074099209 | The specified instrument string refers to more than one instrument. Specify only one instrument at a time. |
| -1074099208 | Getting a property failed because the pins specified in the channel list parameter do not correspond to any instrument channel(s). Pins on disabled sites and pins that are not mapped to an instrument channel are ignored when getting channel properties. Ensure that the pin list specified contains at least one pin that is mapped to an instrument channel on an enabled site. |
| -1074099207 | Invalid value for parameter or property when using multi-instrument sessions. |
| -1074099206 | The driver does not support simulated multi-instrument sessions with an empty resource name. Either specify the Model and BoardType in the DriverSetup string or use the names of instruments present in your system from which to infer the Model and BoardType. |
| -1074099205 | Cannot use instruments from different chassis in the same multi-instrument session. Ensure each multi-instrument session only includes instruments from the same chassis. |
| -1074099204 | Getting an attribute failed because a channel name was used to access this attribute. Use an instrument name instead. |
| -1074098960 | Driver setup string is invalid. Ensure that the driver setup string follows the pattern "[tag0]:[value0]; [tag1]:[value1]" or "RESOURCENAME:[dev0];[tag0]:[value0]&RESOURCENAME:[dev1];[tag1]:[value1]". |
| -1074098959 | The specified resource name is not found in the driver setup string. Ensure the driver setup string includes all desired resources and follows the pattern "[tag0]:[value0];[tag1]:[value1]" or "RESOURCENAME:[dev0];[tag0]:[value0]&RESOURCENAME:[dev1];[tag1]:[value1]". |
| -1074098958 | The specified tag or value is invalid. Ensure the tag and value are not empty and that the tag is not repeated. |
| -1074098957 | The values of the specified tag must be identical for all instruments in a session. Ensure the driver setup portion of the option string is identical for all instruments in a session. |
| -1074098176 | Switch device has been disabled to prevent it from exceeding the simultaneous relay drive limit for a slot.
To recover, call DAQmx Disconnect All or reset the device. The device can be reset either programmatically or with Measurement & Automation Explorer. Refer to your device documentation for more information. |
| -1074098175 | The 5 V fuse on your NI SwitchBlock carrier is blown. Refer to your documentation for help with replacing the fuse. |
| -1074098174 | An expansion bridge has been inserted or removed while your system is powered on. This can lead to unexpected behavior. Restart your system. |
| -1074098173 | One or more cards for your NI SwitchBlock device have been inserted and/or removed while your system was powered on. This can lead to unexpected behavior. Restart your system. |
| -1074098172 | Self-calibration failed. Contact NI technical support at ni.com/support. |
| -1074098171 | Self-calibration failed to converge. Performing an external calibration may fix the problem. |
| -1074098170 | Self-calibration failed. Performing an external calibration may fix the problem. |
| -1074098169 | Switch device has been disabled to prevent it from exceeding the power limit for the carrier.
To recover, call DAQmx Disconnect All, or reset the device. The device can be reset either programmatically or by using Measurement & Automation Explorer. Refer to your device documentation for more information. |
| -1074098168 | Analog bus needed by the current operation is invalid. Verify that all carriers connected using expansion bridge(s) are functioning properly. |
| -1074098167 | Analog bus line(s) in use by another device. Verify other devices are not currently using the analog bus line(s). If you intend to share the line(s) between devices, ensure the Analog Bus Sharing Enabled property is True for all shared channels. |
| -1074098166 | File specified is already opened for output. NI-DAQmx requires exclusive write access. |
| -1074098165 | TDMS support is not installed or is too old. Use an NI-DAQmx runtime that includes TDMS support, or install a supported version of TDMS from a stand-alone installer. |
| -1074098164 | File specified is already opened for output by another task. Specify a different file path. |
| -1074098163 | Disk is full. Free up disk space, or specify a different file path. |
| -1074098162 | File path specified is invalid, or the file is not a valid TDMS file. Specify the location of a valid TDMS file. |
| -1074098161 | Logging to this file format is not supported by NI-DAQmx. Convert the file to TDMS version 2.0 or later, or specify a different file. |
| -1074098160 | File permission error. You do not have the correct permissions for the file. |
| -1074098159 | Property specified is not supported in conjunction with a conflicting property. |
| -1074098158 | WEP key must be either 10 or 26 characters long. |
| -1074098157 | Improper chassis power levels detected. The -12 V fuse on the device might have blown, or there might be a problem with the -12 V rail on the chassis. Try resetting the device. If the error persists, contact NI. |
| -1074098156 | Improper chassis power levels detected. The +12 V fuse on the device might have blown, or there might be a problem with the +12 V rail on the chassis. Try resetting the device. If the error persists, contact NI. |
| -1074098155 | Improper chassis power levels detected. The +5 V fuse on the device might have blown, or there might be a problem with the +5 V rail on the chassis. Try resetting the device. If the error persists, contact NI. |
| -1074098154 | Improper chassis power levels detected. The +3.3 V fuse on the device might have blown, or there might be a problem with the +3.3 V rail on the chassis. Try resetting the device. If the error persists, contact NI. |
| -1074098153 | Internal serial communication bus failed. Try resetting the device. If the error persists, contact NI. |
| -1074098152 | Device power up failed. Try resetting the device. If the error persists, contact NI. |
| -1074098151 | IP address provided is invalid. IP addresses must be of the form x.x.x.x where x is a number from 0 to 255. |
| -1074098150 | User defined information string entered is of an invalid length. |
| -1074098149 | Property requested was not found. The property is either not supported by the object or has not been set. |
| -1074098148 | Input voltage limits exceeded. Protection circuity disabled the inputs. Ensure proper voltage levels on device inputs. |
| -1074098147 | Scaled waveform is too large. After multiplication by the software scaling factor, the magnitude of each sample must be less than 1.0. |
| -1074098146 | Wireless security setting is invalid. Ensure that all necessary settings are specified. |
| -1074098145 | User defined information string entered exceeds the maximum allowable string length. |
| -1074098144 | Storage specified is not valid or could not be found. |
| -1074098143 | Target storage was altered by another process before the changes could be saved. |
| -1074098142 | Power supply configuration failed.
Reboot or cycle the power on the device. |
| -1074098141 | Firmware for this device is too old.
Upgrade the firmware for this device or downgrade the driver. |
| -1074098140 | Firmware for this device is corrupt. Contact NI for help with this device. |
| -1074098139 | Firmware for this device is too new.
Downgrade the firmware for this device or upgrade the driver. If you need help, visit ni.com/support. |
| -1074098138 | Channel you are triggering on is not enabled.
Enable the trigger source channel. |
| -1074098137 | Calibration procedure has failed to resolve the calibration data format conflict.
Perform a complete external calibration on your device. This may modify the calibration data. |
| -1074098136 | Currently installed driver no longer supports the hardware self-calibration data format.
Either self-calibrate your device (this may modify the calibration data) or downgrade your driver to the version supplied with the device. Older driver versions can also be downloaded from ni.com. If uncertain, contact NI technical support. |
| -1074098135 | Currently installed driver no longer supports the hardware external calibration data format.
Either externally calibrate your device (this may modify the calibration data) or downgrade your driver to the version supplied with the device. Older driver versions can also be downloaded from ni.com. If uncertain, contact NI technical support. |
| -1074098134 | Hardware self-calibration data format is newer than the latest revision supported by the currently installed driver.
Either self-calibrate your device (this may modify the calibration data) or upgrade your driver to the version supplied with the device. Driver updates can also be downloaded form ni.com. If uncertain, contact NI technical support. |
| -1074098133 | Hardware external calibration data format is newer than the latest revision supported by the currently installed driver.
Either externally calibrate your device (this may modify the calibration data) or upgrade your driver to the version supplied with the device. Driver updates can also be downloaded from ni.com. If uncertain, contact NI technical support. |
| -1074098132 | Currently installed driver no longer supports this revision of the hardware.
Downgrade your driver to the version supplied with the device. Older driver versions can also be downloaded from ni.com. |
| -1074098131 | Hardware revision is newer than the latest revision supported by the currently installed driver.
Upgrade your driver to the version supplied with the device. Driver updates can also be downloaded from ni.com. |
| -1074098130 | Waveform length must be a multiple of the waveform quantum. |
| -1074098129 | Digital Modulation User Defined Waveform is invalid. |
| -1074098128 | You cannot use the Ref In/Out connector as both an input and an output at the same time. |
| -1074098127 | Device does not support both analog modulation and digital modulation simultaneously. |
| -1074098126 | Enumerated value specified is not a valid value for that enumeration.
The enumerated value may have been exported from a later version of NI-DAQmx and is not supported by the version of NI-DAQmx installed on your system. Check the version specified in the file against the installed version of NI-DAQmx. You can upgrade the version of NI-DAQmx installed on your system, or change the value to one supported by the version of NI-DAQmx you have installed. |
| -1074098125 | Device does not support an external calibration password. |
| -1074098124 | Device cannot be accessed. Possible causes:
Device is no longer present in the system. Device is not powered. Device is powered, but was temporarily without power. Device is damaged. Ensure the device is properly connected and powered. Turn the computer off and on again. If you suspect that the device is damaged, contact NI at ni.com/support. |
| -1074098123 | DAQmx Events are not supported in this version of LabVIEW. LabVIEW 8.0 or later is required to use DAQmx Events. |
| -1074098122 | You only can get the specified property while the task is reserved, committed or while the task is running.
Reserve, commit or start the task prior to getting the property. |
| -1074098121 | Property cannot be queried because the task is not running.
Start the task prior to getting the specified property. |
| -1074098120 | Firmware for the device could not be downloaded, and the device cannot be used. This failure is due to a missing or damaged firmware image file.
Reinstall the driver to eliminate this error. |
| -1074098119 | DAQmx tasks cannot provide a source for a Timed Loop and contain a DAQmx Signal Event at the same time. DAQmx Signal events include the Counter Output event, the Sample Complete Event, the Sample Clock Event, and the Digital Change Detection event.
Tasks that contain a Timed Loop can contain DAQmx Events as long as the events are not a type of DAQmx Signal Event. See documentation for more details. |
| -1074098118 | Task could not be started, because the driver could not write enough data to the device. This was due to system and/or bus-bandwidth limitations.
Reduce the number of programs your computer is executing concurrently. If possible, perform operations with heavy bus usage sequentially instead of in parallel. If you can't eliminate the problem, contact NI support at ni.com/support. |
| -1074098117 | Data Voltage Low Level and Data Voltage High Level must be within a common voltage range. |
| -1074098116 | Simulation disabling is not supported for this device, because it was created as a simulated device. |
| -1074098115 | Device has shut down because a sensor on the device detected a temperature in excess of the maximum recommended operating temperature. Possible causes incude excessive current on the device channels and inadequate chassis cooling.
To use the device again, reduce the current and/or improve the chassis cooling. Ensure that the device has cooled and reset the device (either programmatically or through Measurements & Automation Explorer). |
| -1074098114 | Requested Sample Clock Rate cannot be generated given the specified external Sample Clock Timebase Rate.
To keep the specified Sample Clock Timebase Rate, use one of the Sample Clock Rates that can be generated. |
| -1074098113 | Specified gain is not supported. |
| -1074098112 | Task used as the timing source for a Timed Loop was started before the Timed Loop was executed.
Let the Timed Loop start the task, or use the task without the Timed Loop. |
| -1074098111 | Timebase calibration algorithm failed to converge within the required tolerance.
Ensure that the reference frequency is stable and that the frequency passed to the calibration VI or function is correct. Repeat the external timebase calibration. If the error persists, contact NI Technical Support. |
| -1074098110 | Measurement taken during calibration produced an invalid AO gain calibration constant.
If performing an external calibration, ensure that the reference voltage passed to the calibration VI or function is correct. Repeat the calibration. If the error persists, contact NI Technical Support. |
| -1074098109 | Measurement taken during calibration produced an invalid AO offset calibration constant.
If performing an external calibration, ensure that the reference voltage value passed to the calibration VI or function is correct. Repeat the calibration. If the error persists, contact NI Technical Support. |
| -1074098108 | Pulse low time specified is not supported for this device given the Counter Timebase Rate. |
| -1074098107 | NI-DAQmx has detected a corrupt installation. Re-install NI-DAQmx. If you continue to receive this message, contact NI for assistance. |
| -1074098106 | Device has shut down because a sensor on the device detected a temperature above the device's maximum recommended operating temperature.
To use the device again, either turn the chassis/computer off until the device has cooled, or ensure the device has cooled, and reset the device (either programmatically or through Measurements & Automation Explorer). |
| -1074098105 | Multiple samples cannot be written using a single sample write.
Ensure the waveform contains only a single sample. |
| -1074098104 | Switch device has been disabled to prevent it from exceeding its simultaneous relay drive limit.
To recover, call DAQmx Disconnect All, or reset the device. The device can be reset either programmatically or by using Measurement & Automation Explorer. |
| -1074098103 | Requested operation is not supported because the Reference Clock Source is "None". |
| -1074098102 | Waveform name is the same as an existing script name.
Make sure that the waveform name is different from the names of previously written scripts. |
| -1074098101 | Pause and reference triggers are both configured, which is not supported in this task. |
| -1074098100 | Hardware clocking error occurred.
If you are using an external sample clock, make sure it is connected and within the jitter and voltage level specifications. Also, verify that the rate of the external clock matches the specified clock rate. If you are generating your clock internally, contact NI Technical Support. |
| -1074098099 | Output generation was aborted by the reverse power protection circuitry of the device. Either the output signal exceeded the output power limit, or power was being driven back into the output of the device by an external source. Correct the problem, then generate the signal again. |
| -1074098098 | Hardware clocking error occurred.
If you are using an external sample clock, make sure it is connected and within the jitter and voltage level specifications. Also, verify that the rate of the external clock matches the specified clock rate. If you are generating your clock internally, contact NI Technical Support. |
| -1074098097 | Acquisition has been stopped to prevent an input buffer overwrite. Your application was unable to read samples from the buffer fast enough to prevent new samples from overwriting unread data.
To avoid this error, you can do any of the following: 1. Increase the size of the buffer. 2. Increase the number of samples you read each time you invoke a read operation. 3. Read samples more often. 4. Reduce the sample rate. 5. If your data transfer method is interrupts, try using DMA or USB Bulk. 6. Reduce the number of applications your computer is running concurrently. In addition, if you do not need to read every sample that is acquired, use the Relative To and Offset properties to read the desired samples. |
| -1074098096 | Requested sample clock source is invalid for output.
The specified sample clock source terminal is only supported for input. |
| -1074098095 | Acquisition cannot be started, because the selected buffer size is too small.
Increase the buffer size. |
| -1074098094 | Two signals cannot be simultaneously exported on the same terminal. |
| -1074098093 | NULL pointer was passed for a required parameter. |
| -1074098092 | Specified output operation cannot be satisfied, because it requires lines that are currently in use by another output operation. |
| -1074098091 | Values of the AO channel properties lead to an output voltage that is less than the minimum for the device. |
| -1074098090 | Values for AO channel properties lead to an output voltage that exceeds the maximum for the device. |
| -1074098089 | Specified property is not supported, because Reference Clock Source is "None". |
| -1074098088 | Requested AI Maximum value is too small. |
| -1074098087 | Requested AI Maximum value is too large. |
| -1074098086 | Requested AI Minimum value is too small. |
| -1074098085 | Requested AI Minimum value is too large. |
| -1074098084 | Specified property cannot be set while the task is running.
Set the property prior to starting the task, or stop the task prior to setting the property. |
| -1074098083 | You only can get the specified property while the task is committed or while the task is running.
Commit or start the task prior to getting the property. |
| -1074098082 | Specified string is not valid, because its first character is an underscore. |
| -1074098081 | Specified string is not valid, because its last character is a space character. |
| -1074098080 | Specified string is not valid, because its first character is a space character. |
| -1074098079 | Specified string is not valid, because it contains an invalid character. |
| -1074098078 | Hardware clocking error occurred.
If you are using an external reference or sample clock, make sure it is connected and within the jitter and voltage level specifications at all times. Also, verify that its rate matches the specified clock rate. If you are generating your clock internally, contact NI Technical Support. |
| -1074098077 | Self-calibration constants are invalid.
Perform a self-calibration. Contact NI Technical Support if you need additional information. |
| -1074098076 | Requested coupling type is only valid when the trigger source is an external trigger channel. |
| -1074098075 | External calibration failed, and the external calibration data has not been changed.
Make sure that the reference signal used for the calibration is stable and that the voltage matches the value specified to the calibration software. Disconnect the device from any external signals that might be introducing noise. |
| -1074098074 | Self-calibration failed. The self-calibration date has not changed.
Disconnect the device from external signals, as they might introduce noise. Externally calibrate the device to recalibrate the onboard voltage reference that is used for self-calibration. |
| -1074098073 | Specified value is smaller than the minimum value supported for this property. |
| -1074098072 | Waveform name is too long.
Use waveform names with no more than 511 characters. |
| -1074098071 | Unexpected identifier following the switch operation in the connection list.
Switch operations must be separated by a comma inside the connection list. |
| -1074098070 | A self-calibration cannot be performed during external calibration. |
| -1074098069 | A measurement taken during adjustment of the oscillator phase DAC produced an invalid calibration constant.
Make sure that the measured values passed to the calibration VI or function are correct. Verify the calibration procedure, and repeat the calibration. If the problem persists, there might be a hardware malfunction with your device. Contact NI Technical Support. |
| -1074098068 | Calibration constants stored in the EEPROM and used to adjust reads from the cal ADC are invalid. An incorrect calibration might have been performed, or the calibration data in the EEPROM might have been corrupted.
Perform an external calibration, or contact NI Technical Support. |
| -1074098067 | Calibration constants stored in the EEPROM produced an invalid value for the oscillator frequency DAC. An incorrect calibration might have been performed, or the calibration data in the EEPROM might have been corrupted.
Perform an external calibration, or contact NI Technical Support. |
| -1074098066 | Calibration constants stored in the EEPROM produced an invalid value for the oscillator phase DAC. An incorrect calibration might have been performed, or the calibration data in the EEPROM might have been corrupted.
Perform an external calibration, perform a self-calibration, or contact NI Technical Support. |
| -1074098065 | Calibration constants stored in the EEPROM produced an invalid value for the offset DAC. An incorrect calibration might have been performed, or the calibration data in the EEPROM might have been corrupted.
Perform an external calibration, or a self-calibration, or contact NI Technical Support. |
| -1074098064 | Calibration constants stored in the EEPROM produced an invalid value for the gain DAC. An incorrect calibration might have been performed, or the calibration data in the EEPROM might have been corrupted.
Perform an external calibration, perform a self-calibration, or contact NI Technical Support. |
| -1074098063 | Specified number of reads to average from the calibration ADC is invalid.
The number of reads to average must be greater than 0. |
| -1074098062 | Requested an invalid configuration value for adjusting the direct path output impedance.
Refer to the documentation for a list of valid configuration values. |
| -1074098061 | Requested an invalid configuration value for adjusting the main path output impedance.
Refer to the documentation for a list of valid configuration values. |
| -1074098060 | Requested an invalid configuration value for adjusting the main path post-amplifier gain and offset.
Refer to the documentation for a list of valid configuration values. |
| -1074098059 | Requested an invalid configuration value for adjusting the main path pre-amplifier gain.
Refer to the documentation for a list of valid configuration values. |
| -1074098058 | Requested an invalid configuration value for adjusting the main path pre-amplifier offset.
Refer to the documentation for a list of valid configuration values. |
| -1074098057 | A measurement taken during adjustment of calibration ADC produced an invalid calibration constant.
Make sure that the measured values passed to the calibration VI or function are correct. Verify the calibration procedure, and repeat the calibration. If the problem persists, there might be a hardware malfunction with your device. Contact NI Technical Support. |
| -1074098056 | A measurement taken during adjustment of direct path output impedance produced an invalid calibration constant.
Make sure that the measured values passed to the calibration VI or function are correct. Verify the calibration procedure, and repeat the calibration. If the problem persists, there might be a hardware malfunction with your device. Contact NI Technical Support. |
| -1074098055 | A measurement taken during adjustment of main path output impedance produced an invalid calibration constant.
Make sure that the measured values passed to the calibration VI or function are correct. Verify the calibration procedure, and repeat the calibration. If the problem persists, there might be a hardware malfunction with your device. Contact NI Technical Support. |
| -1074098054 | A measurement taken during adjustment of direct path gain produced an invalid calibration constant.
Make sure that the measured values passed to the calibration VI or function are correct. Verify the calibration procedure, and repeat the calibration. If the problem persists, there might be a hardware malfunction with your device. Contact NI Technical Support. |
| -1074098053 | A measurement taken during adjustment of main path post-amplifier gain and offset produced an invalid calibration constant.
Make sure that the measured values passed to the calibration VI or function are correct. Verify the calibration procedure, and repeat the calibration. If the problem persists, there might be a hardware malfunction with your device. Contact NI Technical Support. |
| -1074098052 | A measurement taken during adjustment of main path pre-amplifier gain produced an invalid calibration constant.
Make sure that the measured values passed to the calibration VI or function are correct. Verify the calibration procedure, and repeat the calibration. If the problem persists, there might be a hardware malfunction with your device. Contact NI Technical Support. |
| -1074098051 | A measurement taken during adjustment of main path pre-amplifier offset produced an invalid calibration constant.
Make sure that the measured values passed to the calibration VI or function are correct. Verify the calibration procedure, and repeat the calibration. If the problem persists, there might be a hardware malfunction with your device. Contact NI Technical Support. |
| -1074098050 | EEPROM contains an invalid calibration date and/or time. The calibration data in the EEPROM might have been corrupted.
Perform an external calibration, perform a self-calibration, or contact NI Technical Support. |
| -1074098049 | Attempted to enable output data lines that were not previously disabled.
Make sure that you are enabling data lines for output only after explicitly disabling them. |
| -1074098048 | Pattern contains an invalid character. |
| -1074098047 | Specified channel is not in the task. |
| -1074098046 | Specified operation cannot be performed while the task is running. |
| -1074098045 | Specified operation can be performed only when the task is running.
Start the task before requesting this operation. |
| -1074098044 | Specified operation did not complete, because the specified timeout expired. |
| -1074098043 | Specified string is not valid, because it is empty. |
| -1074098042 | Generation cannot be started because the output buffer is empty.
Write data before starting a buffered generation. The following actions can empty the buffer: changing the size of the buffer, unreserving a task, setting the Regeneration Mode property, changing the Sample Mode, or configuring retriggering. |
| -1074098041 | Specified channel name is invalid. |
| -1074098040 | Specified timeout value is not supported. Supported timeout values are 0 (try or check once and return), positive numbers up to
4294967, and -1 (try or check until success or error). |
| -1074098039 | Specified property is not supported by the device or is not applicable to the task. |
| -1074098038 | You can get the specified property only while the task is committed or running. |
| -1074098037 | Specified property cannot be set while the task is running. |
| -1074098036 | External stimulus voltage read was outside the expected range.
Verify that the external stimulus voltage is properly connected and has the correct amplitude. |
| -1074098035 | Requested calibration function is not supported by the device. |
| -1074098034 | Invalid physical channel selected for calibration. |
| -1074098033 | Attempt to store calibration constants without completing all the necessary external calibration steps.
Refer to the documentation for the calibration procedure. Verify that all necessary steps are performed before closing the external calibration session. |
| -1074098032 | Unable to synchronize to the external stimulus frequency.
Verify that the external stimulus has the correct frequency, amplitude, and stability. Consult the documentation for the calibration procedure for valid ranges. |
| -1074098031 | Unable to detect the external stimulus frequency.
Verify that the external stimulus is properly connected and has the correct frequency and amplitude. |
| -1074098030 | Requested calibration close action is invalid.
Select Store or Abort. |
| -1074098029 | Requested operation only can be used during an external calibration session. |
| -1074098028 | Invalid calibration area selected.
Select self-calibration or external calibration. |
| -1074098027 | External calibration constants are invalid.
Perform an external calibration. Contact NI Technical Support if you need additional information. |
| -1074098026 | Configured reference clock rate is invalid.
The reference clock rate must be within the valid range and a multiple of the increment value. |
| -1074098025 | Requested impedance for the external trigger is invalid.
Specify an impedance that is appropriate for the external trigger, or choose a different trigger source. |
| -1074098024 | Requested hysteresis is not valid with the configured trigger level and AI Maximum.
Configure the task so the following formula is satisfied: Trigger Level + Hysteresis < AI Maximum |
| -1074098023 | Requested video trigger line number is incompatible with the chosen video signal format. |
| -1074098022 | Requested window trigger level is not valid with the configured AI Minimum and AI Maximum.
Configure the instrument so the following formula is satisfied: AI Minimum < Window Trigger Level < AI Maximum |
| -1074098021 | Requested Trigger Level is not valid with the configured AI Minimum and AI Maximum.
Configure the instrument so the following formula is satisfied: AI Minimum < Trigger Level < AI Maximum |
| -1074098020 | Requested Hysteresis is not valid with the configured Trigger Level and AI Minimum.
Configure the task so the following formula is satisfied: Trigger Level - Hysteresis > AI Minimum |
| -1074098019 | Requested sample rate exceeds maximum real-time sample rate.
If you want a higher sampling rate and have a repetitive signal, enable RIS. |
| -1074098018 | Requested Read Position is invalid in RIS mode. |
| -1074098017 | Requested immediate trigger type while in RIS mode.
Immediate triggering is not compatible with the RIS mode. Select a different trigger type, or do not use RIS. |
| -1074098016 | TDC is not enabled during RIS mode.
TDC must be enabled when the digitizer is in the RIS mode. Enable TDC, or do not use RIS. |
| -1074098015 | Multiple records are not available with RIS. |
| -1074098014 | Requested reference clock source is invalid. |
| -1074098013 | Requested sample clock source is invalid. |
| -1074098012 | Insufficient onboard memory for requested Number of Records and Samples per Channel combination.
Reduce the Number of Records and/or Samples per Channel. |
| -1074098011 | Requested analog input attenuation is invalid. |
| -1074098010 | AC coupling is not allowed with 50 Ohm impedance for this device.
Use DC coupling, or configure a different impedance setting. |
| -1074098009 | Requested record number is invalid.
Use the Records Done property to find out how many records are available. Record numbers start at 0. Use -1 for all available records. |
| -1074098008 | Requested waveform length is invalid, because the number of samples is not an integer multiple of the waveform length increment. |
| -1074098007 | Specified output voltage is not valid with the given sample clock rate.
Make sure your output voltage level is compatible with your sample clock rate by altering the output voltage level or the sample clock rate. Consult your documentation for more information. |
| -1074098006 | Hardware clocking error occurred.
If you are using an external sample clock or an external reference clock, make sure it is connected and within the jitter and voltage level specifications. Also, verify that the rate of the external clock matches the specified clock rate. If you are generating your clock internally, contact NI Technical Support. |
| -1074098005 | Hardware clocking error occurred.
If you are using an external sample clock or an external reference clock, make sure it is connected and within the jitter and voltage level specifications. Also, verify that the rate of the external clock matches the specified clock rate. If you are generating your clock internally, contact NI Technical Support. |
| -1074098004 | Hardware clocking error occurred.
If you are using an external sample clock or an external reference clock, make sure it is connected and within the jitter and voltage level specifications. Also, verify that the rate of the external clock matches the specified clock rate. If you are generating your clock internally, contact NI Technical Support. |
| -1074098003 | Hardware clocking error occurred.
If you are using an external sample clock or an external reference clock, make sure it is connected and within the jitter and voltage level specifications. Also, verify that the rate of the external clock matches the specified clock rate. If you are generating your clock internally, contact NI Technical Support. |
| -1074098002 | Hardware clocking error occurred.
If you are using an external sample clock or an external reference clock, make sure it is connected and within the jitter and voltage level specifications. Also, verify that the rate of the external clock matches the specified clock rate. If you are generating your clock internally, contact NI Technical Support. |
| -1074098001 | Hardware clocking error occurred.
If you are using an external sample clock or an external reference clock, make sure it is connected and within the jitter and voltage level specifications. Also, verify that the rate of the external clock matches the specified clock rate. If you are generating your clock internally, contact NI Technical Support. |
| -1074098000 | Hardware clocking error occurred.
If you are using an external sample clock or an external reference clock, make sure it is connected and within the jitter and voltage level specifications. Also, verify that the rate of the external clock matches the specified clock rate. If you are generating your clock internally, contact NI Technical Support. |
| -1074097999 | Reference Clock Source specified is invalid, given the Sample Clock Source.
When Sample Clock Source is anything other than "OnboardClock", you must set Reference Clock Source to "None", and you cannot export the Reference Clock. |
| -1074097998 | Unable to configure requested delay property given the current clock rate.
Make sure the sample clock rate is greater than or equal to the phase shift DMC threshold of your device, or do not configure the delay. Consult your documentation for more information. |
| -1074097997 | Signal type requested to be exported is not supported for the specified task running on the given device. |
| -1074097996 | Signal type requested to be exported is not valid. |
| -1074097995 | Trigger type requested to be sent as software trigger is not supported for the specified task running on the given device. |
| -1074097994 | Trigger type requested to be sent as the software trigger is invalid. |
| -1074097993 | Specified route cannot be satisfied, because it requires resources that are currently in use by another route within this task. |
| -1074097992 | Specified route cannot be satisfied, because it requires resources that are currently in use by another route. |
| -1074097991 | Specified route cannot be satisfied, because the hardware does not support it. |
| -1074097990 | An attempt has been made to configure a reference trigger when the sample mode of the sample clock has been configured for continuous sampling. Reference trigger is only applicable for finite sampling.
Change the sample mode to finite to use a reference trigger, or do not configure a reference trigger. |
| -1074097989 | Specified property value cannot be used, because the hardware does not support it. |
| -1074097988 | Event delay is outside of the legal range.
Change the value of the delay, and/or verify that the units are correct. |
| -1074097987 | Script is not in the device memory.
Make sure you are referring to a previously written script by its correct name. Also, make sure the script has not been deleted. |
| -1074097986 | Specified sample rate is higher than the fastest rate supported by the device. |
| -1074097985 | You have specified an invalid value for dt in the waveform cluster. The value for dt must be greater than zero. |
| -1074097984 | NI-DAQmx is unable to communicate with the device. Make sure the device is present in and accessible to the system, is not currently being reset, and is not reserved by another driver such as Traditional NI-DAQ (Legacy). |
| -1074097983 | There is not enough free device memory for your script.
Delete waveforms or scripts not in use to free memory. If you have deleted multiple waveforms or scripts, the memory might have become fragmented. To avoid fragmentation, you can change the order in which you write/delete your waveforms and scripts. |
| -1074097982 | There is not enough free device memory for your waveform.
Delete waveforms or scripts not in use to free memory. If you have deleted multiple waveforms or scripts, the memory might have become fragmented. To avoid fragmentation, you can change the order in which you write/delete your waveforms and scripts. |
| -1074097981 | Hardware clocking error occurred.
If you are using an external sample clock or an external reference clock, make sure it is connected and within the jitter and voltage specifications. Also, verify that the rate of the external clock matches the specified clock rate. If you are generating your clock internally, contact NI Technical Support. |
| -1074097980 | Hardware clocking error occurred.
If you are using an external sample clock or an external reference clock, make sure it is connected and within the jitter and voltage specifications. Also, verify that the rate of the external clock matches the specified clock rate. If you are generating your clock internally, contact NI Technical Support. |
| -1074097979 | Waveform is not in the device memory.
Make sure you are referring to a previously allocated and/or written waveform by its correct name. Also, make sure that the waveform was not deleted. |
| -1074097978 | You cannot write data outside the boundaries of your waveform.
Make sure you are not trying to write more data than your waveform can accomodate and that your write location and write offset are set correctly. |
| -1074097977 | The waveform you are trying to allocate on the device has been previously allocated.
Make sure you are not trying to allocate the same waveform twice, or delete the existing waveform before allocating it again. |
| -1074097976 | An attempt was made to set the Samples per Channel property to a value greater than the maximum supported number. |
| -1074097975 | Not enough samples were written to satisfy the initial data transfer request condition.
To successfully start a generation, increase the number of samples initially written to the buffer before starting. Alternatively, decrease the number of samples required to start by changing the data transfer request condition. |
| -1074097974 | The generation is not yet started, and not enough space is available in the buffer.
Configure a larger buffer, or start the generation before writing more data than will fit in the buffer. |
| -1074097973 | Some or all of the samples to write could not be written to the buffer yet. More space will free up as samples currently in the buffer are generated.
To wait for more space to become available, use a longer write timeout. To make the space available sooner, increase the sample rate. |
| -1074097972 | Attempted to write samples that have already been generated or have already been sent to the device for generation.
Increasing the buffer size or writing the data more frequently might correct the problem. |
| -1074097971 | Attempted to write a sample beyond the final sample generated. The generation has stopped, therefore the sample specified by the combination of position and offset will never be available.
Specify a position and offset which selects a sample up to, but not beyond, the final sample generated. The final sample generated can be determined by querying the total samples generated after a generation has stopped. |
| -1074097970 | Attempted to write to an invalid combination of position and offset. The position and offset specified a sample prior to the first sample generated (sample 0).
Make sure any negative write offset specified will select a valid sample when combined with the write position. |
| -1074097969 | Some or all of the samples requested have not yet been acquired.
To wait for the samples to become available use a longer read timeout or read later in your program. To make the samples available sooner, increase the sample rate. If your task uses a start trigger, make sure that your start trigger is configured correctly. It is also possible that you configured the task for external timing, and no clock was supplied. If this is the case, supply an external clock. |
| -1074097968 | Reading relative to the reference trigger or relative to the start of pretrigger samples position when the acquisition is not configured with a reference trigger.
Configure a reference trigger, or configure read position differently. |
| -1074097967 | Reading relative to the reference trigger or relative to the start of pretrigger samples position before the acquisition is complete.
Wait for the acquisition to complete before reading, or increase your read timeout. Also, make sure the hardware is set up and wired correctly, the signal for the reference trigger is correct, and that the reference trigger occurs while the device is acquiring data. |
| -1074097966 | Attempted to read samples that are no longer available. The requested sample was previously available, but has since been overwritten.
Increasing the buffer size, reading the data more frequently, or specifying a fixed number of samples to read instead of reading all available samples might correct the problem. |
| -1074097965 | Attempted to read a sample beyond the final sample acquired. The acquisition has stopped, therefore the sample specified by the combination of position and offset will never be available.
Specify a position and offset which selects a sample up to, but not beyond, the final sample acquired. The final sample acquired can be determined by querying the total samples acquired after an acquisition has stopped. |
| -1074097964 | Invalid combination of position and offset. The position and offset specified a sample prior to the first sample acquired (sample 0).
Make sure any negative read offset specified will select a valid sample when combined with the read position. |
| -1074097963 | Reference clock source and sample clock source cannot be the same.
Use different terminals to bring in your reference clock and sample clock, or use only one of them at a time. |
| -1074097962 | Sample rate desired is too low for an external clock being brought in through the ClkIn connector.
Change the sample rate so it is within limits, or use DDC_ClkIn to bring in your sample clock. |
| -1074097961 | Sample clock rate desired is too high for an external clock being brought in through the backplane.
Bring in your external sample clock through one of the higher-frequency front panel connectors, or use a lower sample rate. |
| -1074097960 | Sample clock rate and the sample clock divisor values are inconsistent with one another.
Consider settting either the sample clock rate or the sample clock divisor, but not both. This allows the driver to automatically select an appropriate value for the other property. Alternatively, make sure the sample clock rate and sample clock divisor satisfy the following constraint: rate = timebase / divisor |
| -1074097959 | Sample clock rate requested is too low for the selected divide-down clock.
Use the high resolution clock, or increase your sample rate. |
| -1074097958 | Interpolation rate specified is not possible for the given sample rate. |
| -1074097957 | Specified Offset is too large for the given AO Gain and Maximum Value.
The following constraint must hold: Offset < (Gain * Maximum Value / 2) |
| -1074097956 | Specified Offset is too small given AO Gain and Minimum Value.
The following constraint must hold: Offset > (Gain * Minimum Value / 2) |
| -1074097955 | Minimum and maximum values for the channel are not symmetric. |
| -1074097954 | Gain value conflicts with specified AI Minimum and AI Maximum properties.
The specified gain and AI Minimum and/or AI Maximum would cause the device to exceed the hardware limit. Lower the gain, or adjust AI Minimum and/or AI Maximum. |
| -1074097953 | Specified topology cannot be used to reset the switch, because that topology is not supported by the connected terminal block.
Refer to the documentation for supported topologies for the given terminal block, or disconnect the terminal block from the switch. |
| -1074097952 | Integer was expected but not found in the script.
Insert an appropriate integer at this location in the script. |
| -1074097951 | PLL has lost phase-lock to the external reference clock.
Make sure your reference clock is connected and that it is within the jitter and voltage level specifications at all times. Also, make sure the reference clock rate is correctly specified at all times. |
| -1074097950 | PLL could not phase-lock to the external reference clock.
Make sure your reference clock is connected and that it is within the jitter and voltage specifications. Also, make sure the reference clock rate is correctly specified. |
| -1074097949 | Hardware clocking error occurred.
If you are using an external sample clock or an external reference clock, make sure it is connected and within the jitter and voltage level specifications. Also, verify that the rate of the external clock matches the specified clock rate. If you are generating your clock internally, contact NI Technical Support. |
| -1074097948 | Hardware clocking error occurred.
If you are using an external sample clock or an external reference clock, make sure it is connected and within the jitter and voltage specifications. Also, verify that the rate of the external clock matches the specified clock rate. If you are generating your clock internally, contact NI Technical Support. |
| -1074097947 | Hardware clocking error occurred.
If you are using an external sample clock or an external reference clock, make sure it is connected and within the jitter and voltage specifications. Also, verify that the rate of the external clock matches the specified clock rate. If you are generating your clock internally, contact NI Technical Support. |
| -1074097946 | Hardware clocking error occurred.
If you are using an external sample clock or an external reference clock, make sure it is connected and within the jitter and voltage specifications. Also, verify that the rate of the external clock matches the specified clock rate. If you are generating your clock internally, contact NI Technical Support. |
| -1074097945 | Hardware clocking error occurred.
If you are using an external sample clock or an external reference clock, make sure it is connected and within the jitter and voltage specifications. Also, verify that the rate of the external clock matches the specified clock rate. If you are generating your clock internally, contact NI Technical Support. |
| -1074097944 | Hardware clocking error occurred.
If you are using an external sample clock or an external reference clock, make sure it is connected and within the jitter and voltage level specifications. Also, verify that the rate of the external clock matches the specified clock rate. If you are generating your clock internally, contact NI Technical Support. |
| -1074097943 | Hardware clocking error occurred.
If you are using an external reference clock, make sure it is connected and within the jitter and voltage level specifications at all times, and its rate is correctly specified. If you are generating your clock internally, contact NI Technical Support. |
| -1074097942 | Hardware clocking error occurred.
If you are using an external reference clock, make sure it is connected and within the jitter and voltage level specifications, and its rate is correctly specified. If you are generating your clock internally, contact NI Technical Support. |
| -1074097941 | Explanation could not be found for the requested status code.
Verify that the requested status code is correct. |
| -1074097940 | Property specified is not valid for this function. |
| -1074097939 | Property requested cannot be read. |
| -1074097938 | Property requested cannot be set. |
| -1074097937 | NULL pointer was passed for a required parameter. |
| -1074097936 | Buffer is too small to fit read data. |
| -1074097935 | Buffer is too small to fit the string. |
| -1074097934 | Trigger line requested could not be reserved because it is already in use. |
| -1074097933 | Amount of time allocated to perform this operation was exceeded. |
| -1074097932 | Device identifier is invalid. |
| -1074097931 | Pretrigger Samples per Channel requested plus minimum number of posttrigger samples exceed the requested Number of Samples per Channel.
Decrease the number of Pretrigger Samples per Channel, or increase Number of Samples per Channel. |
| -1074097930 | Range statement in the list entry contains an invalid character sequence. |
| -1074097929 | Advance trigger and Advance Complete event must use the same polarity in this particular switch device. |
| -1074097928 | Topology does not support scanning. |
| -1074097927 | Switch scan list is too large to fit in the onboard memory of the device. |
| -1074097926 | Switch channel is already in exclusive use within another connection. |
| -1074097925 | Topology specified is invalid.
Make sure the spelling of the topology is correct and that the switch supports that topology. |
| -1074097924 | Device does not support this property. |
| -1074097923 | Action at the end of the scan list is not valid for this device. |
| -1074097922 | Hardware was unexpectedly powered off and back on.
To recover, reset the device (either programmatically or by using Measurement & Automation Explorer). |
| -1074097921 | Switch device does not support this operation. |
| -1074097920 | Explicit connection cannot be made to a switch channel that is reserved for routing. |
| -1074097919 | Connection cannot be made between the specified channels because they are connected to different source channels. |
| -1074097918 | Channel cannot be connected to itself. |
| -1074097917 | Channels used to make the connection between two endpoints must be reserved for routing. |
| -1074097916 | Path contains a leg with two channels that cannot be directly connected. |
| -1074097915 | Leg in path cannot contain two channels that are already directly connected. |
| -1074097914 | Switch channel names cannot be duplicated in the path string. |
| -1074097913 | Switch channels cannot be disconnected because there is no explicit path between them. |
| -1074097912 | Path between two switch channels is not available. |
| -1074097911 | Explicit connection between the channels already exists. You can make only one connection between these channels. |
| -1074097910 | Operation is permitted only while the switch device is scanning. |
| -1074097909 | Operation is not permitted while the switch device is scanning. |
| -1074097908 | Hardware is not responding.
Ensure your hardware is powered on and all cables are properly connected. |
| -1074097907 | Physical channel specified does not exist on this device.
Refer to the documentation for channels available on this device. |
| -1074097906 | Device could not complete the calibration operation.
Calibration could fail for the following reasons: 1. The actual reference signal applied for calibration was different from the value you specified. Ensure that the reference signal applied is the same as the values that were input. 2. The reference signal was not stable over the period of time that the hardware was being calibrated. Ensure that the reference signal specified is free of noise and does not drift over the duration of the calibration. 3. The device is not functioning properly. |
| -1074097905 | Reference frequency applied for calibration is outside the range defined for calibration of this device.
Ensure that the reference frequency falls within the range specified for this device. |
| -1074097904 | Reference voltage applied for calibration is outside the range defined for calibration of this device.
Ensure that the reference voltage falls within the range specified for this device. |
| -1074097903 | Data read from non-volatile memory on the device is invalid. Contact NI Technical Support. |
| -1074097902 | Property must have the same value for all repeated physical channels.
Set the same property value for all of the channels. |
| -1074097901 | Device temperature is outside of the required range for calibration. |
| -1074097900 | Calibration handle is invalid.
Open a calibration session to get a valid calibration handle. Use the valid calibration handle obtained when the calibration session was opened. |
| -1074097899 | Password is required for this operation. |
| -1074097898 | Password supplied is incorrect. |
| -1074097897 | Password is longer than maximum allowed length. |
| -1074097896 | Calibration session is already open on this device.
You can have only one open calibration session for each device. Use the handle obtained when the calibration session for this device was originally opened. |
| -1074097895 | Property must have the same value for all channels on this device. |
| -1074097894 | Bracket character ("[" or "]") at the specified position in the list is invalid. Matching bracket cannot be found.
Check for nested fully specified paths or incorrectly paired brackets. |
| -1074097893 | Number of samples to write must be the same for every channel. |
| -1074097892 | Pattern width specified does not match the number of lines in the digital channel. |
| -1074097891 | Physical channel not specified. |
| -1074097890 | Number of terminals requested cannot be greater than 1. |
| -1074097889 | Number of samples to read must be -1 or greater. |
| -1074097888 | Analog waveform expected as input. |
| -1074097887 | Digital waveform expected as input. |
| -1074097886 | Shared library version installed is incorrect.
This error might be the result of an incorrect installation of NI-DAQmx or a related software package. Reinstall NI-DAQmx, or download the latest version of the driver from the NI website at ni.com. If the error is still returned, contact NI Technical Support. |
| -1074097885 | Task name specified conflicts with an existing task name. |
| -1074097884 | Task specified is invalid or does not exist. |
| -1074097883 | Channel is not in the task, and the channel is not a valid global channel.
Make sure that the channel is in the task or that the channel is a valid global channel. If you explicitly named the virtual channel in DAQmx Create Channel, you must use the name assigned to that channel. Also, check for typing errors. |
| -1074097882 | Requested value is not a supported value for this property. The property value may be invalid because it conflicts with another property. |
| -1074097881 | Current data supplied is outside of the specified range. |
| -1074097880 | Device unable to store calibration constants.
Make sure that your hardware is properly installed, and test the regular operation of the device. |
| -1074097879 | Duplicate channels in the list of physical channels are not supported by this device. |
| -1074097878 | Advance trigger type specified is not supported by the device. |
| -1074097877 | Scanning is not supported by the specified device. |
| -1074097876 | Connection operator is invalid at the designated point in the list entry. |
| -1074097875 | Action at the designated position in the scanlist is not valid for the device. |
| -1074097874 | Unexpected connection separator "&" or sequence separator "&&" in the list entry. |
| -1074097873 | Invalid identifier instead of an expected terminator in the list entry. |
| -1074097872 | Invalid identifier instead of an expected connection operator "->" in the list entry. |
| -1074097871 | Invalid identifier in the list entry. The connection separator "&" or sequence separator "&&" was expected. |
| -1074097870 | Fully specified path cannot contain a connection range. |
| -1074097869 | List cannot end with the connection separator "&". |
| -1074097868 | Identifier in the list entry is too long. |
| -1074097867 | Semicolon or a semicolon modifier must follow a connection range statement.
Refer to the documentation for information on connection ranges and semicolon modifiers. |
| -1074097866 | Invalid identifier instead of an expected connection operator, "->", in the list entry.
Refer to the documentation for proper syntax for connections involving channel ranges. |
| -1074097865 | Invalid identifier after a separator in the list entry. |
| -1074097864 | Invalid channel name in the list entry.
Refer to the documentation for valid channel names for the device in use. |
| -1074097863 | Invalid value in the "<repeat>" statement in the list entry.
The syntax for a repeat statement is "<repeat integer>". Refer to the documentation for valid integer values. |
| -1074097862 | Invalid trigger line in the "<sac>" or "<wfa>" statement in the list entry.
Refer to the documentation for valid trigger lines. |
| -1074097861 | Invalid identifier after the device identifier in the list entry. |
| -1074097860 | Invalid identifier at the end of the switch action.
A connection separator, sequence separator, or valid switch action terminator must follow a switch action. |
| -1074097859 | Hardware necessary for this route is in use by another task or tasks. |
| -1074097858 | Source terminal to be routed could not be found on the device.
Make sure the terminal name is valid for the specified device. Refer to Measurement & Automation Explorer for valid terminal names. |
| -1074097857 | Marker specified in a generate instruction exceeds the waveform boundaries.
Change the marker position or positions to fit within the waveform, or increase the size of the waveform. |
| -1074097856 | Waveform referenced in the script was not found in onboard memory.
Write the waveform to the device before writing the script. |
| -1074097855 | Keyword was expected, but not found in the script. |
| -1074097854 | Valid identifier expected but not found in script.
The identifier should specify a valid waveform or script name. Identifiers cannot start with a number. |
| -1074097853 | Script contains an invalid character or symbol.
Replace the invalid character with a valid symbol or alphanumeric character. |
| -1074097852 | Resource requested by this session has already been reserved by a different session. |
| -1074097851 | Self-test of the device has failed. |
| -1074097850 | Terminal cannot appear multiple times within a single digital input or output task. |
| -1074097849 | Task cannot contain both input and output channels.
Either use channels of one direction in a task or make two separate tasks. |
| -1074097848 | Timestamps have been overwritten. You can no longer read any data. |
| -1074097847 | Stop trigger has not occurred yet. |
| -1074097846 | Record requested has not been acquired yet . |
| -1074097845 | Data requested has been overwritten in the device memory. |
| -1074097844 | Channel cannot be used more than once inside a list of channels.
If you need to use the same physical channel more than once inside your list of channels, refer to that physical channel under different names. |
| -1074097843 | Specified string contains characters that cannot be interpreted by the driver due to installed language support and system locale settings.
If possible, do not use this character. Otherwise, ensure that the appropriate language support is installed on the system, and that the system locale is set correctly. For most Windows operating systems, this is done through the Regional Settings option in the Control Panel. For a LabVIEW RT target, you should install "Language Support for LabVIEW RT" and change the locale setting for the remote system under the "System Setting" tab in MAX. |
| -1074097842 | An unknown connection error has occurred. |
| -1074097841 | An unknown protocol error has occured. |
| -1074097840 | Connection protocol contains invalid data. |
| -1074097839 | Connection protocol contains negative size. |
| -1074097838 | The size limit of the protocol buffer connection has been exceeded. |
| -1074097837 | Bad protocol version has been encountered. Ensure you have a matching driver version installed on each connection end. |
| -1074097836 | The specified protocol is not supported. |
| -1074097835 | A connection error has occurred. Ensure that the device session is still open with session access enabled. |
| -1074097834 | Failed to open connection. Ensure that Session Access has been enabled on the specified device. |
| -1074097833 | The connection timeout has expired. Ensure that the application that hosts the Session Access enabled device is still accessible. |
| -1074097832 | Encountered End of File character when reading the transport. |
| -1074097831 | The connection has been interrupted. Ensure that the application that hosts the Session Access enabled device is still accessible. |
| -1074097830 | The transport contains bad arguments. |
| -1074097829 | The transport contains corrupted data. |
| -1074097828 | Internal error has occurred at the transport layer. |
| -1074097827 | The specified operation cannot be performed when a configuration list is running. |
| -1074097826 | The requested feature is not supported with a configuration list. |
| -1074097825 | The specified attribute is not supported in a configuration list. |
| -1074097824 | The maximum number of configuration lists has been exceeded. |
| -1074097823 | The specified configuration list name is already in use. |
| -1074097822 | The specified configuration list name is invalid. |
| -1074097821 | Duplicate attributes are not allowed in a configuration list. |
| -1074097820 | A configuration list must have at least one attribute. |
| -1074097819 | The configuration list has an insufficient number of steps. |
| -1074097818 | You attempted to compile an empty configuration list. |
| -1074097817 | The compiled configuration list is too large for the device's storage space. |
| -1074097816 | The active configuration list does not exist. |
| -1074097815 | The active configuration step does not exist. |
| -1074097814 | Configuration List memory underflow. The device is not able to move data fast enough to keep up with the Configuration List advance rate. Advance the Configuration List at a lower rate to correct this error. |
| -1074097813 | You have specified a timeout which is too long for the device's internal hardware counter. |
| -1074097812 | The specified language is invalid. |
| -1074097811 | The session contains an outstanding connection error that could not be recovered. Close the session and reopen the session to try again. |
| -1074097810 | The specified value is out of range. |
| -1074097809 | The size of the array passed into this VI is not supported or does not resolve to a fixed size array.
Refer to the VI context help for information about the supported array sizes. |
| -1074097808 | Could not load the dynamic library. |
| -1074097807 | File was not found at specified path |
| -1074097806 | The specified name is longer than the maximum supported name length. |
| -1074097805 | The device watchdog timer expired due to unresponsive firmware or hardware components. To clear this error, reset or power cycle the device. Additionally, contact NI technical support or visit ni.com/support. |
| -1074097804 | The requested data stored in nonvolatile memory is corrupt and cannot be recovered. |
| -1074097803 | The specified resource name is ambiguous. There are multiple resources with this name. Enter a unique alias for this resource in Measurement & Automation Explorer. |
| -1074097802 | An unexpected hardware failure has occurred. Contact NI technical support or visit ni.com/support. |
| -1074097801 | An unexpected firmware failure has occurred. Contact NI technical support or visit ni.com/support. |
| -1074097800 | An unexpected software failure has occurred. Contact NI technical support or visit ni.com/support. |
| -1074097799 | The device session is invalid. The device might have been reset or removed from the system. If you have reset the device through Measurement & Automation Explorer, you can create the session again by initializing the device. |
| -1074097798 | The specified alias is being used by another device. Enter a unique alias. |
| -1074097797 | The device cannot be added to the system configuration because it is not simulated. |
| -1074097796 | The device cannot be removed from the system configuration because it is present. |
| -1074097795 | The installed version of the software cannot read the configuration because it corresponds to a newer software version. Upgrade your software or reset configuration data in Measurement & Automation Explorer. |
| -1074097794 | The installed version of the software cannot read the configuration because it corresponds to an older software version. Downgrade your software or reset configuration data in Measurement & Automation Explorer. |
| -1074097793 | The specified device cannot be found. |
| -1074097792 | The configuration is corrupt. Reset configuration data in Measurement & Automation Explorer. |
| -1074097791 | The device is already in use by another process and cannot be accessed. |
| -1074097790 | Information concerning the primary and secondary error codes has already been added to the error elaboration and therefore does not need further elaboration. |
| -1074097789 | The specified operation cannot be performed because a session has been aborted or a device has been removed from the system. Handle this situation as required by the application and then, if appropriate, attempt to perform the operation again. |
| -1074097788 | Support for this device is not installed. Use a different device or install support for this device. |
| -1074097787 | This operation is not supported for simulated devices. |
| -1074097786 | Bitfile not found at the specified path. |
| -1074097785 | The ongoing operation was aborted. |
| -1074097784 | Acquisition has stopped because the driver could not transfer the data from the device to the computer memory fast enough. This was caused by computer system limitations. |
| -1074097783 | The traits read from the FPGA for this IP are invalid. |
| -1074097782 | The settings to write to the FPGA for this IP are invalid. |
| -1074097781 | The ADC has been overloaded. Data is invalid. |
| -1074097780 | The bitfile did not contain a FIFO for this P2P endpoint. |
| -1074097779 | This device requires a 58W power and cooling capable chassis. Refer to your product documentation for more information. |
| -1074097778 | Settings on this device cannot be changed while another shared session is running. |
| -1074097777 | Currently installed driver no longer supports the hardware manufacturing calibration data format.
Either send your device back to manufacturing for calibration or downgrade your driver to the version supplied with the device. Older driver versions can also be downloaded from ni.com. If uncertain, contact NI technical support. |
| -1074097776 | Hardware manufacturing calibration data format is newer than the latest revision supported by the currently installed driver.
Either send your device back to manufacturing for calibration or upgrade your driver to the version supplied with the device. Driver updates can also be downloaded from ni.com. If uncertain, contact NI technical support. |
| -1074097775 | The driver does not support simulating the specified instrument. |
| -1074097774 | This operation is not supported when using a combination of simulated and real devices. |
| -1074097773 | Getting a property that pertains to multiple channels or devices failed because the property values are different for different channels or devices. Get the specified property for one channel or device at a time. For example, if you are getting a property for two channels and the property values are different, you must get the values one channel at a time. |
| -1074097772 | The specified de-embedding table cannot be found. |
| -1074097771 | The resource requested by this session is already reserved by a different session. Abort the other session and try again. |
| -1074097770 | The resource requested by this session is already reserved by a different session. If resource sharing is intended, ensure that all sessions have compatible settings and try again. If resource sharing is not intended, abort the other session(s) and try again. |
| 1073385472 | Input termination resistor for one or more channels was overloaded. Your data might be invalid. |
| 1073385473 | ADC for one or more channels was overloaded. Your data might be invalid. |
| 1073385474 | PLL was unlocked. Your data might be invalid. |
| 1073385475 | User-defined information string entered exceeds the maximum allowable string length. The string will be truncated to its maximum allowable length. |
| 1073385476 | While writing to the buffer during a regeneration, the actual data generated might have alternated between old data and new data. That is, while the driver was replacing the old pattern in the buffer with the new pattern, the device might have generated a portion of new data, then a portion of old data, and then a portion of new data again.
Reduce the sample rate, use a larger buffer, or refer to documentation about DAQmx Write for information about other ways to avoid this warning. |
| 1073385477 | Requested string could not fit into the given buffer. Only the first part of the string was copied into the buffer. To allow for the terminating NULL character, the number of characters copied into the buffer is equal to the size of the buffer minus one.
Call the function twice. Call the function initially to determine the string size. Use the second function call to get the full string value. In the first function call, pass NULL for the buffer and zero for the buffer size. The positive return value of the function is the string size (which includes the terminating NULL). Use this value to allocate a buffer of sufficient size, then use this buffer in the second function call. |
| 1073385478 | RIS acquisition was completed, but some of the bins were not filled with a sufficient number of samples to perform the requested RIS averaging. Data for those bins was computed from the available samples.
Consider increasing the timeout for the operation. Refer to documentation for details about RIS acquisitions. |
| 1073385479 | Output gain was coerced to the nearest acceptable value, because the original value was too low given the RF Frequency. |
| 1073385480 | Output gain was coerced to the nearest acceptable value, because the original value was too high given the RF Frequency. |
| 1073385481 | Calibration constants stored in EEPROM produced an invalid value for one or more analog input channels. The device will continue to function, but the accuracy of the measurements may be compromised.
An incorrect calibration might have been performed, or the calibration data in the EEPROM might have been corrupted. Perform an external calibration, perform a self-calibration, or contact NI Technical Support. |
| 1073385482 | Self-calibration section of the EEPROM on the device appears to be corrupt.
Perform a self-calibration on the device. |
| 1073385483 | Requested property value exceeds device specification limits. Device performance is not guaranteed.
Use values within device specifications, or set the Allow Out of Specification User Settings property to true. |
| 1073385484 | Buffer size specified is not evenly divisible by 8 times the sector size. For optimal performance, use a buffer size that is a multiple of 8 times the sector size. Refer to the NI-DAQmx Help for more information. |
| 1073385485 | Output power is unleveled. Requested power level is too low for the automatic leveling control (ALC) on this device. If this device uses an ALC input signal, ensure the appropriate cable is connected. |
| 1073385486 | Output power is unleveled. Requested power level is too high for the automatic leveling control (ALC) on this device. |
| 1073385487 | The operation requires a system reboot to complete. |
| 1073385488 | No error occurred |
| 1073385489 | Internal Error %ld occurred. Contact NI with this error information. |
| 1073385490 | Self-calibration data is corrupted.
Perform a self-calibration. Contact NI Technical Support if you need additional information. |
| 1073385491 | Self-calibration range data is corrupted.
Perform a self-calibration range. Contact NI Technical Support if you need additional information. |