NXR-ZGW NetLinx ZigBee Pro Gateway Firmware v3.01.13

Last Updated: 10月02日

NXR-ZGW
NXR-ZGW-PRO

NOTES:

  1. For the proper operation of all devices, it is recommended that all devices be brought up to the most current firmware version.

Loading procedures for v3.01.13:

  • When upgrading from any version less than v3.00.00:
    1. Upgrade to v3.00.00 first (example: v1.01.13 -> v3.00.00)
    2. The upgrade from v3.00.00 to v3.01.11 will require two loads of the file SW5791_01A_NXR_ZGW_v3_01_12.kit. The first load will fail after the third file is transferred with the NetLinx error message "Transfer Aborted - Unsupported file type." After getting this error message, reboot the gateway and verify that the NetLinx OnLine Tree shows v3.01.12 for the version on the gateway. Transfer file SW5791_01A_NXR_ZGW_v3_01_12.kit to the gateway a second time with the "Reboot Device" box checked in NetLinx. This time the entire kit file will transfer. After the gateway reboots, it will download the firmware to the radio. This will take approximately two minutes.
    3. Load SW5795_92_ZIGBEE_END_DEVICE_v3_01_05.kit -- a gateway reboot IS NOT necessary after sending this file.
    4. Load SW5791_07_ZIGBEE_REPEATER_v3_01_05.kit -- a gateway reboot IS NOT necessary after sending this file.
  • When upgrading from v3.00.00:
    1. The upgrade from v3.00.00 to v3.01.12 will require two loads of the file SW5791_01A_NXR_ZGW_v3_01_12.kit. The first load will fail after the third file is transferred with the NetLinx error message "Transfer Aborted - Unsupported file type." After getting this error message, reboot the gateway and verify that the NetLinx OnLine Tree shows v3.01.11 for the version on the gateway. Transfer file SW5791_01A_NXR_ZGW_v3_01_11.kit to the gateway a second time with the "Reboot Device" box checked in NetLinx. This time the entire kit file will transfer. After the gateway reboots, it will download the firmware to the radio. This will take approximately two minutes.
    2. Load SW5795_92_ZIGBEE_END_DEVICE_v3_01_05.kit -- a gateway reboot IS NOT necessary after sending this file.
    3. Load SW5791_07_ZIGBEE_REPEATER_v3_01_05.kit -- a gateway reboot IS NOT necessary after sending this file.
  • When upgrading from v3.01.07:
    1. Transfer the file SW5791_01A_NXR_ZGW_v3_01_12.kit to the gateway via NetLinx with the "Reboot Device" box checked in NetLinx. It is not necessary to reload SW5795_92_ZIGBEE_END_DEVICE_v3_01_05.kit or SW5791_07_ZIGBEE_REPEATER_v3_01_05.kit since these files have not changed in this release.
    2. Recommission all devices on the network.

 

CHANGES in this Release:

  • Fixed a bug where time update from the master could cause all devices to drop offline for a few seconds
  • Fixed a bug with using device number 0

 

Known Issues:

  • On systems that have one gateway and no repeaters, the remotes can become inoperable under extreme amounts of traffic (for example, 30 messages every two seconds to each of six remotes). Rebooting these devices will bring them back online.
  • The gateway does not currently support NDP mode for master connections.
  • In high traffic situations remotes can appear on the gateway commissioning page, even though they are commissioned. This has no impact on the actual operation of the remotes.
  • In some cases, the R3 power source will show as "Unknown" on the gateway web pages when the R3 is in its cradle. This issue does not impact the functionality of the remote or the gateway.

 

Hot Fix For NXR-ZGW NetLinx ZigBee Pro Gateway (v.3.01.17 Available from AMX Technical Support)

1. For the proper operation of all devices, it is recommended that all devices be brought up to the most current firmware version.

2. Loading procedures for v3.01.17:

