[INSTRM-869] Arrange for the ionpump pressure rise alarm/shutdown to be ignored. Created: 19/Dec/19  Updated: 28/Jul/23  Resolved: 28/Jul/23

Status: Won't Fix
Project: Instrument control development
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Normal
Reporter: cloomis Assignee: cloomis
Resolution: Won't Fix Votes: 0
Labels: SPS
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File sm2_b2_ionpumps_stop_20200619_3.png     PNG File sm2_b2_ionpumps_stop_20200722.png    
Issue Links:
Relates
relates to INSTRM-772 Shutdown ion pump when high pressure ... Done
Story Points: 4
Sprint: SM1PD-2020 A, SM1PD-2020 B, SM1PD-2020 C, SM1PD-2020 K

 Description   

We added a shutdown trigger for the ion pumps in INSTRM-772. That has a buffer to get past startup impulses, but we also get spikes when, e.g. the gatevalve is opened or the other pump started.

I do not like the idea of always ignoring 60s spikes, and think we should add a mechanism to temporarily pause or modify the shutdown trigger. Could be started when the cooler, gatevalve, or ionpump state is changed.

 Comments   
Comment by cloomis [ 08/Jan/20 ]

arnaud.lefur fmadec How about this:

  • use the same mechanism which is used to ignore turn on spikes: a config.ionpump.spikeDelay window inside which we warn but do not reject readings above config.ionpump.maxPressure. The default values are currently 300s and 3e-5 Torr.
  • when the gatevalve is opened, restart that window.
  • or when an ionpump allowSpikes command is sent, restart that window.

On further reflection, I wonder if we should have soft and hard limits, where we always turn off the pumps when the hard limit is hit. 5e-4 Torr or so?

Do we have useful data on these spikes? How high, how long, etc.?

Comment by fmadec [ 22/Jul/20 ]

I don't know if it is the right place but:

here are some plots of the b2 ionpump stop

 

Comment by cloomis [ 28/Jul/23 ]

Superseded by INSTRM-2050

Generated at Sat Feb 10 16:29:29 JST 2024 using Jira 8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b.