Jump to content

GoingUnderground

Members
  • Content Count

    1,855
  • Joined

  • Last visited

Community Reputation

681 Good

Profile Information

  • Location
    I'm still in a hole. Should I stop digging?
  • Interests
    Need you ask? London Underground, the GC Woodhead Route with its EM1s and EM2s, and Swiss Railways, particularly the RhB. Oh and skiing, but at my age it gets harder to lose the weight each year to get into my ski pants. Ideal railway, well apart from the Underground, it must be the Gornergratbahn - where else can you ski and go train spotting at the same time.

Recent Profile Visitors

2,599 profile views
  1. The CabControl inherits much, but not all, of its features from the ECoS. The ECoS doesn't have an "Immediate Stop for the running loco" button, but you can force it by configuring it to stop the loco on change of direction, I don't know if that option is available on CabControl, sorry I only have an ECoS and an MC2 handset. To use it with ECoS, you configure the ECoS to Stop the loco on change of direction, and to use it you simply change direction using either the throttle knob, or joystick, or onscreen direction of travel arrows. ESU do warn that the immediate emergency stop on
  2. Can't help you with No.1. The STOP button does what it says on the tin, stops everything by cutting the power at the Main Track out, as described in the manual. You don't need a dedicated button, to stop the current loco, just touch the left hand end of the blue speed slider bar below the loco icon to return the speed of the current loco to Zero.
  3. Nigel is right that 10 amps is excessive. It also has another downside in that it might damage the Select as Hornby may not have designed the Select to be able to cope with a 10 amp supply. But I'd hope that its short circuit/over current protection would cut the track power before any damage occurred. If you have a 2.5 amp one, use that and see how you get on. If that isn't enough, you could get the 4 amp Hornby PSU, they don't seem to be too expensive. But you only need the higher amperage if you have several locos on the move at the same time, and the Select isn't the ideal cont
  4. You are very, very, lucky that the Select only registered an overload. NEVER connect a DC or low voltage AC power source to a layout when the layout is also connected to a DCC controller. If you break that rule it can destroy the output transistors on the DCC system. That's why I say you are very fortunate that all the Select did was register an overload, when it could have turned up its toes. As others have said, you can replace the 1 amp power supply unit that comes with the Select with one with a higher amperage. There appear to be 2 suitable PSUs made by Hornby the
  5. Yes. That is the purpose of the sniffer port, to let you do precisely that. See section 8.8 in the ECoS manual on how to connect a 3rd Party DCC system to the sniffer port. You will have to set up each loco on the SmartControl. Whatever address you give each loco on the SmartControl you need to set up that loco on the ECoS with that address as its sniffer address. In fact I suggest you use the same address as you are using on the ECoS. For example, you may have a loco where the decoder address is 1357 and that's how it is set up on the ECoS. You need to set
  6. Thank you for posting the videos. A 501 Watford to Broad Street via South Hampstead, or to Queens Park and then the Bakerloo line were my routes to work in the early 1980s. So thanks for the memories, and, of course, for the beautiful modelling on Hornsey, an inspiration.
  7. I would agree with you were it not for the fact that neither ESU nor Piko have ever claimed that the SmartControl system can be used with an ECoS. As I've already said, you can interconnect them through the sniffer port, same as with a 2nd ECoS or any 3rd party DCC system, and use the SmartControl handset to control locos, and the ECoS track plan diagram for your points, signals and routes. If you do this, do NOT connect the SmartBox main track out to the layout, it's only connection should be to the sniffer port, and the ECoS main track out should be the only connection to the lay
  8. Forget it. You're wasting your time. The ECosLink bus has master and subsidiary devices. Masters have 7 pin sockets, subsidiaries 6 pin sockets, as you've already noticed. If ESU intended us to be able to connect Masters to Masters then they'd sell a 7 to 7 pin cable. I strongly advise against buying or trying to make up your own 7 to 7 cable as, as far as I know, ESU has not published the pin-outs, and you risk doing serious damage to both devices if you try. And don't try using the 6 pin AUX socket on the ECoS. ESU introduced that with the ECoS 2 saying that it was for future dev
  9. Agreed. I'm afraid that I see the way that some programs do a recap after the ads or after an intervening, often unrelated segment, as simply a way to fill airtime as cheaply as possible, thereby reducing the cost of making the programme. The interleaving of different and often unrelated, threads in a programme is just a way to keep people watching, and for me adds absolutely nothing to the quality or watchability of the programme. In fact it does the reverse by breaking up the flow and annoys the hell out of me. But so many programmes do it, even the ones whose subject matter I en
  10. One of the great things for me about Tim's programme is that he doesn't just look at disused or unchanged buildings and structures. It includes modern ones, like Rotterdam Centraal, reinvigorated ones like Leipzig, small ones like Woody Bay, hidden ones like the Catesby tunnel, ones with no public access like the Severn Bridge Junction signal box, and buildings that only exist because of the railways like the houses in Metroland or the covered way adjoining Malvern station. Also he never forgets the reason for their construction, the locomotives and rolling stock, unlike some other
  11. It's an incorrect assumption that a DCC train won't move because there's no "carrier" as you put it. Most, DCC decoders will run quite happily on DC provided that CV29 has been set to allow running on analogue, and the DC voltage is high enough as DCC decoders need a certain minimum voltage before they start working on DC. The "bit of a buzz" from a DC loco on DCC powered track is a big risk. The longer a DC loco sits stationery on DCC powered track the greater the risk of the motor overheating and burning out. This may well be a particular risk for the Narrow Gauge locos in ques
  12. Incidentally, Piko 59113 was the complete SmartControl DB Freight starter set, http://www.dcctrainautomation.co.uk/piko-59113-smartcontrol-dbag-freight-starter-set-vi-dcc-sound.html not just the SmartControl handset. Apologies, I should have checked before replying when I realised that there was no ESU 59113, but the similarity to the ESU MC2 part number 50113 made me think that your 59113 was a simple typo.
  13. So far, folks seem to be concentrating on the risk to the DC locos' motors. My concern would be that you could damage the output transistors on your DCC controller if there was any way that the DC supply could be fed back in to the DCC circuitry. This could happen if there was a derailment. So I'd be looking to make sure that when running on DC in the mixed gauge section that the DCC rails were totally isolated from the DCC supply, and when on DCC that the DC rails were totally isolated from the DC supply, and that there were clear dead sections between the mixed gauge and the DC a
  14. ESU have very, very vaguely hinted that there might be the very remote and very distant possibility of the SmartControl and SmartBox being supported by them, much the same way as they took over support for, and still do support, the Maerklin Central Station 1 through their CS1 Reloaded firmware upgrade. But it was only the merest and vaguest of hints about the SmartControl/SmartBox. So I definitely wouldn't count on it happening as it may well depend on the contractual relationship between ESU and Piko, and that might give Piko a veto over such a move. All you can do
  15. I have never heard of anyone trying to use a Piko SmartControl handset with an ECoS as if it were a Mobile Control II. Whilst the Piko SmartControl appears to be identical to the ESU Mobile Control II in terms of the hardware, and the appearance of the Piko SmartControl app looks like the ESU Mobile Control app, and the Piko SmartControl app seems to have the same vversion numbers as teh early versions of the ESU Mobile Control, that doesn't mean that they are interchangeable, as you seem to have proved. There might be a software bar in the SmartControl app to stop it connecting t
×
×
  • 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.