Skip to main content

Running at a recent show, we had problems with Legacy locos stopping and resisting all attempts to get them moving.  Hooking up a comms command monitor to a SER2, we see the following:

(Time,   Hex Cmd bytes,   Text of the command)

Press ENG 44 Startup

57.662,   F8,59,FC,   Engine 44  StartUpSequence2(ImmediateStartUp)

Press Speed

Press Restricted
61.735,   F8,58,00,   Engine 44  Set Absolute Speed Step 0
63.532,   F8,59,DF,   Engine 44  Engine Labor 31

Press Slow
63.750,   F8,58,00,   Engine 44  Set Absolute Speed Step 0

Press Medium
65.476,   F8,58,00,   Engine 44  Set Absolute Speed Step 0

Press Limited
67.864,   F8,58,00,   Engine 44  Set Absolute Speed Step 0

Press Normal
69.400,   F8,58,00,   Engine 44  Set Absolute Speed Step 0

-------------------

For comparison, this is what is normally observed:

Press ENG 44 Startup
107.546,   F8,59,FC,   Engine 44  StartUpSequence2(ImmediateStartUp)
Press Restricted
113.421,   F8,58,01,   Engine 44  Set Absolute Speed Step 1
113.452,   F8,58,F0,   Engine 44  Train Brake Level 0
113.483,   F8,58,F0,   Engine 44  Train Brake Level 0
113.499,   F8,59,CC,   Engine 44  Engine Labor 12
113.515,   F8,58,CA,   Engine 44  Set Momentum 2
113.546,   F8,58,CA,   Engine 44  Set Momentum 2
113.733,   F8,58,01,   Engine 44  Set Absolute Speed Step 1
114.300,   F8,58,05,   Engine 44  Set Absolute Speed Step 5
116.643,   F8,58,06,   Engine 44  Set Absolute Speed Step 6
116.956,   F8,58,07,   Engine 44  Set Absolute Speed Step 7
119.180,   F8,58,08,   Engine 44  Set Absolute Speed Step 8

etc.

We have concerns with the club's old Legacy Base and substituted a different command base.  The "Set Absolute Speed Step 0" persisted for speed button presses and red knob turning on the new base! 

So, I figured the speed ramp up/down logic was in the CAB 2.  I pulled the batteries on the CAB2 and tried again.  Same result.

We used the CAB1 speed dial (Set Relative Speed +1) to get the loco moving.

I'm confused.  Where is the logic for speed ramp up/down located?  CAB2 or Command Base?

We have a TMCC power switch for the Legacy base plus TMCC base (but not the LCS components).  I cycled the power to the two bases, and voila! the engine speed commands returned to normal.  Does the presence of the TMCC base on the Y cable affect Legacy speed commands?  Cycling power on both devices reset speed commands back to normal!

Firmware revision levels were 1.52 and 1.60 on the Legacy Bases and CAB2 we were using.  The "Set Absolute Speed Step 0" was observed using both firmware levels.

Any insight into how speed commands are generated by the Legacy Base/CAB2 is appreciated.

John

 

 

 

 

 

 

Original Post

Replies sorted oldest to newest

This problem was noted three times (different locos) during show hours.  Last night, I was the only operator when it happened, so I tried to define the behavior and log the TMCC command stream.   A DCS TIU and WiFi were powered up along with the Legacy base, TMCC base, and LCS devices (WiFi, SER2, multiple ASC2s and Sensor tracks).  I used a single CAB2.

When the Legacy base was swapped out, the problem persisted which suggests that the set absolute speed ramp up commands are originated in the CAB2.

When I pulled and reinstalled the batteries from the CAB2, the problem persisted.  I know the CAB2 exchanges data with the Legacy Base but why did this speed command error propagate across two bases and power cycles in the CAB 2.

Finally, cycling power on both the Legacy and TMCC bases simultaneously cured the set absolute speed 0 problem.

Twilight Zone.

We tear down today so I may not get a chance to investigate this problem for a while.

John

I actually have used the capability to do the same thing Chuck.  It's also kinda' handy for beginners, they tend to forget that they have to watch the track in front and obey the signals at the yard entrances in case someone is pulling out.

MartyE posted:
gunrunnerjohn posted:

I still think it was someone with a remote.   My grandson was screwing with me one day doing that, and it took a bit to figure out what was happening.

LOL!  That had to be fun!

I did get even later.

Add Reply

Post
×
×
×
×
Link copied to your clipboard.
×
×