Date   

Re: Winwarbler #file

David Tucker
 

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

Dave Tucker Nu4N <dwtucker19@...>
 

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


Re: Winwarbler #file

Dave Tucker Nu4N <dwtucker19@...>
 

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





Re: Winwarbler #file

Dave AA6YQ
 

+ AA6YQ comments below
Its been awhile since I used Winwarbler I forgot my settings. I have a singalink with the proper rcvd and tx.
But I cant get it to transmit in PSK
I am using a Kenwood 2000 for rig control on com 6 and tx on com 5.
Any help would be appreciated

+ When you direct WinWarbler to transmit, does your TS-2000 switch from RX to TX? 

+ Did you review 

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

+ and note the TS-2000 requirement at the end of the article?

       73,

               Dave, AA6YQ

 


Winwarbler #file

Dave Tucker Nu4N <dwtucker19@...>
 

Its been awhile since I used Winwarbler I forgot my settings. I have a singalink with the proper rcvd and tx.
But I cant get it to transmit in PSK
I am using a Kenwood 2000 for rig control on com 6 and tx on com 5.
Any help would be appreciated
--
73's NU4N Dave


Re: Change of ClubLog status

Dave AA6YQ
 

+ AA6YQ comments below

The integration of DXKeeper with ClubLog Grid Square map works very well, and the resulting feature is really interesting
.
To make it perfect, I think that DXK should change the status of ClubLog from Y to M also when there is a modification in the Grid column of DXK: Grid added or modified by LotW, Grid added copying from eQSL or QSL etc.
To check, I reuploaded my ~80K log to ClubLog, merged with existing log, and around 1600 QSO's were modified, reflecting the changes LotW or me made to the Grid column.

+ I've just sent you a new version of DXKeeper that does this; please let me know how it goes...

73,

Dave, AA6YQ


Defect in DXKeeper 16.2.4

Dave AA6YQ
 

Invoking the Upload function in the "Club Log" panel on the Main window's "Check Progress" tab includes all 4 of each QSO's
gridsquares in the information uploaded to Club Log, but right-clicking a Log Page Display entry and selecting "Upload to Clublog"
does not include the selected QSO's gridsquares in the information uploaded to LoTW. This defect is corrected in the next version of
DXKeeper, which is imminent.

73,

Dave, AA6YQ


Re: Commander to SatPC32 integration - will not connect

Dave Fugleberg
 

Bill (G4WJS),
You're correct - that's how a well-behaved Windows application works. However, SatPC32 does not. I have a Win10 laptop where I log in with my Microsoft account. Settings..Accounts..Your Info shows that this account is Administrator. If I simply run the installer, it goes through the first few screens, but then errors out with "Error 1925. You do not have sufficient privileges to complete this installation for all users of the machine. Log on as an administrator and then retry this installation".
If instead I run the installer using the "run as Administrator" context menu, the installation completes successfully.

