Yesterday, 05:19 AM
Hi Eelco,
First of all, thank you for your donation to support the BktTimeSync project.
Let's take a look at the issues you've been having:
- Unfortunately, in the Windows environment, there are too many different drivers, especially for COM ports emulated via USB. For maximum compatibility, I had to make a compromise in how the COM port is handled, which meant giving up some features. Losing the connection should automatically unblock the program, but with a long timeout (up to 15 minutes).
- The Bluetooth issue was most likely caused by a frozen Bluetooth stack on the PC itself.
- If you've checked the "auto-grid" option, the WWL locator is automatically sent to WSJT-X every time the time is checked (Sync every)
First of all, thank you for your donation to support the BktTimeSync project.
Let's take a look at the issues you've been having:
- Unfortunately, in the Windows environment, there are too many different drivers, especially for COM ports emulated via USB. For maximum compatibility, I had to make a compromise in how the COM port is handled, which meant giving up some features. Losing the connection should automatically unblock the program, but with a long timeout (up to 15 minutes).
- The Bluetooth issue was most likely caused by a frozen Bluetooth stack on the PC itself.
- If you've checked the "auto-grid" option, the WWL locator is automatically sent to WSJT-X every time the time is checked (Sync every)
73 de Mauro, IZ2BKT