Date   

Re: Uploads to LOTA & EQSL #file

Dave AA6YQ
 

+ AA6YQ comments below
I entered my friends call. Did not show up in e-qsl nor lotw. What next.? I remember when I was using DX Keeper awhile ago it did the same thing. I was wondering why I was not getting Eqsl's or LOTW  qso's  confirmed..  Then I checked LOTW and seen they have never been uploaded. I waited for 30 minutes and tried to upload ago. NO GO.
Thanks.
+ Please answer my question: Have you ever successfully submitted QSOs from DXKeeper to eQSL or LoTW?

73,

Dave, AA6YQ


Re: WinWarbler Deja Vu

Jim Denneny
 

Joe, I don't recall any change.  Verified CONFIG - PTT is set for RTS.  I switch K3s from VOX to PTT. I have walked WW PTT ports from 5 through 10 with no PTT keying WW.  For test purposes, I select CALL button.  Call scrolls through the WW window but K3s does not key.

I have no problem running with winkeyer standalone with radio in VOX mode.  Unfortunately WW will not key radio in VOX mode but Winkeyer can key radio in VOX but not PTT.


Re: Uploads to LOTA & EQSL #file

 

I entered my friends call. Did not show up in e-qsl nor lotw. What next.? I remember when I was using DX Keeper awhile ago it did the same thing. I was wondering why I was not getting Eqsl's or LOTW  qso's  confirmed..  Then I checked LOTW and seen they have never been uploaded. I waited for 30 minutes and tried to upload ago. NO GO.
Thanks.


--
73's NU4N Dave


Re: Uploads to LOTA & EQSL #file

Dave AA6YQ
 

+ AA6YQ comments below

I just upload my call into DX Keeper about to e-qsl and lotw. I waited about 30 minutes and my call did not show up in either eqsl nor lotw.

+ One does not upload one's call to DXKeeper, nor would one expect one's call to show up in either eqsl nor lotw"

+ Have you ever successfully submitted QSOs from DXKeeper to eQSL or LoTW?

73,

Dave, AA6YQ


Uploads to LOTA & EQSL #file

 

I just upload my call into DX Keeper about to e-qsl and lotw.
I waited about 30 minutes and my call did not show up in either eqsl nor lotw.
My accounts are active.
Any suggestions?
Thanks
--
73's NU4N Dave


Re: WinWarbler Deja Vu

Joe Subich, W4TV
 

What did you change in your computer?

Reload the Workspace that you saved the last time WinWarbler was working
correctly. You did save a workspace as recommended in the documentation
- didn't you?

Set K3S Config PTT to DTR & RTS.
If you are using Config PTT - it can be *either* DTR *or* RTS. Determine
which one, set Commander's PRIMARY CAT SERIAL PORT for "TX" on DTR or
RTS as appropriate, Check the "Suppress CAT" box on Commander's Config
-> General tab and Configure WinWarbler for "Xcvr Ctrl App" on the PTT
tab in its Config Dialog.

When you get it working, *SAVE A WORKSPACE* so you can retrieve the
settings the next time you break it.

73,

... Joe, W4TV


On 2021-08-02 12:04 PM, Jim Denneny wrote:
Set K3S Config PTT to DTR & RTS.  VOX turned off. Ran through all com ports in WW Config.  No PTT.  It would be nice to use WW but it is not a big deal
Jim K7EG


Re: WinWarbler Deja Vu

Dave AA6YQ
 

+ AA6YQ comments below
Same problem here. Cycled through all com ports searching for PTT.  Switched K3S from VOX to PTT. Cannot key rig from WW..

+ There are 3 ways for WinWarbler to switch a K3 between RX and TX:

1. configure WinWarbler to use a serial port modem control signal that drives a level-conversion interface connected to the K3's "SEND" input

2. configure Commander to use a serial port modem control signal that drives a level-conversion interface connected to the K3's "SEND" input, and configure WinWarbler to use Commander for RX-TX switching

3. configure Commander to send CAT commands to the K3 for RX-TX switching, , and configure WinWarbler to use Commander for RX-TX switching

