Source: Tempo Communications Webinar
Presenter: Alejandro Asencio, Associate Product Manager - Irrigation
Two-Wire System Overview
What is Two-Wire?
Two-wire irrigation systems require only two wires from the controller to operate many valves in the field, as opposed to conventional systems that require one wire per valve plus a common.
Key Characteristics:
Significantly reduces wire requirements for large systems
Uses decoders as intermediaries between controller and valves
The two wires must always be kept separate and not touching
Different colored wires recommended for tracking
Many systems have constant voltage for two-way communication between controller and decoders
When Two-Wire Makes Financial Sense
Break-even point: Approximately 30-40 valves
Optimal for: Systems with many valves (can operate hundreds on one wire path)
Long-distance capability: Can operate valves across much larger distances.
Expansion advantage: Add zones by extending wire path, not running new wires back to controller
Two-Wire vs. Conventional Wiring
Conventional System:
One wire per valve from controller
Wire bundle grows with each valve
Expansion requires running wire back to controller
Simpler troubleshooting (isolated circuits)
Two-Wire System:
Two wires total for entire wire path
Can operate hundreds of valves
Easy expansion (add to end of wire path)
Requires decoders
More complex troubleshooting (shared circuit)
System Components
1. Controller
Sends voltage and digital communication signals
Provides diagnostics and error messages
May have "short finding mode" or "wire test mode"
Can communicate with decoders bidirectionally (on two-wire/non-conventional systems)
2. Two-Wire Path
30 VAC RMS over two-wire
Supports up to 1.45 amp output
Must use proper two-wire cable (separate colors recommended)
Runs throughout the site connecting all valve boxes
Can be configured as:
Branched/Star pattern (recommended for troubleshooting)
Loop pattern (adds redundancy but harder to troubleshoot)
For more two-wire details see Baseline Two-wire Technical Specification
3. Valves and Solenoids
Standard irrigation valves with solenoids
Solenoid resistance should measure 20-60 ohms
Connected to decoder via two wires
4. Splices
Each valve box contains minimum of 4 waterproof splices:
Two splices connecting decoder to two-wire path
Two splices connecting decoder to solenoid
5. Grounding System
Grounding plates or rods placed periodically along wire path
Surge arrestors at each grounding point
Protects system from lightning damage
Critical because entire system is one linked circuit
For more grounding details see Baseline Surge Arrestor & Grounding Specification
Common Failure Points
Primary Causes of Failure (in order of frequency):
Bad Splices (Most Common)
Compromised waterproofing
Corrosion in connections
Water intrusion leading to decoder failure
Failed Decoders
Usually caused by water intrusion from poor splices
Constant voltage attracts water into exposed connections
Electricity + water = accelerated corrosion
Damaged Wire Insulation
Nicking inner conductors during jacket stripping
Cable damage from digging or landscaping
Repeated thermal expansion/contraction stressing nicked wires
Why Splices Are Critical
Systems with two-way communication are especially vulnerable because:
Constant voltage on the wire path
Electricity literally attracts moisture into exposed connections
Heating/cooling cycles from valve operation create stress
Small imperfections become major failures over time
Proper Splicing - DBRY6 Waterproof Splices
Correct Installation:
Wires must be undamaged (no nicked copper)
Don't overtighten wire twist
Waterproof gel must be pushed away from tube end
Creates protective gel layer from connection to tube opening
Wire nut must be fully inserted into tube
Inadequate Methods (DO NOT USE on two-way communication systems):
Gel-filled wire nuts alone (insufficient protection)
Standard wire nuts with electrical tape
Any non-waterproof connection method
Additional Resources
Recommended: Noe Cruz YouTube video on splicing methodology
20-minute detailed video
Claims 100% success rate with his method
May differ from standard industry methods
Extensive field experience
The Milliamp Clamp Meter Tool
Why a Milliamp Clamp Meter is Essential
Primary Advantage: Non-invasive troubleshooting
No need to break connections
Preserves existing splices
Saves time and materials
Prevents introducing new problems
Without a Milliamp Clamp Meter:
Must physically break wire path in half
Test each section separately
Replace splices each time ($$ and time)
Risk creating new problems with new splices
Walk back and forth to controller repeatedly
ROI: Tool pays for itself quickly through time and materials saved
How It Works
Measures outgoing current on the two-wire path to determine what's happening downstream:
Good decoders: 0.5 - 1.5 milliamps idle (consistent per model)
Failed decoder/short: Much higher current draw
Disconnected decoders: Lower current than expected
Understanding Waveforms
Standard AC Power:
60Hz in USA, 50Hz in other countries
Smooth sine wave
Easy for most meters to read. True RMS handles any waveform accurately
Two-Way Communication:
Rapid bursts of data superimposed on main voltage
Can interfere with measurements
Low Pass Filter eliminates these bursts from readings
Electrical Fundamentals
Ohm's Law Review
V = I × R
Where:
V (Voltage): Electrical pressure (like water pressure from pump)
I (Current): Flow rate of electricity (what clamp meter measures)
R (Resistance): Restriction to flow
Key Principle: With constant voltage from controller:
Lower resistance = Higher current (overcurrent/short)
Higher resistance = Lower current (normal operation)
Very high resistance = No current (open circuit/disconnect)
Water System Analogy
Think of two-wire system as water main and sewer line serving houses on a street:
Components:
Water main: One wire supplying power
Sewer line: Other wire returning power
Houses: Decoders consuming water/electricity
Leaky toilet: Bad decoder (constant high usage)
Burst water main: Short circuit (massive flow)
Broken fire hydrant: Ground fault (water/current leaking to earth)
Closed valve: Open circuit (no flow to houses downstream)
Why This Analogy Works:
Current flows out on one wire, returns on the other
Clamping both wires = average of flow in/out = zero reading
Must clamp only one wire at a time
Upstream has more total flow than downstream
Can identify problem location by where flow changes
Troubleshooting Process
Step 1: Controller Diagnostics
Is the controller turning on?
If NO, check:
Power switch position
Blown fuses
Supply voltage to transformer (should be 120V AC in USA)
Transformer output voltage (should be 24V AC typically)
Connections and wiring
If controller won't turn on WITH wire paths connected:
Disconnect all wire paths from controller
If controller now turns on: Overcurrent condition exists
If controller still won't turn on: Controller problem
If YES, review controller information:
Overcurrent errors?
Specific zone offline messages (zones 18-23 offline)?
Current usage readings?
Diagnostic error codes?
Step 2: Identify Wire Path Configuration
Break any loops before troubleshooting:
Loop systems: Wire path forms complete circle
Makes "upstream vs. downstream" ambiguous
Break connections at furthest points of loops
Converts system to star/branched pattern
Enables clear upstream/downstream measurements
Document your system:
Create or reference system map
Know where valve boxes are located
Understand branching patterns
Mark wire path colors if available
Step 3: Isolate Problem Wire Path
If multiple wire paths exist:
Disconnect wire paths one at a time from controller
Check if error clears with each disconnection
When error clears, you've identified problem path
Reconnect to verify error returns
Focus troubleshooting on that wire path only
Step 4: Determine Problem Type
Three Main Problem Categories:
A. Overcurrent (Short/Ground Fault)
Controller shows overcurrent error or enters short finding mode
High current readings on milliamp clamp meter
Most common problem requiring clamp meter
B. Open Circuit (Disconnection)
Specific zones offline
Lower than expected current readings
May affect multiple consecutive zones
C. Individual Device Problems
Specific zone errors
May only occur when zone operates
Often solenoid-side of decoder
Step 5: Resistance Testing (if needed)
Test 1: Wire-to-Wire Resistance
Disconnect two-wire path from controller
Measure resistance between the two wires
Expected: Very high resistance (>600kΩ or "OL" for overload)
Problem if: Low resistance indicates short
Test 2: Wire-to-Ground Resistance
Measure between each wire and ground lug at controller
Ground lug should have continuity to earth
Expected: Very high resistance (>600kΩ or "OL")
Problem if: Low resistance indicates ground fault
Test 3: Wire Continuity (Shorted End Test)
Short the two wires together at furthest point
Measure resistance between wires at controller
Expected for 14-gauge: 2.5 ohms × 2 × (distance in thousands of feet)
Example: 1,000 feet of 14-gauge = 5 ohms total
Expected for 12-gauge: 1.6 ohms × 2 × (distance in thousands of feet)
Problem if: Much higher = bad splice/corrosion in path
Test 4: Solenoid Resistance
Measure across solenoid wires
Expected: 20-60 ohms
Problem if: Outside this range (open or shorted solenoid)
Step 6: Current Testing Setup
If controller has short finding/wire test mode:
Use this mode for testing
Provides steady current for measurements
May display current draw digitally
If controller is damaged or won't provide test mode:
Create External Power Supply:
Components needed:
Transformer rated for minimum 25 volt-amps or 1 amp current
Standard irrigation solenoid
Wire connectors
Assembly:
Connect transformer to power
Splice solenoid into ONE wire only from transformer
Connect other wire directly from transformer to wire path
Solenoid limits current to safe 200-300mA range
Prevents transformer burnout and decoder damage
Alternative if controller shuts down but isn't damaged:
Splice solenoid into one wire at controller output
Adds enough resistance for controller to operate safely in test mode
Safety Warning: Never connect transformer directly to wire path without solenoid current limiter. Can cause:
Transformer burnout
Tripped breakers
Overheated/melted/ignited decoders
System damage
Measurement Techniques
Using the Milliamp Clamp Meter
Setup:
Set meter to milliamps (first position on dial)
If measuring idle system with communication, hold HOLD button for 2 seconds to engage Low Pass Filter (LPF will appear on display)
Clamp around only ONE wire at a time
Wait 2-3 seconds for steady reading
Critical Rule: Clamp Only One Wire
Why:
Current flows opposite directions on the two wires
Clamping both = average of both = zero (false reading)
Must measure each wire individually
Exception: Clamping both wires can detect imbalance from ground fault on single wire, but not useful for most troubleshooting.
Interpreting Current Readings
Current Math:
Total current = Number of decoders × Current per decoder
Example: 28 decoders × 1.4mA each = 39.2mA total
Measurement Locations:
At controller: 100% of system current
Halfway down path: 50% of system current
At decoder: Only that decoder's current
Reading Analysis:
Higher than expected: Short, ground fault, or bad decoder downstream
Lower than expected: Open circuit, disconnected decoders, or problem upstream
Normal at one point, abnormal at next: Problem is between those two points
The Binary Search Method
Most efficient troubleshooting approach:
Start at controller: Measure current, confirm problem exists
Check both wires: Ensure you're not missing ground fault on single wire
Go halfway: Measure at midpoint of wire path
Still high? Problem is in downstream half
Now normal? Problem is in upstream half
Go halfway again: Measure at midpoint of problem section
Repeat: Continue dividing problem section in half
Pinpoint: When you find where reading changes, problem is at that location
At Branch Points:
Measure at beginning of each branch
Identifies which branch contains problem
Significantly narrows search area
Strategic Measurement Points
Priority locations:
At controller (baseline measurement)
At branch junctions (isolate which branch)
At valve boxes (most likely failure points)
Between valve boxes (only if indicated)
Remember: Problems are most likely at:
Splices in valve boxes
Wire damage during stripping
Decoder connections
Baseline Documentation
For healthy systems:
Record total current at controller for each wire path
Record current at major branch points
Document decoder count for each section
Note decoder model and expected draw per decoder
Save for future comparison
Example Scenarios
Scenario 1: Overcurrent Condition
System Details:
10 decoders total
Each decoder uses 2.5mA idle
Expected total: 10 × 2.5 = 25mA
Symptoms:
Controller shows overcurrent error
System won't operate normally
Step 1: Initial Measurement
Measure at controller
Reading: 80mA (should be 25mA)
Problem confirmed: Overcurrent condition
Step 2: Check Both Wires
Red wire: 80mA
Blue wire: 80mA
Conclusion: Short circuit (not ground fault on single wire)
Step 3: Go Halfway
Measure at midpoint (5 decoders upstream, 5 downstream)
Reading: 12.5mA (5 × 2.5 = expected)
Conclusion: Problem is UPSTREAM (in first half)
Step 4: Check First Half Branches
Branch A (2 decoders): 5mA (2 × 2.5 = normal)
Branch B (3 decoders): 75mA (should be 7.5mA)
Conclusion: Problem is in Branch B
Step 5: Narrow Down Branch B
Measure at first valve box in Branch B
Reading: 75mA (high)
This is the problem location
Step 6: Verify Decoder vs. Splice Problem
Clamp around wire coming off two-wire path to this specific decoder
Reading: 72.5mA (should be 2.5mA)
Conclusion: This decoder is the problem (not the splices to wire path)
Step 7: Resolution
Remove and replace failed decoder
Test removed decoder at controller (should confirm failure)
Measure again after replacement
Verify normal readings throughout system
Total measurements: 7 measurement points to identify exact problem
Without clamp meter: Would have required breaking multiple splices, testing sections, replacing splices, walking to controller repeatedly.
Scenario 2: Ground Fault (Single Wire)
Symptoms:
Overcurrent condition
Affects entire wire path
Measurements:
Red wire at controller: 80mA (high)
Blue wire at controller: 25mA (normal)
Conclusion: Ground fault on red wire only
Finding the Fault:
Use binary search on RED wire only
Find where high current drops to normal
Problem is at that location (likely bad splice or nicked wire)
Alternative: If fault is between valve boxes, use P-203 Ground Fault Locator:
Isolate section of cable (disconnect from decoders and controller)
Clip locator transmitter to BOTH wires (ensures detection regardless of which wire is faulted)
Walk wire path with receiver
Locate exact point of ground fault
Scenario 3: Open Circuit
System Details:
28 decoders expected
Each uses 1.4mA
Expected total: 28 × 1.4 = 39.2mA
Symptoms:
Controller reports zones 18-23 offline
Multiple consecutive zones not working
Step 1: Initial Measurement
Reading at controller: 31.5mA (should be 39.2mA)
Missing: 39.2 - 31.5 = 7.7mA
Calculation: 7.7 ÷ 1.4 = 5.5 decoders
Conclusion: Approximately 6 decoders offline (matches zones 18-23)
Step 2: Use Controller Information
Zones 18-23 are reported offline
Navigate to those zones in the field
Measure current before first offline zone
Step 3: Confirm Break Point
Measure at zone 17: 31.5mA (matches controller reading)
Measure at zone 18: 0mA
Conclusion: Break is between zone 17 and zone 18
Step 4: Inspect Connection
Open valve box between zones 17 and 18
Likely finds:
Disconnected splice
Severely corroded connection
Cut wire
Lightning-damaged section
Step 5: Resolution
Repair or replace connection
Verify current returns to normal (39.2mA)
Test all zones 18-23 for proper operation
Scenario 4: Solenoid-Side Problem
Symptoms:
Overcurrent ONLY when specific zone operates
No overcurrent when system is idle
Analysis:
Problem is on SOLENOID side of decoder, not two-wire path
Short in solenoid circuit only draws current when zone activates
Possible Causes:
Shorted solenoid (resistance too low)
Bad splices between decoder and solenoid
Damaged wire between decoder and valve
Troubleshooting:
Measure solenoid resistance (should be 20-60 ohms)
Inspect decoder-to-solenoid splices
Check decoder solenoid output connections
Test with known good solenoid if available
Scenario 5: Multiple Branches
System Configuration:
Wire path splits into 3 branches at junction
Branch A: 8 decoders
Branch B: 12 decoders
Branch C: 6 decoders
Each decoder: 1.5mA
Expected readings:
Total at controller: 26 × 1.5 = 39mA
Branch A only: 8 × 1.5 = 12mA
Branch B only: 12 × 1.5 = 18mA
Branch C only: 6 × 1.5 = 9mA
Symptoms:
Reading at controller: 68mA (overcurrent)
Step 1: Measure Each Branch
At junction before Branch A: 12mA (normal)
At junction before Branch B: 47mA (high - should be 18mA)
At junction before Branch C: 9mA (normal)
Conclusion: Problem is in Branch B
Step 2: Apply Binary Search to Branch B
Continue halving Branch B until problem found
Efficiency: Eliminated 14 decoders (A and C) from investigation with 3 measurements
Troubleshooting Quick Reference
Problem Type Identification
Symptom |
Problem Type |
Action |
|---|---|---|
Current higher than expected at controller |
Short, ground fault, or bad decoder |
Binary search for where current drops to normal |
Current lower than expected at controller |
Open circuit or disconnected decoders |
Find where current drops to zero |
High current on both wires |
Short circuit between wires |
Binary search on either wire |
High current on one wire only |
Ground fault on that wire |
Binary search on high-current wire only |
Overcurrent only when zone operates |
Solenoid-side problem |
Test solenoid and decoder output circuit |
Specific zones offline per controller |
Open circuit near those zones |
Check connections at/before first offline zone |
Intermittent problems |
Moisture-related or thermal expansion issue |
Check splices, may need to wait for wet weather |
Measurement Interpretation
Reading |
Indicates |
Next Step |
|---|---|---|
High current, problem downstream |
Problem is further along wire path |
Move measurement point forward |
High current, problem upstream |
Problem is behind current location |
Move measurement point backward |
Normal current |
No problem in this section |
Check other branches or sections |
Zero current |
Complete disconnect |
Find break point (where current drops from normal to zero) |
Higher on one wire than other |
Ground fault on higher wire |
Focus on that wire only |
Binary Search Process
Measure at controller → Confirm problem and type
Check both wires → Identify if ground fault is on one wire
Measure at halfway point → Determine which half contains problem
Measure at quarter point → Further narrow problem section
Continue halving → Until problem isolated to single valve box
Verify specific component → Decoder, splice, or wire
FAQ
Why must I use a milliamp clamp meter? Can't I use a regular amp meter?
Standard amp meters (clamp or multimeter) typically have minimum ranges of 0-10 amps or 0-100 amps. Decoders use 0.5-5 milliamps (0.0005 to 0.005 amps). A standard amp meter cannot accurately measure such small currents. You need a specialized milliamp clamp meter that reads down to 0.001 amps.
What is True RMS and why does it matter?
True RMS (Root Mean Square) accurately measures any waveform shape. Many two-wire systems use non-standard waveforms (square waves, slow frequencies, communication bursts). Standard meters assume a smooth sine wave and will give inaccurate readings on unusual waveforms. True RMS calculates the actual effective current regardless of wave shape.
What is the Low Pass Filter and when should I use it?
The Low Pass Filter (LPF) filters out high-frequency signals above 160Hz. Two-way communication creates rapid bursts of data that can make readings unstable. Engaging LPF ignores these bursts while measuring the steady idle current from decoders. Use LPF when measuring idle systems with two-way communication. Starting soon, it will be enabled by default on CMA-360B.
Why do I get zero reading when clamping both wires?
Current flows in opposite directions on the two wires (out on one, back on the other). The clamp meter averages the magnetic fields from both conductors. Equal and opposite currents cancel out, giving zero. You must clamp only one wire at a time to get an accurate reading.
Can I troubleshoot two-wire systems without a milliamp clamp meter?
Yes, but it's much more time-consuming and expensive:
Must physically break wire path connections
Test sections individually
Replace splices each time (cost)
Walk back to controller repeatedly
Risk creating new problems with new splices
A $200 milliamp clamp meter pays for itself quickly
What if my controller won't provide power due to overcurrent?
Option 1: Some controllers have "short finding mode" or "wire test mode" that provides limited current for testing despite overcurrent condition.
Option 2: Splice a solenoid into one wire at the controller to add resistance, allowing controller to operate safely.
Option 3: Create external power supply:
Transformer (25VA or 1A minimum rating)
Solenoid spliced into ONE wire only (limits current to safe 200-300mA)
Connect to wire path for testing
How do I know how much current each decoder should draw?
Method 1: Check manufacturer specifications:
0.5-1.5mA (Excluding flow biCoders)
Method 2: Measure a known healthy system with same equipment
Method 3: Calculate from total:
Measure total current at controller
Divide by number of decoders
Example: 39.2mA ÷ 28 decoders = 1.4mA per decoder
Why are splices so critical in two-wire systems?
Systems with two-way communication have constant voltage on the wire path. Electricity combined with moisture:
Attracts water into exposed connections
Dramatically accelerates corrosion
Creates decoder failures from water intrusion
Causes intermittent communication issues
Eventually leads to complete failure
Gel-filled wire nuts alone are insufficient. Use proper DBry6 waterproof splices.
Should I break loops before troubleshooting?
Yes, highly recommended. Loops make "upstream vs. downstream" ambiguous. Breaking loops at the furthest points converts the system to a star/branched pattern with clear directional flow. This makes binary search troubleshooting much more logical and efficient.
What does it mean if I only have overcurrent when a zone operates?
The problem is on the solenoid side of the decoder, not the two-wire path. When the zone is idle, the solenoid circuit isn't active. When the zone operates, a short in the solenoid, solenoid wiring, or decoder-to-solenoid splices causes overcurrent.
Check:
Solenoid resistance (should be 20-60 ohms)
Splices between decoder and solenoid
Wire condition between decoder and valve
Decoder solenoid output connections
What's the difference between a short and a ground fault?
Short Circuit:
Direct or indirect contact between the two wires
Both wires show high current
Current path: Wire 1 → Short → Wire 2 → Back to controller
Ground Fault:
One or both wires making contact with ground/earth
May show high current on only one wire
Current path: Wire → Ground → Earth → Controller ground
Can be intermittent based on soil moisture
Why would readings change between wet and dry weather?
Moisture affects conductivity:
Wet conditions: Ground can conduct electricity, turning opens into ground faults
Dry conditions: Ground doesn't conduct well, ground faults may not show up
Damaged wire/poor splice: Acts as open when dry, short/ground fault when wet
If problems only appear after rain, inspect splices and wire insulation in affected areas.
How do I locate a ground fault between valve boxes?
Use the P-203 Ground Fault Locator:
Isolate the cable section (disconnect from decoders and controller)
Clip transmitter leads to BOTH wires (ensures detection regardless of which wire is faulted)
Walk the wire path with receiver
Locate the point of strongest signal (fault location)
Excavate and repair
Important: Must know approximate wire path route for this method to work efficiently.
Can I use the clamp meter on systems without two-way communication?
Yes, but with limitations. Systems that only have voltage during zone operation (no idle current) cannot be measured when idle. You must:
Put controller in wire test mode if available
Create external power supply to provide steady test current
Or measure during zone operation (readings will be higher)
What if I'm getting inconsistent readings?
Possible causes:
Communication bursts: Engage Low Pass Filter (hold HOLD button 2 seconds)
Not waiting long enough: Wait 2-3 seconds for reading to stabilize
Clamping both wires: Ensure clamping only one wire
Intermittent connection: Problem comes and goes (moisture-related)
Zone operating during measurement: Ensure system is idle (unless intentionally testing during operation)
What resistance should I see on a healthy two-wire path?
Between the two wires: Very high resistance
Should read >600kΩ (or "OL" for overload on most meters)
Low resistance indicates short
Between each wire and ground: Very high resistance
Should read >600kΩ (or "OL")
Low resistance indicates ground fault
With wires shorted at far end:
14-gauge: 2.5 ohms × 2 × (distance in 1000's of feet)
12-gauge: 1.6 ohms × 2 × (distance in 1000's of feet)
Much higher indicates bad splice/corrosion
Why does binary search work better than checking each valve box?
Linear search (check each box):
10 valve boxes = average 5 measurements to find problem
50 valve boxes = average 25 measurements
Binary search (halve each time):
10 valve boxes = maximum 4 measurements
50 valve boxes = maximum 6 measurements
100 valve boxes = maximum 7 measurements
Binary search is logarithmic (log₂), dramatically reducing measurements needed. Each measurement cuts the problem area in half.
How accurate do my measurements need to be?
You're looking for significant differences, not precise numbers:
Expected: 25mA, Reading: 80mA → Clear problem
Expected: 12.5mA, Reading: 12.3mA → Within normal range
Expected: 5mA, Reading: 72mA → Clear problem
Small variations (±10-20%) are normal due to:
Temperature affecting decoder operation
Communication activity
Voltage fluctuations
Manufacturing tolerances
Large variations indicate problems requiring investigation.
What if multiple wire paths have problems?
Troubleshoot one path at a time:
Disconnect all wire paths from controller
Reconnect one path, verify it's healthy (or identify as problem path)
Disconnect that path, reconnect next path
Repeat until all healthy paths identified
Fix each problem path individually before reconnecting
Don't troubleshoot multiple paths simultaneously - too confusing and time-consuming.
Can lightning damage affect my readings?
Yes. Lightning can:
Destroy multiple decoders (especially without proper grounding)
Create shorts in decoders
Damage wire insulation
Affect all decoders on ungrounded path section
If lightning damage suspected:
Check grounding system first
May need to replace multiple decoders
Inspect all splices in affected section
Verify surge arrestors are functioning
What should I do if I find a bad decoder?
Verify it's the decoder: Clamp around wire to that specific decoder (should be low current, if high = decoder problem)
Disconnect decoder from two-wire path
Remeasure: Confirm overcurrent is gone
Test removed decoder: Connect to controller directly to confirm failure
Inspect splices: Bad decoder often indicates poor splices that allowed water in
Replace splices: Use new DBry6 waterproof splices
Install new decoder: Ensure proper splice installation
Test system: Verify normal operation and current readings
How do I know if a splice is bad without breaking it open?
Indirect indicators:
Overcurrent on wire path
Decoder failure
Corrosion visible on splice exterior
Splice feels loose or spongy
Moisture around splice
Intermittent zone operation
Communication errors at that zone
Cannot definitively test without opening, but if decoder failed or overcurrent exists, inspect all splices at that location.
What's the difference between wire test mode and short finding mode?
Terms vary by manufacturer, but generally:
Short Finding Mode / Wire Test Mode:
Provides limited, safe current despite overcurrent condition
Allows troubleshooting without risking equipment
May display current measurements
Some controllers automatically enter this mode
Others require manual activation
Not all controllers have this feature. Older or simpler controllers may just shut down on overcurrent.
Why do I need to isolate both ends when using a ground fault locator?
Safety and accuracy:
Prevents damage: Transmitter voltage could damage decoders
Prevents false readings: Current could flow through decoder internals instead of fault
Safety: Ensures current only flows through the fault you're trying to locate
Accuracy: Eliminates other current paths that could confuse the locator
Always disconnect from controller and any decoders on the section being tested.
Can I use this troubleshooting method on other brands of two-wire systems?
Yes, the principles apply to all two-wire irrigation systems:
Rain Bird (ICI, TBOS, Maxi-Com)
Hunter (ICD, ACC, ICC)
Toro (Sentinel, Lynx)
Weathermatic
And others
However:
Decoder current draw varies by manufacturer
Waveforms differ between systems
Splice requirements may differ
Controller features vary
Always consult manufacturer specifications
The CMA-360B milliamp clamp meter works with all systems due to True RMS and Low Pass Filter capabilities.
What if I'm still getting errors after fixing the overcurrent?
Possible issues:
Additional problems exist: Fix first problem may reveal second problem
Introduced new problem: New splice may be faulty
Communication issue: Path integrity problems (not overcurrent)
Controller problem: May need reset or has separate issue
Wrong decoder replaced: Verify you fixed correct location
Action:
Take new baseline measurement at controller
Repeat troubleshooting process
Verify all splices are properly installed
Check controller diagnostics for new information
How often should I check my two-wire system?
Preventive maintenance schedule:
Monthly (during active season):
Review controller error logs
Check for new error messages
Test random zones for proper operation
Quarterly:
Document baseline current readings
Inspect accessible splices for corrosion
Test grounding system
Annually:
Complete system test (all zones)
Measure current at all major branch points
Inspect valve boxes for moisture/damage
Check all grounding connections
Update system documentation
After storms:
Check system immediately after lightning
Verify grounding system intact
Test for new errors
Proactive monitoring prevents small problems from becoming system failures.
Locating Tools Reference
CMA-360B Milliamp Clamp Meter
Used for:
Measuring current on two-wire path
Finding overcurrent problems
Locating shorts and ground faults
Voltage testing
Resistance testing
Verifying decoder current draw
When to use: Primary tool for all two-wire troubleshooting
P-203 Ground Fault Locator
Used for:
Finding exact location of ground fault between valve boxes
Locating wire damage in turf areas
Pinpointing shorts in buried cable
When to use: After milliamp clamp narrows problem to between two valve boxes
Requirements:
Know approximate wire path route
Must isolate cable section (disconnect both ends)
Clip transmitter to BOTH wires
Wire/Cable Locator (Standard)
Used for:
Tracing wire path route
Finding valve boxes
Mapping system layout
Verifying wire path direction
When to use:
Before troubleshooting (map system)
Finding unmarked valve boxes
Verifying wire path routing
Setup for two-wire:
Black lead to ground stake
Red lead clipped to BOTH wires (for best signal)
Do NOT clip leads to individual wires separately (can damage decoders)
Multimeter / VOM
Used for:
Voltage testing (power supply, transformer output)
Resistance testing (solenoids, wire continuity, shorts)
Solenoid testing
When to use:
Checking controller power
Testing solenoids (20-60 ohms expected)
Wire continuity tests
Supplement to clamp meter
Note: Cannot replace milliamp clamp meter for current measurements (lacks sensitivity).
Troubleshooting Flowchart
Controller turning on?
├─ NO → Check power supply
│ ├─ Power switch
│ ├─ Fuses
│ ├─ Transformer voltage
│ └─ Connections
│ ↓
│ Fixed? → YES → END
│ ↓ NO
│ Disconnect all wire paths
│ ↓
│ Controller works now?
│ ├─ YES → Overcurrent on wire path → Go to OVERCURRENT
│ └─ NO → Controller problem → Contact manufacturer
│
└─ YES → Review controller errors
↓
What does controller show?
├─ Overcurrent error → Go to OVERCURRENT
├─ Specific zones offline → Go to OPEN CIRCUIT
├─ Zone error during operation → Go to SOLENOID SIDE
└─ Communication errors → Go to COMMUNICATION
OVERCURRENT:
1. Break any loops in system
2. Disconnect wire paths one by one
3. Identify problem wire path
4. Measure current at controller (both wires)
├─ High on both wires → SHORT CIRCUIT
└─ High on one wire → GROUND FAULT
5. Use binary search to locate problem
6. Inspect valve box at problem location
7. Test decoder with clamp meter
8. Replace failed component
9. Verify fix with new measurements
OPEN CIRCUIT:
1. Note which zones are offline
2. Calculate expected vs. actual current
3. Navigate to affected zone area
4. Measure current before first offline zone
5. Measure current at first offline zone
6. Find break point (current drops to zero)
7. Inspect connection at break point
8. Repair/replace connection
9. Verify all zones operational
SOLENOID SIDE:
1. Confirm error only during zone operation
2. Measure solenoid resistance (20-60 ohms)
3. Inspect decoder-to-solenoid splices
4. Check decoder solenoid outputs
5. Replace failed component
6. Test zone operation
COMMUNICATION:
1. Check for overcurrent first (can cause communication errors)
2. Inspect splices at problem decoder
3. Verify decoder not damaged
4. Check wire path continuity
5. Test with known good decoder
6. Replace splices with new DBRY6
END
Best Practices Summary
Installation
Use only specified two-wire cable (double-insulated, solid copper core)
Different colors for different wire paths
Use DBry6 waterproof splices exclusively
Don't nick wire insulation during stripping
Don't overtighten wire twists in splices
Ensure waterproof gel properly positioned in splice
Install grounding at recommended intervals
Install surge arrestors with each ground
Document system layout and decoder locations
Record baseline current measurements
Troubleshooting
Start at controller, gather all available information
Break loops before measuring
Always check both wires
Use binary search for efficiency
Clamp only one wire at a time
Wait 2-3 seconds for stable readings
Engage Low Pass Filter on communicating systems
Measure at branch junctions to isolate problems
Verify fix with new measurements
Document findings for future reference
Maintenance
Proactive monitoring prevents failures
Address intermittent errors immediately
Replace splices when opening valve boxes
Keep system documentation current
Train staff on proper splicing techniques
Inspect after lightning storms
Regular current measurements detect developing problems
Keep spare decoders, splices, and solenoids on hand
Invest in proper tools (milliamp clamp meter, locators)
Learn manufacturer-specific system characteristics
Safety
Never connect transformer directly to short without current limiter
Always use solenoid in test power supply
Isolate sections when using ground fault locator
Power down controller before disconnecting display ribbon
Verify grounding system integrity
Don't exceed transformer ratings
Use proper PPE when working in valve boxes
Follow electrical safety practices
Be aware of other utilities when excavating
Contact manufacturer support when uncertain
Additional Resources
Recommended Training
Noe Cruz YouTube channel: Advanced splicing techniques
Manufacturer-specific training programs
Irrigation Association certification courses
Local distributor technical workshops
Tempo Communications Resources
Product website: Complete CMA-360B specifications
YouTube channel: Tool demonstrations and tutorials
Webinar archives: Past troubleshooting sessions
Technical support: Product-specific questions
Documentation Tools
System mapping software
Current measurement logging templates
Maintenance schedule templates
Troubleshooting checklists
Glossary
Binary Search: Troubleshooting method that divides problem area in half with each measurement
Clamp Meter: Tool that measures current without breaking circuit connections
DBry6: Direct-bury waterproof splice connector for two-wire systems
Decoder: Device that receives signals from controller and operates valves
Ground Fault: Electrical connection between wire and earth/ground
Idle Current: Current consumed by decoder when not operating a zone
Low Pass Filter (LPF): Filter that removes high-frequency signals from measurements
Milliamp (mA): One-thousandth of an amp (0.001 amp)
Ohm's Law: V = I × R (Voltage = Current × Resistance)
Open Circuit: Break in electrical path preventing current flow
Overcurrent: Current draw higher than normal, indicating short or ground fault
Short Circuit: Unintended low-resistance connection between two wires
Solenoid: Electromagnetic coil that opens/closes irrigation valve
True RMS: Measurement method accurate for any waveform shape
Two-Way Communication: Bidirectional data exchange between controller and decoders
Two-Wire Path: Complete circuit of two wires connecting controller to decoders
Upstream/Downstream: Direction relative to current flow from controller
Wire Test Mode: Controller mode providing safe current for troubleshooting
Document Information
Title: Two-Wire System Troubleshooting with Milliamp Clamp Meter - Customer Support Guide
Version: 1.0
Last Updated: Based on Tempo Communications webinar content
Presenter: Alejandro Asencio, Associate Product Manager - Irrigation
Primary Tool: Tempo CMA-360B Milliamp Clamp Meter
Intended Audience: Customer support teams, field technicians, irrigation professionals
Prerequisites: Basic understanding of electricity, irrigation systems, and multimeter use
Related Documents:
CMA-360B Product Manual
P-203 Ground Fault Locator Guide
Manufacturer-specific two-wire system documentation
If you have reviewed all of the above information and have not resolved the issue, consider contacting Hydropoint Support. Hydropoint Support can be reached at support@baselinesystems.com, support@hydropoint.com or 866-294-5847.