The 2.5.16 and 2.6.9 releases are provided for device recovery. That is, recovering a RAVE 
device from a persistent bug or error condition or an ESD event that may have resulted in a 
partially erased flash component (see reference below).

Optionally, a customer may want to identify their AES/EBU RAVEs properly 
with 2.5.16 firmware installed. The only application here is proper visibility within
the CobraNet Discovery GUI. Version 2.5.16 was shipping in RAVE prior to a public release 
of CobraNet Discovery. Therfore, early versions of the firmware indicate analog models only. 
This can be corrected by reprogramming all AES/EBU RAVE units with the proper 2.5.16 file type.
2.5.16 is now posted with correct model reporting. Of course, 2.6.9 and 2.8.5 shipped with all
models indicate the proper version and device. 


				**** IMPORTANT ****

In order to upload code via CobraNet Discovery, a RAVE must have firmware that supports
2.5.16 or later. In other words, the RAVE must already be loaded with version 2.5.16 or 
greater. It should be noted that there have been reported failures when reprogramming 
RAVEs from newer firmware versions to older releases. Example: from 2.6.x to 2.5.x or from
2.8.x to 2.6.x. Versions 2.5.16 and 2.6.9 should not be used as a backward code fix... 
QSC has qualified solid releases for product upgrades. The current upgrade path is via
version 2.8.5. 

			**** SOME NOTES ON RECOVERY ****

Obviously, device recovery options may be limited at the installation site. TFTP upgrades 
require that a working version of code exist in the unit due to the TFTP server residing  
in the code image. On very rare occassions an intermittent error may surface as a result 
of an ESD event. RAVE has protective circuitry at all external connection points. However, 
some wiring and grounding scenarios may place computing and/or network devices at risk. 
An ESD event encountered during runtime will usually affect the temporary memory devices 
and the RAVE product will enter a failure mode. In this case, recovery will likely not be 
possible through TFTP methods. However, an ESD event that partially affects the permanent 
memory device may possibly be recovered through TFTP means. An intermittent error that is 
surfaced as a result of a runtime failure or a failed code upgrade may also be recovered 
through TFTP means via a code reload.
 
 	**  It is important that a RAVE not be power-cycled if a fatal error condition is 
	    suspected with code residing in permanent memory.
 
If a faulty RAVE is power-cycled the unit may lose the ability to recall TFTP functions.
If a reload of code is possible, wait until the Discovery application verifies a successful
download before power-cycling the RAVE. 

Some sites may wish to keep backup flash memory devices on hand. These devices may be purchased 
from QSC Technical Services. Ideally, the backup flash will be a duplicate of the original and
include the physical address (MAC address) of the target RAVE. If this is not possible, a 
generic backup flash may be used temporarily. However, the generic image will have a default 
MAC address. The default MAC address limits its use to one generic flash per LAN (network segment).

A backup flash (preferrably with an original MAC address) may have older code if the network
has been recently upgraded. These units can then be updated (via TFTP) to the required version.