Performance and Limitations

Limitation on SFTP publication - CSV file content not consistent over firmware releases:

• When using the custom I/O contexualization of a Pulse counter device connected to the embedded input of the Panel Server, the format of the CSV files published through SFTP is not consistent with the format seen with firmware version 001.006.000. To see the data label IoCountMeasurement in your CSV scripts, enter IoCountMeasurement in the Consumption meter element name field on the Panel Server web pages at Settings > Embedded input management.

• The above limitation and work-around also apply to a Pulse counter device connected downstream to the I/O Smart Link device.

Limitation on parent/child gateway configuration: In a configuration with Panel Server and PowerTag Link, for Energy devices connected downstream to a child PowerTag Link with parent Panel Server gateway, both Active energy received and Active energy delivered measurements are incorrectly displayed with No data value (NaN) in the Panel Server Monitoring and Control webpage. In addition, these measurements are not published to the upstream application.

As a workaround, view the combined data Active energy delivered + received, which is correctly displayed with accurate values in the Monitoring and Control, Home, and Trending webpages and published to the upstream application.

Limitations on Trending and Home menus:

• During a data dump, in some cases the dashboard does not load due to a timeout. When the data dump process is complete, the dashboard loads.

• When activating publication through Email service for alarms or Schneider cloud services for the first time, you may receive a large number of emails relating to old and existing alarms, especially in the case of long local history. This only occurs once when publication is activated.

• In firmware version 001.007.000, sampled measurements (for example, full-scale voltage phase of carrier input (dbV or dB)) are treated as aggregated data. As a result, an Invalid request message is displayed when viewing data in the Trending webpage. Update to firmware version 001.008.000 or greater to resolve the issue.

• In the Trending menu, some data may be proposed in the filter menu when not applicable. For example, Breaker close count reset and Breaker trip count are displayed erroneously in the data filter menu for devices connected downstream to an I/O Smart Link gateway. Selecting such filters has no impact on the data displayed in trending graphs.

Custom device model: units defined in custom measurement are not published to the Cloud.

Web browser Mozilla Firefox not supported

General performance and limitations:

• No manual addition of wireless devices connected to a child/downstream gateway by using EcoStruxure Power Commission software.

• Automatic discovery of wireless devices under a child gateway is limited to 128 devices because wireless devices are seen as Modbus TCP/IP devices.

• Typical Panel Server latency between Modbus TCP/IP request forwarded to the Modbus serial network is 10 ms.

• Wi-Fi function available through a connection to a Wi-Fi infrastructure only. Access point function not available.

• Some device identification data of the aggregated devices connected downstream from a Smartlink SI B or Smartlink SI D (such as I/O Smart Link or wireless devices) are displayed in the Panel Server webpage if the data is configured and commissioned from the Smartlink SI B or Smartlink SI D webpage.

• Keep firmware up to date in order to allow the Schneider Electric Customer Care Center to remotely access the Panel Server webpages. Remote access certificate validity is as follows:

  • Panel Server Firmware version 001.006.000: certificate valid until 28 January 2024.

  • Panel Server Firmware version 001.007.000: certificate valid until 5 May 2024.

  • Panel Server Firmware version 001.008.000: certificate valid until 23 July 2024

  For more information about Firmware Update, refer to DOCA0172EN EcoStruxure Panel Server - User Guide.

Limitations on logging and alarming:

• The number of individual data points that can be sampled is limited to 5 000 and limited to a flow of 500 data points per minute.

• The number of individual alarms that can be configured for monitoring and sending an email notification is limited to 100.

Limitations on I/O Smart Link:

• Operating time, operation counter, and trip counter not available for Wired devices and Standard I/O.

Limitations on wireless devices:

• Within a parent-child Panel Server gateway configuration, the modification of a contextualized setting of a device to the child Panel Server (for example, auxiliary position modified from SD to SDE) is not automatically reflected in the parent gateway. A manual update in the parent Panel Server is required to display modifications.

• Wireless indication auxiliary: the Panel Server does not manage alarm notification by email or to Schneider Electric cloud applications.

• PowerTag Control:

  • If a PowerTag Control device is connected to a child gateway:

    • No automatic discovery.

    • No data is published to the parent gateway. To be able to publish at the parent gateway level, a custom model has to be developed for the parent gateway.

  • Pairing process to be followed:

    1. Pair the PowerTag Control devices if any in the configuration (all the other wireless devices must be unpowered).

    2. Pair the PowerLogic HeatTag sensors if any in the configuration.

    3. Pair PowerLogic PD100 if any in the configuration.

    4. Pair the other wireless devices.

• PowerTag Display: not supported by Panel Server Advanced.

Limitations on MasterPact NT/NW, ComPacT NS, and PowerPact P/R frame circuit breakers

• MicroLogic 2.0 E. is not supported

• MicroLogic 7.0 E is partially supported.

• MicroLogic 5.0 E and 6.0 E are supported.

• All MicroLogic A, P and H are supported

• Panel Server does not support multiple Modbus/TCP connections to MicroLogic command interface when the MicroLogic is connected under an IFM interface.

Limitations on topology publication to the Schneider Electric cloud: all the devices must be connected at least once to the Panel Server to enable the correct topology to be published to the Schneider Electric cloud.

Limitations on custom model for wireless devices connected under a child gateway: if a custom model uses the same name as a predefined model and devices are already associated with the predefined model, follow this procedure to load the custom model:

1. Decommission any device already associated with the predefined model.

2. Load the custom model in the Panel Server.

3. Reboot the Panel Server.

4. Associate the devices with the newly loaded custom model.

5. Publish the topology in case of use of the Panel Server with a Schneider Electric cloud application such EcoStruxure Asset Advisor or EcoStruxure Resource Advisor.