DocDepot - User contributions [en]

CINQ Edge User Quick Start Guide

2026-07-08T20:12:14Z

DGast:

== '''Connecting to Cinq Edge''' ==
Welcome to Cinq, your gateway to smarter rail monitoring and connected performance. By providing both historical and real-time insights, Cinq lets you know exactly what's on your sites and in motion to help your organization move from reactive problem solving to predictive planning.

=== '''Terminology''' ===
Before you connect to Cinq Edge, it is important to understand the following terminology:

* '''Cinq:''' The system where you view site activity, device data, and organizational settings. Cinq provides features to monitor communication status, review movement history, and manage your sites.
* CINQ Edge''':''' The hardware installed at the site (available in either solar or commercial-powered versions). The CINQ Edge device collects and sends movement, location, and communication data to the dashboard.

=== '''Initial orientation''' ===
As part of the installation and onboarding process for Cinq Edge, COMET Electronics assigns and configures each device before shipment. When your equipment arrives, it already is paired to your site and ready to activate.

Look for your welcome email from COMET Electronics that contains your company administrator username, temporary password, sign‑in link, and MFA (multifactor authentication) setup instructions.<blockquote>Contact [[Comet Support]] if you do not receive your welcome email within 24 hours of initiating your subscription.</blockquote>The company administrator role manages user accounts, assigns user roles and permissions, and maintains access for your organization. During onboarding, the company administrator assigns a site name to each Cinq Edge site. The company administrator also configures directional movement indicators may to match your operational terminology (for example, Inbound/Outbound, North/South, East/West). Once onboarding is complete, your organization is responsible for managing users in Cinq.

=== '''Cinq Edge Power and Startup Behavior''' ===
Your Cinq Edge’s startup behavior will differ based on its power type:

* Commercial‑powered: Activates immediately once powered.
* Solar‑powered: May need between two and 10 hours of direct sunlight to fully charge and establish connectivity. While Cinq Edge is charging, movement activity, communication status, and GPS location do not appear in Cinq. These details populate in Cinq automatically once Cinq Edge is fully powered and communication and GPS signals are established.

<blockquote>If Cinq fails to display GPS data for two days after initial startup of Cinq Edge, contact [[Comet Support]] for assistance.</blockquote>For complete details on how to install Cinq Edge, see the [[CINQ Edge Installation Manual]] topic.

== Viewing Your Cinq Edge sites ==
After you sign in, Cinq displays the Cinq Edge sites associated with your company account.

To ensure that your dashboard is functioning as expected, verify that the following details are displayed:

* Your Cinq Edge site(s).
* Site details and movement activity.

<blockquote>Contact your company administrator if your assigned site or permissions appear incorrect.</blockquote>The map view displays color-coded icons based on your site type to indicate live status and operational activity:

* Cinq Edge: Sites are displayed using grey icons.
* Full-Scale RailNet AEI''':''' Sites are displayed as green, yellow, orange, or red icons based on current site status and activity levels.

[[file:CEwidedashboard.png|500px|center|thumb|Grey icons designate Cinq Edge sites.]]

== Viewing Site Details ==
Select CINQ Edge on the left navigation pane to access the list of your Cinq Edge device(s).
[[File:Screenshot 2026-04-06 105441.png|center]]

Selecting a device allows you to:

* Review equipment moves.
* View site details and configuration information.
* Monitor messages sent from Cinq Edge.
* View site naming and directional movement configuration.
* You can also open your Cinq Edge sites by selecting '''Cinq Edge''' from the left navigation menu.

== Monitoring Railroad Equipment ==
Select Railroad Equipment on the left navigation pane to view railroad equipment activity for your Cinq Edge site(s).

From this view you can:

* See equipment movements detected at the site.
* Review equipment activity and movement history.

* Export movement records to Excel for operational analysis and reporting.

Movement records populate automatically as railroad equipment passes the Cinq Edge site. During initial startup and activation, movement activity may take time to appear.

Your company administrator can customize movement directions to align with your operational terminology, such as:

* Inbound/Outbound
* North/South
* East/West

Movement history and equipment visibility will continue to increase over time as Cinq Edge detects and transmits activity to Cinq.[[File:Screenshot 2026-04-06 105644.png|center|800x800px|border]]
[[File:Screenshot 2026-04-06 105757.png|center|border|800x800px]]

== Track Zones ==
<blockquote>'''NOTE:''' Track Zones are optional and not configured for all Cinq Edge deployments.</blockquote>Track Zones allow your organization to group and monitor specific operational areas for:

* Movement tracking.
* Inventory visibility.
* Operational monitoring.

If track zones are configured for your Cinq Edge site, select '''Track Zones''' from the left navigation pane to view the zones.

Select a track zone name to view:

* Track zone movements.
* Track Zone inventory.
* Movement history associated with the selected zone.
Movement and inventory information are updated automatically when Cinq Edge detects activity and transmits it to the Cinq.

 

[[File:Screenshot 2026-04-06 105853.png|center|border|800x800px]]

