[RudyB]

The Gold version of Traincontroller has a built in graphics editor with which it is possible to modify, or create our own, icons.

Well ... it is an editor, but it has only limited functionality. You'll probably find yourself better off using an external editor and then copy-paste the pixels into the TC editor.

It can also handle transparency, but unfortunately it is not (yet) possible to import .png files (that have an 'alpha channel' for transparency). Often, copied graphics still need some fine tuning for the transparency inside the TC editor itself.

For icons, it usually works best to create and edit the largest size. TC automatically creates the smaller sizes. Usually this gives nicer and more predictable results than start small and then let TC enlarge.

About size:
- TC calls it 28 x 28 pixels.
- The actual grid is 27 x 27 though, because TC overlaps the grid blocks by one pixel.
- the editable canvas is 26 x 26 because TC keeps one blank pixel between icons.

A background image can be used to for instance create a 'switch panel'. For backgrounds, use the 27 pixel grid as a measure. Icons cannot be placed directly on a background image. First place them outside the image and then drag them onto it. Or, first place all images and then place the background as the final step. Also note that the top left grid block of a background image can not be covered by an icon.

The video has a short demo on how this can all work out. If you like to have a closer look at the panel ... the .yrrg file including the graphics used (with the LCD available in 4 colors) is available for download on the Blog's Software page.

Have fun.

Link to video Traincontroller 24: Graphics for Icons and Backgrounds




..

[RudyB]

We use physical sensors to let TC know an event has happened (mostly the event is that a train ran over the sensor, but there may be other uses like physical switches on a real control panel). But TC also has the option to use 'software sensors', so called 'Flagman', to let us know that a certain event has taken place.

A Flagman is a 'virtual man' who raises its 'virtual flag' when an event, or a logic combination of events, takes place. The flag is lowered again as soon as the events are not true anymore. In software terms, the Flagman is a memory location that can have two states: 1 or 0, TRUE or FALSE.

The events on which the Flagman should react are specified in the 'Trigger' tab of the Flagman properties (opened via a double click on the Flagman). It can be a single event, e.g. 'Block 6 occupied'. It can also be a logic combination of several events, e.g. 'Block 6 occupied' AND 'Block 7 occupied' OR 'Schedule 3 is running'.

What can we use Flagman for? Well ... actually for anything we can imagine. Whether you need them depends on the things you like to accomplish.

A simple use could be just for graphics purposes, as is shown in the video with the toggle switch.

Also, it can be very useful to start or stop certain Operations as soon as a logic combination of events becomes TRUE.

Flagman can also be used inside Blocks. When a Flagman inside a block becomes TRUE, then that block gets the status 'Occupied'. The video also shows an example on that.

Link to video Traincontroller 25: Flagman

[Wolfgang181]

hallo Stummifreunde,

super Sache mit diesem Thema,
leider ist mein Schulenglisch schon ziemlich lange her, wenn es diese Thema noch in Deutsch geben würde wäre ich einfach begeistert, so ist es sicherlich gut, aber für mich nur bedingt und mit einigen Anstrengungen zu nutzen.
Trotzdem an dieser Stelle ein herzliches dankeschön und daumen hoch

[RudyB]

Danke Wolfgang für deine positive feedback.

Rudy.

[RudyB]

In the previous video the Flagman was introduced. Flagman can be used to monitor a user specified status on the layout. As soon as that status becomes valid the 'red flag is raised' and a series of Operations can be started. When the status is not valid anymore the flag is lowered.

The status that we want the Flagman to monitor is specified in the Trigger tab. This trigger can make use of the status of almost every element available on the layout, combined with logical statements like AND / OR. Complex logic can be created this way.

The TC Gold version also has some further logic functions that make use of a counter:
- 'Exact (n)' means exactly n of the elements inside this group must be valid to become TRUE.
- 'At most (n)' means that max n elements must be valid.
- 'At least (n)' means that minimum n elements must be valid.

How Flagman and their possible complex trigger logic can be used is up to our own creativity and imagination and the goals we like to accomplish.

The video shows examples of all the logic groups available.

Link to video Traincontroller 26: Flagman Trigger Logic

[RudyB]

One of the logic functions that is available in TC Gold for the Flagman trigger, is the so called ‘Combi Group’. Inside a Combi we can place Blocks and/or Schedules.

The Combi becomes TRUE when a train is on one of the Blocks that is mentioned inside it. If a Schedule is also specified, then the Combi is TRUE when there is a train on a Block AND it is on one of the Schedules.

