Re: TX7T location not being found
toggle quoted messageShow quoted text
That fixed it, pal. Your assumption about the cause is probably correct. BTW, I managed to eek out a brief, 339, contact with JA1NUT the other evening, so the bands may be coming back. I’ll be keeping a ear out for ZM4T this weekend.
From: Gary Hinson
Sent: Monday, November 18, 2019 7:42 PM
Subject: Re: [hamlogger] TX7T location not being found
Same here … so I re-ran the Club Log prefix update …
… which fixed it …
Maybe Club Log had an early end date for them, which someone has kindly corrected.
From: firstname.lastname@example.org <email@example.com> On Behalf Of Ed Tobias
I noticed, this evening, that L32 no longer recognizes the location of TX7T. It had been identifying it correctly (as FO\M) until yesterday or today. So, I’m not sure whether this problem relates to today’s sync with Club Log or with the 3.50.401 L32 update, which I just installed today.