SMM SafeTran \ Lincoln Signals - Version Beta 1.5 - Online Manual

Authored by Jerry Conaway

NS Rules Scripted by Tim McIntosh. USDEF Rules by Kuju/RSC

Updated 2010-1206-0341

Index:
2 - Introduction
2 - Before You Install
3 - Known Issues
3 - Installation
4 - How These Signals Work
5 - Signal Types
8 - Signal Naming
11 - Signal Installation and Linking
12 - Credits

NOTE: This manual pertains to both the NS and USDEF version of this asset. The only difference between the two is scripting. The NS version uses scripting by Tim McIntosh to emulate operations of the Norfolk Southern railroad company. The USDEF version is “plug-n-play” capable with existing Railworks signals and scripts.

This asset represents trackside train traffic control signals of a type built by both SafeTran and Lincoln Industries. The signals were built and installed on the Norfolk Southern Railway in the later half of the mid 00’s. These signals represent the newest railroad traffic control devices in use today.

The prototypes for these signals can be found at Oostanaula, GA, and Cohutta, GA.

Before You Install...

Before you test this packaged asset, there are a few things you need to know:

- This is Beta version software. It has never been tested in limited release. However unlikely, there is still a possibility that it may damage your Railworks program, or even damage your computer. If you do decide to install this package, you do so at your own risk, and the developer of this Asset assumes no liability for any incident arising from it’s use or misuse.

- This version is Work In Progress, meaning it may differ in appearance and function from the final release.

- LICENSING: As of April 2, 2011, the author of this asset will allow the following uses by the End User:
- Modification of the signal shape file (GeoPcDx), texture files (TgPcDx), and .bin files in order to suit the needs of the End User and/or the Railworks community.
- Upload and distribution of the MODIFIED asset to sites that feature Railworks content or to personal websites that feature said content. The asset must still be offered free of charge, and credit must be given in the README files for the modified asset to the original author. Do not upload the original, unmodified assets, as I like to keep track of their downloads from SMMDigital.net
- Use as an attached asset, in modified or unmodified form, on freeware Railworks routes, meaning routes that are produced by an individual or individuals for distribution without monetary gain.
- Use as an attached asset, in modified or unmodified form, on payware Railworks routes, meaning routes that are produced by an individual or individuals for distribution for monetary gain. If you do use this on a payware route, please consider dropping a few coins in the SMMDigital tip jar!

The above Licensing Agreement supercedes all agreements contained within READMEs or Manuals that have been previously distributed. It is extended to the unique assets that were made for the NSAND route, but not to the route itself (i.e. you can use, change, and distribute the assets with the SMM prefix, but you cannot change or redistribute the actual route).

---

Known Issues

- Do not mix the NS scripted signals with the USDEF signals. This may result in unpredictable signal / AI behavior on your route.

- Permissive signals are denoted by a number board (gantrys) or numbers permanently attached to the signal (masts). These numbers are not dynamic and are set at 000. On the prototype, this would be the same as a milepost marker. But since I have no idea what the milepost for the signals will be on your route, I simply used a generic number. Future revisions of the number boards may include dynamic numbering.

---

Please note that the different signal types are stand-alone installations and do not share assets or textures.

Installation – NS Version

- Find the folder where the SMM_SafeTran_NS.zip is located. After running a virus scan on the file, unzip the contents of the file to the folder of your choice.

- Open the Railworks Packager and click on the “Install” button. Navigate to the folder where the unzipped SMM_SafeTran_NS.rwp is located. Choose the .rwp and click on the install button again. Follow the prompts.

- After you open Railworks and the World Editor, make sure that "SMMDigital" and "RailNetwork" is checked under the Object Filter.

- You will find these Assets under the "Modern Signals" category.

Installation – USDEF Version

- Find the folder where the SMM_SafeTran_USDEF.zip is located. After running a virus scan on the file, unzip the contents of the file to the folder of your choice.

- Open the Railworks Packager and click on the “Install” button. Navigate to the folder where the unzipped SMM_SafeTran_USDEF.rwp is located. Choose the .rwp and click on the install button again. Follow the prompts.

- After you open Railworks and the World Editor, make sure that "Kuju" and "RailNetwork" is checked under the Object Filter.

- You will find these Assets under the "Modern Signals" category. These assets install to the Assets/Kuju directory.

Change Log

Release 1.5 Final – 2010-1206
- Removed cantilever and signal bridge from package.

Release 1.2 Beta – 2010-1124
- Released signals that will function with the default RW signal system.

