Jump to content
 

Jammur

Members
  • Posts

    8
  • Joined

  • Last visited

Posts posted by Jammur

  1. Has anyone been able to program or read an address on these chips on the ECoS command station ? (21 pin DCC version)

     

    everytime I try them both it shorts out the whole system, it works perfectly fine on the app but I really need this working on DCC controller.

     

    this is the newest Hornby 21 pin HST model.

     

    kind regards Jamie 

     

     

     

     

  2. 2 hours ago, Pedro32 said:


    Hi there Jamie,

     

    I’ve only installed two sound decoders with stay alive to a Hornby class 31 and 9F so far. I’m waiting for an eventual release of a 47/60 and (assumed they may release in time) pannier sound files for me to install more decoders to some other stock.

     

    Once I installed the sound files to the locos and I set the location and tested sounds etc.  I did this initial testing using my Dynamis, I then kept the toggle for each of the profiles set to DCC on the app. So I’ve not needed to change the location with my ECoS Command station. I’m afraid I’ve not read the locations either as the ECoS has recognised the locations already previously set by the Dynamis. 
     

    Sorry  I don’t know this offers much of a solution? 

     

    regards Peter


    Hi Peter 

     

    thanks for your quick reply. I understand your situation I also have a dynamis so I may try that to set the address, i just can’t seem to set or read the decoder address via the ECoS system for some reason, I’ve programmed over 100 decoders with the locos placed on a separate test track and it’s the first time I’ve came across this issue.

     

    I have looked in multiple forums and even a Google search on this but can’t find anything, would you be able to use your ECoS to read the address of one of your decoders and see if it works so I can rule out the ECoS system? 
     

    Regards Jamie 

  3. On 31/03/2023 at 20:11, Pedro32 said:

    I’ve been watching this range develop since the initial announcement. My view was this offered those who had dabbled with TTS decoders something with a bit of more refinement and also encouraged those who may not have thought Iphone app or android control/sound possible to give it a go.

    I have an ECoS command station as my main DCC controller and use a Dynamis Pro for testing and bench work. Some time ago I had fitted some of my items with TTS sound decoders and while basic they were good value for money.

    That said I decided to order two sound decoders with a stay alive pack for each. R7336 8 pin  TXS sound decoder and R7322 21 pin TXS sound decoder.

    I had read through the instructions and also seen some other Youtube uploads.

    I fitted an 8 pin sound decoder to my Hornby Engineers Grey Class 31- which I had recently rescued from Mazak rot with a new metal chassis The sound decoder and speaker and separate stay alive all fitted together as I expected. Downloading the software was simple and the prompts to remove from track and replacing to install new sound profiles was very smooth sailing. All in all it took me an hour from taking the loco apart to having it running on my bench. I like the fact that I can use an Ipad to adjust the settings including volume and change the decoder location really quickly then flip the control to DCC and then cycle through the options on my Dynamis.

    Today I fitted a 21 pin sound decoder to my new version Evening Star 9F. Again, I used the power supply from my Dynamis as I had done for the 31. The fitting of decoder and stay alive was simple and the tender of the 9F already has a speaker housing though you do have to squeeze things up a bit to reassemble the tender. Took me a while with my thick fingers!
    Loading of the sound profile took slightly longer than I’d hoped as I kept getting an error that the sound profile wasn’t loaded properly. What I did in the end was to remove the decoder off the track then reinsert it again and reinstall the decoder software then install the sound profile and it worked! Sound was much better than TTS in my view and the total fitting time was an hour and a half- probably because I was being extra cautious as the decoders has stay alive packs added and it tells you to remove it from the track for 60 seconds. 
     

    All the extra sounds you get is an added bonus over TTS. And I’m impressed with the range of plastic speaker housing you get in each kit. Instructions once you have found them on the Hornby website are by far the most comprehensive I’ve seen- when compared with the old TTS variant.
     

    I should add that I have a fair few loksound V4/5 sound fitted locos in my loco fleet and these decoders offer versatility as well as being £ cheaper. Rest assured I’m not telling fellow modellers what to buy. Just saying what I’ve found so far. Solid start.

    I’ve installed two sound decoders so far. I’ve now ordered some more  (8pin and 21 pin sound) with a view that it hopefully won’t be too long to wait to see what other Ex-TTS sounds are released…

     

    regards Peter

     

    Hi Peter 

     

    did you manage to get the ECoS system to read / set the address on the new Hornby decoders ? Everytime I try it it shorts out I have set it to DCC on the app.

     

    regards Jamie 

  4. 15 hours ago, richard brown said:

    just reprogram the unit and press the opposite button when you set it up

     

    Richard

    Richard,

     

    Thanks for your reply, how do you change direction for accessories on the ECoS though ?

     

    Cheers

     

    Jam

  5. Hello,

    My first post as I just recently purchased the ESU ECoS 50210, everything works great however I have programmed Train tech weld light and a Trian Tech signal (3 aspect) I used the learn function on the accessories and the ECoS picked it up no problem. However its all backwards, when I activated welding animation it goes off and when I turn it off it comes on, also the signal when I choose red it turns green and when I choose green it goes red? The amber is fine as its in the middle. What am I doing wrong ?

    TIA

    Jammur

  6. On 29/10/2020 at 18:38, GoingUnderground said:

    I did say to turn off Railcom PLUS in the decoder, and I meant RailCom PLUS, not RailCom. That's why I emphasised the word PLUS.

     

    Plus is an extension to the normal RailCom functionality as described here.  http://www.esu.eu/en/support/white-papers/railcomplusr/ 

     

    Plus uses Railcom but it can be turned on and off independently of RailCom itself in both the ECoS and in Plus equipped decoders.

     

    In ESU decoders:

    Plus is turned on and off by Bit 7 in CV28 (Twenty-eight). 

    RailCom is turned on and off by Bit 3 in CV29 (Twenty-nine). 

     

    This is covered in the listing of CVs towards the back of the V4 and V5 Loksound and LokPilot manuals. Changing CV29 is not a good idea if you don't know what you're doing as it controls several other aspects of how a decoder behaves. If you changed CV29 to Zero, then that was a bad mistake as in addition to turning off RailCom in the decoder you've set the decoder to use 14 Speed steps, turned off Long addressing, disabled running on analogue (DC), and told it to use the speed curve set by CVs 2, 5 & 6. 

     

    In ECoS:

    There are two separate tick boxes, one for RailCom, the other for RailCom Plus, in the configuration menu. The Plus box is below the one for RailCom in the ECoS configuration menu.

     

    If you turn off RailCom then that will disable Plus because the Plus functionality uses RailCom to let the decoder communicate with the command station. That's why you got a result.

     

    I suggest that you re-enable RailCom in the ECoS, and do what I suggested before, and that is turn off RailCom PLUS, repeat RailCom PLUS, not RailCom itself, in the decoder using CV28 repeat Twenty-eight by changing the value from 131 to 3, as you'd know if you looked at the LS or LP manuals.

     

    You will need to reprogram CV29 as well if you changed that to Zero. What value to reprogram it to is more problematical as you probably don't know what value it had before you changed it. If it were me, I'd set it to 46 (for 28 or 128 speed steps (2)  + analogue running (4) + RailCom on (8) + Long addressing (32) always assuming that you were usign a long address, or 14 ( 2 + 4 + 8) if  it was a short address.

     

    I will also try this tonight, having issues like this with my 156 and dual v5 chips.

     

    Jam

×
×
  • Create New...