Accordion Maestro
Live demo — data resets daily at 03:00 UTC. Nothing you enter is saved. Server UI →

Troubleshooting Guide

Overview

This guide helps resolve common issues with Accordion Pilot. For each problem, we provide symptoms, causes, and step-by-step solutions.

Connection Issues

Cannot Connect to Device

Symptoms:

  • "Connection refused" error
  • "Timeout" error
  • Unable to attach
  • Connection status shows disconnected

Common Causes & Solutions:

1. Wrong IP Address/Hostname

Solution:
1. Verify IP address of Accordion device
2. Ping device: ping 192.168.1.100
3. Check network configuration
4. Try IP address instead of hostname
5. Verify device powered on

2. Accordion Service Not Running

Solution:
1. SSH to device: ssh accordion@192.168.1.100
2. Check service status: systemctl status accordion
3. Start service: sudo systemctl start accordion
4. Or use firmware command:
   AccordionShell firmware --host 192.168.1.100 --run

3. Firewall Blocking Connection

Solution:
1. Check Windows Firewall settings
2. Allow Accordion Pilot through firewall
3. Check corporate firewall rules
4. Verify port not blocked (typically 50000)
5. Test from different computer/network

4. Network Configuration

Solution:
1. Verify same subnet as device
2. Check network adapter settings
3. Disable VPN if interfering
4. Check router/switch configuration
5. Try direct connection (if possible)

Connection Drops Intermittently

Symptoms:

  • Connects but then disconnects
  • "Connection lost" messages
  • Polling stops working

Solutions:

1. Network Instability

1. Check network cable connections
2. Try different network port/switch
3. Monitor network stability with ping
4. Check for network congestion
5. Use wired connection instead of WiFi

2. Device Overload

1. Reduce polling frequency
2. Disable unnecessary telemetry
3. Remove unused modules
4. Restart Accordion service
5. Update to latest firmware

3. Power Issues

1. Verify stable power to device
2. Check power supply capacity
3. Look for brownouts in logs
4. Use UPS for critical applications

Channel Issues

Channels Not Appearing

Symptoms:

  • Channel list empty
  • Some channels missing
  • Module channels not showing

Solutions:

1. Not Connected

1. Verify connected to device (status bar)
2. Click Attach button
3. Refresh channel list (F5)

2. Module Not Loaded

1. Check which modules needed
2. Load module:
   AccordionShell module --module "ModuleName" --file "config.xml"
3. Refresh channel list

3. Filtering Active

1. Check Find panel (Ctrl+F)
2. Clear filter (Esc or clear button)
3. Check column filters (click filter icon)
4. Reset all filters

4. Alias Configuration

1. Try loading different alias file
2. Deactivate alias temporarily
3. Check alias file syntax (XML valid)
4. Use NetNames if aliases broken

Cannot Read Channel Value

Symptoms:

  • "Read failed" error
  • Value shows as error
  • Timeout reading channel

Solutions:

1. Channel Not Readable

1. Check Capability column
2. Verify shows "Read" or "ReadWrite"
3. Some channels are write-only
4. Check channel documentation

2. Hardware Not Responding

1. Check bus transaction log for errors
2. Verify I2C/SPI device connected
3. Check device address correct
4. Verify device powered on
5. Test with known-good hardware

3. Timing Issues

1. Increase communication timeout (if configurable)
2. Reduce polling frequency
3. Check network latency
4. Verify device not overloaded

Cannot Write Channel Value

Symptoms:

  • "Write failed" error
  • Value doesn't change
  • Channel shows previous value

Solutions:

1. Channel Not Writable

1. Check Capability column
2. Verify shows "Write" or "ReadWrite"
3. Read-only channels cannot be written

2. Value Out of Range

1. Check channel min/max limits
2. Verify value format correct:
   - Boolean: true/false, 1/0
   - Numeric: within range
   - Enum: valid enum value
   - String: correct format

3. Protection/Interlock

1. Check for interlocks (some channels require others enabled first)
2. Verify no protection active
3. Check enable/permission channels
4. Review device documentation

4. Hardware Fault

1. Check bus transactions for NACK/errors
2. Verify device operational
3. Check power to device
4. Test with alternative channel

Polling and Performance

Polling Not Updating

Symptoms:

  • Values don't update
  • Polling checkbox checked but no updates
  • Stale values

Solutions:

1. Polling Not Enabled

1. Check polling checkbox (Ribbon → Appearance)
2. Verify polling interval set (not zero)
3. Try toggling polling off and on

2. Connection Lost

1. Check connection status (status bar)
2. Verify network connectivity
3. Reconnect if needed

3. Performance Issue

1. Reduce number of polled channels
2. Increase polling interval
3. Disable other views (Chart, Transactions)
4. Close unnecessary applications
5. Check CPU usage

4. Channel Selection

1. Some views only poll visible/selected channels
2. Ensure channels visible
3. Try selecting channels explicitly

Application Slow/Laggy

