Com'X 510 reboot after config, looooong time ?

[Anonymous user]

Is my unit broken or am i missing something ? Is it because i have configured meters/gateways on it that it can't see, have i missed a setting ? What are the issues that cause such long reboot times ?

Out of the box boot time seems to be around 5 mins, configure the unit with devices, change the IP and the reboot is taking an eternity, its just sits at the browser stating "Welcome to Com'X 510 The box is starting, please wait" refreshing every now and again, i have been sitting in front of it for around 20 minutes now........

If the boot time truly is this long then that is quite frankly totally unacceptable.

[Bojan]

Hi Hal,

Thank you for the explanation.

Is the PME Log Inserter functionality implemented in ComX510 firmware for the native devices?

Best Regards,

Bojan

[Hal_Etheridge]

Not sure but likely not.

The way to tell is if the ComX appears as an ION node in the PME system.  If it is just added as a gateway but not as a device then LogInserter has no knowledge that it exists.  For instance if a device appears in DiagViewer in the LogInsert tabs then it is a device and any logs will be downloaded automatically.  In that case it is just part of the communications infrastructure like any dumb modbus gateway.

Most likely the only way to get the ComX logs into PME is to use ETL to download and insert them directly into the database - note that I am not remotely close to being an expert on the ComX so I could be wrong so please verify this from another source.

[Bojan]

Hi Hal,

I hope that Colton Peltier​ will be able to confirm if ComX510 has some kind of Log Inserter functionality, as I need to troubleshoot those ION7330 meter data gaps:

I think there are 2 possibilities:

1. ComX510 doesn't have LogInserter and RS485 MODBUS communication is intermittent.

2. ComX510 has LogInserter and ION7330 meter is freezing from time to time.

[Anonymous user]

Hi Bojan,

I'm not familiar with LogInserter, so I think it's unlikely that the ComX supports this functionality. Looking at your logs, I can see an Error 19 on each of the N/A values, Error 19 is a timeout. It seems that the ComX is sending messages to the device but not receiving a reply at these times.

Best Regards,

Colton

[Bojan]

Hi Colton,

From your explanation it, looks like the ION7330 meter is faulty and has to be replaced, but also that in a case of RS485 MODBUS communication interruption, ComX510 would not be able to recover data from meter on-board logs. Right?

Bojan

[Bojan]

Hi Richard,

I'm on a site upgrading 52 Com'X510 to the latest Firmware version v4.0, and it looks like the boot lag is gone, most likely because they changed to only save configuration files on boot up when a change is necessary, not every time the Com'X boots in the latest Firmware version.

The upgrade process is still very time consuming and unpredictable - it takes 15 min, couple of hours, or never to upgrade from version 1.0 to 2.1 and 4.0.

Sometimes, the Web upgrade procedure just stops on 98% and wait for hours, restarts automatically, resets to factory settings or never comes back. The USB procedures sometimes turns on the green power led after 10 minutes, but the firmware versions stays the old one.

Best regards,

Bojan

[Anonymous user]

Bojan, Hi

Thanks for the update, sounds like a small step in the right direction, however it still sounds like its a way off being stable enough for us to consider proposing it anywhere.

Regards

[sesa205726_brid]

Hi Colton,

I did a FAT of a Smart Panel with Com'X510 inside. I upgraded the device to the last fimware version and set it.

After deliver the Smart Panel to the customer, I wanted do SAT but Com'X510 took about 45 minutes for the boot but it was blocked. Then I had to reset the device to factory settings.

Once again the device is not stable despite having been updated to the latest firmware version.

Once again I lost time to work with this product!!!

Other behavior that I and customers note is that the product is very slow. Everything you want do, is very slow: device setting is very slow, pass to web page to another is very slow.

When happens that the product is blocked I can't request technical support because when I have to reset the device I lose everything about the diagnostic.

Then, I ask to myself, what is the sense of the diagnostic if I can't do a diagnostic of what happened to the device?

Should be useful to have a way to go inside the device and unblock it with a special tool, since the during the startup the Ethernet led flashes and seems that part of the OS is on.

Like an Energy Server is it fundamental dont' lose the energy log. But after a reset of the device I lose the energy log and, it is not admissible

I hope in future radical changes of this product.

Regards

[AleksandrKrygin]

I would not recommend to upgrade firmware to version 4.0.10 for resourceadvisor projects. Because with this version gateway cannot do HTTPS push to RA server. Always connection is rejecting.

Only downgrading to 3.6.3 solved my issue. Found this problem in one of customer site and checked with my gateway in lab.

Ticked in tsc was created, still waiting for response.

Also gateway goes to reboot with this firmware when can't reach cellular network (GPRS) and trying to send CSV.

[Anonymous user]

Hi Aleksandr,

Can you share the publication URL of Resource Advisor? I can ensure the certificate support is added back in for our next version in March.

Best Regards,

Colton

[Anonymous user]

Hi Aleksandr,

Can you give me a backup of your configuration and the diagnostic logs after a failure? I'll attach them to the work item for March.

Best,

Colton

[AleksandrKrygin]

Answered to you in PM.

[Anonymous user]

Hi Aleksandr,

We're investigating this issue (Jon Anderson), and think it may be related to the 3G/GPRS your ComX is using. In version 4.0 we've upgraded our ComX's to use TLS 1.2 rather than TLS 1.0 to improve cybersecurity. We think that the improved security handshake may be being broken by a bad cellular connection.

When I try with my ComX using ethernet I'm getting a valid HTTP response. Have you seen this same issue using ethernet? If so, can you provide us with the logs?

Best Regards,

Colton

[sesa64390_bridg]

Hello Colton,

Bojan has been helping us to test the latest Com'X510 firmware data push to Resource Advisor (using the CSV Export publication) for an upcoming project in Toronto.

We have found that using firmware V4 will not connect to the SHA-2 URL (eemhttpna1.resourceadvisor.schneider-electric.com) even when connected using a private Rogers connection (to rule out any network, firewall or cellular issues).

However when the 510 is downgraded to V3.6 the Com'X connects without issue to the Resource Advisor SHA-1 URL (eemhttpna1.energyoperation.schneider-electric.com).

It looks like it's not related to the TLS1.2 handshaking with there being connection issues aswell when using a wired connection?

Thanks

Colin

[AleksandrKrygin]

Hello, I can't do HTTPS-push via SE Ethernet network. Only HTTP:80 and it's working fine, I can see csv files into server folder.

Looking at network diagnostic - it shows that zscaler proxy cutting off HTTPS pushing via 443 port. Unfortunately I don't have any alternative connection in my office except SE network with proxy.

But any way regarding projects needs that we have to use only SE GPRS modems in Com'X gateways. Alternative 3G USB modems (like Huawei) are also not supported by gateway.

So if you planned to use TLS 1.2 without option to manually switch to 1.0 it is not applicable for us, and we will stay on 3.6.3.

Thanks a lot, I hope you will find best solution.

[Bojan]

Hi Colin,

I'll downgrade the Com’X's to V3.6 to move forward with the next week project on-site installs, using the SHA-1 URL:
eemhttpna1.energyoperation.schneider-electric.com server.

Best Regards,

Bojan

[Anonymous user]

Hi Bojan & Aleksandr,

Our team has worked closely with the Resource Advisor team to diagnose and solve this issue. It will be included in our next release, v5.0.

Best,

Colton

[AleksandrKrygin]

Hello, Colton! When we can meet a new release of firmware?

BR!