Main Page

2026-07-02T15:23:52Z

DGast:

== Comet Support ==
[[Comet Support | Contact Comet Support]]

== RailNET Software ==
[[RailNET Software]]

== RailNet Reference Materials ==

=== Documentation Packet ===
[[RailNET Full System Documentation Packet (2024)]]

=== Installation and Operations Guides ===
* [[RailNet AEI System – Operations Manual]]
* [[Railnet AEI System Site Installation Manual]]
* [[RailNET In a NEMA Enclosure Installation Manual]]

=== Upgrade Guidance ===
[[RailNET Upgrade Guidance]]

=== Reporting ===

=== Troubleshooting ===
[[Troubleshooting Index]]

== Cinq Edge ==
* [[CINQ Edge User Quick Start Guide|Cinq Edge User Quick Start Guide]]
* [[CINQ Edge Installation Manual|Cinq Edge Installation Manual]]

== Distribution ==
[[Transcore]]

== Bulletins ==
* [[Product Bulletins]]
* [[Service Bulletins]]

== Education ==
[[Basic Networking]]

== Legal ==
* [[Privacy Policy]]
* [[Cookie Policy]]

Resistance ARC Welding in Proximity to AEI Equipment

2026-06-04T18:12:30Z

DGast:

Resistance ARC welding on or near the rail presents electrical and thermal hazards to AEI equipment and associated wiring. Comet Electronics' position on welding operations in the vicinity of AEI installations is as follows:

=== General ===
All AEI equipment and associated wiring must be positioned outside the spark zone established for the welding operation. Personnel must take precautions to ensure that spatter, hot metal fragments, or slag do not contact equipment housings, cable runs, connectors, or any other wiring associated with the AEI installation.

=== Track Circuit ===
Where AEI equipment is integrated with a track circuit, the track circuit must be disconnected and electrically isolated prior to any welding activity on the rail in proximity of the AEI site. Work should not commence until isolation is confirmed. Proximity is defined as less than 30 ft from track circuit connection.

These requirements apply regardless of welding duration or perceived proximity.

Resistance ARC Welding in Proximity to AEI Equipment

2026-06-04T18:07:39Z

DGast: Created page with "Resistance ARC welding on or near the rail presents electrical and thermal hazards to AEI equipment and associated wiring. Comet Electronics' position on welding operations in the vicinity of AEI installations is as follows: Where AEI equipment is integrated with a track circuit, the track circuit must be disconnected and electrically isolated prior to any welding activity on the rail. Work should not commence until isolation is confirmed. All AEI equipment and associa..."

Resistance ARC welding on or near the rail presents electrical and thermal hazards to AEI equipment and associated wiring. Comet Electronics' position on welding operations in the vicinity of AEI installations is as follows:

Where AEI equipment is integrated with a track circuit, the track circuit must be disconnected and electrically isolated prior to any welding activity on the rail. Work should not commence until isolation is confirmed.

All AEI equipment and associated wiring must be positioned outside the spark zone established for the welding operation. Personnel must take precautions to ensure that spatter, hot metal fragments, or slag do not contact equipment housings, cable runs, connectors, or any other wiring associated with the AEI installation.

These requirements apply regardless of welding duration or perceived proximity.

DGast:

RailNET T10 Version 5 software

2026-02-13T15:38:03Z

DGast:

== Version 5.3.5.33 ==
[[Media:V5.3.5.33.zip|Download Version 5.3.5.33]]
# Critical Update to the TDA204 driver and the related application code for better acquisition.
## Latch before read of WDA and WDB timer values.
## Direct couple of variables to hardware reads.
## Improved acquisition conditions.
# Updated Logging for faster performance, including during acquisition. Writes most log messages to files in daily directories named D:\AEI\LOGS\YYMMDD. Log names are DEFAULT-YYMMDD-NNNN.LOG, where NNNN is the acquisition number.
# Log messages include the acquisition number, train number, and message type.
# These log directories are governed by the DiskManager.LogDaysToKeep parameter, which defaults to 30 days. The minimum is 2 days. The maximum is 255 days. Old directories are deleted when they exceed this age.
# ZIPTRAIN.BAT updated to collect new log files.
# Performance improvement for the VERSION command.
# Managed the three-file update size to ~4 MB.

== Version 5.3.5.9 ==
[[Media:V5.3.5.9.zip|Download Version 5.3.5.9]]
#All nameserver entries for DNS are cleared on every boot before adding 1 or 2 nameservers specified in the configuration. If none are specified, none are added. Both DHCP and static IP behave this way.
#Includes the self-extracting executable for train processor version 7.0.0.     The executable is named T070000.EXE.     Version TGEN7.0.0 09/03/2025     Installation     A. The first step of installation is to extract.        Use the following command from the APU Change prompt:        shell t070000 -o     B. After extraction, simulate a train to force PROCONCE.BAT to run.        Use the following command from the APU Change prompt:        st     Changes     A. This TGEN version runs on either the T10 board or the LX800 board.     B. SSDSCALE.EXE accounts for variable length 035 records.