In stead of monitoring all trains, we can limit the Combi to only certain trains. This is done via the Train button next to the logic function dropdown, which shows only when we selected a Combi.

Actually we can do more than only use trains, we can use so called Train Descriptions. A Train Description can contain one or more trains, one or more wagons and one or more properties like speed or weight. This makes it possible to really focus the Flagman Combi group on a very specific train with very specific properties.

The video shows how the Combi Groups work in general and then how to create the Flagman that monitors if a certain train is driving. In the next video we're going to use these 'train driving' Flagman to update our Train counter.

Link to video Traincontroller 27: Combi Groups and Train Descriptions

[RudyB]

The Traincontroller Switchboard can have counters. We could use a counter to for instance show how many trains are in a hidden yard or shadow station, or how many schedules are active, or how many trains are actually on the move at any moment in time, or ... well, what ever you may like to count, up to how many mugs of coffee you had.

A counter has three parameters:
START defines what number the counter starts at after a reset.
ON defines at which count the switch function of the counter switches on.
OFF defines at which count the switch function of the counter switches off.

The switch function can be used to start Operations, or as a Condition or a Trigger in other Switchboard elements.

Up- and down counting is not done via a Trigger tab in the counter itself, it is done via an operation in any other Switchboard element.

A counter can also be clicked on with the mouse to count up. A right click opens a menu with the possibility to also count down, or reset the counter.

The video shows a counter for trains in a hidden yard and a 'running trains' counter.

Link to video Traincontroller 28: Counter

[RudyB]

In the previous video we had a look at the LCD counter for 'running trains'. The counter was triggered via Flagman. The other counter in the LCD panel, the Schedules counter, is triggered directly from the Schedules themselves, using so called Start and Finish Operations.

With every Schedule it is possible to specify a series of Operations to take place when the Schedule starts, before the train leaves. These can be train functions, like putting lighting on or off, or sounds in a sound decoder. It could also be other Operations though, actually the whole list is available via the 'List' button.

In a similar fashion Finish Operations can be defined, to be executed when the train has come to a halt at the end of the Schedule.

There may be cases where you like to specify the same list of operations to be used with different Schedules. In stead of having to enter the whole sequence multiple times, it is easier to define a so called Macro. The list of Operations now needs to be entered only once, in the Macro, which we can given an appropriate name. After having defined the Macro, it is now available for use in any Operations list.

The video shows how to create a Macro and how it is used in the Schedule Start Operations list.

Link to video Traincontroller 29: Start/Finish Operations and Macros

[RudyB]

In the previous video's we had a look at counters. They have the size of one icon, which can sometimes be a bit too tiny to clearly read. There's a larger, a 4x4, /Nixie Tube' counter on the switchboard. This is made using Extended Accessories.

These' EA's are very versatile and powerful tools. We can use them for nice graphics or for very versatile multi aspect signals or displays, and complex switching arrays.

When we couple a 'switch' connection to the EA, it functions as a combined multi state switch and multi state Flagman, sort of a 'Super Flagman', that can raise different colors of flags and start different Operations lists based on it's several stats.

In this video we'll have a first look at how to define an Extended Accessory and how to build the Nixie Tube 'counter' with it, which is actually not a counter, but a 4 state Switch/Flagman.

Link to video Traincontroller 30: Extended Accessories - Counter



..

[RudyB]

In the previous video we had a first look at Extended Accessories. We used it as sort of a multi-status flagman, to show different graphics based on different statuses, via which we were able to simulate a counter.

In this video we'll again have a look at Extended Accessories, this times used as switches. We can have multiple switches inside one EA. Every switch can have its own properties, and Operations and also Triggers, which at the same time make it act as a Flagman. This is shown with the 8 fold toggle switch array.

We can use the trigger for instance to 'arm' a button, we make it switch 'on' based on certain conditions. Then, clicking it with the mouse switches it off again, at the same time performing a series of operations.

This is shown in the video for a combined 'Schedule Stop' and 'Schedules Terminate' pushbutton. That is to say ... the graphics looks like a pushbutton, but it is an EA with two switches inside.

Link to video Traincontroller 31: Extended Accessories - Switches




..

[Speedy12105]

Hallo,

da muss ich dem Wolfgang recht geben. In Deutsch die Video´s das wäre der absolute Hammer. Kann man da nicht eventuell was machen ?

[RudyB]

In some cases it can be nice to start schedules by operating a switch at the start block, followed by a second switch at the destination block.

This can be accomplished via Autotrain, or when using our own defined Schedules.

The video shows how to set up both options.

Link to video Traincontroller 32: Start Schedules With Start-Destination Switches

