-
Notifications
You must be signed in to change notification settings - Fork 9
Add FFI Functions for Clamp Control #2559
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
this was previously done directly in the GUI event handler
|
Let's do your usual appraoch here where Luke/Tim can test the FFI functions before we write the tests. |
b0dcd0b to
2f8e923
Compare
In MIES the range is limited through the corresponding GUi element. However, when changed externally through a ZeroMQ function call then the range was not checked.
Added the following functions: FFI_GetClampState returns a wave with the current clamp control values FFI_SetClampMode FFI_SetHoldingPotential - allowed only in VC mode FFI_SetBiasCurrent - allowed only in IC mode FFI_SetAutoBias - allowed only in IC mode FFI_SetHeadstageActive - allowed only when no DAQ is running FFI_TriggerAutoClampControl - wraps Pipette, Capacitance and Bridge Balance auto setting in a single call
2f8e923 to
d5bf06c
Compare
|
If the current clamp mode for the headstage in MIES is different from the specific calmp mode of an amplifier setting (e.g. auto bridge balance that applies only to IC) then it is ignored by MIES. |
|
I gave this a try today:
|
That makes sense for any of the TriggerAuto* functions, but all other parameters I would expect to be settable even when the mode is not active (for example, I should be able to set the auto bias parameters before switching to IC) |
close #2547