Date   

Re: importing adif from RumlogNG to Dxkeeper

Dave AA6YQ
 

I can't seem to upload the adif file that contains the 2 test calls

+ Please open the ADIF file with a text editor (e.g. Notepad), copy the text representing a single ADIF record, and post that text here.

73,

Dave, AA6YQ


Re: importing adif from RumlogNG to Dxkeeper

Steve
 

I can't seem to upload the adif file that contains the 2 test calls


Re: Skimmer Spots Overwriting SOTA Spots

Dave AA6YQ
 

@ AA6YQ comments below

When there isn't much DX to chase I like to chase SOTA activators. I have cluster.sota.org.uk set as a spot source along with VE7CC. I only accept Skimmer spots from WA, OR, ID, and BC and I do so to see DX stations that show up on Skimmer before someone from NA-W spots them. I understand how SC combines spots given the time and frequency settings. When I get a spot from the SOTA cluster it shows up in a filter I have based on the Network item.

+ A Spot Database Entry's Network field contains the name of the spot source that most recently contributed information to that Entry. Why does your filter reference this field?

**I was looking for a way to distinguish SOTA spots. There is a telnet link to SOTA spots and I was using the network name for that link. However, I understand why that was the wrong way to do it.

+ What is the objective of your filter?

**The objective of my filter was to isolate SOTA spots from other spots when I just want to chase SOTA . I also jump between a SOTA filter and a Needed DX filter to watch what is going on.

However, if a Skimmer spot comes in for the same station via VE7CC, the SOTA spot is overwritten and the SOTA spot disappears from my filter.

+ Information from a new spot is added to existing information; "over-writing" only occurs when a subsequent spot contains updated information, e.g. a new QSX frequency or a (hopefully) corrected grid square.

** Realizing that the Notes fields are not overwritten but additive I created a different filter using "Notes Like "?#*/*" AND <AGEFILTER> AND <MODEFILTER>" which seems to be doing a good job of isolating the SOTA spots with summit information from RBN spots.

@ SpotCollector recognizes SOTA tags in spot notes, extracts them, and places them in each Spot Database Entry's SOTA field. You can make this field visible in the Spot Database Display. To see all Entries that specify a SOTA tag, you can use

LEN(SOTA)>0

@ instead of

Notes Like "?#*/*"

@ You can use the SOTA field to assemble a "SOTA Need" filter, e.g.

SOTA in ('W7A/CS-014', 'GM/CS-121',' GW/SW-016')

@ Similar support is provided for POTA and WWFF.

73,

Dave, AA6YQ


Re: Skimmer Spots Overwriting SOTA Spots

 

On Sun, Nov 21, 2021 at 11:47 AM, Dave AA6YQ wrote:
**AF9W comments below:
+ AA6YQ comments below

When there isn't much DX to chase I like to chase SOTA activators. I have cluster.sota.org.uk set as a spot source along with VE7CC. I only accept Skimmer spots from WA, OR, ID, and BC and I do so to see DX stations that show up on Skimmer before someone from NA-W spots them. I understand how SC combines spots given the time and frequency settings. When I get a spot from the SOTA cluster it shows up in a filter I have based on the Network item.

+ A Spot Database Entry's Network field contains the name of the spot source that most recently contributed information to that Entry. Why does your filter reference this field?
**I was looking for a way to distinguish SOTA spots.  There is a telnet link to SOTA spots and I was using the network name for that link.  However, I understand why that was the wrong way to do it.  
+ What is the objective of your filter?
**The objective of my filter was to isolate SOTA spots from other spots when I just want to chase SOTA .  I also jump between a SOTA filter and a Needed DX filter to watch what is going on.  
However, if a Skimmer spot comes in for the same station via VE7CC, the SOTA spot is overwritten and the SOTA spot disappears from my filter.

+ Information from a new spot is added to existing information; "over-writing" only occurs when a subsequent spot contains updated information, e.g. a new QSX frequency or a (hopefully) corrected grid square.
** Realizing that the Notes fields are not overwritten but additive I created a different filter using "Notes Like "?#*/*" AND <AGEFILTER> AND <MODEFILTER>" which seems to be doing a good job of isolating the SOTA spots with summit information from RBN spots.  

** All is good now.  I really love your software, it is amazing.  I learn something new every time I use it.  

73,

