KOHLER: CASPIAN RDC MONITOR BETA1 RELEASED
Posted: Mon Sep 07, 2026 2:31 pm
CASPIAN FOR KOHLER
BETA 1 Release is ready for public testing:
This release is actually closer to a Version 1.0 release as we worked through many items to make sure this covered as many Kohler RDC configurations as we have the abilty to do so without an RDC connected to a generator with liquid cooling and an oil pressure transducer. We think this monitor will work with all Kohler genrators that use the latest RDC.
We need testers who have 20KW and below, 20KW and above that have liquid cooled generators and generators that have oil pressure transducers.
CASPIAN RDC MONITOR v6.0 BETA 1 — Build 6.42.0 this is a precursor to a full OnCue Server Emulator that will be developed as we move forward. The final product will eliminate the need for the RDC to connect to Kohler Cloud.
STATUS
This is the first public/tester Beta release candidate built from the flight-tested pre-Beta baseline.
No protocol, decoder, reconnect, telemetry, capability, or logging behavior was intentionally changed for Beta 1 packaging.
PURPOSE
Caspian RDC Monitor is a passive Ethernet monitor for Kohler RDC-family controller traffic to/from the Kohler remote server on TCP port 5253.
It normally observes mirrored/captured traffic rather than polling the RDC directly.
SUPPORTED PLATFORM FOR BETA 1
- Windows 10 and Windows 11
- .NET 8 Windows Forms (net8.0-windows)
- Npcap-compatible packet capture adapter
- Windows 7 support is deferred unless demand warrants a separate compatibility version
IMPORTANT NETWORK RULE
The RDC IP address is used only to select/filter the RDC network endpoint being captured.
Generator model, capability, N/A decisions, and telemetry interpretation are not determined from the RDC IP address.
KEY BETA 1 FEATURES
- Passive RDC/Kohler TCP capture on port 5253
- Automatic startup TCP reconnect for fresh full-state acquisition
- Manual TCP Reconnect button
- Remote IP display with visible change indication
- Compact change-oriented telemetry logging
- Optional Full Traffic Log / AllTraffic diagnostic logging
- EVENT VIEWR LOG matching the live Event Log
- CSV, XLSX, and ODS log export
- Saved/validated RDC IP, TCP port, and capture adapter
- Cold runtime reset when capture target changes
- Confirmed Kohler parameter mappings retained
- Distinction between No Reading and N/A retained
FILES TO READ (in the Docs folder)
- TESTER_INSTRUCTIONS.txt
- KNOWN_LIMITATIONS.txt
- CHANGELOG.txt
- CONFIRMED_KOHLER_PARAMETER_MAPPING_REFERENCE.md
CASPIAN RDC MONITOR v6.0 BETA 1 — KNOWN LIMITATIONS
Build 6.42.0
NEEDED, An Ethernet HUB that allows all traffic to every device on your LAN or a MANAGED SWITCH CAPABLE OF PORT MIRRORING: Recommended managed switch is:
Zyxel 8 Port Network Ethernet Switch | Web-Managed | GS1200-10V3 $29.00 ON AMAZON https://www.amazon.com/dp/B0G4RQ4RZD?re ... le_10&th=1
- Beta 1 targets Windows 10/11. Windows 7 compatibility is not included in this release.
- Passive monitoring requires the monitor PC to actually see the RDC/Kohler Ethernet traffic, normally through switch port mirroring or another valid capture method.
- Small-display/low-resolution UI optimization is not part of Beta 1. Use the accepted larger-monitor layout for this release.
- Some generator/controller families have not yet been validated with live captures.
- 38RCLC oil-pressure and coolant-temperature field identities are known, but final live numeric scaling/capability validation still requires captures from an operating sensor-equipped unit.
- Bench 38RCLC testing without the engine ECM/sensors may correctly show No Reading for ECM-supplied measurements.
- Full Traffic Log can produce substantially larger log files and should normally be enabled only for first-run validation or troubleshooting.
- Remote Server IP is transport/session information only and is not used to infer generator model or capability.
CASPIAN RDC MONITOR v6.0 BETA 1 — TESTER INSTRUCTIONS
Build 6.42.0
1. FIRST RUN
- Select the correct RDC IP address.
- Confirm TCP port 5253 unless your test environment intentionally uses a different port.
- Select the Npcap adapter receiving the mirrored/captured RDC traffic.
- For the first test on a generator/controller, enable Full Traffic Log.
- Click Start Passive.
2. WHAT TO EXPECT
- The monitor learns the live RDC/Kohler TCP session.
- One automatic startup reconnect is performed after enough session information is known.
- The button should show RECONNECTING ... during a monitor-initiated reconnect.
- A successful monitor-initiated reconnect flashes the green TCP Re-established state.
- Remote IP displays the observed Kohler-side server address.
- If the actual Remote IP changes, the field briefly changes background and uses bold text.
3. NORMAL LOGGING
For routine monitoring, Full Traffic Log may be left OFF.
Normal logging creates:
- Compact-YYYYMMDD-HHMMSS.csv/.xlsx/.ods
- EVENT VIEWR LOG-YYYYMMDD-HHMMSS.csv/.xlsx/.ods
4. FULL TRAFFIC LOGGING
Enable Full Traffic Log temporarily when:
- a displayed value is wrong, frozen, impossible, or missing;
- a supported field unexpectedly shows No Reading, N/A, or zero;
- monitor data disagrees with the generator/controller/Kohler app;
- updates appear unusually slow;
- reconnect behavior is abnormal;
- LAN/Internet loss or recovery behaves unexpectedly;
- Remote IP changes repeatedly or unexpectedly;
- Parser Status or Decoder Notes show warnings;
- testing a generator/controller model not previously validated;
- reproducing a problem for analysis.
With Full Traffic Log ON, the monitor additionally creates:
- AllTraffic-YYYYMMDD-HHMMSS.csv/.xlsx/.ods
5. WHEN REPORTING A PROBLEM
Please provide, when available:
- the Compact log set;
- the EVENT VIEWR LOG set;
- the AllTraffic log set if Full Traffic Log was enabled;
- a simultaneous Wireshark capture for protocol/decoder problems;
- generator model/controller type;
- whether the engine was stopped, running, exercising, or under load;
- what value/behavior you expected versus what the monitor displayed.
6. IMPORTANT DISPLAY MEANINGS
- N/A = the measurement is not applicable to the generator hardware as determined from protocol/capability evidence.
- No Reading = the measurement is expected/supported but no valid value has yet been obtained.
BETA 1 Release is ready for public testing:
This release is actually closer to a Version 1.0 release as we worked through many items to make sure this covered as many Kohler RDC configurations as we have the abilty to do so without an RDC connected to a generator with liquid cooling and an oil pressure transducer. We think this monitor will work with all Kohler genrators that use the latest RDC.
We need testers who have 20KW and below, 20KW and above that have liquid cooled generators and generators that have oil pressure transducers.
CASPIAN RDC MONITOR v6.0 BETA 1 — Build 6.42.0 this is a precursor to a full OnCue Server Emulator that will be developed as we move forward. The final product will eliminate the need for the RDC to connect to Kohler Cloud.
STATUS
This is the first public/tester Beta release candidate built from the flight-tested pre-Beta baseline.
No protocol, decoder, reconnect, telemetry, capability, or logging behavior was intentionally changed for Beta 1 packaging.
PURPOSE
Caspian RDC Monitor is a passive Ethernet monitor for Kohler RDC-family controller traffic to/from the Kohler remote server on TCP port 5253.
It normally observes mirrored/captured traffic rather than polling the RDC directly.
SUPPORTED PLATFORM FOR BETA 1
- Windows 10 and Windows 11
- .NET 8 Windows Forms (net8.0-windows)
- Npcap-compatible packet capture adapter
- Windows 7 support is deferred unless demand warrants a separate compatibility version
IMPORTANT NETWORK RULE
The RDC IP address is used only to select/filter the RDC network endpoint being captured.
Generator model, capability, N/A decisions, and telemetry interpretation are not determined from the RDC IP address.
KEY BETA 1 FEATURES
- Passive RDC/Kohler TCP capture on port 5253
- Automatic startup TCP reconnect for fresh full-state acquisition
- Manual TCP Reconnect button
- Remote IP display with visible change indication
- Compact change-oriented telemetry logging
- Optional Full Traffic Log / AllTraffic diagnostic logging
- EVENT VIEWR LOG matching the live Event Log
- CSV, XLSX, and ODS log export
- Saved/validated RDC IP, TCP port, and capture adapter
- Cold runtime reset when capture target changes
- Confirmed Kohler parameter mappings retained
- Distinction between No Reading and N/A retained
FILES TO READ (in the Docs folder)
- TESTER_INSTRUCTIONS.txt
- KNOWN_LIMITATIONS.txt
- CHANGELOG.txt
- CONFIRMED_KOHLER_PARAMETER_MAPPING_REFERENCE.md
CASPIAN RDC MONITOR v6.0 BETA 1 — KNOWN LIMITATIONS
Build 6.42.0
NEEDED, An Ethernet HUB that allows all traffic to every device on your LAN or a MANAGED SWITCH CAPABLE OF PORT MIRRORING: Recommended managed switch is:
Zyxel 8 Port Network Ethernet Switch | Web-Managed | GS1200-10V3 $29.00 ON AMAZON https://www.amazon.com/dp/B0G4RQ4RZD?re ... le_10&th=1
- Beta 1 targets Windows 10/11. Windows 7 compatibility is not included in this release.
- Passive monitoring requires the monitor PC to actually see the RDC/Kohler Ethernet traffic, normally through switch port mirroring or another valid capture method.
- Small-display/low-resolution UI optimization is not part of Beta 1. Use the accepted larger-monitor layout for this release.
- Some generator/controller families have not yet been validated with live captures.
- 38RCLC oil-pressure and coolant-temperature field identities are known, but final live numeric scaling/capability validation still requires captures from an operating sensor-equipped unit.
- Bench 38RCLC testing without the engine ECM/sensors may correctly show No Reading for ECM-supplied measurements.
- Full Traffic Log can produce substantially larger log files and should normally be enabled only for first-run validation or troubleshooting.
- Remote Server IP is transport/session information only and is not used to infer generator model or capability.
CASPIAN RDC MONITOR v6.0 BETA 1 — TESTER INSTRUCTIONS
Build 6.42.0
1. FIRST RUN
- Select the correct RDC IP address.
- Confirm TCP port 5253 unless your test environment intentionally uses a different port.
- Select the Npcap adapter receiving the mirrored/captured RDC traffic.
- For the first test on a generator/controller, enable Full Traffic Log.
- Click Start Passive.
2. WHAT TO EXPECT
- The monitor learns the live RDC/Kohler TCP session.
- One automatic startup reconnect is performed after enough session information is known.
- The button should show RECONNECTING ... during a monitor-initiated reconnect.
- A successful monitor-initiated reconnect flashes the green TCP Re-established state.
- Remote IP displays the observed Kohler-side server address.
- If the actual Remote IP changes, the field briefly changes background and uses bold text.
3. NORMAL LOGGING
For routine monitoring, Full Traffic Log may be left OFF.
Normal logging creates:
- Compact-YYYYMMDD-HHMMSS.csv/.xlsx/.ods
- EVENT VIEWR LOG-YYYYMMDD-HHMMSS.csv/.xlsx/.ods
4. FULL TRAFFIC LOGGING
Enable Full Traffic Log temporarily when:
- a displayed value is wrong, frozen, impossible, or missing;
- a supported field unexpectedly shows No Reading, N/A, or zero;
- monitor data disagrees with the generator/controller/Kohler app;
- updates appear unusually slow;
- reconnect behavior is abnormal;
- LAN/Internet loss or recovery behaves unexpectedly;
- Remote IP changes repeatedly or unexpectedly;
- Parser Status or Decoder Notes show warnings;
- testing a generator/controller model not previously validated;
- reproducing a problem for analysis.
With Full Traffic Log ON, the monitor additionally creates:
- AllTraffic-YYYYMMDD-HHMMSS.csv/.xlsx/.ods
5. WHEN REPORTING A PROBLEM
Please provide, when available:
- the Compact log set;
- the EVENT VIEWR LOG set;
- the AllTraffic log set if Full Traffic Log was enabled;
- a simultaneous Wireshark capture for protocol/decoder problems;
- generator model/controller type;
- whether the engine was stopped, running, exercising, or under load;
- what value/behavior you expected versus what the monitor displayed.
6. IMPORTANT DISPLAY MEANINGS
- N/A = the measurement is not applicable to the generator hardware as determined from protocol/capability evidence.
- No Reading = the measurement is expected/supported but no valid value has yet been obtained.