Date   

Re: Error Logging

Dave AA6YQ
 

+ AA6YQ comments below
Why does this happen??  Every so often DXKeeper throws this curve ball.  Can get around it by manually logging the info, but curios if there is a way around this situation.
+ Please describe the situation to which you are referring in as much detail as you can.

       73,

             Dave, AA6YQ


Error Logging

n7bv@...
 

Why does this happen??  Every so often DXKeeper throws this curve ball.  Can get around it by manually logging the info, but curios if there is a way around this situation.

=============
Thanks.   73, Chuck N7BV


Re: DXKeeper 16.1.9 is available

Dave AA6YQ
 

+ AA6YQ comments below
I don't know if this is a bug or a feature but when the capture window is resized (shrunk vertically) and then returned to its original size, all of the rows are all selected again.

+ That's intentional, Dick; I sought to preserve the previous functionality for those users who found it sufficient and convenient:

- When you expand the Capture window's height, each newly-exposed row is automatically enabled on the new "Capture Layout" window. 

- When you reduce the Capture window's height, each newly-hidden row is automatically disabled on the new "Capture Layout" window.
 
           73,

                   Dave, AA6YQ



       73,

           Dave, AA6YQ

 


Re: DXKeeper 16.1.9 is available

Dave AA6YQ
 

+ AA6YQ comments below

Agreed! One question, though. When I start up I now have the QSL Msg dropdown selected instead of the Comment. I have to re-set the choice to Comment each time I start DXKeeper. Anyone else seeing this?

+ Thanks, Chuck, that's a regression defect. It is corrected in the next version of DXKeeper.

73,

Dave, AA6YQ


Re: DXKeeper 16.1.9 is available

Joe Subich, W4TV
 

Resizing vertically (expanding) always selected all rows.
You are triggering that standard response by expanding the
window.

73,

... Joe, W4TV

On 2021-07-07 10:03 AM, Dick Grote via groups.io wrote:
I like this.
I don't know if this is a bug or a feature but when the capture window is resized (shrunk vertically) and then returned to its original size, all of the rows are all selected again.
--
Dick
K6PBF


Re: DXKeeper 16.1.9 is available

Andy - K0AF
 

Agreed!  One question, though.  When I start up I now have the QSL Msg dropdown selected instead of the Comment.  I have to re-set the choice to Comment each time I start DXKeeper.  Anyone else seeing this?
 
 
73 de Chuck, WS1L  
I see the same thing Chuck; the default for row 10 is "QSL msg". I can change it to "comment" by clicking the "~" on the left side of the entry box but it reverts to "QSL msg" when DXKeeper is restarted. The Cfg window allows you to save and recall the Capture Window layout but it also reverts to "QSL msg" for row 10 regardless of the state when the view was saved.

The new Capture Window layout option is a nice enhancement. Thanks Dave!

Andy - K0AF


Re: DXKeeper 16.1.9 is available

Dick Grote
 

I like this.

I don't know if this is a bug or a feature but when the capture window is resized (shrunk vertically) and then returned to its original size, all of the rows are all selected again.
--
Dick
K6PBF


Re: DXKeeper 16.1.9 is available

Chuck, WS1L
 

Agreed!  One question, though.  When I start up I now have the QSL Msg dropdown selected instead of the Comment.  I have to re-set the choice to Comment each time I start DXKeeper.  Anyone else seeing this?


73 de Chuck, WS1L  


On Wed, Jul 7, 2021 at 6:45 AM John Huffman <hjohnc@...> wrote:
The new "Capture Layout" is outstanding!  Removes clutter and takes up much less screen space.

Thanks, Dave!!

73 de K1ESE
John


Re: DXKeeper 16.1.9 is available

John Huffman
 

The new "Capture Layout" is outstanding!  Removes clutter and takes up much less screen space.

Thanks, Dave!!

73 de K1ESE
John


DXKeeper 16.1.9 is available

Dave AA6YQ
 

* If you are using Window Defender Antivirus (Windows 10), update it to its latest malware definition in

https://www.microsoft.com/en-us/wdsi/definitions

before installing or upgrading to DXKeeper 16.1.9


This version

- provides a new "Capture Layout" window that provides row-by-row control over the Capture window layout (tnx to Dave N9FN, Mike
K9UW, and Joe W4TV)

- updates the Configuration.htm and LogNewCapture.htm documentation files


Notes:

1. Update your firewall and anti-malware applications to consider this new version of DXKeeper to be "safe"

a. JOTTI virus scan: 0 of 15 scanners detected malware in this version's executable

b. VirusTotal: 0 of 69 scanners detected malware in this version's executable

c. submitted to Microsoft for analysis by Windows Defender: no malware detected in this version's executable


