Content
# #south-county — 2026-02-04
**08:23 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770222193149279):** @Mason Radke this fault clears then comes right back. Can you tell me why?
![[F0ADCE0KY0H_pxl_20260204_162153049.jpg]]
![[F0AD34LTB60_pxl_20260204_162113802.jpg]]
**08:23 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770222215564019):** sure. let me look
**08:29 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770222573093419):** it doesnt look like its currently in fault, correct?
**08:29 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770222577882359):** correct
**08:29 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770222590388669):** no fault on the vfd
**08:30 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770222625871559):**
![[F0ADTT0NTEC_image.png]]
**08:30 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770222636128009):** there is a MSG that reads from something.. im assuming the drive
**08:30 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770222641042509):** and one of those bits triggers the fault.
**08:30 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770222644502229):** its currently clear. as you see
**08:30 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770222658050169):** ah
**08:31 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770222683102139):** but its N/O.. so even a comm drop out would not trigger a fault
**08:31 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770222686357989):** it would ahve to come in as a 1
**08:31 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770222700418059):** does the alarm clear now on the object?
**08:32 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770222720441479):** from scada? want me to try to reset it/clear it?
**08:32 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770222723534229):** it was clearing, then returning about 3 secs later
**08:32 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770222726333479):** yes
**08:32 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770222728699969):** ok let me try
**08:33 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770222828919039):** well thats weird
**08:35 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770222921683439):** that's what I thought
**08:35 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770222939014499):** more PAx fun!
**08:35 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770222955843049):**
![[F0ACZL1RPHQ_image.png]]
**08:36 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770222961532129):** both .sts bits are false as well
**08:36 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770222971955829):** wtf
**08:36 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770223013036599):** Michael said he thinks the reason they unchecked the "Ack required" was because this kept popping up.
**08:37 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770223071190509):** i just unchecked it and now its just coming in and out
**08:37 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770223074557009):** as it auto-acks itself
**08:38 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770223097863169):** wait maybe it stopped
**08:39 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770223185065839):** i am going to re-trigger the fault
**08:41 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770223302304289):** oops, crap was that RDT running?
**08:44 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770223473859309):** interesting. (ack is still required)... it went into fault.. it cleared.. and i was able to clear it on scada and it stayed cleared
**08:44 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770223488051629):** hope i didnt screw anything up. .i thought that system already thought it was faulted
**08:56 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770224196696219):** any idea why?
**08:56 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770224210133399):** why it cleared this time?
**08:56 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770224214213359):** yes
**08:56 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770224215203829):** no
**08:57 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770224220636419):** perfect
**08:57 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770224222344329):** lol
**08:57 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770224223171509):** something hung up in plantpax aoi
**08:57 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770224229553119):** im guessing
**08:57 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770224244272099):** alright we'll keep an eye on it
**08:57 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770224247453939):** thank yo!
**08:58 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770224291381839):** let me know if theres anything else i can help with whiel you're threre.. would be nice to knock out all that we can
**10:04 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770228259483209):** for the record:
Troubleshooting TWAS Pump 1 vfd intermittent trip on overcurrent.
Measured amperage - 5.4 - 5.6 - 6.1
I have my meter set to record min/max and am monitoring
An oddity I observed is multiple "clicking" sounds when the fault occurs vs a normal one "click" when the vfd starts normally.
Also observed the "running" light turned on, then off, then on in about one second before the fault.
There is also a VFD fault happening that does not turn on the "Fault" panel indicator right away (maybe some delay?)
**10:05 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770228306862249):** oh boy. sounds like a fun one
**10:05 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770228316403339):** clicking like relay clicking?
**10:05 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770228331711789):** yes
**10:18 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770229080977619):** I'm logging into EWS
**10:18 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770229118855919):** ok i just closed my connection
**10:40 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770230450118469):** @Mason Radke could I pull you away to help me figure out how the call translates from the RDT plc to the VFD?
**10:40 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770230456962459):** for TWAS
**10:40 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770230459971189):** yeah
**10:41 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770230469389089):** I think it is through comms
**10:41 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770230488428169):** it maybe hardwired though
**10:41 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770230497436599):** I'm tracking down drawings
**10:42 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770230527331969):** which PLC is the RDT plc? is that cp4000?
**10:42 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770230536882979):** no they are their own plc
**10:42 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770230554301609):** should pop up on linx
**10:43 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770230592536449):** oh yes i see it
**10:43 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770230596652839):** we are working on 7010
**10:43 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770230597821059):** ?
**10:46 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770230805267159):** yes
**10:48 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770230906007319):**
![[F0AD0PD4J3C_image.png]]
**10:48 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770230911703479):** i see a DO twas run command
**10:48 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770230914151979):** physical output
**10:50 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770231027961039):** copy. in the RDT?
**10:50 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770231032305799):** yes
**10:50 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770231044161379):** copy
**10:51 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770231062829739):** can you trace that back and see if there is anything that would bounce that output?
**10:52 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770231142124679):** k
**10:53 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770231207007769):** high pressure switch maybe.. but it does latch until its reset. so not likely
**10:55 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770231300218299):**
![[F0ADV3XLFPS_image.png]]
**10:55 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770231304554099):** when level drops below 1 it releases the call after 5 seconds
**10:55 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770231315560789):** shouldnt restart until > 2
**10:55 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770231323112739):** im not seeing anything weird
**10:56 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770231411754379):** copy
**11:21 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770232876375929):** it is only 1 ft difference?
**11:21 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770232890082889):** correct
**11:21 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770232902504619):** it's a really slow process so I guess that's ok
**11:22 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770232924396039):** alright, well, guess I'll dive into this bucket full of relays then
**11:22 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770232966445959):**
![[F0AD11P19H8_pxl_20260204_192221461.jpg]]
**11:23 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770232982869309):** easy peasy
**11:23 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770232992315119):** i found the issue with this message
**11:23 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770233004432149):** working on a long term solution
**11:23 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770233008171569):** Laguna?
**11:23 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770233010135039):** ya
**11:23 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770233017461709):** Change channels
**14:55 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770245754615179):** that same thing is happening again with the TWAS pump alarm if you want to take another look
**14:56 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770245810507959):** I'm grabbing some food. I can look in a bit
**15:24 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770247469014319):** Is it still doing it?
**15:30 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770247817690129):** doesn't appear so
**15:30 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770247829507089):** it just cleared while i was looking at it
**15:30 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770247832460109):** hm
**15:30 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770247853426149):** that was me
**15:31 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770247866343339):** I thought you wanted me to see if it was still having the problem
**15:31 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770247890742329):** when it happens again i can see what the animation is tied to.. because there is not .sts_drivefault
**15:31 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770247894970869):** its zero
**15:34 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770248074141869):** copy
**15:48 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770248901501619):**
```
That explains a lot. When you have a **Sine Filter** paired with a **long cable run**, you're dealing with a significant amount of capacitance.
If the VFD isn't tuned specifically for that hardware, the "inrush" required to charge the capacitors in the filter and the long cable can trip the drive's hardware overcurrent protection before the motor even starts to turn. This is likely why your meter doesn't catch it—the spike is occurring in the first few milliseconds (microseconds, even) of the IGBTs firing.
Since you've confirmed the Sine Filter is present, here is the technical "checklist" to stop those nuisance trips on a DG1:
### 1. Confirm P8.11 is Enabled
As we discussed, **P8.11 must be set to 1**. This tells the drive to ignore that initial capacitive "gulp" of current and usually prevents the drive from trying to perform certain motor ID steps that could fail through a filter.
### 2. Check Switching Frequency (P8.9)
Sine wave filters are designed for a specific switching frequency range (usually 4kHz to 8kHz).
* **The Risk:** If the switching frequency is too low, the filter won't "smooth" the wave correctly, causing high ripple current. If it's too high, the VFD might overheat or the filter might saturate.
* **Action:** Check the nameplate on your Sine Filter. It will list a **Required Switching Frequency**. Ensure **P8.9** matches that value exactly.
### 3. Disable "Flying Start" (P1.14)
If the drive is trying to perform a "Flying Start" (catching a spinning load), it sends out a frequency sweep to "find" the motor. Through a sine filter and long cable, the resonance can cause an immediate overcurrent trip.
* **Action:** Set **P1.14** to **0 (Frequency Start)** or **Direct Start** unless your application strictly requires catching a spinning motor.
### 4. Adjust the Flux Start/Pre-heat
If the drive is trying to magnetize the motor through that filter at 0Hz, the filter's inductors can sometimes saturate.
* **Action:** Check **P8.1** (Magnetizing Current). If it's set high, try backing it down slightly, or increase the **Start Frequency (P1.12)** so the drive "jumps" past the resonance point of the filter immediately.
### 5. Check "Voltage Boost" (P8.15)
With a long cable run, you have voltage drop; however, with a sine filter, you have a resonant circuit. If **P8.15** (Manual Torque Boost) is set too high, the drive is pushing extra voltage into a capacitor (the filter), which results in a massive current spike.
* **Action:** Try setting **P8.15 to 0.0%** to see if the drive will start.
---
**Next Step:**
Would you like me to check the specific **Switching Frequency** requirements for a particular filter brand, or should we look at the **Cable Length** parameters to see if the drive needs to compensate for the distance?
```
**15:54 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770249299804999):** There's no delay on over current? I thought it had to be over for a certain amount of time
**15:55 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770249323534279):** This sounds complicated
**19:27 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770262044383739):** The fact that the overcurrent trips immediately rather than after a time delay points to an issue with either VFD settings or the VFD itself. In this case, it appears that enabling the P8.11 "Sine Filter" setting may have solved the problem.
**19:28 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770262137223209):** I found that the apparent "flickering" of the start signal was actually the VFD auto-reset function being set with a delay of 1 second. So when the VFD would see overcurrent, it would reset one second after, then trip a second time, and trip for good because number of tries was set to 1.
**19:29 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1770262153710589):** I increased the auto-reset delay to 5 seconds.
**20:02 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1770264121651159):** could that have been causing the fault signal to be coming in over and over?