Date   

Re: Outgoing spot

Dave AA6YQ
 

+ AA6YQ comments below

Thanks Dave.

As i wrote < a spot coming up in SC > i mean the "notes" box in the incoming spot i see in SC.

Yesterday i did sent a spot for OT4V, writing in the "notes box" of the outgoing spot <clustertest, ignore>.

In the incoming spot in SC, this notes where also shown: <clustertest,
ignore>

Maybe you can test it also sending a spot for OT4A, mentioning <clustertest, ignore> or else?

Hope you'll find the error.

+ Eddie, when you click the "Outgoing spot" panel's Cluster button, SpotCollector sends out the spot notes specified in that panel's Notes box, unless the Notes box is empty; if the Notes box is empty and you're operating in RTTY, then the outgoing spot notes specify "RTTY".

+ Anything else added by the cluster network.

73,

Dave, AA6YQ


Re: Wrong qrz call

Pete Smith
 

I've seen a number of people whose QRZ data are screwed up.  In some instances it's the physical location... one guy who withheld his mailing address discovered that QRZ mapped him to his manager's location.  mine was just a bit off, so I tweaked it manually.

73, Pete N4ZR
Check out the new Reverse Beacon Network
web server at <http://beta.reversebeacon.net>.
For spots, please use your favorite 
"retail" DX cluster.
On 2/11/2021 11:02 AM, Dave Tucker Nu4N wrote:

I work a lot of POTA stns. When I entered there call to be logged, several stns don't have the correct qrz info.
I dont know if its DXLAB or QRZ ??
Any thoughts??
Tnx
--
73's de NU4N Dave


Wrong qrz call

Dave Tucker Nu4N <dwtucker19@...>
 

I work a lot of POTA stns. When I entered there call to be logged, several stns don't have the correct qrz info.
I dont know if its DXLAB or QRZ ??
Any thoughts??
Tnx
--
73's de NU4N Dave


Re: Outgoing spot

eddy on5jk
 

Thanks Dave.

As i wrote < a spot coming up in SC > i mean the "notes" box in the incoming spot i see in SC.

Yesterday i did sent a spot for OT4V, writing in the "notes box" of the outgoing spot <clustertest, ignore>.

In the incoming spot in SC, this notes where also shown: <clustertest, ignore>

Maybe you can test it also sending a spot for OT4A, mentioning <clustertest, ignore> or else?

Hope you'll find the error.

Eddy ON5JK

Op 11/02/2021 om 2:42 schreef Dave AA6YQ:

+ AA6YQ comments,below

Dave i am sorry for digging deeper.

+ There's no reason to apologize, Eddy. Responding to questions about how and why things work the way they do is one of the reasons this group exists.


A spot coming up in SC, for OT4A, shows QRA locator <<JO32>> in the "notes" box.

+ By the "notes" box, are you referencing the "Notes" textbox in the "Outgoing spot" panel at the top of Spotcollector's Main window?

+ If yes, what actions are you taking that result in the "Notes" box being populated? Do you have any logged QSOs with OT4A? Is so, what gridsquare do they specify?

+ If no, to what "notes" box are you referring?

73,

Dave, AA6YQ





Re: Yaesu rotor control stops working, locks up DXView

Dave AA6YQ
 

+ AA6YQ comments below

Hygain Rotor Controller with ERC Version 4 SMD USB interface, All USB ports are not set for energy savings....so they never turn off....

+ Then I recommend two next steps:

1. check the Windows Event Logs for indications of hardware or software failures around the time when the lockups occurred.

2. reboot Windows into "Safe Mode with Networking"; do the lockups still occur?

73,

Dave, AA6YQ


Re: How does DXKeeper figure out zones

Dave AA6YQ
 

+ AA6YQ comments below

I have a bunch of QSOs with W1UU in my log. Recently DXKeeper put W1UU in itu zone 6 but he's in MA, itu zone 8. How does DXK
determine the zone for a station entered via the N1MM-DXKeeper gateway?

+ When I type W1UU into DXView and strike the Enter key, its Main window reports that according to the installed USAP database,
this station is in Massachusetts, ITU zone 8. W1UU's entry in QRZ specifies the same location information. That leaves "the most
recent logged QSO with W1UU specifies ITU zone 6" (with DXKeeper configured to lookup previous QSOs when logging a new QSO) as the
likeliest explanation.

+ How is the Capture window's ITU box populated if you type W1UU in its Call box and strike the Enter or Tab key?

73,

Dave, AA6YQ


Re: Outgoing spot

Dave AA6YQ
 

+ AA6YQ comments,below

