Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

329 Good

Contact Methods

  • Website URL

Profile Information

  • Location
    : nr Alton, Hants

Recent Profile Visitors

443 profile views
  1. A DCC Accessory bus is very sensible and works perfectly well. Accessories do not need to provide feedback over the instruction channel (DCC), but can do where needed though the preference is to use LocoNet, XpressNet, S88 or RS Bus. RailCom is within the NMRA DCC Specification, has been for a long time, and is supported by many manufacturers with a almost all European systems supporting it. It does provide the 2 way communications as does Railcom+ now supported on mainland EU as is BiDIB. It is only the American market |(and to an large extent the UK market) that is lagging behind with little or no innovation nor adoption of standards and comms methods that are operated in EU. I would strongly advise that anyone entering the hobby uses freely available, mainstream commercial products that use open standards thus ensuring that he/she is not tied into any specific make, manufacturer on non standard comms method in the future.
  2. The Digikeijs DR4088 or DR5088RC work very well with a Z21 using LocoNet
  3. Using 2 busses at this stage makes it very easy to run DC on the track and DCC for accessories and you can use the SPDT switch on the Cobalt Digital IP motors to change the polarity of the frogs. When you want to go full DCC later it will be extremely easy with the connection of the DC bus to the DCC controller through an automated current protection device such as a NCE EB1, PSX or MERG DCO. This will give you a properly constructed DCC layout using 2 busses which is best practice
  4. Personally use 2 busses - one for the track and one for accessories. The accessories are fed directly from the command station and the track bus from the command station via an automatic circuit breaker such as an EB1, PSX or MERG DCO. This allows you to operate turnouts when the track is short circuited because a loco has over-run a turnout that is set against. A little bit extra work that you will seriously appreciate later as the layout becomes more complex.
  5. How are you connecting them via Loconet? The LZV100 uses Xpressnet not LocoNet
  6. Wiring point for DC or DCC is exactly the same, in fact DC is probably more sensitive to connectivity issues than DCC at slow speed.
  7. You already have 12v DC available therefore for the cost of a case fan I would add one - you can never make stuff too cool
  8. Four years ago it would have saved me changing to Z21 - though I am very happy that I did
  9. There are a huge number of suggestions made across all of the pages in RMWeb that are impractical from a cost and/or effort perspective yet they are still followed with a level of interest that encourages the posters to experiment unlike the posts in this thread where the so called ‘experts’ are knocking the suggestions down before they have even been tried, and not in a supportive manner. If the attitudes displayed lately in this thread were followed across the hobby then there would be no innovation, development or progress. there are ways to suggest that something is impractical which are not the ways used in these posts and I rather encourage the poster to try what he suggests, it may just work (it wouldn’t be the first off the wall idea that has proved useful and workable) - and if it doesn’t work then at least the idea has been tested and known not to work with lessons being learned along the way.
  10. I do mean go back to the old version - if that cures the buzzing it looks like it is the upgrade that is at fault, if not then it is the CS3. If it doesn’t buzz on the old software then reapply the new upgrade - if it buzzes again then the upgrade is at fault.
  11. Why not roll back the latest Marklin update to confirm that is the cause of the issue?
  12. Depends on whether it was DCC ready before the decoder was fitted or if it is a custom hardwire installation. If DCC ready then all you have to do is remove decoder and refit blanking plug. If hardwired then you need to remove the chip wiring and recreate the DC wiring including suppression and anything else that the loco had originally. If the first not complex, if the the second get CV29 sorted to enable DC and leave it at that
  13. @melmerby Is this setting a precedent in his eyes and when new functionality is introduced by Roco, Digikeijs, Zimo, etc does it mean that he can justify a licence increase based on the increase announced now? Personally it seems very underhand to me.
  14. The tethering term has been adopted by 'phone users as you state however it was in use for connecting devices to other devices by removable cables long before mobile phones and the internet appeared It is valid to use it in the case of model railways where you can plug in, unplug and plug back in a handheld controller to the command station. When the handset is use it is tethered to the command station, when not tethered it cannot be used - same as a phone and internet (which BTW can also be tethered via bluetooth or wifi, it doesn't necessarily mean a wire )
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.