I think there has been a bit of confusion as to what my board is and what it can do. I’ve probably not been as clear as I should have been so I’ll try to clarify that here.

First, the ‘widget’ is a design I have been working on for several years now. It’s gone through a couple of iterations of hardware but for the most part this is a final design. It is meant to be a generic ‘Internet of Things’ device. That itself is a bit confusing as IoT means different things to different people. However, since my application is controlling large scale model trains, I’ll describe it in those terms.

This board will drive motor controllers (ESCs), external serial devices (sound cards, for example), servos, relays and provides a logic level Digital Command Control (DCC) output. It will also accept inputs such as digital and analog devices, sensors, etc.

That is the physical side of the board. On the network side it will accept Bluetooth modules, Xbee, Wifi and SNAP mesh. This means you can run it with your phone, your raspberry Pi or your PC. I also have a couple of proprietary handheld controller designs I’ve been playing with but for now I’m concentrating on Android Phones since they are cheap and available.

My main concentration now, since I am interested in all the cool things DCC decoders will do for you (including saving a lot of wiring inside the locomotive) is to support the three main Large Scale DCC decoders- QSI, SoundTraxx and TCS WOW. I am writing android apps for this with the first one being for Bluetooth. Others will follow as time permits.

Got my new boards in for the latest widget design. On the left is the DCC Amplifier, it turns the logic level signal from the widget into a 15v DCC signal. The board on the right is the new Megawidget.

I have moved away from SOIC components as they are hard as heck to solder by hand. So this one sports an Atmega328 28 pin thru-hole microcontroller. I still have one SOIC component, the 3.3v regulator for the network module but it’s a pretty easy hand solder and the thru-hole version is ridiculously large.

Another advantage to this microcontroller is I can run it at 16mhz using an external crystal. It’s a pretty speedy little sucker at that clock rate.

The boards came out perfect in terms of electrical connections, I didn’t have to cut any traces or add any jumper wires. However I do have a bit of a spacing problem on both the controller and the DCC amp that I will have to address on the next pass. The ISP programmer port is too close to the bluetooth module and the logic input on the AMP requires that I wire it instead of putting a pin header – but for now they are ok.

The plan is to refactor all of my existing code on the firmware side and get it all squeaky clean- bluetooth network, servo control and the DCC output. Hope to have that done this weekend. Eventually it will drive a TCS WOW Sound 5A DCC controller that I will probably put in my Aristo U25B.

I pulled another project off the back burner and got the basics working. This is a Android Phone App I wrote in Python that interfaces to my control widget but with Bluetooth instead of 802.15.4. It uses the same DCC output code as all my other widgets but with a Bluetooth Network interface instead of Xbee. I seem to be late to the party all the time but I found this unit- it’s a pin Xbee compatible unit so it will fit right into my Control Widget design with no problems, just some different software. In the picture above, the unit on the left is my Asus 7″ tablet and the one on the right is a cheapo smart phone I got off of Amazon. Both work quite well. Not sure on the range yet, once I get the boards built I’ll be installing it all in my Aristo U25B for some real world testing.

I don’t have all the function codes working quite yet, but the throttle works great. This is all done with a BT board I’ve had laying around for a while- I have one of the above Xbee type units coming so I will be refactoring the code a bit for that anyhow. I should have boards for testing in about a week.

Here is an expansion of my R/C to DCC circuit. I now have all six channels of a cheap 2.4Ghz Radio Control System driving a 2Amp Economi DCC decoder. Throttle stick drives the speed, the other sticks trigger the bell, horn and other sounds. I have one of the switches doing the direction. The DCC amp can drive a 4A load with peak to 5A so more than enough for most G scale Here I’m driving a single USAT motor block. Still have a couple of small issues in the firmware but for the most part it works quite well. I am going to try to finish this off over the next few days and design a PCB for it.

Here is a diagram of the transmitter controls

A video of everything working. Can’t quite see the blue LED that is the backup light, but the Headlamp LED is quite bright. I still have channel 5 open, not sure what to do with that one at the moment. Basically, you can do throttle, direction and 8 functions with a six channel system.

I’ve been neglecting one of my main investments and interests, my airplane- 172ME.

So I spent some vacation time working on sprucing her up. Put in some new plastic trim and painted the headliners. New seats and wall panels are coming in June. I guess next pass will be an owner assisted 100hr with Dan the mechanic man. I need to take out everything to the bare metal on the inside and put it all back in new. And then do something about the paint on the outside. At least touch it up. Needs new seat belts too, and ADS-B. Always something 🙂