2. If this upgrade doesn't work correctly, see the "After an Upgrade" section of
<http://www.dxlabsuite.com/dxlabwiki/ApplicationStoppedWorking>


3. After upgrading, to revert to the previous version of DXKeeper, see
<http://www.dxlabsuite.com/dxlabwiki/RevertApplicationVersion>


4. The new "Capture Layout" window appears when you click the new Cfg button in the Capture window's upper-right corner, or when you
click the Layout button in the "Capture options" panel on the Configuration window's General tab; using this window, you can

- select which of the Capture window's 18 rows of textboxes, selectors, and controls should be visible (the first row must always be
visible)

- save and later recall up to four Capture window layouts (e.g. for general operation, for DXing, for contesting, for satellite
operations, etc.)

- see https://www.dxlabsuite.com/dxkeeper/Help/Configuration.htm#Capture_Layout_window


DXKeeper 16.1.9 is available via the DXLab Launcher and via

http://www.dxlabsuite.com/download.htm

73,

Dave, AA6YQ


Re: New user joining Group

Dave AA6YQ
 

I have begun the process of transitioning from DXbase (since 2002) to DX Lab, so I am a total rookie. I managed to import my archive log of over 128,000 QSO's with my W1EBI callsign, but I need to do some further log configuration. The Log Display showed that DX Lab had an update, so I clicked "update" and got a screen confirming a successful update. I closed DX Lab. When I went back to open the program again, I got a surprise: "Existing fields were not successfully updated due to an error noted in the errorlog.txt files; the specified log cannot be opened."

I fiddled around and opened the Log Display again. It showed the updated version 16.1.5. There were zero QSO's in the log. What happened to my archive log?

+ Welcome to DXLab, George.

+ To support new modes defined by ADIF, DXKeeper 16.1.5 updates the capacity of your log's MODE item from 8 to 12 characters. Unfortunately, some Windows 10 systems report "insufficient system resources" when DXKeeper attempts to do this.

+ Please place your log file (pathname specified in the "Log file" panel on the Configuration window's Log tab) in a zip archive. Attach the archive to an email message, and send the message to me via

aa6yq (at) ambersoft.com

+ I will then sent you your log file with its MODE item's capacity expanded.

73,

Dave, AA6YQ


New user joining Group

George VA2EBI
 

I have begun the process of transitioning from DXbase (since 2002) to DX Lab, so I am a total rookie.  I managed to import my archive log of over 128,000 QSO's with my W1EBI callsign, but I need to do some further log configuration.  The Log Display showed that DX Lab had an update, so I clicked "update" and got a screen confirming a successful update.  I closed DX Lab.  When I went back to open the program again, I got a surprise:  "Existing fields were not successfully updated due to an error noted in the errorlog.txt files; the specified log cannot be opened."

I fiddled around and opened the Log Display again.  It showed the updated version 16.1.5.  There were zero QSO's in the log.  What happened to my archive log?

George VA2EBI-W1EBI


Re: SpotCollector Web Server

Dave AA6YQ
 

+ AA6YQ comments below
Somehow my wireless connection was set as if it is on a "Public" network, and not a "Private" network, which apparently changes how the firewall (which I believed to be off) behaves. 

Sorry for the confusion / spam.

+ The description of every problem solved is an aide to future users. Thanks, Jon!

        73,

              Dave, AA6YQ


Re: SpotCollector Web Server

Jon KM8V
 

Ok. I figured it out.

Somehow my wireless connection was set as if it is on a "Public" network, and not a "Private" network, which apparently changes how the firewall (which I believed to be off) behaves. 

Sorry for the confusion / spam.

73 de KM8V


Re: SpotCollector Web Server

g4wjs
 

On 06/07/2021 16:56, Jon KM8V wrote:
Ok, on further investigation, it looks like it is logging successful connections - but still will not accept connections from on the LAN.

Is it possible it is somehow only listening on certain interfaces in Windows 10 that an update to Windows or SC changed?
Hi Jon,

netstat will tell you what interfaces the server is listening on. Here it listens 0.0.0.0:8080 which is the all interfaces local address.



--
73

Bill

G4WJS.


Re: SpotCollector Web Server

Jon KM8V
 

Ok, on further investigation, it looks like it is logging successful connections - but still will not accept connections from on the LAN.

Is it possible it is somehow only listening on certain interfaces in Windows 10 that an update to Windows or SC changed?


Re: Windows Registry indicates that the Launcher is not installed

Dave AA6YQ
 

+ AA6YQ comments below

Thanks for the quick reply Dave. This was a weird one.

Good news, I got it working without reinstalling Windows (which, ironically, is a new installation from only a week ago!).

Just for the record, here's what I did:
1) Loaded a system restore point from 3PM yesterday, before I did the initial DXLab installation
2) Ran both CCleaner and Ashampoo PC Optimizer, backing up the registry first (CCleaner offers that option)
3) Ran the DXLab Launcher installer and it successfully did the upgrade to the latest Launcher.
4) Installed the remaining DXLab apps from the Launcher.

