Serial Terminal on Windows: COM Ports, Baud Rates and HEX Debugging

Serial never went away. Network switches still have console ports, industrial controllers still talk RS-232/485, and every embedded board with a UART can be reached with three wires and a USB adapter. What has changed is that Windows hid the details — so the first twenty minutes of any serial job is usually spent guessing parameters.

The five parameters you must match

Serial has no negotiation. Both sides must be configured identically or you get nothing, or you get garbage.

Parameter	Common values	What a mismatch looks like
Baud rate	9600, 19200, 38400, 57600, 115200	Garbled characters, or a silent terminal
Data bits	8 (almost always), sometimes 7	Corrupted high bits; characters shifted by a bit
Parity	None, Even, Odd	Random wrong characters, or a parity-error indicator
Stop bits	1, sometimes 1.5 or 2	Framing errors, dropped or duplicated characters
Flow control	None, XON/XOFF, RTS/CTS	Output stops mid-stream, or bytes vanish at speed

The near-universal default for console ports is 9600 8N1, no flow control. Embedded boards and modern gear often use 115200 8N1. When in doubt, try those two before anything else.

Finding the right COM port

1. Plug in the adapter before opening your terminal — most clients only enumerate ports at startup.
2. Open Device Manager → Ports (COM & LPT) and look for a new entry such as USB Serial Port (COM4).
3. If it appears as an unknown device, install the adapter's driver first. The cheap clones that ship without one are the usual cause of a wasted afternoon.
4. If the port number is above COM9, some older software struggles; you can reassign it in Device Manager → Port Settings → Advanced.

Why a HEX monitor matters

When a device is not answering, a text terminal tells you nothing — there is simply no output. A HEX monitor shows you the raw bytes in both directions, which distinguishes three very different failures:

• Nothing at all — wiring, wrong port, or the device is not powered.
• Bytes arriving but unintelligible — wrong baud rate or encoding. Real traffic, wrong settings.
• Your bytes going out, nothing coming back — the device is not listening, or TX/RX are swapped.

FlyTerminal's HEX monitor shows live TX/RX with direction markers, so you can see which side is silent without reaching for a logic analyser. For binary protocols — Modbus, custom MCU frames, anything that is not printable ASCII — it is the only view that means anything. See also debugging serial protocols with a HEX monitor.

Fixing garbled output

1. Check baud rate first. It accounts for the large majority of "garbage" reports.
2. Check encoding. Non-English text and some device banners are not UTF-8; try Latin-1 or GBK.
3. Check flow control. At 115200 with no flow control, a fast-talking device will overrun you.
4. Check the cable. Null-modem vs straight-through, and TX/RX crossed the right way.
5. Check voltage levels. RS-232 is not TTL. A 3.3 V board needs a level shifter, not a nine-pin cable.

Log everything

Serial sessions are often the only record of what a device said before it failed. Turn on session logging with timestamps and direction markers, and let it rotate. It costs nothing and it is the first thing an auditor or a colleague will ask for.

FAQ

Why does my USB-to-serial adapter not appear?

Usually a missing driver, or the adapter was plugged in after the terminal started. Install the driver, then restart the terminal so it re-enumerates ports.

What is the default baud rate for Cisco console ports?

9600, with 8 data bits, no parity, 1 stop bit and no flow control. Many other vendors match this, but check the device documentation — some gear ships at 115200.

Can I use a serial port and SSH at the same time?

Yes, with a client that keeps each session independent. In FlyTerminal you can open a serial console and an SSH session as separate tabs and switch between them.

Is serial secure?

It is physically local, which is the point — but it is also unauthenticated. Treat console access as privileged and control who can physically reach the port.