Be sure that you are using JMRI version 4.14 or later. If you have
nodes #02.01.57.00.00.76 or
earlier that have never been upgraded, then
first go to Tower-LCC-Upgrade.html.
Using Firefox, Google
Chrome, or Safari, (NOT Microsoft Edge) download the latest firmware.
Note that these upgrades will not disturb your existing configuration data which is stored in a different NVR chip.
C5 Updates Include:
IMPORTANT NOTICE: Because the CDI now uses different names for many variables, all existing CDI backup files created with older node firmware (before rev. C5) have become outdated. The C5-UPDATE doesn't affect your existing configuration, so it is strongly advised to create a new backup file immediately after updating to rev. C5.
Note: The Tower LCC includes a switching supply to provide power
to its daughter cards efficiently. This means that it requires at least 8V
from the bus to start up. This exceeds the current official 7.5V OpenLCB
node operating minimum. This upgrade enforces that exception by preventing
normal operation if the bus voltage is not sufficient.
Note: Version C5 stores its Virtual Track Circuit information
in a different format than version B5 did. If you are updating directly
from B5 to C5 You will need to re configure the track circuit section
after an upgrade. Do NOT restore a configuration saved from an earlier
firmware version. It will destroy your virtual track circuit
When ever an update to your Tower LCC firmware is needed, a
program such as "Firmware Update" in JMRI version 4.14 or later is
required. Download the latest firmware version to your local JMRI User
Files folder or someplace where you can easily access it.
To enter Firmware update mode:
Start JMRI and select "LCC".
Click ‘Select’ to pick a firmware file.
If the node does not automatically enter boot mode and start the upgrade it may be forced into boot mode by un-powering it, then holding down the ‘Gold’ button as you power it up again. The gold LED should start flashing to indicate that it is in forced boot mode. This will also likely be required after a failed upgrade attempt.