You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking under the hood, this exception is caused because these two enums in constants.py dont share the same names and so enum_bitfield_to_list calls next with an empty list
D'oh, nice find. This is also broken for device.ai_couplings because of these two enums:
class_CouplingTypes(Enum):
AC=1#: Device supports AC couplingDC=2#: Device supports DC couplingGROUND=4#: Device supports ground couplingHF_REJECT=8#: Device supports High Frequency Reject couplingLF_REJECT=16#: Device supports Low Frequency Reject couplingNOISE_REJECT=32#: Device supports Noise Reject couplingclassCoupling(Enum):
AC=10045#: Remove the DC offset from the signal.DC=10050#: Allow NI-DAQmx to measure all of the signal.GND=10066#: Remove the signal from the measurement and measure only ground.
I've got some spare time today, so I'll look into why our internal metadata/generator is being inconsistent here.
This was found following the 'example of using an nidaqmx.system.System object' at https://nidaqmx-python.readthedocs.io/en/latest/
Looking under the hood, this exception is caused because these two enums in constants.py dont share the same names and so enum_bitfield_to_list calls next with an empty list
The text was updated successfully, but these errors were encountered: