Content
# #paso-vinedo-boost — 2026-03-25
**11:26 [andy](https://slack.com/archives/C0APPMD2AUQ/p1774463170095949):** in case it causes confusion, correct typo, "Vinedo"
**11:26 [Kevin](https://slack.com/archives/C0APPMD2AUQ/p1774463192297399):** has renamed the channel from "paso-vindeo-boost" to "paso-vinedo-boost"
**11:33 [andy](https://slack.com/archives/C0APPMD2AUQ/p1774463597311339):**
Ok my dudes, this project has been in progress for the better part of a year.
My panel is built, it's being shipped to Tesco for them to install it into their MCC.
I'm waiting to hear back when they are ready for me to perform the FAT at their location which requires my program to be ready to run.
I have the program mostly built, I have an ACD file and Ignition pretty ready.
@Mason Radke I need you to modify the program to run 4 VFDs, 2-4 are duty pumps, 1 is the high flow (weird order, I know).
**11:33 [andy](https://slack.com/archives/C0APPMD2AUQ/p1774463613254429):** I want to use LLS, everything else like the other Orchard Bungalow program.
**11:33 [Mason Radke](https://slack.com/archives/C0APPMD2AUQ/p1774463627999709):** should be an easy modification
**11:39 [andy](https://slack.com/archives/C0APPMD2AUQ/p1774463978914109):** I will confirm more complicated control strategy soon. I just talked to the customer and I don't think we have total clarity on what we are doing yet. But I'm establishing this project in all of our brains.
**11:47 [andy](https://slack.com/archives/C0APPMD2AUQ/p1774464447593249):**
![[F0ANZ6CNMLL_image.png]]
**11:47 [andy](https://slack.com/archives/C0APPMD2AUQ/p1774464477286859):** All objects are created an linked, and IO is linked for the most part, to the PAX Objects.
**12:18 [andy](https://slack.com/archives/C0APPMD2AUQ/p1774466316277899):**
Claude came up with this;
P_LLS is *worth using for Pumps 2, 3, and 4* — specifically for motor management: fault handling, run-time-based alternation, standby promotion, and the HMI faceplate. Those are real time-savers. But it's *not a complete solution* for this strategy. The pressure-based start logic, flow-based stop logic, speed synchronization between duty pumps, and Pump 1 integration all have to be custom-written external to P_LLS, with P_LLS simply receiving the resulting demand signal. Think of it as a useful building block rather than the control strategy itself.
**12:19 [Mason Radke](https://slack.com/archives/C0APPMD2AUQ/p1774466345778289):** absolutely
**12:19 [Mason Radke](https://slack.com/archives/C0APPMD2AUQ/p1774466353475949):** it wont do it all.. just handles pump rotations nicely
**12:19 [Mason Radke](https://slack.com/archives/C0APPMD2AUQ/p1774466373197559):** this is how we're using it currently
**12:20 [andy](https://slack.com/archives/C0APPMD2AUQ/p1774466408914929):**
What CALLS the Pumps
Pumps are called entirely based on *discharge pressure dropping below setpoints*, with time delays to avoid nuisance starts:
• *Lead duty pump* is called when discharge pressure falls below *45 PSI* and stays there for *10 seconds*
• *Lag duty pump* is called when the lead pump alone cannot bring pressure back up to 45 PSI and that condition persists for *10 seconds*
• *Pump 1* (fire flow) is called when _both_ lead and lag duty pumps together still cannot maintain 45 PSI for *10 seconds*
All pressure setpoints and time delays are operator-adjustable via the OIT.
What Dictates SPEED
Once called, pump speed is controlled by the *PLC's internal PID loop* using the *discharge pressure transmitter signal* (4–20 mA, 0–200 PSI) as the process variable. The PLC modulates VFD speed up or down continuously to chase the pressure setpoint. A few nuances:
When both lead and lag duty pumps are running, the PLC *locks their speeds together* — they always run at the same speed simultaneously
Pump 1 uses its *own dedicated discharge pressure transmitter* (separate from the combined 8" header transmitter used for Pumps 2–4) for its PID reference
• Flow rate is monitored in parallel but does *not* drive speed — it only influences shutdown decisions (see below)
What RETIRES the Pumps
Retirement is a mix of *flow-based and pressure-based* logic, working in reverse order from how they were called:
• *Lag duty pump stops* when flow drops to *80%* of the lead duty pump's capacity and holds there for *30 seconds*
• *Lead duty pump stops* when flow drops further to *40%* of its capacity and holds there for *30 seconds*
• *Pump 1 stops* when flow drops below *500 GPM* and holds there for *30 seconds*
So the key distinction is: *pressure calls the pumps in, flow retires them out*. This asymmetry makes sense — you don't want a pump to short-cycle by starting and stopping on the same pressure signal, so flow rate (a more stable indicator of actual demand fading) is used to confirm that it's genuinely safe to step a pump down.
All flow thresholds and time delays are operator-adjustable on the OIT.
**12:20 [andy](https://slack.com/archives/C0APPMD2AUQ/p1774466437096649):** This is not how Orchard Bungalow was done. There was pressure setpoints only, no retiring based on flow.
**12:21 [Mason Radke](https://slack.com/archives/C0APPMD2AUQ/p1774466481811929):** did we discuss having some flow control in there? i dont remember
**12:21 [andy](https://slack.com/archives/C0APPMD2AUQ/p1774466485872669):** They are asking for me to be ready to test Mid April with this. I will be driving up there, loading the program and running VFDs at their shop simulating system pressure with the PAX object, so it needs to be ready ready
**12:21 [andy](https://slack.com/archives/C0APPMD2AUQ/p1774466494634849):** Can you achieve this?
**12:21 [Mason Radke](https://slack.com/archives/C0APPMD2AUQ/p1774466509755229):** i am gone all of april
**12:21 [Mason Radke](https://slack.com/archives/C0APPMD2AUQ/p1774466518568559):** i will have time here and there for remote work
**12:22 [andy](https://slack.com/archives/C0APPMD2AUQ/p1774466552020059):** Ah i thought it was for part of april. This is a problem for me then.
**12:23 [andy](https://slack.com/archives/C0APPMD2AUQ/p1774466607935969):** i also need you to finish Cambria Water Opto project as well, and control strategies for Cambria SST Wastewater.
**12:23 [andy](https://slack.com/archives/C0APPMD2AUQ/p1774466626175479):** I've become very reliant on you
**12:24 [Mason Radke](https://slack.com/archives/C0APPMD2AUQ/p1774466663017199):** my calendar fills up fast these days.. i highly suggest working with kevin on getting things on the calendar
**12:24 [Mason Radke](https://slack.com/archives/C0APPMD2AUQ/p1774466669105919):** opto is very close
**12:24 [Mason Radke](https://slack.com/archives/C0APPMD2AUQ/p1774466678904709):** and is next on my list
**12:25 [andy](https://slack.com/archives/C0APPMD2AUQ/p1774466714626889):** Vinedo is higher priority than Opto since we didn't make enough progress in between projects.
**12:26 [Mason Radke](https://slack.com/archives/C0APPMD2AUQ/p1774466793681629):** I will be working from the road in april, but there are times where ill be completely offline. maybe part of one week here, and part of another work week there.. a handful of days.. i will be able to be productive.
**12:27 [Mason Radke](https://slack.com/archives/C0APPMD2AUQ/p1774466858479049):** i have to so much to do, i work off of our calendar... we really need to coordinate to get things scheduled or i will get buried.. just gonna be a process to figure out
**12:27 [andy](https://slack.com/archives/C0APPMD2AUQ/p1774466863577209):** Thanks for the update
**12:28 [andy](https://slack.com/archives/C0APPMD2AUQ/p1774466923349939):** Yeah I feel like I have tried to make everyone aware of these projects and aware of the progress deadlines and I think that hasn't happened. I will need to make some adjustments.
**12:28 [andy](https://slack.com/archives/C0APPMD2AUQ/p1774466934725159):** @Kevin can you give me a call when you have a minute
**14:24 [Mason Radke](https://slack.com/archives/C0APPMD2AUQ/p1774473885354499):** Code for this should only take a day. I’m sure we can get that done. Once you know dates for commissioning let us know and we can schedule it. I'll let you know which days I won't be a available at all