Model Railway Forum banner
1 - 6 of 6 Posts

· Registered
Joined
·
6 Posts
Discussion Starter · #1 ·
Looking For Some Help.On Thursday I Installed 6 DCC Concepts digital cobalts with no issues in conjunction with my ecos 50200 command station on a layout i am building. I also installed one cobalt digital ip with the centring off and address sorted..On Friday i received a new engine with a loksound v4 micro decoder with railcomplus. Running it on track kept firing up 3 of the accessory decoders. Have realised i will need a separate bus for the decoders. On Saturday i tried to install several cobalt ip digital decoders put i cannot get them to respond to the Ecos ie cannot get the centring off and cannot get the 197 command to work on the installed cobalt ip. I have switched of the railcom and railcomplus on the command station when programming . Also the first Cobalt digital ip which had been installed will not switch at all if railcomplus is active on the command station but works if it is switched off. Has anyone else had these issues.
 

· Administrator
Joined
·
10,744 Posts
Have you tried contacting DCC Concepts direct? They will have tested how to the ECoS and their products interact and should be able to give you an answer.

David
 

· Just another modeller
Joined
·
9,967 Posts
*** Cobalt is of course fully tested with ECOS, but ECOS has many progressive changes, with some things not always actually within DCC standards. Most SW versions are OK (including the last one we updated) but we have over time found two of them that had issues in some areas. M4 is more of an issue than Rail-com.

(Actually, the same "not quite to Standards" things also happen with some loco decoders - for example, the way some standards-related CVs are used by ESU and Zimo is actually outside the DCC standards. Not a great issue but a sign that manufacturers are not always working within them).

ESU do a very clever job of trying to make ESU work with 4 different digital protocols, but multi-protocol systems with several digital protocols on at the same time are also often the cause of small problems because the timings of commands can have conflicts. We recommend strongly that with the ESU ECOS unit, M4 is turned off if not used, and depending on your ESU software version, Rail-com Plus can also interfere with things - so turn them off unless you really are using them. (Neither are actually DCC standards related functions and their timings can interfere with DCC communication from time to time).

kind regards, Richard
 

· Just another modeller
Joined
·
9,967 Posts
*** Always happy to help. I think you will find that disabling M4 will help many things :).

Please do not hesitate to ask / call us at any time - we are here 7 days a week to help customers.

regards
 
1 - 6 of 6 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top