Release Notes:

Bug Fixes and Improvements:

1. HDMI audio status not updating when audio source is not present
   
2. USB HID interface incompatibility with TSI touch screen
3. Video tearing in Genlock mode
   
4. Intermittent DHCP discovery and request packets with Auto-IP source
   
5. Mouse connected via USB HID cannot wake up remote PC when in sleep mode
   
6. USB HID incompatible with keyboards that have embedded Smart Card readers
   
7. Added Fujitsu Smart Reader keyboard support with USB HID interface
   
8. Analog audio drops when set to 4K60 video resolution
   
9. Switching from Genlock to Fast Switch may induce a black screen
   
10. Video and USB HID loss due to mouse movements induced after a long period of time
    

New Features:

1. Multicast Hello packets: previous firmware and API release only use broadcast Hello packets
   which require an IP helper in large multi-switch networks. SDVoE systems can now be
   configured to use only multicast Hello packets. For backwards compatibility, broadcast Hello
   packets can be optionally supported.

1. Initial Production FPGA firmware release.
   

Update Procedure:

RX FPGA Upgrade Process:

1. On the TCVRs, there is a dip switch to set the operational mode to Encoder of Decoder. Ensure the dip switch is set to Decoder for all TCVRs. Ensure there are no TCVRs in the system set to Encoder.
   
2. Connect the TCVR(s) SDVoE port (SFP cage or RJ45 port) to the MXNet or AV over IP switch via fiber or category cable. If fiber cable will be used to connect the TCVR(s) to the switch, slide the SDVoE dip switch towards the SFP cage. If a category cable will be used to connect the TCVR(s) to the switch, slide the SDVoE dip switch towards the RJ45 port.
   
3. Ensure the TCVR(s) are powered and remain powered through the upgrade process. The three viable options are detailed below:
   
1. PoE via SDVoE RJ45 port - If the TCVR(s) SDVoE port will be connected to an MXNet or AV over IP switch utilizing a category cable, then the TCVR(s) will power up via PoE. If the TCVR(s) SDVoE port will be connected to an MXNet or AV over IP switch utilizing a fiber cable, then the TCVR(s) will need a category cable to be powered via PoE. Slide the PoE dip switch towards 10G and insert a category cable into the SDVoE RJ45 port. A PSU24 can be utilized for PoE for this use case.
   
2. PoE via 1G Extension Port - As mentioned above, if the TCVR(s) SDVoE port will be connected to an MXNet or AV over IP switch utilizing a fiber cable, then the TCVR(s) will need a category cable to be powered via PoE. An alternate option for PoE on the TCVR(s) is to use the 1G extension port. Slide the PoE dip switch towards 1G and insert a category cable into the 1G Extension port. A PSU24 can be utilized for PoE for this use case.
   
3. Local Power via 12V adapter: If the TCVR(s) SDVoE port will be connected to an MXNet or AV over IP switch utilizing a fiber cable, then local power can be used instead of PoE. Connect the provided 12V adapter into a standard US power socket and screw in the locking mechanism on the TCVR(s) to ensure continuous power throughout the upgrade process.
   
4. Connect the CBOX SDVoE SFP cage to the MXNet or AV over IP switch via fiber or category cable.
   
5. Ensure the CBOX is powered and remains powered through the upgrade process. The two viable options are detailed below:
   
1. Port 6 (PoE) - Insert a category cable into Port 6 (PoE) from a PSU24 or any other PoE supported switch. Do not connect this port to your MXNet or AV over IP switch that will be utilized for AV distribution.
   
2. Local Power via 12V adapter: Connect the provided 12V adapter into a standard US power socket and screw in the locking mechanism on the CBOX to ensure continuous power throughout the upgrade process.
   
6. Once the TCVR(s) and CBOX have booted up, verify that the CBOX can see the TCVR(s) presence on the CBOX. This can be confirmed by verifying the number of decoders reported on the SDVoE Info OLED. The OLED should report Online RX: X (X = number of decoders).
   
7. Connect a category cable from your local management network switch to any available port on the back of the CBOX or connect directly into a PC or laptop
8. If connecting to your local management network, ensure your laptop is connected to your local network and that the CBOX is reporting a valid IP address. The CBOX IP address can be found on the CBOX Status OLED.
   
9. If connecting to the CBOX from a PC or laptop, you will need to set up your device to communicate with the CBOX.
   
1. Navigate to the Control Panel on your Windows PC and select the View network status and tasks under the Network and Internet heading.
   
   
   
2. Click on the Change adapter settings in the left panel of the window.
   
3. In the Network Connections window, double click on the Ethernet port that will be used to access the switch. In the example below, Ethernet 2 was the port connected to the switch.
   
4. At the bottom of the Ethernet status menu click on the Properties button.
   
   
   
5. Under the “This connection uses the following items:” list heading, double click on Internet Protocol Version 4 (TCP/IPv4)
   
   
   
6. Click on the Use the following IP address radio button and change the IP address of your PC to an IP address within the subnet of your CBOX. When finished entering the parameters, click on OK. In this example, the CBOX IP address was 192.168.2.110, so the PC IP address was set to 192.168.2.2 with a /24 subnet.
   
   
10. Open Mentor by entering the IP Address of the CBOX into your web browser. You should see the following SYSTEM UTILITIES page:
    
11. Navigate to the MXNET DECODERS (RX) UPDATES section and click the checkbox for FPGA.  Upload the RX FPGA file. RX Example: 10G-GEN2-RX-FPGA-2.1.0.0-web(0B5F) 2.apz. Click on the SELECT DECODERS button and select the radio button for all TCVRs in the system.
    
12. The upgrade process will begin. Do no disconnect any device in the system during the upgrade process. Once the process has completed, the RX FPGA upgrade is complete.