== Version 5.3.5.8 ==

#Development only release.

== Version 5.3.5.7 ==

#When the ETHERNET settings specify DHCP, all nameserver entries for DNS are cleared on boot so nameservers provided by the DHCP server are refreshed and used.
#TDA 204 Driver to version 2.0.10.
#Maintenance report support for fepform.exe with this command usage:     fepform "input filename" "output filename" <ANYARG FOR MAINT>

== Version 5.3.5.6 ==
[[Media:V5.3.5.6.zip|Download Version 5.3.5.6]]
#Fixes issue where the application would crash when iterating through the train data post-acquisition.

== Version 5.3.5.4 ==

#Fixes issue where Default Gateway was not being properly set.
#Fixed issue with SSH tunneling.
#Fixes issues with detector interface.

== Version 5.3.5.3 ==
[[Media:V5.3.5.3.zip|Download Version 5.3.5.3]]

*This file is only meant to upgrade from 5.3.5.2**
*Fixes issue where Default Gateway was not being properly set.
*Fixed issue with SSH tunneling.

== Version 5.3.5.2 ==
 [[Media:V5.3.5.2.zip|Download Version 5.3.5.2]]
#Implements the TDA204 digitizer for the T10.
#Includes the self-extracting executable for train processor version 4.2.0.     The executable is named P040200.EXE.     Version PROC4.2.0 06/02/2025
###Installation     A. The first step of installation is to extract.        Use the following command from the APU Change prompt:        shell p040200 -o     B. After extraction, simulate a train to force PROCONCE.BAT to run.        Use the following command from the APU Change prompt:        st
###Changes     A. Added IOTO010.EXE from TGEN618 for additional I/O fixups.     B. Semaphore files now include:        AXCNVFIX.SEM cancels sequence axle conversion errors.        LLOCOFIX.SEM desensitizes cancellation logic on lead locomotives.        SEQSCALE.SEM assigns scale data to cars in order,                     skipping any locomotives at the start.        SSDSCALE.SEM assigns scale data to the cars in order,                     skipping any locomotives anywhere.     C. Detects Windows version, running on either XP (LX800) or Windows 10 (T10).
#Added cmt-curl configurable consist and maintenance reporting via ftp or sftp.  This is intended to be a universal method for all our units in the future.
#Added ZIPTRAIN.BAT to collect trains and configuration files so that Comet can more readily diagnose issues.
#To add two new users for SCP, aeiSCP and aeiTransfer, do this:     A. First extract f.bat, sshd_config, and zip.psp.        Use the following command from the APU Change prompt:        shell add-scp-users -o     B. Next, reboot to add the users.        Use the following command from the APU Change prompt:        r,c
#The readscale.exe utility takes two arguments, the TRAINNUM.SCA filename, like 00001045.SCA for train number 1045, and the scale configuration file, like CSXSCALE.CFG, and produces the 055 file, in this case 00001045.055.
#The installation documents its results in the Maint Report and site notepad.
#Restored the original, small simulated train.
#Corrected defect in the DP command which prevented EarlyWarning parameters from being displayed under Session1 when the D and Enter keys were pressed.
#NTP errors are logged only when the error state changes so they don't fill up the log. A default NTPPARM.DAT file is created if it is missing, preventing some NPT errors.
#Renamed the DETECTOR1 process to DETECT1, DETECTOR2 to DETECT2, etc., up to DETECTOR10 to DETECT10, since process names are limited to eight characters.
#For I command, Aux 2, #3 now correctly displays the text set up in VIO.CFG.
#Session 10 is now accessible.
#Parameter loading prints "Old parameter detected", when one is obsolete.

== Version 5.3.4.37 ==

[[Media:V5.3.4.37.zip|Download Version 5.3.4.37]]
#Validates MFT files on startup, logging errors to SYS$ERR.LOG and notes.
#Fixed two $REMPORT Watchdog issues.
#Fixed D,* command to page properly, not one file at a time.
#Fixed Watchdog not enabled.
#Fixed DIR command causing a crash.
#Fixed file delete error when removing old trains.

== Version 5.3.4.34 ==

#Double Track fixes.
#IBackup/IRestore fixes.

== Version 5.3.1.1 ==

#Ported 5.2.0.17 for Windows 10.
#Ported for hardware (COMeT10-3900).
#TDA204 Driver replaces RTX.

RailNET T10 Version 5 software

2026-02-13T15:37:41Z

2026-02-09T20:21:28Z

DGast: Created page with "Railert ATR Installation Guide Railert II User Guide media:400958_Teifenbach G84/120/24"

[[Railert ATR Installation Guide]]

[[Railert II User Guide]]

[[media:400958_Teifenbach G84/120/24]]

Consist Reporting-Confidence Logic

2026-01-30T02:35:33Z

