Jump to content
 

BusDriverMan

Members
  • Posts

    83
  • Joined

  • Last visited

Everything posted by BusDriverMan

  1. By NSE days, stations had rationalised their trackwork a lot, with big pressure to use simple, standard pointwork wherever possible… lots of double slips in a station throat suggests steam era or Kings Cross If you already have three-way points, double slips, or scissors crossovers, might be better to use them to improve the fiddle yard! I've had to cut back the scope of my own layout… which is a shunting layout in N on a salvaged 1200x200mm board. Which will no longer have a loop. Which means… more shunting, ok, not so bad then
  2. I swore off inkjet printers forever after staining one too many kitchen curtain with unexpected behaviour of refill kit syringes but you're making me reconsider £70 (plus endless ink) is very cost-effective for the results you're getting here!
  3. I particularly like the back elevation and the guttering! Sorry - I think you answered this in a video or a youtube comment already - but is it right that pretty much all of the brickwork, stonework, tiling etc across the whole layout are the output of your desktop printer?
  4. I received mine yesterday - D8606, BFYE, weathered, and very pleasing! It's my first loco with a Next18 socket and I haven't ordered a decoder yet. Was wondering if anyone can advise how many LEDs are used for the head and tail lights and can they be individually switched? By the look of the exploded diagram there's two LEDs under the nose at each end - one for the headcode box and one for the tail lights. I'd like to be able to control all four LEDs explicitly from four decoder functions - is that possible? Tail lights switched on when the loco's not running light is a particular annoyance of mine. Another is having both tail lights on at once - until the late 80s the only train that did that were the Edinburgh-Glasgow push-pulls and trains carrying the head of state. Looking at the diagram, the tail lights operate with a lightpipe from a single LED, so turning one of them off would be a permanent operation by removing part of one lightpipe - has anyone done this? Finally has anyone customised the headcode panel and retained the lighting? Applying Rule 1 - in the alternate universe my layout is set in, by a quirk of fate, these designs turned out to be reliable and became the standard Type 1 loco. So I'd rather like to give it a domino headcode and TOPS markings for that post-1977 look
  5. I built a DCC++ throttle, and expanded it awkwardly into a decoder programmer, after losing all patience with JMRI DecoderPro for this. The Bodnar code was the inspiration but I wrote mine from scratch, sending commands to the DCC++ base station over its serial interface. The control panel was an early experiment in CNC engraving, with one of those cheap desktop mills apparently intended for engraved circuit boards. Key lesson was not to expect good results from plywood offcuts… Electronically it's an Arduino Nano with an encoder, some keys, and that 7-segment display all wired directly to it with precarious ribbon cable. I built it to act as a basic controller - turn right to make loco move right, turn left and it goes left. Then I added other modes, experimtally. In one, the encoder became the reverser, and the two function buttons below became "Accelerate" and "Brake". This made shunting an Inglenook layout more fun. I've stripped everything off my layout and will be rewiring it from scratch, with a sensible power supply arrangement that's not the bodge you see in the photo. I plan to build a new controller to be fixed to the edge of the layout, along with separate or swappable throttle units which more accurately reflect a real train's controls e.g. reverser, power lever, brake lever, physical head- and tail-light switches, speedo showing MPH… but that's some way away at the moment! I'd like the layout controller to be able to act like a TOPS terminal. Rather than plainly entering a decoder ID and sending speed instructions to it, you'd define a train (possibly including several locos/motors/decoders) and assign a specific cab to a throttle unit. Config info stored on an SD card then will map the throttle inputs to speed commands to specific decoders. (I'm dimly aware of stock DCC techniques for consisting, involving writing CV values, but I strongly believe the only job a decoder ought to be doing is making a motor turn at a specific speed, and all the fancy stuff should happen in the controller system.) I'll award myself bonus points if I build a throttle unit that's a facsimile of a 1st-gen DMU control desk complete with gear-shift control, that can also be plugged into my computer and used with Diesel Railcar Simulator
  6. Maybe we need a Shapeways equivalent for etched components…
  7. AC electrics will fit in perfectly as long as you include a 25kV steam generator wagon and a hefty jumper cable as the first vehicle…
  8. I could do with a few sets of these… is there a practical way I might be able to order some?
  9. Stripped out the redundant track, most of the original wiring, and the original controllers. Skimmed everything with plaster and painted a neutral grey - looks a lot neater now! I'd started cutting track but realised the loop was far too cramped, so it will be a siding instead.
  10. Basically as well as vaccines the government ought to be providing every household in the UK with a pillar drill. If elected I will… 94000 looks absolutely fantastic. I love what-if designs.
  11. I've thought about making an experimental miniaturised NX panel, either standalone (with probably Arduino-based interlocking, TD berth control, and train simulation) or interfaced with SimSig. Probably using pushbuttons and a "CANCEL" Shift key rather than push-pull switches because cost / availability. I'm thinking of a design based on ~25mm square tiles, probably cosmetic rather than actually modular, using 64x32 OLED screens for berths and possibly addressable RGB LED strips for the route lights. Gratified the relevant Railway Group Guidance Note gives provision to have the first route light to flash white instead of strictly requiring the routesetting switch to flash!
  12. This is just to say you're building my dream layout here - 3rd rail with fully prototypical signalling…! I'm actually devastated that you've had so much success with JMRI as you expertly documented in the other thread. It confounds me, so I was convinced I'd need to write my own system running on a Raspberry Pi and a network of Arduinos (or Atmel microcontrollers with Arduino firmware) to achieve a layout with working signalling controlled by a route-setting panel. But now I know JMRI is definitely a viable option
  13. It's still there now! Or at least, mostly still there - haven't been close up to compare to the photo here.
  14. @D6150 go on, give us a clue - real prototype or ahistorical? Which hemisphere?
  15. Looking very good! Wish I had the wherewithal to create ad-hoc apps like that. I think there's scope for 1-3 Dapol signals plus perhaps two dummies. The station would probably have had a distant, home, and starter in each direction, plus a subsidiary to signal from the platform to the yard and a shunting signal from the yard to the platform. I've wanted to have a go at sketching signalling diagrams for ages, so thanks for the pretext. Not to scale, these are the signals and points (and facing point lock on lever 5) that would probably have been operated by the signalbox: The numbering is semi-realistic for a lever frame, I think - in reality they wouldn't be numbered 1-10 with no gaps, there'd be two or three spare levers in the middle somewhere. Signal 8 you'd definitely want, for signalling trains from the platform to the fiddleyard Signal 7 is a subsidiary signal, for trains going from the platform to the yard. I think you could either - scratchbuild or kitbash a dummy subsidiary signal onto the post of signal 8 - omit Signal 7 and use Signal 8 for movement into the yard - not particularly realistic but a good compromise Signal 2 could either be in the scenic area or assumed to be further back out of sight. If it's in the visible area it would be positioned so approaching drivers can see it. Signal 3 could either be in the scenic area or beyond the backscene. it wouldn't get used much unless you're using the fiddle stick. Signal 4 is, I'm not 100% sure of the correct name for it, a yellow shunting signal. It only applies for movement over the crossover. When the crossover points are normal trains can pass it at danger to get to the other side of the yard. When the route is set over the crossover, trains leaving the yard must wait for it to clear. Signals 1, 9 and 10 would definitely be well outside the scenic area. There would probably be a small signal cabin, big enough for a 12-lever frame, somewhere near the fiddleyard end of the platform. I have no idea how the ground frame would be set up - I some of the points could've been operated with an individual lever near the point blades! If you really felt adventurous, you could add a page to the phone app representing the 10+ levers in the signalbox, and operate signals that don't physically exist…
  16. That looks absolutely fantastic - and I love the CAD mockup! (Cardboard Aided Design... )
  17. Oh, I like this very much! I'd always wanted to make something similar - maybe a Mk1 BSK or BFK with a 504 cab end, roof destination box, no jumper cables... What's the theory - Blue Star control with the other coaches through-wired?
  18. Plankton is my first layout. It's intended to be a small fun shunting layout where I can develop my skills and play with ideas, set in the late 70s somewhere in the fictional Scotland in my head, where rail transport receives subsidy that's at least proportional to that of roads, and air-braked wagonload freight fits between turn-up-and-go passenger services on lines purposefully worked close to capacity. I've always had an interest in railways, and had a few 00 models as a kid, but layouts never progressed beyond ambitious track plans. I came back to railway modelling when I found I could make a cheap base station with DCC++, cheap block detection with current transformers and an Arduino, and thus build a layout with working signalling and interlocking. Not that I've managed to get the block detection to work yet, but I'm working on it! Plankton started out as a 1200x200mm baseboard for an unknown modeller's uncompleted layout. It sat in my local MRC's scrap pile for a while until I nabbed it in 2017. I quite quickly laid down an Inglenook layout, stuck the DCC++ base unit underneath, made a homebrew controller based on another Arduino, and was up and running. The points are motorised with SG90 servos superglued directly to the underside of the baseboard, and with some adjustable feet underneath it has a semi-permanent home in the living room on top of the piano: The original plan had been to cram in Timesaver alongside Inglenook. Perhaps Timesaver could've been a wagon workshop, and Inglenook the marshalling yard for arriving and departing wagons. But when I placed the tracks down it looked very contrived and cramped, with a requirement to stable wagons on the turnout linking the two sections, so I abandoned that idea. This is the new plan - a branch terminus with a run-round loop long enough for a Type 2 + five 15ft wagons (or two coaches), with a crossover to the yard. I've suggested where signals would go - PL is "Position Light", either shunting or subsidiary, and YPL is a yellow position light shunt signal for movement over the crossover onto the main line. Inspired by @Izzy's Priory Road, I think I can get a 450mm sector plate overhanging the edge of the board which can fold out of use - possibly a train turntable. Alternatively the line would continue to the board edge, with a kickback siding for stock storage. The operating pattern would be: 1. With eight wagons and a shunting engine in the yard, assemble five wagons as per Inglenook rules 2. Freight train arrives with five more wagons and is signalled into platform 3. Train engine leaves wagons in platform and runs round back to the home signal 4. Train engine backs onto prepared train in the long siding and departs (into the sector plate road it came from, filling it) 5. Shunting engine collects wagons from platform into yard (pulling forward into an empty sector plate road) 6. While shunting takes place, DMU or prototypically short loco-hauled passenger train arrives and departs from the third sector plate road, giving a rationale for not using the extra space of the main line and loop for shunting. I want the signalling to be colour light, partly because I like colour light signals but also because I am deeply unenthusiastic about making working lattice-post semaphores in N gauge. Also because the idea of building an NX panel is what brought me back to railway modelling. Now, "colour-light 1970s branch terminus" is a bit contrived - maybe it's a short urban/suburban branch included with the resignalling of a larger station and controlled from its signalling centre as a rationalisation measure and operated under Track Circuit Block. Or maybe the line is Absolute Block and there's a signalbox and signaller at the terminus, and scope for simulating block instruments. I was scratching my head a bit about how to signal freight trains departing the yard. Should they get a starter signal, should they just proceed under the authority of the yellow shunting signal, or should there be another Up signal on the other side of the two turnouts to the platform starter? Since making the diagram I've decided there'd be another signal a short distance down the line. Next steps will be to get block detection working as this will inform how the rewiring goes, lift some of the track, remove the controllers from the board edge, then give the whole thing some paint. I'm pretty tired of staring at the blue board!
  19. I like the electronics board! I also have Arduino-controlled servo-driven points on a similar layout, but on mine the electronics are mounted directly to the underside of the baseboard - I think your way is better. I don't recognise all the components here - top left is a bluetooth or wifi module, right - will you operate points with your phone? And how did you select the DC converters?
  20. BusDriverMan

    Starfighter!

    wait wait you've missed off the wing outer panels, no way an aircraft had such tiny wings
  21. Looking really good! Is that a little chunk missing from the top of the destination display mounting? How are you planning to glaze the cab front? The horizontal line where the offside panel is bonded to the destination box is quite distinctive - worth painting a stripe directly onto the inner side of that glazing panel?
  22. I love the planning and organisation here! Y'know, it'd be quite straightforward to draw up those modular stripboard point controller modules and get them cheaply made as PCBs. Possible new product for Mr MegaPoints as I'm sure many others would like the same control system.
×
×
  • Create New...