Kesseltronics rTC: configuration and diagnostics
Find controller status, device traffic, incident reports and backup tools at sites with an rTC.
Where this applies
Applies to rTC / Laguna & Kesseltronics controllers, using rTC-Installers-Manual-20230727. Confirm the installed model in NXT Wash Admin and match its interface version before applying a setting.
Open the controller's recorded site address in Chrome or Chromium and sign in with your assigned account. The manual's example network addresses are not the address plan for a converted White Water site. The updated network map lists rTC at 192.168.100.91 on the site-device LAN. Confirm the actual site assignment; the separate TCS tunnel LAN applies to TunnelWatch / TCS2.
Start with controller status
The homepage shows current alerts, active overrides and daily wash counters. Some alerts link to support documents (manual page 17). Under System Setup → Version Information, record the rTC software version and the versions of connected hardware such as I/O nodes or PBS units (page 26).
Find the right diagnostic view
The manual groups the following views under Spy:
| View | What it tells you | Manual page |
|---|---|---|
| History | Time-stamped events, alerts and configuration changes. Red means error, green error cleared, yellow warning and black information. | 107 |
| Vehicle History | Measurements recorded for a selected vehicle; find it by day and hour after it leaves the wash. | 107–108 |
| Inputs and Outputs | A snapshot of controller I/O. A green indicator means that input or output is currently on. | 108 |
| Sensor Measurements | Current readings from analog sensors. | 109 |
| Configuration Report | A printable summary of controller settings. | 109 |
| Tunnel Monitor | Vehicles waiting or being washed, plus conveyor speed in pulses per hour. | 110 |
| Logs | Recent messages exchanged with external devices. Log capacity is limited. | 114–115 |
| Remote Devices Talking to the r-TC | Traffic volume from external devices, useful when one device may be sending excessive messages. | 115 |
Access Interface Tellers is a separate diagnostic view for devices using the PDQ Access interface and appears only when that interface is enabled. Its Active Tellers list records successful communication since the last controller reboot (page 114). Treat it as historical evidence over that period, rather than assuming every listed device is connected right now.
The XML log covers several device types. The manual notes that most PBS 5000 messages are omitted to conserve log space, so that log is not a complete list of every message on the controller.
Preserve an incident report
Under Tools → Downloads, choose Incident Report and identify the date and time of the problem. The controller collects files such as History, Configuration and Black Box data into a ZIP for support analysis (page 98).
The same area provides individual History and Black Box files. Black Box data records controller activity including inputs and outputs, and older records are eventually overwritten. Collect the relevant period promptly. A Core Dump File may help investigate a software crash (page 99). Keep diagnostic packages with the support case, not in the shared documentation site.
Configuration areas to recognize
System Setup controls installed interfaces and devices. Some changes automatically reboot the rTC after a notification (page 22). Gate/Pulse includes pulse length, the conveyor distance represented by one pulse, and minimum car length used for detecting an entering car (page 28). Those values belong to the installed conveyor and sensing setup; do not copy them from another site's configuration.
The manual also separates physical Inputs and Outputs from Input Assignment (pages 40–46), and the Basic Package, Wash Packages and Options setup (pages 68–71). Use those sections when reconciling the site's equipment and package configuration with the installer. They do not establish an NXT Wash interface mapping by themselves.
Back up before a configuration change
Tools → Backup / Restore provides a Backup button and an optional notes field. The documented controller stores up to 25 backups and makes an end-of-day backup when it detects changes (page 102). Tools → Downloads → Configuration File saves a copy to the technician's computer (page 98).
A restore replaces the current configuration and automatically reboots the controller. Replacing the configuration through Uploads also reboots it and loses tracking of vehicles being washed (pages 100 and 102). Schedule either operation while the wash is out of use, with the current configuration saved first.