IZ2BKT:
I'm using a U-blox7 USB GPS receiver with Windows XP\SP3. Your
BktTimeSync application finds the GPS receiver and receives updates but the application becomes non-responsive. Once it begins to receive updates I cannot close the application. I need to end the process tree in the Windows Task Manager in order to close the application. I tried to set to manual sync but once I click the sync now button the application becomes non-responsive. When the application is running its CPU usage is always 47-50%. I've included the diagnostics log below.
I'm wondering if you have any insight into why the application becomes non-responsive. As I said, it is working, however I'd like to be able to close the application without having to use the task manager to end the process tree.
Please let me know if you need additional information.
73,
Tim
KA9EAK
https://outbackofbeyond.wordpress.com/
Fri Jul 28 20:06:07 2017 --> Fri Jul 28 21:06:00 2017Sync GPS OK, next to :
Windows Versione: 5.01
BKTTimeSync Versione: 1.8.2
NTP Server: tick.usno.navy.mil
NTP Porta: 123
NTP Offset:
NTP ON: 0
Autostart: -1
Start in tray: -1
Sync all'avvio: 0
Sync ogni: 60 minuti
Sync massima: 12 ore
GPS Porta: 8
GPS Baud: 9600
GPS Bit: -1
GPS Bit di stop: 2
GPS Parità:
GPS RTS: -1
GPS DTR: -1
GPS Offset:
GPS Always Connected: 0
Sequence: 1
Fri Jul 28 20:02:03 2017 --> Sync start P1
Fri Jul 28 20:02:03 2017 --> Sync GPS COM open
Fri Jul 28 20:02:03 2017 --> GPS rx str P1
Fri Jul 28 20:02:03 2017 --> GPS rx str: $GPTXT,01,01,02,u-blox ag -
www.u-blox.com*50
Fri Jul 28 20:02:03 2017 --> GPS rx str P1
Fri Jul 28 20:02:03 2017 --> GPS rx str: $GPTXT,01,01,02,HW UBX-G70xx 00070000 *77
Fri Jul 28 20:02:03 2017 --> GPS rx str P1
Fri Jul 28 20:02:03 2017 --> GPS rx str: $GPTXT,01,01,02,ROM CORE 1.00 (59842) Jun 27 2012 17:43:52*59
Fri Jul 28 20:02:03 2017 --> GPS rx str P1
Fri Jul 28 20:02:03 2017 --> GPS rx str: $GPTXT,01,01,02,PROTVER 14.00*1E
Fri Jul 28 20:02:03 2017 --> GPS rx str P1
Fri Jul 28 20:02:03 2017 --> GPS rx str: $GPTXT,01,01,02,ANTSUPERV=AC SD PDoS SR*20
Fri Jul 28 20:02:03 2017 --> GPS rx str P1
Fri Jul 28 20:02:03 2017 --> GPS rx str: $GPTXT,01,01,02,ANTSTATUS=OK*3B
Fri Jul 28 20:02:03 2017 --> GPS rx str P1
Fri Jul 28 20:02:03 2017 --> GPS rx str: $GPTXT,01,01,02,LLC FFFFFFFF-FFFFFFFD-FFFFFFFF-FFFFFFFF-FFFFFFF9*53
Fri Jul 28 20:02:04 2017 --> GPS rx str P1
Fri Jul 28 20:02:04 2017 --> GPS rx str: $GPRMC,010708.00,A,4318.46619,N,08807.29533,W,0.083,,290717,,,A*66
Fri Jul 28 20:07:08 2017 --> Sync GPS offset greater than that required
Fri Jul 28 20:07:08 2017 --> GPS rx str P1
Fri Jul 28 20:07:08 2017 --> GPS rx str: $GPVTG,,T,,M,0.083,N,0.154,K,A*28
Fri Jul 28 20:07:08 2017 --> GPS rx str P1
Fri Jul 28 20:07:08 2017 --> GPS rx str: $GPGGA,010708.00,4318.46619,N,08807.29533,W,1,07,1.38,276.0,M,-34.1,M,,*6E
Fri Jul 28 20:07:08 2017 --> GPS rx str P1
Fri Jul 28 20:07:08 2017 --> GPS rx str: $GPGSA,A,3,15,20,21,13,18,29,05,,,,,,2.35,1.38,1.90*04
Fri Jul 28 20:07:08 2017 --> GPS rx str P1
Fri Jul 28 20:07:08 2017 --> GPS rx str: $GPGSV,4,1,13,05,18,073,20,10,12,264,17,13,48,059,24,15,75,126,30*74
Fri Jul 28 20:07:08 2017 --> GPS rx str P1
Fri Jul 28 20:07:08 2017 --> GPS rx str: $GPGSV,4,2,13,16,03,297,,18,41,273,28,20,63,057,17,21,62,305,33*77
Fri Jul 28 20:07:08 2017 --> GPS rx str P1
Fri Jul 28 20:07:08 2017 --> GPS rx str: $GPGSV,4,3,13,24,11,150,25,27,10,326,,29,30,194,18,30,04,032,*71
Fri Jul 28 20:07:08 2017 --> GPS rx str P1
Fri Jul 28 20:07:08 2017 --> GPS rx str: $GPGSV,4,4,13,51,36,207,*4F
Fri Jul 28 20:07:08 2017 --> GPS rx str P1
Fri Jul 28 20:07:08 2017 --> GPS rx str: $GPGLL,4318.46619,N,08807.29533,W,010708.00,A,A*7E
Fri Jul 28 20:07:08 2017 --> Sync start P1
Fri Jul 28 20:07:08 2017 --> GPS rx str P1
Fri Jul 28 20:07:08 2017 --> GPS rx str: $GPRMC,010709.00,A,4318.46634,N,08807.29528,W,0.178,,290717,,,A*67
Fri Jul 28 20:07:09 2017 --> Fri Jul 28 21:07:00 2017Sync GPS OK, next to :