Symptoms:

  • UI unresponsive
  • Slow to switch pages
  • Delayed response to clicks

Solutions:

1. Too Much Data

1. Reduce polling frequency (500ms or higher)
2. Filter channel list (show fewer channels)
3. Reduce chart lookback points
4. Clear transaction log
5. Clear application log

2. Resource Limitations

1. Close unused applications
2. Check available RAM
3. Check CPU usage
4. Restart Accordion Pilot
5. Restart computer if needed

3. Network Latency

1. Check network response time (ping)
2. Reduce polling frequency
3. Use wired connection
4. Minimize network traffic

4. View Complexity

1. Close unused views/windows
2. Simplify chart (fewer series)
3. Disable transaction logging if not needed
4. Reduce grouping in grid

Bus Communication Issues

I2C NACK Errors

Symptoms:

  • "NACK" in transaction log
  • I2C reads/writes fail
  • Device not responding

Solutions:

1. Wrong Address

1. Verify I2C device address (7-bit vs 8-bit)
2. Check device documentation
3. Try I2C scan:
   AccordionShell i2c --channel "I2C_BUS" --scan
4. Look for device in scan results

2. Device Not Powered

1. Verify device has power
2. Check power supply voltage
3. Measure voltage at device
4. Verify enable signals asserted

3. Pull-Up Resistors

1. Verify I2C bus has pull-up resistors
2. Check resistance (typically 4.7kΩ - 10kΩ)
3. Measure signal levels with scope
4. Add pull-ups if missing

4. Bus Contention

1. Verify no address conflicts
2. Check only one master on bus
3. Disable other I2C devices temporarily
4. Check for short circuits

5. Timing Issues

1. Reduce I2C clock speed
2. Check for clock stretching issues
3. Verify capacitance on bus < spec
4. Reduce cable length

SPI Communication Failures

Symptoms:

  • SPI transactions fail
  • Incorrect data received
  • No response from device

Solutions:

1. Wrong SPI Mode

1. Verify SPI mode (0-3) matches device
2. Check clock polarity (CPOL)
3. Check clock phase (CPHA)
4. Try all 4 modes to identify correct one

2. Chip Select Issues

1. Verify correct CS pin used
2. Check CS polarity (active low/high)
3. Ensure CS toggles for each transaction
4. Check CS timing with scope

3. Clock Speed

1. Reduce SPI clock speed
2. Verify device max frequency
3. Check signal quality at device
4. Consider capacitance/inductance

4. Wiring

1. Verify MOSI/MISO not swapped
2. Check CLK connection
3. Verify ground connection
4. Check for signal integrity issues

UART No Data

Symptoms:

  • UART receives nothing
  • Garbled data
  • Framing errors

Solutions:

1. Baud Rate Mismatch

1. Verify baud rate matches device
2. Common rates: 9600, 115200
3. Try other standard rates
4. Calculate actual vs expected if custom rate

2. Format Mismatch

1. Verify data bits (7 or 8)
2. Check parity (None, Even, Odd)
3. Verify stop bits (1 or 2)
4. Common: 8N1 (8 data, no parity, 1 stop)

3. TX/RX Swapped

1. TX of one device → RX of other
2. Verify connections not reversed
3. Try swapping if unsure

4. Voltage Levels

1. Verify logic levels compatible
2. Check if level shifter needed (e.g., 5V ↔ 3.3V)
3. Measure voltage levels

Module Issues

Module Won't Load

Symptoms:

  • Module load fails
  • Error in log
  • Channels don't appear

Solutions:

1. File Not Found

1. Verify file path correct
2. Use absolute path
3. Check file exists
4. Verify file permissions

2. Configuration Error

1. Check XML syntax valid
2. Verify all required parameters present
3. Check parameter values correct format
4. Review module documentation

3. Dependency Missing

1. Check module requires other modules
2. Load dependencies first
3. Verify module compatible with firmware
4. Update firmware if needed

4. Hardware Not Available

1. Verify hardware module depends on is present
2. Check device connections
3. Verify device powered

Module Loaded But Channels Missing

Symptoms:

  • Module loads successfully
  • Expected channels don't appear
  • Some channels missing

Solutions:

1. Refresh Channel List

1. Press F5 to refresh
2. Reconnect to device
3. Check logs for errors

2. Configuration Issue

1. Verify module configuration defines channels
2. Check parameter values
3. Reload module with different config

3. Naming Conflict

1. Check for duplicate channel names
2. Rename channels in configuration
3. Use unique NetNames

Audio/Video Issues

No Audio Output

Symptoms:

  • Audio channel set but no sound
  • Silent output
  • Media file not playing

Solutions:

1. Verify Configuration

1. Check audio channel configured correctly
2. Verify sample rate matches
3. Check bit depth supported
4. Verify mono/stereo setting

2. Volume/Mute

1. Check volume level (not zero)
2. Verify not muted
3. Check hardware volume controls
4. Test with different volume level

3. Physical Connections

1. Verify audio cable connected
2. Check speakers/headphones powered on
3. Try different audio output device
4. Test with known-good cable

