Jump to content

RailNET: Updating the Main Program: Difference between revisions

From DocDepot
← Older edit
VisualWikitext
DGast (talk | contribs)
651 edits
AShanks (talk | contribs)
templateeditor
263 edits
No edit summary
 
(41 intermediate revisions by 2 users not shown)
Line 1: Line 1:
This content originated as Comet Electronics Document 480026 
'''NOTE: '''Some content below previously was published as '''Comet Electronics Document 480026: Updating Software'''. 
= Purpose =
= Overview =
<p>Comet Electronics is aware of the ever-changing environment of the rail industry. We are constantly adjusting and fixing components as needed to provide the best service. It is common that software may need updated for the APU’s, and it is important to keep the most updated files to optimize APU functionality.&nbsp;</p>
<p>This procedure provides details for authorized personnel to use in updating the software on the RailNet APU-102. Regular updates are required to optimize functionality and resolve known issues.</p>
<p>Access the files in the Upgrade Files section below to update either your RailNet T-10 or LX-800 software. The T‑10 upgrade requires a three‑file update. The LX‑800 upgrade uses a single package file.</p>
<p>Based on your software, perform the appropriate upgrade procedure using the dedicated section below (T‑10 Upgrade Procedure or LX‑800 Upgrade Procedure).</p>
<p>If you have questions or experience an issue during the update process, contact [[Comet_Support|Comet Support]] for assistance.</p>


Link to software
= Prerequisites =
'''IMPORTANT: &nbsp;'''Before updating software on the RailNet APU‑102 (T‑10 or LX‑800),&nbsp;''always''&nbsp;run the&nbsp;<code>ibackup</code>&nbsp;command to create a mirror of your current configuration. This backup prevents data loss and ensures that your system can be restored if the update process fails.&nbsp;This backup prevents data loss and ensures that your system can be restored if the update process fails.


<p>'''Requirements:'''</p><p>· Upgrade file</p>
To confirm that the backup was created successfully, in the change menu of Session 1, enter <code>\mirror.txt</code>. Verify that the creation date of the backup matches the system date of the APU-102. (If the backup date is older than the system date, repeat the process to create a current image.) Optionally, once you have created your backup, run a parameter dump.
= Upgrade Procedure =
{| class="wikitable" style="border-collapse: collapse; width: 76.8817%; height: 10px; border-color: rgb(0, 0, 0); border-style: solid;" border="2"
|- style="background-color: rgb(230, 126, 35);" 
! style="width: 40%;" | ATTENTION
! style="width: 60%;" | DO NOT ATTEMPT TO UPDATE VIA SERIAL PORT!!!
|}


#Connect and login to the APU.
:'''NOTE:''' Use the <code>irestore</code> command to restore the original parameters and software version from your backup, if needed.
#Enter – ibackup
###We do this incase anything goes wrong.
###irestore will bring back the original parameters and software version.
###Do a Reboot
###Enter – Type \mirror.txt
###This will show you the backup that you just done.
####You will see an updated date and time with this prompt.<br>