DGast: Created page with "There are a few factors that can affect applying tags to a car. (assuming we even read tags). When we read both tags, they will be applied. Where we have to be careful is when we only read one tag. How we handle accurate reporting is called “Confidence Logic”. It is dynamically based on site conditions and parameter settings. There are 3 confidence levels and 3 “conditions” that impact tag reporting.The key philosophy in how confiden..."

There are a few factors that can affect applying tags to a car. (assuming we even read tags). When we read both tags, they will be applied. Where we have to be careful is when we only read one tag. How we handle accurate reporting is called “Confidence Logic”. It is dynamically based on site conditions and parameter settings. There are 3 confidence levels and 3 “conditions” that impact tag reporting.The key philosophy in how confidence logic works is “if in doubt, throw it out.”You need to understand Intertrack Communications (ITC) before getting into confidence logic. When you have adjacent tracks and trains moving on both, you '''WILL''' read tags from the train on the other track. We do not want to report the wrong tag on our train, so how do we deal with it? This requires ITC is correctly cabled and configured. ITC shares data between double track APUs when both tracks are occupied to determine where to apply tags read on both APUs. Maintaining communication with the other APU is vital. Even when no data is to be exchanged, the ITC sends a "heartbeat" that is monitored on the other end. It is constantly checking for the heartbeat. If it does not receive the heartbeat, it assumes the link is down and reports ITC Fail which affects how we report singly tagged cars. The Pentium class APU with 5.x software interchanges more data than the DOS based 4.x APU and sends a different heartbeat. However, they can still be connected if properly configured. The 5.x APU will see it is receiving the 4.x heartbeat and will adjust its ITC logic to match.  The following table is from the CNF help screen on the APU. The CNF command is no longer used to setup, but its help is still there and is useful to understand CNF. The confidence settings are done in the parameter editor under AEI reporting options for each active session. These values in this example are the defaults and may need adjustment for your specific site conditions.  AEI CONFIDENCE LOGIC PARAMETERSThe following parameters are used to filter AEI data from outgoing consists based on software comparisons between AEI tag information and axle generated car information.
{| class="wikitable" style="border-collapse: collapse; width: 100%; height: 207px;"
|- style="height: 23px; background-color: rgb(149, 165, 166);"
! style="height: 23px;" colspan="2" | Current Settings 
|- style="height: 23px;"
| style="text-align: center; height: 23px;" colspan="2" | Default Confidence Level :  3
|- style="height: 23px;"
| style="text-align: center; height: 23px;" colspan="2" | Double Track Active Confidence Level :  2
|- style="height: 23px;"
| style="width: 50%; text-align: center; height: 23px;" colspan="2" | ITC Failure Confidence Level :  1
|- style="height: 23px; background-color: rgb(149, 165, 166);"
! style="width: 50%; height: 23px;" | Conditional Options  
! style="width: 50%; height: 23px;" | Confidence Level Options
|- style="height: 23px;"
| style="width: 50%; height: 23px;" | D - Default. Used when no abnormal conditions exist.
| style="width: 50%; height: 23px;" | 0 - Tags are not reported.
|- style="height: 23px;"
| style="width: 50%; height: 23px;" | T - Double Track Active. Used when train is active on adjacent track.
| style="width: 50%; height: 23px;" | 1 - Tag is reported only if both left and right tags were read.
|- style="height: 46px;"
| style="width: 50%; height: 46px;" | F - Intertrack Communications Failure. Used when APU cannot access data on adjacent track's APU.
| style="width: 50%; height: 46px;" | 2 - Single tags are reported only if no discrepancies exist between car and tag information.
|-
| style="width: 50%;" |
| style="width: 50%;" | 3 - All tags are reported.
|}
                           
== '''Confidence Level 3, report all tags:''' ==
On single track systems we typically apply all tags read, unless multiples were read over the axle platform and we don’t have a matching pair. On double tracks with single moves and ITC functioning properly, it works like a single track system.  Considered condition "Default".   
== Confidence Level 2, report clean singles: ==
A single tag read on a car must fit the car. It's compared for correct axle count, car length, EGC, position where read, etc. It can still match with minor disqualifier errors, but too many and it gets reported as an untagged car. Typically, this level is used with both tracks occupied on double track sites. (and ITC functioning properly)-this condition is called:“DTA," (Double Track Active). Also used for some single tracks where there are "presence aware" adjacent tracks where stray tags might get read.  
== Confidence Level 1, Must have Both tags to report: ==
We have to read both tags to report on the car. Typical for double track sites where the ITC communication has failed. When ITC is down, we are not sharing data with the other track's APU. We have no crosschecks or tag filtering so we have to be as defensive as possible in this state."ITC Fail"Version 5.0 exchanges axle and tag data. After the train clears, the APU processes its own train and the train from data received from the other track. If a tag shows up on both consists, it is thrown out.

APU-102 Wayside Equipment Command Shell (WECS)

2026-01-29T17:34:10Z

DGast: /* Command: LT94 */

Tag: Detector Support

