COM'X200 Firmware Version 1.1.14 gateway function

[EvonneYin]

Hi All,

Does the Gateway function work via the GPRS Modem or only the onboard Ethernet port?

Thanks!

[LaurentCoene · Accepted solution]

Only on the ethernet port!

[JamesJeanette]

Laurent is correct.  The gateway of the Com'X 200 Version 1.1.14 is a Modbus gateway.  This means that you cannot use the Com'X 200 as a gateway for GPRS, WiFi, or to the connected WAGES DI/AI (inputs) as it is released today.  We are working with the development team to have more gateway functionality introduced, but that will come later in the year.

Until then, you can still actively monitor and log data from the embedded DI/AI (inputs).  Also very important, the Com' X 200 is natively ready to connect to the cloud through RSP - Remote Service Platform...the infrastructure for safe & optimized cloud connectivity.

James

[JamesAZZO]

Not good unless only for uploading log files. Not remote access to devices. But...InHands do this no problem. Need a =S= solution.

[sesa77557]

Hi James, I have met an important Customer few hours ago and he asked me if he can use the gateway function to monitorize the embedded DI/AI.

From your last feedback I suppose that today it is not possible. Am I right?

When do you think to implement this feature? (thanks to a firmware update?) Do you have a detailed scheduling about the release of new features like this one?

I think that this is quite strange and it can be seen from Customers as a limit of the link between gateway functions and embedded DI/AI features, moving some Customers to opt for other solutions...

Thanks to give us a feedback.

Roberto

[LaurentCoene]

Yes, this is currently not possible to use the gateway function on the DI and AI! (I know it's lame!)

That means that you'll still need to use an EGX100 with a SIM10M or a Twido or a SmartLink for the DI or SIM10M for the AI or use an Automation Server with the IOs you need.

After a chat with the LoB, they mentioned that Q1 2015 is targeted for this feature, however many things can change between now and then!

[arjanbijker]

I agree with James - not good. We will NOT push the device here until that is resolved.

Also, there must be a way to disable to security / built in firewall of the device.

Not good if you have the EBX200s connected on your corporate APN network.

[Anonymous user]

Hello Arjan

What do you mean by "disable to security / built in firewall"

In future release 1.3,

We will introduce a setting to enable or disable the "modbus-TCP to Modbus-RTU gateway" feature

//==========================================

About the "modbus-TCP to Modbus-RTU gateway" feature : we use an internal wellknown Linux firewall in the Com'X 200

This firewall is called "Netfilter" and is configured using a tools called "IpTables".

At the developpment level, we can thus implement any route.

Today, the only routes authorized are from serial port to LAN ports (we have discarded this feature for all port having a WAN connectivity)

This setting is consistent by default with cibersevcurity rules

If you have a business story that requires other configuration, please describe it, and I will transmit it to the marketing

Regards

     Jef

[JamesAZZO]

Arjan,

What makes you think that you cannot use the EBX200 with a private GPRS APN using a SIM Card? (presuming this is what you mean?) If that's the case, we're in trouble because we run our own private APN with the telco here, and we intend on using this product with our SIM cards. Why would the firewall block this?

Thanks,

James

[arjanbijker]

Hi James,

The EBX200 works with private/corporate APN.

But the shortfalls are as following:

1. You cannot access it remotely via Telnet or SSH. The only allowed

protocol is HTTP over GPRS , but this is a non-starter with this product -

takes way too much bandwidth and you cannot login remotely - timeout all

the time (I have tried this). If Schneider can enable ssh or telnet for

remote connections this it would be excellent. The other alternative is

to roll out with 3G instead of GPRS - then at least HTTP will work.

My opinion is that when you are on a corporate APN network, I don't want

the built-in security features of the EBX. Please don't disable ping /

ICMP / ssh / telnet requests (we need it! especially on GPRS!)

I will setup my firewalls or routers to take care of the rest.

2. You cannot ping it from WAN interface (so you don't know if the device

is on your network or not)

3. On the device itself you cannot see your WAN IP address - makes remote

troubleshooting extremely hard, because you have to guess now what the WAN

ip is.

4. The gateway functionality doesn't works over GPRS/WAN interface. If we

are connecting mid-super devices to the EBX we lose all the additional

functionality like onboard logging, waveform capturing etc.

[JamesAZZO]

Thanks for such a comprehensive reply. 3G being enabled would certainly be the way to go for us.

[nigel_greenwave]

The COMX has much potential, but until the inputs can be exposed via a gateway I will continue to use a EGX.

[JamesJeanette]

It's coming...I have sent your feedback to the engineers. 

Thanks for sharing!

[sesa205726_brid]

Hi ,

I want tosignalanomalies about the functionality as gateway on Com'X200 with firmware version 1.1.14

1. with BCPM devices:

for to set the BCPM devices are using the tools ION Setup and E3X, the Com'X200 is used as gateway. The BCPM device is detected and read rightly, but when is send the configuration not all the parameters are changed and it is present a modbus communication error.

The same procedure, if done with an EGX, has not problems.

2. with Sepam devices (MV protection relay)

when is used the configuration tool (SFT2841), Com'X200 used as gateway, doesn't allow the configuration because the Sepam is not detected by the tool software.

The same operation, if done with an EGX, allow to set rightly the Sepam.

Seems that this firmware version doesn't work rightly as gateway.

Thank you for your attention.

BR@

[JamesJeanette]

Thank you for this feedback Salvatore.  I will escalate this for our support teams to address.

James