Serial Auto-Detect

Last updated: April 2026

When connecting to an unfamiliar serial device, you may not know the correct baud rate, data bits, parity, or flow control settings. Manually trying every combination is tedious and error-prone. RockTerm's Auto-Detect feature solves this by probing the port with common setting combinations and analyzing the response to find the correct configuration automatically.

How It Works

Auto-Detect opens the serial port with each candidate configuration, sends a carriage return to prompt the device to respond, and reads whatever comes back. A scoring algorithm evaluates the response based on:

• Printable character ratio — Correct settings produce readable ASCII text. Wrong settings produce random bytes and control characters.
• Keyword recognition — The engine looks for common terminal keywords: login, password, router, switch, cisco, console, welcome, u-boot, and others.
• Prompt detection — Characters like >, #, $, and : are strong indicators of a working connection.
• Corruption markers — Streams of null bytes (0x00) or 0xFF are penalized heavily, as these are reliable signs of wrong baud rate or parity settings.

What Gets Tested

RockTerm tests approximately 60 setting combinations, ordered by probability so the most common configurations are tried first:

Priority	Configuration	Covers
Tier 1	All standard baud rates with 8N1, no flow control	Most modern devices, Cisco, Juniper, Linux consoles, embedded systems
Tier 2	All standard baud rates with 7E1	Legacy terminals, PLCs, industrial equipment
Tier 3	All standard baud rates with 7O1	Older industrial and point-of-sale systems
Tier 4	8N1 with RTS/CTS and XON/XOFF flow control	Devices requiring hardware or software flow control
Tier 5	Rare baud rates (230400, 460800, 921600, 300, 600) with 8N1	High-speed embedded devices, very old equipment
Tier 6–7	8E1, 8O1, and 2-stop-bit variants	Uncommon configurations

Standard baud rates tested: 9600, 115200, 19200, 38400, 57600, 4800, 2400, and 1200.

If a high-confidence match is found during Tier 1 testing, the remaining tiers are skipped. A full scan of all 60 combinations typically completes in under 30 seconds.

Using Auto-Detect

1. Open the serial connection dialog (File → Connect → Serial or press Alt+S).
2. Select the correct COM port from the dropdown. If you're not sure which port, unplug and replug the serial adapter and click Refresh to see which port appears.
3. Click the Auto-Detect button.
4. In the Auto-Detect dialog, click Start Detection.
5. RockTerm will begin probing. The progress bar shows which configuration is currently being tested, and the Best Match panel updates in real time as better matches are found.
6. When detection completes, review the results:
   • Green confidence score — High confidence. The settings are almost certainly correct.
   • Yellow confidence score — Moderate confidence. The settings are likely correct but you may want to verify.
   • Red confidence score — Low confidence. The device may not be responding, or the correct settings were not in the test set.
7. Click Use These Settings to apply the detected configuration to the connection dialog, then click Connect.

Tips for Best Results

• Power on the device first. Auto-Detect works by reading the device's response. A powered-off device produces no data to analyze.
• Devices that send unsolicited output (boot messages, login prompts, periodic status updates) are detected fastest and with highest confidence.
• Quiet devices that only respond to specific commands may take longer or produce lower confidence scores. Auto-Detect sends a carriage return to try to provoke a response, but some devices require a specific key sequence.
• Close other applications that might be using the serial port. Only one application can access a COM port at a time.
• Check your cable. A null modem cable, straight-through cable, or USB-to-serial adapter must match what the device expects. Auto-Detect cannot compensate for incorrect cabling.

When Auto-Detect Doesn't Find a Match

If Auto-Detect reports no data received or a very low confidence score:

• Verify the device is powered on and connected to the correct port.
• Try pressing Enter or the space bar on the device's physical console (if accessible) to generate output, then run Auto-Detect again.
• Check that you selected the right COM port — unplug the adapter, click Refresh, replug, and click Refresh again to identify the correct port by elimination.
• Some devices require specific baud rates outside the common set (e.g., 14400 or 28800). In those cases, consult the device documentation and configure the settings manually.
• If using a USB-to-serial adapter, ensure the driver is installed. Check Device Manager (Windows) or dmesg | grep tty (Linux) to confirm the adapter is recognized.

← Back to Support Articles

Still need help?

If you're still experiencing issues, contact us or email info@rockriverresearch.com.