This article details the commands and responses that are available for external wayside detectors to retrieve AEI data from the APU102.
= Transport: =
Currently, this interface is available via RS232 or Ethernet. When using Ethernet, assign each detector a unique IP port to attach to. Currently, the default port is 24.

= Logging in: =
Once a connection is made, simply send an <ENTER>. A prompt will be returned.

For example:

[[image:WECSIMG1.png|center]]

= Commands Supported: =

*TDIR – Train directory (list last 5 trains)
*LT94 – Consist dump in T94 (S918A;S9203) format.
*STAT – AEI unit status.
*EXIT – Exit the interface.

For an updated list of commands, type “?” at the prompt.

Example:

[[image:WECSIMG2.png|center]]

= Typical Usage: =
Once the train clears the AEI system, the APU102 processes the train and makes the final consist available to the external wayside detector unit(s). Because there is a finite period of processing required by the APU102 to produce this consist, it may take as long as two minutes after the train clears the site before a consist can be accessed (especially in multitrack territory). In most cases, it will be available within 10 seconds

To allow the external processors to be aware that processing may still be underway, a “STAT” command is available. By inspecting the “Postprocessing?” and “Acquiring” fields returned by the STAT command, the external device is able to determine if additional wait time is necessary.

In the simplest usage scenario, a defect detector accesses the AEI interface only after it has finished recording a train. In that case, the detector would simply request a periodic STAT dump from the unit, unit it is reported that “acquisition” and “post processing” is complete. At that time, the external device can issue an “LT94” command to retrieve the consist for the last train.

= Interface Health Support: =
To allow the APU102 to conduct simple health reporting to our customer’s maintenance hosts, the software will expect to see periodic commands issued (typically “stat”, or simply an “<enter>”). If no activity is seen for longer than 2 minutes, the APU102 will log and report a message to the customer’s maintenance host indicating the connection has been disconnected.

== External Detector Command Responses: ==
==== Command: TDIR ====
Sends up to the last 5 TDIR entries. Terminates with “EOL*LineCount” message
{| class="wikitable" style="border-collapse: collapse;"
|- style="background-color: rgb(149, 165, 166);"
! style="width: 52px;" | Ref
! style="width: 90px;" | Field
! style="width: 33px;" | Type
! style="width: 30px;" | Size
! style="width: 159px;" | Description
|-
| style="width: 52px;" | TDIR00
| style="width: 90px;" | Segment ID
| style="width: 33px;" | AN
| style="width: 30px;" | 4
| style="width: 159px;" | “TDIR”
|-
| style="width: 52px;" | TDIR01
| style="width: 90px;" | Train Seq
| style="width: 33px;" | N
| style="width: 30px;" | 8
| style="width: 159px;" | Train Sequence #
|-
| style="width: 52px;" | TDIR02
| style="width: 90px;" | Start Date
| style="width: 33px;" | N
| style="width: 30px;" | 8
| style="width: 159px;" | Start Date in YY-MM-DD
|-
| style="width: 52px;" | TDIR03
| style="width: 90px;" | Start Time
| style="width: 33px;" | N
| style="width: 30px;" | 8
| style="width: 159px;" | Start Time in HH:MM:SS
|-
| style="width: 52px;" | TDIR04
| style="width: 90px;" | End Date
| style="width: 33px;" | N
| style="width: 30px;" | 8
| style="width: 159px;" | End Date in YY-MM-DD
|-
| style="width: 52px;" | TDIR05
| style="width: 90px;" | End Time
| style="width: 33px;" | N
| style="width: 30px;" | 8
| style="width: 159px;" | End Time in HH:MM:SS
|-
| style="width: 52px;" | TDIR06
| style="width: 90px;" | Owner Code
| style="width: 33px;" | AN
| style="width: 30px;" | 4
| style="width: 159px;" | Lead Loco Owner
|-
| style="width: 52px;" | TDIR07
| style="width: 90px;" | Number
| style="width: 33px;" | N
| style="width: 30px;" | 6
| style="width: 159px;" | Lead Loco Number
|-
| style="width: 52px;" | TDIR08
| style="width: 90px;" | Dir
| style="width: 33px;" | A
| style="width: 30px;" | 1
| style="width: 159px;" | ‘<’ = R to L, ‘>’ = LtoR
|-
| style="width: 52px;" | TDIR09
| style="width: 90px;" | Total Axles
| style="width: 33px;" | A
| style="width: 30px;" | 4
| style="width: 159px;" | Total Axles in Train
|-
| style="width: 52px;" | TDIR10
| style="width: 90px;" | Total Vehicles
| style="width: 33px;" | A
| style="width: 30px;" | 4
| style="width: 159px;" | Total Vehicles in train
|-
| style="width: 52px;" | TDIR11
| style="width: 90px;" | Total Tags
| style="width: 33px;" | A
| style="width: 30px;" | 4
| style="width: 159px;" | Total tag count.
|}
Example:

[[image:WECSIMG3.png|center]]

==== Command: STAT ====

