Changes for page Updating Firmware
Last modified by Alexander Mott on 2024/10/15 14:55
From version 37.1
edited by Alexander Mott
on 2024/10/15 14:55
on 2024/10/15 14:55
Change comment:
There is no comment for this version
To version 35.1
edited by Alexander Mott
on 2024/10/15 14:51
on 2024/10/15 14:51
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -4,8 +4,9 @@ 4 4 5 5 ShowRunnerCLC™ is tested against the latest Crestron firmware releases, and as such it is recommended to update all device firmware whenever starting up a job. While firmware updates can be performed at any time, it is recommended to update network devices after their network settings have been configured but before loading the ShowRunnerCLC™ program and starting up the job in order to avoid any potential bugs that may result from using outdated firmware. Controlled hardware should be updated once all devices on any given Cresnet/ZUMLINK bus or wireless gateway are online and uniquely addressed. Any communication issues on the bus or gateway should also be resolved prior to updating firmware. 6 6 7 -Current Crestron firmware can be downloaded from [[Crestron's website>>https://www.crestron.com/Support/Search-Results?c=4]]. Old firmware releases can be downloaded using an SFTP client (such as FileZilla or WinSCP) and connecting to "ftp.crestron.com" using your Crestron credentials. Current and former firmwarereleases are sorted by device model in the "firmware" folder of Crestron's FTP server.7 +Current Crestron firmware can be downloaded from [[Crestron's website>>https://www.crestron.com/Support/Search-Results?c=4]]. Old firmware releases can be downloaded using an SFTP client (such as FileZilla or WinSCP) and connecting to "ftp.crestron.com" using your Crestron credentials. Firmware are sorted by device model in the "firmware" folder of Crestron's FTP server: 8 8 9 + 9 9 = Network Devices = 10 10 11 11 Networked devices (i.e. devices connected via Ethernet to the LAN or Control Subnet) should always be updated when starting up a job. You can check the current firmware version of most network devices by running the ##ver## command in Text Console or by exporting a Device Summary using the Device Discovery Tool.