User: ptonsparky, Location: NE (9.06 miles @5.9 Degrees from Winged Horses)
Asked on: Friday, October 24, 2025 at 9:21 am EDT
Answered on: Friday, October 24, 2025 at 9:21 am EDT
Question: I've done small scale PLC for 40 years or so and this is the first time I've had an input fail. Voltage to it but no response. I've been using a two second delay to flag a coil failure, which is fine once up and running. I changed it to one second but feel I could make it even less.PLC output to an interposing relay that then controls a starters 480v coil. Input back to the PLC via the starter's aux contacts. Any educated guesses as too how long that should take? IIRC program scan time is about 10 milli second. I'm not worried about contact bounce.
Alright, 40 years and this is your first input failure? That's a testament to your skills and quality equipment! Let's dial in that fault detection time.Here's a breakdown of the delays involved and a reasonable estimate
Delays in the System:
1. PLC Output Response
The PLC sending the signal to energize the interposing relay is very fast. It's essentially instantaneous compared to the other components. Consider it less than 1 ms.2.
Interposing Relay Pickup Time
This is the first significant delay. Relay pickup times typically range from
5-20 ms. Consult the relay's datasheet for the exact specification. A good assumption is around 10 ms unless you have the datasheet.3. Starter Coil Energization
Similar to the interposing relay, starter coils generally energize in the range of
10-30 ms. Again, the datasheet is your best source, but 20 ms is a reasonable assumption.4. Starter Auxiliary Contact Closure
This happens essentially simultaneously with the starter coil energizing. It's mechanically linked. So, the delay is included in the starter coil energization time.5.
PLC Input Response
The PLC reading the input is extremely fast, again less than 1 ms.6.
PLC Scan Time
You stated your PLC scan time is around 10ms, but that's only the time to process one loop through the program. It may take 2 scan cycles to detect the change in input. So assume
20ms.
Total Estimated Delay
1 ms (PLC Output) 10 ms (Interposing Relay) 20 ms (Starter Coil) 20 ms (PLC Scan time) -------
51 ms Total Estimated DelayRecommendations
Target Delay Time
Based on these estimates, a
100ms - 150ms delay for fault detection should be reliably safe. It gives a generous buffer for variations in component performance and age. Experiment Carefully
Gradually reduce the delay time in your PLC program in small increments (e.g., 25ms at a time). Carefully monitor the system's behavior. You're looking for false positives (flagging a coil failure when it's actually working).
Consider Worst-Case Scenarios
Think about factors that could slow down the system:
Low Voltage
If the 480V supply is consistently low, the starter coil may energize slower.
Worn Components
Older relays and starters may have slightly slower response times due to increased friction or coil degradation.
Datalogging
If your PLC has datalogging capabilities, record the status of the output and the input over time. This provides valuable data for fine-tuning the delay and troubleshooting future problems.
Consider a "Staggered" Approach
If you need very fast detection, consider a tiered approach:
Fast Alert (e.g., 50ms)
This triggers a warning signal.
Delayed Trip (e.g., 500ms - 1 second)
If the input still hasn't come on after this longer delay, initiate a shutdown/fault.
Important Considerations for Input Failure
Root Cause Analysis
Now that you've had an input failure, thoroughly investigate the cause. Was it:
Wiring
A loose connection or broken wire?
Input Module
Failure of the input module itself?
Auxiliary Contact
A burned or sticking contact in the starter?
Noise
Electrical noise interfering with the input signal? (Less likely with a hardwired aux contact, but still possible).*
Input Module Type: What type of input module are you using (e.g., discrete, analog)? If it's discrete, is it sinking or sourcing? This can affect troubleshooting.By carefully considering the component delays and implementing a robust testing strategy, you can optimize your fault detection time while minimizing the risk of false alarms. Good luck! Flag for review