Charles,
Without putting you off, in my usual bloated way, I would highlight a few
considerations. These may or may not be applicable to your particular situation however considering the future of ones layout direction may sae some duplication/doublehandling (wasted effort)
FIRSTLY:
Please refer the "Schematische Darstellung" @
http://maerklin-info.de/...s/Systemarchitektur2.pdfHere Marklin have "put a stake in the ground" and shown that any legacy 6015/6017 track must be seperate from any "systems" track.
The ski-lifter solution only isolates the centre rail and then only in a single pickup train. This is the 1st hurdle as it provides a potential solution for when different track sections are driven from different controllers and leverages the tradition
common ground for the rails.
1) a previous MM/MNews(2006?) article effectiely implied that, in a 6021 environment, there was no need for the ski-jump as long as.
a)) the booster(s) were in-phase digitally - i.e. all off the same 6021
b)) the ski did not "dwell" across the join.
most operators have known/assumed/gotawaywith this for years.2) however with the CS , the output to the track must ALSO isolate the ground/return rail from the common ground concept.
Thus a CS/6017x solution can (may not be supported) only work if
1) the ski-jump isolates the the power (reds)
2) the transformer that drives the CS is totally sepearte from any transformer that drives a 6015/17 and does NOT have a ground(brown) in common.
The schematic indicates that the 60172 (unreleased / dropped?) will/was meant to be able to operate on a par with the CS "power to the track" .This is in addition to its ability to support bidirectional mfx.
Note: If the 60172 is wired as shown it would not need to relay mfx data back to the CS from a decoder as the track circuit is tied as one.
SECONDLY:
I reemphasise that any legacy use of a power circuit and the "common ground" concept as it relates to Accessory return (16V AC from the same transformer) or s88 contact (using the common rail as return) must be reviewed and preferably elliminated.
THIRDLY:
Not widely discussed is the subject of problem determination, and trying to identify in which circuit a short occured and its impact on the WHOLE layout.
Unitl the CS-upgrade for booster hits the streets I have no idea if the CS will indicate/isolate that section - the technology is available but the desire may not be .
For the 60129 (of similar DiltaControl as booster) implementation I see an IMMEDIATE benefit in that ONLY the relevent section cuts out. I am forever hopeful that someday the CS will be able to detect and report this information, in the meantime we still have the indicator LED on the booster. (and a momentary switch in the feed to allow a selectie reset)
FOURTHLY:
While the rumoured native attach of boosters to the CS is still pending, the information to hand is that it will use the same 5pin flat cable . This has 2 drawbacks. distance and connector type.
While the CS System-Bus does not take a leaf out of the loconet book and use industry standard RJ12/RJ45 connectors it does offer a more structured way of extending the control circuits up to 100m (As above, I am hopeful that the future will allow for feedback/status information)
My personal summary.
- eliminate any design that connects accessorys to track
- plan for independant sensor(s88) return bus (I use contact tracks extensively so this is a problem)
- plan for a 60129 mentality (one booster per 60129), even if the direct attach ends up able to deliver the same functionality.
-