I have been having trouble with enabling and disabling the Counters with configIO(). It doesn't seem to work like the way I would expect it to. If I run the command, d.configIO(EnableCounter0 = True) it sets Counter0 to True and Counter1 to False, but if I do the command d.configIO(EnableCounter = False) it does the exact same thing setting Counter0 to True and Counter 1 to False. I found that whether you set it to True or False does not matter at all. If you set it equal to anything, it will set that Counter to True and the other one to False. If I declare both of them, They will both be equal to true no matter what I set it equal to. This set up would be fine for what I am doing if only I knew a way to set them both equal to False. Any help with this problem would be great.
.png%3Fitok=PHGBxf6M "EEV Blog Reviews LabJack T7-Pro & Software Tools")
.jpg%3Fitok=B1YcuDFK)
.png%3Fitok=Ybt-OlgU "LabJack + JEDI One Can Create a Powerful Distributed DAQ Ecosystem")
That is a bug. configIO is enabling the counter when EnableCounter0 or EnableCounter1 are set, ignoring the True/False value. The default, non set value (None) disables the counter. Thanks for catching that and reporting it. I fixed the issue in our LabJackPython repo. on GitHub. Download and install this version to fix the issue:
https://github.com/labjack/LabJackPython
configIO will now set EnableCounter0 or EnableCounter1 properly to the True/False value set.
Here are some further details on EnableCounter0 and EnableCounter1. The following parameters are set together due to how the low-level protocol works:
TimerCounterPinOffset, default of None = 4
EnableCounter1, default of None = False
EnableCounter0, default of None = False
NumberOfTimersEnabled, default of None = 0
If any are set, the other parameters need to be configured or they will be configured with the default value mentioned above. If none are set, the method does not configure these settings and only reads the current configuration.
Thanks so much! It works great now.