When a new engine is brought to our layout and we ‘throttle it up’, the speed at which it moves at every DCC speed step is unknown. To know the engine speeds, they need to be measured. This is done by measuring the time at takes to travel a given distance. This results in a scale speed in m/s. Given the layout scale (N, HO, O, …), this is then translated to ‘real world’ speed in km/hr. Traincontroller has a built in function to automatically perform these measurements at different DCC speed steps. This is called Speed Profiling.
What is the use of speed profiling our engines?
Well … first of course to have our on screen speed gauges show the correct km/hr values.
But more important, to have accurate brake- and stop distances, in cm. One and the same engine, with the same block entry speed, will repeatable stop at the same spot. But it’s probably not the point that we specified in cm. Also, different engines, and different block run in speeds, will give different stop positions. Absolute accuracy can only be accomplished when engine speeds have been measured.
After my engines were profiled, the stop accuracy, measured over different engines and over different speeds with which they drove into the block (20, 40, 60 km/hr), was well within +/- 2 cm, as the image shows.
The video shows how to prepare the engine’s CV values, how to prepare the mearurement track, how to perform the speed profiling and finally, how to do measurements to fine tune the ‘brake compensation’.
A PDF with a step by step ‘cook book’ explanation is available via this link: Traincontroller_Speed_Profiling