Firmware Version 001.002.000

New Features

• Addition of supported devices:

  • HeatTag sensors

  • Wireless indication auxiliaries for ComPacT and PowerPacT circuit breakers

  • PowerLogic Tag 2P energy sensors

  • Wireless CO₂ sensors

  • Wireless temperature and humidity sensors

  • PowerTag A (EwSenseTemp) sensor

  • PowerTag Ambient wireless temperature sensors

• Addition of separated network topology

• Addition of Modbus TCP/IP client protocol

• Addition of digital inputs to monitor the state of external contacts or as pulse counter

• Addition of EcoStruxure Panel Server webpages for monitoring

• Enhancement of typical response time to Modbus/TCP IP request for a wireless IEEE 802.15.4 device

• Enhancement of maximum response time to Modbus/TCP IP request for a wireless IEEE 802.15.4 device

Known Issues

• The separated mode is configured to segregate downstream Modbus TCP/IP devices connected on ETH1 port from upstream communication systems connected on ETH2 port. With the current firmware version, it is only possible to access the downstream Modbus TCP/IP devices data from the EcoStruxure Panel Server embedded webpages. A monitoring software connected on ETH1 port using Modbus TCP/IP will not be able to access the Modbus TCP/IP devices connected on ETH2 port. For such applications, use only the switched mode.

• When an active alarm is present (as reported in the Modbus register) for a PowerTag Energy M250/M630 for ComPacT NSX 3-pole circuit breaker, a PowerTag Energy F160, a PowerTag Rope, or a PowerLogic Tag Rope (see commercial references in the table below), the alarm is still active although the value of the ENVT (External Neutral Voltage Tap) setting is changed by using the EcoStruxure Panel Server webpages or EcoStruxure Power Commission software.

  To work around this issue, restart the EcoStruxure Panel Server Universal (see DOCA0172EN EcoStruxure Panel Server - User Guide for detailed procedure).

  The alarm for phase-to-neutral voltage protection is one of the following:

  • 80% Undervoltage on phase-to-neutral

  • 120% Overvoltage on phase-to-neutral

  The following table lists the devices concerned by the issue:

  Devices	Commercial reference
  PowerTag M250 3P 250A	LV434020
  PowerTag M250 3P+N 250A	LV434021
  PowerTag M630 3P 630A	LV434022
  PowerTag M630 3P+N 630A	LV434023
  PowerTag F160 3P/3P+N	A9MEM1580
  PowerTag Rope 200 A 3P/3P+N	A9MEM1590
  PowerTag Rope 600 A 3P/3P+N	A9MEM1591
  PowerTag Rope 1000 A 3P/3P+N	A9MEM1592
  PowerTag Rope 2000 A 3P/3P+N	A9MEM1593
  PowerLogic Tag Rope 120A 3P	PLTR1203P
  PowerLogic Tag Rope 600A 3P	PLTR6003P
  PowerLogic Tag Rope 1000A 3P	PLTR10003P
  PowerLogic Tag Rope 2000A 3P	PLTR20003P

• When an active alarm is present (as reported in the Modbus register) for a PowerTag Energy 1P+N , a PowerLogic Tag 1 P or 2P, or an Acti9 Active iC40 or iC60, the alarm is still active although the value of the Phase Sequence setting is changed by using the EcoStruxure Panel Server webpages or EcoStruxure Power Commission software.

  To work around this issue, restart the EcoStruxure Panel Server Universal (see DOCA0172EN EcoStruxure Panel Server - User Guide for detailed procedure).

  The alarm about phase sequence is one of the following:

  • 80% Undervoltage

  • 120% Overvoltage

  • Overcurrent over 45%, 50%, or 80% of nominal current

  • Load current is 0 A

  The following table lists the devices concerned by the issue:

  Devices	Commercial reference
  PowerTag A9 P63 1P+N Top	A9MEM1560
  PowerTag A9 P63 1P+N Top	A9MEM1561
  PowerTag A9 P63 1P+N Bottom	A9MEM1562
  PowerTag A9 P63 1P+N Bottom RCBO	A9MEM1563
  PowerTag A9 F63 1P+N 110V	A9MEM1564
  PowerLogic Tag QO 10-30A 1P+N	PLTQO301P
  PowerLogic Tag QO 35-60A 1P+N	PLTQO601P
  PowerLogic Tag E-Frame 10-60A 1P+N	PLTE601P
  PowerLogic Tag QO 10-30A 2P	PLTQO302P
  PowerLogic Tag QO 35-60A 2P	PLTQO602P
  PowerLogic Tag E-Frame 10-60A 2P	PLTE602P
  Acti9 Active iC40 and iC60	A9TAA●●●●, A9TAB●●●●, A9TDEC●●●, A9TDFC●●●, A9TDFD●●●, A9TPDD●●●, A9TPED●●●, A9TYAE●●●, A9TYBE●●●

• On systems with both Modbus devices and wireless devices, the table view of measurements may display in some rare cases the same measurements value for the wireless devices as for the Modbus device as shown below:

  This issue is only within this page and does not affect the measurements reported on the Modbus register to the upstream system nor the measurements reported in the single device webpage.

  This issue does not affect systems with only wireless devices or only Modbus devices.

  Follow this procedure to resolve the issue:

  • For systems with more wireless devices than Modbus devices (for example, 10 wireless devices and 5 Modbus devices):

  1. Remove all devices from the project.

  2. Add all Modbus devices.

  3. Add all wireless devices.

  4. Remove the wireless devices only again.

  5. Add all the wireless devices again.

  • For systems with more Modbus devices than wireless devices (for example, 10 Modbus devices and 5 wireless devices):

  1. Remove all devices from the project.

  2. Add all wireless devices.

  3. Add all Modbus devices.

  4. Remove the Modbus devices only again.

  5. Add all the Modbus devices.

  • For systems with same number of Modbus devices as wireless devices (for example, 5 Modbus devices and 5 wireless devices):

  1. Remove all devices from the project.

  2. Add all wireless devices.

  3. Add all Modbus devices.

  4. Remove the Modbus devices only again.

  5. Add all the Modbus devices.

Features

Performances and Limitations

• The typical response time to Modbus/TCP IP request for a wireless IEEE 802.15.4 device is 30 ms.

• The maximum response time to Modbus/TCP IP request for a wireless IEEE 802.15.4 device is 1 s, set-up Modbus/TCP client time-out accordingly.

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

• The maximum number of Modbus/TCP concurrent connections is 32.