candishtowers
-
Posts
29 -
Joined
-
Last visited
Content Type
Profiles
Forums
Articles
Gallery
Posts posted by candishtowers
-
-
Thank you both, tried the re-boot to no effect but re-typed DCC address again and that cured it.
-
1
-
-
I updated my class 50 sound to the latest v1.40 today. No errors were received. The class 50 shows as connected with the Bluetooth icon, but does not move nor is there any sound. Interestingly, I have a TXS fitted Class 66 King Charles and this is shown as connected with the Bluetooth icon, though it is in the display case (with no power).
I guess I’ll do a decoder reset on the 50 and see if that cures its ills. I wondered if anyone else has had phantom trains shown as Bluetooth connected when they are not? -
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.
-
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.
-
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!
-
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.
-
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.
-
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!
-
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.
-
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.
-
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.
-
Thank you 96RAF, changing the CV2 to the value 2 did the trick. Never fiddled with them before. Perhaps I will read the manual more. Cheers.
-
The settings for CVs, 2,3,4,5,6 & 29 are 159,15,15,255,72 & 2 respectively.
-
Hmm, had not considered the CVs. Never altered any before, but I will post the CV details tonight when I arrive home in case they are all working for some reason. Also, my track is powered by an EcOS Command Station. Cheers.
-
So, bought myself a Hornby Railroad Colas 47….tested on analogue and runs fine. I put in the TXS decoder, and loaded the sound profile for the 47. All sounds work correctly, however using the speed control on the HM7000 causes the loco to shoot forward to full speed immediately and the speed is uncontrollable. As soon as I set the speed slider to the left (off) the loco stops immediately.
I carried out a full reset of the decoder, linking it again, this time loading both the default sound profile as well as the “small” class 08 profile. Same result - the loco is uncontrollable.
One thing I did I notice is that this decoder takes perhaps twice as long time wise to link to the Bluetooth, and, as soon as you put the loco on the track or switch the current off and on, the loco jerks forward an inch or two. No other locos I have fitted with TXS do this.
Is it a question for CS and a possible return, or does anybody have any more suggestions to cure the errant decoder? Thank you.
-
Well I’ve learnt a lot reading all this. Thank you. Tried everything-nothing works. Can’t remember which stall at the show I bought it from either so I’ll put it down to experience. I suppose I could send it off to ESU in Germany, but it may be good money after bad doing that!
-
So, failrly new to DCC, went along to the recent show in Milton Keynes and bought a shiny new ESU Lokpilot Decoder, to put in my shiny new loco - cost a hefty £34, but hey?
Anyway, ran the train on DC, Ok, and then put in the ESU 21 Lokpilot. Nothing.
So, I put the chip on my ESU decoder tester, the 2 green lights come up as they should on the tester, but as soon as I try to read the chip, the reader “Error” message appears and the controller and board shut down.
Think I’ve goosed the Lokpilot to be honest - would this be a reasonable assumption or is there any other test I can do to see if it’s “KAPUT’ or not? Cheers.
-
I linked my King Charles III loco via the HM7000 app. When I tried to install the loco profile I received the error message “Could not locate profile SD65535”.
I deleted the loco and reset the decoder and linked again -same result.
(I cannot seem to get the “Resettable” icon though, just “Link”.)
I then made the mistake of trying to load the Class 66 profile - I now receive the error message Sound data/Profile ROM mismatch”. Loco is now “dead”.
Any ideas please, or is it case for Hornby CS to resolve?
-
Reading the article “ Moving the Goods” in “The Collector” recently there is a picture of a train near Durham. Nothing special in that, however, the engine has just passed under a semaphore signal with home and distant arms and between them is what looks like a subsidiary or calling on arm. All are in the “off” position.
i have not seen such a signal before and so I am questioning what was the meaning of the subsidiary signal when the driver would have taken the main line signals as his authority to proceed?
-
Thanks guys, I had a look at the ZIMO site too. I think I’ll just it down to “experience” and not go around messing with CVs as much - Should be OK to do that I know, but hey? I can live with it, perhaps I’ll find a new home for the decoder so it controls just lights or something.
-
I have been trying to re-set my 21 pin Bachmann decoder (CV No. 8 reads as 101) but with no sucess. I have messed up the CV playing around with them and the loco woks but is "jittery" for want of a better word. I have an ECOS controller so I thought it would be easy to reset the decoder by writing 8 to CV8 on teh programming track. No such luck. The ECOS reads "OK" on the display once this is done, but all the CVs remain the same, so CV1=69 which I programmed the loco to initially instead of a reset which i should expect to show 3 as CV1. I could just buy another decoder I suppose, and the loco does work, but not smoothly. Just wodered if anybody had any ideas to try and further the re-set?
-
Ah! Thank you all for the “pointers”.
-
Ah! Thank you all for the “pointers”.
-
Hornby Class 08 fitted with stay alive: All shows correctly on the app and all sounds play as they should on engine start-up…..but after one circuit of my track, sound diminishes to almost nothing. Turning the slider for the volume does not help as all that does is to make the speaker distort. If I turn off the track power for 2 mins everything works as it should until a circuit around the track and the sound almost fades to nothing again. Very strange. Any thoughts?
Bluetooth connection query
in HM | DCC (HM7000)
Posted
I have an 2021 5th generation iPad Pro running the HM7000 DCC software. The time taken from powering up the locos to them being detected under Bluetooth is consistently around 100-105 seconds. I was wondering if this were a normal time for the locos to be recognised by the app?