Content
# #rancho-ynecita — 2026-02-09
**06:59 [Mason Radke](https://slack.com/archives/C09D358F91R/p1770649189632529):**
![[F0ADQ12L799_image.png]]
**07:00 [Mason Radke](https://slack.com/archives/C09D358F91R/p1770649216894779):** estes is faulted.. we're getting the fail to start which is good, but i'll make sure there is a fault alarm
**07:04 [Kevin](https://slack.com/archives/C09D358F91R/p1770649456578959):** I turned off my alarms the other night.
**07:20 [Kevin](https://slack.com/archives/C09D358F91R/p1770650412283799):** When it faults on fail to start does it keep trying to start or does it need a reset first
**07:48 [Mason Radke](https://slack.com/archives/C09D358F91R/p1770652115389099):** I’ll have to look
**08:15 [Mason Radke](https://slack.com/archives/C09D358F91R/p1770653708500349):** had to drop my car off for service
**08:15 [Mason Radke](https://slack.com/archives/C09D358F91R/p1770653710249189):** im logged in now
**08:15 [Mason Radke](https://slack.com/archives/C09D358F91R/p1770653724467429):** if its actually faulted it probably shouldnt keep trying to start right?
**08:33 [Mason Radke](https://slack.com/archives/C09D358F91R/p1770654837482279):** so its not faulted. our Fail To Start status just shows as faulted.
**08:34 [Mason Radke](https://slack.com/archives/C09D358F91R/p1770654849205309):** want me to latch that as an interlock so it doesnt retry?
**08:36 [Mason Radke](https://slack.com/archives/C09D358F91R/p1770655000869229):** hm, it already does latch until reset.
**08:36 [Mason Radke](https://slack.com/archives/C09D358F91R/p1770655005040769):** let. me see why this alarm keeps coming in
**08:49 [Mason Radke](https://slack.com/archives/C09D358F91R/p1770655763538769):** so it only triggered once on SCADA.. its either vtscada re-sending the notification every 10 minutes or signl4 doing something
**08:53 [Mason Radke](https://slack.com/archives/C09D358F91R/p1770656017077149):**
![[F0ADR11T9R9_image.png]]
**08:54 [Mason Radke](https://slack.com/archives/C09D358F91R/p1770656040858669):** found it.. do we want repeating notifications? once i acknowledged the alarm on VTscada, it stopped alerting
**08:54 [Mason Radke](https://slack.com/archives/C09D358F91R/p1770656061646989):** its kind of nice for letting us know that something needs to be looked at.. one and done might be easier to ignore
**08:54 [Mason Radke](https://slack.com/archives/C09D358F91R/p1770656065645529):** let me know what you think
**08:55 [Mason Radke](https://slack.com/archives/C09D358F91R/p1770656107867139):**
![[F0ADR1CR2HH_image.png]]
**08:55 [Mason Radke](https://slack.com/archives/C09D358F91R/p1770656132816659):** once i ack the alarm, it stopped notifying on signl4.. once i hit reset, it cleared the fail to start alarm and its ready to try again.
**08:58 [Mason Radke](https://slack.com/archives/C09D358F91R/p1770656308125719):** it was not retrying to start the pump every 10 minutes.. it was latched out until we hit reset..
**09:25 [Kevin](https://slack.com/archives/C09D358F91R/p1770657916166019):** Copy. I'm conflicted as to if it should try to restart. In our case where it seems it is a comm issue, then yes I want it to keep trying. But if it's an actual problem then I'm not sure I do. But I can't think off hand what event would be that we would want it to not try again.
**09:26 [Mason Radke](https://slack.com/archives/C09D358F91R/p1770657962261839):** we could increase the fail to start timer.. give it something long like 10 minutes
**09:27 [Kevin](https://slack.com/archives/C09D358F91R/p1770658048038059):** Good idea. Let's try that