I started using SimpleCom in order to connect to my serial devices, and I've gotta say that it's really cool to be able to use it inside Windows Terminal.
The only problem I found is that it's using a lot of my CPU and I've no idea if it's a widespread issue.

RT

Once connected, the title of the console window shows the slashes:

I think the cause is the MS UI Gothic font is a Japanese only font, and not unicode. Setting the font to something like MS Shell Dlg might work better?

Or is yen sign separators normal for separating paths in Japan?

Thx for your great software.

The instructions in the readme were "Press F1 to leave its serial session and to finish SimpleCom". When F1 is pressed, a dialog is displayed prompting to leave the serial session. If "Yes" is selected, the program does not close and F1 no longer does anything.

The com port is not fully closed because characters can still be received, they just don't seem to be able to be sent.

@ngbrown has suggested me in #2 that we should call SetCommTimeouts() to avoid high CPU usage. I think we need to set 0 to ReadIntervalTimeout, but I cannot evaluate it because I cannot reproduce the problem (high CPU usage) on my environment (Windows 10 + USB serial converter + Raspberry Pi 4 (Raspberry Pi OS AAArch64)). So I need the help.

First of all, thank you for your work so that I can connect to the serial port in the Windows terminal!
But when using the serial port, I often need to use the arrow keys in vim or use it to find the first few commands, I hope you can fix this problem to make it better. thanks again.

As @ngbrown pointed in #2, I've elided some error handlings, but it should be handled.
We need to add it for the following at least:

• SimpleCom/SimpleCom/WinAPIException.cpp

  Line 27 in e28874d

  FormatMessage(FORMAT_MESSAGE_ALLOCATE_BUFFER | FORMAT_MESSAGE_FROM_SYSTEM | FORMAT_MESSAGE_IGNORE_INSERTS, NULL, _error_code, 0, reinterpret_cast<LPTSTR>(&_error_text), 0, NULL);

  • Add default error message if FormatMessage() failed.

• SimpleCom/SimpleCom/SimpleCom.cpp

  Line 54 in e28874d

  ReadConsole(hStdIn, console_data, 4, &data_len, nullptr);

• SimpleCom/SimpleCom/SimpleCom.cpp

  Line 71 in e28874d

  ResetEvent(overlapped.hEvent);

• SimpleCom/SimpleCom/SimpleCom.cpp

  Line 96 in e28874d

  ResetEvent(serialReadOverlapped.hEvent);

• SimpleCom/SimpleCom/SimpleCom.cpp

  Line 175 in e28874d

  SetCommState(hSerial, &dcb);

• SimpleCom/SimpleCom/SimpleCom.cpp

  Line 176 in e28874d

  PurgeComm(hSerial, PURGE_TXABORT | PURGE_RXABORT | PURGE_TXCLEAR | PURGE_RXCLEAR);

• SimpleCom/SimpleCom/SimpleCom.cpp

  Line 177 in e28874d

  SetCommMask(hSerial, EV_RXCHAR);

• SimpleCom/SimpleCom/SimpleCom.cpp

  Line 178 in e28874d

  SetupComm(hSerial, 1, 1);

• SimpleCom/SimpleCom/SimpleCom.cpp

  Line 191 in e28874d

  GetConsoleMode(hStdIn, &mode);

• SimpleCom/SimpleCom/SimpleCom.cpp

  Line 195 in e28874d

  SetConsoleMode(hStdIn, mode);

• SimpleCom/SimpleCom/SimpleCom.cpp

  Line 198 in e28874d

  GetConsoleMode(hStdOut, &mode);

• SimpleCom/SimpleCom/SimpleCom.cpp

  Line 200 in e28874d

  SetConsoleMode(hStdOut, mode);

  • Throws WinAPIException if they failed.

It was reported in #19

I try build by myself with vs 2022, but its failure, here is error:

Severity	Code	Description	Project	File	Line	Suppression State
Error	C2039	'contains': is not a member of 'std::map<TString,TString,std::less<TString>,std::allocator<std::pair<const TString,TString>>>'	SimpleCom	~\SimpleCom\SimpleCom\SerialDeviceScanner.cpp	105	

It would be good to accept some command line parameters and connect straight away. Accept COM port number and baud rate directly at command line, and don't display dialog when parameters are passed.

Since most COM ports are now provided by USB devices, it may also be good to accept the USB Device ID in place of the COM port number. Something in the format of FTDIBUS\VID_0403+PID_6001+AH063JZ9A\0000. Provide another command option that lists all the COM ports and their associated USB Device ID.

Hello,
I use SimpleCom from Microsoft Terminal, but after the last update it doesn't work properly, because the arrows don't work.
Strangely, if I launch it directly, the arrows work fine.
Is it just me or did this occur to someone else?

Buffer size of StdInRedirector is 4, 1 is for StdOutRedirector. They are small because I assume SimpleCom is used for the console - it is enough to redirect typing by the hand. (I think the human cannot type so fast 😁)

However we might get the gain when the peripheral send many chars (e.g. log dumping) if we expand buffer size for StdOutRedirector. It is worth to work. OTOH we should consider it for StdInRedirector because we need to handle F1 key to terminate SimpleCom. We have to catch F1 (0x1b + 0x4f + 0x50), and also have to handle multibyte chars (e.g. Japanese Kanji). We might use ReadConsoleInput(), but I'm not sure.

First of all, thank you for this tool. I've been using it a lot since I have discovered it with my dev machines.

Occasionally I forget the command line arguments, that the tool accepts, and find myself typing in --help as argument, often used to get all supported arguments of a tool or program.

I think SimpleCom would benefit from the implementation of a --help argument, as one doesn't have to look it up on the web each time this way.

What do you think of this idea?
Thank you for your time.