V start (CV2) defaults to a value of 176 on installation and after re-set

[candishtowers]

8 pin decoder TXS decoder fitted to Hornby 2MT 2-6-0. On a new installation loading standard profile following CVs are read V Start (2) 176, Acceleration (3), 15, Deceleration (4), 15, VHigh (5) 255 & VMid (72). With V Start reading a value of 176, the loco, obviously, takes off like a rocket!

So I reset the decoder using the re-set code and relinked again. Same result.

I can alter CV2 to the reset value of 2 and all is well again, however the value is not retained in the chip memory after a power down and it resets itself to a value of 176.

I have reset the decoder about 4 times in total, all with the same result. I have 15 other TXS decoders which are performing well. Strange. Any ideas anyone, before I contact HCS? Cheers.

[96RAF]

Obviously a glitch. Is it that particular sound profile on that decoder or any profile. Which profile is it.

Manually set CV2 until it is resolved.

[SteveM6]

That sounds like a continuation of the problem that some (all?) CVs don't write over to the decoder from the app. We are waiting for a fix from the app developers for this.

As Rob suggests, set the CV the old fashioned way with a DCC controller until the fix is delivered.

[candishtowers]

Hi, thanks. I have an EcOS and programmed CV2 to 2. Returned the result "OK". Read CV2 and it was 2. Great. Switched the current off, read CV2 again and it had reverted to 176! Tried another write of CV2 to 2, OK returned, checked and this time the CV had gone to 156! I'm baffled. The CV address of 2 does not seem able to be set to 2, it appears to have an address of either 156 or 176 which I cannot overrite despite numerous atempts. The value of 2 returned after my first reset on the EcOS of the CV, I cannot replicate.

[96RAF]

Does the value of CV2 stick after you have powered down. What I am looking for is when you operate that loco after a power cycle does it work or has the runaway actually come back. Don’t try to read back the value. If it works correctly then the write has stuck and the glitch is in the app, else the problem is in the decoder.

[Fishmanoz]

For clarity:

• the CV is CV2
• the value (not address) is 2, 156, 176 etc

Have you tried writing 8 to CV8 to do the standard DCC reset (not unlink etc)?

When you say the “standard” sound profile, do you mean the factory default profile?

Have you tried loading the correct (or close if not correct) v2 sound profile for the 2MT to the decoder to see if that changes anything?

[candishtowers]

Thanks for your replies. Right, I have tried writing 8 to CV 8 on both the EcOS and app. The CV2 value of 2 after the decoder reset does not stick when the loco is powered down and up again, the VStart CV2 value returns to 159/160 or even 176 on occasions. The profile I am loading is the standard default profile V2.0.

[RDS]

What are you using to read the value of CV2.

[96RAF]

Thanks for your replies. Right, I have tried writing 8 to CV 8 on both the EcOS and app. The CV2 value of 2 after the decoder reset does not stick when the loco is powered down and up again, the VStart CV2 value returns to 159/160 or even 176 on occasions. The profile I am loading is the standard default profile V2.0.

 

 

Can you please tell us the DCC address you used. Thanks.

[candishtowers]

Just for clarity, I have attached a couple of photos on the EcOS, if I write 2 to CV2, EcOS returns the message “OK”, when I read CV2, immediately again, the message is returned “CV2 Value : 176”. This latter value varies, sometimes it’s 159,rarely, 160 and 176 as shown. no matter what do, I cannot make the value of CV2 to stick at 2!

[candishtowers]

After an unlinking, or reset via CV8, the default address has returned to 3. I don’t alter this address until everything is set up and running correctly. If I manage to eventually sort the decoder, CV1 will be 91.

[96RAF]

That looks like you are on default address 3 after the reset. Have you moved away from that and written a new DCC address (long or short).

Edit - I see you replied as I was typing.

[96RAF]

OK - nitty gritty time.

Do you have another loco on track and active with an address within the range 116 to 127. If so can you please delete that loco and power cycle all the kit.

Also if you reset, then power cycle your controller, even briefly can you regain control of those loco.

[candishtowers]

Thanks for your guidance. There is something going wrong with my setup. I think it’s something to do with my EcOS. I did I as you suggest and I put a known good TXS class 31 (which has been performing fine) on the tracks with an address of 124. It did I not behave as I expected juddering and lo and behold it took off like a rocket and on reading the CV2 value it was 159. On checking my EcOS it has a yellow hazard warning next to address no.3 and on doing a CV reset on the class 31, it would not take an address of 3 (greyed out). i can put any other number in but not 3. So, further work on the EcOS to find out what is causing an address conflict -took all the locos off the track and the yellow hazard is still there. Never seen that before. I’ll go onto the EcOS forums. So, I’ll park this for now -guess it’s my setup somewhere and not the decoder itself. I’ll let you know.

[96RAF]

That behaviour is exactly what this new bug is responsible for. Any loco within the duff range address can affect other locos causing loss of control. Odd that may seem, but true. Being worked towards a decoder update.

Hence the request to delete that loco and power cycle the kit to purge any TSR (terminate and stay resident) data lodged within the decoders and/or DCC controller system. I do not think your ECoS is the root cause.

Would it be punitive to reset the ECoS unit - eg loss of loco database, track-plan, accessories, etc.

[candishtowers]

Thank you. I tried one last time - I loaded the default steam profile via the app, made the address loco’s address 91, checked CV2 which was showing 2. Powered off, back on, read the CVs again and CV2 was now showing 176.

Incidentally, I have asked for advice on the EcOS forum about what could be causing the controller to show an address conflict when I don’t have anything else programmed on 3.

So, is the decoder faulty and should be returned for replacement to Hornby CS?

I am not sure about resetting the EcOS - I have a backup but am reluctant to do it!

[96RAF]

There may be a glitch but pointless returning the decoder if it can be fixed by an OTA update.

ECoS forum insight may be handy as Hornby have one such controller for testing I believe.

[candishtowers]

Mea culpa. Thank you everyone for your suggestions and help. The EcOS problem was to blame, I had made a recent purchase of the Caroline Inspection saloon to the default of address of 3 which I had not noticed until another look through the EcOS addresses. This is what was causing all the problems I believe, as I have now given the address of 91 to the 2MT and after numerous playing around with the loco, the VStart CVhas remained at 2. All sorted, but it was my fault for being lackadaisical in address settings.

[96RAF]

That doesn’t explain why the set value was not sticking, even if one address was common to more than one decoder, as this could happen in the HST or DMU power car/dummy car scenario.

[candishtowers]

Yes, you are quite correct. I have spoken with Chris D. in CS and he says there will be an OTA update in the next week or so to adress this issue. He recommends all of my TXS's are updated to avoid this issue if a CV is allocated between 116 & 127.

[96RAF]

Under testing as we speak.