EQ Wave Troubleshooting

LED Status Indicators

The EQ Wave has two sets of indicators, and they report different things.

Green (LINK / ACT) are driven by the network interface and report the optical link:

Red report startup progress. On a healthy unit they light at power-on and go out within a few seconds, and they stay out in normal operation. What matters is not that they light, but whether they go out. Red LEDs still lit a minute after power-on mean startup did not finish, and how many are lit says how far it got:

If the red LEDs stay lit

Each case below has a small number of checks that are actually worth doing. If they do not resolve it, the fault is inside the device and further steps on site will not help — contact support@eq.systems with the details listed under Getting Additional Help.

Both red LEDs stay lit — hardware initialization did not complete.

1. De-energize at the upstream breaker or supply, wait ten seconds, and re-energize. A single failure to start can be cleared this way; a repeatable one cannot.
2. Confirm the supply is within the rated input range and is stable. A supply that sags during startup can stop the device part-way through.

If it recurs after a clean power cycle on a known-good supply, the measurement front end is not responding and the unit needs to come back. Report it.

One red LED stays lit — the device is running but never finished joining the network.

1. Check the green LINK LED. If it is off, the problem is the optical path: check the fiber at both ends and the media converter’s own LEDs.
2. Confirm the gateway or switch at the other end is powered and running.
3. Power cycle the unit as above.

If the link is good and the gateway is up and it still stops here, report it.

No LEDs at all, red or green — the device is not running.

1. Confirm power is present and within the rated input range, measured at the power input terminals.
2. Check the upstream breaker, fuse, or supply.

If power is confirmed good and the unit stays completely dark, report it.

Quick Diagnostic Checklist

Before starting detailed troubleshooting:

• Check LED status using table above
• Verify media converter LEDs (both amber and green illuminated)
• Test network connectivity: ping sensor at 192.168.10.10 or gateway at 192.168.10.2
• Review data streams via EQ Sight or direct TCP connection

Power and System Issues

No Power - Both LEDs Off

Symptoms:

• LINK and ACT LEDs completely dark (no red startup flash)
• Device unresponsive
• No network connectivity

Troubleshooting Steps:

1. Check Power Source:

   • Verify power supply voltage (4.5–48V DC on v1.3, 4.5–36V DC on v1.2, or 85–528V AC)
   • Measure voltage at power input terminals
   • Verify power supply can deliver at least 2.4W DC or 2.7W AC
   • Try alternative power input method

2. Check Connections:

   • Verify power terminal connections are tight
   • Check for corrosion or damage
   • Ensure proper wire sizing (12–20 AWG)
   • Verify polarity for DC inputs

3. Test with Alternative Power:

   • Try USB power for testing (limited functionality)
   • Use known good power supply
   • Check for blown fuses in external power supply

Expected Resolution: LINK and ACT LEDs should both illuminate solid green

Intermittent Power Issues

Symptoms:

• LEDs flicker or go off intermittently
• System restarts unexpectedly
• Data interruptions

Troubleshooting Steps:

1. Check Power Quality:

   • Monitor input voltage stability
   • Look for voltage sags or surges
   • Check for loose connections
   • Verify power supply capacity under load

2. Environmental Factors:

   • Check operating temperature (-40°C to +70°C)
   • Ensure adequate ventilation
   • Look for vibration or shock
   • Check for moisture ingress

3. Load Analysis:

   • Verify power consumption 2.7W AC / 2.4W DC typical
   • Check for excessive network load
   • Monitor internal temperature
   • Review system diagnostics

Network Connectivity Issues

No Network Connection

Symptoms:

• Cannot ping device IP address
• LINK LED off
• No data streaming

Troubleshooting Steps:

1. Physical Connection:

   • Verify fiber optic cable connections
   • Check media converter power and status LEDs
   • Test fiber cable with optical power meter
   • Try known good fiber cable

