Interface

Content → Objects → Locomotives

• Index | General | Interface | Speed | Details | Functions | Multiple Units | CVs | BBT | SBT | BAT | Calibrate | Shunting Mode

LocoDialog Interface Tab.

If more than one command station is used, then the command station that is responsible for controlling the loc-decoder is specified in this field. The "Interface identifier" field can remain empty if the object is connected to the first command station (first 'digint' in rocrail.ini) from the list of command stations.

If this option is activated all Loco and Function commands will send to all connected Command stations.

See: Addressing

The decoder address which range depends on the decoder type and underlying Command Station.

• Attention: Contrary to the NMRA standard with addresses greater than 127, addresses from 100 must already be programmed in the Locomotive decoder as "long address" when controlling with Rocrail. For this it is essential to consider CV29/Bit5=1 and CV17/18 or do not use the addresses between 100 and 127
• Marklin mfx-Decoders may need special settings depending on the command station. See the wiki page of the relevant command station, if applicable.
• Locos with address 0 (zero) are considered to be analog locos without decoders which are only supported by TrackDriver (like Dinamo) systems. Address 0 is only accepted if the protocol is set to Analog, otherwise an error message will be displayed.
  "Stretched 0 Bit" according to NEM 670 is not supported.

The optional secondary address can be used for WIO or T4T (TrainCoupling&CommunicationSystem).

Some Command Station, like the ESU Ecos, are using an Object ID instead of an address for referring to a specific loco.
This field can be left empty because the Ecos library can also look up locos by ID or address.

Some command stations do support multiple protocols; Check the user manual for details.
If the address is set to zero the protocol should be set to Analog for Track Driver support.

Notes:
With Rev. 2.1.4466+ the term "Serverdefined" was replaced by "Default". Functionally, nothing has changed. Default, is the default mobile digital protocol used by the Command Station (CS). This setting is only of interest in case of multi protocol CS like Ecos/CSx(dcc/mfx). For a "DCC only" CS this option has no effect at all. Or for the Märklin 6051 its always Motorola.

If the Command Station cannot determine the decoder type itself the version must specify as listed in the SRCP description. Most systems do not use this parameter because it is set directly in the CS or it does only support one version.

Number of speed steps the decoder is set up to. Rocrail needs the number of the decoder's speed steps e. g. to be able to calculate the wanted velocity in percent or KM/H.

• The number of speed steps of the decoder, the command station and Rocrail must match otherwise the loco light (F0) may not work correctly.

The optional second speed steps can be used for T4T.

Number of extra functions supported by the decoder used. Default F0…F4.

The IP address and port of the locomotive its live streaming camera, which will be showed in the throttle dialog.
Supported streaming formats:

• HTTP
• Roco

The field in the middle is the number of frames to skip. This will reduce CPU power and fluency of the video stream.
Note: Frames will also be skipped if the graphic processing is slow, even if this parameter is set to zero; The video stream cannot be paused.

The field on the right is an option for the ThrottleDialog.

The Roco video locomotive must be configured in "Client Mode".
This can be done with the Roco Videolok utility.
The port must be set to 5152.
Note: It can take up to 30 seconds before the first frames are coming in after starting the camera.

• Demo: https://youtu.be/6A57b-VoOSw
• Camera Streaming
• ESP32-CAM

Note: If a train is assigned to the locomotive, and this train contains a car with a streaming camera, the camera of the car will be used instead.

Can be used:

• When this is an analog loco in combination of the Dinamo CS. (Check the documentation.)
• A WIO with the mobile option activated.
• A RocNetNode mobile decoder

A value of 5 is a good start to experiment with.

Some old Delta like decoders need some pause between a direction change and the last turnout command. With about 100ms this will do the trick.

XpressNet does not propagate loco changes issued by throttles.
By activating this option, and if the loco is not in auto mode, every second a request is send to the Command Station to get the actual information needed to update the Rocrail clients.
Use with care. This option is not recommended and not supported in the Forum, and uses unnecessary CPU resources.

Inverts the hardware running direction.
This is an alternative to program the direction in the decoder by CV29.

A flag for correcting the BiDi, RailCom, direction in case the decoders is not correctly polarised.
See also: BiDi Direction

If WIO as Mobile decoder be used, this can simulate Vstart and Vhigh, CV2/CV5.

Uncheck this option only if the decoder has accelerating and decelerating not implemented.
The interval is the time between the speed steps.

• Only available in combination with DCC and Trains.
• The max. load and the acceleration range must be set greater then zero.
• If the total train weight is zero the min. acceleration value is used.
• The new calculated acceleration value will be written by POM in CV3 after assigning a train or in case Car properties have been modified.
• The min. acceleration value will be written by POM in CV3 after releasing the assigned train.

MFX Protocoll - start-up delay (tested with CS2):

• Decoder mSD/3 - version 3.2 : CV178 index 1
• Decoder mSD - version 1.17.19 : CV78 index 1
• Decoder mfx - version 0.0.24.186 : CV78 index 1

The max. load for this locomotive in tons.

The CV3 range to use for loads between zero and max. load.

20130723.090557.995 r9999I cmdrD000 OLoc     2707 processing cmd="assigntrain" for [E03]
20130723.090557.995 r9999I cmdrD000 OLoc     2848 consist [train1] assigned to loco [E03]
20130723.090557.995 r9999I cmdrD000 OCar     0354 car [test] loaded weight [500]
20130723.090557.995 r9999I cmdrD000 OLoc     2026 loco [E03] adjust acceleration: CV3=16
20130723.090557.995 r9999I cmdrD000 OVirtual 0437 program cmd=1 mode=0
20130723.090557.995 r9999I cmdrD000 OVirtual 0465 POM: set CV3 of loc 1003 to 16...
20130723.090557.995 r9999I cmdrD000 OLoc     2079 loco [E03] train length=56 weight=500 

Deprecated

This option is not active and greyed out by default. It can be used for old-fashioned decoders offering no regulation and mass simulation.

• Regulated (see below) has to be deactivated in order to enable Interval.

The Interval merges in a pause between the decoder steps with a value of 1 corresponding to 100ms. With modern decoders this parameter is not needed and should be left to zero.

Tip: The Interval can be used to increase the deceleration / acceleration for decoders with a very limited tuning range. Some older Marklin locos with control potentiometers suffer from this limitation. Small interval values, e. g. in the range of 1 to 5, may help in this case. It should be noted that no other locos in need of automatic speed control at inclines (see Regulated below) are present on the layout and that in all blocks the type of incline should be set to "none".

If the decoder has motor management (BEMF) this flag should be set to prevent velocity changes by Rocrail when a locomotive enter a block defined as an incline block.
Deactivating this option activates Interval (see above) and automatic speed control at inclines.

Note: Rocrail is able to adjust the speed at inclines within certain limits in auto mode. The type of incline has to be specified in the block properties.

The following table gives hints on the impact of the parameters. It is supposed that the V_Mode-Percent-Option is not set and km/h is applicable.

Independently of the values in the table, the breaking will end at the speed defined in V_Min.

Hint: At interval = 10 the number of steps = time in seconds.
Higher values for Interval and/or Decelerate reduce the amount of necessary steps respectively speed commands.
This can help to avoid the above mentionned overload of the command station.

Example: At Interval = 5 and Decelerate = 5 the speed is reduced from 100 km/h to 10 km/h in 9 seconds with 18 steps respectively commands.
At Interval = 10 and Decelerate = 10 the reduction takes also place in 9 seconds, but with only 9 steps respectively commands.

Hint: The speed steps are not visible in the throttle, but only in the trace or on the real layout.