The MVTrack can be used in both directions if the option One-way is disabled.
This option can only be used if the underlying sensor system generates only one event for a train. (Delayed off.)
If the reverse direction distance is not equal to the forward direction the second distance field can be used for the reverse distance. If left zero the first distance field will be used for both directions.
|s1||sensor one to trigger the measurement||ID|
|s2||sensor two to trigger the calculation||ID|
|distance||distance between s1 and s2||mm|
|distanceR||distance between s2 and s1||mm|
|scale||locomotive gauge/scale: H0=87, N=160…||-|
|mph||Miles Per Hour||true/false|
The sensors may also be used by a block; they both will get the events.
See also: http://www.rocrail.net/doc/rocrail-wrappers/wrapper-en.html#mv
If activated the selected loco will get informed of the measured kmh and will adjust its CV 5 value to match the wanted Max. km/h.
Multiple runs at the highest speed step are necessary to come close to the wanted result.
Depending on the hight of the difference between Vtarget and Vactual, CV5 will be varried.
If the used sensors will report a loco Code this will overwrite the selected loco ID in this dialog. (RailCom, RFID, …)
Note 1: The CV 5 will be adjusted by a POM write command.
Note 2: The CV 6 will be set by POM to 30% of the CV 5 value. (This percentage can be adjusted on the Loco Calibrate Tab.)
See also: Loco Calibrate
The measured value can be used with the rocrail variable %mvspeed% as Dynamic text in a Action of type "text".
The action must be called with status "in" in the action control of "MVTrack".
The example assumes that the text field txtSpeed is defined.
This feature, without calibrate, is also available in Blocks.
The measure value is than transfer in the rocrail variable %bkmvspeed% to the block action control.
In case of MPH the calculated KM/H is multiplied by 0.621371192.
Note: Trace level Calculation must be activated in the server.
A file with the name "mvtrack.csv" is created in the server working directory with the following content:
Time,TrackID,LocoID,TrainID,KMH,Velocity,Direction 20170529.151329.757,mvtrack,E03,robbie,123.3,0,fwd 20170529.151350.917,3,NS2418,,150.6,50,fwd
Remark: Unless the LocoID will not be forwarded by BiDi systems dynamically, "LocoID" = "unknown" is inserted (as well as "TrainID"). Example:
Time,TrackID,LocoID,TrainID,KMH,Velocity,Enterside 20190410.211945.699,mvtrack,unknown,unknown,101.2,0,- 20190410.213422.012,mvtrack,unknown,unknown,84.2,0,-
Shall the LocoID be displayed without use of BiDi systems, measure velocity track in the block must be utilized.