Recover Train Information

From FYM Wiki
Revision as of 14:37, 13 February 2019 by Flankbell (talk | contribs) (Created page with "When 2 trains couple together, only one set of information is saved with the new train so formed. (a train is defined as a single FYM entity, it can be a single car or a numbe...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

When 2 trains couple together, only one set of information is saved with the new train so formed. (a train is defined as a single FYM entity, it can be a single car or a number of engines and cars)


This information consists of the following:

1. The Train Symbol

2. The TSAR Reference

3. The Train Originator

4. The Date and Time of Dispatch

5. The notes associated with this train.

6. Block information specified for this train.

Items 3 and 4 are used internally by both FYM and TrainFinder and cannot be entered directly by a player.


Usually the information discarded is of no importance. However, there are times when it is important to be able to recover this information and apply it to a train e.g. a. Following the unintentional coupling of 2 trains (with or without damage) b. When engines are replaced on a train and the train is to retain it's original identity.

To assist you with this, FYM stores up to 150 data sets (items 1 to 5 above) and provides an easy and convenient way of applying a data set to a train. Discarded data is not retained for cars being humped.

A. An unintentional coupling of 2 trains


While doing some run throughs I didn't notice that the lead train (NS 395-16) was moving slower than the autorack train (NS 28Q-28) and unfortunately the 2 trains coupled - luckily at a relative velocity < 20mph so no damage ensued. (How to handle damaged trains will be covered under s separate topic).

Now I have 1 train NS 395-16 and all the information for NS 28Q-28 has disappeared. Clearly I can't just run this as 1 train (Each was bound for a different destination). So I must get back the original trains including all the information associated with them.

A.1 Separate the trains

Uncouple the 2 trains as you would ordinarily and move them slightly apart. If you select each in turn and open the Train Information form you will notice that both have identical data sets for items 1, 2 and 5 above (Items 3 and 4 will also be identical but not visible to you).

A.2 Determine which train has the incorrect information

With the Train Information form open select any unit in the list and click on the History Tab.


The last entry for that unit's History will give the correct Train symbol if this is now different to that which appears in the 'Train:' box (top left) then this is the train with the incorrect information.

A.3 Assign the correct information to the train


Press the 'i' button in the 'TSAR Data Reovery' section. This will open the Train Name and Information form.


From the list of trains in the left hand box, select the one which corresponds to the correct Train Symbol in the unit's History. In this case we select NS 28Q-28. FYM will store up to 150 such data sets in any logon session.

To apply the selected data set to the train simply press COPY.

You now have the correct information assigned to both trains involved in this incidient. Both trains can now continue on their way.

B. Engine replacement and retaining original data This section covers the situation where a train arrives at your yard and you decide (for whatever reason) to replace the engines before sending it on it's way.

When the engines are attached the train will assume the information of the engines and the original (and correct) information will be discarded. To recover this information you should proceed as in A2 and A3 above. Step A2 may be ignored if you know the original Train Symbol.

It is important that you use this method rather than just re-applying a TSAR to the train. The player who applies the TSAR is assumed to be the originator of the train. Clearly if a TSAR is re-applied to a train it will invalidate this assumption. So in order that TrainFinder can track a train throughout it's journey from source to destination it is important that the originator and date/time as initially recorded (when the TSAR reference is set) are kept with the train.