Thanks for this great terminal software, especially the HEX view combined with the ability to enter custom baud rates is what it makes so valuable for me.
I have discovered one issue with line endings. I have a linux based system, which sends all kinds of line endings in the same data stream over the serial interface. The data is just a log file. Mostly a <CR><LF>, a single <LF> but also a single <CR> is sent as the line ending. Here, everything is working as expected.
Sometimes, the combination <CR><CR><LF> is sent. If such a character combination comes in, either with or without preceeding characters, the line ending is ignored at all and the cursor stays after the last visible character. The next caracter is just written after that on the same line. If I activate the Option "Ignore line feed character", this double-<CR> line endings are handled correctly, generating a empty line in ASCII view. This would be the expected behaviour, but the lines only containing a <LF> as line end wont show the correct behaviour.
Furtheron I have a modem (from ublox) which shows this combination as well. So probably not very uncommon.
I kindly ask you to have a look into the code what's going on here. I checked the options, the help file and the forum. Unfortunately, I have not found any solution for that. Probably this is a "feature"?
In the following example using a modem with echo on, the comination is received just before the modem response "+URAT: 7". I am using CoolTerm 1.8.0 Build 861 in line mode.
ASCII mode:
Code: Select all
at+urat?
at+urat?+URAT: 7
OK
Code: Select all
61 74 2B 75 72 61 74 3F 0D 0A 61 74 2B 75 72 61
74 3F 0D 0D 0A 2B 55 52 41 54 3A 20 37 0D 0A 0D
0A 4F 4B 0D 0A
Bernhard