Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

1,206 Excellent

1 Follower

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I think the LV101 is 3Amp max, so that's reasonable for 2mm or 4mm scales. Unless you have a large setup where it is sensible to isolate failures to particular areas (eg. up-main, down-main, fiddle yard, goods yard, etc.) it should be OK as it is. The LV101 should be fine to protect itself. The decoders don't need "protecting", as they are not in the path of any short circuit - the short will occur through the loco's wheels and pickups, but doesn't go through the decoder. Further, Zimo decoders are pretty well protected internally against a loco internal failure (eg. a moto
  2. Mike, its experimenting time - there are loads of ways to approach this: One is to leave the speed increments as you have them, and alter 7224 by programming its "speed table" (probably the 28 step form), and using that to alter how it responds to speed instructions. If you want to try a really small portable speed/direction control, then EngineDriver allows you to connect various small bluetooth game controllers, and set use those for loco control. - Nigel
  3. I assume you've found that on most phones, with EngineDriver, the volume key is the speed control ? (Doesn't work on Apple phones because Apple prevent software writers using the volume key for anything other than volume). The function labels, and the latching nature of each function for each loco, on both the computer throttle and the phone throttle can be customised. They are set in the roster-entries for the locos stored in JMRI. My earlier point about panel development really comes into its own with control via phones. - Nigel
  4. Connecting points for stay-alive will require searching third-party (hobbyist) pages deciding which are talking sense and which are useless, and/or deducing the structure of the decoder from component layout. Some decoder designs are easier than others and better documented. In general you're looking for decoder positive (easy, usually the blue wire) and decoder ground (harder, may not be manufacturer documented, and may be somewhere between two components in the middle of the decoder). One issue with using a decoder's motor output is that it can reverse. Whether that's a p
  5. It can go almost anywhere subject to being designed to work there. After the decoder's rectifier (ie. tacked into the decoder, as per typical decoder stay-alives), or directly on the output to the lights. Putting it after the rectifier means soldering wires into a decoder. There will be something online on how to do it for most decoders. Going after the decoder output risks an issue when the decoder re-starts after an interruption to power. Initially the decoder will come back to its default state, which is probably "motor output zero", which means the lights are
  6. I Googled TCS UWT-100 CV Programming, and found a TCS webpage that was extremely thin on detail. It says that CV Programming is only available in LCC mode and more details will be provided. Since the page is dated last March this is not promising. I suggest contacting John Russell, who still posts here as BromsMods, because I think he is now the UK conduit for all things TCS. It is inconceivable to me that a new DCC throttle would not enable easy Ops Mode programming via wifi or radio. Sound locos thrive on such, since you can instantly hear the difference while the lo
  7. I think others have reported it to work. However, the DCC011 is very expensive for a RJ45 (ethernet) splitter box. For example, Farnell offer a RJ45 splitter for £6, and that won't be the cheapest option. - Nigel
  8. Yes Bob, I expect Paul will be able to provide something suitable, tweaked to suit your requirements (eg. if running in a short space, your requirements may be different to having 50 yards of running line). A few years back he produced some for me to fit into some 7mm Mid Suffolk locos for a well known East Anglian modeller. With and without Westinghouse pumps and the like, as appropriate for each loco. Choice of speaker also affects the sound. One thing I did in the Mid Suffolk locos was to use different speaker arrangements to make individual locos of the same class sound
  9. I can't say why there isn't a 3-way, you could ask on the JMRI-Users mailing list on Groups.IO. But many 3-ways don't have the mechanical constraints that you describe, so a pair of turnouts achieves the correct operation. The "rules" you'd need are not overly difficult. If the turnouts are not clickable, then they can then be controlled by something else that you place on the interface. That something else might be three "internal sensors" (one per path through the three-way) that can trigger a sequence of actions, the sequence would ensure that the turnouts move in the correct order
  10. Whilst you're free to use JMRI in any way you wish, I'll point out a few things... The Layout Editor (which produced the drawing above) is for constructing a logical description of the track and signals. If you push the layout editor further, you can set blocks, and place signals at the end of blocks, and have JMRI work out the rules (turnout positions and track occupancy) to determine the signal aspects. But, as a logical description, the visual appearance options are limited. There is some scope to change the appearance, but it doesn't offer everything.
  11. Enabling Railcom and RailCom Plus is a few simple CV changes to each loco, and does not need a LokProgrammer. Some of the more advanced features of RailCom Plus may need a LokProgrammer to set them. Your startup problem sounds like "inrush current" as everything fires up. A work-around is a few section switches on the layout, and at power up, you switch them on manually, so the system doesn't see such a big surge in power.
  12. Generally one measures current in series.... Put ammeter in series with track feed on DC (ie. one wire from controller goes to one ammeter lead, the other ammeter lead goes to the track, thus ammeter is in series) and test what the loco draws when running over a range of speeds, ideally with a load (train) on it, or pushing against a stationary object. Make sure for initial tests that ammeter has adequate range (1A minimum, preferably quite a bit more) otherwise ammeter will either blow its internal fuse or be damaged. Once you have an initial reading on a high current setti
  13. I'm fairly sure someone has published an Arduino sketch for putting commands onto the NCE Cab Bus. So, could build a DIY equivalent to a MiniPanel where it did respond to a switch going to "off". Sticking with the NCE MiniPanel, it would be possible to build a processing unit which responded to the first "on" event in one way, and the second "on" event in a different way. Thus a push button on the minipanel would be "first push = on, second push = off" or whatever the processing unit was doing. The question is where to insert the processing unit into the system. The two ea
  14. Ok. with that motor/gearbox, I'd be reasonably certain its OK with a small decoder. If you have a DC ammeter and can check it on DC under load, that would be a good confirmation, but I'd be pretty confident of it being acceptable. - Nigel
  15. Which motor is being used, and what's its maximum current on DC running ? I'm a little concerned that a MX617 is a bit small, and later you discuss a Lenz "mini" which is also small, yet this is a fairly substantial loco (you talk about lead-filled boiler, etc.). I had in mind next size up, so "Lenz Standard" or Zimo MX623. With a very efficient motor, the smaller decoders will be OK. Paper box or paper packet will do, though a plastic box is fine. There is heat dissipation to consider, so I'd avoid tight wrapping, but try to use something which is vented in some way.
  • 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.