RAF96

Firing the 6010 pulse output into a relay coil is foolproof where the relay contacts direct the CDU discharge direct to the solenoids.

Probably no different from the call to keep the screen live when a phone is plugged in, say for use as a sat-nav.

This will continue to happen until you stop your phone nodding off, regardless of the app setting.

Correct. It is a simple matter if the track is DCC powered to drive the 6010s from a PSU direct. I made up a cat-o-9-tails to power several 6010s from a spare single P9300. If you use the Hornby track adapter cable the PSU output can be plugged into a choc-block connector and onward to as many jack plugs as you have 6010s. You can feed DC into the 6010 Track connector in lieu of a jack input. The jack size is 6.3mm x 3.0mm and easily found on the net. Such multi-plugs are available for CCTV cameras but only in 5.25mm jack size.

The app has a setting also to pause and resume or not when the phone nods off. Once again operator problem, not hardware or software.

It is with regret that I announce the passing of Yelrow after a long fight with cancer. John was an outspoken forum member and a fountain of knowledge across all scales, especially Hornby-Dublo 2 and 3-rail. He will be sorely missed.

Just remember the output of the CDU is relative to the square of the voltage so a 19 volt supply would give a lot more oomph than a 15 volt supply. You can power the 6010s from the Track DCC supply but then it can only be operated by a DCC controller not OTA from the app. Just a quirk of the 6010 unit. It doesn't have a CV12 like to loco decoders to flip twixt app and DCC. There is another way to have levers and the app, in that you can fire the output of the 6010 into the coil of a pair of relays (one for each point direction) and the relay pulls in long enough to allow the CDU to punch thru' the main contacts direct to the solenoid motor.

You can request to join the TGG group, noting that it only runs on windows and uses Hornby Elite or eLink as the controller(s), which will rule out many folk.

I'll stick with TGG. Loco detection is cheap and uncomplicated. Auto-ops is by way of program scripts written in English not 'puter speak. It is like Railmaster but with sensor driven events not timed events.

The problem is that the same folk post the same problem on many fora, giving the impression it is a widespread problem when in fact it is likely local to one or two folk. Other folk are reporting no problems with ECoS but there is this programming short, which is odd. You should get an indication of a fault (usually loco wiring) on the prog track but the short duration and limited potential of the signal should not trip a controller. Regardless of that Hornby will be looking at the problem next week when they drag their dusty ECoS out of the cupboard, where it has been since last testing when nothing untoward was seen.

7K decoders are 1 amp so twice as capable of handling loads than their previous decoders. All clearly visible in the spec sheet in the famous manual.

You cannot re-map TTS sounds. I'm sure it says that in the blurb somewhere.

The app has just bern update to fettle the power cycle anomaly. Also each profile has been updated with the CV19 glitch fix. Before reporting or trouble-shooting faults it is always recommended to install the latest profile version.

You have to realise that using an 8pin decoder restricts you to directional lighting plus aux 1 and aux 2. A 21pin decoder will add 2 x logic level aux functions.

Ask Liais for a copy of the instructions they knocked off with the device.