Skip to content
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

Seal mode bugs #212

Open
campagnola opened this issue Mar 13, 2024 · 4 comments
Open

Seal mode bugs #212

campagnola opened this issue Mar 13, 2024 · 4 comments

Comments

@campagnola
Copy link
Contributor

Some bugs encountered in seal mode that may or may not be related:

  • When crossing the 100 MΩ threshold, holding should switch to -70 mV. Sometimes this doesn't happen, and it may be related to the auto bias being on or off.
  • When crossing the 1 GΩ threshold, sometimes the state doesn't transition to cell attached

Related: I think the auto bias button should not affect the holding potential when in VC mode, but currently that might not be the case. The options while in VC should be:

  • "off" -> no auto bias is applied when switching to IC
  • "VC" -> when switching to IC, the VC holding potential is used as the initial auto bias value
  • "manual" (maybe?) user manually sets the auto bias value
@jessicatrnh
Copy link
Contributor

This is related to task #208

@jessicatrnh
Copy link
Contributor

Noted issues with seal feature 02/27/2024

@jessicatrnh
Copy link
Contributor

jessicatrnh commented Mar 21, 2024

Still seeing issues with -1kPa not being applied continuously when seal function is enabled. Auto mode switch between regulator and atmospheric with brief pulses of -1kPa in regulator over 5 iterations. ~5 seconds in A mode and brief switch to R mode. -70mV not applied when 100MOhm reached.

state defaults to "fouled" when seal feature fails.

@outofculture
Copy link
Collaborator

Issues aren't seen when seals happen quickly. Workaround is to re-enter Seal mode multiple times. Holding gets turned off completely if seal fails. Test pulse analysis needs to be improved to better handle "next state" behavior. The switching to Atmosphere is the worst of the current behaviors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants