Date   

Re: VE7CC - Spot Source

Charles N2SO
 

FB Curt. I'm glad that worked out. If you want skimmer spots just enter the command "set/skimmer" or if you use VE7CC software program, just check the skimmer box in the configuration window. Then re-start Spotcollector.

On Fri, Oct 16, 2020 at 9:31 AM Curt Bowles <curt.bowles@...> wrote:
Hi Charles

That worked just fine this time...thanks for the feedback... appreciated.

73
--
Curt Bowles
VE3ZN



--
73, Charles N2SO
 

--
73, Charles N2SO


Re: VE7CC - Spot Source

John Battin
 

I had the same THING FOR ABOUT 6 HOURS

 

Sent from Mail for Windows 10

 

From: Curt Bowles
Sent: Friday, October 16, 2020 6:24 AM
To: DXLab@groups.io
Subject: [DXLab] VE7CC - Spot Source

 

Anyone else having issues with VE7CC…

NO changes have been made to the setup under “SpotCollector/Config/Spot Sources” : 

SpotCollector has been unable to connect to VE7CC for the last 24 hours or so.

Keep getting this msg:

Winsock Error # 10060 - The attempt to connect timed out @ 16-Oct-20 1119

 

Host Address: dxc.ve7cc.net

Port: 23

Caption: VE7CC

Plus my user name and password 

--
Curt Bowles
VE3ZN

 


Re: VE7CC - Spot Source

Curt Bowles
 

Hi Charles

That worked just fine this time...thanks for the feedback... appreciated.

73
--
Curt Bowles
VE3ZN


Re: VE7CC - Spot Source

Charles N2SO
 

Sorry about that. The image did not go through. VE7CC appears to be down. Possible weather problems. It was suggested to try another node like: N4ZKF-1 (+CW Skimmer)
Should be the same feed.

On Fri, Oct 16, 2020, 8:00 AM Curt Bowles <curt.bowles@...> wrote:
Charles N2SO

Excuse my ignorance but what does "From CCusers" mean...

Nothing else in you msg
--
Curt Bowles
VE3ZN


--
73, Charles N2SO


Re: VE7CC - Spot Source

Curt Bowles
 

Charles N2SO

Excuse my ignorance but what does "From CCusers" mean...

Nothing else in you msg
--
Curt Bowles
VE3ZN


Re: VE7CC - Spot Source

Charles N2SO
 

From CCusers



On Fri, Oct 16, 2020 at 7:24 AM Curt Bowles <curt.bowles@...> wrote:

Anyone else having issues with VE7CC…

NO changes have been made to the setup under “SpotCollector/Config/Spot Sources” : 

SpotCollector has been unable to connect to VE7CC for the last 24 hours or so.

Keep getting this msg:

Winsock Error # 10060 - The attempt to connect timed out @ 16-Oct-20 1119


Host Address: dxc.ve7cc.net

Port: 23

Caption: VE7CC

Plus my user name and password 

--
Curt Bowles
VE3ZN



--
73, Charles N2SO
 

--
73, Charles N2SO


VE7CC - Spot Source

Curt Bowles
 

Anyone else having issues with VE7CC…

NO changes have been made to the setup under “SpotCollector/Config/Spot Sources” : 

SpotCollector has been unable to connect to VE7CC for the last 24 hours or so.

Keep getting this msg:

Winsock Error # 10060 - The attempt to connect timed out @ 16-Oct-20 1119


Host Address: dxc.ve7cc.net

Port: 23

Caption: VE7CC

Plus my user name and password 

--
Curt Bowles
VE3ZN


Pathfinder does not obtain (and diplay in DXKeeper LOG page) NAME and QTH data from QRZ.COM

Tom DF7TV
 

Hello,
since about October 12, 2020 I can not get the NAME and QTH data from QRZ.COM into a new QSO Log in DXKeeper by clicking the "CBA" button. Surprisingly the email address of a new contact for example, is correctly inserted from QRZ.COM as before.
I looked into the ErrorLog of Pathfinder and DXKeeper, but there are no actual errors shown.

73
Tom


Debugging a "No Matching QSO in Log" Error When Synchronizing With LoTW

Dave AA6YQ
 

The diagnostic procedure described in message

<https://groups.io/g/DXLab/message/196791>

of the "LoTW upload first time" thread is now available with an annotated screen shot in

<https://www.dxlabsuite.com/dxlabwiki/LoTWNoMatchingQSOInLog>

As always, corrections and suggested improvements are welcome.

73,

Dave, AA6YQ


Re: Spot Collector Error Log

Jim Denneny
 

Thanks Dave

Jim


Re: Spot Collector Error Log

Dave AA6YQ
 

+ AA6YQ comments below

My apology Dave. SC Error has cleared itself.

+ By that, I assume you mean that you unchecked the "Log debugging info" box on the Configuration window's General tab.

73,

Dave AA6YQ


Re: Spot Collector Error Log

Jim Denneny
 

OK Dave

My apology Dave.  SC Error has cleared itself.

73, Jim K7EG


Re: Default Mode in Capture Window

Dave AA6YQ
 

+ aa6yq COMMENTS BELOW

It would seem that there is no "default" signal report for JT65/WSJT.
Instead O/O simply indicates "signals copied at both ends" (or QSO complete).

I understand Fred's request for a default but unchecking "Initialize RST items to 59/599" and leaving those fields blank would be just as valid as O/O - ie. logging the QSO as complete is equivalent to O/O.

+ Fred AB1OC, are you comfortable with using blank signal reports as defaults instead of O and O (or O and RO)?

73,

Dave, AA6YQ


Re: Spot Collector Error Log

Dave AA6YQ
 

+ AA6YQ comments below

Deleted error.txt in Config / General tab. Restarted SC. Error remains. Regenerated errorlog.txt. Unable to copy paste file here. Sent you a zipshare copy of errorlog via ambersoft.

+ The zipshare you sent me was empty.

+ You do not need to copy/paste the errorlog.txt file to attach this file to an email message and send the message to

aa6yq (at) ambersoft.com

+ Unless the errorlog.txt contains the two word phrase

program error

+ it is being generated by the fact that you have "log debugging info" enable on the Configuration window's General tab. When I searched the errorlog text that you posted earlier today, I did not see the phrase "program error".

+ See

<https://www.dxlabsuite.com/dxlabwiki/ErrorLogs>


73,

Dave, AA6YQ


Re: Spot Collector Error Log

Jim Denneny
 

Dave

Deleted error.txt in Config / General tab. Restarted SC.  Error remains. Regenerated errorlog.txt.  Unable to copy paste file here.  Sent you a zipshare copy of errorlog via ambersoft.  Hope this helps you locate my issue.
Jim K7EG


Re: LOTW upload first time

Dave AA6YQ
 

+ AA6YQ comments below

Hi Dave.....this "No matching QSO in log" error has me stumped. What is DXkeeper comparing my uploaded Qs to?

+ As I stated in my previous response

"DXKeeper expects that the information reported by LoTW for a QSO exact matches that QSO's information in your log; any discrepancy produces this error message"

< https://groups.io/g/DXLab/message/196762>

+ In that response, I provided an example:

"For example, if you submit a QSO to LoTW whose start time is 00:00:00 Z, then modified the logged QSO's start time to 00:00:01Z, and the invoke "Sync LoTW QSOs", the result will be "no matching QSO in log".


You say any discrepancy will cause this but that could mean anything!!

+ The discrepancy can only be in one of the logged items that DXKeeper submits to LotW. The 10 items that DXKeeper submits to LoTW are documented in the second paragraph of this article:

<https://www.dxlabsuite.com/dxkeeper/Help/QSL.htm#QSLing%20via%20LotW>

1. Callsign of the station worked
2. UTC date at which the QSO began
3. UTC time at which the QSO began
4. QSO Mode (mapped to modes accepted by LOTW)
5. QSO Frequency
6. QSO Band
7. QSO receive frequency
8. QSO receive band
9. Satellite name
10, Propagation mode

How am I supposed to know what has mismatched on 88 Qs???

+ As I suggested in my previous response, "Pick one mismatch, and get to the bottom of it. That will likely explain the other 87."

+ Choose one QSO in your log for which DXKeeper reported "no matching QSO in log". Right-click this QSO, and select "Update from LoTW" from the pop-up menu. After the operation completes, navigate to DXKeeper's Databases folder and use Notepad to open the file

LoTW_UpdateSingle_ADI.txt

+ After the <eoh> tag in this file, you will find ADIF fields containing information being reported by LoTW. For example, the TIME_ON and QSO_DATE fields will convey the QSO's start time. In the logged QSO you chose, compare each of the 10 items that DXKeeper sent to LoTW with the information reported by LoTW. Find the mismatch.

I have printed off the list of calls and started looking at what I logged.
I cant see anything that I missed or could be interpreted as wrong. One of the Qs I actually confirmed with a qsl card and the data on the card I received matches my log

exactly!!! If my start time is logged a minute off what the other guy uploaded, is this grounds for this error to pop up??

+ The "no matching QSO in log" message is not reporting a mismatch between what you submitted and what your QSO partner submitted.

+ The "no matching QSO in log" message is reporting a mismatch between the information you submitted to LoTW, and the information LoTW is now reporting to DXKeeper -- which should be identical to what you submitted. If it's not identical, then you either changed the contents of one of those 10 items in the logged QSO after submitting it to LoTW, or the data was corrupted in transmit between DXKeeper and LoTW, or LoTW corrupted the data you submitted.

Why did LOTW report this group of 88 errors (87 no matches error) from my first upload while I was trying to sync the Second batch I uploaded with my second callsign?

