开云体育

Hallo, I (just) recently experienced problem in dowloading (just few, 5/6) eQSL images. The following warning appears:?"from eQSL.cc: PROCESSOR OVERLOAD - THROTTLING INVOKED -->" I have the latest

Perhaps that spots submitted through a web interface are more likely to be illegitimate, since it's perceived to take less effort than setting up a cluster connection with a fake source callsign. 73,

Thanks Dave for your prompt reply. Will continue to switch between the loops of the quad manually… but it’s a pity because Acom HW it’s very good. 73. A.Ma.

Under Alerts, there is the Quick Enable / Disable on alerts, The Band Activity Display is checked, with a Green ON beside it. Not getting any SFI info with logging. I've had 4 heart attacks, the first

There have been no recent posts on the HamApps group regarding SFI data not being logged. There are no messages waiting moderator approval. I don't know where you posted your question, it definitely

Dave, I tried the JTAlert support group, they sent me here. Guess I'll keep filling it manually, I like to have that data with qso in log. 73's

+ AA6YQ comments below Although I understand what you are saying I struggle with the logic. If I enter a random Swedish call in DXView, I get the grid locator of central Stockholm which of course is

+ AA6YQ comments below Can you do a global exclusion for all -@ calls like you do for -#? + What's the rationale for ignoring spots from DX Summit? + Skimmers generate spots in high volume; that's why

* more AA6YQ comments below The question was about the '-@' suffix, not '-#', though. The former is appended by DX Summit, on spots submitted through their web interface, from what I understand. *

There are no grids in AD1C's CTY files and DXKeeper does not use them unless one chooses to import the Big CTY file to populate the override list. AA6YQ and/or I supplied a reference grid for each

Hi Dave, Can you do a global exclusion for all -@ calls like you do for -#? 73, George W2GS

The question was about the '-@' suffix, not '-#', though. The former is appended by DX Summit, on spots submitted through their web interface, from what I understand. 73, ~iain / N6ML

Joe, I'm not so well versed in the CTY terminology. With the "default grid" I mean the reference grid that pops up when you enter a random call in DXView. All DXCC entities seem to have at least one.

Although I understand what you are saying I struggle with the logic. If I enter a random Swedish call in DXView, I get the grid locator of central Stockholm which of course is very wrong for e.g. my

Thanks, Dave! That works!!!!!!!!!!!!!! 73 Glenn W0GJ

+ AA6YQ comments below Very appreciate to help me to connect Commander to Acom 2000S remote antenna switch via serial port. First question: it’s possible? + No. As described in

I use this to check DXCC Progess on 60 meters: QSO_Begin BETWEEN #2020-01-01 00:00# and #2020-12-31 23:59# AND BAND='60M' Tom NQ7R

+ AA6YQ comments below I am using Commander / DXKeeper / WSJT-X / JT Alert for FT-8 and all seems to work well, including automatic logging to LoTW and DXKeeper. However in DXK I notice that the name

+ AA6YQ comments below Hello all. I use WSJT-X 2.1.2 and JTAlert 2.15.10 for FT8. I have the box checked in JTAlert, Logging to fill the SFI, A, and K boxes in DXKeeper 15.4.3. When I first started

+ AA6QY comments below Anyway to use the "standard" Fkeys in Winwarbler, F1, CQ, F4 my call, etc, to be consistent with other logger programs? + No. In all modes, F2 is used to start transmission, and