Dave, AA6YQ

 
--
Bob AF9W
DXLab user since 2011


Re: importing adif from RumlogNG to Dxkeeper

Dave AA6YQ
 

+ AA6YQ comments below

I am experimenting with importing adif file from my iPad using RumlogNG . I am going to us this for Pota. the issue that I am having, I have both Dxkeeper userDefine 0 and Rumlog user defined 1 setup for Pota. when I import the adif file in to DXkeeper I can't find the pota info from rum log. I have checked the file with ADIF master and it is there but how do I get the info into to the user defined #.

+ Please post an example of an ADIF record exported by RumlogNG that specifies a POTA code.

73,

Dave, AA6YQ


importing adif from RumlogNG to Dxkeeper

Steve
 

I am experimenting with importing adif file from my iPad using RumlogNG . I am going to us this for Pota. the issue that I am having, I have both Dxkeeper userDefine 0 and Rumlog user defined 1 setup for Pota. when I import the adif file in to DXkeeper I can't find the pota info from rum log. I have checked the  file with ADIF master and it is there but how do I get the info into to the user defined #. I have been away for the radio for a couple of years, so getting my head back in the software.. lol

Thanks Steve VE1SK


Re: Skimmer Spots Overwriting SOTA Spots

Dave AA6YQ
 

+ AA6YQ comments below

When there isn't much DX to chase I like to chase SOTA activators. I have cluster.sota.org.uk set as a spot source along with VE7CC. I only accept Skimmer spots from WA, OR, ID, and BC and I do so to see DX stations that show up on Skimmer before someone from NA-W spots them. I understand how SC combines spots given the time and frequency settings. When I get a spot from the SOTA cluster it shows up in a filter I have based on the Network item.

+ A Spot Database Entry's Network field contains the name of the spot source that most recently contributed information to that Entry. Why does your filter reference this field?

+ What is the objective of your filter?

However, if a Skimmer spot comes in for the same station via VE7CC, the SOTA spot is overwritten and the SOTA spot disappears from my filter.

+ Information from a new spot is added to existing information; "over-writing" only occurs when a subsequent spot contains updated information, e.g. a new QSX frequency or a (hopefully) corrected grid square.

73,

Dave, AA6YQ


Skimmer Spots Overwriting SOTA Spots

 

When there isn't much DX to chase I like to chase SOTA activators.  I have cluster.sota.org.uk set as a spot source along with VE7CC.  I only accept Skimmer spots from WA, OR, ID, and BC and I do so to see DX stations that show up on Skimmer before someone from NA-W spots them.  I understand how SC combines spots given the time and frequency settings.  When I get a spot from the SOTA cluster it shows up in a filter I have based on the Network item.  However, if a Skimmer spot comes in for the same station via VE7CC, the SOTA spot is overwritten and the SOTA spot disappears from my filter.  I understand that this is the way SC is designed to work.  Does it make any sense to be able to prioritize Spot Sources or to have special handling for Skimmer spots so they don't overwrite spots from other sources?  

I don't consider the situation to be a problem.  It would just make my operating simpler. 
--
Bob AF9W
DXLab user since 2011


Re: Q65 Spotcolletor

Dave AA6YQ
 

* more AA6YQ comments below

Setup Win7 WSJT-X 2.5.2 (running 2 instances) DXKeeper, DXView, and Spotcolletor.
One instance was running 6M FT8 the other 2M Q65-60A trying to see if I could decode EME during the contest this weekend. I was tuned to a local station frequency on Q65 but Spotcolletor was showing it as QRA64. Of course I didn't try to log it to see if it was logging correctly or not.

+ If the Spot Database Entry was created by one of your WSJT-X instances, then that instance reported the mode as QRA64. That said, I haven't yet updated SpotCollector to recognize the character that WSJT-X reports for Q65; I'll do that in the next version.

* Bill G4WJS informs me that Q65 supersedes QRA64. Thus when the current version of SpotCollector reports QRA64, the mode is actually Q65. This has been corrected in the next version of SpotCollector.

73,

Dave, AA6YQ


Re: Q65 Spotcolletor

Dave AA6YQ
 

+ AA6YQ comments below

Setup Win7 WSJT-X 2.5.2 (running 2 instances) DXKeeper, DXView, and Spotcolletor.
One instance was running 6M FT8 the other 2M Q65-60A trying to see if I could decode EME during the contest this weekend. I was tuned to a local station frequency on Q65 but Spotcolletor was showing it as QRA64. Of course I didn't try to log it to see if it was logging correctly or not.