4. Media File

1. Verify file format supported
2. Check file uploaded correctly
3. Try different file
4. Verify file not corrupted

Video Not Displaying

Symptoms:

  • Image/video doesn't appear
  • Black screen
  • Wrong resolution

Solutions:

1. Display Connection

1. Verify display cable connected
2. Check display powered on
3. Try different display
4. Check cable type (HDMI, DisplayPort, etc.)

2. Resolution Mismatch

1. Check video resolution matches display
2. Try lower resolution
3. Verify display supports resolution/refresh rate
4. Check via channels for resolution settings

3. Media File

1. Verify file format supported
2. Check file uploaded
3. Try different file
4. Check codec support

Firmware Update Issues

Firmware Update Fails

Symptoms:

  • Update doesn't complete
  • Error during update
  • Version doesn't change

Solutions:

1. Connection Lost During Update

1. Ensure stable network connection
2. Use wired connection (not WiFi)
3. Verify no power interruptions
4. Try update again

2. Insufficient Space

1. SSH to device
2. Check disk space: df -h
3. Clean up old files
4. Remove unnecessary data

3. Service Won't Stop

1. Check no other clients connected
2. Manually stop service:
   sudo systemctl stop accordion
3. Try firmware update again

4. Repository Inaccessible

1. Check internet connection
2. Try default repository
3. Verify firewall not blocking
4. Check repository URL correct

Device Won't Boot After Update

⚠️ Critical Issue

Symptoms:

  • Device not responsive after firmware update
  • No network connection
  • Cannot SSH

Immediate Actions:

1. DON'T PANIC
2. Wait 2-3 minutes (may still be booting)
3. Check power LED status
4. Check network link LED

Recovery Steps:

1. Power cycle device (unplug, wait 30s, reconnect)
2. Wait for full boot (2-5 minutes)
3. Try ping
4. Try SSH connection
5. If still unresponsive, contact E-Sharp support immediately
6. Have serial console access if available

Prevention:

  • Always test firmware updates in development environment first
  • Never interrupt firmware updates
  • Ensure stable power supply
  • Keep previous firmware version available for rollback

Data and Files

Cannot Export Data

Symptoms:

  • Export fails
  • File not created
  • Export button disabled

Solutions:

1. No Data to Export

1. Verify data exists (channels visible, log has messages)
2. Ensure selected items exist
3. Check time range contains data

2. Permission Issues

1. Choose writable location
2. Verify folder permissions
3. Try different folder (e.g., Documents)
4. Run as administrator if needed

3. Disk Space

1. Check available disk space
2. Clean up temporary files
3. Choose different drive

Alias File Won't Load

Symptoms:

  • Alias load fails
  • Error message
  • Channels show NetNames not aliases

Solutions:

1. File Format Error

1. Verify XML syntax correct
2. Check for special characters
3. Validate XML with validator tool
4. Compare with working alias file

2. File Path

1. Use absolute path
2. Verify file exists
3. Check file permissions
4. Remove quotes from path if present

3. Alias Conflicts

1. Verify no duplicate aliases
2. Check for invalid characters in aliases
3. Ensure NetNames match actual channels

Getting Help

Before Contacting Support

Gather Information:

  1. Version Information:

    • Accordion Pilot version (Help → About)
    • Firmware version
    • Module versions

  2. Export Logs:

    • Application log
    • Relevant transactions
    • Error messages

  3. Document Steps:

    • What you were trying to do
    • Exact steps taken
    • When error occurred

  4. Screenshots:

    • Error messages
    • Configuration screens
    • Unexpected behavior

  5. Configuration:

    • Export alias files
    • Module configuration files
    • System settings

Contact Information

E-Sharp Support:

  • Email: support@esharp.se
  • Include all gathered information
  • Be specific about issue
  • Attach logs and screenshots

Diagnostic Commands:

# Check connection
ping 192.168.1.100

# View firmware version
AccordionShell firmware --host 192.168.1.100

# List modules
AccordionShell module

# Test basic operation
AccordionShell init --host 192.168.1.100
AccordionShell list

Common Error Messages

"Parameter 'host' can't be omitted"

Cause: No connection established Solution: Use init --host <address> first

"Channel not found"

Cause: Channel name incorrect or doesn't exist Solution: Verify channel name, check list output

"NACK"

Cause: I2C device not acknowledging Solution: Check address, power, connections

"Timeout"

Cause: No response from device/hardware Solution: Check connections, power, device state

"Module load failed"

Cause: Module configuration error Solution: Check config file syntax, parameters

"Connection refused"

Cause: Accordion service not running Solution: Start service via firmware command

"Access denied"

Cause: Permissions issue Solution: Check file/folder permissions, run as admin

See Also

An unhandled error has occurred. Reload 🗙

Rejoining the server...

Rejoin failed... trying again in seconds.

Failed to rejoin.
Please retry or reload the page.

The session has been paused by the server.

Failed to resume the session.
Please retry or reload the page.