A new Digikeijs owner
Recieved my Digikeijs DR5000 command station, DR5033 booster and a DR5088RC block detector late last week. Spent the holiday weekend installing and learning about the system and have some comments to share.
The layout had two10+ year old Digitrax Zephyr DCS50's, one running as a booster. I am planning to utilize RailCom to report the loco number back to JMRI for automated running, among other things and all decoder purchases during recent years are RailCom capable(ESU and TCS). RailCom requires a command station that will use an interupt for the RailCom signal, and a detector that can receive the signal.
Looking at available options, TCS is still working on their command station which has RailCom and LCC, RRCirKits is still working on a block detector with RailCom and LCC capability, and ESU's Cab Control has RailCom but their LocoNet is not yet active. Because I have a significant investment in SE8c,s, BDL168's, DS64's and Digitrax throttles having LocoNet is important. With the TCS/RRCirKits combo I would end up with an LCC bus and the LocoNet bus connected via JMRI but the Digitrax throttles would not function.
Digikeijs components seemed to answer all my needs. They have RailCom capability and the command station handles LocoNet complete with working Digitrax throttles. Ryan at Iron Planet Hobbies is the USA distributor for this Dutch company and great to work with. Free shipping is prompt and the components arrived in good time and great shape.
First task was to download the software and manual, upgrade the firmware, do some setup on the command station, then hook up and run trains. The software runs on a PC and connects via USB using 3 COM ports: config, LocoNet, and XpressNet. I need to run the LocoNet-over-TCP server on the command station. The setup went well and when hooked to the track, to LocoNet and to power the Digitrax throttle worked perfectly. The software could also open a throttle and run trains. So far, so good.
My layout has a couple of unique 'opportunities'. Mounted on the layout is a RaspberryPi 3 B+ running JMRI connected via a Digitrax PR3 to LocoNet. The PC (located across the train room) is connected to the internet, can run JMRI, and uses an RRCirkits LocoBufferUSB to also connect to the LocoNet. This allows remote control of the layout for such things as grandchildren and remote dispatching. JMRI handles two or more computers connected this way very well.
The Digikeijs DR5000 command station has a built in LAN and wireless WLAN which I understand is the same module. RocRail and other software can connect thru your home router to the LAN. The Z21, Roco and some other throttles can connect directly to the WLAN. You can run JMRI on a laptop using a LocoNet-over-TCP (LNTCP) connection, run the WiThrottle server in JMRI on the laptop, and run trains with your smartphone running Engine Driver(Android) or WiThrottle(iPhone). There are aso a couple of other phone apps that can connect directly to the WLAN.
Here's where things went a bit south. My objective was to connect the RaspberryPi to the LAN and eliminate the PR3 to LocoNet connection. The RPi running JMRI was set up with an LNTCP connection and after some experimenting and learning I was able to connect the RPi to the LAN and control the layout. Engine Driver could connect thru the RPi to the DR5000 and run the trains.
But when I connected the laptop to the WLAN, the LNTCP connection on the RPi crashed. Restarted the RPi and connected the PC running JMRI via USB and the LNTCP COM port, and the RPi crashed again. Connected the PC running JMRI first and had the train running then connected the laptop and LNTCP crashed on the PC. Subsitiuted a second laptop on the LAN for the RPi, with the same results.
My conclusion at this point is that the LocoNet-over-TCP server on the Digikeijs DR5000 can only handle ONE attached device connecting via LNTCP.
The one benefit to the Digikeijs system (and the ESU Cab Control) is that it is upgradeable. This was one major factor in my initial decision. I have been in touch with Digikeijs support in the Netherlands and have had many email exchanges with Ryan at Iron Planet Hobbies. I do expect that I will see a solution some time in the future.
My present solution is to connect the RaspberryPi thru the PR3 and LocoNet, and to connect the PC thru the LocoBufferUSB and LocoNet. That combination is bulletproof. Phones and the ProtoThrottles still connec thru WiThrottle on the RPi. The LAN receptacle and WLAN are currently un-used.
I gained an upgradeable command station that utilizes my Digitrax throttles and Digitrax accessories (for a lot less money than the LCC option), and one that can utilize RailCom. I've lost the conveniece of a throttle on the Zephyr. All-in-all I am happy with where I am at with this system. Below is a graphic of how my layout wiring is connected. BTW there are two LocoNet connections on the DR5000. The LocoNet-B has RailSync and is required for boosters and Digitrax BDL168's. The LocoNet-T is for throttles and everything else.