Railcom for pc control?

[MikeH_83]

Hi all,

 

I have just about finished my baseboards and now am looking to laying track and sorting out the bus wire and all that.  My plan is to probably have an ECoS command station (maybe linked to z21?) but also have computer control setup for automation using RR&co (atm just have Hornby e-link for testing purposes).  I like the idea of being able to sit back and watch or at will take control of a loco and enjoy controlling that whilst following the signals and such.

 

Now to the important bit,  Would it be better to use railcom for detection?  My fiddleyard won't be that huge so I will end up taking stock off and having abit of a changeover probably on a monthly basis so I am thinking this might help with the computer software by using railcom?

 

If so I assume I would have to use the esu railcom detector? and esu's bus thingy http://www.esu.eu/en/products/digital-control/ecosdetector/ecosdetector-rc/ Or would the dcc4pc board work? Is it true that if you have more than 1 loco in a railcom detection zone the cv just reads as 0? Except for the dcc4pc one?

 

I am also planning to use megapoints for the points and signals.  So right now I am trying to get my head around what's needed as my last layout was many moons ago and dc.

 

Thanks very much

[Ron Ron Ron]

If you are going to be constantly changing stock and wish to take advantage of what RailCom has to offer, may I suggest you look at using RailCom Plus decoders which will automatically log on to the DCC system as soon as the are placed on the live rail, or when track power is switched on.

 

Q. Why would you want a Z21 linked to the ECoS ?

 

 

.

[RFS]

RR&Co Traincontroller (TC) doesn't need Railcom in order to run automated schedules.  It's all done by tracking so you only need standard occupancy detectors for TC.  The type of occupancy detectors you use need to match the protocol of your command station. I use Lenz and that requires ODs that use Xpressnet - in my case I'm using LDT RS8s.

 

You could have problems with Railcom detection in certain circumstances.  For example, I have some Bachmann 4-CEPs (class 411) which have a motor coach at one end.  The other 3 coaches are wired for lighting.  If this unit enters a monitored section with the powered coach at the rear, then the first coach will trigger the OD, but until the rear coach enters the zone the Railcom detector can't see the decoder.

 

All points need to be DCC-managed by a suitable accessory decoder so that TC can set them as part of schedules. 

[MikeH_83]

If you are going to be constantly changing stock and wish to take advantage of what RailCom has to offer, may I suggest you look at using RailCom Plus decoders which will automatically log on to the DCC system as soon as the are placed on the live rail, or when track power is switched on.

 

Q. Why would you want a Z21 linked to the ECoS ?

 

 

.

Ah ok cool, So the newer lokpilot and zimo decoders I'm assuming support this?  I was thinking of the z21 because the mobile app looks abit nicer but I guess your right, I wouldn't need it.

 

RR&Co Traincontroller (TC) doesn't need Railcom in order to run automated schedules.  It's all done by tracking so you only need standard occupancy detectors for TC.  The type of occupancy detectors you use need to match the protocol of your command station. I use Lenz and that requires ODs that use Xpressnet - in my case I'm using LDT RS8s.

 

You could have problems with Railcom detection in certain circumstances.  For example, I have some Bachmann 4-CEPs (class 411) which have a motor coach at one end.  The other 3 coaches are wired for lighting.  If this unit enters a monitored section with the powered coach at the rear, then the first coach will trigger the OD, but until the rear coach enters the zone the Railcom detector can't see the decoder.

 

All points need to be DCC-managed by a suitable accessory decoder so that TC can set them as part of schedules. 

Ah ok, I didn't know with the regular switching of stock if it would throw things out and would require railcom to work "better" If not then I guess I could just save some money and use normal detection modules.  I would probably end up with lighting in most of my stock too so I wouldn't want it to make it go haywire.  I shall make sure I use a protocol for the ECoS that it supports and use detectors of the same  (probably the esu stuff although I noticed the ECoS supports a few different ones), Thanks for clearing that up

 

I will check if megapoints will work with TC or not.  Cheers