Nigelcliffe

Cheapest DCC Sound - "Virtual Sound Decoder", which is a component within JMRI. Free. Plays out either through computer speakers, or through Android throttle running Engine Driver.

I've seen glitches which involve the protocols available (CV12). It may be worth experimenting with those, turning off the "not needed" ones. (The glitches I saw with those were affecting RailCom behaviour, not power management ). Otherwise, suggest a support email to Zimo, they usually answer if your issue is explained clearly.

Pedantically, there is only "JMRI". PanelPro and DecoderPro are just different starting screens of the same software, and all of the features of either are available from either starting place - just traverse the menu structures to get the different commands. One can setup different preferences for the starting places (so things then do behave differently), or even have multiple different preferences (profiles). Rob - regularly take a backup copy of the SD card in your PI. They do go "squit" sometimes, and the backup copy means you can put that onto a new SD card and be back where you were. A better option for a regularly used system is a SSD disc drive, but I think that's only practical on a Pi-4 processor. The Pi-5 has some teething issues over JMRI compatibility (along with numerous other software package compatibility issues), its getting there, but may be a little flakey for some users. - Nigel (who designed the roster view, which is the starting page listing locomotives, in "DecoderPro" ).

The key with thinned flanges is extending (or creating new) bearing blocks so the wheels are adequately supported. A different axle length is a very small matter in comparison to the bearings. - Nigel

You need the decoder manuals, different decoders will do things differently. Then, relate the relevant CV changes to how to make those changes on your PowerCab handset. Ideally you also need documentation from the provider of the specific sound file loaded in the decoder (otherwise you've no idea where to start*) For many decoders, it is incredibly complicated button-pushing-madness-inducing-insanity to do it on a handset. Yes, its possible if you're very methodical, but its much simpler with a computer interface and software (eg. JMRI) to help with things. (* unless you read all the CVs and work out the initial setup, which brings me back to "use a computer" to help...). - Nigel

Coastal DCC have a shop, with demonstration facilities (part of a larger building shared with Orwell Model Railways). Car park spaces on the forecourt. For any retailer, it is sensible to contact in advance to be sure the relevant expert will be present with time available for the customer.

Compare with TCS UWT-50 (I prefer the 50 over the UWT-100). I think as handset designs, the TCS units are amongst the best on sale. But, as with everything, need to check/create suitable infrastructure in the layout to use them. The trouble with any handset design work is the cost of manufacturing them. Plastics/hardware are expensive for the numbers likely to be sold for for model railway controllers. ( I used to work in the design of phones, biggest difference to model railway controllers being the numbers likely to be sold. Which in turn relates to cost to make, and budget available for design work ). - Nigel

No, its whole Prodigy system for the "sniffer" - just an option which is cheaper and available now. There are a lot of handsets that could connect to the Z21, but not Prodigy ones. Handset list would include: Lenz, ZTC (with some wiring faff on connectors), Roco, Digitrax, Uhlenbrock, Fleischmann, and others.

You could pull the Gaugemaster out of the store, connect the Prodigy track output to the "sniffer" port on the Z21, and thus use the Prodigy handsets for control knob control with the Z21 sending instructions to the track. There are also ways to add a £20-ish control knob to Android Phones, if using the EngineDriver App for loco control. That does require running JMRI on another computing device. I'm not aware of the control knobs working with the Roco App. - Nigel

I think by the time the Kinesis is available to buy, the Uhlenbrock DaisyII WLan will also be available. That's listing at Euro330 in various EU-land retailers, so expect it to be £330 in the UK. The DaisyII is a well designed handset. Uhlenbrock have RailCom and LocoNet. And support in numerous computer control packages. That's a lot of boxes ticked...

The MiniPanel is an "Input" device, so it cannot output to LEDs. You can use the MiniPanel with toggle or rotary switches (requires two MiniPanel inputs per switch, one for each direction of the turnout), and those switches would give indication of direction. If wedded to momentary switches and LEDs, then you need an output device on the panel. The simplest may be an accessory decoder, and cheapest simplest might be an Arduino based accessory decoder. It is also possible to use an NCE AUI device for output, but I think its harder work than accessory decoder. As the Yarmorc 8044 appears to be an accessory decoder to operate turnouts, with signals over DCC, I'd expect it to work correctly with an NCE system. You say "couple of PowerCabs and a 5Amp booster". I'm assuming you've got this arranged with ONE command station, and at least the second PowerCab operating as a "ProCab" throttle. Two PowerCab systems, each acting as Command Station is a rapid way to blow them up. (As with any DCC system, ONE Command Station only, unless you're into very advanced control hand-over arrangements). - Nigel

