Mark DiVecchio's O-Gauge Train Layouts

1992 Layout Page

2006 Layout Page

2009 Layout Page

P&LE Postcards by Howard Fogg 

Plasticville Buildings

Portable Layout Page

Train Clubs

Bing Track

Remote Train Control Program

YouTube Channel

OOK Radio Support

Technical Videos

3D Prints for my Layout

More RTC Videos

ADPCM - Playing clips from .mth sound files

P&LE McKees Rocks Locomotive Shop
3D Printer Project

White Tower Restaurant
3D Printer Project

RFID Train Detection
Engine and Car Operation
Hints and Tricks

RFID Tag Programmer using PN532

RTC Control Language - Scripting

More RFID Tag Videos

RTC Control Language - Signaling
ESP8266 Sketches :
RTCRemote
 RTCWTIU

RTC Adapter

This Page last updated on .

I started development of this web page in January 2025. It will be under construction for a while.

On this page, I describe the ESP8266 code for RTC Adapter (in sketch RTCAdapter.ino using built-in WiFi and an external CC1101E radio) .

Click here for the copyright notice.

If you want the program itself, drop me an email .

You can follow our conversation about RTCAdapter on the OGR Forum at:    https://ogrforum.com/topic/rtcadapter-missing-link-between-a-remote-and-wtiu

 Background

I've been working on ways to control my MTH trains from my PC for many years. About 8 years ago, I released the first version of my Remote Train Control (RTC) program for the PC. The very first version was for a TIU tethered between the Remote jack on the TIU to a serial port on the PC (or a USB serial port). Next came a radio which enables RTC to communicate to over a wireless radio connection to a TIU. After that came the ability for RTC to communicate over WiFi with both the WIU/TIU and the WTIU.

I've written several utility sketches to help me learn and understand how the trains are controlled. For example:
With a lot of effort, I was able to understand almost all of the communications between the Remote and TIU. I am now able to create packets to control the engines. The packets are complete with correct addressing, command syntax and CRC.

I figured this out by examination of the packets that I could sniff using Mike Hewett's original RS-232 interface design and the port settings that he found. Without Mike's insights into the RS-232 data stream, I don't think that I would have been able to get a foothold into this protocol.

So again, I figured this out just by looking at the RS-232 stream over the tether cable. No code disassembly, no logic analyzers, no opening up of Remotes or TIU's.

The sketches originally used USB based serial communications to the RTC program using the Infiduino. Then they moved to the ESP8266 using WiFi commications with the RTC program.
Now I've written an ESP8266 sketch that acts as a bridge between a Remote and the WTIU (RTCAdapter).

 The ESP8266

Mike Hewett always seems to be acknowledged on my web pages and he deserves it. Mike learned about the ESP8266 based NodeMCU board and started to use it in his projects. After I saw his success and how easy it was to use, I started to rewrite my RFID Train Detection (RTCNFCIRQ) sketch to use that device.

The ESP8266 is a small powerful computer connected to a WiFi Radio. They are available from many sources on the Internet. Watch out for knock-offs.

My Ideas

Below is a photo of an ESP8266. I've been using the LoLin version with the CH340 USB chip and one built-in LED on D4. Note that the CH340 chip (SOP-16 chip near the USB connector) is unlabled - probably a clone. Bought on eBay. It has built-in WiFi. Read below about the CH340 driver issues with the unlabeled chip in Windows.

NOTE: After all the trouble I had with the unlabeled CH340 USB chip, I no longer recommend the version of the ESP8266 with the unlabeled device. Apparently the unlabeled CH340 is a clone that does not work with the latest original CH340 drivers (which do work with the original CH340). Either find an ESP8266 with a labeled CH340 or use the ESP8266 with the CP2102 USB chip. When I bought these on eBay, the photo of the device showed a labeled CH340.





Below is a photo of another ESP8266. It is the AITRIP version with the Silicon Labs CP2102 USB chip and one built-in LED on D4. Note that the CP2102 chip (28 pin QFP SMD chip near the USB connector) is labeled. Bought on Amazon. It has built-in WiFi.

NOTE: After all the trouble I had with the unlabeled CH340 USB chip, I no longer recommend the version of the ESP8266 with the unlabeled device. Apparently the unlabeled CH340 is a clone that does not work with the latest original CH340 drivers (which do work with the original CH340). Either find an ESP8266 with a labeled CH340 or use the ESP8266 with the CP2102 USB chip.


The ESP8266 that I have all have the LED on pin D4. Some versions of the ESP8266 have the LED on pin D0. This can be powered with a USB cable plugged into a USB port (on your computer or on the WTIU itself) or directly from a 5 volt wall wart.

Assembled and Wired Hardware

For the RTC Adapter sketch, you need an ESP8266 with a CC1101 radio attached. There are a few sources for the radio and here are photos of two that I've used.  It requires some wiring to connect the two devices. I used 30 gauge wirewrap wire but any method of wiring will work. There is a photo below using female-female DuPont wires to do the interconnection.

