Date   

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






Re: jtalert not logging to dxkeeper

Dave AA6YQ
 

+ 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


Re: jtalert not logging to dxkeeper

Kurt Cathcart
 

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


I'll see if I can remedy the wsjt to jtalert problem.


-Kurt, KR2C

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

This was all working before a hard drive crash. After a restore, it seems that all is working well except for the jtalert logging to dxkeeper.

No alerts seem to show up on jtalert and when I log a QSO in FT8, it seems nothing gets passed to dxkeeper.

+ When you're using JT-Alert, DXLab applications are relatively passive: they receive directives - like "lookup callsign" and "log QSO" from JT-Alert, and then execute them.

+ Focus first on getting JT-Alert to correctly interoperate with WSJT-X. When that's working, then configure JT-Alert to correctly interoperate - one at a time -- with DXKeeper, DXView, SpotCollector, and Pathfidner.

73,

Dave, AA6YQ





Re: Issue attempting to remove Duplicate QSO's - Program Error 3043

Joe Bales
 

Error Free with log on local drive.  I will leave the database in the local drive.  I work from home 95% of the time the past 2 years and don't plan to change that.  So, when actually in the office I will not be doing any remote hamming thus no need for the database to be in the cloud.  I have a Gigabit network with a Verizon Fiber connection.  so who knows what caused the error.  I will still look into your suggestions that you included in your first reply.  

thanks again


Re: Issue attempting to remove Duplicate QSO's - Program Error 3043

Dave AA6YQ
 

+ AA6YQ comments below
QSL on that Dave.  I will look into this and see if the same error occurred with the successful operation with log on local drive.  

+ If that were the case, there's be  "see errorlog" entry in DXKeeper's Main window's title bar, and there'd be an errorlog.txt file in your DXKeeper folder with entries whose timestamps are consistent with when you ran the duplication removal operation on a log file on your local drive.

    73,

            Dave, AA6YQ


Re: Issue attempting to remove Duplicate QSO's - Program Error 3043

Joe Bales
 

QSL on that Dave.  I will look into this and see if the same error occurred with the successful operation with log on local drive.  

Joe


Re: Can't update to TQSL 2.5.9

neil_zampella
 

FWIW ... all that means is that you won't be able to get any updates after 1 year, the program will still work.

Neil, KN3ILZ

On 11/20/2021 12:24 PM, John W1JA wrote:
Thanks Dave for calling in the big guns. I will wait for their responses.

Thanks Neil. I have been hearing about Revo for decades. I would have bought it on sale right now, just to have around. But the sale price is for just 1 year. :(  I have problems like this way less often than annually. I'll just use the free version if I need it.


Re: Can't update to TQSL 2.5.9

Dave AA6YQ
 

+ AA6YQ comments below

Thanks Dave for calling in the big guns. I will wait for their responses.

+ I’ve forwarded Rick K1MU’s response to you.

73,

Dave, AA6YQ


Re: Can't update to TQSL 2.5.9

John W1JA
 

Thanks Dave for calling in the big guns. I will wait for their responses.

Thanks Neil. I have been hearing about Revo for decades. I would have bought it on sale right now, just to have around. But the sale price is for just 1 year. :(  I have problems like this way less often than annually. I'll just use the free version if I need it.

5741 - 5760 of 210236