Date   
SpotCollector: QSY to spot on VFOB?

Andy (KU7T)
 

Hi, 
I am using SpotCollector and Commander in SO2R mode. Commander shows both VFOs correctly. Is there a way to QSO from Spotcollector by mouse click and tell it which VFO to go to?  My scenario is that I am calling CQ on one band, but want to find spots on teh other radio. Doable?  If it matters, I am using Flex via TCP API,

Thanks
Andy
KU7T

Re: user defined slider values

Carl - WC4H
 

Sent you a zipped folder Ghassan.  Please read the note I wrote.

BTW,  when you see the buttons on Commander, there will be some in the "Alt" Section.

The buttons I use are:
Power On/Off
Tuner On
Tuner Tune
10w, 50w, 75w, 100w for quick changes
RF Pwr Slider for full control
AF Gain Slider
USB Mod Level Slider (helps control the ALC level in FT8)

On the ALT position (most of the ones that match the "Function Button on radio):
AGC (toggles F, M, S)
AN
NB
NR
Comp (on /off)
TBW (toggles 3 values)
Moni
IPO+(Off/On)

If you happen to access your PC remotely, you can ensure a value is in effect by cycling through.  That is, to make sure it's really on, turn of then on again.  That is because there's no way to capture the current value of most of these settings.

Lastly, the folder inlcudes more buttons that you may or may not want to use.

73.
Carl - WC4H


 

Re: user defined slider values

ghassan chammas
 

Thank you dave. Well noted.
Ghassan



Sent from Samsung tablet.

-------- Original message --------
From: Dave AA6YQ <aa6yq@...>
Date: 13/04/2019 00:14 (GMT+02:00)
To: DXLab@groups.io
Subject: Re: [DXLab] user defined slider values

+ AA6YQ comments below

I have programmed the first slider to alter the RF out, using the following parameters:

Lower b: 0
upper bound 255
small step :1
big step: 2
command : fefe940e140A0<D3>fd

it is functioning ok , but I need to improve on 2 issues:

1- the response to my click is very slow. if i click like 3 or 4 times on the arrow or inside the slider , it takes a few seconds to react and it varies the rf power very slowly.

+ I suggest setting "Big step" to 16, so you can more rapidly approach the desired level, and the home in with small steps.

+ Reducing the "Commander Interval", as has been suggested, will also help. See

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


2- Important for me: is there a way to READ the value of the RF i am asking for when i am clicking so as to know how much i am exciting my linear BEFORE i tx.

I can read RF out in commander , above the freq display but only when txing. can i know how much did i specify the RF power to be before I tx? (of course the radio, ic7300 will show me in discreet integer percentage, but this is not accurate enough for me.)

+ Commander does not continuously poll the radio to track its RF Power level. There are too many parameters to poll in this manner, and doing so would make frequency tracking less smooth.

+ However, if you set the Slider's "Label" parameter to

RF Pwr <value 100> w

+ as has been suggested, then the slider will show the last RF Power you set using the slider. If you only use the slider (as opposed to the radio's front panel) to set the RF Power, then then the value shown on the slider will be correct.

         73,

                 Dave, AA6YQ




Re: SpotCollector: QSY to spot on VFOB?

Dave AA6YQ
 

+ AA6YQ comments below

I am using SpotCollector and Commander in SO2R mode. Commander shows both VFOs correctly. Is there a way to QSO from Spotcollector by mouse click and tell it which VFO to go to? My scenario is that I am calling CQ on one band, but want to find spots on teh other radio. Doable? If it matters, I am using Flex via TCP API,

+ When Commander's primary transceiver is Flex 6XXX, Slice A is mapped to VFO A, and slice B is mapped to VFO B. In simplex, VFO A specified the RX/TX frequency. When split, VFO A specifies the RX frequency and VFO B specifies the TX frequency.

+ There is no way to use VFO B (Slice B) to specify the RX/TX frequency.

73,

Dave, AA6YQ

Re: mouse jumps around

Rob N1KEZ
 

I had the same problem. Also with a Palstar. It’s when Windows 10 recognizes it as a serial mouse and loads the drivers. Took me a while to fire out. Google disabling serial mouse to find how to do that in the registry. It’s easy once you know it. Every now and then it pops up again as a problem after updating Windows. 

Re: SpotCollector: QSY to spot on VFOB?

ART W2NRA
 

Hi Andy,

Why couldn’t you CQ on VFO B and work spots on VFO A?

73, Art, W2NRA

On Apr 12, 2019, at 9:40 PM, Andy (KU7T) <ku7t@...> wrote:

Hi, 
I am using SpotCollector and Commander in SO2R mode. Commander shows both VFOs correctly. Is there a way to QSO from Spotcollector by mouse click and tell it which VFO to go to?  My scenario is that I am calling CQ on one band, but want to find spots on teh other radio. Doable?  If it matters, I am using Flex via TCP API,

Thanks
Andy
KU7T

Re: SpotCollector: QSY to spot on VFOB?

Andy (KU7T)
 

I am trying to work one guy on VFO A, and would like to jump to another spot on VFO B (different band)

73
Andy
KU7T

Re: Upload to LOTW stopped

Dave AA6YQ
 

+ AA6YQ comments below

On Wed, Apr 10, 2019 at 01:37 PM, K9FD wrote:

Not quite sure when the upload to LOTW stopped working,  but was about the
time I upgraded TQSL to the latest version.  But I am not sure this is connected
or not.

I can go to the QSL screen,   Add Requested,  and the QSOs appear fine,  when I
click "Upload to LOTW" the TQSL screen pops up and the box "DXkeeper LOTW
Upload"  box appears and operation stalls at this point.  "waiting for TQSL
to complete processing"
I have to cancel the operation or it never completes

Everything has been working for more than a year,  this is the first time I have had
this problem.

Im sure its something where a setting has changed or i dumb thumbed some check
box.    If I try TQSL manually it will go to LOTW etc all works fine,  it also will sync
LOTW to DXK.    just the process of TQSL reading the DXK qsos tagged for upload
does not work.  Have cleared the upload,  rebooted,  etc

+ Merv K9FD's report above is the result of a defect in TQSL 2.4.5 that in some circumstances causes garbage characters to be written to the result file that DXKeeper inspects to determine if TQSL successfully completed an upload. TQSL developer Rick K1MU has sent a corrected version of TQSL to Merv and I that correctly reports its results. Expect a public release of the new TQSL version soon.

      73,

             Dave, AA6YQ

DXLab User Forum at the Visalia International DX Convention

Dave AA6YQ
 

The forum was held earlier today; as you can see, it was well attended:

<http://www.dxlabsuite.com/Visalia 2019/DXLab Forum Attendees.jpg>


My thanks to Björn SM7IUN and Dave W6DE for taking over at the last minute after illness made it impossible for me to attend:

<http://www.dxlabsuite.com/Visalia%202019/DXLab%20Forum%20Bjorn%20and%20Dave.jpg>

And thanks to Ron KF7ZN for serving as scribe during the session. Ron's notes will be published here.


Photo credit: Jim K1IR

73,

Dave, AA6YQ

Re: DXLab User Forum at the Visalia International DX Convention

Dave AA6YQ
 

The picture showing attendees is viewable via

<http://www.dxlabsuite.com/Visalia%202019/DXLab%20Forum%20Attendees.jpg>

73,

             Dave, AA6YQ

 

On Sat, Apr 13, 2019 at 06:29 PM, Dave AA6YQ wrote:

The forum was held earlier today; as you can see, it was well attended:

<http://www.dxlabsuite.com/Visalia 2019/DXLab Forum Attendees.jpg>


My thanks to Björn SM7IUN and Dave W6DE for taking over at the last minute after illness made it impossible for me to attend:

<http://www.dxlabsuite.com/Visalia%202019/DXLab%20Forum%20Bjorn%20and%20Dave.jpg>

And thanks to Ron KF7ZN for serving as scribe during the session. Ron's notes will be published here.


Photo credit: Jim K1IR

"Aged" LoTW indications

Steve - N3SL
 

This is certainly not a "critical" item (to me), but it appears the "maximum age" setting in the "controls" panel, Spot Collector, Spot Database tab has no effect - or "unexpected" effect.

I have it set to 12 months.  Several spots show up as "LoTW users" (via background color indication), but clearly are outside the 12-month limit as listed in the LoTW.mdb database (and in LoTW).  An example is XW3DT, which I worked in Feb, shows as LoTW user, but he hasn't uploaded since 2013.  The date of last upload listed in LoTW.mdb indeed is 2013.

I've gone through the help file, and everything appears to be setup correctly.  As I said, this is not a critical item, but wondering why it's (apparently) not working - or perhaps it's me....

Steve, N3SL

Re: "Aged" LoTW indications

Dave AA6YQ
 

+ AA6YQ comments below

On Sun, Apr 14, 2019 at 03:41 PM, Steve - N3SL wrote:

This is certainly not a "critical" item (to me), but it appears the "maximum age" setting in the "controls" panel, Spot Collector, Spot Database tab has no effect - or "unexpected" effect.
 
I have it set to 12 months.  Several spots show up as "LoTW users" (via background color indication), but clearly are outside the 12-month limit as listed in the LoTW.mdb database (and in LoTW).  An example is XW3DT, which I worked in Feb, shows as LoTW user, but he hasn't uploaded since 2013.  The date of last upload listed in LoTW.mdb indeed is 2013.
 
I've gone through the help file, and everything appears to be setup correctly.  As I said, this is not a critical item, but wondering why it's (apparently) not working - or perhaps it's me....

+ Did you direct SpotCollector to "Recompute" after changing the "Maximum age of last LotW upload" setting as specified in 

<https://www.dxlabsuite.com/spotcollector/Help/ConfigurationDatabase.htm#Maximum%20age%20of%20last%20LotW%20upload>

?

       73,

              Dave, AA6YQ

 

 

       73,

              Dave, AA6YQ

Re: "Aged" LoTW indications

Steve - N3SL
 

No, I didn't.  And the "12 month" setting has been that way for years.  

But, just did the recompute, and XW3DT still shows as a LoTW user.   Again, it's not critical.  Just curious, more than anything.

Steve

On Sun, Apr 14, 2019 at 6:06 PM Dave AA6YQ <aa6yq@...> wrote:

+ AA6YQ comments below

On Sun, Apr 14, 2019 at 03:41 PM, Steve - N3SL wrote:

This is certainly not a "critical" item (to me), but it appears the "maximum age" setting in the "controls" panel, Spot Collector, Spot Database tab has no effect - or "unexpected" effect.
 
I have it set to 12 months.  Several spots show up as "LoTW users" (via background color indication), but clearly are outside the 12-month limit as listed in the LoTW.mdb database (and in LoTW).  An example is XW3DT, which I worked in Feb, shows as LoTW user, but he hasn't uploaded since 2013.  The date of last upload listed in LoTW.mdb indeed is 2013.
 
I've gone through the help file, and everything appears to be setup correctly.  As I said, this is not a critical item, but wondering why it's (apparently) not working - or perhaps it's me....

+ Did you direct SpotCollector to "Recompute" after changing the "Maximum age of last LotW upload" setting as specified in 

<https://www.dxlabsuite.com/spotcollector/Help/ConfigurationDatabase.htm#Maximum%20age%20of%20last%20LotW%20upload>

?

       73,

              Dave, AA6YQ

 

 

       73,

              Dave, AA6YQ

Re: "Aged" LoTW indications

Dave AA6YQ
 

+ AA6YQ comments below

No, I didn't. And the "12 month" setting has been that way for years.

But, just did the recompute, and XW3DT still shows as a LoTW user. Again, it's not critical. Just curious, more than anything.

+ What background color appears in the Spot Database Entry for XW3DT?

+ In the "Background Colors" panel on the Configuration window's "Spot Database Display" tab, what colors are specified for Normal, LoTW, "eQSL AG" and "LoTW & eQSL AG"?

73,

Dave, AA6YQ

Re: "Aged" LoTW indications

Steve - N3SL
 

I have a light green for LoTW, and yellow for LoTW+eQSL.   XW3DT shows as light green.  The "normal" and "eQSL AG" are white.


On Sun, Apr 14, 2019 at 7:19 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

No, I didn't.  And the "12 month" setting has been that way for years. 

But, just did the recompute, and XW3DT still shows as a LoTW user.   Again, it's not critical.  Just curious, more than anything.

+ What background color appears in the Spot Database Entry for XW3DT?

+ In the "Background Colors" panel on the Configuration window's "Spot Database Display" tab, what colors are specified for Normal, LoTW, "eQSL AG" and "LoTW & eQSL AG"?

         73,

                Dave, AA6YQ





Re: "Aged" LoTW indications

Steve - N3SL
 

Maybe, I'm misleading you here, Dave.   The color is in DXKeeper.  XW3DT isn't being spotted now, so I can't comment on what would show there (without a bogus spot to tick off the world).  I have no idea what showed back in February when he was really spotted!  Is that what I'm missing?


On Sun, Apr 14, 2019 at 7:19 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

No, I didn't.  And the "12 month" setting has been that way for years. 

But, just did the recompute, and XW3DT still shows as a LoTW user.   Again, it's not critical.  Just curious, more than anything.

+ What background color appears in the Spot Database Entry for XW3DT?

+ In the "Background Colors" panel on the Configuration window's "Spot Database Display" tab, what colors are specified for Normal, LoTW, "eQSL AG" and "LoTW & eQSL AG"?

         73,

                Dave, AA6YQ





Re: "Aged" LoTW indications

Dave AA6YQ
 

+ AA6YQ comments below

Maybe, I'm misleading you here, Dave. The color is in DXKeeper. XW3DT isn't being spotted now, so I can't comment on what would show there (without a bogus spot to tick off the world). I have no idea what showed back in February when he was really spotted! Is that what I'm missing?

+ The first sentence of your first post was

" This is certainly not a "critical" item (to me), but it appears the "maximum age" setting in the "controls" panel, Spot Collector, Spot Database tab has no effect - or "unexpected" effect."

+ Your first post did not mention DXKeeper.

+ In DXKeeper, a "Maximum age of most recent LoTW upload to be considered active" option is provided on the "QSL Configuration" window's LoTW tab. This setting is considered when logging a new QSO.

+ The background color used to display a logged QSO in DXKeeper's Log Page Display is governed by that QSO's "LoTW Member" item. This enables you to accurately record a 2011 QSO with XW3DT with its "LoTW Member" item set to 'Y', while logging new XW3DT QSOs with their "LoTW Member" set to 'N'.

+ If a logged QSO with XW3DT has its "LoTW Member" item erroneously set to 'Y',

1. select the QSO's entry in the Log Page Display

2. change the "LoTW Member" item selector to 'N'

3. click the Save button

73,

Dave, AA6YQ

Re: "Aged" LoTW indications

Steve - N3SL
 

Wow!  Don't know that I'd ever been to that tab since "set up" years ago!   As you undoubtedly knew, the "aged" box was blank.
Sorry for all the bandwidth and your time chasing this.

As always, THANK YOU for the assistance!

73,
Steve

On Sun, Apr 14, 2019 at 7:55 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

Maybe, I'm misleading you here, Dave.   The color is in DXKeeper.  XW3DT isn't being spotted now, so I can't comment on what would show there (without a bogus spot to tick off the world).  I have no idea what showed back in February when he was really spotted!  Is that what I'm missing?

+ The first sentence of your first post was

" This is certainly not a "critical" item (to me), but it appears the "maximum age" setting in the "controls" panel, Spot Collector, Spot Database tab has no effect - or "unexpected" effect."

+ Your first post did not mention DXKeeper.

+ In DXKeeper, a "Maximum age of most recent LoTW upload to be considered active" option is provided on the "QSL Configuration" window's LoTW tab. This setting is considered when logging a new QSO.

+ The background color used to display a logged QSO in DXKeeper's Log Page Display is governed by that QSO's "LoTW Member" item. This enables you to accurately record a 2011 QSO with XW3DT with its "LoTW Member" item set to 'Y', while logging new XW3DT QSOs with their "LoTW Member" set to 'N'.

+ If a logged QSO with XW3DT has its "LoTW Member" item erroneously set to 'Y',

1. select the QSO's entry in the Log Page Display

2. change the "LoTW Member" item selector to 'N'

3. click the Save button

    73,

           Dave, AA6YQ





updated eQSL AG and LoTW databases are available...

Dave AA6YQ
 

...via the Databases tab of DXView's Configuration window.

73,

Dave, AA6YQ

Smart SDR 3.0.1.9 loaded but WSJT-X stopped receiving

K4PX K4PX
 

So my Flex 6400+Maestro was working great on FT8 with WSJT-X until I loaded Smart SDR 3.0.1.9 and now it will not receive.  I did not change anything.  I can hear the audio and WSJT-X is not reporting anything on the 0 dB-80 dB vertical scale.  I am using DX Labs.  Any ideas?  Thank you!