First, thank you for connecting LOGic to WSJT's log. Great time saver.

I do have a question. Has anyone had problems with missing callbook info when LOGic is reading QSO data from WSJT? I've noticed that LOGic finds the info in one of the enabled callbooks but the data does not get passed to LOGic's log every time. It works about 50% of the time. It seem LOGic quits watching the callbook lookup too soon. Is there a way to throttle that function like I can a callbook batch update? I do use JTAlert along with WSJT. Don't think this would be a factor but don't know that for sure.This is not a big problem because I just do a callbook batch update at the end of the day. But being lazy, I'd like to have LOGic do it for me on the fly.

I have LOGic's internal callbook enabled as well as QRZ and FCC. I am a subscriber to QRZ which I understand gives me XML access to the database. It seems to happen when the callsign is found in QRZ. QRZ is second on the list right after LOGic's and QRZ is before FCC. Those three are the only one's I have enabled. My internet service typically runs at 20 Mbs download or faster.

That's good that you are subscribed to QRZ.COM. If you are not using the subscription, LOGic will pop the callbook window on top to preserve QRZ's advertising revenue. That could be be the cause of the problem you are seeing.

Make sure that LOGic is set up to use your QRZ subscription. Merely paying them will not cause LOGic to automatically use XML. You have to set it up accordingly. In LOGic's callbook setup, make sure you are using QRZ SUBSCRIPTION. Disable QRZ.COM. Do not use that.

You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.