Performance and Limitations

Performance

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

• The number of individual alarms that can be selected for publication is limited to 500. Among the 500 alarms, a maximum of 300 can be from Modbus-SL devices.

  For more information about Calculation of Valid Configurations for Data Measurements, refer to DOCA0172•• EcoStruxure Panel Server - User Guide.

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

• Keep firmware up to date in order to allow the Schneider Electric Customer Care Center to remotely access the Panel Server webpages.

  Remote access certificates for each firmware version are valid up to the dates indicated in the table.

  Panel Server firmware version	Remote access certificate validity date
  002.006.001	10 January 2027
  002.006.000	10 January 2027
  002.005.000	08 October 2026
  002.004.000	10 August 2026
  002.003.000	07 May 2026

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

General Limitations

• For any data conversion to INT64 using logic codes, the largest number that can be accurately represented is 9007199254740991. Any number larger than this will be invalid.

• Web browser Mozilla Firefox not supported.

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

Limitations on Wi-Fi Communication

Limitations on Publication

• For legacy Smartlink devices and embedded input devices, configured as Pulse counter, when publication is to Schneider Electric cloud, non-standard units can be misinterpreted, and misleading values are published. To avoid this issue, in the webpages configure the pulse counter unit using standard (SI) units (for example, Wh) and use the pulse weight to convert to the desired unit (for example kWh). For more information, refer to the section Pulse Digital Input Parameters in DOCA0172•• EcoStruxure Panel Server - User Guide

• When SFTP or HTTPS publication is enabled, alarms are displayed in the Panel Server webpages but are not published on SFTP or HTTPS servers.

• 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.

Limitation on Parent/Child Gateway Configuration

• The parent Panel Server is unable to display and manage the measurements values of the digital inputs configured on the child Panel Server gateway. It is recommended to replace the child Panel Server with an I/O Smart Link device to enable the inputs and outputs of the channels configured in the I/O Smart Link to be correctly displayed in the Panel Server webpages and published to any associated Cloud application.

• 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 and Home webpages and published to the upstream application.

  NOTE: In EcoStruxure Energy Hub (EEH) the combined data Active energy delivered + received is not displayed.

• 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.

• 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.

Limitations on Custom Device Models

• Due to updated format of custom device models, models created before October 2025 cannot be imported into Panel Server from EPC Web tool. The updated format for custom device models is compatible with Panel Server firmware version 002.004.000 or later. Refer to the Custom Model Compatibility table in DOCA0172•• EcoStruxure Panel Server - User Guide.

  For information about creating and modifying custom device models in EPC Web tool, refer to EPC Web.

• Existing current and available versions of models in Panel Server are indicated with a deprecated format icon in the custom device models table in the Panel Server webpages. They continue to be supported.

• Switching between versions in Panel Server webpages depends on the format of the current and available versions, as indicated in the following table:

  Current version	Available version	Can be switched?
  Deprecated format	Deprecated format	Yes
  Deprecated format	Updated format	Yes
  Updated format	Deprecated format	No
  Updated format	Updated format	Yes

  For a detailed explanation of supported custom device models and associated actions, refer to Custom Models for Downstream Modbus Devices in DOCA0172•• EcoStruxure Panel Server - User Guide.

• Backward compatibility with existing custom models after a firmware update:

  1. After updating the Panel Server firmware, if devices associated with a custom model display erroneous data or the custom model can no longer be imported to webpages, update and regenerate the custom model using EPC Web.

  2. Import the custom model again into the Panel Server.

  3. Perform a Switch versions and update action for the custom model.

• Publishing device identification dynamically: Panel Server retrieves identification data for devices dynamically from the device, with the following exceptions:

  • User application name

  • Device family

  The following static values in custom device models are not supported by Panel Server:

  • Hardware revision

  • Software revision

• Units defined in custom measurement are not published to the Cloud.

• 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. Associate the devices with the newly loaded custom model.

  4. 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.

Limitations on Data Sampling and Alarming

• Alarms are not published for devices that have Disconnected status at the moment that the remote configuration is received by the Panel Server after publishing a topology.

  Check that all devices are connected before publishing a topology.

• After modifying the data sampling configuration of a device, the following Panel Server webpages are frozen and not available while the changes are being applied:

  • Data management

  • Backup & restore

  • Custom models

Limitations on Modbus Devices

• 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.

• Limitations on Acti9 Smartlink Modbus devices:

  • For legacy Acti9 Smartlink Modbus devices, when Panel Server is unable to read the hardware version due to non-standard UTF-8 characters, a replacement character (�) is displayed at Identification > Hardware revision in the webpages. Previously the non-standard characters were not decoded and No data was displayed.

• Limitations on I/O Smart Link devices:

  • When commissioning an I/O Smart Link (as a replacement for a legacy Acti9 Smartlink Modbus with firmware version 001.003.00X) in EcoStruxure Power Commission software, leaving None in the Signal Element line causes an error when the device is commissioned in the Panel Server. The I/O Smart Link commissioning configuration cannot be saved in the Panel Server.

  • I/O Smart Link devices support the following special characters:

    ASCII	1	2	4	5	6	7	8	11	12	13	14	15	30	32	33	61	63	64	93	95
    Character	space	!	#	$	%	&	‘	*	+	,	-	.	=	?	@	\	^	_	|	~

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

• Limitations on MasterPacT NT/NW, ComPacT NS, and PowerPacT P/R frame circuit breakers. For details about which trip units and interfaces are supported, refer to:

  • Modbus TCP/IP Devices Circuit Breakers and Associated Trip Units connected via IFE and EIFE interfaces

  • Modbus Serial Devices Circuit Breakers and Associated Trip Units connected via IFM interface or BSCM Modbus SL/ULP module

Limitations on Wireless Devices

• For ZBRT pushbutton devices, communication with buttons is lost when the Panel Server changes from one channel to another. Decommission the ZBRT device (refer to the ZBRZ commissioning module instruction sheet NNZ21729) and discover the ZBRT devices again to re-establish communication.

• For Exiway Link devices, light status value (ON, OFF) is relevant only when the device is not in emergency mode.

Limitations on Input Devices Configured as Pulse Counter

Depending on the language of your browser, when entering a value in the Pulse weight field, to add a decimal value (for example 1.5), you may need to copy and paste the value into the field. An error message may pop up to indicate that the value is not valid but the value is used for the calculation of consumption and flow.