So all good for now. Would be nice to know exactly what the problem was, but I'll take the results anyway :) .

+ I'm glad that you got it sorted, Rowland!

73,

Dave, AA6YQ


Re: Windows Registry indicates that the Launcher is not installed

RowlandA
 

Thanks for the quick reply Dave.  This was a weird one.

Good news, I got it working without reinstalling Windows (which, ironically, is a new installation from only a week ago!).

Just for the record, here's what I did:
1)  Loaded a system restore point from 3PM yesterday, before I did the initial DXLab installation
2)  Ran both CCleaner and Ashampoo PC Optimizer, backing up the registry first (CCleaner offers that option)
3)  Ran the DXLab Launcher installer and it successfully did the upgrade to the latest Launcher.
4)  Installed the remaining DXLab apps from the Launcher.

So all good for now.  Would be nice to know exactly what the problem was, but I'll take the results anyway :) .
73,

Rowland K4XD


Re: USB Relay interface

Larry K8UT
 

Hamilton,

Another option would be to using the network interface in Commander, although my freeware application "FreqEZ" may be more sophisticated than you require. FreqEZ is somewhat of a DIY project compared to the expensive off-the-shelf Band Decoder products. But it was written specifically for DXLab's Commander and - using tcp/ip UDP packets - avoids all of the mess surrounding serial port assignments in Windows.

You can read about FreqEZ here:
https://hamprojects.info/freqez/

-larry (K8UT)

------ Original Message ------
From: "Dave AA6YQ" <aa6yq@ambersoft.com>
To: DXLab@groups.io
Sent: 2021-07-06 1:06:25
Subject: Re: [DXLab] USB Relay interface

+ AA6YQ comments below

I have used DXLAB since 2015 and currently use a parallel interface for antenna switching.

I would like to replace the parallel interface with a USB relay module. After hours of web searches and reading manuals I haven't found a solution. Can it be done?

+ You could use a USB relay module that

- programmatically emulates a parallel port

or that

- responds to the microHAM protocol

or that

- responds to the OTRSP protocol

+ I built a relay module driven by this USB device:

https://www.piexx.com/index.php?main_page=index&cPath=12

+ using the OTRSP protocol.

+ There are commercial devices that can be controlled with the microHAM protocol; K1XM has devices that can be controlled by the OTRSP protocol:

https://k1xm.org/index.html


+ See "SO2R Serial Port panel" in

https://www.dxlabsuite.com/commander/Help/Configuration.htm#SO2R%20Serial%20Port

73,

Dave, AA6YQ







--
Hamilton K1HMS
Amherst, NH USA


<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>







Re: USB Relay interface

Tim Rife
 

While not technically a USB relay, FreqEZ2 by Larry, K8UT, is worth a look.  He sells a Raspberry Pi hat with 16 relay outputs that, when paired with a raspberry Pi, will listen for UDP packets on your network from your logging suite (Commander) and change antennas accordingly.  Switching can be done automatically or manually, selected with the click of a mouse.  You can also employ multiple units to increase the number of relay outputs if needed.  Very affordable and flexible solution and the software is free.  I am not affiliated with Larry at all, just a happy customer.

Documentation can be found here:

https://hamprojects.info/freqez/ <https://hamprojects.info/freqez/>

73,

Tim
KK9T

On 7/6/2021 1:06 AM, Dave AA6YQ wrote:
+ AA6YQ comments below

I have used DXLAB since 2015 and currently use a parallel interface for antenna switching.

I would like to replace the parallel interface with a USB relay module. After hours of web searches and reading manuals I haven't found a solution. Can it be done?

+ You could use a USB relay module that

- programmatically emulates a parallel port

or that

- responds to the microHAM protocol

or that

- responds to the OTRSP protocol

+ I built a relay module driven by this USB device:

https://www.piexx.com/index.php?main_page=index&cPath=12

+ using the OTRSP protocol.

+ There are commercial devices that can be controlled with the microHAM protocol; K1XM has devices that can be controlled by the OTRSP protocol:

https://k1xm.org/index.html


+ See "SO2R Serial Port panel" in

https://www.dxlabsuite.com/commander/Help/Configuration.htm#SO2R%20Serial%20Port

73,

Dave, AA6YQ







--
Hamilton K1HMS
Amherst, NH USA


<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>





2281 - 2300 of 204552