Ekho Translator (EK-WL8-TRH) Replacement Instructions

Who this article is for

This article is for engineers and technicians who design, commission, or maintain Ekho hybrid wireless systems.

Typical situations:

• You need to replace an existing Ekho translator (TRN) due to failure or upgrade.
• You have a backup from Ekho Configurator and want to restore it to a new translator but get an error.
• An output unit (EK‑WL8‑OUT) does not operate during testing.
• Ekho devices do not appear as expected on the fire panel loop.

1. Basic rules when replacing an Ekho translator

Key principles to avoid data loss and restore failures when swapping translators.

1.1 Preconditions

Check these points before physically changing the translator.

Before replacing a translator, make sure:

• The new and old units are the same translator family/type
  (same manufacturer / same Ekho translator series).
• As far as possible, the new translator’s firmware version matches the old one.
  • Large version gaps between backup and target firmware can cause restore errors or inconsistent behaviour.

1.2 Recommended high‑level flow

Overview of the end‑to‑end process from backup to on‑site verification.

Diagram 1 – High‑level translator replacement flow (concept)

Old Translator (TRN-OLD)                     New Translator (TRN-NEW)
-------------------------                    -------------------------
[1] Connect Config Tool
[2] Take backup     ----------------------->  [3] Connect Config Tool
(Backup file)                                  [4] Check FW/Tool version
                                               [5] Restore backup
                                               [6] Verify devices on-site

Typical error messages and what they usually mean.

When restoring to a new translator, you might see errors such as:

• “Backup file refers to translator with different ID”
• “Device count mismatch – expected XX, found YY”
• “Cannot restore data to clean system – looking for 65XX…” (example wording)

Typical causes:

1. Translator ID mismatch

   • Some versions embed the original translator’s ID in the backup file and do not fully support restoring to a different translator without additional steps.

2. Config Tool vs firmware version mismatch

   • Backup was created with Config Tool v10 + TRN FW v10, but you are trying to restore into TRN FW v12 using Config Tool v12, etc.
   • Large jumps can cause schema / structure mismatches.

3. Corrupted or incomplete backup from the old translator

   • If the old translator was unstable when the backup was taken, the resulting file may be inconsistent.

2.3 Recommended detailed restore process

A structured decision flow to resolve most restore problems.

Diagram 2 – Detailed restore decision flow

          Start
            |
            v
  Check old setup:
  - Config Tool version?
  - TRN-OLD FW version?
            |
            v
 Check TRN-NEW FW + Tool
            |
            v
Same major version as old?
      /           \
    Yes            No
    |              |
Try restore        Try installing
with same major    matching Tool
Config Tool        (and, if possible,
                   align FW), then
                   restore
            |
            v
Restore OK?
      /         \
    Yes          No
    |            |
   Done   ->  Factory reset or
              clear TRN-NEW,
              try again
                       |
                       v
       Still failing?
            |
            v
   Manual re-creation
   of configuration

Practical steps:

1. Verify versions

   • Note the Config Tool and TRN‑OLD firmware you used to create the backup.
   • Connect TRN‑NEW and check its firmware version and the Config Tool version.

2. If possible, install the same major Config Tool version you used for TRN‑OLD

   • Try restoring the backup to TRN‑NEW using that same major tool version.
   • If successful, you can then upgrade firmware/tools afterwards if needed.

3. “Clean system” and device count errors

   • If errors mention a “clean system” or device count mismatch:
     • Check whether TRN‑NEW already has some configuration stored.
       If so, factory reset or clear its internal configuration before restoring (if supported).
     • Ensure the expected number of devices in the backup is consistent with what TRN‑NEW is allowed to handle.

4. If restore is still impossible

   • Export as much configuration data as possible from the backup or screenshots.
   • Re‑enter configuration manually into TRN‑NEW using Ekho Configurator.

3. EK‑WL8‑OUT output unit does not operate – troubleshooting

Step‑by‑step checks when an Ekho output module does not activate as expected.

3.1 Check physical wiring and load first

Rule out simple cabling or load issues before changing configuration.

1. Verify wiring to the load

   • Confirm that COM / NO / NC terminals are wired according to the datasheet.
   • Check polarity and supply for any external PSU or sounder/beacon being driven.

2. Swap test

   • Temporarily move the same wiring and load to a known good output unit:
     • If it works on the other unit, the wiring/load is OK and the issue is likely the original EK‑WL8‑OUT or its configuration.
     • If it still does not work, suspect the load/wiring rather than the module.

Diagram 3 – Simple swap test

 [Load + wiring] ---> [EK-WL8-OUT #1]  (No output)
              |
              |---(temporarily)----> [EK-WL8-OUT #2]  (Known good)

3.2 Check address, zone, and cause & effect (C&E)

Ensure the panel is actually commanded to drive that specific output.

1. In Ekho Configurator and/or the fire panel programming:
   • Confirm the address and zone of the EK‑WL8‑OUT.
2. Review the C&E logic:
   • Which events (Fire, Pre‑alarm, MCP, etc.) should trigger this output?
   • Is the output configured in the correct group, and is that group being triggered by your test?
3. During testing:
   • Make sure the test event you are generating matches the condition that should activate the EK‑WL8‑OUT (e.g. you aren’t only simulating a pre‑alarm when the output is configured to activate only on full fire).

3.3 Check wireless link quality and device status

Poor signal or battery problems can prevent outputs from operating reliably.

1. In Ekho Configurator, check for the problematic EK‑WL8‑OUT:
   • RSSI / signal strength
   • Battery status
2. If signal is marginal:
   • Consider moving the device, changing the location of the translator/repeater, or associating it with a closer repeater.
3. Confirm that:
   • The device is paired with the correct translator.
   • There are no communication faults reported.

3.4 Address swap test

Use a known good device to separate hardware problems from configuration issues.

1. Identify a known working EK‑WL8‑OUT (or another I/O device).
2. Temporarily swap the addresses / roles:
   • Assign the working unit the same address/C&E role as the problematic one.
3. Observe:
   • If the known good device now works with the problematic address → likely a hardware issue on the original unit.
   • If neither device works on that address/role → likely an addressing or C&E configuration issue.

4. Devices not appearing or not behaving as expected on the panel loop

4.1 Quick checks

1. In Ekho Configurator:
   • Confirm the device is actually paired to the translator.
   • Check its signal and status.
2. On the panel:
   • Have you run a loop scan / auto‑learn since adding the new devices?
   • Is the address range correctly configured in the panel?
   • Are there any duplicate addresses on the loop?

4.2 Typical scenarios

• Device is visible in Ekho Configurator but not on the panel loop

  • Check the translator‑to‑panel wiring and any intermediate modules.
  • Confirm that the panel has the translator configured as the appropriate device type (e.g. loop interface, gateway, etc., depending on the panel brand’s integration).

• Device is not visible even in Ekho Configurator

  • Check that batteries are fitted and isolation tabs removed.
  • Confirm that you followed the correct learn/pairing procedure.
  • Move the device closer to the translator or repeater for pairing.

5. Before requesting RMA – what to collect

Before you consider an RMA (return/replace) for Ekho components, it helps to gather:

• Device details: model, serial/lot number, location on site.
• Software context:
  • Ekho Configurator version
  • Translator firmware version(s)
• Logs and configuration files:
  • Any backup files or exported config
  • Screenshots of device status / error messages
• Tests already performed:
  • Swap tests with other devices
  • Results of address / C&E changes
  • Any changes to wiring or layout

Providing this information up front allows support to reproduce and diagnose issues faster and reduces the back‑and‑forth with the customer.

Last reviewed: 2026-04-16 — Reviewed by: Philip Green