EQ Wave Troubleshooting
This guide provides systematic troubleshooting procedures for common issues. For emergency support, contact (415) 562-5251.
LED Status Indicators
The EQ Wave has two status LEDs that provide quick diagnostic information:
| LED | Pattern | Meaning | Action |
|---|---|---|---|
| LINK | Solid Green | Optical link established with endpoint | Normal operation |
| LINK | Off | No optical link | Check fiber cable and media converter |
| ACT | Solid Green | Device active and transmitting data | Normal operation |
| ACT | Off | Device inactive | Check power and connections |
| Both | Red flash at startup | Boot sequence | Normal — both turn solid green shortly |
| Both | Solid green | Powered, awaiting connection | Connect fiber to media converter |
| Both | Off | No power | Check power supply and connections |
For detailed diagnostics beyond basic LED status, check the EQ Sight web interface on the gateway for device status and data stream health.
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:
-
Check Power Source:
- Verify power supply voltage (4.5–36V DC or 85–528V AC)
- Measure voltage at power input terminals
- Verify power supply can deliver at least 2.4W DC or 3.3W AC
- Try alternative power input method
-
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
-
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:
-
Check Power Quality:
- Monitor input voltage stability
- Look for voltage sags or surges
- Check for loose connections
- Verify power supply capacity under load
-
Environmental Factors:
- Check operating temperature (-40°C to +70°C)
- Ensure adequate ventilation
- Look for vibration or shock
- Check for moisture ingress
-
Load Analysis:
- Verify power consumption 3.3W 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:
-
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
-
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
-
Network Configuration:
- Verify IP address settings
- Check subnet and gateway configuration
- Default IP is 192.168.10.10 (fixed)
-
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:
-
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)
-
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:
-
Port Accessibility:
- Verify TCP ports 1534, 1535 are open
- Test with telnet or netcat
- Monitor network statistics
-
Bandwidth Issues:
- Check network bandwidth availability
- Monitor system diagnostics for buffer overflows
- Reduce data streaming rate if necessary
- Optimize network infrastructure
-
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:
-
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
-
Configuration Check:
- Verify system voltage configuration
- Check PGA gain settings
- Confirm voltage divider ratios
- Review calibration factors
-
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:
-
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
-
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
-
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:
-
Wiring Check:
- Verify all voltage and current connections
- Check for consistent CT orientations
- Ensure common voltage reference (V0) connection
- Verify timing synchronization between channels
-
System Configuration:
- Check system type setting (Delta, Wye, etc.)
- Verify phase sequence (A-B-C rotation)
- Review nominal frequency setting
- Check sampling synchronization
-
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:
-
Network Analysis:
- Check network bandwidth and congestion
- Monitor packet loss statistics
- Verify network switch performance
- Test network infrastructure
-
System Health:
- Check system status via EQ Sight
- Monitor for network congestion
- Review recent configuration changes
- Contact support if persistent
-
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:
-
Protocol Verification:
- Verify data parsing matches protocol specification
- Check for endianness issues in multi-byte values
- Validate data structure alignment
- Review protocol documentation
-
Network Issues:
- Monitor for network errors
- Check cable integrity
- Look for EMI/RFI interference
- Test with different network equipment
-
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:
-
Temperature Monitoring:
- Check internal temperature readings
- Verify operating range (-40°C to +70°C)
- Monitor ambient temperature
- Check for heat sources nearby
-
Ventilation:
- Ensure adequate clearance around device
- Check for blocked ventilation
- Verify mounting orientation
- Consider additional cooling if needed
-
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:
-
Mounting Inspection:
- Check mounting hardware tightness
- Verify DIN rail or panel mount security
- Look for mechanical stress
- Check for proper mounting orientation
-
Vibration Sources:
- Identify vibration sources
- Consider vibration isolation
- Check equipment mounting
- Monitor acceleration levels
-
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:
- Disconnect power
- Wait 10 seconds
- Reconnect power
- Verify both LEDs flash red briefly, then turn solid green
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
Information to Collect
Before contacting support, gather:
- Device serial number and firmware version
- LED status patterns (refer to table above)
- 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