Menu
▾
▴
trustedqsl-testing
|
From: qsl F. <qsl...@or...> - 2020-02-27 10:42:54
|
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><font size="+1">
Dear All,</font></p>
<p><font size="+1">Back in Nantes, I uploaded my /MM log
yesterday evening using TQSL 2.5.2. </font></p>
<font size="+1">
</font><font size="+1"><span lang="en-US">AA/ First test with 21
QSO, 7 locators (4 characters) </span><span lang="en-US">and
“</span><span lang="en-US">Report on QTH difference”
radio-button
checked</span><span lang="en-US">:</span><span lang="en-US"><br>
After
a first </span><span lang="en-US">scan</span><span lang="en-US">
of
the log I had 21 mismatches reported </span><span lang="en-US">which</span><span
lang="en-US">
is normal as my Station Location is F5MYK/MM and locator is
null.
Trying to upload the same file again I entered an endless loop </span><span
lang="en-US">and
</span><span lang="en-US">canceled the operation </span><span
lang="en-US">after
more than 10000+ errors. </span><span lang="en-US">Solved
after a stop/start of the software.</span></font><br>
<font size="+1">
</font><br>
<font size="+1"><span lang="en-US">BB/
With option “Override station location with QTH details from the
log” checked:<br>
</span></font><font size="+1"><span lang="en-US">I
</span><span lang="en-US">sliced my log into 5 files (from 250 QSO
up
to 20000) and uploaded with TQSL. In some cases TQSL reported
that “n
QSO were already signed...” but I never uploaded those files
before?<br>
<br>
CC/ The stats:<br>
</span></font><font size="+1"><span lang="en-US">from
my VQLOG 26586 QSO including 375 SWL reports (beacons, heard but
no
QSO etc…).</span></font><br>
<font size="+1">
</font><font size="+1"><span lang="en-US">LoTW
log is now 26483 and the delta with VQLog is 103. </span></font>
<br>
<font size="+1">
</font><font size="+1"><span lang="en-US">I
doubt I have more than 100 QSO showing same
Date/Time/Band/Mode/Gridsquare/MyGridsquare </span><span
lang="en-US">but who
knows</span><span lang="en-US">? </span><span lang="en-US">Anyway
it
is less than 0.5%.</span></font><br>
<font size="+1">
</font><font size="+1"><span lang="en-US"><br>
DD/
</span><span lang="en-US">Suggested upgrades?</span></font><br>
<font size="+1">
</font><font size="+1"><span lang="en-US">- For the present I am not
sure I can check that the stations in my log are credited of my
varying locators ?</span></font><br>
<font size="+1">
</font><font size="+1"><span lang="en-US">> To show both locators
in the QSO details cards and records per call
queries…<br>
</span></font><br>
<font size="+1"><span lang="en-US">With the reserves in my /DD, my
conclusion as a /MM user is that the version 2.5.2 could be a
giant step forward!<br>
</span><br>
</font>
<font size="+1"><span lang="en-US">Thanks
a lot,</span></font><br>
<font size="+1">
</font><font size="+1"><span lang="en-US">73,
Frank - f5myk<br>
</span><br>
</font>
<br>
<font size="+1">
</font>
<p style="margin-bottom: 0cm; line-height: 100%"><font size="+1"><br>
</font>
</p>
<font size="+1">
</font>
</body>
</html>
|
|
From: qsl F. <qsl...@or...> - 2020-02-28 19:51:57
|
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><font size="+2">Hi Rick & All<br>
<br>
</font></p>
<p><font size="+2">AA/ My mistake !<br>
Thanks a lot for the message with the image.png.<br>
I am using a very old version of VQLog and the ADIF exporter
writes own_gridsq instead of my_gridsquare.<br>
Much better now and very sorry for the inconvenience.<br>
</font></p>
<p><font size="+2">May I suggest that if the user chooses "Override
Station Location with QTH from the log", TQSL could ensure that
the field MY_GRIDSQUARE is used at least for a few records ?</font></p>
<p><font size="+2"><br>
BB/ New uploads :<br>
For years 2013 up to 2017, logs are less than 2000 QSO and it is
OK.<br>
It seems that above 2500 lines (2018 & 2019) the upload is
more difficult ?<br>
I searched in both logs without finding why my_gridsquare is not
imported for all ADIF records.</font></p>
<font size="+2">2018 log:<br>
Line 1-5 are the ADIF header.</font><br>
<font size="+2">Line 6 - 3290 are ADIF records.<br>
<br>
Line 2671 - EA7ALL - my locator is detailed NJ35BW<br>
Line 2672 - UA3QUP - my locator is missing NJ35CW ?<br>
I did not check for all QSO but the DB is populated with the next
~600 QSO except for my_gridsquare field ?<br>
</font>
<p><font size="+2">I tried to find some difference between those
lines but saw nothing special but the fact that the GL contains
the string 'CW'?<br>
In case you need it, I will send this file to your private
address. Hope it won't bother you...<br>
</font></p>
<p><font size="+2">2019 log:<br>
After a few tries I uploaded the first 5000 lines (only) and the
same problem appears around line 2450.</font></p>
<p><font size="+2"><br>
</font></p>
<p><font size="+2">73, Frank</font></p>
<p><font size="+2"><br>
</font></p>
<p><font size="+2"><br>
</font></p>
<p><font size="+2"><br>
</font></p>
<p><font size="+2"> <br>
</font></p>
<p><font size="+2"><br>
</font></p>
<p><font size="+2"><br>
</font></p>
<p><font size="+2"></font><br>
</p>
</body>
</html>
|
|
From: Rick M. <k1...@ar...> - 2020-02-28 20:22:43
|
Frank,
The first thing you should look at is the log on the LoTW page that
describes what actions LoTW took when these logs were uploaded.
On the LoTW site, choose "Your Account", then "Your Activity".
Look at the "Result" link for one of your logs; you may see that LoTW was
rejecting some of these gridsquares. For example, LoTW has rules that
verify that grids are within the borders of various entities, and it may
have rejected some of your input.
73,
-Rick
On Fri, Feb 28, 2020 at 2:52 PM qsl F5MYK <qsl...@or...> wrote:
> Hi Rick & All
>
> AA/ My mistake !
> Thanks a lot for the message with the image.png.
> I am using a very old version of VQLog and the ADIF exporter writes
> own_gridsq instead of my_gridsquare.
> Much better now and very sorry for the inconvenience.
>
> May I suggest that if the user chooses "Override Station Location with QTH
> from the log", TQSL could ensure that the field MY_GRIDSQUARE is used at
> least for a few records ?
>
>
> BB/ New uploads :
> For years 2013 up to 2017, logs are less than 2000 QSO and it is OK.
> It seems that above 2500 lines (2018 & 2019) the upload is more difficult ?
> I searched in both logs without finding why my_gridsquare is not imported
> for all ADIF records.
> 2018 log:
> Line 1-5 are the ADIF header.
> Line 6 - 3290 are ADIF records.
>
> Line 2671 - EA7ALL - my locator is detailed NJ35BW
> Line 2672 - UA3QUP - my locator is missing NJ35CW ?
> I did not check for all QSO but the DB is populated with the next ~600 QSO
> except for my_gridsquare field ?
>
> I tried to find some difference between those lines but saw nothing
> special but the fact that the GL contains the string 'CW'?
> In case you need it, I will send this file to your private address. Hope
> it won't bother you...
>
> 2019 log:
> After a few tries I uploaded the first 5000 lines (only) and the same
> problem appears around line 2450.
>
>
> 73, Frank
>
>
>
>
>
>
>
>
> _______________________________________________
> Trustedqsl-testing mailing list
> Tru...@li...
> https://lists.sourceforge.net/lists/listinfo/trustedqsl-testing
>
--
Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA
|
|
From: Rick M. <k1...@ar...> - 2020-02-29 01:36:33
|
I've looked at Frank's log. The issue here is that this is a very large
number of station locations, more than what LoTW is expecting.
>From the 3285 QSOs there's 1230 different station locations (from 1117
different Gridsquares).
LoTW allows up to 999 different station locations, and the one that hit the
limit is the EA7ALL QSO. Once you hit 999, then the rest of the QSOs are
using the same station location setup.
I need to work with the HQ staff to get this limit increased.
As far as the duplicate QSOs being discovered, they're interesting. For
example, you have a QSO on 2018/02/27 at 1457 with a station from ML01ox
then another QSO at the same time from ML02oa. Since the time is the same,
TQSL considers this to be a dupe with an unexpected change of QTH. This is
of course incorrect, as this QSO happened across adjacent grids.
It would be better if the log emitted this as a single QSO with
"MY_GRIDSQUARE" set to "ML01ox,ML02oa", but they're counted as "already
uploaded" assuming they're the same QSO.
This probably should be something that TQSL allows - another setting that
indicates that the station roams across gridsquares and therefore grid
changes are to be ignored.
So this ran into a limit and I'll work to get that lifted. Cutting the log
into two pieces will get past that limit.
This has been really helpful in testing this new feature - it's going to
make operations like yours so much easier to handle for LoTW uploads.
73,
-Rick
On Fri, Feb 28, 2020 at 3:22 PM Rick Murphy <k1...@ar...> wrote:
> Frank,
> The first thing you should look at is the log on the LoTW page that
> describes what actions LoTW took when these logs were uploaded.
> On the LoTW site, choose "Your Account", then "Your Activity".
> Look at the "Result" link for one of your logs; you may see that LoTW was
> rejecting some of these gridsquares. For example, LoTW has rules that
> verify that grids are within the borders of various entities, and it may
> have rejected some of your input.
> 73,
> -Rick
>
> On Fri, Feb 28, 2020 at 2:52 PM qsl F5MYK <qsl...@or...> wrote:
>
>> Hi Rick & All
>>
>> AA/ My mistake !
>> Thanks a lot for the message with the image.png.
>> I am using a very old version of VQLog and the ADIF exporter writes
>> own_gridsq instead of my_gridsquare.
>> Much better now and very sorry for the inconvenience.
>>
>> May I suggest that if the user chooses "Override Station Location with
>> QTH from the log", TQSL could ensure that the field MY_GRIDSQUARE is used
>> at least for a few records ?
>>
>>
>> BB/ New uploads :
>> For years 2013 up to 2017, logs are less than 2000 QSO and it is OK.
>> It seems that above 2500 lines (2018 & 2019) the upload is more difficult
>> ?
>> I searched in both logs without finding why my_gridsquare is not imported
>> for all ADIF records.
>> 2018 log:
>> Line 1-5 are the ADIF header.
>> Line 6 - 3290 are ADIF records.
>>
>> Line 2671 - EA7ALL - my locator is detailed NJ35BW
>> Line 2672 - UA3QUP - my locator is missing NJ35CW ?
>> I did not check for all QSO but the DB is populated with the next ~600
>> QSO except for my_gridsquare field ?
>>
>> I tried to find some difference between those lines but saw nothing
>> special but the fact that the GL contains the string 'CW'?
>> In case you need it, I will send this file to your private address. Hope
>> it won't bother you...
>>
>> 2019 log:
>> After a few tries I uploaded the first 5000 lines (only) and the same
>> problem appears around line 2450.
>>
>>
>> 73, Frank
>>
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Trustedqsl-testing mailing list
>> Tru...@li...
>> https://lists.sourceforge.net/lists/listinfo/trustedqsl-testing
>>
>
>
> --
> Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA
>
--
Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA
|
|
From: Rick M. <k1...@ar...> - 2020-02-27 13:33:47
|
On Thu, Feb 27, 2020 at 6:26 AM qsl F5MYK <qsl...@or...> wrote:
> Dear All,
>
> Back in Nantes, I uploaded my /MM log yesterday evening using TQSL 2.5.2.
> AA/ First test with 21 QSO, 7 locators (4 characters) and “Report on QTH
> difference” radio-button checked:
> After a first scan of the log I had 21 mismatches reported which is
> normal as my Station Location is F5MYK/MM and locator is null. Trying to
> upload the same file again I entered an endless loop and canceled the
> operation after more than 10000+ errors. Solved after a stop/start of the
> software.
>
Do you recall what those errors were? I'd like to understand what caused
this error.
The problem reported by Walter earlier this week would cause an error
message loop ("Unable to open ca-bundle.crt. Your TQSL installation is
incomplete"), which I've now fixed. So, if it's that, then the cause is
known.
> BB/ With option “Override station location with QTH details from the log”
> checked:
> I sliced my log into 5 files (from 250 QSO up to 20000) and uploaded with
> TQSL. In some cases TQSL reported that “n QSO were already signed...” but I
> never uploaded those files before?
>
The "Already Uploaded" can be reported for duplicated QSOs. For example, if
you sign a QSO with a given station and a bit later try to sign that same
QSO, it'll be reported as "previously uploaded" even if that actually never
made it to Logbook.
CC/ The stats:
> from my VQLOG 26586 QSO including 375 SWL reports (beacons, heard but no
> QSO etc…).
> LoTW log is now 26483 and the delta with VQLog is 103.
> I doubt I have more than 100 QSO showing same
> Date/Time/Band/Mode/Gridsquare/MyGridsquare but who knows? Anyway it is
> less than 0.5%.
>
Not bad.
> DD/ Suggested upgrades?
> - For the present I am not sure I can check that the stations in my log
> are credited of my varying locators ?
>
By this, I assume you mean that your QSOs were uploaded with the proper
locators. You can query a QSO on the Logbook page and see the details
there, or you can download your log from LoTW and check the QSO details in
that download. It appears that you've verified this using VQLOG, though.
> > To show both locators in the QSO details cards and records per
> call queries…
>
Here, I think you mean with QSLs - showing full details of both your QTH
and that of whom you've worked. But I'm not sure what you're asking for.
Can you elaborate?
> With the reserves in my /DD, my conclusion as a /MM user is that the
> version 2.5.2 could be a giant step forward!
>
Thanks, 73
-Rick
>
> Thanks a lot,
> 73, Frank - f5myk
>
>
>
> _______________________________________________
> Trustedqsl-testing mailing list
> Tru...@li...
> https://lists.sourceforge.net/lists/listinfo/trustedqsl-testing
>
--
Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA
|
|
From: qsl F. <qsl...@or...> - 2020-02-27 19:30:24
Attachments:
ibbcllhfncapfadm.png
pcjkbghilhafpmbo.png
|
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi Rich and All,</p>
<p>AA/ About the errors :<br>
As I wrote my last message I tried to see the mistakes again
without success.<br>
The first upload clearly stated the discrepancy between my Station
Location and the log.<br>
For the second upload of the same log I am not sure I saw an
explanation, I only remember the error counter which was
increasing quickly.</p>
<p>BB/ I first tried to upload 21 QSO (year 2013) and then I upload
the log for the whole year 2013.<br>
I had the message (quotation from memory) "21 QSO were already
signed and 300 are new". I chose the button "Upload the new QSO"
and it was OK.<br>
For the following years I only uploaded each file once. When I
process the logs I try to avoid logging the same station in the
same minute when the QSO took place on the 'locator edge' ... <br>
</p>
<p>DD/ It is up to you but for moving stations this could be
interesting to show the locator registered with the QSO ?<br>
Today I received 2 messages from Brazilian stations (extracts
below), they are not able to see my registered locators?<br>
</p>
<p>QUOTE<br>
</p>
<p>can you help me inform me your grid locators from this qsos? <br>
6m was a incredible qso because is blocked prop from here .. rare
open
<br>
</p>
<table align="center">
<tbody>
<tr>
<td><a
href="https://lotw.arrl.org/lotwuser/qsodetail?qso=1100840367"
target="_new">Details</a></td>
<td>PY7DJ</td>
<td>F5MYK/MM</td>
<td style="text-align:center">2019-11-17 17:22:00</td>
<td style="text-align:right">17M</td>
<td style="text-align:center">FT8</td>
<td style="text-align:right">18.10050</td>
<td><a
href="https://lotw.arrl.org/lotwuser/qsodetail?qso=1141279668"
target="_new">-NONE-</a></td>
<td> </td>
</tr>
<tr>
<td><a
href="https://lotw.arrl.org/lotwuser/qsodetail?qso=1100125923"
target="_new">Details</a></td>
<td>PY7DJ</td>
<td>F5MYK/MM</td>
<td style="text-align:center">2019-11-15 17:38:00</td>
<td style="text-align:right">15M</td>
<td style="text-align:center">FT8</td>
<td style="text-align:right">21.07547</td>
<td><a
href="https://lotw.arrl.org/lotwuser/qsodetail?qso=1141279342"
target="_new">-NONE-</a></td>
<td> </td>
</tr>
<tr>
<td><a
href="https://lotw.arrl.org/lotwuser/qsodetail?qso=1100125920"
target="_new">Details</a></td>
<td>PY7DJ</td>
<td>F5MYK/MM</td>
<td style="text-align:center">2019-11-15 19:49:00</td>
<td style="text-align:right">6M</td>
<td style="text-align:center">FT8</td>
<td style="text-align:right">50.31475</td>
<td><a
href="https://lotw.arrl.org/lotwuser/qsodetail?qso=1141279359"
target="_new">-NONE-</a></td>
<td> </td>
</tr>
<tr>
<td><a
href="https://lotw.arrl.org/lotwuser/qsodetail?qso=802970480"
target="_new">Details</a></td>
<td>PY7DJ</td>
<td>F5MYK/MM</td>
<td style="text-align:center">2016-12-12 00:34:00</td>
<td style="text-align:right">40M</td>
<td style="text-align:center">JT65</td>
<td style="text-align:right">7.07600</td>
<td><a
href="https://lotw.arrl.org/lotwuser/qsodetail?qso=1141259461"
target="_new">-NONE-</a></td>
<td> </td>
</tr>
</tbody>
</table>
<p>UNQUOTE</p>
<p>QUOTE</p>
<p><img src="cid:par...@or..." alt=""></p>
UNQUOTE<br>
<p>I already explained that it is not a mistake as my DXCC was
'NONE', but it seems that PY3TO does not know my locator. Idem for
PY7DJ.<br>
</p>
<p><br>
</p>
<p>Using the QSO details I can see the locator of PY7DJ but I do not
know if he sees mine ?</p>
<p><img src="cid:par...@or..." alt=""></p>
<p><br>
</p>
<p>Thanks again for all the work done,</p>
<p>73, Frank - f5myk<br>
</p>
<p><br>
</p>
</body>
</html>
|
|
From: Rick M. <k1...@ar...> - 2020-02-28 02:18:41
|
Frank,
If your grid was uploaded, you would see that detail.
For example, here's a QSO of mine (completely bogus, so I'm not giving
anything away):
[image: image.png]
So, you should see the grid appearing in any QSOs you upload.
73,
-Rick
On Thu, Feb 27, 2020 at 9:02 PM qsl F5MYK <qsl...@or...> wrote:
> Hi Rich and All,
>
> AA/ About the errors :
> As I wrote my last message I tried to see the mistakes again without
> success.
> The first upload clearly stated the discrepancy between my Station
> Location and the log.
> For the second upload of the same log I am not sure I saw an explanation,
> I only remember the error counter which was increasing quickly.
>
> BB/ I first tried to upload 21 QSO (year 2013) and then I upload the log
> for the whole year 2013.
> I had the message (quotation from memory) "21 QSO were already signed and
> 300 are new". I chose the button "Upload the new QSO" and it was OK.
> For the following years I only uploaded each file once. When I process the
> logs I try to avoid logging the same station in the same minute when the
> QSO took place on the 'locator edge' ...
>
> DD/ It is up to you but for moving stations this could be interesting to
> show the locator registered with the QSO ?
> Today I received 2 messages from Brazilian stations (extracts below), they
> are not able to see my registered locators?
>
> QUOTE
>
> can you help me inform me your grid locators from this qsos?
> 6m was a incredible qso because is blocked prop from here .. rare open
> Details <https://lotw.arrl.org/lotwuser/qsodetail?qso=1100840367> PY7DJ
> F5MYK/MM 2019-11-17 17:22:00 17M FT8 18.10050 -NONE-
> <https://lotw.arrl.org/lotwuser/qsodetail?qso=1141279668>
> Details <https://lotw.arrl.org/lotwuser/qsodetail?qso=1100125923> PY7DJ
> F5MYK/MM 2019-11-15 17:38:00 15M FT8 21.07547 -NONE-
> <https://lotw.arrl.org/lotwuser/qsodetail?qso=1141279342>
> Details <https://lotw.arrl.org/lotwuser/qsodetail?qso=1100125920> PY7DJ
> F5MYK/MM 2019-11-15 19:49:00 6M FT8 50.31475 -NONE-
> <https://lotw.arrl.org/lotwuser/qsodetail?qso=1141279359>
> Details <https://lotw.arrl.org/lotwuser/qsodetail?qso=802970480> PY7DJ
> F5MYK/MM 2016-12-12 00:34:00 40M JT65 7.07600 -NONE-
> <https://lotw.arrl.org/lotwuser/qsodetail?qso=1141259461>
>
> UNQUOTE
>
> QUOTE
>
> UNQUOTE
>
> I already explained that it is not a mistake as my DXCC was 'NONE', but it
> seems that PY3TO does not know my locator. Idem for PY7DJ.
>
>
> Using the QSO details I can see the locator of PY7DJ but I do not know if
> he sees mine ?
>
>
> Thanks again for all the work done,
>
> 73, Frank - f5myk
>
>
> _______________________________________________
> Trustedqsl-testing mailing list
> Tru...@li...
> https://lists.sourceforge.net/lists/listinfo/trustedqsl-testing
>
--
Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA
|
Thanks for helping keep SourceForge clean.
X