+ When you invoked "Sync LoTW QSOs", LoTW reports QSOs newly-confirmed on or after the day you last submitted "Sync LoTW QSOs" - erroneously ignoring the time of the last "Sync LoTW QSOs" invocation that DXKeeper submits with its query to LoTW. Evidently, the QSOs you submitted in your first batch were confirmed on the same day as the QSOs you submitted in your second batch. Ignoring the time of last invocation is a defect in LoTW, but it hasn't been corrected in the ~10 years since I reported it.

+ Furthermore, LoTW is not the source of the "no matching QSO in log" error messages. DXKeeper is displaying this error message because the information being reported by LoTW is inconsistent with the information DXKeeper sent to LoTW, as described above.

What filter or SQL do I need to get the list of 88 errors appearing on my log screen again?
Thank you for your help..it is appreciated. I am not sure where to look next.

+ Focus on debugging a single logged QSOs that generated the "no matching QSO in log" error message, using the steps prescribed above.

73,

Dave, AA6YQ


Re: Best way to enter a general comment

Dave AA6YQ
 

+ AA6YQ comments below

What is the best way to enter a general comment in the log? Such as when one starts to use a new amplifier or make certain adjustments to an antenna. I would like to find a way to put this on the timeline of the log rather than in a comment file.

+ Define a new "my QTH" that is in all respects identical to the "my QTH" that you're currently using, but with updated descriptions of your rig and antenna in the "my QTH" fields provided for that purpose. Then change your "default myQTH ID" to specify the ID for this new "my QTH". In the future, you'll be able to distinguish QSOs made before and after the change by filtering on the myQTHID field.

73,

Dave, AA6YQ


Best way to enter a general comment

Fredric T. Serota
 

What is the best way to enter a general comment in the log? Such as when one starts to use a new amplifier or make certain adjustments to an antenna. I would like to find a way to put this on the timeline of the log rather than in a comment file. Thanks,

Fred, K3BHX


Re: DXKeeper problem

Dave AA6YQ
 

The following message started coming up when I start DXKeeper: "This QSO has not been unlocked for modification; set its end time?" The upper boxes are flashing red and blue but they are blank. I have not been able to find a QSO that does not have an end time.

+ To what does "the upper boxes" refer? Which items have their labels flashing in red or blue font?

73,

Dave, AA6YQ


Re: LOTW upload first time

Ted Boerkamp
 

Hi Dave.....this "No matching QSO in log" error has me stumped. What is DXkeeper comparing my uploaded Qs to?
You say any discrepancy will cause this but that could mean anything!! How am I supposed to know what
has mismatched on 88 Qs??? I have printed off the list of calls and started looking at what I logged.
I cant see anything that I missed or could be interpreted as wrong. One of the Qs I actually confirmed with a qsl card
and the data on the card I received matches my log exactly!!! If my start time is logged a minute off what
the other guy uploaded, is this grounds for this error to pop up??
Why did LOTW report this group of 88 errors (87 no matches error) from my first upload while I was trying to sync the
Second batch I uploaded with my second callsign?
What filter or SQL do I need to get the list of 88 errors appearing on my log screen again?
Thank you for your help..it is appreciated. I am not sure where to look next.
Regards

Ted VE3SS

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ
Sent: Wednesday, October 14, 2020 8:23 PM
To: DXLab@groups.io
Subject: Re: [DXLab] LOTW upload first time

+ AA6YQ comments below

Hi Dave and Ian, Just submitted my second batch of logs using my second call VE3TJB (540 Qsos) Upload was perfect again. After sync lotw qsos I now got message 626 Qsos processed (How come that many?)

+ "Sync LoTW QSOs" reports all QSO reported by LoTW as "accepted" since the last time you invoked "Sync LoTW QSOs".

And 539 log entries updated and 88 errors.

I have 1 duplicate qso in log (my fault!)..the rest all from the VE3NKZ group (first group I submitted yesterday) And they all say "no matching QSO in log".....this error is not listed in the link page you gave me to read So not sure what this means...can you please explain and let me know how I fix it.

+ "No matching QSO in log" is an error reported by DXKeeper, not LotW. DXKeeper expects that the information reported by LoTW for a QSO exact matches that QSO's information in your log; any discrepancy produces this error message. For example, if you submit a QSO to LoTW whose start time is 00:00:00 Z, then modified the logged QSO's start time to 00:00:01Z, and the invoke "Sync LoTW QSOs", the result will be "no matching QSO in log".

Should I fix these 88 errors and resubmit before hitting the sync lotw qsls button??

+ You should understand why LoTW is reporting information that doesn’t match your logged QSOs before proceeding. Pick one mismatch, and get to the bottom of it. That will likely explain the other 87.

73,

Dave, AA6YQ







--
This email has been checked for viruses by AVG.
https://www.avg.com

3341 - 3360 of 200099