+ If the Spot Database Entry was created by one of your WSJT-X instances, then that instance reported the mode as QRA64. That said, I haven't yet updated SpotCollector to recognize the character that WSJT-X reports for Q65; I'll do that in the next version.

Just thought I'd let ya know.

+ Thanks! I meant to try 6M EME when my friend Lance W7GJ was QRV from the South Pacific, but higher priorities intervened...

73,

Dave, AA6YQ


Q65 Spotcolletor

N2XK Fred
 

Hello,
Setup Win7 WSJT-X 2.5.2 (running 2 instances) DXKeeper, DXView, and Spotcolletor.
One instance was running 6M FT8 the other 2M Q65-60A trying to see if I could decode EME during the contest this weekend. I was tuned to a local station frequency on Q65 but Spotcolletor was showing it as QRA64. Of course I didn't try to log it to see if it was logging correctly or not.
Just thought I'd let ya know.

Thanks,
Fred
N2XK


Re: Connect to VE7CC Cluster

Mike Daly
 

Perfect. Thank you.
Mike

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ
Sent: Sunday, November 21, 2021 0:38
To: DXLab@groups.io
Subject: Re: [DXLab] Connect to VE7CC Cluster

+ AA6YQ comments below

I am not able to connect to the VE7CC cluster. If I log into the cluster directly I get the output. But when connecting via Spot Collector, I get "Winsock Error# 11001- Authoritative answer: Host not found @ 11/21/2021 0018 In the Spot Source Host Address I have http://www.bcdxc.org/ve7cc/ I expect this is the wrong address.

+ Set the host address to ve7cc.net and set the port to 23

73,

Dave, AA6YQ


Re: Sending CW from WW to ICOM IC-7300 via CI-V

MARK KEMPISTY
 

Dave,

Thank you very much.  I definitely over thought it.  That is working exactly like my WinKeyer which I can now leave at home.

Mark 
AA3K


Re: Sending CW from WW to ICOM IC-7300 via CI-V

Dave AA6YQ
 

In my response below, I should have mentioned that after you have WinWarbler able to send text in CW via Commande,r you can then employ WinWarbler macros to send signal reports, etc. See

https://www.dxlabsuite.com/dxlabwiki/Macros

As noted in this article, macros can include "substitution commands", e.g. <rstsent> and <rstreceived> to send the report you've already recorded in the Main window's "QSO Info" panel. See

http://www.dxlabsuite.com/winwarbler/Help/Macros.htm

73,

Dave, AA6YQ

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ
Sent: Saturday, November 20, 2021 8:12 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Sending CW from WW to ICOM IC-7300 via CI-V

+ AA6YQ comments below

I am trying to write WinWarbler macros that send CI-V commands to Commander to have the IC-7300 send CW for me. I'm doing this because I want the 7300 to generate the CW freeing the tight timing off of the computer particularly when in the field doing POTA.