Release 1 Beta – 2010-1118

---

How These Signals Work.

I have limited knowledge of the operations of the signal scripts for Railworks. The best resource for building your own signal system using this asset is the “Pikes Signal Pack for Railworks v2” PDF that is included in “Railworks NS, NORAC, C&O, & CSX Signals” package. This package is available in the file library at Trainsim.com, and it tells in depth how to set up these signals so that trains can move properly through routes in the sim.

---

Signal Types

This package contains several different signals to meet most of your signaling needs.

Various 2 and 3 head signals.

Bi-Directional (some assembly required)

Two and three-head gantry mounted signals.

NOTE: NS and USDEF signals will differ significantly in operation and choice of signal types. The 2H 13 * (Two head 1 over 3 aspect) signal is not available in the USDEF package.

---

Signal Naming

PLEASE NOTE: The signal naming conventions used for the Griswold Signals will differ from those listed in the “Pikes Signal Pack for Railworks v2” PDF. That manual was written for different signals, but will still have information pertinent to the Griswold signals.

This signal pack does not contain the RW short (what they call Dwarf) signals. The signals in this package are equivalent to the “Tall” signals used in RW. Also, the “Head” signals have been combined into Gantry post signals.

The signal naming conventions go somewhat as follows:

SMM_SafeTran - Name of the manufacturer of model and prototype.
USDEF – Signals for default Railworks signal system. If this is not present, then signals are NS-Rule.
G - Gantry Mount. No letter prefix for non-gantry signals.
H* - Number of heads on the signal.
T* - Number of signal links to track.
P – Permissive block signal. Will be denoted by a number placard attached to the signal mast. Read the “Pikes” manual for more information on this signal.
R – Restricted signal. This is the same as the “E” signal in Railworks. This signals is used EOL when no more signals will be beyond this one. A number after the R designates multiple links and how many of them will be restricted.

Example: G H3 T3 R2 – This signal is a gantry mount, 3 Head, 3 Link signal, with the last two links leading to the end of the line or an unsignaled yard.

Signals that do not have a “P” or “R” at the end of their designation are Absolute and must stop the train and hold on Red.

Signal Identification

Tool-Tipping has been enabled for the NS-Rule signals. Simply hold your mouse cursor over the signal name in the Signal ID box to easily identify which signal you want to choose.

---

Signal Installation and Linking

Linking of signals takes some time to master, but if you do it wrong, your signals will not operate in sync, or worst case, will not work at all. The following procedure should be followed to install signals on your route:These are simple linking instructions. More details on setting up these signals is contained in the “Pikes Signal Pack for Railworks 2” PDF:

- Choose a signal from the Signal Object filter.

- Place the signal beside the track at the point where you want your track block to begin.

- If using a single-link signal, place the link on the track next to the signal base.

- For a double link signal, place link 0 at the base of the signal, and link 1 a bit further down the tracks.

- For setting up a turnout signal, place a signal with three links (T2) before the turnout. Place link 0 at the base of the signal. Place link 1 on the mainline beyond the turnout frog. Place link 2 on the siding beyond the turnout frog.

- Rotate your signal into it’s final position.

- - F2 the World Editor to save your results.

Signal Placement Tips

Here are a few tips that I have learned to help make a more realistic signal system:

- Do not place links “inside” the business area of a turnout (i.e. near the points or the frog). Placing links within these areas will cause the signal to malfunction.

- Keep in mind when placing this signal what you might want the next signal to do. For example, at a certain spot on a single track mainline, you want to place a signal. Further down the line is a passing siding. You know at the passing siding you need a 3H 2T signal. Since signals communicate their status to one another, do you want a signal on the main that communicates conditions at the siding down the road, or do you want a simple single link signal that will simply give a clear signal, no matter what the conditions at the siding?

- It may help you to spend some time observing signal conditions on a prototype Railroad.

---

Conclusion

If you have comments or suggestions concerning this project, please contact me at betatesting@smmdigital.net. I will not answer postings or private messages left through Forums or other internet portals. Due to the volume of mail, and the fact that I do have a life outside of simming, I will not be able to answer every piece of mail that I receive.

Please note that although a third party has provided the modified script for these signals, they are not expected to provide support for them. Please e-mail any questions you might have to the above mailing address.

---

Credits

Technical Assistance

Tim McIntosh ("Pikehkr"

Scripting

Alex Riley (“Trainguy76”)

3DCanvas Technical Assistance