- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Link copied. Please paste this link to share this article on your social media post.
Hi Guys,
I am setting up a testing system to use ComX200 with firmware v1.1.20 as a gateway, the system structure please see below. In the system, ComX200 can communicate with downstream device PM5350 and ION6200 via EGX300 properly. But PME cannot talk to PM5350 (set up ComX as a gateway site in PME), and I don’t know how to configure PME to talk to ION6200. Does firmware 1.1.20 support gateway functionality?
Any comments and suggestions are welcome.
Accepted Solutions

Posted: 2014-08-26 08:42 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Link copied. Please paste this link to share this article on your social media post.
The Modbus gateway features is only available for interfaces that are not dedicated to the wan.
If the Com'X 200 is configured with 2 separated IP networks,
- the modbus gateway features will only work for interface eth2
- the modbus gateway features will not work for interface eth1
If the Com'X 200 is configured with 2 switched IP networks,
- the modbus gateway features will work for interface eth1 and eth2
This rules has been implemented in order to enforce ensure cybersecurity :
If the customer wants to separated the network between
- "Publication network" (public, connected to the wan) and
- "Acquisition network" (private and reserved technical devices),
It seems logical to disable anybody from the pubic network to send modbus request to any devices connected to the com'X 200
Please consult pages 35-36 of the design guide for more details
Regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Link copied. Please paste this link to share this article on your social media post.
Hi Ryan,
I found the same problem with the Com'X here in our office (also if it is version 1.1.14). It is impossible to access the Com'X as a gateway neither with PME nor with Modscan or PMCModbus. The connection is always timing out. I have also reported this problem to the technical support.
Daniel

Posted: 2014-08-26 08:42 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Link copied. Please paste this link to share this article on your social media post.
The Modbus gateway features is only available for interfaces that are not dedicated to the wan.
If the Com'X 200 is configured with 2 separated IP networks,
- the modbus gateway features will only work for interface eth2
- the modbus gateway features will not work for interface eth1
If the Com'X 200 is configured with 2 switched IP networks,
- the modbus gateway features will work for interface eth1 and eth2
This rules has been implemented in order to enforce ensure cybersecurity :
If the customer wants to separated the network between
- "Publication network" (public, connected to the wan) and
- "Acquisition network" (private and reserved technical devices),
It seems logical to disable anybody from the pubic network to send modbus request to any devices connected to the com'X 200
Please consult pages 35-36 of the design guide for more details
Regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Link copied. Please paste this link to share this article on your social media post.
Here are the excerpts from the Design Guide:
James
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Link copied. Please paste this link to share this article on your social media post.
Hi Daniel, I got you case in our support system. I will get you back after I verify the both structure, 2 seperated IP and 2 switched IP.
Technically, ComX200 supports two kinds of gateway configuration which can be found at page 35 and 36 in design guide that can be downloaded at . You can see the tests I am doing below, maybe you would like to do some tests on your device according to design guide to see if they works fine.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Link copied. Please paste this link to share this article on your social media post.
Hi Jef & James,
Thank you very much for your answers which is very helpful to make me understand the strategy of ComX200 working as a gateway. Today, after going throught the gateway part of design guide, I changed my network and did further tests, but PME still cannot talk to the downstream device under ComX200. Could you do me a favor to help to check my system configuration to see if there are wrong settings on them? Does the firmware v1.1.20 support gateway funcation?
1. Sperated IP address
ComX200 connects to PM5350 properly, The configuration page of ComX200 can be login to from the machine hosting PME via IP 10.25.1.1.
PME can reach to ION6200 which is connected to EGX300, but cannot talk to PM5350 successfully.
2. 1 IP for both ports
On the computer hosting PME can access into ComX200 configuration page via IE, but PME cannot connect to PM5350 successfully.
Thanks,
Ryan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Link copied. Please paste this link to share this article on your social media post.
Today, both of the strucure are working properly, for the seperated IP system I fouud that the default gateway setting of network connection on the machine hosting PME was 10.24.1.1, I changed it to 10.25.1.1, then PME can talk to downsterad devics successfully.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Link copied. Please paste this link to share this article on your social media post.
Thanks..this was confusing me as to why you were having this issue.
Did you make any changes?
James
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Link copied. Please paste this link to share this article on your social media post.
The only change I made is to correct the Default gateway setting for Local Area Connection from 10.24.1.1 to 10.25.1.1.