RTC Adapter Versions 1, 2 & 3


RTCAdapter Version 1

 An ESP8266 with a CC1101E radio (from Elechouse) attached. This is needed for RTCAdapter script.

https://www.elechouse.com/product/915mhz-cc1101-wireless-module/
The illustration shown on this site is labeled RF1100SE but this specific 915Mhz version is V3.1.

This can be powered with a USB cable plugged into a USB port (on your computer or on the WTIU itself) or directly from a 5 volt wall wart.
Wiring side of the ESP8266 + Elechouse radio board.

Signal Name ESP8266
Pin		 CC1101E
Radio
Pin
VCC 3V VCC
GND G GND
MOSI D7 SI
MISO D6 SO
Select D8 CSN
SCLK D5 SCLK
GDO2 D2 GDO2
GDO0 D1 GDO0

RTCAdapter Version 2

 An ESP8266 with a CC1101E radio (E07-900M10S 8 pin version from Darrell Lamm) attached.

Get it from :  https://www.ebay.com/itm/144715454017

There is also a 10 pin version of this radio with the same pinout as the Elechouse board. Either one will work : https://www.ebay.com/itm/146353854626
Wiring side of the ESP8266 + E07-900M10S radio board. Note that this radio uses an 8 pin interface, just a little different than the 10 pin interface of the Elechouse radio (but all the same signals).

Signal Name ESP8266
Pin		 CC1101E
Radio
Pin
VCC 3V VCC
GND G GND
MOSI D7 MOSI
MISO D6 MISO
Select D8 CSN
SCLK D5 SCK
GDO2 D2 GDO2
GDO0 D1 GDO0

RTCAdapter Version 3

 An ESP8266 with a CC1101E radio (E07-900M10S 8 pin version from Darrell Lamm) attached using female-female Dupont Wires.

Get the radio from :  https://www.ebay.com/itm/144715454017

The 10 pin version of this radio will also work fine: https://www.ebay.com/itm/146353854626

This is a good quick and easy test bed that does not require soldering or wirewrap. These Dupont wires are not that great of a connection and since they are just push on, they can fall off. Find a more secure way to interconnect these devices for the longer term.

Signal Name ESP8266
Pin		 CC1101E
Radio
Pin		 Dupont Wire Color
VCC 3V VCC Yellow
GND G GND Green
MOSI D7 MOSI Blue
MISO D6 MISO Violet
Select D8 CSN Brown
SCLK D5 SCK Orange
GDO2 D2 GDO2 Red
GDO0 D1 GDO0 Gray

FWIW: These wires were first made by Berg Electronics which was sold to DuPont and is now owned by Amphenol. Pins are 0.025 x 0.025 inches square.

RTC Adapter Version 4

User "Bobbyding" on the OGR Forum, did me a great favor by designing a PCB for the RTC Adapter. He sent me two sample boards that he ordered and the Gerber files so I could make up as many as I need.


ESP8266 running the RTCAdapter script and one of Darrell Lamm's CC1101 Radios
Bobby designed it so that it could use the orginal Elechouse CC1101 radio, Darrell Lamm's 10-pin clone of that radio and his 8-pin version.
On this board, I am using Darrell's 8-pin version.
Links to all of the radios are just below.
The board can use both the LoLin version (with the CH340) and the HiLetgo/Aitrip version (with the CP2102) of the ESP8266.
One is slightly narrower than the other so be sure to check when you solder in your headers.
The LED, labeled RSSI which stands for Received Signal Strength Indicator. It lights up whenever a data packet is received from the Remote.

Bobby suggested that using headers would be good so that the ESP8266 and radio could be removed.
The RSSI LED and resistor are soldered on.
I used an LED that lit up nicely with a 8.2Kohm resistor. Your mileage may vary and a different resistor value may be needed.
You can put headers in all of the radio positions if you want.
The PCB Layout

Below are the links to get the Gerber files for this PCB.

RTC Adapter Version 5

I've also used a fifth version of the radio during early testing : an E07-915MS10 from ElecBee (formerly eByte). You can get it here.  This radio does not have wirewrap pins and you must solder wires to the radio board. It worked just fine.


Parts Sources

Here are some sources for the parts that I used. There are many others on eBay and Amazon.

For the Wirewrap assembly:

Proto board  : 4in-X-2in-7X5cm-Proto-Board-Double-Sided-FR-4

Wirewrap tool : wirewrap tool
30 Gauge wirewrap wire: 30AWG-Wire-Wrap-Wire-Blue

For the Dupont wires assembly:

Breadboard Jumper Wires (Dupont wires) Length 20cm, 40pin Male to Female, 40pin Male to Male, 40pin Female to Female :  

Three sources for the CC1101 Radio:

CC1101 Wireless Transceiver 868/915MHZ + U.FL Whip Antenna 8 pin  from Darrell Lamm w/ FCC/CE Cert : https://www.ebay.com/itm/144715454017
CC1101 Wireless Transceiver 868/915MHZ + U.FL Whip Antenna 10 pin  from Darrell Lamm w/ FCC/CE Cert : https://www.ebay.com/itm/146353854626
    -- web site of Darrell Lamm, designer of the CC1101 Wireless Transceiver:   https://oscaledeadrail.com/

