User Tools

Site Tools


Tams MasterControl & RedBox


Choose Rocrail Properties… in the menu File and continue to change to tab Controller in the displayed window. If Tams MC/RedBox shall be sole controller, all other existing controllers have to be deleted from the list. Opening the menu New the controller tamsmc is chosen and subsequently added to the list by pressing Add. In order to parametrize the controller mark the line NEW - tamsmc and click on Properties. The window TAMSMC opens:

Properties for controller type tamsmc
All given values are exemplary!

Interface ID

The interface ID NEW may be replaced by a proper ID, e. g. TAMS-MC or RedBox.


The interface to which MC is connected can be selected in the drop down list and is written into the field Port, e. g. COM4.


The type is fixed to tamsmc.


With this parameter the data transfer rate is configured. The controller supports values of 1200, 2400, 4800, 9600, 14400, 19200, 38400 or 57600 baud. If an USB interface is used, 57600 baud are used exclusively.

Hardware Flow

Configuration of hardware flow. Use of CTS is recommended because the controller supports CTS flow control. Only deactivate flow control in case it is an USB connection and the USB driver does not support CTS.


This parameter configures the max. length of delays which, as the case may be, Rocrail has to consider between commands to the controller.
For using the Programming Track, PT, this value should be set to 4000 to give the MC time to scan the acknowledge of the decoder.

In case commands to the controller get lost ("Error on mutex, trywait …"), raise the value to 4000 ms.


In the sensor part one can set the number of connected s88 modules and how to scan for changes (Polling).

Note: Also make the necessary settings in the Control station :!: (e.g. RedBox with CV-Navi)


Define here the number of 8 port connected modules. Some modules have 16 ports, so you have to multiply it by two in that case.
In case of using p50 it is necessary to enable event polling. P50x does not support unsolicited events.
If the number is set to zero, no sensors are polled.


No description available.


Default: 200ms
In case the option "Poll" is deactivated Rocrail scans regularly if the controller has sent changes of sensor states. The time between these scans (sleep) can be set here.


No description available.


Setting this flag will poll for sensor events every 200 ms. Since Tams MC supports the p50x protocol, with which sensor events are transmitted automatically, this option should be deactivated!


No description available.


No description available.


Programming track

The new introduced tamsmc library has implemented the programming track instruction in the p50xa format.

The PT mode must be set in the programming Tab before reading/writing CV's. This will stop polling the s88 to avoid read CV read errors.
Do not use this mode in automatic mode because it blocks sensor events and system status which will lead to accidents.

System info

No description available.


No description available.


No description available.

Overrule throttle

No description available.

Echo commands

Echo switch commands. Since the command station does not give feedback of the switch position, this can be simulated by activating the option.

This is needed, for example, when two switches with the same address are connected together to one decoder output. In this case the correct position of both turnouts can only be displayed correctly by the clients (Rocview, …) if this option is activated.


No description available.

Switch time (ms)

See below.

Loco decoder setup

With the Send button the decoder setup can be stored in the MC/RedBox.

Decoder protocol Version Speed steps CV-Navi code
Motorola 1 14, 27, 28 MM1
Motorola 2 14, 27, 28 MM2
NMRA DCC - 14, 27, 28, 126 DCC

The decoder definitions are listed up in the CV-Navi utility.

Configuration advices


With the CV-Navi Tool the MC and RedBox can be configured and maintained.

Switch time

The switch time of switches or solenoid-operated switches can be set in the Tams MC itself (see manual).

The effective switch time value is configured in Tams MC, not in Rocrail properties: For single switch commands the maximal switch time is used. If more commands are sent consecutively (e. g. set of train route), the minimal switch time is used.

Example 1:

  • In MC the switch times are configured to min. 200 ms and max. 500 ms.
  • In Rocrail the switch time is configured to 100 ms, the route switch time is set to 10 ms.

If only one switch will be set, the actual switch time is 500 ms.
If a route with a couple of switches will be set, the actual switch time of a single switch is 200 ms.

Example 2:

  • In MC the switch times are configured to min. 200 ms and max. 500 ms.
  • In Rocrail the switch time is configured to 250 ms, the route switch time is set to 300 ms.

If only one switch will be set, the actual switch time is 200 ms.
If a route with a couple of switches will be set, the actual switch time of a single switch is 200 ms. There is a delay of 100 ms (300 ms - 200 ms) between the switch commands.

The switch times should be configured advisedly. As the case may be the minimal and maximal switch time has to be set to the same value in the MC. In case the Route switch time in Rocrail is considerably shorter than the minimal switch time in the MC, it may happen in layouts with switches without position detectors that a train starts before the route was set completely and properly.
Init field pause should be set to twice the value of (two switches at initialization!) minimal switch time in the MC.

Reduction of amount of commands

Too many commands in a short time period may lead to complications with Tams MC (as with other controllers), which show up in error messages "error on mutex trywait" and occasionally lost commands.

It is recommended to reduce the amount of commands to the controller and to slow down the sequence of the commands. For this purpose the following Rocrail settings come into consideration:


Emergency break

Question: Tams MC is in modus STOP and EMERGENCY BREAK is pressed, Power is switched on and MC shows HALT on its display. Why is the power switched on?
Answer: In modus STOP power is switched off completely. In modus HALT power is on track, but all driving positions are set to 0. Thus all locomotives come to a stop. This characteristic complies with DCC norm.

p50x-tams-en.txt · Last modified: 2023/09/17 08:49 by rjversluis