Product Name: UDM-0808-SIG
FG#: FG1402-01
Firmware Version: v0.70
Device ID: $153

Release Date: 11/20/2009

----------------------------------------------------------
1. Prerequisites
----------------------------------------------------------
  - UDM-RX02N firmware v 1.46
   When downloading kit files from NetLinx Studio:
   - Within the "Send to NetLinx Device" dialog box please check the "Reboot
     Device" check box before proceeding with a KIT file download to UDM 
     devices.

Upgrading from v0.55 to v0.70:

   Files Required:
   SW1402_ONE_v0.6x.kit         - must be applied to a version 0.55 hub first
   SW1402_KIT_TRANSITION.kit 	- must be applied to a hub that has had the SW1402_ONE_v0.6x applied
   SW1402_KIT_v0_70.kit         - complete KIT for this build of UDM-0808
 
   WARNING:  DO NOT perform steps 1,2,3 out of order, that may cause unit to become 
             unresponsive and require service. 

   - Step 1: Download SW1402_ONE_v0_6x.kit.
     After reboot the UDM should be ready for next transfer after ~1:30. 
     Version will show as 0.60 in the Netlinx Studio Online Tree. 
   - Step 2: Download SW1402_KIT_TRANSITION.kit.
     After reboot the UDM should be ready for next transfer after ~1:30. 
     Version will show as 0.60 in the Netlinx Studio Online Tree. 
   - Step 3: Download SW1402_KIT_v0_70.kit.
     After reboot the the UDM controller transfers various files to the 
     hub components, this will take ~12 minutes. 
     ~35 to 45 seconds after reboot, telnet into the UDM-0808-SIG to 
     monitor the firmware transfer progress. 
     To turn on diagnositic messages, type:
     MSG ON<enter>
     The last item transferred will show as:
        (0000708830) UDM-0808 - firmware update (FWID 217) on device 9
        (0000714354) UDM-0808 - 1024 of 1072
     The hub will be reboot itself after the final transfer completes.

   WARNING:  DO NOT attempt to transfer the SW1402_ONE_v0_6x.kit to the UDM Hub after 
	     it has been upgraded to v0.68 or higher, that may cause unit to become 
             unresponsive and require service. 


Upgrading from v0.68 or higher to v0.70:

Files Required:
   SW1402_KIT_v0_70.kit         - complete KIT for this build of UDM-0808

   - Download SW1402_KIT_v0_70.kit.
     After reboot the the UDM controller transfers various files to the 
     hub components, this will take ~12 minutes. 
     ~35 to 45 seconds after reboot, telnet into the UDM-0808-SIG to 
     monitor the firmware transfer progress. 
     To turn on diagnositic messages, type:
     MSG ON<enter>
     The last item transferred will show as:
        (0000708830) UDM-0808 - firmware update (FWID 217) on device 9
        (0000714354) UDM-0808 - 1024 of 1072
     The hub will be reboot itself after the final transfer completes.


----------------------------------------------------------
2. Firmware Revision History
----------------------------------------------------------

  - Hub now shows Master/Client status via Online Tree in NetLinx Studio, 
    Show Device and Show System in terminal, and DEVICE_INFO() in code.
  - Other IR Modes added:
    RPRC05 (same functionality as RPAMX)
    RPRC02 (same functionality as RPENDELEO)
    RPMIOR1 (previously undocumented)

    RPAMX and RPENDELEO are still supported, but are somewhat confusing because 
    of the labelling on the remotes. 
    RPMIOR1 maps the MIO SNAPI channels to endeleo remote channels for compatibility 
    with other endeleo remotes
  - Added support for receive of all 255 AMX IR codes by the RXO2N.
    This is enabled via the new 'MIO' receive mode set via the 'RP' command.
 	Example:
	SEND_COMMAND dvRX, "'RPMIO'"
	Configures the Rx to use the standard AMX IR codes.
 
    Note: Avoid using toggling functions when using the RX as an IR receiver. 
    Due to limitions in the RX communications, holding a button results in 
    multiple pushes and releases instead of a push/hold/release.
  
  - Improved RX02N detection and online handling.
  - Serial handling (RS232 from and to RX02Ns) has been much improved.
    Notably, fixed RS232 transmit strings losing characters if they started 
    with "$02" and ended with "$03".
  - UDM-0808 can now connect to masters with ICSP security enabled. 
  - Firmware IDs corrected and updated.
  - Added EDID support. The VGA input ports now provide a default EDID to the
    attached host, currently using the same EDID as the TPI-PRO.
  - UDM-0808 commands added:
    ?C - return connections for audio and video
    ?V - return video connections
    ?A - return audio connections
    ?MM - show master mode status
    ?RPU - show 'restore on power up' flag status
    RESETFACTORY - resets compensation, input types, and web page settings to factory defaults

  - Restore on power up is now the default (RPUON)

  - A web page has been added which provides a rudimentary control method if
    there is no master connection. The web page is labeled 'Control' on the 
    Admin tab of the web pages and allows commands to be directly entered and
    replies (notifications) to be displayed for the UDM-0808 hub and RX02Ns.
    	Use Accept button to send commands.
    	Use Refresh button to get new replies. 
    	New replies are added to the bottom of the list.
    	Use Clear button to clear replies.

  - Fixed ipSettings.xml web page will not load if network has no domain 
    suffix.
  - Fixed audio loss problem on port 1