{| class="wikitable" style="border-collapse: collapse; width: 76.8817%; height: 46px; border-color: rgb(0, 0, 0); border-style: solid;" border="2"
*See [https://docdepot.railrsm.com/index.php/Restoring_T-10_Software_on_an_APU-102_Unit Restoring T-10 Software on an APU-102 Unit] for details about backing up and restoring T-10 software.
|- style="height: 46px;"
| style="width: 40%; height: 46px;" | NOTE:&nbsp;
| style="width: 60%; height: 46px;" | IF THE PROMPT GIVES YOU A TIME AND DATE OLDER THAN WHAT THE APU IS SHOWING AS TODAYS DATE, THEN START THE PROCESS OVER AGAIN
|}


#Run a parameter dump (optional).
*See [https://docdepot.railrsm.com/index.php/APU102_Auto-Recovery_Quick_Start_Guide_(LX800) APU102 Auto‑Recovery Quick Start Guide (LX800)] for details about backing up LX-800 software.
#Zrec the files. (F.BAT, V52_1_0.exe, ZIP.PSP).
 
#File is V5.2.1.0RC3 (this file name is subject to change as newer versions are made)
= Upgrade Files =
#Do a full reboot. There is no need to shell anything as this is a self-executing update.
Download the appropriate software file:
#Your system should be updated. Don’t forget to look at your parameters as they will have to be updated.
* [https://docdepot.railrsm.com/index.php/RailNET_T10_Version_5_software RailNET T‑10 Version 5 software]
#To make sure that the driver was updated, type, shell dir c:\windows\rtss\009\wdidvr.rts
* [https://docdepot.railrsm.com/index.php/RailNET_LX-800_Version_5_software RailNET LX‑800 Version 5 software]
#The output is shown below. The date provided should be 04/26/2024.
 
<p>[[file:SoftwareUpdated1.png]]</p>
= T-10 Upgrade Procedure =
Complete the steps below to update the T-10 software using a three-file update (plus supporting batch file):
 
::'''IMPORTANT: '''Do not attempt to update via serial port.
<ol>
  <li>Connect and login to the APU-102.</li>
  <li>Zrec the following files: <code>F.BAT</code>, <code>V53-4-37U</code>, <code>V53-4-37U-List</code>, <code>ZIP.PSP</code>.
    <div class="note">'''NOTE:''' File names are intended as examples and subject to change based on latest release.</div></li>
  <li>Reboot the system to finalize the update.
    <div class="note">'''NOTE: '''The update is self‑executing; no shell commands are required.</div></li>
  <li>Review your parameters after reboot, as they may need to be updated.</li>
  <li>To verify that the software update was successful, enter the following command: <code>version</code>.
    <div class="note">'''NOTE: '''This command may take a few moments to run.</div></li>
  <li>The system displays the version information, as in the example image below.
    <div class="note">'''NOTE:''' Version details may vary based on the software release.</div></li>
</ol>
::[[File:T-10_version_info.png]]
 
= LX-800 Upgrade Procedure =
Complete the steps below to update the LX-800 software using a single package file:
 
::'''IMPORTANT: '''Do not attempt to update via serial port.
<ol>
  <li>Connect and login to the APU-102.</li>
  <li>Zrec the file: <code>V5.2.0.17Full.zip</code>.
    <div class="note">'''NOTE:''' File names are intended as examples and subject to change based on latest release.</div></li>
  <li>Confirm that the received file is present.</li>
<li>Enter <code>dir ssunzip.exe</code>.</li>
<li>Enter <code>shell ssunzip V5.2.0.17FULL.zip</code>.</li>
<li>Perform a full system reboot.</li>
<li>Review your parameters after reboot, as they may need to be updated.</li>
</ol>

Latest revision as of 14:11, 19 December 2025

NOTE: Some content below previously was published as Comet Electronics Document 480026: Updating Software. 

Overview

This procedure provides details for authorized personnel to use in updating the software on the RailNet APU-102. Regular updates are required to optimize functionality and resolve known issues.

Access the files in the Upgrade Files section below to update either your RailNet T-10 or LX-800 software. The T‑10 upgrade requires a three‑file update. The LX‑800 upgrade uses a single package file.

Based on your software, perform the appropriate upgrade procedure using the dedicated section below (T‑10 Upgrade Procedure or LX‑800 Upgrade Procedure).

If you have questions or experience an issue during the update process, contact Comet Support for assistance.

Prerequisites

IMPORTANT:  Before updating software on the RailNet APU‑102 (T‑10 or LX‑800), always run the ibackup command to create a mirror of your current configuration. This backup prevents data loss and ensures that your system can be restored if the update process fails. This backup prevents data loss and ensures that your system can be restored if the update process fails.

To confirm that the backup was created successfully, in the change menu of Session 1, enter \mirror.txt. Verify that the creation date of the backup matches the system date of the APU-102. (If the backup date is older than the system date, repeat the process to create a current image.) Optionally, once you have created your backup, run a parameter dump.

NOTE: Use the irestore command to restore the original parameters and software version from your backup, if needed.

Upgrade Files

Download the appropriate software file:

T-10 Upgrade Procedure

Complete the steps below to update the T-10 software using a three-file update (plus supporting batch file):

IMPORTANT: Do not attempt to update via serial port.
  1. Connect and login to the APU-102.
  2. Zrec the following files: F.BAT, V53-4-37U, V53-4-37U-List, ZIP.PSP.
    NOTE: File names are intended as examples and subject to change based on latest release.
  3. Reboot the system to finalize the update.
    NOTE: The update is self‑executing; no shell commands are required.
  4. Review your parameters after reboot, as they may need to be updated.
  5. To verify that the software update was successful, enter the following command: version.
    NOTE: This command may take a few moments to run.
  6. The system displays the version information, as in the example image below.
    NOTE: Version details may vary based on the software release.

LX-800 Upgrade Procedure

Complete the steps below to update the LX-800 software using a single package file:

IMPORTANT: Do not attempt to update via serial port.
  1. Connect and login to the APU-102.
  2. Zrec the file: V5.2.0.17Full.zip.
    NOTE: File names are intended as examples and subject to change based on latest release.
  3. Confirm that the received file is present.
  4. Enter dir ssunzip.exe.
  5. Enter shell ssunzip V5.2.0.17FULL.zip.
  6. Perform a full system reboot.
  7. Review your parameters after reboot, as they may need to be updated.
Retrieved from "https://docdepot.railrsm.com/index.php?title=RailNET:_Updating_the_Main_Program&oldid=2200"