Rumlogng clublog setup3/21/2023 ![]() I did a couple of simple tests thereafter: 1) quit GT: the clublog.adi file remained in the GT folder but the lotw.adi file was gone 2) restart GT: the clublog.adi file was updated (new timestamp) and a new lotw.adi file was generated. And suddenly, all the grids were properly colored again. After a minute or so, a new lotw.adi file also showed up. After starting GT, though, the ClubLog.adi file appeared almost immediately. ![]() Before startup, only the GridTracker_QSO.adi file appears. You can actually watch the results in real time if you have the GridTracker folder that holds the. Assuming that LOTW is the only source that can provide QSL verification (and hence, give me a properly colored grid), I cleared those files (using the “clear log” button in the QSO status window) and restarted GT. adi file for each logging program to which it’s connected. However, the GT Wiki indicates that when GT starts, it will create a temporary. adi files from LOTW, ClubLog, or GT 2) testing on an older version of GT 3) systematically turning off logging programs one at a time and then turning them back on. Initial attempts at a fix that did not solve the issue: 1) reloading all. Setup: Icom-7610, MacOS 10.15.7 running GT, WSJT-X, JTBridge, and RUMlogNG. My apologies in advance if this is a Captain Obvious type of solution: I think I found the fix and thought I’d post the results in case anyone else runs across this issue. All connections in the Settings/Logging window gave a “passed” result when tested. Recently (1/27/22) I posted about an issue in which the set QSL color (green) had disappeared after working perfectly for a couple of weeks and reverted to the QSO color (yellow), with no apparent intervention on my part.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |