Index AMI Gateway Not Reading Meter: Configure the Protocol from the App Step by Step

With the compatible harness connected between the meter and the Index AMI, configuration is done from Noatec's apps. If you haven't connected the harness yet, see the harnesses & wiringguide first.

Configuration apps

Choose either of Noatec's two apps — both can perform the full configuration:

• Index AMI Gateway (Android) — Bluetooth pairing, quick on-site configuration. Available on Google Play.
• Index AMI Configuration Tool (Windows / Linux) — for mass deployment and advanced diagnostics. Distribution via soporte@noatec.co.

Configuration steps

Generic steps for any meter. Model-specific parameters (speed, DLMS address, Modbus registers) are in the harness guide.

1. Connect the certified harness between the meter and the Index AMI phoenix connector.
2. Power the gateway from the meter's service bus.
3. Open the app, pair via Bluetooth and select the meter profile (DLMS/COSEM, Modbus RTU, etc.).
4. Set the serial speed, parity and address according to the manufacturer's default values.
5. Verify the first reading — if the log shows a read OK with the total active energy value, the integration is ready.
6. Enable the WireGuard tunnel to send telemetry to the AMI Platforms (see companion guide).

TCP-UART Bridge

With the harness connected and the meter profile selected, the TCP-UART bridge converts the serial frame into a TCP stream that the AMI Platforms can query. You must configure it from the app before receiving telemetry.

• UART mode: RS485 (half-duplex bus, up to 1.2 km) or RS232 (point-to-point, max. 15 m). Must match the installed harness.
• Baud rate: Meter serial speed. Typical: 9600 bps (Microstar, ISKRA MT174, Star DTS27) — 19,200 bps (Landis+Gyr ZMG405). Full range: 110–115,200 bps.
• Frame format (fixed): 8 data bits · No parity (None) · 1 stop bit · RX timeout: 500 ms. Not configurable in the current version.
• TCP mode:
  • None — the gateway does not forward data over the network. Useful only for local field testing.
  • TCP — the gateway listens on the configured port and forwards the raw frame to the AMI Platforms that initiate the connection.
  • Modbus TCP — the gateway converts the Modbus RTU serial reading to Modbus TCP format: replaces the CRC-16 with an MBAP header and exposes the result on the configured port. The AMI Platforms read it as a standard Modbus TCP client. Required for Star DTS27 and any Modbus RTU meter.
• TCP port: Port on which the gateway accepts AMI Platforms connections. Default: 8090. Change only if this port is blocked on the corporate network.

Bridge configuration steps

1. Connect the gateway via BLE and go to Connectivity Configuration → TCP-UART Bridge.
2. Select the UART mode: RS485 or RS232 according to the connected harness.
3. Enter the meter's baud rate (9600 for Microstar, ISKRA and Star; 19,200 for Landis+Gyr ZMG405). The 8N1 frame format is fixed.
4. Select the TCP mode: TCP for DLMS meters (Microstar, ISKRA, Landis+Gyr); Modbus TCP for Modbus meters (Star DTS27). Confirm the port (8090) and timeout (30 s).
5. Press «← Back» and «Apply changes to device». The gateway restarts and is ready to accept AMI Platforms connections.

In the app go to Overview → Connectivity Status → TCP Bridge section. Confirm that the «Port» field shows 8090 and the mode matches what you configured. If the AMI Platforms are already active, you will see the date of the last received connection.

If something is not working

Support documents

• RS485 diagnostics: bus not responding
• DLMS/COSEM: IEC 62056 protocol

Next steps

With the Index AMI reading the meter correctly it can already send readings to the AMI Platforms over direct TCP. If your deployment requires encrypted remote access, consider enabling WireGuard VPN point-to-point — optional.