Date
1 - 11 of 11
Any Way to Retrieve Logs Sent to Endorsement Checker?
|
Hello 070'ers,
In pursuing the 365 endorsement I brought m radio along on vacation in North Central New Mexico to try and fill in a bunch of blanks that occur due to summer vacation. Here's the rub. My vintage HP laptop's hard drive went belly up and all the contacts I made filling in dates have been lost. Except -- a few days ago I uploaded the PSK log to the PODXS 070 Endorsement checker. So now I am wondering if there is any way to get that ADIF file back. Does anybody know? Completely off-topic I am otherwise having a lot of fun here in the Land of Enchantment activating SOTA summits with my KX2. Yesterday I managed a SSB contact with Eli HA9RE in Hungary with just 12 watts and a homebrew doublet! I was on Cerro de los Taoses. That was a rea kick. If you want to read and see more here is my blog entry on it with a cool drone video of the summit: https://kg6mzs.com/2022/07/14/cerro-de-los-taoses/ TIA and 73 Eric KG6MZS |
|
|
|
KN4ZXG
Eric, I don't know the answer to your question about the endorsement checker. The endorsement checker shows your ADIF file headers so it is obviously there but I don't see a way to retrieve it. However, if you upload your logs to LOTW or eQSL you will be able to download ADIF from either of those.
You will also be able to check for the dates you have submitted but going into the endorsement checker, clicking on your callsign from when you last uploaded your log. There's a row on that page that's gray and starts with the "Awards Progress:" on that line is a link "070-365". Click on that, then scroll down or search for your callsign. You will be able to click on it and it will open a PDF that shows your progress in 365 and will show all the days you have and haven't done. Hope this helps! |
|
|
|
Assume video Eric! Beautiful portable QTH. Have fun.
toggle quoted message
Show quoted text
Best 73, Buz, WA5AMM On Jul 15, 2022, at 10:55 AM, Eric KG6MZS <contact@...> wrote: --
de, WA5AMM, Buz |
|
|
|
Thanks for the reply Ted, Unfortunately I did not upload that ADIF anywhere but to the endorsement checkers. I know the dates I thought I had filled in, but that obviously isn't enough to rebuild the QSO log entry. It looks like unless I can get that ADIF i submitted it's "we'll get 'um next year!" and a painful less [re]learned about backing up OFF the hard drive. 73 Eric KG6MZS On 7/15/22 9:37 AM, KN4ZXG wrote:
Eric, I don't know the answer to your question about the endorsement checker. The endorsement checker shows your ADIF file headers so it is obviously there but I don't see a way to retrieve it. However, if you upload your logs to LOTW or eQSL you will be able to download ADIF from either of those. |
|
|
|
David, K9DWR
* Eric KG6MZS <contact@...> [2022-07-15 09:55]:
Thanks for the reply Ted,I think I may be able to get at the ADIF. Let me take a look. -- David, K9DWR #1604 LONP #255 david@... |
|
|
|
GA - Bob - K4VBM
Eric,
Each of the 070 awards has some facility to show you the QSOs that applied to the award, so that can help you reclaim your lost data. FOR EXAMPLE: On the worked the world page, you can download some of the data as a TXT or XLS file. Maybe that will somehow help you capture some of the information you lost, as it has date, time, band, and call sign. Unfortunately, only the QSOs that applied to the WTW endorsement will be present. For Grids, click on the 'Have' number link in both the green awarded section and the yellow working on section In general, click on the 'Have' number link for each different award and see what you can find and reclaim. This probably won't help you, but some info here also about your last upload. Go back to the Endorsement checker web page and find your call sign in the list. Over to the right there is a link in very tiny font that says 'rpt'. Click on that. For you, I get this: Unescaped left brace in regex is deprecated here (and will be fatal in Perl 5.30), passed through in regex; marked by <-- HERE in m/^(\w+)(,{ <-- HERE .+})?$/ at ../adif-validator/ADIF/Validator.pm line 92, <DATA> line 126.
Unescaped left brace in regex is deprecated here (and will be fatal in Perl 5.30), passed through in regex; marked by <-- HERE in m/^,{ <-- HERE (-?(?:\d+(?:\.\d*)?)):(-?(?:\d+(?:\.\d*)?))}$/ at ../adif-validator/ADIF/Validator.pm line 107, <DATA> line 126.
Unescaped left brace in regex is deprecated here (and will be fatal in Perl 5.30), passed through in regex; marked by <-- HERE in m/^,{ <-- HERE (.+)}$/ at ../adif-validator/ADIF/Validator.pm line 110, <DATA> line 126.
KJ4IZW ADIF VALIDATOR
This reviews a AIDF file for warnings/errors using the v3.0.4 spec: http://www.adif.org/304/ADIF_304.htm
Tue Jul 12 15:43:51 EDT 2022
==============
ADIF_VER:
PROGRAMID: HamRadioDeluxe
PROGRAMVERSION: Version 6.7.0.391
ADIF_VERS: 2.2
CREATED_TIMESTAMP: 20220712 124020
Records: 72
==============
#++
#
# HRD Logbook version 6.7.0.391, Copyright © 2003 - 2021 by HRD Software, LLC
# https://www.HamRadioDeluxe.com/
#
# Created: 20220712 124020
#
#--
==============
[ERROR: BAD_ENUM_VALUE MODE x1] Not an allowed value for this enumerated field.
rec 28 line 327 VA7GEM:20220521:014253:PSK63F:40m PSK63F
[ERROR: BAD_ENUM_VALUE STATE x1] Not an allowed value for this enumerated field.
rec 13 line 184 WH7TT:20220709:002016:PSK31:20m [DXCC=110] bad value: 'CA'
[ERROR: INVALID_POSITIVE_NUM DISTANCE x3] This value should be positive.
rec 43 line 467 VA7GEM:20220514:200814:PSK31:20m 0.0
rec 44 line 474 KA5VZG:20220514:194453:PSK31:20m 0.0
rec 45 line 479 WB9KVI:20220514:194058:PSK31:20m 0.0
[ERROR: INVALID_POSITIVE_NUM RX_PWR x72] This value should be positive.
== 100% of RECORDS == (values:0.0)
[ERROR: UNKNOWN_FIELD ADIF_VERS x1] Unknown field name.
rec 0 line 0 HEADER
[ERROR: UNKNOWN_FIELD HRDCOUNTRYNO x72] Unknown field name.
== 100% of RECORDS == (values:)
[WARNING: MISSING_PARENT_FIELD MY_CNTY x69] Cannot validate this field without parent field defined.
== 95% of RECORDS == (values:MY_DXCC)
[WARNING: MISSING_PARENT_FIELD MY_STATE x69] Cannot validate this field without parent field defined.
== 95% of RECORDS == (values:MY_DXCC)
[WARNING: NO_ADIF_VER x1] Optional ADIF_VER missing from header.
0
==============
FIELDS USED:
100% (72) ANT_AZ
100% (72) ANT_EL
100% (72) A_INDEX
100% (72) BAND
100% (72) CALL
100% (72) COUNTRY
100% (72) DISTANCE
100% (72) DXCC
100% (72) EQSL_QSL_RCVD
100% (72) EQSL_QSL_SENT
100% (72) FORCE_INIT
100% (72) FREQ
100% (72) HRDCOUNTRYNO
100% (72) K_INDEX
100% (72) LOTW_QSL_RCVD
100% (72) LOTW_QSL_SENT
100% (72) MODE
100% (72) PFX
100% (72) QSL_RCVD
100% (72) QSL_SENT
100% (72) QSO_COMPLETE
100% (72) QSO_DATE
100% (72) QSO_RANDOM
100% (72) RST_RCVD
100% (72) RST_SENT
100% (72) RX_PWR
100% (72) SFI
100% (72) STATION_CALLSIGN
100% (72) SWL
100% (72) TIME_OFF
100% (72) TIME_ON
97% (70) NAME
95% (69) MY_CNTY
95% (69) MY_COUNTRY
95% (69) MY_GRIDSQUARE
95% (69) MY_NAME
95% (69) MY_RIG
95% (69) MY_STATE
95% (69) OPERATOR
93% (67) MY_LAT
93% (67) MY_LON
79% (57) STATE
66% (48) TX_PWR
63% (46) QTH
58% (42) GRIDSQUARE
58% (42) LAT
58% (42) LON
52% (38) ADDRESS
47% (34) QSL_RCVD_VIA
47% (34) QSL_SENT_VIA
44% (32) COMMENT
43% (31) CONT
41% (30) CQZ
40% (29) MY_CITY
38% (28) ITUZ
27% (20) LOTW_QSLRDATE
25% (18) MY_POSTAL_CODE
18% (13) BAND_RX
18% (13) MY_CQ_ZONE
18% (13) MY_ITU_ZONE
16% (12) CNTY
16% (12) EMAIL
16% (12) SRX_STRING
16% (12) STX_STRING
11% (8) QSL_VIA
4% (3) IOTA
4% (3) SRX
4% (3) STX
2% (2) OWNER_CALLSIGN
==============
excluded: BAD_STRING,BAD_MULTILINE_STRING,BAD_MULTILINE_NEWLINE,NO_TYPE,BAD_NUMBER.SRX,BAD_NUMBER.STX,UNKNOWN_SUB_ENUMERATION.CNTY
For me, I get this:
|
|
|
|
David, K9DWR
* David Rock <david@...> [2022-07-15 11:19]:
* Eric KG6MZS <contact@...> [2022-07-15 09:55]:I forwarded what I could find in the checker. It only has whatever the mostThanks for the reply Ted, recent upload was, so hopefully the 72 entries are all that you are looking for. If there was a different upload, I don't think I can get that. -- David, K9DWR #1604 LONP #255 david@... |
|
|
Eric, |
|
|
|
Erik...one thought?
Do you have a current LotW that's uploaded?
Milt.
N6MG -----Original Message-----
From: Eric KG6MZS <contact@...> To: main@070Club.groups.io Sent: Fri, Jul 15, 2022 7:55 am Subject: [070Club] Any Way to Retrieve Logs Sent to Endorsement Checker? Hello 070'ers,
In pursuing the 365 endorsement I brought m radio along on vacation in North Central New Mexico to try and fill in a bunch of blanks that occur due to summer vacation. Here's the rub. My vintage HP laptop's hard drive went belly up and all the contacts I made filling in dates have been lost. Except -- a few days ago I uploaded the PSK log to the PODXS 070 Endorsement checker. So now I am wondering if there is any way to get that ADIF file back. Does anybody know? Completely off-topic I am otherwise having a lot of fun here in the Land of Enchantment activating SOTA summits with my KX2. Yesterday I managed a SSB contact with Eli HA9RE in Hungary with just 12 watts and a homebrew doublet! I was on Cerro de los Taoses. That was a rea kick. If you want to read and see more here is my blog entry on it with a cool drone video of the summit: https://kg6mzs.com/2022/07/14/cerro-de-los-taoses/ TIA and 73 Eric KG6MZS |
|
|
|
A Huge, Booming Thank You to all who responded.
I am back up and running with all the QSOs I had up until my last upload -- minus a few FT8 contacts. FT8 just doesn't have a great group like this to offer such fine support. I only lost July 13 and 14 in the 365 day quest. My major logbook is all safe and sound and backed up back home. This was only the stuff that was on this refurbished HP that I got just for taking of the road for vacations. All the stuff from my grid DM17 gridpedition is safely in my main log. I am now in that laborious process of setting up this work computer -- a spiffy MacBook Pro -- with Boot Camp to run Windows 10 and the dreaded HRD suite. I just had my first PSK contact there, so I got it all working. I just forgot how hard it is to set up HRD from scratch. I'm used to importing all my macros and prefs. It is nice to have a large, sharp and bright display, though. So much better that the old HP laptop. I should've done this instead of the HP. Thanks again everybody. You all are the best! 73 Eric KG6MZS |
|
|
|
Eric K9VIC (2404 is)
I just looked through my log to see what days I've worked you. We had a qso on July 6th, but not on either of the two missing dates. Eric/K9VIC
On Friday, July 15, 2022 at 01:32:35 PM CDT, Eric KG6MZS <contact@...> wrote:
A Huge, Booming Thank You to all who responded. I am back up and running with all the QSOs I had up until my last upload -- minus a few FT8 contacts. FT8 just doesn't have a great group like this to offer such fine support. I only lost July 13 and 14 in the 365 day quest. My major logbook is all safe and sound and backed up back home. This was only the stuff that was on this refurbished HP that I got just for taking of the road for vacations. All the stuff from my grid DM17 gridpedition is safely in my main log. I am now in that laborious process of setting up this work computer -- a spiffy MacBook Pro -- with Boot Camp to run Windows 10 and the dreaded HRD suite. I just had my first PSK contact there, so I got it all working. I just forgot how hard it is to set up HRD from scratch. I'm used to importing all my macros and prefs. It is nice to have a large, sharp and bright display, though. So much better that the old HP laptop. I should've done this instead of the HP. Thanks again everybody. You all are the best! 73 Eric KG6MZS |
|
|