+ See "Switching a Transceiver between Reception and Transmission" in

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

 

73,

        Dave, AA6YQ

 

 

 

 


Re: WinWarbler Deja Vu

g4wjs
 

On 02/08/2021 17:20, Jim Denneny wrote:
Hi Bill. Sometimes.  What am I missing?
Hi Jim,

if Commander can key your rig then you should have WW defer to Commander for PTT "Xcvr Ctrl App" on the Config->PTT panel of WW.



--
73

Bill

G4WJS.


Re: WinWarbler Deja Vu

Jim Denneny
 

Hi Bill.  Sometimes.  What am I missing?


Re: WinWarbler Deja Vu

g4wjs
 

On 02/08/2021 17:04, Jim Denneny wrote:
Set K3S Config PTT to DTR & RTS.  VOX turned off. Ran through all com ports in WW Config.  No PTT.  It would be nice to use WW but it is not a big deal

Jim K7EG
Jim,

do you use Commander?



--
73

Bill

G4WJS.


Re: WinWarbler Deja Vu

Jim Denneny
 

Set K3S Config PTT to DTR & RTS.  VOX turned off. Ran through all com ports in WW Config.  No PTT.  It would be nice to use WW but it is not a big deal

Jim K7EG


WinWarbler Deja Vu

Jim Denneny
 

Same problem here. Cycled through all com ports searching for PTT.  Switched K3S from VOX to PTT. Cannot key rig from WW..

Jim K7EG


Re: Winwarbler #file

David Tucker <nu4ndave@...>
 

Sure will Thanks Dave !!

73 Dave NU4N

On 8/1/2021 11:43 AM, Dave AA6YQ wrote:
+ AA6YQ comments below
Thanks Dave I got it working. PTT com 5 I set to RTS.Now it transmits.

+ Good! Now that you have it working, save your settings to a Workspace so that you can easily restore them if you lose them in the future:

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

      73,

           Dave, AA6YQ

 


Re: Winwarbler #file

Dave AA6YQ
 

+ AA6YQ comments below
Thanks Dave I got it working. PTT com 5 I set to RTS.Now it transmits.

+ Good! Now that you have it working, save your settings to a Workspace so that you can easily restore them if you lose them in the future:

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

      73,

           Dave, AA6YQ

 


Re: Winwarbler #file

 

Thanks Dave I got it working. PTT com 5 I set to RTS.Now it transmits.
--
73's NU4N Dave


Re: Winwarbler #file

 

Yes signalink workes on FLDIGI. Rx yes Tx no
--
73's NU4N Dave


Re: SOLVED- Commander/SatPC32 integration issue

Dave Fugleberg
 

Yep that’s accurate, although I’m not sure whether the exact same runtime error is true for all versions of Windows or all versions of SatPC32. That was what my system reported though.
Thanks!

On Sat, Jul 31, 2021 at 8:49 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

OK, I figured out what was preventing me from successfully connecting to SatPC32 from Commander. I'm documenting my findings here in case it helps some poor soul in the future.

Note: This issue will NOT affect users who use only one account for everything in Windows 10 (likely the majority of hams).  It manifested because my (perfectly legitimate) user account strategy collided with some assumptions on the part of the author of SatPC32.


