Railmaster/Elink not writing CVs to Decoder.

[ModelHawk216]

I am hoping that someone on here can offer me advice and help me to correct the issue that I have with my Hornby Railmaster and Elink controlled layout.

A few weeks ago I had a locomotive with a Hornby TTS Decoder that had what looked like a dodgy bit of soldering on the speaker wires. I now regret trying to programme that locomotive as when I had read the CVs to it on my programming track and then transfered it to my running track to test it, an electrical short happened.

Shortly afterwards I noticed that with two of my DCC on board for directional and interior lighting Coaches I was unable to use these funtions. Also since then, when I tried to add other Sound Decoder fitted models to my layout I am able, it seems, to read and then write the CVs to the model. But, when I place it on my running layout track to test there is nothing at all from the model, no lights or sound functions.

It is puzzling as all the locomotive models, that also includes other DCC fitted coaches aswell, that were programmed before the issue are running and sound as they should.

I have now bought another new Elink Controller and fitted this with its new USB lead and new Programming Wire leads, but still the issue is there.

I really hope that someone can help as I do love using a Hornby Elink Controller and Railmaster Programme and do not want to change to another DCC system unless I really have to.

Please may I thank in advance, anyone that replies to my Discussion.

[P-Henny]

I suggest putting all your decoder fitted rolling stock into two physical piles. One pile containing decoder fitted rolling stock that have no issues and the second pile with decoder fitted rolling stock that do have issues.

Now with the second pile with issues, one at a time put each item on the 'programming' track piece and write 8 to CV8 to factory reset them. Initially test them back on the main layout using DCC Address 03 which will be their addresses if the reset is successful.

If the reset now returns full control, then re-program each fixed item to the original configuration you prefer.

If a reset doesn't work, then try option B which is to completely delete the errant rolling stock item from the Railmaster throttle roster list and re-add them again from scratch and see if that fixes them.

Based upon your statement that the replacement eLink controller made no difference, then I suspect that all the affected decoders have had their configuration corrupted by the short circuit.

See this previous thread for why a short circuit can corrupt a decoder. Read all my replies in this linked thread, not just the one that displays when the page is opened.

https://uk.hornby.com/community/forum/decoder-issues-with-coaching-stock-374930#post-374977

Since a proportion of your decoder fitted rolling stock still function A-OK, then that really does suggest that the issue is with the invidual decoders and not with Railmaster or the original & replacement eLink controllers. Thus buying a new replacent controller system is likely to be a wasted expense.

EDIT: I have just noticed that the thread I referred you too in the link, was also started by you. So is this new reported issue a continuation of your previously reported issue, because the guidance suggested in both answers for you to follow is basically the same.

If the decoders that are still not functioning correctly are the same decoders that were affected in your previously posted thread and following the 'reset' guidance has not fixed them. Then you must consider that they have been permanently damaged and will need replacing as previously suggested.

[ModelHawk216]

Firstly may I thank P-Henny for your reply to my posting.

I have tried all of your suggestions to hopefully correct the issue I have but, I'm afraid I have had no joy.

Over the last two days I have now tried to send a "Help Request" to RailMaster using the internal route. But, although I have set the settings in my Windows Defender Firewall to allow communications to RailMaster, it has always failed as "unable to send" Help message.

Here is a copy of the message I have been trying to send to Railmaster;

Hello Hornby RailMaster Help,

The issue I am having started about five weeks ago when I had an electrical short caused by a faulty soldering on a TTS Sound Decoder fitted to a Hornby Locomotive. I was able to clear this and have since discarded the TTS Sound Decoder. But when I was powered up again, I noticed that the DCC functions ie, the directional and interior lighting did not work on two of my DCC fitted coaches, although four other Bachmann DCC decoder fitted coaches with directional and interior lighting on my layout were working as they should.

Then, when I tried to reprogramme the coaches, although the CVs seemed to be read correctly and written to the Decoder, when the were placed on to my running track layout, none of the functions worked.

I soon found out that any locomotive that had not been programmed before the “short” could not be programmed and added to my layout. Locomotives that had been previously programmed and added to the Elink list when placed on my running track are working fine.

I thought my issue may have been with my Elink Controller, USB cable, programming wires and track, therefore I replaced them all with new components, but to no avail.

I have posted twice in reference to this issue on the Hornby RailMaster Forum under the name ModelHawk216 and have followed the reply suggestions of Factory Resetting the decoders etc but with no joy.

I really hope you can help as I do really enjoy using the Hornby RailMaster and Elink system and would be very reluctant to change to another system.

Best regards Richard Smith.

I am hoping that someone can suggest a solution to my issue as I have stated before I do not want to give up on my Hornby RailMaster Elink system.

I still feel that it may be be something minor that it causing the problem. As why is it that all previously programmed locomotive decoders are working fine, but new locomotives with factory fitted decoders cannot be programmed by my new Elink controller since the electrical short some six weeks ago.

I may be clutching at straws here but, can a electrical short deregister RailMaster and although I can run the previously programmed locomotives I am unable to programme any further models.

I thank anyone who has taken the time to read my posting and hopefully can past on some advice and help to me.

 

[96RAF]

A simple test I use to check if an eLink is actually sending programming commands is to put one of those led track testers on the programming track. It will flash in concert with the programming burst, so you know at least eLink is sending something in response to RM's programming commands, even though not exactly what.

[Fishmanoz]

Try sending your Help request externally as an email to support@rail-master.com.

[96RAF]

I emailed HRMS today about your problem Richard and they said they do have your direct email, but as it was not via the inbuilt reporting system they do not have the supporting files to aid their investigation. I suggest you send a brief reference again from within RM to complete the loop.

A short circuit will not deregister your copy. If it is registered then the key code will show on screen in the usual place.

[ModelHawk216]

Hello All,

 

I am very pleased to report that I, with great support and advice from Hornby RailMaster Help, managed to sort out my issue I had with my layout since a electrical short I had in early December.

Therefore I am a very happy Railway Modeller again.

It turned out to be a Hornby Track Connector on my layout that must have been corrupted when the short happened, because when this was isolated everything worked as it should.

Thanks again to everyone who took the time to read my posting, especially those who replied with advice which was followed and ruling out certain issues that it could have been. This was much appreciated.

Happy Modelling Everyone.

[96RAF]

Glad that it's sorted.

Odd that a simple metal and plastic connector should be 'corrupted'. More likely the connector was an analogue one and the capacitor blew, which shouldn't have been there anyhow for a dcc track connection.