DCC
More Wires
10 April 2012 01:35
After saying I was going to finish up the DCC electronics several times, I’ve finally made a start. There are two parts to this. The first is finishing up the remaining DCC power protection and occupancy detector panels. I did the first three tables last year, starting around January. The third was the first I’d done as a removable panel, which I wired up back in November. At the same time I’d begun the work of setting up a third accessory power bus, adding a switch and meter to the main panel. However at that point I’d stalled, with my attention off the layout over the holidays, and when I returned it was to work on buildings.
Read More...
Read More...
Bus Wiring and November 2011 Status
03 December 2011 22:48
DCC is often said to simplify a model railroad because it requires “only two wires”. While that’s true to an extent, most real model railroads will require quite a bit more. Or maybe I just like to over-complicate things.
Read More...
Read More...
DCC Power II
27 November 2011 22:01
The DCC Power work continues, but it’s still not done, as I have to do the power panels for the urban scene and the unsceniced return loops, but with the panel I built and tested back in September/October finally installed under the tables of the River Crossing scene, I’m at the halfway mark (having done the Riverside Station scene back in March).
To recap, the board contains a PM42 DCC circuit breaker that provides four separate circuit breakers and a BDL168 occupancy detector that can provide up to sixteen occupancy detectors and eight transponding sensors (see my pages on occupancy detection and the BDL168 for more details). This board provides occupancy detection for six electrical blocks, two each on the commuter tracks and one on each subway track where it loops below the expressway. Although I’m also wiring up the transponding sensors, as mentioned previously I’m having doubts about them due to problems in testing and the anticipated low power draw of my trains being borderline to register on them.
Read More...
To recap, the board contains a PM42 DCC circuit breaker that provides four separate circuit breakers and a BDL168 occupancy detector that can provide up to sixteen occupancy detectors and eight transponding sensors (see my pages on occupancy detection and the BDL168 for more details). This board provides occupancy detection for six electrical blocks, two each on the commuter tracks and one on each subway track where it loops below the expressway. Although I’m also wiring up the transponding sensors, as mentioned previously I’m having doubts about them due to problems in testing and the anticipated low power draw of my trains being borderline to register on them.
Read More...
Fun with JMRI II and September 2011 Status
07 October 2011 22:57
I’ve been playing around with JMRI some more, and trying to debug my transponding problem with the first of the electronics boards. This is really baffling. I checked the wiring, and it was fed through the RX sensor properly. I replaced BOTH the PM42 and the BDL168 circuit boards (I’ve got a stack of them waiting for more electronics boards once I get this one working) and I tried using other blocks. And I had more transponding sensor failures. On both sets of RX sensors. One defective set I might accept, but two?
So I tried a variety of things, and noticed that the non-functional detectors would, every once in a while, work. In fact, I discovered that with the train motionless, one of them would periodically cycle from detection to non-detection, emitting a LocoNet message reporting the change in status each time. I tried moving the wires. I pulled a fresh RX1 set out of a bag, and set it up atop a trash can (see above) with every wire fed through it fully separated from every other wire in mid-air (about the middle of this I was holding things in both hands and wishing I had a third arm). And that failed too, reliably as it were.
Read More...
So I tried a variety of things, and noticed that the non-functional detectors would, every once in a while, work. In fact, I discovered that with the train motionless, one of them would periodically cycle from detection to non-detection, emitting a LocoNet message reporting the change in status each time. I tried moving the wires. I pulled a fresh RX1 set out of a bag, and set it up atop a trash can (see above) with every wire fed through it fully separated from every other wire in mid-air (about the middle of this I was holding things in both hands and wishing I had a third arm). And that failed too, reliably as it were.
Read More...
Fun with JMRI
28 September 2011 00:52
Some weeks I don’t get much done. Well, that’s not quite true, I did a lot of work on the website this week, but the railroading time suffered. I did find some time to play with the test track I’d set up last week though, configuring JMRI to report block status based on the BDL168 outputs.
If you’re not familiar with JMRI it’s a free software package that allows a computer to interact with any of several DCC command stations that support computer interfaces, including Digitrax. It’s also available for Windows, Linux and Macs. And while not the most Mac-like program, it works, even on the ten-year-old iMac I’m using for the layout controller.
So what I have is a test track that’s an oval divided into two electrical blocks, each connected to an output of the BDL168. I named them, creatively enough, “One” and “Two”. And I used the Layout Panel editor to draw a schematic of the track. When displayed, red shows occupied (it’s configurable) and green shows clear. Even on my old computer, the change is nearly instantaneous once the locomotive crosses the insulated rail joiners from one block to the other.
Read More...
If you’re not familiar with JMRI it’s a free software package that allows a computer to interact with any of several DCC command stations that support computer interfaces, including Digitrax. It’s also available for Windows, Linux and Macs. And while not the most Mac-like program, it works, even on the ten-year-old iMac I’m using for the layout controller.
So what I have is a test track that’s an oval divided into two electrical blocks, each connected to an output of the BDL168. I named them, creatively enough, “One” and “Two”. And I used the Layout Panel editor to draw a schematic of the track. When displayed, red shows occupied (it’s configurable) and green shows clear. Even on my old computer, the change is nearly instantaneous once the locomotive crosses the insulated rail joiners from one block to the other.
Read More...
DCC Power I
20 September 2011 23:27
After assembling the first of my DCC protection and Occupancy Detection boards, I decided I wanted to test it and get some experience with using it. So I set up my loop of test track with insulated rail joiners separating it into two halves, and connected the feeder to outputs 1 and 2 of the BDL168, which correspond to RX4 A, detectors A & B. All of these are powered by PM42 section 1. For DCC, I used my Zephyr, and for the DC supply I used the 2 Amp, 12 Volt supply I plan to use for these systems (it’s the black box just above the Zephyr in the photo above). Powering it up, nothing went “Zap!”, which I count as a success.
Read More...
Read More...
Miscellany and March 2011 Status
05 April 2011 01:06
March was another of those “not much obvious happened” months. I did manage to get the layout back together, with two of the circuit-breaker/block-occupancy-detector systems wired up. And I installed some lighting in the Subway Station as a test. But I still don’t have the track back together and operational (I’m waiting on some more DCC electronics on order). In the meantime, I’ve amused myself with several things and some work on the website as I plan my next moves.
First, I’ve taken more photographs of the Overhead Transit Station (photo above) and the associated platforms I’m using on the Urban Station scene, and updated my pages for it and for the Unitrack platforms. The photos were also added to the Stations photo album. Once I get the Riverside Station track operational, I’m going to be turning my attention to the Urban Station for a time (and as noted last time I’ve added a page about the Urban Station itself). I have some new track (Kato’s new V15 20-874 set and 20-875 single-track concrete-tie track) on order for that, about which more after it arrives. I really like the combination of the Overhead Station (and expansion for a second platform), the new platforms, and the V15 set; this makes for a really nice modern-looking station.
I’ve also done some more testing of DC power packs, checking out the behavior of pulsed power on motor temperatures (no effect that I could measure) and examining yet another power pack. The notes on both have been added to the DC Power Pack page. Photos were added to the Electronics photo album.
And I built another of Don’s LOLBoosters, and ran some tests for him. Not much to say on that, but I added a couple of photos and some text to my page on it.
Read More...
First, I’ve taken more photographs of the Overhead Transit Station (photo above) and the associated platforms I’m using on the Urban Station scene, and updated my pages for it and for the Unitrack platforms. The photos were also added to the Stations photo album. Once I get the Riverside Station track operational, I’m going to be turning my attention to the Urban Station for a time (and as noted last time I’ve added a page about the Urban Station itself). I have some new track (Kato’s new V15 20-874 set and 20-875 single-track concrete-tie track) on order for that, about which more after it arrives. I really like the combination of the Overhead Station (and expansion for a second platform), the new platforms, and the V15 set; this makes for a really nice modern-looking station.
I’ve also done some more testing of DC power packs, checking out the behavior of pulsed power on motor temperatures (no effect that I could measure) and examining yet another power pack. The notes on both have been added to the DC Power Pack page. Photos were added to the Electronics photo album.
And I built another of Don’s LOLBoosters, and ran some tests for him. Not much to say on that, but I added a couple of photos and some text to my page on it.
Read More...
How I learned to stop worrying and love the BDL168
08 March 2011 00:39
Well, perhaps that’s a bit strong, but I’m coming to terms with its design flaws and the poor state of the documentation surrounding it and the PM42. I now have the first set of PM42 circuit breakers and BDL168 occupancy detectors (with two sets of RX4 “transponding receivers”) installed, and have done a bit more reading over the weekend. I’ve discovered a few things and come to a few conclusions as a result of that work, and that’s making me feel that I have a handle on this now. But I had to work through a number of issues to get to this point.
Read More...
Read More...
February 2011 Status - Occupancy Detection Revisited
03 March 2011 23:43
Work has progressed slowly this month, partly from distractions, and partly because I’ve been reluctant to finish up the block occupancy detector wiring. I finally realized that the reason for this was that I wasn’t happy with my hybrid approach to occupancy detection and transponding.
To recap, my Subway and Commuter loop tracks were to be divided into blocks, with Digitrax BDL168 occupancy detectors and PM42 circuit breakers (circuit breakers are typically one per track per table, whereas there may be two, three or even four detectable track sections on a single track on one table, and more in a couple of cases). The PM42 provides for four circuit breakers, which is a nice fit for the four tracks, and the BDL168 is divided into four independent quadrants (so each can be wired to a separate circuit breaker), each with four block detectors. I’d originally planned one PM42/BDL168 per scene, meaning that wires would have to cross a table boundary in the Urban and Riverside Station scenes.
And that was a problem, for several reasons. First, running wires between tables violates my “keep all wires except bus wires local” design goal (it makes the layout harder to disassemble), second while the BDL168 can support 16 occupancy detectors, in some places I needed more than four on one track, which broke the association of the PM42 circuit breaker element to a single track, meaning a short would shut down a second line. And finally, I wanted to do Transponding, and the BDL168 only supports 8 transponding sensors (using a pair of RX4 sets), meaning some blocks would be able to report which train was in them, and some would only be able to report that some train was present, but not which. None of these were fatal flaws, but they were eating at me. And I finally realized that I only needed two more sets (seven instead of five) to fix these problems.
Read More...
To recap, my Subway and Commuter loop tracks were to be divided into blocks, with Digitrax BDL168 occupancy detectors and PM42 circuit breakers (circuit breakers are typically one per track per table, whereas there may be two, three or even four detectable track sections on a single track on one table, and more in a couple of cases). The PM42 provides for four circuit breakers, which is a nice fit for the four tracks, and the BDL168 is divided into four independent quadrants (so each can be wired to a separate circuit breaker), each with four block detectors. I’d originally planned one PM42/BDL168 per scene, meaning that wires would have to cross a table boundary in the Urban and Riverside Station scenes.
And that was a problem, for several reasons. First, running wires between tables violates my “keep all wires except bus wires local” design goal (it makes the layout harder to disassemble), second while the BDL168 can support 16 occupancy detectors, in some places I needed more than four on one track, which broke the association of the PM42 circuit breaker element to a single track, meaning a short would shut down a second line. And finally, I wanted to do Transponding, and the BDL168 only supports 8 transponding sensors (using a pair of RX4 sets), meaning some blocks would be able to report which train was in them, and some would only be able to report that some train was present, but not which. None of these were fatal flaws, but they were eating at me. And I finally realized that I only needed two more sets (seven instead of five) to fix these problems.
Read More...
Building A DCC Booster
25 January 2011 01:45
It’s been longer than usual between updates. That’s partly because other things kept me away from working on the layout or this website (the layout is still apart awaiting final assembly of the backdrops), but mostly it’s because I’ve been spending evenings the last couple of weeks building and testing a DCC booster kit. I didn’t actually need another booster, but Don offered me one and it seemed like a good way to gain some soldering experience (which it was, although I had a bit of a scare when it didn’t work).
Read More...
Read More...
DC Motors, Poles, and Skewed Windings, Oh My!
12 December 2010 22:22
So, what is a “5 pole” motor, and why should I care if my models have one? And do they? That question occurred to me a few weeks back, and I’ve been doing a bit of reading since then. What I discovered was a mixture of fact and Internet lore of uncertain origin. I also discovered that some models do have “5 pole” motors, while others have “3 pole” ones. But oddly, at least in the case of Kato (and possibly also Micro Ace), the “3 pole” motors are the better ones. Or at least the newer ones, although I think they’re better too.
Read More...
Read More...
Kato Lightboard Flickering II
20 November 2010 02:50
I seem to spend an inordinate amount of time worrying about light. First it was the layout lighting, then it was the flickering interior lights, which annoyed me when I detailed my first commuter EMU, and which I wrote about nearly two months ago when I did the original planning for a flicker-prevention circuit. Now I’m back, having built several prototypes and refined my design. I think I have a winning solution.
Read More...
Read More...
A Matter of Time
11 November 2010 23:18
Railroads have always been concerned with time. Early ones used timetables alone to keep trains on the same track from colliding. This didn’t work very well, particularly given the accuracy of mid-1800‘s pocket watches and the lack of synchronized time sources, and many lives were lost. Signaling systems and other protection methods were gradually developed. But timetables continued to be important for all trains in scheduling the use of tracks even with other systems used for protection, and timetables were required for passenger trains, as trains from different places needed to coordinate their arrival and departure at interconnection points, so passengers could move smoothly from one to the next as part of a longer journey. Railroads gradually developed standards for time-keeping (and they’re responsible for the adoption of the standard time zones used in the U.S.), and also influenced the development of clocks and watches to provide accurate and synchronized time sources.
Japanese passenger trains today are famed for their obsessive adherence to schedules, with deviations measured in seconds, not minutes. So it only seems reasonable that a model railroad of a Japanese passenger line should operate to timetable (well, eventually,I need a yard/staging tracks before that will be much fun).
Read More...
Japanese passenger trains today are famed for their obsessive adherence to schedules, with deviations measured in seconds, not minutes. So it only seems reasonable that a model railroad of a Japanese passenger line should operate to timetable (well, eventually,I need a yard/staging tracks before that will be much fun).
Read More...
Freight Trains, Electronics and October 2010 Status
01 November 2010 23:27
Not much got done on the layout itself in October, mostly I’ve been running trains (as documented in an earlier post with a video) and doing a bit of electrical work (mostly the previously noted update to the power panel). I’ve spent a good bit of time on a couple of other things though.
Read More...
Read More...
Adding a DCC Meter, And Related Topics
22 October 2010 00:54
Although I wrote about the power panel previously, there were a couple of things left undone. I was missing one of the ammeters for the lighting power (the store I get them from had run out), and I’d misplaced one of my LNRP LocoNet Repeater panels, so I’d substituted a UP5 panel I took off the old HO layout. Also, I’d realized that my portable RRampMeter DCC volt/amp meter was useful, but wiring it into the system when I wanted to check something was a real nuisance. Over the summer I bought or found the missing bits, and finally decided to order a new RRampMeter (the version without the nice case) to mount as a permanent part of the circuitry (I’m keeping my other meter--the one with the case--for workbench and other testing uses). So it’s a good time to summarize what the panel does, and talk about the new meter a bit.
Read More...
Read More...
Car Lighting Power Protection and September 2010 Status
03 October 2010 23:04
There isn’t much status to give for this month, as the only major layout event was finally completing the Rapid/Shinkansen loop and running DCC trains (a major milestone, but one I’ve already covered). But this month also marks the one-year anniversary of when I first started keeping this record (I didn’t actually get it online until November, but I was making offline entries and writing down design information from September 2009), and it’s worth a short look back on the year.
Read More...
Read More...
Detailing a Kato Commuter EMU
28 September 2010 01:21
I haven’t done much work on the layout recently. Aside from having fun running trains, I’ve been working on finishing up my first DCC train. I started added DCC decoders (motor and cab) to this train last October.
Read More...
Read More...
Kato DCC Decoders and a Decoder Tester
18 September 2010 00:05
Now that I have some real working track, I’m even more motivated to get some of my trains converted to DCC (so far there’s just one, the Jōban E231 described on my Adding DCC and Lights page). So, back I go to the hell that is Kato “DCC Friendly” decoder installation. Really, the marketing person who thought that phrase up was truly evil. There’s nothing friendly about this process. DCC doesn’t have to be hard, but with Kato it all too often is.
Read More...
Read More...
Tunnel Roofs, Castings and Track
11 September 2010 00:51
Just a brief update: For the last month or so I’ve been working on the Subway roof that carries the Rapid/Shinkansen tracks along the front of the Riverside Station scene, above the subway tracks at the front of the table. That’s now been “finished” (WS inclines glued where needed, plaster and roadbed applied over that, all painted) and it’s supporting the tracks quite nicely. The decision to use 2mm sheet styrene turned out to be a good one. The track here is a bit hard to visualize (and some of it is missing in the above photo), see the track plan for a diagram.
Read More...
Read More...
Myths The Internet Told Me and August 2010 Status
04 September 2010 01:54
The Internet is a wonderful invention. Without it, I wouldn’t be able to order trains from halfway around the globe and have them delivered in under a week, nor would I have any idea of the difference between an E233-1000 and an E233-2000 (both are commuter trains, but the 2000 is a narrow-bodied variant with a end door for emergency exits; this model runs through onto the Chiyoda subway and nobody makes a model of it yet, but I want one). I hear that some people have more serious uses for the Internet, as well.
Read More...
Read More...
