G4BKI not1mm tips page

Visit full install page on github for information.
Latest information, support and questions can be found on the not1mm github Dicussions page.

I install and update by doing the following:

Finding non-UTF8 characters: grep -axv '.*' file.txt

Don't you ..........
While there has been a significant improvement with Logger32 CW generation, there are several things the Windows user can do to help eliminate 'choppy CW generation'.

The first thing is to go into Windows audio configuration and TURN OFF Windows sound generation. There is a good technical reason for this if you are using the PC's serial port for keying the transmitter.

The second thing is to slightly reconfigure the COM ports. Go into Windows Device Manager [if using Win 10, select Control Panel/All Control Panel Items/Systems/Device Manager], select Ports(COM & LPT), then at each Com port, select Properties/Port Settings/Advanced.

Then find Rcvr (bytes) and set it to 64; then select Tx (bytes) and also set it to 64. Change 'Latency Timer' to 1ms [NOTE! This depends on the specific RS-232 COM type device, some have it and some don’t]. This will improve the speed of your USB/Serial devices and help eliminate CW stutter.

Tread carefully. Before each update back up to a USB stick or external SSD.
You increase your chances of problems by running interfaces 'to the max'. Don't talk with your rig at 115200 baud rate, drop it to something sensible like 38400. Remember that you must change your rig to match and that some [TS-590S(G)] must be fully powered off before the change is actually made.
IC-7610 owners [I am one] use Logger32. Check for and install the latest Icom drivers before connecting the radio to the computer. Select the correct COM port. Open Device Manager expand Ports, with the radio power supply turned off, note the COM ports. Turn on the radio power supply. The additional virtual COM ports are associated with the radio. There are two that will show up. The first should be the radio control. Set the radio menu baud rate to the fixed rate that you want to use. Auto selection can make mistakes when searching. Use 19200 with the CI-V interface and a sensible rate for the USB interface. Use 'Icom' as the type (not any other specific IC-7nnn).The IC-7610 rig ID is 98. In the IC-7610 go to MENU/SET/Connectors/CI-V/C-IV USB Echo Back and set it to ON. When changing rigs, make sure Radio1 is ON in the Radio menu of Logger32.
Many answers to 'help' questions come from Gary, ZL2IFB; Jim, W5IFP and Aki, JA1NLX and not the main author Bob, K4CY [he does appear occasionally].
Prevent
For v3, download the latest .chm help file, saving it into C:\Logger32. Open Windows Explorer, navigate to C:\Logger32. Left Click once on Logger32.chm, right click and go to Properties. Then Unblock it as shown:

Many errors are caused by a corrupted .INI file. Exit the program. Rename the Logger32.INI file in the C:\Logger32 directory. Install the latest program update. Start the program. If this eliminates the error it was probably the .INI file. You may need to do some window location redefining, etc. Make sure that rig firmware is up to date. Watch out for Icom rigs, such as the IC-7300 (BTW: rig ID 94), which auto speed detect and can get it wrong.
Some users report a stubborn (re-)appearance of a Logger32.chi file which is an old-style Help index file. This breaks the indexing in the newer CHM Help files. Simply remove this file if you see it in the Logger32 directory. You could start Logger32 with a script which removes this file before starting Logger32 itself. Do not remove the Logger32.chw file.

After ......

You'll have to go through TWO cycles of this. Start Logger32, go through the above. Old version starts. New version is offered again. Go through the above process again and it finally installs! It's deeply flawed and yet it remains unfixed. I won't run Logger32 all the time with Full Admin privileges!

W4/VP9KF - CW keying hints

CW keying hints
How to make your logging program work with CW.

The K1EL WinKeyer needs to have the correct FTDI USB driver loaded on the PC. Use Device Manager to confirm it is there and to see what COM port it is on. It may have changed.
If the keyer 'disappears', go into Device Manager, right click on the USB port and deselect "allow USB to sleep when inactive".
Download the WKxMGR software from K1EL and confirm you can talk to the WinKeyer. It is useful to configure the WinKeyer, update the firmware and for trouble shooting. Note there are different versions depending on the WinKeyer you have.

Early WK2USBs had a problem of getting locked up if they had internal batteries installed and the PC's USB port went to sleep. To unlock the WK2USB you need to disconnect the WinKeyer's internal batteries. There is a firmware update that fixes this problem. If you are operating while connected to a PC, leave the batteries out anyway. Memories will be retained.

Please remember that the Logger32 code is written by ONE person and supported (website) by a group of volunteers. It's tough because of the vast number of transceivers, support devices, modes and versions of PCs and Windows that are supported. Some troubleshooting is recurring and is not easy to find in the ex-Yahoo Group 'archives' [lets out a groan]. Hence these notes. Some problems are difficult to reproduce without many hours of exploratory time.