With the help of balises (ID transmitters), a basic automatic operation can be set up. To do this, commands are assigned to the balises, which are interpreted by a locomotive equipped with an ID reader when it passes the balise. Balises and ID readers are available for CTC based on IR (infrared) and NFC (RFID). For the following considerations, there is no difference between IR and NFC.
Note: The functionality described here requires the CTC app from version 4.00 and associated locomotive firmware as a prerequisite. Signals and triggers of balises (ID transmitters) configured with older CTC versions must be adjusted. Most of the time, it is easier to remove the relevant lines under “Connected Products” in the Config-Dialog and then add them again.
The basic components of automation with CTC are:
- Driving orders
- Blocks
- Routes
- Timetables
Blocks/Track Sections (Block)
In real railways, blocks are the basis for preventing collisions between trains. The entire track plan is divided into individual blocks (track sections). Turnouts (junctions) may only exist between blocks.
Understanding how block-based model railway control works is essential for understanding automation in CTC. This concept has been nicely described by Dominik Mahrer on modellbahn.mahrer.net.
Signals
Signals, in conjunction with balises (ID transmitters), worked as real train control already in CTC version 3.
If a balise is linked to a signal, it transmits the status of the signal (e.g., Stop) and its distance to the locomotive, which responds accordingly (e.g., stop before the red signal).
With CTC Version 4, it is also taken into account the direction of travel of the locomotive, so it only stops before the red signal if it applies to its direction of travel.
Also, the distance from the ID reader to the front and rear end of the locomotive can be defined within the locomotive. This distance is taken into account during target braking.
By the way, signals are allowed to exist purely virtually, i.e., they can only be seen on the track diagram. No signal is then installed on the layout.
Controlling Signs
Instead of signals, you can also use signs. A sign is added as a product to a turnout like a signal, but does not appear on the control panel and therefore cannot be changed during operation. A sign has no connections, but parameters to determine the sign’s meaning.
With signs as well, you have the option of setting them up virtually, i.e. you only see them in the track diagram. As a result, no sign is put up on the layout.
Paths (Path)
A path establishes a connection between two blocks by appropriately switching all the turnouts in between and finally opening the departure signal of the starting block.
When switching the path, all affected turnouts, signals and blocks are reserved and only released again when a locomotive reaches the block at the end of the path.
Driving Orders (Job)
A typical driving order is the journey from one station to another, possibly with intermediate stops.
The simplest form of a driving order is just a sequence of routes to be switched.
For automatic operation, the driving order can be supplemented with balises (or more precisely their three-letter IDs), which a locomotive should approach in chronological order. A command can also be assigned to each balise.
If the balise also emits a command (e.g. stop in 60cm), the locomotive decides whether it executes the command sent out by the balise or the command recorded in the driving order. For example, a stop always takes precedence over a speed reduction.
A driving order with balises always applies to the locomotive standing in the starting block of the driving order.
Schedules
A schedule is a collection of driving orders that are started at times specified in the schedule (model time). In this way, full automation can be configured.
Configuring Locomotive Sensor
In order for the locomotive to be able to perform a targeted braking, it needs to know how far its ID reader is from the start or end of the locomotive. This is where the two new parameters “dFront” (front) and “dBack” (back) of the ID reader come into play, which define the distance of the ID reader in cm.
Note: When dealing with shuttle trains with the locomotive at one end of the train, when placing your balise on the track, you need to consider that in reverse driving, the ID reader is quite far away from the start of the train.
Processing Events (Triggers)
With so-called triggers, you can respond to events (or state changes) on your model railway, e.g.
- A turnout was switched.
- A signal turned red.
- A locomotive passed a balise.
With a trigger, you determine how to respond to which event. The trigger is always created at the action to be changed by it. You can find out more about this in chapter 4.3 - Linking actions.
Examples
In the following, some typical applications of automation are briefly described. In the “Articles about CTC”, we will gradually publish more detailed descriptions.
#
Automatic Stop at the Signal
For a CTC locomotive to automatically stop in front of a red signal, a balise is installed in the track at a sufficient distance from the signal. Both the actual braking distance and the distance of the ID reader to the beginning of the train need to be taken into account.
The balise is then linked to the signal and thus each time sends out the state of the signal as a command. The distance to the signal is entered in the trigger’s config. How to configure a trigger can be found in Chapter 4.3 - Linking Actions.
For correct functionality, it is important that the correct direction was chosen when configuring the signal. This is because the locomotive only reacts to commands corresponding to its direction.
Note: By direction of the locomotive, the adjustable driving direction (forward/backward) on the control panel is not meant, but whether it is moving clockwise or counter-clockwise. The locomotive determines this direction from the read IDs. #
Automatic Stop with Two Balises
By placing a second balise directly before the signal, you can achieve the locomotive stopping within a few millimeters accuracy. Here, the command “minimal speed” is sent from the first balise with a distance shortly before the second balise. The second balise then immediately (at 0 cm) sends out the command “stop”.
Especially when stopping in sidings, this has the advantage that the locomotive stops above the balise and therefore knows immediately where it is the next time the model railway is switched on.
#
Stop
A stop at a station is achieved by using two balises. The first one informs the locomotive to slow down to minimum speed shortly before the second balise. The second one then transmits the “Stop” command and how long the locomotive should wait before it continues. Alternatively, the “Reverse” command can be used, where the locomotive continues in the opposite direction after the waiting time.
The commands can be permanently assigned to the balises or transmitted via the locomotive’s drive order.
Alternatively, the locomotive can also be stopped by a signal and only continue its journey with the next entry in the timetable.
#
Shuttle Train
A shuttle train is enabled by at least two travel orders, namely, outbound and return trips. These are then inserted into a timetable as often as desired.
#
Scheduled Operation
For scheduled operation, individual driving orders are first created. These can then be individually tested.
Following this, a timetable with departure times is created from these driving orders. Individual driving orders may be used any number of times in this process. However, you must keep in mind that a driving order will only be carried out if there is a locomotive in the start block of the driving order. Depending on which locomotive has been moved to the start block by other driving orders, it is entirely possible that the same driving order will be executed by different locomotives at different times.