2. Fiber Optic Issues:

   • Clean fiber connectors with lint-free wipes
   • Inspect connector end faces for damage
   • Ensure proper connector seating
   • Check for cable bending radius violations

3. Network Configuration:

   • Verify IP address settings
   • Check subnet and gateway configuration
   • Default IP is 192.168.10.10 (fixed)

4. Media Converter Issues:

   • Verify media converter power
   • Check Ethernet connection to switch
   • Test with different media converter
   • Verify 100Base-FX compatibility

Expected Resolution: LINK LED solid green, ACT LED solid green, device responds to ping

Cannot Access Data Ports

Symptoms:

• Network connectivity works (ping successful)
• TCP connections to ports 1534/1535 fail or timeout

Troubleshooting Steps:

1. Network Verification:

   • Verify device responds to ping at 192.168.10.10
   • Test TCP connection with telnet or netcat (ports 1534, 1535)
   • Verify computer IP address is in same subnet (192.168.10.x)

2. Device Issues:

   • Power cycle the device
   • Verify both LINK and ACT LEDs are solid green
   • Test from a different computer

Data Connection Timeouts

Symptoms:

• Ping works but data streaming fails
• Intermittent data loss
• Application cannot connect to data ports

Troubleshooting Steps:

1. Port Accessibility:

   • Verify TCP ports 1534, 1535 are open
   • Test with telnet or netcat
   • Monitor network statistics

2. Bandwidth Issues:

   • Check network bandwidth availability
   • Monitor system diagnostics for buffer overflows
   • Reduce data streaming rate if necessary
   • Optimize network infrastructure

3. Application Issues:

   • Increase application TCP buffer sizes
   • Implement proper error handling
   • Check application processing speed
   • Monitor client-side resources

Measurement Issues

Inaccurate Voltage Readings

Symptoms:

• Voltage readings significantly different from reference
• Inconsistent measurements
• Wrong scaling

Troubleshooting Steps:

1. Connection Verification:

   • Verify voltage reference connections (V0 terminal)
   • Check voltage divider scaling configuration
   • Ensure proper grounding of measurement circuit
   • Verify input voltage is within specified range

2. Configuration Check:

   • Verify system voltage configuration
   • Check PGA gain settings
   • Confirm voltage divider ratios
   • Review calibration factors

3. Signal Quality:

   • Check for EMI/RFI interference
   • Verify cable shielding integrity
   • Look for ground loops
   • Monitor signal-to-noise ratio

Acceptance Criteria: ±0.2% accuracy for RMS voltage (sensor only; field measurements may vary with wiring and connections)

Inaccurate Current Readings

Symptoms:

• Current readings don’t match applied current
• Wrong power factor calculations
• Phase angle errors

Troubleshooting Steps:

1. CT/Rogowski Setup:

   • Check CT polarity and direction
   • Verify CT ratio configuration matches actual CT
   • Ensure CT secondary is properly terminated
   • Check for proper CT burden resistance

2. Wiring Verification:

   • Verify CT primary direction (arrow toward load)
   • Check secondary connections (I+ and I-)
   • Ensure CT secondary never left open
   • Verify consistent CT orientations

3. Configuration:

   • Check CT ratio settings in configuration
   • Verify Rogowski coil sensitivity (if applicable)
   • Review current sensor calibration
   • Check input range settings

Acceptance Criteria: ±0.5% magnitude, ±0.2° phase accuracy (includes typical external sensor contribution)

Phase Angle Errors

Symptoms:

• Incorrect power factor readings
• Wrong phase sequence
• Inconsistent phase relationships

Troubleshooting Steps:

1. Wiring Check:

   • Verify all voltage and current connections
   • Check for consistent CT orientations
   • Ensure common voltage reference (V0) connection
   • Verify timing synchronization between channels

2. System Configuration:

   • Check system type setting (Delta, Wye, etc.)
   • Verify phase sequence (A-B-C rotation)
   • Review nominal frequency setting
   • Check sampling synchronization

