Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

679 Good


Contact Methods

  • Website URL

Profile Information

  • Location
  • Interests
    Modern(ish) image N gauge (late 1980s)
    Pre-nationalisation 00 gauge
    Computer control/automation
    Realistic operations
    3d printing

Recent Profile Visitors

1,159 profile views
  1. The MRC's new YouTube channel is here. Only one video so far, but do subscribe for more updates from the club.
  2. Command station: HDL LocoCentral (kit of parts for self-soldering) Computer interface: HDL LocoBuffer (kit of parts for self-soldering) Servo control: HDL LocoServo (kit of parts for self-soldering) General I/O*: HDL LocoIO (kit of parts for self-soldering) Short circuit protection: MERG DCO (kit of parts for self-soldering; available to MERG members from the MERG Kit Locker) Booster: Digikeijs DR5033 DigiBoost Converter from Loconet-B to Loconet-T: HDL LocoPanel (kit of parts for self-soldering) Feedback (non-Railcom): Digikeijs DR4088LN/CS Feed
  3. Ahh, yes, that is a different thing. I can see how that might cause indeterminacy - I have some locomotives from OO Works for the planned 00 gauge layout that have pickups like this, so will need to think about dealing with this, either by adding more pickups or putting resistance wheelsets on the leading and trailing axles.
  4. There is a very interesting mechanical system for this involving servos, but I cannot recall the details now.
  5. In other words, when I asked, "Do you have definite information on this that I do not? If so, it would be very interesting to know the details. If not, then it seems misleading to describe it as "false" rather than merely stating that it is uncertain." The correct answer would have been to state that you do, in fact, have specific information that I do not, rather than falsely stating that I have somehow claimed "that an interface will be developed". I notice that you have now for the third time totally ignored the response to the effect that there is no possible good f
  6. I wrote, "There has been some suggestion recently that iTrain might one day support CBUS, but I am not sure how accurate that this information is." Can you explain how you can possibly conclude in good faith that this is in any way misleading, or how you can possibly conclude in good faith that this amounts to a statement that "an interface will be developed"?
  7. Yes, quite: reliability is important for automation, as discussed in the video.
  8. In terms of occupancy detection for turnouts, incidentally, one of the matters that influenced my decision to install them on this layout is that I am trying to make the representation of the signalling system as realistic, within the bounds of my resources and skill level, as the trains themselves. In reality, in the 1980s, switches and crossings would be fully track circuited and the occupancy of switches and crossings would be shown on the signaller's display and would in fact control whether points can be changed or routes set. (Also, do not forget that it is possible that a train under ma
  9. Indeed - the tail lamps will all be set to be DCC controllable so that they will only illuminate when at the rear of the train, and the locomotives have been/will be (only some are complete) re-wired so as to allow independent control of the front and rear lights. Unfortunately, for obvious reasons, it is not possible physically to remove the tail lights when not at the rear of a train, so one will have to make do with them being present but dark, which is the best that can be done for rakes that can be hauled in either direction without human intervention.
  10. My own layout is set after the era of brake vans - but I do plan eventually to fit tail lights to rear wagons. I may have to add resistive wheelsets in the interim, however, as fitting carriage/tail lights can be quite time consuming and I may well wish to run the layout before I have finished this task.
  11. Michael - RailCom decoders are not necessarily very expensive; the basic Zimo decoders (e.g. the 6 pin MX617) cost £20 and come with RailCom as standard. Nonetheless, it is not an essential feature; you just need to do manual data entry every time that you put a train on the track if you do not use RailCom. It is right that it would be unwise to plan on the assumption that iTrain will be able to interface with MERG CBUS, as this has not been confirmed, but I do not understand why Iain Morrison states with such certainty that it is a false rumour; do you have definite information on
  12. Interesting. I shall have to consider that for my next layout. However, occupancy sensors for turnouts do enable a nice display of the train moving along the layout in the signalling display of TrainController. I should note that I do plan to fit carriage lighting, so the resistance wheelsets will mostly not be an issue.
  13. There should not be any issues with trains passing from a section with a RailCom occupancy detector to a section without one: the tiny signal sent back by the RailCom equipped decoder is ignored by the section without a RailCom sensor. Just as long as your hardware supports RailCom and generates the appropriate RailCom cutout, there should not be a problem.
  14. It is not essential to have occupancy dectection for turnouts, but I recommend it (at least for TrainController - check whether this can be done in iTrain). An occupancy sensor on a turnout has two functions: (1) it prevents the turnout from being changed while it is occupied; and (2) it prevents any route including the turnout being reserved while it is occupied. If you have a short train and a long turnout (as I have on my layout with class 121s and British Finescale CV10 turnouts), it is possible for a train to disappear entirely from being able to be detected while crossing a t
  15. To clarify: DR5088RC: connects with LocoNet, RailCom compatible DR4088LN: connects with Loconet, not RailCom compatible, has S88N bus interface DR4088CS: connects with S88N bus, not RailCom compatible. I am not sure what you mean by identifying turnouts here, and I wonder whether there may be some confusion over various concepts, especially the difference between blocks, occupancy sensors and train identification. A block is a logical section of track which may have one or more occupancy sensors to detect the presence of trains. It is also possible
  • 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.