| Build | Status (github) |
|---|---|
| MSVC |
DccLite is an open source software for controlling a model railroad. It is loosely based on DCC++, but it does not implement a full command station like it. This software is aimed for those who need to control model railroad accessories, like turnouts, lights, read input from sensors, etc.
You can easily connect it to JMRI and use it to control your model railroad acessories, turnouts and signalling system.
If you would like to know more, please visit our (working in progress) wiki at: DCCLite Documentation
Support an infinite (depends on your network) number of IOT devices connected to the server for controlling model railroad devices.
You can configure and control each IOT node using this tool, an Arduino or any other board for:
- Turning on / off leds or signals
- Throwing / closing turnouts using servos
- Reading sensor states
And this can be easily integrated with JMRI and use all the rich features from JMRI to control your model railroad devices.
The main design goal of DCCLite is to be easy as possible to config and specially, to do fine tunning of devices without the need for recompiling code and uploading it to an Arduino. This is specially useful when you have a large model railroad and in such case, a single Arduino will not be enough for all devices.
Another design goal is to allow the installation of the Arduino boards as close as possible to where they are needed. If you have a yard throat with several turnouts and signals, instead of running wires all over the place, you can put a single arduino mega (or perhaps two) close to it. For controlling it, you just need to provide power and connect it to a Ethernet cable connected to your local network. No need for running dozens (or even hundres) of wires from the devices to the Arduino meters away.
Lua scripting support was added. This allow you to add custom behavior to your layout when something happens, like executing a custom action when a signal aspects changes or when a turnout is throw.
This tool can be integrated with JMRI for easily controlling your devices. The Broker server emulates a DCC++ connection and JMRI will think that it is simple talking with a DCC++ device. But diferent of a regular DCC++ device, DccLite can be composed of several Arduino boards spread all over your model railroad talking with your PC throught an Ethernet network.
Why not use DCC++?
Until the current date (March 2024) DCC++ does not have an easy or standard way to serve multiples Arduinos for a large model railroad. Right now, only for controlling my model railroad staging yard I need four Arduinos just for turnouts.
So, DCC++ does not allow me:
- Have multiple Arduinos working together on the same layout / network
- Allow simple configuration throught config files and without needing to use serial port commands and plugging arduino to PC everytime I need to adjust a setting
- Configure and use Servos on Turnouts
On the other side, this project is not aimed as a replacement for DCC++, but also as a independent system for controlling model railroad devices. It does not include code or support for controlling mobile decoders (locomotives), like DCC++.
So, why not use DCC++Ex and EX-Rail?
This project started before DCC++EX and also before their Automation (EX-Rail) project. Probably most of the DccLite functionality is covered there, but it still requires to compile and keep uploading code on a Arduino or any other IOT device, as DccLite you can simple do this from a config file and let the server software (Broker) automagically upload this to the IOT device. Much simple and easier process for fine tunning your model railroad.
I do not claim that this way of doing things is better or worse for any solution you choose. But, the DccLite is my preferred method and works fine for me.
This code needs the following libraries to be built:
- cityhash
- Dear ImGui - Optional, only for building IMGUI apps (still in development)
- Ethercard
- Freetype - Optional, only for building IMGUI apps (also optional even with those tools)
- Fmt
- GoogleTest
- JsonCreator
- ldmonitor
- Lua
- magicenum
- RapidJson
- SDL - Optional, only for building IMGUI apps (still in development)
- Sol
- spdlog
- sigslot
- wxWidgets - Optional, only for building native GUI apps (still in development - abandoned?)
All code is licensed under the MPLv2 License.