Ten years ago, RTC started controlling trains over a phone cord plugged into the Remote jack of the original TIU. Later, it moved to a 900 Mhz radio on a small board connected to the PC via a USB connection. Now it has moved to a WiFi connection that does not require any external hardware or cables.
Once you get the WTIU or WIU/TIU connected up on your WiFi network or you let your WTIU create a network on its own, RTC will find all of your TIU and create WiFi connections to them. Pressing the [Read] button on the main screen will locate all of the engines on all of the TIUs.
Let me tell you a little about how the RTC program (and the App for that matter) finds the TIUs. There is a special Ethernet protocol called mDNS. This protocol lets devices like computers, printers and WTIUs locate other devices on the router. The program transmits an mDNS request over the WiFi asking all of the WTIU to respond. RTC (and the App) waits for responses. Once all of the WTIU respond, the program asks each one to report on which TIU number is it and on how many AIU are connected.
But there is a catch. The mDNS communications over Ethernet (WiFi or wired) is not what is called a "reliable" connection. This means that not all WTIU are guaranteed to respond. Maybe they will or maybe they won't. Maybe they won't even get the original request.
RTC gets around this by requiring you to specify the active TIU on your layout. RTC then checks the responses to the mDNS request to make sure that all of the TIU have responded. If they haven't, RTC warns you about it and lets you send the mDNS request again.
More to follow...