Sends single line detailing current status.
{| class="wikitable" style="border-collapse: collapse;"
|- style="background-color: rgb(149, 165, 166);"
! Ref
! Field
! Type
! Size
! Description
|-
| STAT00
| Segment ID
| AN
| 4
| “STAT”
|-
| STAT01
| Seconds UTC
| N
| 10
| Time in seconds since UTC 1/1/70
|-
| STAT02
| Local Date
| N
| 8
| Date in YY-MM-DD
|-
| STAT03
| Local Time
| N
| 8
| Time in HH:MM:SS
|-
| STAT04
| Acquisition Clock
| N
| 10
| Time in Ms since start of clock synch.
|-
| STAT05
| Acquiring
| A
| 1
| Y/N
|-
| STAT06
| Post Processing?
| A
| 1
| Y/N
|-
| STAT07
| Current Axle
| N
| 5
|
|-
| STAT08
| Current Speed
| N
| 4
| Ft/Sec
|-
| STAT09
| Current Seq
| N
| 4
| Current (or next) train seq
|-
| STAT10
|
|
|
|
|}
Example:

[[image:WECSIMG4.png|center]]

==== Command: LT94 <SEQ#> ====

Sends consist information for a train. Refer to the “T94 report specification” for details concerning the format of the output.  In the Detector Support Interface the train direction is indicated by "<" or ">".  This is intended to give direction without defining direction.  The Direction should be translated to S9203 format of NSEW when reporting to the client host.

Example:

<code class="mwt-code">AEI>LT94
AEM*00076*TA75511*060817*2245*2250*070*Y*411*0002*G*G*N*0*E*028*015*06334*G*03*02*105*105*0436
RRE*001*D* *0000000000*A* *G*N*K*00*00*020*06*01
RRE*002*D*CSXT*0000008518*B* *G*G*K*38*14*021*06*01
RRE*003*D*CSXT*0000005864*B* *G*G*L*35*17*015*04*01
RRE*004*R*BNSF*0000432638*A* *G*G*K*40*03*019*04*01
RRE*005*R*BNSF*0000780578*A* *G*G*K*38*18*019*04*01
RRE*006*R*BNSF*0000782917*B* *G*G*K*36*15*019*04*01
RRE*007*R*DMIX*0000190145*A* *G*G*K*40*19*020*04*01
RRE*008*R*GATX*0000073427*A* *G*G*K*38*18*020*04*01
RRE*009*R*CSXT*0000130078*B* *G*G*K*40*14*021*04*01
RRE*010*R*RBOX*0000040426*A* *G*G*P*37*18*021*04*01
RRE*011*R*CSYX*0000013492*A* *G*G*K*35*14*020*04*01
RRE*012*R*CEFX*0000011185*A* *G*G*K*35*11*021*04*01
RRE*013*R*CEFX*0000011164*A* *G*G*K*34*02*021*04*01
RRE*014*R*CEFX*0000012279*B* *G*G*K*35*08*021*04*01
RRE*015*R*CEFX*0000012241*A* *G*G*L*35*11*021*04*01
RRE*016*R*UELX*0000030024*A* *G*G*K*36*13*022*04*01
RRE*017*R*ADMX*0000085135*B* *G*G*K*31*17*022*04*01
RRE*018*R*UELX*0000100029*B* *G*L*K*32*00*022*04*01
RRE*019*R*UELX*0000030332*B* *G*G*K*38*14*022*04*01
RRE*020*R*AGPX*0000095235*B* *G*G*K*29*13*022*04*01
RRE*021*R*TILX*0000512211*B* *G*G*K*33*21*023*04*01
RRE*022*R*CRDX*0000014293*B* *G*G*K*30*13*022*04*01
RRE*023*R*AEX *0000006514*B* *G*G*K*32*07*023*04*01
RRE*024*R*HPJX*0000015051*B* *G*G*K*29*16*023*04*01
RRE*025*R*MMID*0000005059*B* *G*G*K*31*01*023*04*01
RRE*026*R*CSXT*0000228209*B* *G*G*K*31*17*023*04*01
RRE*027*R*CSXT*0000223017*B* *G*G*K*33*15*024*04*01
RRE*028*R*CSXT*0000226487*A* *G*G*K*32*15*023*04*01
RRE*029*R*CSXT*0000222012*B* *G*G*K*33*12*024*04*01
RRE*030*R*SSAM*0000043512*B* *G*G*K*30*15*025*04*01
RRE*031*R*CNA *0000555065*B* *G*G*K*31*14*025*04*01
RRE*032*R*BCOL*0000041799*B* *G*G*K*33*15*025*04*01
RRE*033*R*IC *0000624463*A* *G*G*K*29*14*024*04*01
RRE*034*R*SRY *0000318278*A* *G*G*K*24*15*024*04*01
RRE*035*R*ATW *0000300134*B* *G*G*K*30*16*025*04*01
RRE*036*R*CSXT*0000227184*A* *G*L*K*00*18*025*04*01
RRE*037*R*CSXT*0000228251*A* *G*G*K*28*12*025*04*01
RRE*038*R*CSXT*0000220682*B* *G*G*K*23*09*025*04*01
RRE*039*R*CSXT*0000227268*B* *G*G*K*27*13*025*04*01
RRE*040*R*CO *0000604922*B* *G*G*K*30*03*025*04*01
RRE*041*R*BO *0000605218*A* *G*G*K*29*08*025*04*01
RRE*042*R*NYC *0000883927*B* *G*G*K*28*06*025*04*01
RRE*043*R*CSXT*0000228059*A* *G*G*K*30*11*026*04*01
RRE*044*R*GATX*0000030055*A* *G*G*K*30*15*026*04*01
RRE*045*R*CSXT*0000137183*B* *G*G*K*30*16*026*04*01
RRE*046*R*ETCX*0000000926*B* *G*G*K*29*13*025*04*01
RRE*047*R*ETCX*0000052031*B* *G*G*K*29*08*026*04*01
RRE*048*R*ETCX*0000000911*B* *G*G*K*30*12*026*04*01
RRE*049*R*ETCX*0000001074*A* *G*G*K*30*13*026*04*01
RRE*050*R*NAHX*0000800254*B* *G*G*K*28*17*026*04*01
RRE*051*R*ATW *0000114033*A* *G*G*P*27*15*027*04*01
RRE*052*R*SOU *0000085042*B* *G*G*K*23*09*025*04*01
RRE*053*R*XTTX*0000137248*A* *G*G*K*03*10*026*04*01
RRE*054*R*AEX *0000009055*B* *G*G*K*29*04*026*04*01
RRE*055*R*NAHX*0000060730*A* *G*R*K*28*00*026*04*01
RRE*056*R*IC *0000010093*A* *G*G*K*27*07*026*04*01
RRE*057*R*TTJX*0000081671*B* *G*G*K*30*16*026*04*01
RRE*058*R*AEX *0000004142*B* *G*G*K*27*12*026*04*01
RRE*059*R*AEX *0000007490*A* *G*G*K*24*11*026*04*01
RRE*060*R*TIMX*0000062024*A* *G*G*K*33*11*026*04*01
RRE*061*R*TIMX*0000062002*A* *G*G*K*26*16*026*04*01
RRE*062*R*EEC *0000000818*A* *G*G*K*29*15*027*04*01
RRE*063*R*AOK *0000021548*B* *G*G*K*26*13*026*04*01
RRE*064*R*AOK *0000029817*B* *G*G*K*25*10*026*04*01
RRE*065*R*TTZX*0000087558*A* *G*G*K*24*16*026*04*01
RRE*066*R*NOKL*0000732566*B* *G*G*K*10*08*026*04*01
RRE*067*R*CN *0000625334*B* *G*G*K*23*11*027*04*01
RRE*068*R*ABOX*0000052094*B* *G*G*K*29*14*027*04*01
RRE*069*R*ABOX*0000051922*B* *G*G*K*26*15*028*04*01
RRE*070*R*ABOX*0000052018*B* *G*G*K*28*15*027*04*01
RRE*071*R*NW *0000178393*A* *G*G*K*22*10*026*04*01
RRE*072*R*RFMX*0000464339*B* *G*G*K*28*03*026*04*01
RRE*073*R*SIRX*0000460326*A* *G*G*K*29*02*026*04*01
RRE*074*R*CRDX*0000004845*A* *G*G*K*28*13*026*04*01
RRE*075*R*CHVX*0000889374*A* *G*G*K*31*14*026*04*01
RRE*076*R*CHVX*0000890226*A* *G*G*K*21*12*026*04*01
RRE*077*R*PSPX*0000006162*A* *G*G*K*29*11*026*04*01
RRE*078*R*CSXT*0000292015*B* *G*G*K*31*07*026*04*01
RRE*079*R*AEX *0000004133*B* *G*G*K*27*11*026*04*01
RRE*080*R*CSXT*0000251152*B* *G*G*K*27*04*026*04*01
RRE*081*R*NCHX*0000046090*A* *G*R*K*27*00*026*04*01
RRE*082*R*ACFX*0000064791*A* *G*R*P*29*00*026*04*01
RRE*083*R*NDYX*0000827685*B* *G*G*K*19*02*026*04*01
RRE*084*R*ATW *0000113151*B* *G*G*K*31*14*027*04*01
RRE*085*R*GVSR*0000782018*A* *G*G*K*27*18*027*04*01
RRE*086*R*EEC *0000002094*A* *G*G*K*31*13*026*04*01
RRE*087*R*RBOX*0000032673*A* *G*G*K*23*15*027*04*01
RRE*088*R*TTZX*0000085477*A* *G*G*K*22*15*025*04*01
RRE*089*R*BCOL*0000873518*A* *G*G*K*21*13*025*04*01
RRE*090*R*WC *0000037150*B* *G*G*K*14*10*025*04*01
RRE*091*R*WC *0000037653*A* *G*G*K*27*12*025*04*01
RRE*092*R*CNIS*0000623214*B* *G*G*K*26*14*025*04*01
RRE*093*R*HOKX*0000112086*B* *G*G*K*31*15*025*04*01
RRE*094*R*FMLX*0000051685*B* *G*G*K*26*12*025*04*01
RRE*095*R*CSXT*0000485038*B* *G*R*L*00*08*025*04*01
RRE*096*R*CSXT*0000705742*A* *G*G*K*29*12*025*04*01
RRE*097*R*CSXT*0000486398*B* *G*G*K*21*16*025*04*01
RRE*098*R*RBOX*0000043652*A* *G*G*K*23*16*025*04*01
RRE*099*R*SOU *0000530948*B* *G*G*K*32*14*025*04*01
RRE*100*R*CN *0000407054*A* *G*G*K*28*11*025*04*01
RRE*101*R*GMRC*0000021085*B* *G*G*K*32*14*025*04*01
RRE*102*R*MEC *0000032144*B* *G*G*K*30*15*025*04*01
RRE*103*R*CVC *0000402528*A* *G*G*K*31*14*025*04*01
RRE*104*R*MEC *0000032071*A* *G*G*K*29*16*025*04*01
RRE*105*R*RBOX*0000036246*A* *G*G*K*32*14*025*04*01
RRE*106*R*ADMX*0000017757*A* *G*G*K*34*02*024*04*01
RRE*107*R*SHPX*0000201378*A* *G*G*K*30*16*024*04*01
RRE*108*R*UTLX*0000628032*B* *G*G*K*29*17*024*04*01
EOT*108*E*CSXE*0000028671*00*20*K
EOC*0000005867</code>

