开云体育

Also today, and I don't know if/why they would be related, my Outlook web app isn't playing nice: https://outlook.office.com/mail/ The error message is: UTC Date: 2024-11-25T20:14:44.578Z Client Id:

Hello Chris Much appreciate your taking the time out to respond to my request for help. So just to “sooth my aching” head is the “blue tooth library” thing you mention the reason for the error

We have a machine (let’s call 66) that is our main logger. ?We want to have a laptop on the same network that can lookup log entries and add C to the QSL Sent column and possible add some comments

Hi Ken, Thanks for your follow up.? Since all these programs were working previously and you've not made any changes to the software, you can be sure something external to the software is at play,

Hi Scott, I tried that with no success.? I also fired up the NAQP version and still no luck. What's my next step? 73, Ken

Hi Tom, Thanks for your interest in MeshSense! Unfortunately Linux devices with AMD CPUs are currently not compatible, but we hope to add support in the future. The technical reason is that the

Hi Ken, Thanks for your e-mail.? The rig interface code in all our software is identical.? Since rig interface is working in CQ WW, from CQ WW's rig interface form, click the Save Settings button

After using the CQ WW log this weekend (and loving it), I went back to ACLog this morning and the rig interface function has stopped working. Even after reloading a previously saved version that I

For some reason I had two rigs setup (don’t have two rigs) for something I was doing in the past. It appears to be working correctly after swapping rigs. Sorry for the bother! Appreciate your

Hello and thanks for reading my message… I am trying to load and run the Meshsense App on a 64 bit AMD processor machine running a fully updated versions of Linux and an OS of Ubuntu Jammy

Hi Randy, Thanks for your follow up.? I'm sorry that you are still having trouble.? Once configured properly, the frequency will update as you turn your VFO.? Make sure you use the Yaesu Newer 2

A bit of added info. When you hit a DX spot it will change the xcvr to that frequency. Also the large data screen at the bottom of the rig interface setup page is highly populated.

I pulled the cable that comes out of the yaesu ftdx101mp (com4) from the computer. I then put it back in and was able to get rig interface to accept the com port and it is now working on the rig

Hi Fred, Remember that the "Queue Time" is only reported once/hour.? If a big log came in just before you uploaded it will take longer to clear your upload. Larry / W1DYJ

Perhaps not to your specific question .... I often check LoTW's queue time after doing an upload.? Previously (months ago) the minimum queue delay would usually be just less than 60 seconds - unless

That fixed it! Well, first I had to check "Record RST", that took care of the problem, then I had to set the default RST. Those are the settings that changed when my computer rashed, thanks for the

Hi Mark, Thanks for your e-mail.? Nothing is immediately changed in your log on upload.? You have to do a subsequent download, after LoTW has processed your records.? More details are here: I

Hi Kerry, Thanks for your e-mail.? Click Settings > RST Settings and set to your preference.? Deselect the option to leap over the fields if you prefer. Enjoy! 73,

I will also note that we should be on the latest version of TQSL. Version 2.7.5 was just released. 73 -Jim NU0C "Dave (NK7Z) via groups.io" <dave@...> wrote:

Hi Mark, While I can't help you with what is wrong, I can let you know ACLog, and LoTW, deal with my log, (50K contacts), flawlessly.? Is your TQSL cert still valid? 73, and thanks, Dave