Date   

Google Earth - DXView

Rien Aarden
 

Hello Dave,
 
I have the following problem with Google Earth and DXview
After I have installed Google Earth
I go to DXView and then to the config
Enable Google Earth and then the Sync button
then I get the message that an app on the PC needs to be opened to open Google Earth.
What can I do best to resolve this problem Dave?
Of course I have already uninstalled Google Earth several times
and on newly installed unfortunately the same message every time and Google Earth does not open immediately.
 
Thanks in advance for your help Dave grt
Rien, PA7RA


Re: Where to start?

Dave AA6YQ
 

+ AA6YQ comments below

AS Dave suggested I started with COMMANDER. I use WIN4Yaesu to control my FTdx5000.
I connected Commander to one of the WIN4 com0com ports. Since I know nothing abt DXKEEPER I connected LOGic 9 to another WIN4 com0com port. When I change the freq. on any of the 3 (WIN4, LOGic 9, or Commander) the others change also. Plus COMMANDER tells %of RF pwr.

I still have a lot of study of the COMMANDER to do.
I am a happy camper.

One Quick question.

Will DXLabs support using the Flex Tuning knob?

+ If SmartSDR is running, yes; if you don't have a Flex Signature radio, no.

+ Commander does support the Griffin Powermate:

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

73,

Dave, AA6YQ


Re: REALLY MESSED UP LOG

perry
 

I did make a back up and sent a reminder on my phone 2 back up every month .... thank you ever so much Dave !

 

From: Dave AA6YQ
Sent: February 10, 2020 6:57 PM
To: DXLab@groups.io
Subject: Re: [DXLab] REALLY MESSED UP LOG

 

+ AA6YQ comment below

 

its all back and correct!!

 

+ Good! Now be sure to make a backup at least once a week, and retain the last 4 backups. Configuration window, Log tab, Backup button.

 

+ And before even thinking about using the "Modify QSOs" panel, always make a backup on the spot.

 

          73,

 

                 Dave, AA6YQ

 

 

 

 

 


Re: REALLY MESSED UP LOG

Dave AA6YQ
 

+ AA6YQ comment below

its all back and correct!!

+ Good! Now be sure to make a backup at least once a week, and retain the last 4 backups. Configuration window, Log tab, Backup button.

+ And before even thinking about using the "Modify QSOs" panel, always make a backup on the spot.

73,

Dave, AA6YQ


Re: Where to start?

W8UV Phil
 

AS Dave suggested I started with COMMANDER. I use WIN4Yaesu to control my FTdx5000.
I connected Commander to one of the WIN4 com0com ports. Since I know nothing abt DXKEEPER 
I connected LOGic 9 to another WIN4 com0com port. When I change the freq. on any of the 3
(WIN4, LOGic 9, or Commander) the others change also. Plus COMMANDER tells %of RF pwr.
I still have a lot of study of the COMMANDER to do.
I am a happy camper.
One Quick question.
Will DXLabs support using the Flex Tuning  knob?
Phil  W8UV


Re: REALLY MESSED UP LOG

perry
 

THANK YOU THANK YOU EVER SO MUCH !!! thanks for fixing my mess you are the best Dave !!! its all back and correct!!


Re: Complicated (?) problem

Dave AA6YQ
 

+ AA6YQ comments below

I'm using the programs that came on the original CD - and updates to the microHam program that you alerted me to. I will send you all my version(s) information separately, Joe. I can't believe this is anything other than "my own" problem, or microHam users would have been vocal long ago! It's got to be something (nearly) specific to me.... BUT (huge "but" or extra "t" in my case) I DO have another virtual port program installed..... Let me see what killing that does

+ I recommend killing and disabling the other virtual port program and then rebooting Windows.

73,

Dave, AA6YQ


Re: Complicated (?) problem

Steve - N3SL
 

I'm using the programs that came on the original CD - and updates to the microHam program that you alerted me to.  I will send you all my version(s) information separately, Joe.  I can't believe this is anything other than "my own" problem, or microHam users would have been vocal long ago!  It's got to be something (nearly) specific to me....  BUT (huge "but" or extra "t" in my case) I DO have another virtual port program installed..... Let me see what killing that does!  Didn't even dawn on me, as everything is A-OK under v1803....

Thanks

On Mon, Feb 10, 2020 at 5:02 PM Joe Subich, W4TV <lists@...> wrote:

 > So without all the gory details, just this:  Anyone using the microHam
 > box/software successfully beyond Win10 v1803?

Yes, I and many other users are running on Win 10 1909 without issue.

 > I get error messages that the ports have not been created
 > (while the microHam program communicates with the radio just fine!).