Dave i am sorry for digging deeper.

+ There's no reason to apologize, Eddy. Responding to questions about how and why things work the way they do is one of the reasons this group exists.


A spot coming up in SC, for OT4A, shows QRA locator <<JO32>> in the "notes" box.

+ By the "notes" box, are you referencing the "Notes" textbox in the "Outgoing spot" panel at the top of Spotcollector's Main window?

+ If yes, what actions are you taking that result in the "Notes" box being populated? Do you have any logged QSOs with OT4A? Is so, what gridsquare do they specify?

+ If no, to what "notes" box are you referring?

73,

Dave, AA6YQ


Re: Yaesu rotor control stops working, locks up DXView

Dave AA6YQ
 

+ AA6YQ comments below

The add-on controller is new to me, but it has a standalone config utility. Before I changed the DXV config rotor settings from Yaesu to HyGain I used the standalone utility to change the protocol from something called RS232G (IIRC) to DCU-1.

The utility help file said that would use a subset of the DCU-1 protocol.

At any rate, that is what I think, but I'm not yet familiar enough with it to be confident about what caused what behavior.

+ In this case, at least, all's well that ends well.

73,

Dave, AA6YQ


Re: Yaesu rotor control stops working, locks up DXView

Tim Vandagriff
 

Hygain Rotor Controller with ERC Version 4 SMD USB interface,
All USB ports are not set for energy savings....so they never turn off....


How does DXKeeper figure out zones

Pete W1RM
 

I have a bunch of QSOs with W1UU in my log.  Recently DXKeeper put W1UU in itu zone 6 but he’s in MA, itu zone 8.  How does DXK determine the zone for a station entered via the N1MM-DXKeeper gateway?

 

 

Pete Chamalian, W1RM

W1rm@...

 


Re: Outgoing spot

eddy on5jk
 

Dave i am sorry for digging deeper.

A spot coming up in SC, for OT4A, shows QRA locator <<JO32>> in the "notes" box.

His station description on the cluster ON0DXK confirms the right QRAloc: --JO21sd--.

Also on QRZ.com the detals for OT4A says: --JO21sd--.

JO32 is outside of Belgium.

I do not know the way a spot is travelling, between the "spotter" (myselve), the cluster ON0DXK, maybe VE7CC,

and finally SC.

What is going wrong and where Dave?

Thanks

Eddy ON5JK

Op 30/01/2021 om 16:59 schreef Dave AA6YQ:

+ AA6YQ comments below
In every spot i am sending, i see that tere's always "JO21" at the end of the spot notes.

Sometimes i see spots from other stations with their QRA-locator on the end, sometimes there is not.

Is there a place to select when sending a spot, with the locator or not?
+The cluster node you're using to convey outgoing spots is doing that, not SpotCollector.
How many caracters a spot note can contain as a maximum?

+ 29 characters.

       73,

             Dave, AA6YQ

 


Re: Yaesu rotor control stops working, locks up DXView

Chuck, WS1L
 

The add-on controller is new to me, but it has a standalone config utility.  Before I changed the DXV config rotor settings from Yaesu to HyGain I used the standalone utility to change the protocol from something called RS232G (IIRC) to DCU-1.  

The utility help file said that would use a subset of the DCU-1 protocol.  

At any rate, that is what I think, but I'm not yet familiar enough with it to be confident about what caused what behavior.


73 de Chuck, WS1L



On Tue, Feb 9, 2021 at 2:57 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

It's only been 24 hours, but using the HyGain selection in DXView instead of the Yaesu one has it working for me without any problems.

+ The Hygain and Yaesu rotor control protocols are different: the command to rotate a Yaesu rotator to heading XXX is MXXX<13>, but the command to rotate a Hygain rotator is AP1XXX;

+ Unless you have a rotator controller that automatically accepts both protocols, I don't understand how they could both work.

       73,

              Dave, AA6YQ








Re: DK Keeper colors.

Dave Tucker Nu4N <dwtucker19@...>
 

Thanks much Lain  !!
--
73's de NU4N Dave


Re: Q65 Unrecognized mode when trying to upload to LOTW

D. Scott MacKenzie
 

Thank you

-----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Joe Subich, W4TV
Sent: Tuesday, February 9, 2021 7:30 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Q65 Unrecognized mode when trying to upload to LOTW


> What did I do wrong?

Nothing.

Q65 is still "beta" (WSJTX 2.4.0 is a RELEASE CANDIDATE).

LotW has not added Q65 to its list of supported modes and it has not been added to the tQSL config file. The ADIF standards group had not announced a standard for Q65 (probably Mode=MFSK, SubMode= Q65).