Currently, if I use the following WW macro <xcvrcommand: FEFE94E0173333FD> the 7300 immediately sends 33 (33 33 in the macro and I only have the ASCII values for 0 - 9 memorized, maybe I'm not the geek that I think I am). But when I execute the following <xcvrcommand: FEFE94E017><xcvrcommand: 'de AA3K TEST><xcvrcommand: FD> there is a 4 or 5 second delay before the 7300 sends the resulting CW. I would like to build up these macros to use <callsign>, <RSTsent> and possibly other macro commands but the delay has got me stumped. I do not see anything in the message history here that suggests a solution.

+ There's no need to send CI-V commands to your IC-7300 to direct it to send CW; WinWarbler can be configured to direct Commander to send text to your IC-7300 to be transmitted in CW. See item 5 in

https://www.dxlabsuite.com/dxlabwiki/CWConnection

+ If this doesn't get you going, please let me know.

73,

Dave, AA6YQ


Re: Sending CW from WW to ICOM IC-7300 via CI-V

Dave AA6YQ
 

+ AA6YQ comments below

I am trying to write WinWarbler macros that send CI-V commands to Commander to have the IC-7300 send CW for me. I'm doing this because I want the 7300 to generate the CW freeing the tight timing off of the computer particularly when in the field doing POTA.

Currently, if I use the following WW macro <xcvrcommand: FEFE94E0173333FD> the 7300 immediately sends 33 (33 33 in the macro and I only have the ASCII values for 0 - 9 memorized, maybe I'm not the geek that I think I am). But when I execute the following <xcvrcommand: FEFE94E017><xcvrcommand: 'de AA3K TEST><xcvrcommand: FD> there is a 4 or 5 second delay before the 7300 sends the resulting CW. I would like to build up these macros to use <callsign>, <RSTsent> and possibly other macro commands but the delay has got me stumped. I do not see anything in the message history here that suggests a solution.

+ There's no need to send CI-V commands to your IC-7300 to direct it to send CW; WinWarbler can be configured to direct Commander to send text to your IC-7300 to be transmitted in CW. See item 5 in

https://www.dxlabsuite.com/dxlabwiki/CWConnection

+ If this doesn't get you going, please let me know.

73,

Dave, AA6YQ


Sending CW from WW to ICOM IC-7300 via CI-V

MARK KEMPISTY
 

I am trying to write WinWarbler macros that send CI-V commands to Commander to have the IC-7300 send CW for me.  I'm doing this because I want the 7300 to generate the CW freeing the tight timing off of the computer particularly when in the field doing POTA.  

Currently, if I use the following WW macro <xcvrcommand: FEFE94E0173333FD> the 7300 immediately sends 33 (33 33 in the macro and I only have the ASCII values for 0 - 9 memorized, maybe I'm not the geek that I think I am).  But when I execute the following <xcvrcommand: FEFE94E017><xcvrcommand: 'de AA3K TEST><xcvrcommand: FD> there is a 4 or 5 second delay before the 7300 sends the resulting CW.  I would like to build up these macros to use <callsign>, <RSTsent> and possibly other macro commands but the delay has got me stumped.  I do not see anything in the message history here that suggests a solution.

Thanks in advance for any help.


Re: Can't update to TQSL 2.5.9

John W1JA
 

FB Neil. For some reason I interpreted the Revo website language to mean that the program would no longer function after one year. I'm considering buying it while it's on sale.

About my TQSL issue: Rick K1MU contacted me by email. He suggested I use the Microsoft "Program Install and Uninstall troubleshooter." It successfully deleted my existing TQSL version, and I installed 2.5.9 with the tqsl-2.5.9.msi installer I downloaded from the LotW website.

73, John W1JA


Re: Connect to VE7CC Cluster

Dave AA6YQ
 

+ AA6YQ comments below

I am not able to connect to the VE7CC cluster. If I log into the cluster directly I get the output. But when connecting via Spot Collector, I get "Winsock Error# 11001- Authoritative answer: Host not found @ 11/21/2021 0018
In the Spot Source Host Address I have http://www.bcdxc.org/ve7cc/
I expect this is the wrong address.

+ Set the host address to ve7cc.net and set the port to 23

73,

Dave, AA6YQ


Connect to VE7CC Cluster

Mike Daly
 

Dave,
I am not able to connect to the VE7CC cluster. If I log into the cluster directly I get the output. But when connecting via Spot Collector, I get "Winsock Error# 11001- Authoritative answer: Host not found @ 11/21/2021 0018
In the Spot Source Host Address I have http://www.bcdxc.org/ve7cc/
I expect this is the wrong address.
Thanks in advance.
Cordially,
Mike, n5sj


Re: jtalert not logging to dxkeeper

Kurt Cathcart
 

Here is what it looks like:


286    7.817274    127.0.0.1    127.0.0.1    UDP    156    52979 → 2237 Len=124

287    7.817347    127.0.0.1    127.0.0.1    ICMP    184 Destination unreachable (Port unreachable)


Not sure why this is happening but I'll ping the WSJT-X guys.


-Kurt, KR2C

On 11/20/2021 4:43 PM, Dave AA6YQ wrote:
+ AA6YQ comments below

OK, Thank you. I was thinking that the problem was between jtalert and DXK.

+ There could be a problem between JT-Alert and DXKeeper, but if JT-Alert isn't interoperating with WSJT-X, JT-Alert will have nothing for DXKeeper to log.

+ Start upstream, and proceed downstream step-by-step:

WSJT-X => JT-Alert => DXKeeper

73,

Dave, AA6YQ





5761 - 5780 of 210264