Loco ID number changed

[KeithT]

I run MTS11 and my Saxon was set to No 1.
This afternoon it started normally, ran 20yds and stopped.
The MTS station showed a short. I reset it but the Saxon would not move or respond to any command. My rack loco on No3 ran normally. I tried unplugging the MTS to reset it without any success. It was only when I tried running through the numbers that I found that the Saxon had reset itselt to No2!
How can that be?
Am I having my usual affect on digital components? :-

 

[stockers]

New one on me Keith.
Glad it was only number 2, you could have been hours.

 

[mike]

possably due to the close proximaty off the 2 new olimpic mascots...

 

[KeithT]

possably due to the close proximaty off the 2 new olimpic mascots...

No they would just have frightened the pants off it.

 

[stevelewis]

Hi Keith

I think a serious reply is called for ?

Try a decoder reset, I think its a Massoth sound decoder in that loco?

Any probs give me a ring if you wish I'll pm my number
Steve

 

[KeithT]

Hi Keith

I think a serious reply is called for ?

Try a decoder reset, I think its a Massoth sound decoder in that loco?

Any probs give me a ring if you wish I'll pm my number
Steve

Thanks Steve, it seems happy enough on No2 at least for the moment. Everything works as it should.
Yes I forgot to mention it is a Massoth card.

 

[Zman]

Am I having my usual affect on digital components? :-

Probably!

 

[rhaetianfan]

Interesting!
At the end of last season my LGB Ballenberg rack loco decided to stop working for no apparent reason so it was returned to its box and, of course, forgotten. Over a recent weekend, with trains emerging from hibernation, I thought it would be nice to run a ?steamie? amongst the electrics so no. 1067 was fished out of its box. Selecting what was believed to be its stored identity on the Navigator returned a big X, so no joy there. Dismantle loco to check for wiring damage, or other evidence of things not as they should be such as fried chip ? all appears well (LGB MTS II decoder, directly plugged into loco circuit board). Place loco on programming track to check identity ? CV1 returns ?225? as programmed value. Loco # 225 selected ? nothing. Recheck CV1 and now it reads ?197? but still the loco refuses to respond to this, or code 3. Decide to go back to basics and re-programme it to #7 and lo, all is well again!
I?m just waiting to see what code it wants next time I try it...
In fairness, this is the first time an LGB loco has thrown a wobbly in 15 years of garden railway operation but as a mechanical engineer by past training I have to accept that fault rectification these days involves more than a gentle (or not so gentle) tap with a hammer!
So, random identity changes may be catching..!

M

 

[Zman]

So, random identity changes may be catching..!

Sorry, who are you ?

 

[rhaetianfan]

So, random identity changes may be catching..!

Sorry, who are you ?

:thinking:

M

 

[KeithT]

So, random identity changes may be catching..!

Sorry, who are you ?

Have you noticed Zman has become the thin man......

 

[Zman]

So, random identity changes may be catching..!

Sorry, who are you ?

Have you noticed Zman has become the thin man......

Several thin men!

 

[KeithT]

So, random identity changes may be catching..!

Sorry, who are you ?

Have you noticed Zman has become the thin man......

Several thin men!

Can't deny that, most of Morley.....