System configuration personalizes how the Index AMI identifies itself on the network and controls time synchronization, connectivity monitoring, and automatic restart behavior. These parameters are the same in the Android app and the desktop tool — the difference is only how you access them.

Where to configure it

App Android: Android app: Main Menu → System Configuration
Herramienta de escritorio: Desktop tool: template editor → sections Device Identification, RTC, ICMP and Scheduled Restart.

Device identification

These fields allow the operator to recognize each unit in inventory. They do not affect Index AMI operation, but are essential for traceability in mass deployments.

Custom label (required): Short name identifying the unit — appears in the device list. Max. 64 characters. Use a code that indicates zone and number: MET-NORTH-001, SUB-5-G2.
Device number: Numeric ID for integration with the AMI Platforms or inventory system. Range: 0–4,294,967,295.
Description: Free text for model, protocol or installation notes. Max. 128 characters.
Location: Postal address, geographic reference or GPS coordinates. Max. 128 characters.
Port label: Physical connector used for the meter: RJ45-1, RJ45-2, DB9-RS232, RJ12, Pin 27→A. Max. 128 characters. In desktop templates this field is pre-filled with the meter profile.

Full example: Label «MET-NORTH-001» · Number «100001» · Description «Microstar P2000-D RS485 HW3» · Location «5th St #10-20, Manizales» · Port «RJ45-2».

Time synchronization (NTP/RTC)

The Index AMI synchronizes its internal clock with an NTP server so that reading timestamps are accurate. The first boot may take up to 2 minutes to synchronize.

NTP host (required): Time server address. Use pool.ntp.org for most installations, or the corporate NTP server if the network requires it.
NTP port: Standard NTP port: 123. Change only if your network uses an NTP proxy on a different port.
Sync interval: How often in hours the Index AMI contacts the NTP server. Range: 1–24 hours. The default of 12 h is suitable for most installations.

If the Index AMI has no internet access on startup, logs will have incorrect timestamps until the first synchronization is established. Verify LTE connectivity before deploying.

Connectivity monitoring (ICMP/Ping)

The Index AMI periodically pings an external server to detect connectivity loss. If the server does not respond, the Index AMI can initiate an LTE reconnection cycle.

ICMP host (required): Server to monitor. Use 8.8.8.8 (Google DNS) or 1.1.1.1 (Cloudflare) if the network allows it. For corporate networks, use the AMI Platforms or internal server IP.
Number of packets: How many pings are sent per cycle. Range: 1–65,535. A value of 5 balances detection and consumption.
Interval: Time between ping cycles, in milliseconds. 60,000 ms (1 minute) is the typical field value.
Timeout: How long the Index AMI waits for a response before marking the cycle as failed. 5,000 ms is adequate for LTE networks with low latency.

In environments with firewalls that block ICMP, use the MQTT or AMI Platforms server as host, as long as it accepts ping.

Scheduled restart (Runtime)

The Index AMI can restart automatically every certain number of hours to free memory and ensure long-term stability.

Restart period: Hours of continuous operation before automatic restart. Range: 0–48 hours.

0 = disabled (no restart). 24 = daily restart (recommended in field). 48 = restart every two days.

The restart interrupts BLE, LTE and active TCP connections for approximately 30 seconds. Schedule restarts during low-demand hours (e.g. 03:00 local).

Configuration steps

Open the app or tool and connect the Index AMI via BLE.
Navigate to System Configuration (app) or edit the template in the desktop tool.
Complete the Identification section: custom label (required), device number, description, location and port label.
In the RTC section: enter the NTP host (pool.ntp.org if no corporate server), port 123 and sync interval (12 h recommended).
In the ICMP section: enter the host (8.8.8.8), packets (5), interval (60,000 ms) and timeout (5,000 ms).
In Scheduled Restart: enter 24 for daily restart, or 0 to disable it. Press «← Back» and then «Apply changes to device».

Verify the configuration

In the Android app go to Overview → Device Profile tab. Confirm that the label, number and description you entered appear in the Asset Information fields, and that «Date and Time» shows the correct UTC time (indicating NTP synchronized).

If something is not working

Symptom	Probable cause	Action
UTC time does not sync or is incorrect	The Index AMI had no LTE connection on startup — NTP requires internet for the first sync	Verify that the 4G APN is active first. The Index AMI will sync NTP automatically on the first cycle after connecting.
ICMP always reports connectivity failure	Host 8.8.8.8 is blocked by the operator or corporate network firewall	Change the ICMP host to the MQTT broker or AMI Platforms IP, which is accessible from the SIM.
Scheduled restart does not happen at expected time	Restart counts hours of operation since last boot, not a fixed clock time	For a night restart, calculate the interval from installation time, or use 24 h for daily restart.

Support documents

Configure 4G APN — prerequisite for NTP

Next steps

With the system identified and the clock synchronized, the next step is to configure LTE connectivity. See the 4G APN configuration guide to enter the mobile operator APN.