The documentation for the program (including the article that's linked to in the DxLab Wiki) insists that one must run the installer using 'Run as Administrator' menu, even if they are an administrator, which matches my experience.

But frankly, getting the program installed is not the problem.  The problem I experienced is that on my shack desktop, the program itself (having already been installed) will not RUN unless I 'run as administrator'. That's where I ran into issues. This seems to be related to the way I have my accounts set up on the shack PC, and has nothing to do with either SatPC32, DxLab, or the interface between the two.  So, I am going to go investigate that, and perhaps rethink how I manage accounts on that machine, and see if I can get past this.  Thanks to all who have chimed in to help.  Once I get everything working, I'll post an update.

73 de W0ZF


On Sat, Jul 31, 2021 at 4:03 AM g4wjs <bill.8@...> wrote:
Dave,

why are you running the SatPC32 installer using "Run as Administrator"? Most Windows installers will request elevated rights for just the parts of the installation that need it, like writing to the system registry. The installer should cause the system to prompt for credentials of an account with Administrator rights if it needs it, and automatically drop the elelvated rights when they are no longer needed.

73
Bill
G4WJS.

On 31/07/2021 02:25, Dave Fugleberg wrote:
OK, so I uninstalled SatPC32 using the standard Windows 10 'Apps and Features' panel, and reinstalled. This time, I ran the installer using 'Run as Administrator', but when prompted for a location I instructed it to install to a new folder c:\SatPC32\.  The installation completed successfully.

I tried to run it normally (NOT as Administrator), and it immediately pops an error dialog with the title Error and the text "runtime error 217 at 00673791".

I closed that dialog and ran it using the 'Run as Administrator' right click context menu, and it runs fine.

So, it still appears to want to touch some protected area of Windows, which is bad form indeed.

I wonder what's different between my Windows system and Bill's ?  
73 de W0ZF





On Fri, Jul 30, 2021 at 7:36 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below
SatPC32 is installed to the default location where its installer puts it - C:\Program Files (x86)\SatPC32\
 
Joe, if I try to run the application as a regular user, it errors with "runtime error 217 at 00673791".
 
By the way, this is Windows 10 Pro version 21H1 OS Build 19043.1110

+ You have SatPC32 installed in a file system location that Windows considers "protected", which means it requires Administrator privileges to run.

+ I suggest that you uninstall it, and install it in an unprotected location, like C:\SatPC32

     73,

           Dave, AA6YQ



--
73

Bill

G4WJS.


Re: Commander vs 15.1.6 Radio selection

 

That got it, thanks
73 de KE5WCT
Mike Wilson


On Sat, Jul 31, 2021 at 4:41 AM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

I have had to revert back to my FT-450 while the FT0991A is in the shop. But to my surprise, the FT-450 is no longer listed in the Radio drop down on the Configuration general tab. it is listed for secondary CAT Serial port 'CAT protocol. But enabling the secondary CAT serial port causes a error msg that the ports are invalid. I am using an extremal scu-17 for the interface to Win-10. this arrangement works great for wsjt-x ft8.

+ You evidently have an obsolete Radio.txt file in your Commander folder:

1. terminate Commander

2. download this file into your Commander folder, replacing the existing Radios.txt file

www.dxlabsuite.com/commander/Radios.txt

3. start Commander

      73,

              Dave, AA6YQ








--
Mike
KE5WCT


Re: Commander vs 15.1.6 Radio selection

Dave AA6YQ
 

+ AA6YQ comments below

I have had to revert back to my FT-450 while the FT0991A is in the shop. But to my surprise, the FT-450 is no longer listed in the Radio drop down on the Configuration general tab. it is listed for secondary CAT Serial port 'CAT protocol. But enabling the secondary CAT serial port causes a error msg that the ports are invalid. I am using an extremal scu-17 for the interface to Win-10. this arrangement works great for wsjt-x ft8.

+ You evidently have an obsolete Radio.txt file in your Commander folder:

1. terminate Commander

2. download this file into your Commander folder, replacing the existing Radios.txt file

www.dxlabsuite.com/commander/Radios.txt

3. start Commander

73,

Dave, AA6YQ


Re: Commander to SatPC32 integration - will not connect

g4wjs
 

Dave,

why are you running the SatPC32 installer using "Run as Administrator"? Most Windows installers will request elevated rights for just the parts of the installation that need it, like writing to the system registry. The installer should cause the system to prompt for credentials of an account with Administrator rights if it needs it, and automatically drop the elelvated rights when they are no longer needed.

73
Bill
G4WJS.

On 31/07/2021 02:25, Dave Fugleberg wrote:
OK, so I uninstalled SatPC32 using the standard Windows 10 'Apps and Features' panel, and reinstalled. This time, I ran the installer using 'Run as Administrator', but when prompted for a location I instructed it to install to a new folder c:\SatPC32\.  The installation completed successfully.

I tried to run it normally (NOT as Administrator), and it immediately pops an error dialog with the title Error and the text "runtime error 217 at 00673791".

I closed that dialog and ran it using the 'Run as Administrator' right click context menu, and it runs fine.

So, it still appears to want to touch some protected area of Windows, which is bad form indeed.

I wonder what's different between my Windows system and Bill's ?  
73 de W0ZF





On Fri, Jul 30, 2021 at 7:36 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below
SatPC32 is installed to the default location where its installer puts it - C:\Program Files (x86)\SatPC32\
 
Joe, if I try to run the application as a regular user, it errors with "runtime error 217 at 00673791".
 
By the way, this is Windows 10 Pro version 21H1 OS Build 19043.1110

+ You have SatPC32 installed in a file system location that Windows considers "protected", which means it requires Administrator privileges to run.

+ I suggest that you uninstall it, and install it in an unprotected location, like C:\SatPC32

     73,

           Dave, AA6YQ



--
73

Bill

G4WJS.


Commander vs 15.1.6 Radio selection

 

I have had to revert back to my FT-450 while the FT0991A is in the shop. But to my surprise, the FT-450 is no longer listed in the Radio drop down on the Configuration general tab. it is listed for secondary CAT Serial port 'CAT protocol. But enabling the secondary CAT serial port causes a error msg that the ports are invalid. I am using an extremal scu-17 for the interface to Win-10. this arrangement works great for wsjt-x ft8.
--
Mike
KE5WCT


Re: Report needed DX entities

Dave AA6YQ
 

+ AA6YQ comments below

Is it possible to create a report listing only unworked DXCC entities? Yes:

1. on the Main window's "Log QSOs" tab, click the RAT button to display the "Realtime Award Tracking" window

2. in the "Award Progress Filter" panel on the "Realtime Award Tracking" window's DCC tab

2a. set the Band selector to ANY

2b. set the Mode selector to MIXED

2c. check the Unworked box, and uncheck all the other box (unless you want to see unworked deleted DXCC entities, in which case check that box too)

2d. click the Report button

+ For additional information about tracking DXCC award progress, see

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

+ and

https://www.dxlabsuite.com/dxkeeper/Help/Progress.htm#Checking%20and%20Analyzing%20DXCC%20Progress

73,

Dave, AA6YQ


Report needed DX entities

Steve, N5EP
 

Is it possible to create a report listing only unworked DXCC entities?   DXKeeper's DXCC progress report will include unworked DXCC entities if the "Hide" box is not checked in the Awards config panel, but I would like to get a report only containing the unworked entities that I still need.

Steve, N5EP


Re: shortcuts, COM port questions ic-7300

Den, ve2iea
 

Works great, thank you Dave!

73
Den

1361 - 1380 of 204068