COM'X 510 - No Modbus TCP Device Data

[AdhishS]

Experiencing an issue where a COM'X is no longer able to load data from PM8000s due to "A communication error has occurred". The COM'X is showing TCP connection timeouts for each device. Restarting the COM'X and increasing timeout parameters has not changed anything.

Firmware:

COMX510 - 6.5.4

PM8000 - 3.1.0

PAS600L - 1.5.1

Customer has the following project architecture:

- LX40_1: 2x PM8000 (Ethernet daisy chain)

- LX40_2: 1x COM'X 510

- LX40_3: 1x PAS600L 

- LX40_4: 1x PAS600L

The intention is for the COM'X 510 to serve as the principal energy server where all other WAGES (collected by PAS600Ls) and electrical data (PM8000s) are displayed and logged. Each LX40 router is equipped with a public static IP address (Telus SIM cards) and the communication on the Telus network works properly. The public static IPs have changed over the course of the project due to having to replace SIM cards, however the COM'X data was verified successfully before and after these changes. 

LX40_1 uses the following port forwarding rules, and I can successfully connect to the meters webpages using 9444 and 9445:

<PublicIP>.9502 --> <PM800_1>.502

<PublicIP>.9444 --> <PM800_1>.443

<PublicIP>.9503 --> <PM800_2>.502

<PublicIP>.9445 --> <PM800_2>.443

Similar port forwarding rules are used for the other LX40s, with the same issue that HTTPS data is working but Modbus is not. As a test, I checked whether LX40_3 could read Modbus data from the PM8000s connected to LX40_1 or PAS600L connected to LX40_4, however getting the same issue of connection timeout. 

Please see COMX diagnostics and configuration files attached and also screenshots attached of Modbus parameters of COM'X, PM8000 and PAS600L. Any troubleshooting advice would be appreciated.