Measurement Computing Data Acquisition Systems rev.10.4 - Manual (Page 328)

4.7-10 Daq API Command Reference 908594 Programmer’s Manual
API Error Codes (Cont.) – daqError
Error Name Code # hex-dec Description
DerrDaqStalled 83h – 131 PersonalDaq Only. The low level driver has stalled in an attempt to continue
collecting data.
Corrective Actions:
• If using the PersonalDaq check that the unit is still properly connected
to the PC and that all USB cables and hubs are properly connected.
DerrDaqLostPower 84h – 132 PersonalDaq Only. The PersonalDaq does not have enough power to operate
properly. The unit either does not have enough power supplied to it by the host
pc or the auxiliary power is not connected. Some PC’s and notebooks may not
supply the appropriate power necessary for the PersonalDaq to operate properly.
Corrective Actions:
•
Some PC’s and notebooks may not supply the appropriate power
necessary for the PersonalDaq to operate properly and you may need
to operate the PersonalDaq with the auxiliary power connection
attached. Check the manual for instructions on using the auxiliary
power input.
• Another way to circumvent this problem is to place an external USB
hub between the host computer and the PersonalDaq. The placement
of the USB hub allows the PersonalDaq to run off power supplied by
the hub rather than the host PC.
DerrDaqMissing 85h – 133 PersonalDaq Only. The PersonalDaq is missing. This occurs when a session is
open with a PersonalDaq but the PersonalDaq has been found to be missing.
Corrective Actions:
•
Check the USB cable connections on the PC, PersonalDaq as well as
any USB hubs in use.
DerrScanConfig 86h – 134 The scan configuration programmed is not legal. One or more channel
configuration parameters have been found to be in error.
Corrective Actions:
• Check that all channels have been configured using legal parameters
and settings for that channel type. Inspect channel parameter settings
and flags for each channel being configured using the daqAdcSetScan
or daqAdcRd… API functions.
DerrInvTrigSense 87h – 135 Invalid trigger sense specified. The trigger sense specified for a hardware based
trigger (either TTL or Analog) is not allowed for the current device.
Corrective Actions:
•
Check that your device is capable of the using the trigger sense
provided. For instance, some devices can use TTL Above and Below
Level while not being available on other devices.
DerrInvTrigEvent 88h – 136 Invalid trigger event specified. The trigger event specified is not available for the
device being configured.
• Check that the value being passed is a legal value based upon trigger
sense values in the header file for the programming language which
you are using.
Corrective Actions:
•
Check that your device is capable of the using the trigger sense
provided. For instance, some devices can use Software Analog Level
triggers while not being available on other devices.
• Check that the value being passed is a legal trigger Event which is
defined in the header file for the programming language which you are
using.
DerrInvTrigChannel 89h – 137 Invalid trigger channel specified. The trigger channel specified for a trigger Event
is not valid.
Corrective Actions:
•
Check that the trigger channel provided is a valid channel number.
•
Check that the trigger channel provided is currently configured in the
scan list. See daqAdcSetScan for details on channel scan list
configuration
DerrDacWaveformNotActive 8Ah – 138 An invalid waveform operation has been issued while a waveform operation is not
currently active. This may occur if the application issues an API which is only
valid while waveform output is currently active.
Corrective Actions:
• Typically this error will be issued when a waveform API such as
daqDacArm function is issued while a waveform output is currently
active. The application should refrain from making such calls during an
active waveform output operation.