CC1101 915MHz Wireless Module:  https://www.elechouse.com/product/915mhz-cc1101-wireless-module/

E07-915MS10 915MHz CC1101 SPI 1.2km 10dBm Communication Interface RF Transceiver Module:  CC1101-SPI-1-2km-10dBm-Communication-Interface-RF-Transceiver-Module

Three sources for the ESP8266:

NOTE: After all the trouble I had with the unlabeled CH340 USB chip, I no longer recommend the version of the ESP8266 with the unlabeled device. Apparently the unlabeled CH340 is a clone that does not work with the latest original CH340 drivers (which do work with the original CH340). Either find an ESP8266 with a labeled CH340 or use the ESP8266 with the CP2102 USB chip.

Aitrip ESP8266 NodeMCU CP2102 ESP-12E Internet WiFi Development Board      https://www.amazon.com

HiLetgo 3pcs ESP8266 NodeMCU CP2102 ESP-12E Development Board      https://www.amazon.com

LoLin NodeMCU Lua ESP8266 CH340G ESP-12E Wireless WIFI Internet Development Board (NOT RECOMMENDED):  https://www.ebay.com

The Gerber files for the PCB:

Bobby has given me permission to post these files. If you update them, I'd like to hear about what you did. Like all RTC bits and pieces, these are released under the GNU General Public License as published by the Free Software Foundation, version 3 or any later version as described at the bottom of this page. You can download the ZIP file and submit to most PCB fab houses to build the board (both Bobby and I used JLCPCB).

Gerber Files:   Gerber_RTC_Adapter_V2.0D_2025-06-03.zip
JSON Description :    PCB_RTC_Adapter_V2.0D_2025-06-03.json

For more information: "A History of Gerber Files and the Man Who Made Them" and "What are Gerber Files? Understanding the Blueprint of Electronics Manufacturing".

Headers used on the PCB

We use 1x10 headers (need 2), 2x4 headers and 2x5 headers (need one or the other depending on which radio you use). You can get these most anywhere.

RTC WiFi Adapter (sketch in file RTCAdapter.ino)

This requires that a CC1101E radio (such as the one from Elechouse, Darrell Lamm or eByte) be wired to the ESP8266.

This adapter does not control the WIU/TIU or the TIU, only the WTIU. It will co-exist with the WIU/TIU and TIU (thanks to Vernon Barry for helping me realize this). The Adapter sketch requires that the Remotes all be at version 6.10 and that each WTIU have a unique TIU number.

This is a new sketch that I've just started to develop so it is not complete yet (especially Super TIU Mode). It is meant to act as bridge between the Remote and the WTIU. The Remote only communicates via a radio and the WTIU only communicates via WiFi. This sketch, which requires a CC1101E radio, listens for commands over the radio from a Remote, translates them to what the WTIU requires and sends them via WiFi to the WTIU. Then it takes responses from the WTIU over WiFi, converts them to what the Remote requires and sends them over the radio to the Remote.

From version 12 of RTCAdapter onward, the Remote number selects between normal RTCAdapter operation  and "Childproof" mode. Remote numbers 1-7 and 15 operate in normal RTCAdapter mode. Remote numbers 8-14 operate in childproof mode. This mode restricts further what commands are processed. Click "Childproof" mode  for details.

The sketch named "RTCAdapter.ino" compiles into one runtime module which can be uploaded into the ESP8266. At the bottom of this page are instructions for loading a precompiled binary into an ESP8266 and instructions for compiling the source code yourself.