----------------------------------------------------------
3. Known Issues 
----------------------------------------------------------
  - If firmware transfer hangs on device 1 for more than a minute or two,
    reboot the UDM-0808. Transfer will resume after reboot. 
  
  - Sending the SW1402_ONE_v0_6x.kit or original SW1402_KIT_v0_55.kit to 
    a v0.68 or higher hub may cause the unit to become unresponsive and 
    require service. 
  - Do not mix old firmware RX02Ns with new firware 0808s, or vice versa.
    This will result in poor communication between the RX and the hub.
    Update the RX02Ns to match the 0808 to which they are connected. 
  - ICSP password may have to be reentered if 0808 reboots.
  - there are some problems with IE 8 browser compatibility - use IE7 compatibility
    with this browser
  - Audio pop and noise when doing FW upgrade.
  - Audio "pops" with control when Digital Audio is used
  - Brighness, Sharpness, and Skew levels don't update when updated via 
    their respective commands.

----------------------------------------------------------
4. Programming Information
----------------------------------------------------------    
 
Commands:

“’?CO<O#>’”

Returns connection status for video outputs in the hub

Syntax:
	SEND_COMMAND <DEV>, “’?C<O#>’”

Variables:
O# = output port number:
1-8 = Outputs 1-8 – a value of 0 or “ALL” means all outputs


Example 1:
SEND_COMMAND dvUDM,”’?C’”
Returns which video inputs are connected for all outputs

Example 2:
SEND_COMMAND dvUDM,”’?C1”
Returns which video input is connected to output 1

The returned commands are of the form

V<O#>-I<I#>
A<O#>-I<I#>

Where

O# is the queried output port number, and I# is the connected input number (zero if disconnected), for example

V4-I2
A4-I2

Would show that video output 4 was connected to input 2, and
audio output 4 was connected to input 2.


----------------------------------------------------------    
 “’?VO<O#>’”

Returns connection status for video outputs in the hub

Syntax:
	SEND_COMMAND <DEV>, “’?V<O#>’”

Variables:
O# = output port number:
1-8 = Outputs 1-8 – a value of 0 or “ALL” means all outputs


Example 1:
SEND_COMMAND dvUDM,”’?V’”
Returns which video inputs are connected for all outputs

Example 2:
SEND_COMMAND dvUDM,”’?V3,4”
Returns which video input is connected to output 3 and which video input is connected to output 4

The returned command is of the form

V#-II#

Where

O# is the queried output port number, and I# is the connected input number (zero if disconnected), for example

V6-I3

Would show  that output 6 was connected to input 3

----------------------------------------------------------    
“’?AO<O#>’”

Returns connection status for audio outputs in the hub

Syntax:
	SEND_COMMAND <DEV>, “’?A<O#>’”

Variables:
O# = output port number:
1-8 = Outputs 1-8 – a value of 0 or “ALL” means all outputs


Example 1:
SEND_COMMAND dvUDM,”’?A’”
Returns which audio inputs are connected for all outputs

Example 2:
SEND_COMMAND dvUDM,”’?A1”
Returns which audio input is connected to output 1

The returned command is of the form

AO#-II#

Where

O# is the queried output port number, and I# is the connected input number (zero if disconnected)

----------------------------------------------------------    
“’RESETFACTORY’”

Resets values to factory defaults

Syntax:
	SEND_COMMAND <DEV>, “’RESETFACTORY’”
Example:
SEND_COMMAND dvUDM, “’RESETFACTORY’”
Resets the hub to factory defaults, currently these are


All video inputs set to type VGA - LOCAL
All audio inputs set to type ANALOG - LOCAL
All connections reset
RPU set to ON
All RX compensation values set to default (SD0):
- Brightness 48
- Sharpness 0
- Red Skew 0
- Green Skew 0
- Blue Skew 0
IR Remote Protocol is set to RPAMX

After reboot:
All webserver settings are set to default.

----------------------------------------------------------    
“?MM”

Shows whether the hub is set to be a cascade master (MM-ON) or a cascade client (MM-OFF)

Syntax:
	SEND_COMMAND <DEV>,”’?MM’”
Example:
SEND_COMMAND dvUDM,”’?MM’”

----------------------------------------------------------    
“?RPU”

Returns whether RPU is ON (and the hub restores connections and settings internally) or if RPU is OFF (and 
the hub relies on the connected master to restore status and settings)

Syntax:
	SEND_COMMAND <DEV>,”’?RPU’”
Example:
SEND_COMMAND dvUDM,”’?RPU’”