You may have an antivirus program interfering with the Eltima VSPAX
drivers used to create the virtual ports or another virtual serial
port package causing issues.  Are you trying to use another virtual
port package?

73,

    ... Joe, W4TV


On 2020-02-10 4:39 PM, Steve - N3SL wrote:
> Will try here with a "simple" question to see if I get a hit:
>
> I run the "original" microHam keyer and router software (virtual ports).
> Have for years, without problems.  Any Win10 upgrade beyond v1803 has the
> router software still seeing my radio, but none of the programs using the
> virtual ports (Commander, WSJT-X, MMTTY) can read radio status, key the
> rig, etc. and I get error messages that the ports have not been created
> (while the microHam program communicates with the radio just fine!).
>
> So without all the gory details, just this:  Anyone using the microHam
> box/software successfully beyond Win10 v1803?  If so, we can take this
> "offline" for more discussion. (Yes, I've been to microHam support.)
>
> Otherwise, the current setup works just fine, and I'm done updating Win10!
>
> Thanks,
> Steve, N3SL
>





Re: DXComnander Logging VFO B

Dave AA6YQ
 

+ AA6YQ comments below

Was hitting the wrong tab. Your suggestion of the temp swap of VFO's works fine. Thanks.

+ Ah, you were clicking the XFC button instead of the "M x S" button; I'm glad it's working correctly.

+ Please post the resolution on the eHam forum; thanks!

73,

Dave, AA6YQ


Re: No one is more deserving ...

Dave AA6YQ
 

+ AA6YQ comments below

Congratulations, Dave! This award is so well-deserved!!

DXLab is superb, as is your helpful support to all of us out here using your great suite of programs!

+ Thanks, Mike!

73,

Dave, AA6YQ


Re: No one is more deserving ...

Dave AA6YQ
 

+ AA6YQ comments below

There is no way to thank Dave enough for all the work he does!

But I'll say THANK YOU DAVE anyway. He has spent a lot of time helping me with both direct answers and pointing out the right sections in the manual for even more info.

And the price never increases either!!!

+ Thanks, Ron!

73,

Dave, AA6YQ


Re: DXComnander Logging VFO B

Stuart - VK6MK
 

Was hitting the wrong tab.  Your suggestion of the temp swap of VFO's works fine.  Thanks.

Stuart VK6MK

On Mon, 10 Feb 2020 at 14:27, Dave AA6YQ <aa6yq@...> wrote:
I tried that and that would work however for me the VFO's swap for a split second then go back . Is there a setting to make the VFO's hold the swap and then manually swap after logging ?

+ I don’t have an FTDX-101MP, but the ops who helped me test Commander's support for the FTDX-101MP reported that its MxS button was working correctly. When I test it here (with no actual radio), clicking the "M x S" button causes Commander to send three CAT commands to the radio:

SV; - which directs the radio to swap VFOs

FA; - which directs the radio to report the (new) Main VFO frequency

MD0; - which directs the radio to report the (new) Main VFO mode


+ Please do the following:

1. set your radios Main VFO to 7005 in CW

2. set your radio's Sub VFO to 14200 in USB

3. on the General tab of Commander's Configuration window, check the "log debugging info" box

4. on Commander's Main window, click the VFO panel's "M x S" button

5. on the General tab of Commander's Configuration window, uncheck the "log debugging info" box

6. attach the errorlog.txt file from your Commander folder to an email message, and the message to me via

aa6yq (at) ambersoft.com


          73,

                Dave, AA6YQ








Re: No one is more deserving ...

Mike Flowers
 

Congratulations, Dave! This award is so well-deserved!!

DXLab is superb, as is your helpful support to all of us out here using your great suite of programs!

- 73 and good DX de Mike, K6MKF, NCDXC Secretary

-----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Peter Laws
Sent: Monday, February 10, 2020 07:00
To: DXLab@groups.io
Subject: [DXLab] No one is more deserving ...

http://www.arrl.org/news/view/arrl-board-grants-awards-and-recognitions

``The Board conferred the ARRL President’s Award on David H.
Bernstein, AA6YQ, in recognition of “exemplary, outstanding, and continuing
service” to ARRL and its members as part of the ARRL Logbook of The World
team. Bernstein was a charter member of the ARRL Logbook Committee and a
“founding, influential, and devoted member” of the Committee on
Communication with ARRL Members.''

Sincere congratulations, Dave.

73,
Peter


--
Peter Laws | N5UWY | plaws plaws net | Travel by Train!


Re: No one is more deserving ...

Ron KU7Y
 

There is no way to thank Dave enough for all the work he does!

But I'll say THANK YOU DAVE anyway. He has spent a lot of time helping me with both direct answers and pointing out the right sections in the manual for even more info.

And the price never increases either!!!

OK, back in my hole,

Ron, KU7Y
Mountain Home, ID DN23dc
CW Ops #1211
BUG USERS #189
SKCC #4904
QRP ARCI #8829
SOC #2
Idaho DX Association
Ron@...


Re: Winwarbler Keyboard CW problem

Jim Miller, AB3CV
 
Edited

Hi Dave

Both his K3 and my K3 are using the latest firmware. He has a K3 with a serial port. I have a K3s with a USB connection. I see the same behavior on both.

I'll do the debug test shortly.

Test performed and error.txt sent.

Thanks

Jim ab3cv


Re: No one is more deserving ...

Dave AA6YQ
 

+ AA6YQ comments below

Dave your going to have to build an additional "trophy room" when you keep getting these. Congrats on this recognition from the ARRL, for all your help.

+ Thanks, Danny!

73,

Dave, AA6YQ


Re: No one is more deserving ...

Dave AA6YQ
 

+ AA6YQ comments below

I m a long time (almost from the beginning) continuous user. I can attest that Dave has NEVER wavered in his dedication and support of this outstanding program.

Simply the BEST!

Congratulations Dave! Well deserved!

+ Thanks, Joe!

73,

Dave, AA6YQ


Re: Winwarbler Keyboard CW problem

Dave AA6YQ
 

+ AA6YQ comments below

All apps updated so using latest versions of all DXlabs modules.

I'm new to Winwarbler for CW and setting it up for a friend. I'm using XCVR CTRL App for interfacing to the K3.

I have Keyboard Mode panel set to Auto Start, Auto Stop and Character.

This seems to be the proper set of options desired by my friend who just wants it to ragchew as if he was using his paddle, i.e. each character sent in real time.

What I'm finding is that if start typing a sentence the sent stream heard in the monitor headphones as well on the K3 screen is only partially sent.

For example if I type a single character "o" it is correctly sent. If I type "oo" that is also correct. However if I type "what is going on" the "what" is often garbled sending at most a partial "w" (dit) and picking up with "going" and continuing correctly. It seems like hitting the space bar will cause an interruption in the stream as well.

+ In character mode, WinWarbler conveys text to be transmitted to Commander as it is entered, and Commander conveys the text to the K3; what happens after that is the K3's responsibility.

+ What version of K3 firmware is your friend running?

+ Is anyone else using WinWarbler for CW transmission with a K3 experiencing this sort of behavior?

+ Jim, when you have the opportunity, please do the following:

1. on the General tab of Commander's Main window, check the "log debugging info box"

2. with WinWarbler configured as you've described above, type "what is going on"

3. when transmission completes,

3a. on the General tab of Commander's Main window, uncheck the "log debugging info box"

3b. attach the errorlog.txt file from Commander's folder to an email message, and send the message to me via

aa6yq (at) ambersoft.com

73,

Dave. AA6YQ


Re: No one is more deserving ...

Danny Douglas <n7dc@...>
 

Dave your going to have to build an additional "trophy room" when you keep getting these. Congrats on this recognition from the ARRL, for all your help.


N7DC@...
Ex WN5QMX,WA5UKR,ET2US,ET3USA,SV0WPP,VS6DD,N7DC/YV5/G5CTB
QSL Bureau, DIRECT, LOTW Preferred, eQSL used but upload at a courtesy only, as do not use the system for awards.

On February 10, 2020 at 5:03 PM "Phil Cooper via Groups.Io" <pcooper@...> wrote:


Congratulations Dave!

A most deserved recipient, and not just “exemplary, outstanding, and continuing service” to ARRL and its members", but also to all us DXLab users too.

73 de Phil GU0SUP



-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Peter Laws
Sent: 10 February 2020 15:00
To: DXLab@groups.io
Subject: [DXLab] No one is more deserving ...

http://www.arrl.org/news/view/arrl-board-grants-awards-and-recognitions

``The Board conferred the ARRL President’s Award on David H.
Bernstein, AA6YQ, in recognition of “exemplary, outstanding, and
continuing service” to ARRL and its members as part of the ARRL
Logbook of The World team. Bernstein was a charter member of the ARRL
Logbook Committee and a “founding, influential, and devoted member” of
the Committee on Communication with ARRL Members.''

Sincere congratulations, Dave.

73,
Peter


--
Peter Laws | N5UWY | plaws plaws net | Travel by Train!






Re: Winwarbler Keyboard CW problem

Jim Miller, AB3CV
 

I never said I was using Winkey. I'm using XCVR control App, AKA Commander.

Jim

18461 - 18480 of 209549