Com'X 510 Firmware Version 3.5.24

[Arneil_Dalope]

Hi,

Just found the latest version of firmware through our friend google.

ComX510v3-5-24_Firmware_EBX510 | Download Schneider Electric

The firmware we got here in the community is Version 3.0.7. Good thing I checked first otherwise I will use the one we got here. Would be good if the community also has the updated latest firmware of the all the devices.

Cheers,

Arneil

[sesa59910]

Thanks for this Arneil, I was completely unaware this came out.

Just as an additional FYI for anyone else that may be interested, below are the release notes for 3.5.24. They are copied directly from the PDF within the firmware ZIP file.

New Features

Device Support

See Known Issues for device support before upgrading the Com’X firmware.

MasterPact MTZ

Wired support only. The MTZ must be manually created as an Ethernet device. Device discovery is not available with MTZ using IFE.
See Known Issues for MasterPact MTZ support before upgrading the Com’X firmware.

IFE IO Modules

Single device view for IO modules is now available for all breakers.

ZigBee Devices

EM4399 is now supported.

System Level View

The Com’X displays a navigational link for each Ethernet connected device within the Device Settings page.

Network Access

Enabled upstream access in Firewall Management is design to provide network access for devices down stream of Com’X that would normally have no access to the internet. This gives the downstream IP device access to remote servers such as DNS, SMTP, SNTP, etc.

ZigBee Green Power

In this release, the ZigBee support has been updated to support a dual stack for both ZigBee Green Power and ZigBee Pro.

ZigBee Network Management

Careful management of the ZigBee network is very important to maintain easy access to the ZigBee devices within the monitoring system.

A ZigBee device joined to a network will remain joined to that network until it is freed by the Com’X. Deleting the network without removing its joined devices will leave these devices unable to join other networks until they are manually placed in a pairing mode. This requires physical access to the ZigBee device, which may be prohibitive due to its location.

Always delete ZigBee devices before performing a factory reset on the Com’X. Verify the devices have been removed from the network after deleting by navigating to Maintenance > Logs and confirm a “leave the network” entry for each device. Once confirmed, you can perform a factory reset. ZigBee Pro devices such as the EM4300 will leave the network quickly, but Green Power devices such as the eMAG will take up to a minute due to their periodic communications to the network.

Follow this best practice also when removing an unwanted device from the network before power cycling (shutting down) or resetting the Com’X.

Digital Service Platform

Digital service platform is a background platform that enables a variety of optional Schneider Electric digital services. DSP replaces the Remote Service Platform.

DSP allows you to remotely manage firmware upgrade, configuration backup on the cloud, troubleshooting, and parameter settings; associate a SIM card; and publish collected data to Schneider Electric energy management services.

See Known Issues before upgrading the Com’X firmware.

Improvements

Version 3.5.24 supports the following improvements:

Custom model support

Com’X 510 now supports custom models based on Schneider Electric models. Please review Known Issues for a list of limitations for this feature.

Corrections

Version 3.5.24 supports the following corrections:

• Improved Network Diagnostic PING service. [179607]

• Corrected ‘Factor’ calculation for custom models. [179397]

• Corrected PM500 Lead/Lag Power Factor indication. [169016]

• Added default publication parameter selection for the EM4300 ZigBee device. [177263]

• Custom model edits are now applied without the need to log out and back in. [167751]

• Custom models are now supported in Real Time Trending. [167686]

• Custom events based on digital inputs are now operational. [172682]

• Added additional predefined WAGES measurements for custom models. [172755]

• Boolean variables coming from custom models are now refreshed. [182418]

• Self-sign certificate has been upgraded to SHA2. [177111]

• PM500 now reports all powers correctly. [179119]

• PL Tags now support Modbus Scattered Read. [168816]

• Improved Control Reset performance for PM5xxx. [155655]

• Deleted devices no longer persist on the Real Time Trending page. [167775]

• Negative values now supported for custom models in Real Time Trending. [167752]

• Custom model topic names now support white spaces. [167675]

• ATS48 Soft starter measurement inconsistencies corrected. [167923]

• ION 7600 IP device now supported. [171898]

Known Issues

Custom Device Model

• Models based on Schneider models in the Com’X 510 are not supported on Single Device View, Summary View, and Control pages.

• The ‘Factor’ parameter for custom model creation has no character limit. If more than 10 characters are entered, the associated measurement will not be displayed. [147750]

• Custom models based on the MasterPact MTZ X eIFE are not functioning. [189481]

• User cannot define overlapping register and coil addresses when creating custom models with multiple frames. [179785]

Device Support
MasterPact MTZ/ IFE IO

• The MasterPact MTZ is supported in wired configuration using an IFE or eIFE. It must be manually created as an Ethernet device using the IP address of its connecting IFE/eIFE and slave address of 255.

• Custom models for the MTZ can be created, but a custom model based on an MTZ should not be created. Custom Models based on the MTZ will appear as out of service in this release.

• Heavy communications to the MTZ can cause the MTZ to go out of service. The out of service time can be reduced or disabled by changing the out of service time setting in the Diagnostics > Communications Check page.

• Setting the Date/Time in the MTZ may not successfully set the time in the IFE on the first attempt.

System Topology Best Practices

You must use this topology to trigger pre-defined events:

1. A MasterPact MTZ must be created as an Ethernet device type using the MasterPact MTZ X IFE or MasterPact MTZ X eIFE device models.

2. For any additional breakers associated with the same IFE, create a new IFE/eIFE using the same IP address as the MasterPact MTZ X IFE/eIFE. Then create the breakers as Modbus serial devices under the IFE.

ZigBee dongle replacement

Issue: When replacing the ZigBee dongle on the Com’X, ZGP devices are orphaned and must be reset. This reset action is generally not possible for eMAG.

Some configuration data is saved by the ZigBee dongle. This data is downloaded to the dongle only after commissioning the ZGP devices.

Solution: After the ZigBee commissioning is finished, perform a backup of the Com’X configuration. Use this backup configuration in the event the ZigBee dongle must be replaced.

Outstanding Issues

• Heat Energy and Heat Power measurements are not converted to kWh when published, logged, or displayed in dashboards. The values are delivered with the selected Count and Flow units created in the custom pulse meter. [172584]

• Custom Events based on a custom pulse meter (heat energy) are not being detected after the initial event. [183039]

• When the Network Mode is set to 2 separate ports, only 1 of the ports may have a static IP. The other port must be either a DHCP server or DHCP client. [182046]

• Disabling DSP does not disable publication. Publication attempts will continue if DSP is disabled while publication is enabled. [189071]

• EM6400 and EM6438 meters with firmware versions earlier than v03.05.03 are not supported. [187426]

• EM4300 devices created in version 3.0.7 and earlier will not disconnect from the ZigBee network when deleted after upgrading to version 3.5.24. The EM4300 will need to be manually set to its pairing mode after it is deleted. Delete the EM4300 before the upgrade if the EM4300 must be removed from the configuration. [191111]

• Predefined events for MasterPact, PowerPact, and ComPact NSX breakers will only be detected when connected serially to the Com’X or IFE. They will not be detected if connected via ULP to the IFE. [195285]

• The default Count Unit given for a selected Count Element must be used when creating a pulse meter. The pulse measurement and flow will be incorrect if the default is not used. [180265]

• Predefined frames of custom models based on Schneider models are not editable, and are not always displayed. [176413]