Before WSJTX 2.4.0 is ready for General Release, I'm sure all of the pieces will be in place. In the meantime, map your Q65 QSOs to the generic DATA mode if you *must* upload right now.

73,

... Joe, W4TV


On 2021-02-09 7:12 PM, D. Scott MacKenzie wrote:
Hi all:



I am trying to upload a Q65 mode contact to LOTW from DXKeeper. I get
an "unrecognized mode" error in the response from LOTW. I am using TQsl 2.5.7.
What did I do wrong?





Scott









Re: Q65 Unrecognized mode when trying to upload to LOTW

Joe Subich, W4TV
 

What did I do wrong?
Nothing.

Q65 is still "beta" (WSJTX 2.4.0 is a RELEASE CANDIDATE).

LotW has not added Q65 to its list of supported modes and it has
not been added to the tQSL config file. The ADIF standards group
had not announced a standard for Q65 (probably Mode=MFSK, SubMode= Q65).

Before WSJTX 2.4.0 is ready for General Release, I'm sure all of the
pieces will be in place. In the meantime, map your Q65 QSOs to the
generic DATA mode if you *must* upload right now.

73,

... Joe, W4TV


On 2021-02-09 7:12 PM, D. Scott MacKenzie wrote:
Hi all:
I am trying to upload a Q65 mode contact to LOTW from DXKeeper. I get an
"unrecognized mode" error in the response from LOTW. I am using TQsl 2.5.7.
What did I do wrong?
Scott


Fixed - RE: [DXLab] Q65 Unrecognized mode when trying to upload to LOTW

D. Scott MacKenzie
 

 

I figured it out – thank you

 

Kb0fhp

From: DXLab@groups.io <DXLab@groups.io> On Behalf Of D. Scott MacKenzie via groups.io
Sent: Tuesday, February 9, 2021 7:12 PM
To: DXLab@groups.io
Subject: [DXLab] Q65 Unrecognized mode when trying to upload to LOTW

 

Hi all:

 

I am trying to upload a Q65 mode contact to LOTW from DXKeeper.  I get an “unrecognized mode” error in the response from LOTW.  I am using TQsl 2.5.7.  What did I do wrong?

 

 

Scott

 


Q65 Unrecognized mode when trying to upload to LOTW

D. Scott MacKenzie
 

Hi all:

 

I am trying to upload a Q65 mode contact to LOTW from DXKeeper.  I get an “unrecognized mode” error in the response from LOTW.  I am using TQsl 2.5.7.  What did I do wrong?

 

 

Scott

 


Re: Exporting from DX4WIN to DXLab

w6de
 

You might also find some helpful information from these two article in the DXLab Wiki:

http://www.dxlabsuite.com/dxlabwiki/ManageMultipleQTHs

http://www.dxlabsuite.com/dxlabwiki/LotWMultipleCallsignsLocations

 

The DXLab WIKI has a lot of how-to-do-it articles.  You might bookmark the WIKI for future reference:

http://www.dxlabsuite.com/dxlabwiki/TitleIndex

Use the search box in the upper right corner.  Be imaginative with your searches, I found the above two articles by searching for à multiple ß

 

73,

Dave, w6de

 

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Saad Mahaini via groups.io
Sent: Monday, February 08, 2021 05:50
To: DXLab Reflector
Subject: [DXLab] Exporting from DX4WIN to DXLab

 

Hello Friends,

 

I've been getting my feet wet with DXLab over the last few months and got everything installed and working well now.

 

I have not yet moved my log, but i believe I'm ready for the final step and to make the move now

 

I read the instructions on importing the ADIF and i assume DX4WIN exporting the log to ADIF should be straight forward also

 

I have one log for Qs i made with two call signs and four different QTHs.  I also have another log with different call and QTH. 

 

Anything i should be aware of before i start the process? 

 

73 Saad N5FF

 

 

 


Re: DK Keeper colors.

iain macdonnell - N6ML
 

On Tue, Feb 9, 2021 at 2:29 PM Dave Tucker Nu4N <dwtucker19@comcast.net> wrote:

Dumb me I forgot what the colors represent in DXK . Like white,blue and yellow.
On the "Log" tab of DXKeeper's Configuration window, in the "Log Page
Display" panel, click the "Colors" button. The window that appears
will show your current assignments.

73,

~iain / N6ML


DK Keeper colors.

Dave Tucker Nu4N <dwtucker19@...>
 

Dumb me I forgot what the colors represent in DXK . Like white,blue and yellow.
73's
--
 Dave NU4N

4401 - 4420 of 204014