Troubleshooting Index

2026-01-29T17:31:44Z

DGast:

[[Site Not Reporting: Missing DNS.DAT]]

[[Obtaining Diagnostic Train Records]]

[[APU-102 Wayside Equipment Command Shell (WECS)]]

[[RailNET Basic Diagnostics]]

AEI Site Installation Introduction

2026-01-29T17:31:08Z

DGast: /* Additional Information */

[[Railnet AEI System Site Installation Manual]]

This manual provides instructions for installing and optimizing the equipment at an Automatic Equipment Identification (AEI) site. It explains installation and optimization for each component of the AEI system. The following summarizes the purpose of each chapter in this guide.
= Introduction =
The chapter you are currently reading summarizes the information provided in the other sections of this manual.
= Installation Procedure =
This chapter includes the following sections:
===== Overview =====
Overviews the installation section of this manual.
===== Site Preparation =====
Outlines site considerations, construction, and installation for single track and double track AEI sites.
===== AEI Component Installation =====
Includes installation procedures for the following AEI System components: 
*Tiefenbach wheel transducer 
*TDA-105 
*Antenna 
*Presence detector 
*Heliax coaxial cable

= Optimization Procedure =
This chapter includes the following sections:
===== Overview =====
Overview of the optimization section of this manual.
===== APU Application Software =====
Provides an in-depth explanation of the APU-102 application software and the initial steps necessary to log on and navigate through the software.
===== System Optimization =====
Provides optimization recommendations for the APU-102 System software.
===== RF Power Optimization =====
Instructions for RF unit optimization.
===== Wheel Detector Optimization =====
Lists optimization steps for the Tiefenbach wheel detector and its interface, the TDA-105.
===== Loop and Loop Detector Optimization =====
Includes procedures for loop and loop detector optimization.
===== System Operational Checkout =====
This checkout procedure offers a method for testing system operation. It demonstrates how to simulate a train from the track using the software or the APU-102 buttons.
===== Appendix A: Site Optimization Checklist =====
Assists in verifying that all optimization procedures were completed.
===== Appendix B: Installation Tools and Supplies =====
Provides a general list of all tools and supplies usually supplied by the installation contractor. Does not include material usually supplied in Comet Electronics installation kits. 
===== Appendix C: Site Drawings =====
This appendix contains generic site installation drawings, with an indexed listing at the beginning. The drawings are arranged in the order they will normally be used at the site.
= Additional Documentation =
For AEI System operation, APU application software user interface, system troubleshooting, a detailed description of system components, and a glossary of AEI System terms, refer to the [[APU-102 Manual|AEI System Operations Manual]].
= Additional Information =
This manual does not include information on intermodal, nonstandard, and collocated installations. If your installation includes any of the following, contact Comet Electronics for additional information.
* Intermodal antennas (tiers 1 and/or 2) 
*The following non-standard installations: 
***Three or more tracks
***SmartPass or RailPass integrated readers 
***More than one wheel transducer per track 
***More than one presence loop per track 
***Switch point (route) indication 
***Double track unrestricted sites with inside (island) huts 
***Sites with concrete or steel ties 
*Colocated installations, such as: 
*** Scales 
***Humps 
***Defect detectors [[APU-102 Wayside Equipment Command Shell (WECS)]]