I agree that this would be useful.
It is true that a closed loop interface with the loco would be the best
solution. But I bet most people will not take the time to do anything
that complicated. I expect most people would simply mark two points on
the layout with a known distance and time it. Hence I would go with the
easiest approach and let the user determine how to make the speed
measurement. In the programs most basic form, the user enters the known
test track length. At most it would provide a timer function where the
user hits a key to stop and start the timer and which time when it stops,
the speed is calculated.
But I propose something more MANUAL but elegant from a user point of
view. Here is how I think the program should work from this point of
view. (Clearly other more Automatic operation modes could be supported
at the same time.)
PROGRAM OPERATION:
The program starts and a user enters a locomotive address to be tested.
Speed is set to zero and user is instructed to place the locomotive on
the test section. Clinking that window away, the locomotive database is
called up and a pane pops up showing the current speed steps along with
Kick, Start, Mid and Max values.
The user is then told that the Acceleration and Deceleration CV will be
set to Zero and restored when all the test are done. (this may be
presented as a choice to the user with a note as to why)
The user is then presented with two mode of operations. Continuous loop
running or back and forth. (more on that later). If not save in a
preference file, the user is also asked for a the distance between the
two start and stop points of the test section. If it is a loop, you
could also provide a calculator for the length in the program.
Obviously the longer and straighter the test section, the more accurate
the measurement. But in most cases, people are more interested matching
the locomotive relative speeds as opposed to making a speed step match an
accurate scale speed. Anyway....
The user is then given the choice of setting one of the following test:
1) KICK, START V, 1st SPEED TABLE setting
2) START V, MID V, MAX V
3) SPEED TABLE.
The program then opens to a panel with a manual throttle and the
appropriate variables shown.
===========
TEST #1 (KICK)
This test should be run first for it can effect the results for Start
Voltage or the lowest speed steps in the Speed Table. The window open
and presents the START V and the first Speed Step of the Speed table.
(The user need to make sure the track is clean!) The user must then
choose START V or 1st Speed Table value to be set. The program then
enables the value chosen by turning off or on the speed table setting.
The test comes in two phases. First phase is Setting the Start Voltage
or First Speed Table value. Second is setting the kick start value.
The concept behind this test is to first establish the minimum speed that
can be sustained coming down from a running position so that Kick start
is NOT involved. Once the values for START V or 1st SPEED TABLE variable
are determine, we go to Kick start phase. Here the kick start value is
adjusted so that from a stopped position, the first throttle speed step
setting gets the locomotive to run reliable at the value established by
in the first phase.
First Phase:
The engine is placed on the test track behind a marked starting point.
A) From a stop condition, the clicks on the START button which starts the
test by starting the loco. The loco starts at a medium speed that is
high enough to guarantee motion. A timer is started to prevent runaway.
If the timer times out, we go to D step.
B) The users Click the TEST button which then changes the the Speed Step
to 1. The Countdown timer is re-started to prevent loco runaway if there
is no response on the next step.
C) The user is then asked to observe the locomotive and click one of two
buttons labeled STALLED or MOVING on the screen. The locomotive is
stopped when a button is pressed or the timer times out. If the MOVING
button is pressed, we skip to step G If the time times out, we got to
step H.
STALL BUTTON IS PRESSED
D) If the Stall Button is pressed, the user is asked to PRESS the VERIFY
KEY. The VERIFY key sends a new speed step value that would guarantee
the locomotive should move. A timer starts to prevent runaway again.
E) The user is then asked if the locomotive started again. IF yes, then
the STALL is verified because the CV value is to low as opposed to dirty
track. Proceed to Step F below. IF no, then the test must be repeated
by first fixing the locomotive via a note to the user and then proceeding
to step H
STALL VERIFIED
F) If the stall is verified, the CV value is reset to the PREVIOUS value
which we knew the Loco DID NOT stall at. The system then restores the
Accel and Deceleration CV's. The user is told the Test Phase 1 is
complete. Goto step H.
MOVING BUTTON IS PRESSED.
G) If the moving button is pressed, then the CV value is lowered in
preparation for the next test.
RESET TEST
H) The user then holds down a key which reverses the engine back to the
starting point again. Releasing the key stop the engine. IF the test is
NOT COMPLETE we Goto Step A. ELSE we exit to second phase.
----------------
Second Phase: KICK START
The kick start value is first set to 1.
A) From a stop condition, the clicks on the START button which starts the
test by setting the speed step to 1. A timer is started to prevent
runaway. If the timer times out, we go to H step.
B) The user is then asked to observe the locomotive and click one of two
buttons labeled STALLED or MOVING on the screen. The locomotive is
stopped when a button is pressed or the timer times out. If the MOVING
button is pressed, we skip to step G. If the time times out, we got to
step H.
STALL BUTTON IS PRESSED
D) If the Stall Button is pressed, the user is asked to PRESS the VERIFY
KEY. The VERIFY key sends a new speed step value that would guarantee
the locomotive should move. A timer starts to prevent runaway again.
E) The user is then asked if the locomotive started again. IF yes, then
the STALL is verified because the KICK START value is to low as opposed
to dirty track. Proceed to Step F below. IF no, then the test must be
repeated by first fixing the locomotive via a note to the user and then
proceeding to step H
STALL VERIFIED
F) The KICK start value is too low and must be incremented by one and
the test repeated.
MOVING BUTTON IS PRESSED.
G) If the MOVING is verified, the CV value is correct. The system then
restores the Accel and Deceleration CV's. The user is told the TEST IS
COMPLETED. Exit.
RESET TEST
H) The user then holds down a key which reverses the engine back to the
starting point again. Releasing the key stop the engine.
=====================
TEST #2 (STRT,MAX) and TEST#3 (SPDTBL)
For Test #2 and #3 above, the user chooses which variable to be tested or
adjusted. If TEST#1 was performed, the STATV and First Speed Step are
locked out by default. The user is given the option of unlocking them.
Also note that when the timer is running, the user is not allowed to
adjust any values. Only stop is allowed. The program then proceeds to
the test phase.
Test Phase:
As mention before, I see two operator modes of operations. LOOP and
BACK AND FORTH
The engine is placed on the test track at one end before the start mark.
From a stop condition, the user Hits (pressing momentarily) the control
key starts the test by starting the loco.
1) LOOP. The engine is place on a section of track in a form of a loop.
A) The users hit the key again to start the timer when the loco passes
the mark.
B) When the loco passes the same mark after completing one pass around
the loop, the key is hit again, the timer stops and the speed is
calculated. However the engine continues running around the loop in
preparation for the next test. During this lap, the user can change the
CV value.
C) Go to step A above.
2) BACK AND FORTH. This simply means that the engine is on a section of
track that is not continuous. The engine must go back and forth to be
tested. (This would work for loop too and might be faster!) Here is the
procedure:
A) The users hit the key again to start the timer when the loco passes
the start mark.
B) When the loco passes the stop mark, the key is hit again, the timer
stops and the speed is calculated. At the same time the engines is also
stopped. The user can change the CV value at this time.
C) Press and HOLDING the key again allows the engine to move again in the
same direction but at a slow speed to make sure it goes past the mark in
preparation for a run in the opposite direction.
D) Releasing the key stops the engine then changes direction and starts
the engine again.
E) Go to step A above.
Pressing the key twice in a row in quick succession stops the test and
restores the Accel and Deceleration CV's. A Display always tell the user
what state the system is in a what to do next. The idea is to make as
much of the control hands off as much as possible.
So there it is.......
Mark Gurries
Michael Mosher wrote:
I've been contemplating creating a program similar to Racetrak that talked
through a MS100 or LocoBuffer to the command station instead of driving a
booster directly. That would be much more convenient to me and for the
club. Also since the club has a Toth speedometer, I was think of making a
option to use the speedometer in place of the master loco. i.e.:
"For speed step xx (CV yy) adjust the speed of test loco until the
speedometer reads zz"
But since I don't know java, I would write it in C, probably using John's
LN1 interface.
I think the only tricky thing would be the option of filling in blank values
using existing known values.
----- Original Message -----
From: "David Harris" <dpharris@...>
To: "jmri" <jmriusers@...>
Cc: "John E. Kabat Jr." <sljkrr@...>
Sent: August 13, 2002 09:53 AM
Subject: [jmriusers] Racetrack
Hi-
My oNeTrak club now has its act together getting our modules finished
and connected to the NTrak club's modules. We would now like to MU some
engines together. (I in particular, as I just installed some decoders
into three SD40-2s :-) However, getting two engines to perform
similarly is harder than you would think. Fortunately, there is a
program to help: Racetrack (see:
). I have asked John Kabat if
he supported the DC100 or Locobuffer, but unfortunately, he is not
supporting the program at this time.
I think a Racetrack module would be great for JRMI. Before I start, has
anyone done this or do any of you have some suggestions?
David
Best Regards,
Mark Gurries
Linear Technology
Power Supply & Battery charger Applications Engineer/Manager
---------------------------------------------------------
Model Railroad Club and NMRA DCC presentations are at:
--------------------------------------------------------
Audio Enthusiast (Love SAE equipment)
----------------------------------------------------------
Bob Jacobsen