Tower-LCC Firmware C6 Update.

Be sure that you are using JMRI version 4.20 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. (e.g. 'TowerLCC_C6_UPDATE.hex')

Note that these upgrades will not disturb your existing configuration data which is stored in a different NVR chip.

C6 Updates Include:

• We have changed the power initialization process to allow a node to initialize and operate with no other nodes present. This will allow small installations such as demo layouts and modules to operate without any other nodes or JMRI present. The node does require a power supply and terminators to be connected.

• Per user request, we have added a veto action to the 'Change' (Toggle) consumer action.

• Rev-C5 uses a delay of 8 ms from power up, then clears the flag, but the red led error might still get triggered if the CAN Receive FIFO isn't emptied fast enough within that time. With rev-C5a we now hold back the red led error until the message 'Node Initialization Complete' is sent, which takes at least 200 ms to complete. Any data received before the node has established its alias isn't required to be handled.
• We also made a minor update to the Power Monitor. If the PowerOK event gets changed by the user, it gets rehashed so that is is effective immediately. The PowerOK event now responds to Identify Producer when queried, if the power monitor is active.

C5a also includes all C5 updates:

• In the CDI Configuration Tool, writing the Node Description field erased the I/O-Line-1 Description field; now fixed;
• A Node Power Monitor is added; the R/B/G leds remain lit if the node voltage is above 3.0V, but below ~4.8V internally (8V* on the bus) the node will not startup;
• If the node internal voltage is above ~4.8V for more than 1 second, the R/B/G leds will go dark, the node initializes its alias and starts normal operations;
• If the node internal voltage drops below ~4.4V, the node is de-initialized and a user-configurable (optional) 'PowerNotOk' event message is sent, the node reboots within 50ms (de-initialization means the node inhibits all CAN-bus messages (except 'PowerNotOK') and FRAM read/writes); the PowerNotOK eventID is stored in EEPROM, so it doesn't need to access FRAM in a low power situation;
  
• On reboot from PowerNotOK (brown-out), the well-known 'Node Power Failed' message and user-configurable (optional) 'PowerOK' message are sent;
• On (re)boot from any other event (power on, reset message, firmware download, factory reset) these 'Node Power Failed' messages will not be sent;
• The node Alias is now saved to EEPROM; upon (re)boot this stored alias will now be used instead of freshly allocating it from the NodeID and risking an alias 'collision' with other nodes, causing multiple nodes to re-allocate their alias; this can be useful on CAN-bus power dropouts, where one (or more) node(s) may reboot where others continue to operate;
• The CDI XML is partially re-written to get rid of the 'Child' references in the CDI Configuration Tool;
• All previous updates and fixes through C4b.

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 information.

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:

1. Start JMRI and select "LCC".

2. Select ‘Firmware Update’ from the LCC drop down list.

3. Click ‘Select’ to pick a firmware file.

4. From the file menu, select: 'TowerLCC_C6_UPDATE.hex' or the latest upgrade available.
5. Select your 'Target Node ID'.
6. Optionally you may check the ‘Lock Node’ check box to take the node off line during the upgrade.
7. Click the 'Load' button to initiate the download to Tower-LCC revision C5a.
   
   

8. Wait until 'updating device firmware..' progress bar is complete and shows 'Operation Complete'.
9. Open the OpenLCB Network Tree window. (LCC-Configure Nodes)
10. The updated node should now show 'Model: Tower-LCC' and 'Software Version: rev-C6'.
11. Any errors will be shown in the lower window ticker tape display.

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.