DT602 is usual US/Digitrax fixed button behaviour. Probably the most disappointing feature of an otherwise pretty good upgrade on the earlier DT400/500 types. As far as I know, the only US designed controller with control over button latching are the new TCS handsets - they pull their latching behaviour from the central system's database of locos.

Look at how different systems implement "recall" stacks. Many offer this, some implement the recall feature much better than others. Some offer control of stack-size, others have a fixed stack-size. Some users find a stack of 2 is ideal, others prefer slightly larger stacks of 4 or 6, depends on your operating requirements. All of this comes down to writing down your key requirements, and visiting a decent DCC dealer for a demonstration of different systems. What you "require" might be possible for a couple of hundred pounds, or it might be best part of a thousand. But knowing what you're trading off for those requirements will help the decisions.

I think you'll blow your budget. Doing it with "bits and pieces" - a wireless DT602 is the DT602DE, which is around £250/260. To that add a UR93 at £170. And then add a LocoNet compatible command station, cheapest option there might be a Digitrax Zephyr at £230. I think that lot comes to £650. Or as a "complete package" - the wireless "Evox" system from Digitrax, which is a DT602DE, UR93 and a command station box is about £620. There are other ways, but it would require two handsets, and commercial wireless systems are never going to be cheap. I strongly recommend getting a demonstration of a system before parting with that amount of money, being sure the control works for your way of driving things. - Nigel

It ought to. Roco list the earlier DT400/402 series as working with the Z21, and there's not much difference in what comes out the back of a DT602.

Handheld - Digitrax DT series throttles, two speed knobs. Desk based - ESU ECoS Just about any system which allows use of a smartphone as a throttle - either directly with maker equipment, or indirectly via a connection from JMRI software. The touch screens can usually be configured with multiple throttles on screen. Multiple handsets on most systems, one handset for one loco, other handset for second loco.

The only thing you can do with the EZ is reprogram decoder to a short address between 1 and 9. (Or put it in the waste bin and get a decent DCC system). Reports so far suggest a fault, but unclear if its a loco or a decoder fault. There are scenarios for both which fit the reported behaviour. - Nigel

If you want control via JMRI, and thus EngineDriver/WiThrottle, then its available: https://www.jmri.org/help/en/html/hardware/roco/z21/index.shtml I think it translates as this:

Yes it can, if the Tortoise is wired following the instructions in the Tortoise manual. Requires either: a) an AC power source, typically around 12-15v AC, and two rectifier diodes, that creates three wires: + volts, 0volts and -volts. b) a "stacked DC power source", typically achieved with two DC power bricks of about 9v DC, connected so the +volts of brick1 is connected to the 0volts of brick2. This also creates three wires which are: 0volts (relative to brick1), +volts (relative to brick1) and 2+volts (relative to brick1). Or re-labelling them relative to brick2, its -volts, 0volts and +volts, the same as you get in (a). The single pole change-over switch then selects between +volts and -volts, and the result goes to the motor. The other side of the motor connects to the 0volts. Once you get your head round this approach its very efficient in number of wires to baseboards, etc.. The return to the 0volts from all motors can be connected to each other, so its 1 return wire for entire layout and 1 wire out from each switch to each motor. - Nigel

No, its how the decoder is working (or not working). I don't know where Gaugemaster sourced their next18 decoders, but a quick look at their manual suggests its not a very advanced design. Different decoder and it will work - a J72 I did a couple of years ago would run for at least 2 feet without power. I used a Zimo decoder, which is what I guess was used in the Hornby magazine article.

Gaugemaster rebadge decoders designed by others. Currently they sell rebadged Digitrax decoders.

If you tried it, then you'd know whether the stay alive still works.

There's no issue with coreless motors and DCC on commonly available decoders. (There may have been an issue 25 years ago on a handful of very early decoder designs which used very low frequency control of motors. Which is just like analogue DC use where there are some DC controllers which use low frequency control which are bad for coreless motors....). As the model responds under programming, I'd look for things like: a) is the correct address being called up ? b) is the model in a decoder consist (CV19 set to anything other than zero) or does the control system have it in an internal consist (so routing instructions to another address). It doesn't sound like an electrical or motor issue if the model moves when programming is happening.

Most likely explanation is DC-running is enabled in the decoder (CV29). The decoder interprets this as DC, so engages full power in the DC direction. Turn off DC running to deal with the problem. https://www.2mm.org.uk/articles/cv29 calculator.htm

Manufacturers are under no obligation to stick to wiring colour conventions. So, if red is connected to negative, that doesn't matter to them.