Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
Updating Logged QSOs to Reflect Status Downloaded from IOTA
|
I have tried to update my IOTA status several times using the .csv file downloaded from the IOTA website¡¯s MY IOTA/DOWNLOAD QSOS, using the Update button in DXKeeper¡¯s Check Progress/IOTA panel without success. The report shows ¡°Updates: 0¡± and don¡¯t contain any QSOs. Generated Progress reports show none of the new contacts contained in the .csv file are ¡°Verified.¡±
I¡¯m sure I must be doing something wrong, but can¡¯t figure out what it is. I followed the steps in the online instructions faithfully. I checked the .csv file to be sure it contained my recently submitted and approved IOTA QSOs (it did) and I noticed the approved QSOs were ¡°Accepted¡± rather than ¡°Verified,¡± but I don¡¯t know if that¡¯s relevant. What am I missing? I¡¯m pretty sure this worked for me last year¡ Thanks, Steve K4WA |
|
+ AA6YQ comments below
I have tried to update my IOTA status several times using the .csv file downloaded from the IOTA website¡¯s MY IOTA/DOWNLOAD QSOS, using the Update button in DXKeeper¡¯s Check Progress/IOTA panel without success. The report shows ¡°Updates: 0¡± and don¡¯t contain any QSOs. Generated Progress reports show none of the new contacts contained in the .csv file are ¡°Verified.¡±+ As I posted here late last month, IOTA again changed the format of the .csv file exported from IOTA.org: /g/DXLab/message/226441 + As stated in its release note, the current version of DXKeeper has been updated to support this new format: + At my suggestion, the IOTA team has setup an online group with which to communicate impending changes to application developers like me. There has been no notification of another change to the .csv file format. + What version of DXKeeper are you running, Steve? The version number is shown in the upper-left corner of DXKeeper's Main window. ? ? ?73, ? ? ? ? ? ? Dave, AA6YQ |
¿ªÔÆÌåÓýThanks Dave, I was on 17.9.7, but updated to the latest and that fixed it. ?I have nine ¡°not found in log(s)¡± I have to figure out, but five of those are my call from IOTAs I activated and received credit. ?Not sure how I should handle those, and hopefully the other four will be easy to resolve. ?Thanks (once again) for correcting my path. 73, Steve ?K4WA On Jan 21, 2025, at 11:07?PM, Dave AA6YQ <aa6yq@...> wrote:
|
|
+ AA6YQ comments below
Thanks Dave, I was on 17.9.7, but updated to the latest and that fixed it. I have nine ¡°not found in log(s)¡± I have to figure out, but five of those are my call from IOTAs I activated and received credit. Not sure how I should handle those, and hopefully the other four will be easy to resolve. + What action did you take that resulted in the "not found in log" reports? 73, Dave, AA6YQ |
|
The IOTA report came back with the ¡°not found in log¡± indications. Some were easy to adjust, like KL7/call in the report and call/KL7 in my log. Ditto with just the call versus call/6. VS6BG I can¡¯t explain; the call and data is the same in both the IOTA report and my log.
toggle quoted message
Show quoted text
The five IOTA activations I did that I got credit for show my call as the worked station, and of course, my call is not in the log. In order to qualify for credit, IOTA wanted me to send my IOTA card with the first QSO from the activation. I could show the first station I worked from each activation as being on the island; I¡¯m not sure what all the repercussions of that might be. Or, I could try to insert my call as if I worked myself from the island, but that would be weird. I wonder how others have addressed that? 73, Steve K4WA On Jan 22, 2025, at 12:35?PM, Dave AA6YQ <aa6yq@...> wrote: |
|
+ AA6YQ comments below
The IOTA report came back with the 'not found in log' indications. Some were easy to adjust, like KL7/call in the report and call/KL7 in my log. Ditto with just the call versus call/6. VS6BG I can't explain; the call and data is the same in both the IOTA report and my log. + The reported QSO time must be within 15 minutes before or after the logged QSO time. The five IOTA activations I did that I got credit for show my call as the worked station, and of course, my call is not in the log. In order to qualify for credit, IOTA wanted me to send my IOTA card with the first QSO from the activation. I could show the first station I worked from each activation as being on the island; I'm not sure what all the repercussions of that might be. Or, I could try to insert my call as if I worked myself from the island, but that would be weird. I wonder how others have addressed that? + If activating an IOTA island gives you IOTA credit for working and confirming that island, then I suggest that you log a QSO with yourself on the correct band and mode with the QSO time as specified in the .csv file you downloaded from IOTA. However, this would not qualify you for a DXCC confirmation with the island's DXCC entity; that's why DXpeditioners to rare DXCC entities must arrange for someone to work them from their home station. 73, Dave, AA6YQ |
+ If activating an IOTA island gives you IOTA credit for working and confirming that island, then I suggest that you log a QSO with yourself on the correct band and mode with the QSO time as specified in the .csv file you downloaded from IOTA.I only activated US islands in FL, AL, and GA this year, so the DXCC confirmation wouldn¡¯t be an issue in this case. So, I¡¯ll take your suggestion, and worry about the rare one when/if I activate it. that's why DXpeditioners to rare DXCC entities must arrange for someone to work them from their home station.Or they could use their satellite connection to work the rare island from their home station a few times while cooling their heels on the boat offshore, like several members of the last Bouvet operation supposedly did¡ ? Thanks for your help! |
|
# More AA6YQ comments below
snip< that's why DXpeditioners to rare DXCC entities must arrange for someone to work them from their home station.Or they could use their satellite connection to work the rare island from their home station a few times while cooling their heels on the boat offshore, like several members of the last Bouvet operation supposedly did ?? # As Dave K1ZZ quipped, "it's just a long microphone cord". 73, Dave, AA6YQ |
|
I successfully entered my call for the activations, now I have just one little glitch. I set up a filter for the 6m band, and when using the filter, the IOTA Progress button shows all my VHF IOTA confirmations quite accurately. I guess I also need to set up a filter to disregard 6m contacts to run the Progress report for HF IOTAs? When I run the IOTA Progress for HF without a filter, the program inserts four 6m verified contacts, three in place of the correct HF verified QSOs, and one for an IOTA I¡¯ve verified on 6m, but not on HF.
toggle quoted message
Show quoted text
73, Steve K4WA On Jan 22, 2025, at 2:12?PM, Dave AA6YQ <aa6yq@...> wrote: |
|
Not disregard 6m, just selected HF bands in Advanced Filters selection box. That worked¡
toggle quoted message
Show quoted text
73, Steve On Jan 23, 2025, at 1:46?PM, Steve via groups.io <k4wa@...> wrote: |
|
+ AA6YQ comments below
I successfully entered my call for the activations, now I have just one little glitch. I set up a filter for the 6m band, and when using the filter, the IOTA Progress button shows all my VHF IOTA confirmations quite accurately. I guess I also need to set up a filter to disregard 6m contacts to run the Progress report for HF IOTAs? When I run the IOTA Progress for HF without a filter, the program inserts four 6m verified contacts, three in place of the correct HF verified QSOs, and one for an IOTA I've verified on 6m, but not on HF. + The definition of distinct HF and VHF IOTA awards was another surprise. My plan is to replace the "Progress" and "Submission" buttons in the IOTA panel on the Main window's "Check Progress" tab with "HF Progress", "VHF Progress" , "HF Submission" and "VHF Submission" buttons; that will require making tab a bit wider to accommodate the wider button names. + In the meantime, appropriately filter the Log Page Display by band before invoking the Progress or Submission buttons. You can use a script to combine the filtering and progress reporting steps into a single function. 73, Dave, AA6YQ |
to navigate to use esc to dismiss