Cab2 recording feature

Did you stop the train in exactly the same place you started at? If not that's the reason why. 

Yes I did and after each stop , the train advances a little forward each time until eventually, it bypasses it’s original stopping  point all together.

FWIW using the sensor track and a Legacy engine equipped with a IR sensor IMO is more accurate.  Unfortunately none of these electronics are mil-spec.  You will have variances because of a number of factors and just the engine themselves not be that particular.  Like I said I have had much better results with the ST because it is triggered by a spot on the track and depending on the length of the recording, the shorter the better, and stop from the ST it can be fairly accurate.

Thanks Marty!  I have found that to be true as well with the ST but was just curious as to why the Cab2 recording tends to become less accurate during playback time.  I’m not complaining, I’m just trying to learn the why’s and why nots of the legacy system as a whole.  

I've found the same thing.  I write it off as the ST truly triggers the recording to start based on locomotive position rather than the CAB2 which could be more random.

MARTYE, if you’re playing back a recording made by the cab2, can you use the sensor track to tell the engine to do a specific task such a make a stop while the recording is still in play?  I have this layout that I’m setting up for Christmas and it has a passenger stop.  We’ve discussed this in the past about the cab2 not starting and stopping at the same points each time it makes a few loops.  I’m just wondering if the ST could be programmed to stop the engine where the ST is placed and not halt the original recording that’s in play.

Thanks for your help

This is possible. You could program a SensorTrack custom user recording to cause one particular ID'd engine to stop, or ALL passing engines to stop. However, for the stopped location to be consistent each time, the engine's speed must be exactly the same each time is approaches and crosses over that SensorTrack.

There is no linkage between the SensorTrack triggering an engine behavior and the CAB2 recording/playback triggering an engine behavior. Neither effects the other. If a CAB2 recording happens to be playing back during this, it won't be cancelled or interrupted, it will continue to run normally.

Thanks Rudy!  When I gets some time this afternoon, I’ll see if I can get this to work like I hope it will.

Railsounds posted:

This is possible. You could program a SensorTrack custom user recording to cause one particular ID'd engine to stop, or ALL passing engines to stop. However, for the stopped location to be consistent each time, the engine's speed must be exactly the same each time is approaches and crosses over that SensorTrack.

There is no linkage between the SensorTrack triggering an engine behavior and the CAB2 recording/playback triggering an engine behavior. Neither effects the other. If a CAB2 recording happens to be playing back during this, it won't be cancelled or interrupted, it will continue to run normally.

Rudy, when i playback a general recording with a passenger station stop,  the locomotive start to creep past the point that I want it to stop.  Can you tell me what actions do i need to record on the sensor track to cause the locomotive to stop each time during a general recording playback?  It sounds as though im going to have to place a sensor track way before the passenger station to activate the stopping process of the engine as well as keeping the current sensor track in place to actually stop the engine.  

You can do it with one track, but the only way to get reliable stop locations is to use the CAB2 preset speed commands, both when you are creating the original recording and every time you use it to play back.

If you are manually running the throttle during the trip, and hit the track at not EXACTLY the same speed you were going when the recording was created, it won't stop in the same place.

Try this experiment. Let's say you have a loop with a station, and the track is somewhere on the second half of the loop, closer to the station during your approach. 

Position somewhere near the station in a position that is "past" the SensorTrack. It doesn't matter exactly where.

Press the SensorTrack record button, so it is ready to start recording when the engine rolls over.

Now, go to the speed page on your CAB2. Set your momentum to Low. Press a speed preset command, let's say Medium. Do not touch the throttle, brake, boost or any other speed command. Let the engine traverse the loop, and cross over the SensorTrack. You will hear a single bell ring indicating the recording has started. Using throttle, brake, speed button--whatever you want--stop the engine at the desired location. 

Wait a few seconds or a minute (but less than 5 minutes) and then press the Medium Speed button again. Now, press the button on the SensorTrack to stop recording.

