Great Video on something I was having a problem doing. Loved the detail that you went into, and pointed out some of the Why and If that is important in the end. Thank You! Joe KK3JOE
Well. I truly stand corrected! I honestly thought my logbook was the most concise data. I had no idea how substantial the lookup procedure is. Thank you. Steve. GJ6WRI
Mike: Thanks for the excellent tutorial. I noticed after loading 6.7.0.244 that the test tab in the callsign lookup takes quite a while to populate, far slower than it used to be. Is this a problem on my end or has something changed since the last release?
Thanks for the hierarchy info. I would be nice if the entry window would flag/warn/announce the discrepancies from the sources I selected BEFORE I saved the contact. All the data sources often disagree on CQ and ITU zones, and Grid locations. I would like to choose or do further online research to confirm which data is correct. This would be especially useful for updating old log entries.
Not a bad idea, David. We used to do that, but these sources vary quite a bit sometimes. So the approach we've taken is to allow people to orient what they feel is the best source at the top. We also dong "guess" about zones or grids. If the fields are empty, we don't try to guess. What call and source were you looking at?
@@HamRadioDeluxe Hi Mike, I use QRZ and HamCall. The two databases often disagreed. UN6P grid squares differ between the two databases. QRZ = MO60lb HamCall = MO60LC. I have four LoTW confirmations showing his grid as MO60LC. So in this instance HamCall appears to be correct. I'm trying to update my 70,000+ Qs with the correct CQ/ITU zones and grid squares. A tedious job since I can't simply compare the two databases and my previous logged data on same screen. I know this is not a problem for the average ham.
Thanks. That's why we recorded this one. This was a significant change from the way it looked before. We'll be doing more videos after the 6.7 release is published.
Default locator? If I understand the question properly, we don't populate any data based on defaults. We only populate verified data. If the locator is found in one of the lookup sources, we use it. If not, we leave it blank.
Great Video on something I was having a problem doing. Loved the detail that you went into, and pointed out some of the Why and If that is important in the end. Thank You! Joe KK3JOE
Glad it helped!
Well. I truly stand corrected! I honestly thought my logbook was the most concise data. I had no idea how substantial the lookup procedure is. Thank you. Steve. GJ6WRI
Thanks Mike for the great video and also for our time to do it.
Great tutorial Mike, can’t wait to try it! Thanks to the entire HRD team for all the hard work!!! Be blessed guys!!!
KE8BYM
Mike: Thanks for the excellent tutorial. I noticed after loading 6.7.0.244 that the test tab in the callsign lookup takes quite a while to populate, far slower than it used to be. Is this a problem on my end or has something changed since the last release?
Thanks for the hierarchy info. I would be nice if the entry window would flag/warn/announce the discrepancies from the sources I selected BEFORE I saved the contact. All the data sources often disagree on CQ and ITU zones, and Grid locations. I would like to choose or do further online research to confirm which data is correct. This would be especially useful for updating old log entries.
Not a bad idea, David. We used to do that, but these sources vary quite a bit sometimes. So the approach we've taken is to allow people to orient what they feel is the best source at the top. We also dong "guess" about zones or grids. If the fields are empty, we don't try to guess. What call and source were you looking at?
@@HamRadioDeluxe
Hi Mike, I use QRZ and HamCall. The two databases often disagreed. UN6P grid squares differ between the two databases. QRZ = MO60lb HamCall = MO60LC. I have four LoTW confirmations showing his grid as MO60LC. So in this instance HamCall appears to be correct. I'm trying to update my 70,000+ Qs with the correct CQ/ITU zones and grid squares. A tedious job since I can't simply compare the two databases and my previous logged data on same screen. I know this is not a problem for the average ham.
No station images with the look up?
When will 6.7 be available for download? Still just 6.6 on the site
Friday morning in the US.
Tried to add coupon code at check out and it would not take it.
need new updated tutorials v6.6 plus
Thanks. That's why we recorded this one. This was a significant change from the way it looked before. We'll be doing more videos after the 6.7 release is published.
Can I disable the default LOCATOR for callsigns?
Default locator? If I understand the question properly, we don't populate any data based on defaults. We only populate verified data. If the locator is found in one of the lookup sources, we use it. If not, we leave it blank.
coupon code did not work! It says that code is invalid.
RATS! That's my fault. Sorry. I got distracted and thought I had created it. Try it now. >Mike VK4/WA9PIE
@@HamRadioDeluxe It worked, Thank you!!! KG5CFR