NX Controller changes in v1.8.120 (hotfix)
IMPORTANT: When upgrading from any version 1.6.x or earlier, you MUST turn security OFF. Security can be reenabled after the upgrade is complete.
Changes in versions from v1.8.108 to v1.8.120
- Fixed NDP devices not connected due to IGMP issue
- Fixed changing IP via ID button holding during run-time
- Fixed SSH_CLIENT_CLOSE command from keeping ssh socket from working again
- security improvements
- Fixed 'v' missing from netlinx studio controller connection
- Fixed dot1x command information
Changes up from 1.8.97 to 1.8.107
- Improved secure NTP usage
- Fixed issue with Dante Mic 2 enabling from Web GUI 1.9.3 DVX2265
- Fixed ?FAN_SPEED in DVX-XXXX-4K units
- 802.1x fixes and updates
- Fix NVRAM usage (timing change), fixes Duet module loading reliability, and persistence in netlinx programs
- Updated WebGUI to properly recognize/report the DxLite Tx or HDBaseT devices on boot
- Improved async messages status so messages are queued until ?CONFIG command response is parsed and sent to WebGUI by websocket
Step 1: Switcher Update
Programming note: Due to a memory allocation change in the DGX MCPU, an “Out of Memory Error" will occur when upgrading from versions prior to 3.8.18. To help prevent this, a separate MCPU only kit has been included in the attached EnovaDGX zip file so it can be sent first prior to the full kit, if needed. See details below.
REMEMBER: The front panel of the DGX will show the update status or this can be monitored via the DGX WebGui System/Devices page by clicking the "Switcher Update Status" button.
- If upgrading from to v3.8.25 from v3.8.13 or later :
- With all I/O cards in the DGX enclosure and the 5002 online, send the EnovaDGX_3.8.25.kit and allow it to fully update the DGX system (MCPU and all I/O cards) per the normal process. This update should take about 30-40 minutes.
- Once the 5002 is back online proceed to the Controller Update and Endpoint Update steps.
- If upgrading to v3.8.25 from ANY version PRIOR to v3.8.13 (including 3.6.30):
- With all I/O cards in the DGX enclosure and the 5002 online, first send the simple MCPU Only kit (DGXMCPU_FW_simple_v3_8_5_2.kit) and allow it to finish updating the MCPU. This update should only take about 10 minutes.
- Once that update is complete and the 5002 is back online, send the full EnovaDGX_3.8.25.kit and allow it to fully update all I/O cards. This final update time will depend on the starting versions of all I/O cards in your system. (40+ min)
- Once the 5002 is back online proceed to the Controller Update and Endpoint Update steps.
Step 2: Controller Update
IMPORTANT: When upgrading from any version 1.6.x or earlier, you MUST turn security OFF. Security can be reenabled after the upgrade is complete.
- Next load SW2106_NX-X200_Controller_v1_8_120.kit to device 0, wait for the DGX to reboot and come back online before proceeding to the Endpoint Updates.
Step 3: 4K60 Endpoint Update
Finally, update the 4K60 DXLink (Twisted Pair/Fiber) Transmitter/Receiver endpoints to the latest firmware version.
Note: Version v1.7.6 has some important offline fixes that will help with consistent endpoint online behavior.
- IMPORTANT: For Autosetup, dipswitch 3 should remain OFF.
- DX-TX-4K60 (download latest version from the product page)
- DX-RX-4K60 (download latest version from the product page)
- 4K60 DXLink Fiber endpoints (compatible only with 4K60 DXLink Fiber I/O cards) require v1.7.6 or later.
- DXFP-TX-4K60 (download latest version from the product page)
- DXFP-TX-4K60 (download latest version from the product page)
These 4K30 RX are reccomended for 2k and 4K30 DXLink Output cards but with v3.8.23 and later, the 4k30 RX will now show up properly on 4K60 DXLink output cards and pass video. However, it is important that any ICSP commands must be sent only to the 4K30 RX in this case rather than the DGX port as with 4K60 TX/RX)
Please note that 2k TX/RX are NOTcompatible with the 4K60 I/O cards. They will not connect properly nor pass video consistently. They are supported on 2k/4k30 I/O cards within the same cage that also has 4K60 I/O and endpoints.
Discretion must be used to ensure that any video passed to or through I/O cards and/or endpoints does not exceed the supported maximum video format for that specific product.
- 2K endpoints (compatible/supported only with 2k and 4K30 DXLink I/O cards)