ORIGINAL ISSUE:
Commander would not connect to SatPC32 after configuring per the article in the wiki (https://www.dxlabsuite.com/dxlabwiki/SatelliteTracking).

SYMPTOM: In the SatPC32 panel of Commander, Clicking the Connect button had no effect. Status remained "Disconnected".

ROOT CAUSE:

Commander and SatPC32 running at different privilege levels - Commander as a normal user, and SatPC32 as an administrator.

Why? Because SatPC32 would not start unless I used the 'Run as administrator' option in the right-click context menu. Attempts to run the program without it yielded the error "runtime error 217 at 00673791".

Why?  Because SatPC32 could not find its configuration files.

Why? Because the installer placed the config files in the AppData  folder of the Administrator user account, which the application could not see if not running as  administrator.

Why? I have two accounts on this PC - let's call them User1 and User2. User1 is an administrator; User2 is a standard user.  I always log in as User2, and elevate privileges using User1 only as necessary. When installing applications, Windows prompts me for the password for User1.  However, the SatPC32 installer does not follow that convention, and requires one to run it as an administrator (install fails otherwise).
Following their instructions, I ran the installer using the 'Run as administrator' context menu, and provided the password for User1.  This causes the installer to install in the context of User1.

SOLUTION - The solution is actually in the SatPC32 FAQ - http://www.dk1tb.de/FAQ_e.htm#StandardUser
It involves copying the SatPC32 folder of config files from the AppData path of User1 to that of User2.  Now User2 can run the application as User2 without elevated rights.  Now Commander is able to connect to SatPC32 and obtain Sat name, mode, and uplink/downlink frequency, so DxKeeper can grab that when logging a QSO.

Thanks to all who provided suggestions - they eventually helped me track this down.

+ Nice work, Dave.

+ I added a new "Troubleshooting" section at the end of "Interoperating with the SatPC32 Satellite Tracking Application" in

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

+ Does it correctly describe the symptoms and their resolution?

        73,

                Dave, AA6YQ








Re: SOLVED- Commander/SatPC32 integration issue

Dave AA6YQ
 

+ AA6YQ comments below

OK, I figured out what was preventing me from successfully connecting to SatPC32 from Commander. I'm documenting my findings here in case it helps some poor soul in the future.

Note: This issue will NOT affect users who use only one account for everything in Windows 10 (likely the majority of hams). It manifested because my (perfectly legitimate) user account strategy collided with some assumptions on the part of the author of SatPC32.


ORIGINAL ISSUE:
Commander would not connect to SatPC32 after configuring per the article in the wiki (https://www.dxlabsuite.com/dxlabwiki/SatelliteTracking).

SYMPTOM: In the SatPC32 panel of Commander, Clicking the Connect button had no effect. Status remained "Disconnected".

ROOT CAUSE:

Commander and SatPC32 running at different privilege levels - Commander as a normal user, and SatPC32 as an administrator.

Why? Because SatPC32 would not start unless I used the 'Run as administrator' option in the right-click context menu. Attempts to run the program without it yielded the error "runtime error 217 at 00673791".

Why? Because SatPC32 could not find its configuration files.

Why? Because the installer placed the config files in the AppData folder of the Administrator user account, which the application could not see if not running as administrator.

Why? I have two accounts on this PC - let's call them User1 and User2. User1 is an administrator; User2 is a standard user. I always log in as User2, and elevate privileges using User1 only as necessary. When installing applications, Windows prompts me for the password for User1. However, the SatPC32 installer does not follow that convention, and requires one to run it as an administrator (install fails otherwise).
Following their instructions, I ran the installer using the 'Run as administrator' context menu, and provided the password for User1. This causes the installer to install in the context of User1.

SOLUTION - The solution is actually in the SatPC32 FAQ - http://www.dk1tb.de/FAQ_e.htm#StandardUser
It involves copying the SatPC32 folder of config files from the AppData path of User1 to that of User2. Now User2 can run the application as User2 without elevated rights. Now Commander is able to connect to SatPC32 and obtain Sat name, mode, and uplink/downlink frequency, so DxKeeper can grab that when logging a QSO.

Thanks to all who provided suggestions - they eventually helped me track this down.

+ Nice work, Dave.

+ I added a new "Troubleshooting" section at the end of "Interoperating with the SatPC32 Satellite Tracking Application" in

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

+ Does it correctly describe the symptoms and their resolution?

73,

Dave, AA6YQ


Re: SOLVED- Commander/SatPC32 integration issue

Bill Pence
 

Wow. Great troubleshooting!


On Sat, Jul 31, 2021, 8:23 PM Dave Fugleberg <davefugleberg@...> wrote:
OK, I figured out what was preventing me from successfully connecting to SatPC32 from Commander. I'm documenting my findings here in case it helps some poor soul in the future.

Note: This issue will NOT affect users who use only one account for everything in Windows 10 (likely the majority of hams).  It manifested because my (perfectly legitimate) user account strategy collided with some assumptions on the part of the author of SatPC32.

ORIGINAL ISSUE:
Commander would not connect to SatPC32 after configuring per the article in the wiki (https://www.dxlabsuite.com/dxlabwiki/SatelliteTracking).

SYMPTOM: In the SatPC32 panel of Commander, Clicking the Connect button had no effect. Status remained "Disconnected".

ROOT CAUSE:
Commander and SatPC32 running at different privilege levels - Commander as a normal user, and SatPC32 as an administrator.

Why? Because SatPC32 would not start unless I used the 'Run as administrator' option in the right-click context menu. Attempts to run the program without it yielded the error "runtime error 217 at 00673791".

Why?  Because SatPC32 could not find its configuration files.

Why? Because the installer placed the config files in the AppData  folder of the Administrator user account, which the application could not see if not running as  administrator.

Why? I have two accounts on this PC - let's call them User1 and User2. User1 is an administrator; User2 is a standard user.  I always log in as User2, and elevate privileges using User1 only as necessary. When installing applications, Windows prompts me for the password for User1.  However, the SatPC32 installer does not follow that convention, and requires one to run it as an administrator (install fails otherwise).
Following their instructions, I ran the installer using the 'Run as administrator' context menu, and provided the password for User1.  This causes the installer to install in the context of User1.

SOLUTION - The solution is actually in the SatPC32 FAQ - http://www.dk1tb.de/FAQ_e.htm#StandardUser
It involves copying the SatPC32 folder of config files from the AppData path of User1 to that of User2.  Now User2 can run the application as User2 without elevated rights.  Now Commander is able to connect to SatPC32 and obtain Sat name, mode, and uplink/downlink frequency, so DxKeeper can grab that when logging a QSO.

Thanks to all who provided suggestions - they eventually helped me track this down.

73 de W0ZF





SOLVED- Commander/SatPC32 integration issue

Dave Fugleberg
 

OK, I figured out what was preventing me from successfully connecting to SatPC32 from Commander. I'm documenting my findings here in case it helps some poor soul in the future.

Note: This issue will NOT affect users who use only one account for everything in Windows 10 (likely the majority of hams).  It manifested because my (perfectly legitimate) user account strategy collided with some assumptions on the part of the author of SatPC32.

ORIGINAL ISSUE:
Commander would not connect to SatPC32 after configuring per the article in the wiki (https://www.dxlabsuite.com/dxlabwiki/SatelliteTracking).

SYMPTOM: In the SatPC32 panel of Commander, Clicking the Connect button had no effect. Status remained "Disconnected".

ROOT CAUSE:
Commander and SatPC32 running at different privilege levels - Commander as a normal user, and SatPC32 as an administrator.

Why? Because SatPC32 would not start unless I used the 'Run as administrator' option in the right-click context menu. Attempts to run the program without it yielded the error "runtime error 217 at 00673791".

Why?  Because SatPC32 could not find its configuration files.

Why? Because the installer placed the config files in the AppData  folder of the Administrator user account, which the application could not see if not running as  administrator.

Why? I have two accounts on this PC - let's call them User1 and User2. User1 is an administrator; User2 is a standard user.  I always log in as User2, and elevate privileges using User1 only as necessary. When installing applications, Windows prompts me for the password for User1.  However, the SatPC32 installer does not follow that convention, and requires one to run it as an administrator (install fails otherwise).
Following their instructions, I ran the installer using the 'Run as administrator' context menu, and provided the password for User1.  This causes the installer to install in the context of User1.

SOLUTION - The solution is actually in the SatPC32 FAQ - http://www.dk1tb.de/FAQ_e.htm#StandardUser
It involves copying the SatPC32 folder of config files from the AppData path of User1 to that of User2.  Now User2 can run the application as User2 without elevated rights.  Now Commander is able to connect to SatPC32 and obtain Sat name, mode, and uplink/downlink frequency, so DxKeeper can grab that when logging a QSO.

Thanks to all who provided suggestions - they eventually helped me track this down.

73 de W0ZF




5441 - 5460 of 208158