When upgrading from any version less than v3.00.00:

  1. Upgrade to v3.00.00 first (example: v1.01.20 -> v3.00.00)
  2. The upgrade from v3.00.00 to v3.01.16 will require two loads of the file SW5791_01A_NXR_ZGW_v3_01_16.kit. The first load will fail after the third file is transferred with the NetLinx error message "Transfer Aborted - Unsupported file type." After getting this error message, reboot the gateway and verify that the NetLinx OnLine Tree shows v3.01.12 for the version on the gateway. Transfer file SW5791_01A_NXR_ZGW_v3_01_16.kit to the gateway a second time with the "Reboot Device" box checked in NetLinx. This time the entire kit file will transfer. After the gateway reboots, it will download the firmware to the radio. This will take approximately two minutes.
  3. Load SW5795_92_ZIGBEE_END_DEVICE_v3_01_05.kit -- a gateway reboot IS NOT necessary after sending this file.
  4. Load SW5791_07_ZIGBEE_REPEATER_v3_01_05.kit -- a gateway reboot IS NOT necessary after sending this file.

 

When upgrading from v3.00.00:

  1. The upgrade from v3.00.00 to v3.01.16 will require two loads of the file SW5791_01A_NXR_ZGW_v3_01_16.kit. The first load will fail after the third file is transferred with the NetLinx error message "Transfer Aborted - Unsupported file type." After getting this error message, reboot the gateway and verify that the NetLinx OnLine Tree shows v3.01.16 for the version on the gateway. Transfer file SW5791_01A_NXR_ZGW_v3_01_16.kit to the gateway a second time with the "Reboot Device" box checked in NetLinx. This time the entire kit file will transfer. After the gateway reboots, it will download the firmware to the radio. This will take approximately two minutes.
  2. Load SW5795_92_ZIGBEE_END_DEVICE_v3_01_05.kit -- a gateway reboot IS NOT necessary after sending this file.
  3. Load SW5791_07_ZIGBEE_REPEATER_v3_01_05.kit -- a gateway reboot IS NOT necessary after sending this file.

 

When upgrading from v3.01.07:

  1. Transfer the file SW5791_01A_NXR_ZGW_v3_01_16.kit to the gateway via NetLinx with the "Reboot Device" box checked in NetLinx.

    It is not necessary to reload SW5795_92_ZIGBEE_END_DEVICE_v3_01_05.kit or SW5791_07_ZIGBEE_REPEATER_v3_01_05.kit since these files have not changed in this release.
  2. Recommission all devices on the network.

 

Prerequisites:

  • NXR-ZGW firmware v3.00.00
  • Zigbee Coordinator firmware v3.00.00
  • NXR-ZRP firmware v3.00.00
  • R4 ZigBee module firmware v3.00.00

 

CHANGES in this Release:

  • Fixes the "auto-release" bug by sending correct system number information
  • Includes zero-config fix
  • Icsp may now use ports other than 1319
  • Includes two new features
    1. May send Netlinx command to Gateway to turn Gateway to "Joinable"
      -- send_command <device>, 'Join'
    2. May send Netlinx command to Gateway to make a connect R4 bind to a different Gateway (must make other gateway joinable with previous command or go on website and click joinable)
      -- send_command <device>, 'Bind, <R4 mac address>, <new gateway extPanId>, [optional]<AESkey>'
      -- ex) send_command 11383, 'Bind, 00:0d:6f:00:00:c6:11:d7, AZG70010' //no password
      -- ex) send_command 11383, 'Bind, 00:0d:6f:00:00:c6:11:d7, AZG70010, aa:c9:9a:cb:61:ca:70:e7:13:df:ee:6f:d6:42:59:86'

 

KNOWN ISSUES:

  • On systems that have one gateway and no repeaters, the remotes can become inoperable under extreme amounts of traffic (for example, 30 messages every two seconds to each of six remotes). Rebooting these devices will bring them back online.
  • Setting the gateway device number to 0 can cause it to not be correctly recognized by the master on master firmware releases less than v3.50.430.
  • The gateway does not currently support NDP mode for master connections.
  • In high traffic situations remotes can appear on the gateway commissioning page, even though they are commissioned. This has no impact on the actual operation of the remotes.
  • In some cases, the R3 power source will show as "Unknown" on the gateway web pages when the R3 is in its cradle. This issue does not impact the functionality of the remote or the gateway.
  • If using an ICSP port other than 1319, downgrading to firmware versions prior to 3.01.17 can cause the gateway to be unable to connect until it is reset to defaults. Setting the port to 1319 prior do downgrading the firmware avoids this issue.