3. Signal Quality:

   • Monitor for noise and interference
   • Check cable lengths and routing
   • Verify grounding practices
   • Look for timing synchronization issues

Expected Results:

• Phase sequence: A→B→C positive rotation
• Phase angles: ∠VA = 0°, ∠VB = -120°, ∠VC = +120°

Data Quality Issues

Missing Data Packets

Symptoms:

• Intermittent data gaps
• Application reports missing data
• Inconsistent update rates

Troubleshooting Steps:

1. Network Analysis:

   • Check network bandwidth and congestion
   • Monitor packet loss statistics
   • Verify network switch performance
   • Test network infrastructure

2. System Health:

   • Check system status via EQ Sight
   • Monitor for network congestion
   • Review recent configuration changes
   • Contact support if persistent

3. Application Optimization:

   • Increase TCP buffer sizes if possible
   • Implement application-level buffering
   • Optimize data processing speed
   • Use multiple threads for data handling

Data Corruption

Symptoms:

• Invalid data values
• Checksum errors
• Parsing failures

Troubleshooting Steps:

1. Protocol Verification:

   • Verify data parsing matches protocol specification
   • Check for endianness issues in multi-byte values
   • Validate data structure alignment
   • Review protocol documentation

2. Network Issues:

   • Monitor for network errors
   • Check cable integrity
   • Look for EMI/RFI interference
   • Test with different network equipment

3. If Issues Persist:

   • Document specific error patterns
   • Note when corruption occurs (specific data types, times)
   • Contact support with error examples
   • Provide network configuration details

Environmental Issues

Temperature-Related Problems

Symptoms:

• Performance degradation in extreme temperatures
• Thermal shutdown events
• Measurement drift

Troubleshooting Steps:

1. Temperature Monitoring:

   • Check internal temperature readings
   • Verify operating range (-40°C to +70°C)
   • Monitor ambient temperature
   • Check for heat sources nearby

2. Ventilation:

   • Ensure adequate clearance around device
   • Check for blocked ventilation
   • Verify mounting orientation
   • Consider additional cooling if needed

3. Environmental Protection:

   • Check for direct sunlight exposure
   • Verify enclosure IP rating
   • Look for heat-generating equipment nearby
   • Consider thermal insulation if needed

Vibration and Shock Issues

Symptoms:

• Intermittent connection problems
• Mechanical damage
• Mounting hardware loosening

Troubleshooting Steps:

1. Mounting Inspection:

   • Check mounting hardware tightness
   • Verify DIN rail or panel mount security
   • Look for mechanical stress
   • Check for proper mounting orientation

2. Vibration Sources:

   • Identify vibration sources
   • Consider vibration isolation
   • Check equipment mounting
   • Monitor acceleration levels

3. Connection Security:

   • Verify all electrical connections
   • Check for wire fatigue
   • Ensure strain relief adequate
   • Consider flexible connections

System Recovery Procedures

Power Cycle

If the device behaves erratically or becomes unresponsive:

1. Disconnect power
2. Wait 10 seconds
3. Reconnect power
4. Verify both red LEDs light and then go out within a few seconds, and that the green LINK LED comes on

Firmware Issues

v1 devices require return to factory for firmware updates. Contact support to initiate the RMA process if:

• Device behaves unexpectedly after a firmware change
• System is unresponsive and power cycling does not resolve the issue

Getting Additional Help

Contact support@eq.systems.

Information to Collect

Before contacting support, gather:

• Device serial number and firmware version
• LED status: how many red LEDs are lit, whether they ever go out, and what the green LINK and ACT LEDs show
• Whether a power cycle changed anything, and whether the fault repeats every time
• Approximately how long after power-on the device stopped
• Complete error description: when it started, how often it occurs, what changed
• Network configuration: IP address, gateway, subnet
• Installation details: power source, sensor types, environmental conditions
• Recent changes: configuration updates, firmware updates, wiring changes