Last Updated: 10月05日
- When upgrading from any version less than v3.00.00, an upgrade to v3.00.00 must be performed first. Load the SW0148_01B_MIOR4_ZIGBEE_MODULE_v3_00_00.kit file first. If SW0148_01A_MIOR4_v3_00_00.kit is accidentally loaded first, the radio will be unable to communicate with the host processor and cannot be upgraded. In this case, the host processor will have to be downgraded to an older version of the firmware and then upgraded again with the radio being upgraded first. Once the remote is upgraded to v3.00.00, the v3.01.05 firmware may be loaded in any order.
- For the proper operation of all devices, it is recommended that all devices be brought up to the most current firmware version.
- Support has been added for the NetLinx command DEVICE_WAKE. This command requests that a device in standby state wake up. If the device is in standby state, it will transition to awake, generating an asynchronous AWAKE DATA_EVENT. Due to the nature of the STANDBY state, the R4 in STANDBY syncs with the gateway at approximately 50 second intervals. The request to wake will not be processed until one of these sync events, so the AWAKE state will appear delayed.
- Telnet interface through the USB port. Open a telnet session, IP address 10.0.0.2, TCP port 23, and type "help" for a list of available commands. This interface may be used to configure the R4 for use in a network using a pre-configured key.
- To set the preconfigured key:
- Start a telnet session with the R4 through the USB port.
- Use the command "set zigbee extended PAN ID [preconfigured key]"
Where: extended PAN ID = Network desired to join (AZGxxxxx)
[preconfigured key] = user supplied key
Example: set zigbee AZG12345 11:22:33:44:55:66:77:88:99:11:22:33:44:55:66:77
- Reboot R4.
CHANGES in this Release:
- Resolved bugs with connectivity (R4/R3s falling offline and never coming back online)
- Added support for the "DEVICE_WAKE" NetLinx command
- Resolved R4 sleep bugs
- Resolved bugs with hard keys becoming disabled after using set up pages
- Added support for the Get Time function
- On systems that have one gateway and no repeaters, the gateway or 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 "show mem" command is not functional on the telnet interface to the R4.
- When two R4 remotes are connected on the same USB bus, downloads will occasionally fail, or units will fail to be recognized.
- Setting the R4 device number to 0 can cause it to not be correctly recognized by the master.