DVX-3266-2265-4k Switcher & Controller Update
Table of Contents
This article contains two downloads (located in upper right corner of this page). Installation instructions are after the release notes.
Changes/Features Overview:
Enova DVX 4K 5002 Switcher updates v2.0.4: (see Switcher Readme for details on prior versions)
- Changed in 2.0.4
- (Feature) Added support for new DXLink 4K60 DWP TX
- Fixed issue where the logo would not show after disconnecting the input route of an output
- Changed in previous 2.0.1
- Fixed issue where logo would not show after switching beween unused/empty inputs or after reboot if routed input was unused/empty
- Fixed issue where TCP bound 4K60 DXLink TX/RX would not come online consistently after DVX reboot and the DXLink cable had to be hotplugged or the DXLINK ETH command had to be toggled to get the endpoints to come online again
- Fixed issue where HDMI Mirrored output AUDIO was not present after a DVX reboot and the group had to be reselected
NX Controller changes in v1.8.200 (hotfix)
IMPORTANT: If needing to downgrade from any 1.8.xxx version to any 1.6.20x version, you must disable Authentication on Server Ports on the General tab of the Webgui prior to downgrading. After downgrade, you will need to do a reset factory to properly reset the password paths. This will also re-enable the security. Then reload your code.
v1.8.211
- Fixed audit log issue so that after using "clear audit" the audit logging will continue
- Updated description to "SDAuditLog on" command to indicate a reboot is required to start logging
v1.8.210
- Corrected LDAP-authenticated users roles to allow execution of certain SSH CLI commands related
to device security and logging
v1.8.209
- Fixed issue causing an NX controller to lockup over time if there were unreachable url in its URL list
v1.8.207
- Improved ssh_client open/close issues
- Improved duplicate ssh keys on NX to be unique on each unit
v1.8.206
- Fixed issue to allow for pre-connection closure of socket without causing soft rebbot
v1.8.205
- Improved SSH_CLIENT_OPEN memory usage
v1.8.203
- Modified JVM statup parameters to prevent Web Server crash due to java.lang.StackOverflowError
-- reset factory needed for new defaults to take effect
v1.8.202
- Added a check for possible issues that could cause the hs_err_pid412
v1.8.201
- Added TLS_CLIENT_OPEN to support TLSv1.3
v1.8.200
- Improved memory usage on Netlinx programs
v1.8.197
- Fixed a bug with certificate loading on v1.8.195
v1.8.196
- Fixed bug causing no OFFLINE event when calling IP_CLIENT_CLOSE
v1.8.195
- upgrade openssh to "SSH-2.0-OpenSSH_9.8"
v1.8.193
- Fixed bug with URL entry when using port 1320
v1.8.192
- Fixed SSH_CLIENT_OPEN/CLOSE bug
v1.8.190 (Release)
- Fixed boot issue in manufacturing when using blank MSOM with 1.8.x firmware
v1.8.187
- Added Telnet support for upper case icsp commands: SEND_STRING, SEND STRING, SEND_LEVEL, SEND LEVEL, SEND_COMMAND, SEND COMMAND
v1.8.186
- Fixed icsp TLS issue connections with Controller-to-Controller and Controller-to-Panel scenarios
v1.8.184
- upgrade TLSv1_2 to TLSv1_3
v1.8.183 (Release)
- Added support for new DXLink 4K60 DWP TX in Webgui of DGX and DVX4k
- Improved boot time to be faster (except for High Security Mode which takes a few minutes longer due
to security key creation and authentication)
- Fixed issue with telnet URL list commands causing telnet session to lock up when deleting URL item
- Fixed static ip gateway persistence issue during upgrade from 1.6.x to 1.8.x firmware
- Fixed telnet Master to Master issue
See v1.8.183 Readme for earlier version history
Known Issues
- The update should take about 5 minutes after the firmware transfer has completed. If after 5 minutes you can refresh the online tree and
still see the old version of firmware, then power cycle the unit to initiate/complete the update. If refreshing the online tree fails to
contact the processor, please give the process a few more minutes to complete.
- See included readme for additional known issues.
Overall steps to this article:
- Update DVX central Controller version followed by updating DVX Switcher version
- Update DXLINK endpoints
Step 1:
The order of loading the firmware is to update the central controller first, then update the switcher.
IMPORTANT: When upgrading from any Master/Controller version 1.6.x or earlier, you MUST turn security OFF. Security can be reenabled after the upgrade is complete.
- Load SW2106_NX-X200_Controller_v1_8_183.kit to device 0, wait for the DVX to reboot and come back online.
- Load SW1906_25A_SWITCHER_v2_0_4.kit to device 5002. The DVX will reboot and the 5002 will begin the update. Do not power cycle the DVX until the 5002 has fully completed the update and is back online in Netlinx Studio. The front panel of the DVX shows the update status.
IMPORTANT: This upgrade can take from 30 min to 2 hours depending on the starting firmware. Please be patient and don't reboot the DVX until it is done.
NOTE: If updating the 5002 from v1.9.9 or later, the 5002 upgrade progress can be monitored Netlinx Studio Notifications
- Tip: It is recommended to send the command ?FWVERSION to 5002:1:0 before and after the upgrade and keep the responses handy so you can verify all components have updated correctly. See Readme for details.
Step 2:
**If the link takes you to the product page of a device, find the newest revision under downloads.
If you have DXLINK Transmitter or Receiver endpoints, please update their firmware also.
- 2K endpoints
- RX - https://help.harmanpro.com/dxlink-rx-x00-firmware
- TX - https://www.amx.com/en/products/dx-tx
- These can not be AutoSetup with DVX-4K but they will get a Private IP (198.18.x.x) initially. Using the new commands in the DVX-4K Readme, the DVX-4K will allow these endpoints to be given a Public IP address.
- Send Commands must be sent to the endpoints
- 4K30 endpoint
These may show up as AutoSetup with DVX-4K but but may require a hotplug after system power cycle if they don't come back as Autosetup initially. If not, they will get a Private IP (198.18.x.x) and can be set to traditional binding. Using the new commands in the DVX-4K Readme, the DVX-4K will allow these endpoints to be given a Public IP address.
- Send Commands must be sent to the endpoints
- 4K60 endpoints - RECOMMENDED for use the DVX-4K
- DX-TX-4K60 - https://www.amx.com/en-US/products/dx-tx-4k60
- DX-RX-4K60 - https://www.amx.com/en-US/products/dx-rx-4k60
- These will AutoSetup by default and Send Commands can be sent to the DVX port OR to the endpoints
Note: v1.6.7 (or later versions) fixes the Serial String ascii/hex issues on the previous versions
TIP - Other non-4k60 DXLink/HDBT endpoint devices may not show up online after a reboot of the DVX. To work around this, try toggling the Ethernet via send command after the DVX comes online. (eg. For a connected SDX or VPX try sending: DXLINK_IN_ETH-OFF followed by DXLINK_IN_ETH-AUTO)