The engine will again complete the loop and trigger SensorTrack playback. It should stop in front of the station at the same position as last time. After the pause, it will start automatically around the track again and the cycle will repeat forever. 

The point of this example is to show the degree of repeatability you can expect when the engine is traveling at EXACTLY the same speed when the recording is created and when it is played back. But if you are manually running the throttle and running over the track at different speeds each time, you will not get repeatable stops.

Railsounds posted:

You can do it with one track, but the only way to get reliable stop locations is to use the CAB2 preset speed commands, both when you are creating the original recording and every time you use it to play back.

If you are manually running the throttle during the trip, and hit the track at not EXACTLY the same speed you were going when the recording was created, it won't stop in the same place.

Try this experiment. Let's say you have a loop with a station, and the track is somewhere on the second half of the loop, closer to the station during your approach. 

Position somewhere near the station in a position that is "past" the SensorTrack. It doesn't matter exactly where.

Press the SensorTrack record button, so it is ready to start recording when the engine rolls over.

Now, go to the speed page on your CAB2. Set your momentum to Low. Press a speed preset command, let's say Medium. Do not touch the throttle, brake, boost or any other speed command. Let the engine traverse the loop, and cross over the SensorTrack. You will hear a single bell ring indicating the recording has started. Using throttle, brake, speed button--whatever you want--stop the engine at the desired location. 

Wait a few seconds or a minute (but less than 5 minutes) and then press the Medium Speed button again. Now, press the button on the SensorTrack to stop recording.

The engine will again complete the loop and trigger SensorTrack playback. It should stop in front of the station at the same position as last time. After the pause, it will start automatically around the track again and the cycle will repeat forever. 

The point of this example is to show the degree of repeatability you can expect when the engine is traveling at EXACTLY the same speed when the recording is created and when it is played back. But if you are manually running the throttle and running over the track at different speeds each time, you will not get repeatable stops.

 

 

Thank you Rudy!  I will try this when I get home.

Blake Morris posted:

Railsounds posted:

You can do it with one track, but the only way to get reliable stop locations is to use the CAB2 preset speed commands, both when you are creating the original recording and every time you use it to play back.

If you are manually running the throttle during the trip, and hit the track at not EXACTLY the same speed you were going when the recording was created, it won't stop in the same place.

Try this experiment. Let's say you have a loop with a station, and the track is somewhere on the second half of the loop, closer to the station during your approach. 

Position somewhere near the station in a position that is "past" the SensorTrack. It doesn't matter exactly where.

Press the SensorTrack record button, so it is ready to start recording when the engine rolls over.

Now, go to the speed page on your CAB2. Set your momentum to Low. Press a speed preset command, let's say Medium. Do not touch the throttle, brake, boost or any other speed command. Let the engine traverse the loop, and cross over the SensorTrack. You will hear a single bell ring indicating the recording has started. Using throttle, brake, speed button--whatever you want--stop the engine at the desired location. 

Wait a few seconds or a minute (but less than 5 minutes) and then press the Medium Speed button again. Now, press the button on the SensorTrack to stop recording.

The engine will again complete the loop and trigger SensorTrack playback. It should stop in front of the station at the same position as last time. After the pause, it will start automatically around the track again and the cycle will repeat forever. 

The point of this example is to show the degree of repeatability you can expect when the engine is traveling at EXACTLY the same speed when the recording is created and when it is played back. But if you are manually running the throttle and running over the track at different speeds each time, you will not get repeatable stops.

 

 

Thank you Rudy!  I will try this when I get home.

Rudy, is it the momentum feature thats throwing the locomotive timing off?  Is that whats causing the engine to advance forward a little each time it stops??

Thank You

One of the steps was missing the word "engine," it should read "Position your engine somewhere near the station in a position that is "past" the SensorTrack. It doesn't matter exactly where."

Momentum should be set to the same value when making the recording and when playing back the recording. 

Railsounds posted:

Momentum should be set to the same value when making the recording and when playing back the recording. 

Ok and thanks Rudy