Ok, not engineering but eh. Here are my new Brahma Chickens. Ordered 18, they sent 21. All arrived fine and healthy. These will grow into rather large birds, the males can reach 12-14 lbs. I’m not sure why I like chickens but I do. This is the first time I’ve gotten all one breed of chicken. Last shot IS engineering I guess- my fortress Chicken Coop with automatic aluminum door, all solar powered.

Got my prototype to run first pass. This is a motor driver chip that I have wired to convert logic level DCC to 14v 5A DCC. I was working with the LMD18200 but that sucker was $16 from mouser! Ouch. And it only did 3A. This is the L298N which is only 3 bucks from Sparkfun. Big difference! Now I just need to layout a PCB and get it off this breadboard. Sometimes rainy days are not so bad…

I’ve been working with the series 1 Xbee for several years in order to control large scale model trains. For those not familiar with this device, the Xbee 1 is an integrated package that communicates on the 802.15.4 IEEE wireless network. This is the base level network, only the MAC layer, no mesh or other high level network layers. I have the device configured in ‘API’ mode, which means it accepts standard format messages with a header and checksum and passes those out to the network. It’s actually very simple- all of the nodes are on the network and any node (via a 16 bit address) can talk to any other node. So this means I can do anything with this from controlling trains to controlling turnouts or animations or sending back telemetry from the locomotives, etc, etc.

Well, it turns out that the 802.15.4 protocol is rapidly becoming one of the standards used in IoT, Internet of Things. From what I have read, it has about 65% or so of the wireless IoT market share. So I’ve been working on ways to control large scale trains with this in mind. I’ve had quite a bit of success with this and now one of the outputs of my control widget board can generate DCC messages to directly drive DCC decoders (up to 3Amps for now, I have a 5amp version I’m working on).

This is an open-ended algorithm, it can generate the proper DCC bit stream from any input of hex bytes. This lets me keep the network traffic down as the widget generates all the timing for the DCC signal. I only have to pass the basic commands over the network which keeps everything nice and small and fast.

Anyhow, here is the latest incarnation of the DCC 802.15.4 Widget driving a QSI decoder. This one is installed in an Ariso Dash9. Unlike previous designs this one has only one connection- the DCC output from the widget. This is fed to a ‘DCC amplifier’ that then drives the QSI DCC decoder. A 14.8v 5000mah battery provides the power.

This was an interesting install for a couple of reasons. First, the decoder is ‘plug and play’, I disconnected the track pickups and plugged the decoder into the socket- everything just works, no rewire of the motor blocks or LEDs! Very cool. The outputs of the DCC amplifier then drive the decoder directly, no motor controllers or relays or anything.

The second reason was the software. I’m not sure about the vintage of the QSI firmware but it was not happy with the extended DCC packet format for the throttle messages. So I branched the software and made a version that only sends the base DCC packets. I put the QSI into ’28’ step mode and all was good. I wasn’t particularly pleased by this but what can you do eh? I still need to do some CV tweaking for the momentum and braking but it’s working well.

At some point I will be trying out the new WOW large scale decoder and the Economi 400 to see how they react to the extended packets. I’ve played with the Econami 100 and 200 decoders so I assume the 400 will behave in a similar way. Nevertheless, I’m thinking I will need to re-work my firmware to include both the extended and the base level DCC packet generation. That is the official standard according to the DCC docs so I should support it.

Above is the basic circuit. On the left is the DCC driver, then next assembly is the 14v to 5v stepdown power supply which can deliver 2.5 amps of 5v (for servos, etc) to the IoT Widget. In the middle with the Xbee is (obviously) the Control Widget. On the right is speaker #2, I’ll be routing most of the horn and bell sounds to this one with the big sub in the engine compartment handling all of the prime mover sounds.

A picture of the main speaker driver. This is a tangbang full range speaker with passive radiator. Really nice bass from this unit. Here is link to it: tang-bang-speaker

Here is a shot of the ‘terminal’ (Hand held controller) I’ve developed for interacting with the IoT 802.15.4 network. This one is a back-lit alpha numeric display which works great- I can see it out on the layout as it gets dark at night.

Above is a new design I’m trying out- This is a full color graphic touch screen that has tons of features. It incorporates a usb programmer port, a speaker and a built in lipo charger circuit. I just can squeeze it into the same case as the alpha display so we shall see how it goes. Work in progress.

This is the widget driving an Econami 200. Since it’s only 2 amps, I will probably be using this in a critter or railcar of some type. Right now all I have it hooked to in this video is the speaker.

Here is a video of the widget controlling the QSI. I think all the firmware changes are in so I’ll be buttoning up the unit and taking it out to the layout soon for some real world testing. I may go ahead and run the servo lines out just so I don’t have to open it back up when I put servos on the couplers.