Tim765

Thanks for the advice. my latest observations: usually when an OL occurs; after clearing it, pressing the red button twice does the trick, resetting all locos. But sometimes, the loco which had the problem restarts at its previous speed. Then a third press of the red button seems to be needed. Any ideas why? I think my Select is v1.4 or earlier.

Hi, I have recently got a Hornby Select contoller. It works fine, but I'm having problems with the OL message. This happens when there's a short-circuit or derailment - ok. But what do I do to reset the Select ? There's no useful instruction in the manual, so I've been pressing the red button, which usually then mean I get an ES message. I've turned the Select off and on by removing its plug. But then, after I've rerailed - mayhem - with loco 3 starting up (I understand this because 3 is the default), plus the one I was controlling reverting to its previous - or a higher - speed! Why aren't all loco speed settings cancelled when turning off/on?

I thought that was the whole cause of my problem. If not, why did going from 1.67 to 1.74 cause all these issues?

Thanks for the replies. As RM is on my laptop, which doesnt usually have an internet connection, RM has not been automatically updated in the past. I was also not aware you couldnt skip previous version updates. Due to problems getting any life at all out of the elink when I first installed 1.74, I had already added the 3 new lines to my .ini file, having read another thread. However I've now made sure they match what P-Henny suggests. The rectangular red button seems to work now to reset the elink, which helps speed up the derailment process. I was not aware of its purpose before, so never used it, so it may have worked all along.. I still don't see the short-circuit message though.

I have just upgraded to RM v1.74. I am now having a problem with derailaments and any other short-circuits> These cause all locos to be 'dead' and RM to stop responding. The only way to restart is to turn off the elink, quit RM, and restart both. Then all is fine until the next issue. My old vsn was 1.67 I think, and this responded to short-circuits with a msg, asking you to clear it and click to continue. This was fine. Why in 1.74 is there no such msg ? This seems a big backward step..