Communications :
There is some debug output that the sketch sends out the USB port. You can use a terminal emulator (I like 'Termite" or "PuTTY") set at 115200 baud to watch this debug output.

What works and what doesn't

  1. Keep your phone/pad handy. RTCAdapter was designed to let you run trains. It does not do everything that the App can do.
  2. This Adapter will co-exist with WIU/TIU and TIU as long as all TIU/WTIU have a unique TIU number.
  3. All of the Remotes must be at version 6.10.
  4. I only have one WTIU so I can't test Super TIU mode and the code for that mode is not complete. As a reminder, according to Barry's book, when you operate in Super TIU Mode, all TIU and all Remotes must be in Super TIU Mode. I've been able to do some testing using a WTIU along with a WIU/TIU and I would appreciate your feedback. I've ordered a second WTIU but more are not expected in country for several months (as of Feb 2025).
  5. I have tested all of the "normal" running commands (startup, shutdown, speed, whistle, horn, lights, couplers, smoke, etc.) for single engines, lashups and All Engine mode.
  6. I've tested all of the accessory and switch control functions (so routes and scenes should work).
  7. I've tested most of the hot keys.
  8. I've not tested any of the really esoteric things like Speed mode, Track and Trolley modes (and maybe others).
  9. Protocast and ProtoDispatch are not supported at all and will probably lock up the RTC Adapter and require a reboot.
  10. I've not tested TMCC mode as I don't have any TMCC hardware.
  11. The architecture of the MTH Remote/TIU system has one basic limitation. The communications over the radio uses one frequency to send commands to the TIU. This channel runs at 9600 baud (roughly bits/sec). When you use multiple Remotes, they all have to share this bandwidth. When you get "enough" communications traffic from many Remotes, commands start to get dropped due to colliding radio signals. Retries are attempted and that uses up yet more bandwidth.
  12. RTCAdapter always responds to the Remote as TIU Version 6.10 because the Remote only understands up to DCS v6.10.
Let me know what problems you find and I will try to fix them.

WiFi Setup

Make sure your WiFi router is powered on and operating. Follow all of MTH's instructions to connect the WTIU to the router in "HOME" mode.

See the hints section below if you want to run the WTIU in "MTH" mode. I've tested RTCAdapter in "MTH" mode and it seems to work fine.

If you have multiple WTIU, each should have a unique number/address. Use the App to set the WTIU numbers. "More->Advanced Features->System Settings->TIU Settings". Then select a WTIU and click on "TIU Address->Edit".

When you first load the ESP8266 with the compiled sketch and run it, it must connect up to the WiFi router (so we need the SSID of the router and the password) and you must tell RTCAdapter how many WTIU to look for.

The first time it runs, it will automatically connect in this "setup" mode. After that, it will reenter "setup" if the SSID router is not found or if you perform two presses of the ESP8266 reset button [RST] a few seconds apart.

Setup is performed by connecting to the ESP8266 from your phone or WiFi enabled computer. Tap on your WiFi icon and follow along (using the cell phone as the example):


 After you upload the RTCAdapter sketch into the ESP8266, it will start an Access Point (AP). If you look on your phone, you will see the new WiFi AP listed as RTCAdapter.

Touch on that AP to connect to it.

The phone should connect up and you should see "RTCAdapter Connected without internet".

If your phone can't seem to maintain the network connection, look for a prompt asking if you want to stay connected even though an internet connection is not available. When you get that prompt, press "Stay Connected".
Then startup a web browser. Enter this IP address into the Address Bar:  192.168.4.1 . Press GO. You should see this screen which lists all of the accessible WiFi routers in the area. Here is were we enter the information that the RTCAdapter sketch needs to communicate with your WTIU via the WiFi router.

Enter:
The SSID of your router
The WiFi password of your router
The TCP Service port of this device (don't change this).
The active WTIU on your layout. Check each box if the WTIU is present.
(You can pinch zoom in to make checking the boxes a little easier.)

Then click on [Setup Remote to WiFi Adapter].
You should see this screen indicating that the device has saved your information, is rebooting and will connect up the WiFi Router.

The ESP8266 will reboot and start. If the LED on the board stays on, the board is having trouble connecting to the router. If the LED blinks, the board is having trouble finding the number of WTIU that you specified.

If you need to change these setting after first setting them, press the ESP8266 reset button twice a few seconds apart. The ESP8266 will then let you go through these setup steps again.

The RTC Adapter will reboot.

The Adapter first tries to connect to the router. The LED on the ESP8266 will stay solid blue until it does that. If the LED stays on solid, it indicates the sketch can't connect to the WiFi router. Probably the wrong SSID and/or password were entered.

After the connection, the sketch fast blinks the LED to indicate how many WTIU are expected.

Then the Adapter tries to find your WTIU(s). It will try over and over forever. The LED will slow blink on each try. When it finally finds the WTIU(s) and they successfully handshake, the LED will go out. It must find exactly the WTIU that you entered during setup.

Then the sketch is waiting for commands over the radio from the Remote

Once everything is running, the LED will blink each time it forwards a command from the Remote to the WTIU.


Here are two videos of RTCAdapter in action. You can also watch these videos at this YouTube playlist link.


Image loading....


Tour of Trainroom and RTC Adapter Setup


On my layout, the Adapter is powered by a 5VDC wall wart but can also be powered by a USB port (on your computer or on the WTIU itself) .

1.    The Adapter acts as a relay between the Remote and the WTIU. It listens for commands from the Remote using a 915Mhz radio, translates those commands as necessary for the WTIU and then sends them to the WTIU over WiFi.

1.    The Adapter does not replace the App. This Adapter only does the easy stuff. You will need the App to do the hard stuff. Adapter lets you add engines,  runs engines and lashups and controls the AIU. At the top of this web page is a list of what it does not do. It only works with the WTIU, does not work with the WIU as the WIU/TIU combination already has radio based control from a Remote.



Image loading....


Running RTCAdapter


1.    I’m always looking for feedback on the Adapter. I’ve believe most engine and lashup functions work. I’m less sure about Super TIU Mode. I’ve gotten inconsistent results with that. Let me know what works for you and what doesn’t. I’ll do my best to fix the bugs.

Getting the sketches into an ESP8266

There are two ways to get the sketch loaded into the ESP8266

1. Use the pre-compiled binary file that I supply and upload it into the ESP8266 using a COMx port.

2. Use the pre-compiled binary file and I supply and upload it into the ESP8266 using the HTTPUpdater and a browser (like Firefox or Chrome). This requires that you do the very first upload using a COMx port.

3. Install the complete Arduino/ESP8266 development environment (IDE), compile the sketch yourself and load it into the ESP8266 using a COMx port.

4. Using the Arduino/ESP8266 IDE, compile the sketch yourself and load it into the ESP8266 using the OTA (Over the Air) technique. This requires that you do the very first upload using a COMx port.

Here are (probably incomplete) instructions for each method.

1. RTCAdapter : loading pre-compiled binary code using RTCAdapter-X.XX.zip and COMx port

RTCAdapter          This is an ESP8266 NodeMCU based sketch using WiFi and a CC1101E radio.

If you want to work with this, contact me for the zip file. I will have it on-line once it is stable.

1. install Python 3.12 from:

https://www.python.org/downloads/release/python-3128/

I used the "Windows installer (64-bit)". Some users have reported that they had to check the box  "[X] Use admin privileges when installing py.exe" in order for the "upload.bat" file to execute correctly.
 

Image loading....


Installing Python


You can also watch these videos at this YouTube playlist link.

2. Make a folder somewhere (Some users have reported difficulties if this folder is on a OneDrive)

3. unzip the RTCAdapterX.XX.zip file into that folder

4. connect your ESP8266/CC1101E to a USB port. You will need to know the COMx port that Windows assigns to the ESP8266. You can use the "Device Manager" to get that. Search for that program and run it. Click on "Ports (COM & LPT)" and note the COMx port assigned.

5. It appears that some (maybe all) ESP8266 are not supported by the default WIN10 and WIN11 CH340 driver. If you get a permission error on the COMx port when uploading, you will have to replace the current CH340 driver with an older version. On my computer, I replaced the current version 3.9.2024.9 with version 3.5.2019.1. I've run the following steps on both WIN10 and WIN11 machines:

    a. Go to the folder "CH340" which was installed as part of the main RTCAdapter.ZIP.
    b. Double click on "setup.exe". Click the [Yes] button at the UAC prompt.
    c. Click on [INSTALL] (for version 3.5.2019.1) and in a minute or so, you should see the "Driver install success!" message.

    You can look at the version of the driver installed by right clicking on "My Computer->Manage->Device Manager->Ports (COM & LPT)->Properties->Driver".
    If you ever need to return to the default CH340 driver, on the Properties window in Device Manager, click on [Update Driver].
    I found that Windows kept on updating the driver automatically. Click here for a Registry edit that should prevent this.

5a. Other versions of the ESP8266 use the Silicon Labs CP2102 USB chip. This version of the board seems to work better with the default Windows drivers. If the default Windows drivers don't get loaded, you can download the "CP2102 Universal Windows Driver" from the Silicon Labs web site. Unzip the file, right click on "silabser.inf" and select "Install".

6. edit the file "upload.bat" with notepad

    edit the port number for the USB port connected to the ESP8266

    change "COM3" to your USB serial port.

    save the file

6. double click on "upload.bat" and the upload into the ESP8266 should occur.

Image loading....

Loading Compiled Binary of RTC Adapter into the ESP8266


You can also watch these videos at this YouTube playlist link.

7. Here is a transcript of a successful upload:

E:\Projects\ESP8266\RTCAdapter>rem

E:\Projects\ESP8266\RTCAdapter>rem USB

E:\Projects\ESP8266\RTCAdapter>"C:\Users\markd\AppData\Local\Programs\Python\Python312\python" -I "upload.py" --chip esp8266 --port "COM3" --baud "115200" ""  --before default_reset --after hard_reset write_flash 0x0 "build\esp8266.esp8266.nodemcuv2/RTCAdapter.ino.bin"
esptool.py v3.0
Serial port COM3
Connecting.....
Chip is ESP8266EX
Features: WiFi
Crystal is 26MHz
MAC: c8:c9:a3:56:63:4b
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Auto-detected Flash size: 4MB
Compressed 408992 bytes to 292129...
Wrote 408992 bytes (292129 compressed) at 0x00000000 in 25.7 seconds (effective 127.1 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting via RTS pin...

E:\Projects\ESP8266\RTCAdapter>rem

E:\Projects\ESP8266\RTCAdapter>pause
Press any key to continue . . .

8. Then follow the instructions above to enter the SSID and password of your router into the ESP8266.


2. RTCAdapter : loading pre-compiled binary code using RTCAdapter-X.XX.zip and the HTTPUpdater (with a browser like Firefox or Chrome)

RTCAdapter          This is an ESP8266 NodeMCU based sketch using WiFi and a CC1101E radio.

If you want to work with this, contact me for the zip file. I will have it on-line once it is stable.

You must have used method 1 or 3 at first to upload the pre-compiled binary, then further uploads can use this method.

1. Open "http://RTCAdapter-XXXX.local:8885/update" in your browser - replace XXXX with the four hexidecimal digits of your ESP8266.

2. Just click [Browse...] to select the "Firmware" file at ".\build\esp8266.esp8266.nodemcuv2\RTCAdapter.ino.bin"

3. Press [Update Firmware]. The "FileSystem" update is not used.

3. RTCAdapter  : compiling source code using RTCAdapter-X.XX.zip and a COMx port.

RTCAdapter          This is an ESP8266 NodeMCU based sketch using WiFi and a CC1101E radio.

If you want to work with this, contact me for the zip file. I will have it on-line once it is stable.

To compile this from source code, I used the Arduino IDE version 2.3.4. You will have to download the IDE, install it and then install the ESP8266 board support.

1. Make a folder somewhere

2. unzip the RTCAdapterX-XX.zip file into that folder

3. connect your ESP8266/CC1101E to a USB port

4.  It appears that some (maybe all) ESP8266 are not supported by the default WIN10 and WIN11 CH340 driver. If you get a permission error on the COMx port when uploading, you will have to replace the current CH340 driver with an older version. On my computer, I replaced the current version 3.9.2024.9 with version 3.5.2019.1. I've run the following steps on both WIN10 and WIN11 machines:

    a. Go to the folder "CH340" which was installed as part of the main RTCAdapter.ZIP.
    b. Double click on "setup.exe". Click the [Yes] button at the UAC prompt.
    c. Click on [INSTALL] (for version 3.5.2019.1) and in a minute or so, you should see the "Driver install success!" message.

    You can look at the version of the driver installed by right clicking on "My Computer->Manage->Device Manager->Ports (COM & LPT)->Properties->Driver".
    If you ever need to return to the default CH340 driver, on the Properties window in Device Manager, click on [Update Driver].
    I found that Windows kept on updating the driver automatically. Click here for a Registry edit that should prevent this.

4a. Other versions of the ESP8266 use the Silicon Labs CP2102 USB chip. This version of the board seems to work better with the default Windows drivers. If the default Windows drivers don't get loaded, you can download the "CP2102 Universal Windows Driver" from the Silicon Labs web site. Unzip the file, right click on "silabser.inf" and select "Install".

5. Download and install the IDE from the Arduino download page.

    Click on menu item  "Tools->Board->Boards Manager", select "esp8266 Community version 3.1.2" and click on [Install]. There may be a newer version.

    Before compiling, use the "Tools->Board->esp8266" menu to select board "NodeMCU 1.0 (ESP-12E Module)".

    From the Arduino IDE, use the "Sketch->Include Library->Manage Libraries", find these libraries and click [Install]. There may be newer versions.
   
ESP_DoubleReset_Detector v1.3.2 by Khoi Hoang
ESP8266TimerInterrupt v1.6.0 by Khoi Hoang
Time  version 1.6.1 by Paul Stoffregen
  
    Then, from the zip file, copy the following additional libraries into the your library folder (...\libraries):

CC1101E_OOK_ESP version 1.0.0 as modified by Mark DiVecchio
CC1101E_OOK_ESP_SPI version 1.0.0 as modified by Mark DiVecchio
FIFObuf1.1.2 by Pavel Pervushkin as modified by Mark DiVecchio. I removed some debug print() statements which are not needed. (Do not load this from the Arduino IDE Library Manager - it retrieves an older verion)

    Press the [Verify] button on the Arduino IDE. It should be error free and if you set the IDE preference for verbose output during compile, you should see these libraries being used (they might not be in the same folders on your computer):

Using library ESP8266WiFi at version 1.0 in folder: C:\Users\XXXX\AppData\Local\Arduino15\packages\esp8266\hardware\esp8266\3.1.2\libraries\ESP8266WiFi
Using library ArduinoOTA at version 1.0 in folder: C:\Users\\XXXX\AppData\Local\Arduino15\packages\esp8266\hardware\esp8266\3.1.2\libraries\ArduinoOTA
Using library ESP8266mDNS at version 1.2 in folder: C:\Users\\XXXX\AppData\Local\Arduino15\packages\esp8266\hardware\esp8266\3.1.2\libraries\ESP8266mDNS
Using library EEPROM at version 1.0 in folder: C:\Users\\XXXX\AppData\Local\Arduino15\packages\esp8266\hardware\esp8266\3.1.2\libraries\EEPROM
Using library SPI at version 1.0 in folder: C:\Users\\XXXX\AppData\Local\Arduino15\packages\esp8266\hardware\esp8266\3.1.2\libraries\SPI
Using library ESP_DoubleResetDetector at version 1.3.2 in folder: C:\Users\XXXX\Documents\Arduino\libraries\ESP_DoubleResetDetector
Using library LittleFS at version 0.1.0 in folder: C:\Users\\XXXX\AppData\Local\Arduino15\packages\esp8266\hardware\esp8266\3.1.2\libraries\LittleFS
Using library FIFObuf at version 1.1.2 in folder: C:\Users\XXXX\Documents\Arduino\libraries\FIFObuf
Using library CC1101E_OOK_ESP at version 1.0.0 in folder: C:\Users\\XXXX\Documents\Arduino\libraries\CC1101E_OOK_ESP
Using library CC1101E_OOK_ESP_SPI at version 1.0.0 in folder: C:\Users\\XXXX\Documents\Arduino\libraries\CC1101E_OOK_ESP_SPI
Using library ESP8266HTTPClient at version 1.2 in folder: C:\Users\\XXXX\AppData\Local\Arduino15\packages\esp8266\hardware\esp8266\3.1.2\libraries\ESP8266HTTPClient
Using library ESP8266WebServer at version 1.0 in folder: C:\Users\\XXXX\AppData\Local\Arduino15\packages\esp8266\hardware\esp8266\3.1.2\libraries\ESP8266WebServer
Using library ESP8266TimerInterrupt at version 1.6.0 in folder: C:\Users\\XXXX\Documents\Arduino\libraries\ESP8266TimerInterrupt
Using library EspSoftwareSerial at version 8.0.1 in folder: C:\Users\\XXXX\AppData\Local\Arduino15\packages\esp8266\hardware\esp8266\3.1.2\libraries\SoftwareSerial


6. Before uploading the compiled sketch into the ESP8266, from the "Tools->Port" menu, select the USB COMx port connected to the ESP8266.

7. Then press [Upload] on the Arduino IDE.

8. Then follow the instructions above to enter the SSID and password of your router into the ESP8266.

4. RTCAdapter  : compiling source code using RTCAdapter-X.XX.zip and use the OTA (Over the Air) upload.

RTCAdapter          This is an ESP8266 NodeMCU based sketch using WiFi and a CC1101E radio.

If you want to work with this, contact me for the zip file. I will have it on-line once it is stable.

You must have used method 1 or 3 at first to upload the pre-compiled binary, then further uploads can use this method.

Follow the steps in method 3 up until step 6. Do this instead:

6. Before uploading the compiled sketch into the ESP8266, from the "Tools->Port" menu, select "RTCAdapter-XXXX at 192.168.1.117 (NodeMCU 1.0 (ESP-12E Module))". Where XXXX is replaced by the 4 hexidecimal digits of the ESP8266 and the "192.168.1.117" is replaced by the IP address of the ESP8266 on your network.

7. Then press [Upload] on the Arduino IDE.

 Childproof Mode

Version 12 of RTC Adapter supports what I am calling the "Childproof Mode". We know that really there is no such thing possible but I concieved of a version of RTCAdapter that prevents all dangerous commands from being forwarded to the WTIU.

And who can see handing a $1,000 iPhone running the App to a 6 year old to play with trains?

The Remote number selects between normal RTCAdapter operation  and "Childproof" mode. Remote numbers 1-7 and 15 operate in normal RTC Adapter mode. Remote numbers 8-14 operate in childproof mode. This mode restricts further what commands are processed. For example, in childproof mode, the Emergency Stop command is not sent to the WTIU (although the Remote still locks up).

These commands would be permitted but limited:
These commands would not be permitted:
Speed maximum should be programmed in the Remote. (MENU->CONTROL->MAX SPEED)


Possibly Useful Tools to Help Get your WTIU On-Line - WIU Packet

Here is a utility program that might help you confirm that your WIU or WTIU setup is correct. You can download this program from this DropBox link:

https://www.dropbox.com/scl/fi/lbbpr5ifvl327r14ikiqx/WIU3.zip?rlkey=2vhb92x1om67bjipmka6rvme0&st=gr29sj6g&dl=0

Just start it and you should see a list of the found WIU/WTIU in the upper right list box (this program finds both WTIU and WIU/TIU).



If you want to rescan your network again, press the [Scan WTIU] button.

Press the [Connect] button to create a WiFi connection the WTIU that you select from the list.

Press [Handshake] and this program will show you the TIU number and number of AIU connected to this WIU/WTIU. You might see something like this:

WIU/WTIU TCP Sending Local Port = 64629
Session Connected
H5 Response : H5 70973C94 okay
->
H6 Response : H66499F4B2 okay
->
x Response : x33
-> TIU/WTIU #4 with 3 AIU(s)

The [Find Engines] button will ask the TIU about the engines connected to it. You will see all of the engines that are associated with that TIU.

P&LE U28B #2808 :   Reading Engines   - TIU #4 : Engine # 1 of 2 Engine(s) Total
A&S 0-8-0 #211 :   Reading Engines   - TIU #4 : Engine # 2 of 2 Engine(s) Total

The [Send String] button will send whatever string you type in the box to the TIU. Don't use this unless you know the TIU commend set. This spreadsheet describes the TIU command set.

Checking the "Debug Mode" checkbox will display a lot of technical information that may not be useful.

Bonjour Browser

Another tool that runs on Android (and probably iPhones) smart phones. The program "Bonjour Browser" can search for local devices on your WiFi network like printers, scanners and .... WIU and WTIU.

Run the program on your cell phone and you should see something like this:



You won't see the detailed information that my program provides but you should see the WIU and WTIU listed. On this example, there are two MTH devices, mthdcs-1456 and mthdcs-00DE. If you see this on your smartphone, you can at least know that your devices are connected to the WiFi router and those devices are visible to the MTH App.

mDNS Discovery

Another useful tool is mDNS Discovery available from the Google Play Store (and possibily on iPhones).

In the Service Type field, you have to enter the service type for the WTIU, that is "mth-dcs". Make sure that "TCP" is selected. Press the [Search] button and you should see all of the WTIU on your layout.
 



mDNS Discovery is the same technique used by the App, RTC Adapter and the RTC program itself to locate WIU/TIU and WTIU.

 Debugging Hints

If you are having trouble getting the RTCAdapter going, here are a few things to consider.

1. To load the program into the ESP8266, the ESP8266 and the PC must be connected with a "data" type USB cable. There are also "charging" USB cables which only connect power and not the communications signals.

2. When you plug the ESP8266 into the PC, the PC should make a sound or at the least show you some kind of message in the lower right corner of your screen. If you don't get the sound, maybe you are using a "charging" cable.

3. Check that the PC can communicate with the ESP8266. Right click on "My Computer->Manage->Device Manager". Double click on "Ports (COM & LPT)". You should see something like "Silicon Labs CP210x USB to UART Bridge(COM3)"  or "USB-SERIAL CH340 (COM3)". You can look at the version of the driver installed by right clicking on "My Computer->Manage->Device Manager->Ports (COM & LPT)->Properties->Driver"

4. If the above hints don't help, you should load the older CH340 device driver as described above.

4. If you want to run the WTIU in "MTH" mode, it will work. Here are some hints:

        When you press the reset button (RST) button on the ESP8266 two times about 3 seconds apart, RTCAdapter will go back into setup mode and let you connect with your PC or mobile device to change the SSID and password to be used.

        The SSID and password would be same as what MTH describes in their documentation (pg 6 of WTIU User's Guide):
                    SSID :    MTH_DCS-XXXX ("XXXX" is printed on the bottom of the WTIU -  all upper case - the XXXX will have "zeros" but never "ohs")
                    Password : mthdcswifi     (all lower case)

5  If you have multiple RTCAdapters, you should be sure never to have two or more RTCAdapters powered on at the same time as that will confuse the Remote big time.

The Case


There have been discussions about a case (or box) for the RTCAdapter on the OGR Forum at:    https://ogrforum.com/topic/rtcadapter-missing-link-between-a-remote-and-wtiu

Travis Moody sent me some emails about what he did. I include that here:

Date sent:    Tue, 22 Jul 2025 00:41:02 +0000 (UTC)
From:    Travis Moody <moodytr89yahoo.com>
Subject:    Re: RTC Adapter PCB on the way

Mark,

Thank you for sending the PCB's. I will work on getting a 3D file made up to house it. Just doing some preliminary looking, if you decide to make a revision, it would be helpful to move the ESP board to the edge so that the USB port is not recessed from the edge of the main PCB. I will make a hole in the case big enough to allow larger headed cables to enter.

Travis
Travis,

Bobby, who did the PCB, was really just doing a PCB before anyone thought of a case for it. I agree with you, some alternate placement should be considered next time (if there is one).

Mark
Mark,

Very good. His case accounts for some heat dissipation, but I haven't had any heat related issues. I am attaching some pics to show what I came up with. I also found the antenna extensions to be needed for larger club layouts, but this thing works.

PDF description :   Moody Loco Works

STL file:   3D Print File

The case on Tinkercad:  https://www.tinkercad.com/things/14cXWwNW5Qg-rtcadapter-case

Antenna on Amazon.



AMAZINGLY. Great Job Mark, and thank you very much for all the hard work.

Travis






Copyright Notice

As I mentioned in the posts on the forum, I am releasing these programs and documentation under the  GNU GENERAL PUBLIC LICENSE Version 3 and GNU Free Documentation License Version 1.3. These licenses permit anyone to use the program and the documentation to produce follow on programs as long as those programs remain covered by the GNU licenses.

The Free Software Foundation web page talks about what "free software" means.

For more information, look on the Open Source Initiative web site which includes a description of what Open Source means and their certification of the GPL version 3.

Here is the copyright notice for those two licenses:
GNU GPL

This is part of the Remote Train Control Program for Windows
© Copyright 2025 by Mark DiVecchio

Remote Train Control is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

Remote Train Control is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with Remote Train Control.  If not, see <http://www.gnu.org/licenses/>.
GNU FDL

This is part of the Remote Train Control Manual.
© Copyright 2025 by Mark DiVecchio

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts and no Back-Cover Texts. You should have received a copy of the GNU Free Documentation License along with Remote Train Control. If not, see <http://www.gnu.org/licenses/>.
This site prepared and maintained by Mark DiVecchio

email :  markd@silogic.com

SD&A HOME
 
 Mark's Home Page

The DiVecchio genealogy home page
The Frazzini genealogy home page

This site will be under construction for a while.