Current Release Version
| Release 2.2 - May 2016 | The following CRs were resolved in this release: | |
| CR Number | Summary | |
| USB driver upgrade for stability. Failure to decrypt Broadcast packets repaired.The data portion of each decoded HART message is added to the XML output in clear text. Updated to 64-bit capable USB drivers. Updated to Windows .Net Framework 4.5. Problems with thread safety and memory leakage repaired in WiAnalyPacketserver.exe New dual x32 and x64 installation program Allows operation without the WA hearing the network form. This allows WA to be used to analyze logs produced by the System Level Tests. Crashing during batch testing repaired. | ||
| NOTE: If you have WiAnalys 2.X or earlier installed on your computer, use the Control Panel to uninstall the following items *before* installing this release: · Silicon Laboratories USBXpress Development Kit · Silicon Laboratories USBXpress Device (Driver Removal) | ||
Prior Released Versions
| Release 2.0 - August 2011 | HART messages in the decrypted payload are parsed and presented in human-readable format. The display column formerly named Payload is now renamed as Payload Hex. The human-readable text is now located in the Payload column. A specialized DD used to parse the messages is included in the release and is located in the WiAnalys home folder. An xml-encoded version of the log file is produced. Commands to and from the gateway would not decrypt intermittently, now functioning properly. Searching for packets could cause the WiAnalys to crash, repaired. Decoding of the Transport Byte, label “Broadcast” changed to “Broadcast Pipe”. The devices on the network are erased from the Device Network dialog at the beginning of each run. This prevents a rare situation where device information from a previous run is used mistakenly with a different device leads, leading to hard-to-diagnose decryption problems. The network ID and join key are written to the beginning of the .log file at the beginning of each capture. These values are used when the file is later played back. | |
| Release 1.5 - March 2011 | CR Number | Summary |
2207 | Enter a packet number in the text control and click the Goto button to jump to a specific packet. | |
| 2397 | The packet type is displayed in the column SL Ctl in the Security Layer. | |
| 2757, 2759 | Network IDs are translated automatically into upper case. | |
| 2864 | Screen flickering problem resolved. | |
| 2187 | Large files may be captured and played back. Only 1000 packets are retained in the GUI at any one time. A windowing feature allows user to page-up and page-down inside a large file. | |
| 2585 | WriteNetworkKey command with too few data bytes no longer breaks stops decryption. | |
| 2487 | Invalid packets exceptions are handled. | |
2861 | During data capture is was possible for spurious newlines to be interjected in | |
The devices on the network are erased from the Device Network dialog at the beginning of each run. This prevents a rare situation where device information from a previous run is used mistakenly with a different device leads, leading to hard-to-diagnose decryption problems. The network ID and join key are written to the beginning of the .log file at the beginning of each capture. These values are used when the file is later played back. | ||
| Release 1.3 - August 2010 | Minor update | |
| Release 1.1 - March 2009 | Minor update | |
| Release 1.0 - August 2008 | Initial release | |