[RudyB]

In can be nice to enhance a layout with physical signals, either just for some 'eye candy', or to get closer to a possible ideal to create a prototypical model railway.

The blocks in Traincontroller have 'internal' signals by default. These are used by TC to control train traffic. Physical signals on the layout do not have any function with regard to train control, they are merely there for the visuals.

The signals on the layout require some hardware. The lights, in my case, are red and green LED's. They are switched by a DCC function decoder. Via a DCC address the signal is switched form red to green, and back, by Traincontroller.

On my layout I use Arduino microcomputers as DCC decoders. One Arduino, which can be had for as little as $4,- , can control 16 signals, which makes it a very money efficient solution. The Arduino DCC function decoder software that is used can be downloaded from the blog, just follow the video link. The schematics for the LED's and for the optocoupler circuit can be found on the blog as well.

Two things are needed to get a signal that we placed on the switchboard working:
1: We need to tell TC to what DCC address the signal is connected on the physical layout.
2: The signal needs to be coupled to the internal block signal.

The video shows how this is achieved.

Link to video Traincontroller 33: Physical Signals on the Layout



..

[RudyB]

In the previous video we controlled a physical signal on the layout, using a signal symbol on the switchboard and connect it to a DCC address to control the hardware as well as connect it to an internal block signal for the switch logic.

If following the internal signals is all the 'eye candy' you need there could have been an easier way. Internal block signals can be connected to a DCC address themselves, there's no need to add additional signal symbols in that case.

But if you want to have a bit more control on the logic of when a signal changes aspect, then adding an additional signal is the way to go, because they have a Trigger tab as well as a Conditions tab, where logic functions can be built to control the signal's aspects.

The video shows both examples.

Link to video 34 Traincontroller 34: Internal versus External Signals




..

[RudyB]

To those who may have been following the TC video's and who might be interested in the graphics used with icons, extended accessories, control panel background and LCD screen ... the current status of the TC-Gold file including all the graphics is available for download over here:

Link to TC Gold file download.




..

[RudyB]

A quite common situation is that there’s a slow train at a station that wants to go on the move, but that an Intercity is approaching and you want to give this faster train priority to leave the station first.

The trick here is to use a condition in the Route of the slow train that says the Block of the intercity train must be not reserved. That way the slow train’s Schedule or Schedule successor will start, if there’s no condition preventing that and when the Rules are set to ‘Train may stay in start block’. The train will only start driving though when the condition for the Route is met … the intercity Block is not reserved.

The video shows how this can be accomplished.


Link to video Traincontroller 35: Fast Train Overtakes Slow Train.

[RudyB]

The block 'occupied' status and the corresponding highlight colour only appears as long as the block occupancy sensor is triggered. When working with momentary sensors, like I do with reed switches and magnets, the occupied status flickers as many times as the sensor triggers. Just because one reed often switches two times when a magnet passes over it and also bacause I have multiple magnets under my trains, used for driving backwards.

Page 138 of the user manual warns against potential problems when sensors are triggered multiple times by the same train. Although with me TC never got confused and traffic flow was error free, the messages window showed warnings of sensors being triggered when not expected.

Well ... I can't avoid multiple triggers with my sensors ... but there are ways to trigger the block occupancy indicator just once, like is advised. This is done by not using the sensor directly inside the block, but by using a Flagman in the block.

On page 292 of the manual a method is described using 2 detectors and a Flagman with its memory on 'toggle'. This method wont work for me, since I have only one sensor per block! Also my sensors are triggered more than once, which means this flagman will get toggled multiple times. This is not going to work .. I need to find another solution.

What I did is to use switches (one for every block, two for every 2-directional block) on the switchboard as an intermediate. It is switched on by the sensor, which is now an 'external;' sensor, it does not reside inside the block anymore. A flagman is used inside the block that in turn is triggered by the switch and that now determines the 'occupied' status.

The advantages are:
- The switch is switched on only once, no matter how often the sensor is triggered
- the flagman therefore is triggered only once ... absolutely no more multiple occupancy triggers
- the switch can be put off at any occurrence which we can choose ourselves. I chose to do it when the train reaches the stop marker of the block, that way I also can see if a train is driving (occupied is on) or stands still (occupied is off).

Combined with the block release Rule put on 'smart and upon entry' this gives nice early release of blocks and a nice flow of trains on the layout.

But switching the 'occupancy' switch off can be done via any other sensor on the layout or via an 'action marker' in any block, at exactly the point that is right for your situation.

Link to video Traincontroller 36: Block Occupancy with Momentary Sensors

[RudyB]

