1. Q: Is the MFM meter powered ON and displaying readings on its local screen?

A: If no → check power supply, wiring, fuses.
If yes → move to communication check.

2. Q: Are the CT/PT connections and polarity correct?

A: Wrong CT/PT wiring will not stop communication, but readings may be incorrect. Ensure CT direction and ratio are correct.

3. Q: Is the communication port (RS-485 / Ethernet) enabled and configured in the MFM?

A: Verify baud rate, parity, stop bits, and slave ID in the meter settings. These must match the EnMS software.

4. Q: Are RS-485 communication wires (A/B) connected properly?

A: Yes → check for polarity (A to A, B to B).
No → correct wiring and ensure termination resistor at last device.

5. Q: Can you read data from the meter using Modscan/Modpoll (from a laptop)?

A:

• If YES → meter is healthy, issue is in EnMS configuration.

• If NO → problem in wiring/port/settings.

6. Q: Is the Modbus ID and register mapping correct in EnMS software?

A: If wrong ID/registers → EnMS cannot read values. Correct as per the MFM manual.

7. Q: Are there error messages in EnMS software (Timeout, CRC error, device not found)?

A:

• Timeout → wiring/ID/baud mismatch.

• CRC error → data corruption due to noise or wrong settings.

• Device not found → wrong IP/ID or device offline.

8. Q: Has the network converter (RS-485 to USB/TCP) been checked?

A: Faulty converters or driver issues can stop communication. Replace/test with another converter.

9. Q: Is the polling interval in EnMS software configured properly?

A: Very short polling may cause a data timeout. Set 5–10 seconds polling.

10. Q: Could the meter’s communication port be faulty?

A: If all settings are correct and Modscan also fails, → meter port may be damaged. Replace or repair.

✅ Final Checklist for Client:

• Meter powered and displaying locally

• CT/PT wiring is correct

• RS-485/Ethernet wiring correct & terminated

• Baud rate/parity / stop bits / ID matched
  

• Test with Modscan/Modpoll
  

• Verify EnMS configuration (ID, IP, registers)

• Check the converter/network device

• Review EnMS logs for error type