EOTMonitoring

Introduction

This topic needs more info and much clean-up, but here are some things gleaned from the Yahoo group forum.

How to monitor EOT using ATCS Monitor

Cab-to-EOT communications are on 452.9375 MHz, however ATCSMon only decodes EOT-originated messages as found on 457.9375 MHz.

For best results, select "Enable FIR filter" in the DSP/GPS configuration dialog. If the filter for EOT modulation shows as "Not Defined", download and import EOT_Filter.ini from the group temporary files area.

EOT Technical Information

_The below was added based on a message in the YahooGroup(?) forum, perhaps someone would care to format? Original information from Andrew Beard._

It's an old question, but I was looking for EOT monitoring info and figured since nobody had replied I'd answer.

EOT IDs are unique, and are generally assigned by the manufacturer out of a block assigned to them by the AAR. As best I can tell they aren't railroad dependent so much as dependent on when the railroad bough them, and from who.

The frequency at which the head end polls the rear is dependent on the head end. Generally it's not very often, especially since the EOT is transmitting at a minimum about once a minute. Most of the time it's not dependent on any braking input, but it may be dependent on when it got a valid transmission from the EOT last (it may poll more often if it hasn't gotten an ACK from the EOT in a while).

> How are EOT ID's assigned? Are they pretty much a serial number for that
> unit, or are certain ID's assigned to EOT's based on the railroad that
> purchases them?
>
> Also, how often does the head end (452.9375) poll the rear end? Is it
> preset, set by the controller, or based on brake inputs from the
engineer? > Thanks!
> Darrell

Comments/Questions

-- BrianSwan - 07 Jun 2007