In the previous video we had a look at how to create flicker free block occupancy with momentary sensors. I used the stop marker as the point where the occupancy was taken away again. This has two advantages:

1. It is possible to see if a train is still running in the block (occupied = on) or when it stands still at the stop marker (occupied = off).
2. Use of the Schedule Rule for release of blocks and routes 'Smart or upon Entry' can be used to gain a high throughput of trains traffic.

In this video shows the difference between a few Schedule Rules for release of blocks and routes with some live footage of trains running.

Link to video Traincontroller 37: Block Occupancy and Release Rules




..

[RudyB]

This video shows several options to close and open a railroad crossing, both for a single track and for multiple tracks, and for the situation where the crossing is immediate behind a railway station where trains stand still.

Link to the video.

[RudyB]

Often we would like trains to enter a station at a certain track, for instance passenger trains always to track 1, cargo trains always to track 2. We could use a multitude of Schedules, one for every train (group) ... but we could also use just one schedule and add some conditions in the blocks.

This video shows three scenarios that all use just one schedule that has multiple destination blocks.

1. Trains drive into the station always at lane 1 first, then 2, then 3, etc.
2. Specific trains drive into specific lanes.
3. Passenger trains always drive into lane 1 and go to lane 2 only if 1 is occupied. Cargo trains the other way around.

Link to the video




..

[RudyB]

It is quite easy to create automated train traffic in Traincontroller, by having trains run on cycle- or shuttle schedules and by using the option that a schedule can start one or more successors at it's finish.

Another way of automating traffic would be the use of timetables. Both ways can also be used intermingled.

A timetable is merely a list of schedules and macro's that are going to be executed at their given date / time. The ability to use the date makes it possible to create 365 different timetables. Which one is run, is selected by the date field in the timetable window. This date is your layout's 'fake' date ... it is entirely separate from the current real world date.


Link to video Traincontroller 40 - Timetables

[RudyB]

Traincontroller 41 - Loading Wagons Based on a Timer

Some model railways (like to) simulate the loading or unloading of bulk goods. The task at hand is to stop the train with the first wagon accurately under the silo, wait a few seconds, then advance the train exactly one wagon length ... and so on until all wagons have had their turn.

Often a hardware sensor is used to detect the gap between wagons. Its signal is used to stop the train when it is advancing. If the following criteria are met, there’s no need for a sensor, we can simply advance the train with a given speed for a given time.
1: the engine runs smooth and stable at low speed.
2: the number of wagons in a train does not change during a session.

This video shows this time based solution. With the tests I performed this proved more than accurate enough. The next video will show the solution with an additional wagon sensor.

This video shows this way of working based on a timer The next video will show how to do it with a wagon sensor.

Link to video Traincontroller 41 - Loading Wagons Based on a Timer

[RudyB]

Traincontroller 42 - Loading Wagons Using a Sensor

In the previous video we simulated wagon loading by advancing the train one wagon at a time, using a fixed speed during a certain amount of ms. This is accurate enough if the engine runs stable at low speeds and if the number of wagons in a train does not change throughout a driving session.

If one of these conditions is not met, we can use a sensor to detect the wagons. This could be a light beam sensor that triggers if it sees the gap between the wagons, or a reed switch on the track combined with a magnet under every wagon, or a very short stretch (1/2 ") of current detection and a resistor on an axle of every wagon. The end of the train is assumed if no new wagon is detected after a given number of seconds.

Link to video Traincontroller 42 - Loading Wagons Using a Sensor



..

[RudyB]

September 2017 version 9 of Traincontroller was released. Time for a few new video's about the new features that version 9 has to offer.

This first video is about the new User Interface.

Link to demo downloads, user manual, more info and the video.




...

[RudyB]

One of the new features of TC9 are the Pins that can be shown on the switchboard. There are three categories:

1: Dr. Railroad pins. Dr. Railroad is the diagnostic tool that scans your layout for issues. In stead if presenting them in a list, they now also can be shown on the switchboard as pins. They quickly pinpoint you to the location on your layout where something is wrong or is missing.

2: System pins. These come in handy when debugging Schedules. In red and yellow they highlight places where the Schedule is restricted. Green pins show all the spots where the Schedule makes reservations.

3: User pins. These are used as 'sticky notes'. You can attach User pins to items on your layout and write text in them. Handy if you like to remember why you did certain things the way you did them, or if you are in the process of building a new layout and you like to have a couple of To Do memo's for the next time you will be able to work on it.

[url= https://www.youtube.com/watch?v=blI20Gr1...player_embedded]Link to video.[/url]