MIES wrong gain in Current Clamp

[StanDriessens]

Description:

• What was MIES doing at the time of the unexpected behavior?
  When moving from VC to CC test pulse. Gains are incorrect resulting in -1450 mV membrane
  potential. This only happens on systems with NI digitizers. Restarting MutliClamp commander and relocking digitizer + pressing autofill on the gain solves the problem. But requires holding voltage to be turned off. After this it does not reoccur until the system is restarted. If necessary we can upload experiment file where this happened.

• Did user input immediately precede the unexpected behavior?

• What did you expect to happen?

Igor Pro Experiment files can be attached as zip file if needed.

The following contains installation information (keep unchanged):

MIES version: Release_2.6_20220606-71-g496c8c28
Date and time of last commit: 2022-07-25T13:06:17+02:00
Submodule status:
 e46385bee5c53a0daa1eca0c1d6af44d19677c13 Packages/IPNWB (e46385b)
 56f1da31d786a593892280c2d2b2b1190def0fb5 Packages/doc/doxygen-filter-ipf (heads/main)
 a8d4707e7c72555baefbb9a4d52de920e1d8ebb9 Packages/unit-testing (a8d4707)

Igor Pro version: OS:Microsoft Windows 10 Pro (22H2);OSVERSION:10.0.19045.4894;LOCALE:US;IGORFILEVERSION:9.0.1.2;

Installation self-test results:
Checking system properties:
Igor 64bit: 9.01, 39200
Windows 10: True
ASLR: True (Very Bad)

Checking known defines:
DEBUGGING_ENABLED: No
EVIL_KITTEN_EATING_MODE: No
BACKGROUND_TASK_DEBUGGING: No
THREADING_DISABLED: No

Checking base installation:
Mies version info: Valid "Release_2.6_20220606-71-g496c8c28..." (Nice!)
ITC XOP: Found version 1.0.2.0 (Nice!)
JSON XOP: Found version 1.0.0.1 (Nice!)
VDT2 XOP: Found version 3.0.0.0 (Nice!)
Axon Telegraph XOP: Found version 3.0.0.0 (Nice!)
Multi Clamp Commander XOP: Found version 2.0.0.0 (Nice!)
ZeroMQ XOP: Found version 1.0.0.1 (Nice!)
JSON XOP: Present in the right version (version-770-g9d1bd48) (Nice!)
ITC2 XOP: Present in the right version (5fe4ed6) (Nice!)
Results: 8 checks, 1 number of errors

Checking extended installation:
NI-DAQ MX XOP: Found version 1.1.5.0 and hash is ok (Nice!)
Results: 1 checks, 0 number of errors

[t-b]

Thanks for the report.

Does that error happen consistently?

Have used a different MIES version before which did not show the bug?

Do you use a JSON configuration file or do a manual setup?