Again: Train starts and runs at full speed, out of control!

[Per Olsen]

Hello.

You might have seen my earlier posts on this problem.  I have had this problem a long time, and many times I was sure I had fixed it.  But it keeps coming back.  I am using a TAMS controller, all train-decoders have been disabled for analogue control, etc.  You may see in my earlier messages here in this forum.

Anyway.   It happened again today.  And luckily, I had my son with me as it happened (me and my son own this layout together) this time. 

No trains were running.  No automatic or anything else was active.  I did have one loc-control open on the screen.  My son and I were discussing a total different matter, when all of a sudden, we both saw the loc-control suddenly advanced the speed of the loco from zero to full speed!  I looked down at the TAMS, and it also advanced from zero to full speed.  I had to stop it by pressing the red STOP button before I had an accident!

I do not like to say this, but it seems to me that this MUST be something the WDP is doing on its own?  Have I mis-configured something to make this happen?  What else could it be?  It certainly cannot me a decoder-problem, which I used to think.  And it cannot be the TAMS that gave the full speed, because if it was, the display on the screen would not show the increased speed from the TAMS (this we checked later).

Now I am afraid to start my layout again.  I do not want to have more crashes like this.

And, I must say, this problem can come 2-3 times a day, or it can go weeks between each time.  It happened 2 times today (the first time I did not happen to look at the loc-control), and it has been a few months since last time.  So very irregular..

What can I do?  I must have this fixed now,  I cannot continue with this big problem.  Please help!!   

Regards,
Per.

[Markus Herzog]

Hello Per,

is there always the  loco control of the loco affected open?
Maybe a defect at the End Button on the keyboard (this sets a loco control to max speed)

Other possibilities are of course dispatcher task which call loco macros (I hope you don´t do such things...).

Another idea: open train inspector (F7 window) and monitor if there are still commands visible even if all routes have been released.

Regards
Markus

[Per Olsen]

Hello Markus!

I did not touch the keyboard, it could of course maybe malfunction anyway..  No, the loco control of the affected loco is normally not open, so I have not seen this before.  The first incident earlier today, the loco control of the loco running wild, was not open.  It was just "luck" that it was open on the last incident. 

I did not know that the end button would put it to full speed (I probably should have known..?).  But can that happen, also to locos with not open loco control?

No, I do not have any dispatcher task that calls any loco macros.

I can try the F7 window next time.  If I dare to restart WDP, that is....  But also, in this case today, I had not run any automatics, no routes, nothing, since I started the PC.  So there should be nothing left that would show up in F7, I think..?

Regards,
Per.

[Markus Herzog]

Hello Per,

But can that happen, also to locos with not open loco control?

Absolutely no.

can try the F7 window next time.  If I dare to restart WDP, that is....  But also, in this case today, I had not run any automatics, no routes, nothing, since I started the PC.  So there should be nothing left that would show up in F7, I think..?

That´s correct. Remaining parts could there only be from former routes etc.

Then I have absolutely no idea.

Maybe you upload a backup to the forum so when can take a look at your data.

But to be honest: no idea, the only know cases are the one if mentoined in my first post.

Regards
Markus

[Markus Herzog]

P.S: You did also not use the app before? And you use no joystick with WDP? Are there other throttles or components like the SniffControl connected to the EasyNet of the Tams?

[Per Olsen]

Hello again.

No, I use no app.  No, I use no joystick.  I have a hand-control connected to the EasyNet from the TAMS.  Should I disconnect the EasyNet?

Regards,
Per.

[Per Olsen]

Hello again.

Today we discovered something….: 
My son, Thomas, powered up the Tams Controller, to check on a loco with an MFX decoder.  The PC was not turned on, so the WinDigiPet did not run.  Only the Tams Controller was activ, and it was set on an MFX (M3) address.  Suddenly another loco, a DB MZ1459 with a Zimo decoder on DCC address 28, started to run at full speed.  This decoder has formerly been disabled for AC and DC analogue mode.

On the positive side:  This should exclude the PC and WDP from this problem.
On the negative side:  The problem is still not solved.

EasyNet is not connected to the Tams.  No Joy-stick is connected.  No app was in use.

I have a bad feeling now…:  Could it have something to do with M3-protocole ?  Maybe some decoders (in my case Zimo) have a problem with the M3 from Tams?  Could the Tams be faulty?

We really must have a solution to this problem.  If we must buy a new Controller, we will.  In that case, which Controller should we buy?  It must work correctly with both DCC, MM and MFX.

We are very desperate now…

Best regards,
Per.

[Per Olsen]

Anybody….?

[Stefan Lersch]

Hello Per,

there's only one thing that comes into my mind that you could check: for some decoders it's not sufficient to disable the analogue mode in CV 29 and/or CV 49. Some have also settings in CV 56 or similar. Give it a try.

[Per Olsen]

Hello, Stefan.

I have programmed all decoders to
CV29=0 or 1, meaning Bit2 and Bit3 is 0 (Analogue operation and Railcom is OFF). 
CV28=0 Railcom off
CV50=0 AC and DC analogue mode OFF (some decoders)

I checked again the last loco that ran off, all paramtres above are set correctly.  The decoder is Zimo.

I have a bad feeling that the problem has something to do with Zimo (or maybe also others) decoders in combination with the M3 (MFX) from the Tams Controller, as M3 always is active on the tracks when this happens.  I did upgrade the Tams Controller to the newest firmware.

I am lost now….  And I MUST get this fixed now.  Too much damage is done to locos and other things when this happens.

Should I change to another Controller, in that case, which is recommended?  One that I can be 100% sure will not cause similar problem, and works perfect with both DCC, MM and MFX?  Or what else may be my problem?  I am getting desperate to have this fixed.  As it is now, I have to watch the layout very carefully for runaway locos all the time.  And with 60+ trains in hidden yards (shadow-stations) at all times, it is a very big job..

If I have to replace the Controller (or any other components), I will.  In that case I need advice as to what equipment to buy.  Any help?

Regards,
Per.

[Stefan Lersch]

Hi Per,

as I said, that's was my only idea. Sorry, but I can't help you there.

[Per Olsen]

Hello Stefan.

OK, thank you anyway.

Let's hope somebody else have any ideas.  Or suggestions to what I should replace…

Regards,
Per.

[Per Olsen]

Hello.

Just a short update:
I contacted Zimo support, and got some hints from Stephan Hubinger.  So I have changed all my Zimo decoders to use long addresses, to avoid some problems with reading (mis-reading?) MM1 addresses (I use only DCC where possible).  So far (a few days) it seems to work.  I will test this for a period of time, hope the problem is gone now

Regards,
Per.

[Stefan Lersch]

Hello Per,

very interesting! Never heard of something like that before. Thanks for the information!

[Per Olsen]

Hello Stefan.

I also think it is strange, but I will try (anything!) to get this solved..  I am very tired of this problem.

Regards,
Per.