Date   
Re: Flex has released SmartSDR 2.5.1 and SmartSDR 3.0.27

Kent Olsen
 

I wish I could say that my upgrade from 2.4.9 to 2.5.1 went ok, but it did not. Nothing to do with DXLab yet. 

The upgrade screwed up the names for the DAX devices so I had to go thru and change them. All works well now. I will let you know if I have any disconnects from Commander. 

Thanks
73
Kent
N6WT


On Wed, Jun 12, 2019 at 6:14 PM Tom Denio via Groups.Io <n5moa=yahoo.com@groups.io> wrote:
I upgraded? to v2.5.1 on my 6500.

Upgrade went smoothly, I haven't (yet) seen the issues you are having using Commander 14.0.8 and v2.5.1.

  This "TX/MIC Profile Changes: All settings are now saved automatically as the settings are changed.", imo, is stupid. Someone else may, but I see no need/purpose for it. Other than to screw up my settings. Yes I can import my settings again. Why?

I know that isn't a DXLab's issue. I've already vented in the SSDR forum. :-)

If an issue pops up with DXLabs I'll post it.

73, Tom
N5MOA



Re: Flex has released SmartSDR 2.5.1 and SmartSDR 3.0.27

Kent Olsen
 

Dave

I think I had a disconnect from Commander while using WSJT-X. I went to transmit and it would not. I then hit Tune on WSJT-X and after a brief hesitation, it started to transmit.

Thanks
73
Kent
N6WT


On Wed, Jun 12, 2019 at 6:46 PM Kent Olsen via Groups.Io <kilo6dko=gmail.com@groups.io> wrote:
I wish I could say that my upgrade from 2.4.9 to 2.5.1 went ok, but it did not. Nothing to do with DXLab yet. 

The upgrade screwed up the names for the DAX devices so I had to go thru and change them. All works well now. I will let you know if I have any disconnects from Commander. 

Thanks
73
Kent
N6WT


On Wed, Jun 12, 2019 at 6:14 PM Tom Denio via Groups.Io <n5moa=yahoo.com@groups.io> wrote:
I upgraded? to v2.5.1 on my 6500.

Upgrade went smoothly, I haven't (yet) seen the issues you are having using Commander 14.0.8 and v2.5.1.

  This "TX/MIC Profile Changes: All settings are now saved automatically as the settings are changed.", imo, is stupid. Someone else may, but I see no need/purpose for it. Other than to screw up my settings. Yes I can import my settings again. Why?

I know that isn't a DXLab's issue. I've already vented in the SSDR forum. :-)

If an issue pops up with DXLabs I'll post it.

73, Tom
N5MOA



Re: Flex has released SmartSDR 2.5.1 and SmartSDR 3.0.27

Dave AA6YQ
 

+ AA6YQ comments below

I think I had a disconnect from Commander while using WSJT-X. I went to transmit and it would not. I then hit Tune on WSJT-X and after a brief hesitation, it started to transmit.

+ Yes, that's the sort of behavior I've seen with both SmartSDR v2.5.1 and v3.0.27. I did not see it with v2.5.0 or v3.0.25.

73,

Dave, AA6YQ

Re: Flex has released SmartSDR 2.5.1 and SmartSDR 3.0.27

Kent Olsen
 

I may have found the problem. There is a new setting in SSDR. 

In SSDR click on settings then "TX Band Settings". On mine, the box for 20m "PTT Inhibit" was checked. It was the only one checked. I don't know why.

Thanks
73
Kent
N6WT


On Wed, Jun 12, 2019 at 7:08 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

I think I had a disconnect from Commander while using WSJT-X. I went to transmit and it would not. I then hit Tune on WSJT-X and after a brief hesitation, it started to transmit.

+ Yes, that's the sort of behavior I've seen with both SmartSDR v2.5.1 and v3.0.27. I did not see it with v2.5.0 or v3.0.25.

         73,

              Dave, AA6YQ





Enhancement Suggestion: image support

w3mmm.radio@...
 

hi-
New member here, and I did search to see if this had been addressed before but didn’t find anything.  I’ve been a DX Labs Suite user for many years and love the product.

What I’m seeking is a way to display a thumbnail image alongside a log record within DX Keeper.  

If I were to add such a feature myself, I would include the thumbnail to the right of the “Details” section, above the log page view.

I would pull from the “file” field in the Details section, and if that file had a .gif or .jpg extension, I’d show the thumbnail automatically in the blank area to the right of the details section each time that log record is pulled up. 

Thag image could be any number of things:
- a scan of a QSL card for the contact
- a picture of the person or club
- a screen capture of the FT8 contact for that QSO.
- maybe an eQSL image if configured that way
- the image on QRZ.com for that callsign.

The images themselves would be elsewhere: on a local drive or on the Internet.  The thumbnail as shown natively in the DX Keeper display could be clicked to either visit the internet source or open the full sized local image in the users default image editor.

Anyway, just a thought, I know that DX Keeper isn’t meant to be graphical but this would be really useful/ enjoyable for me.

73, Jay W3MMM

Re: Enhancement Suggestion: image support

Dave AA6YQ
 

+ AA6YQ comments below

New member here

+ Welcome, Jay!

and I did search to see if this had been addressed before but didn’t find anything. I’ve been a DX Labs Suite user for many years and love the product.

What I’m seeking is a way to display a thumbnail image alongside a log record within DX Keeper.

If I were to add such a feature myself, I would include the thumbnail to the right of the “Details” section, above the log page view.

I would pull from the “file” field in the Details section, and if that file had a .gif or .jpg extension, I’d show the thumbnail automatically in the blank area to the right of the details section each time that log record is pulled up.

Thag image could be any number of things:
- a scan of a QSL card for the contact
- a picture of the person or club
- a screen capture of the FT8 contact for that QSO.
- maybe an eQSL image if configured that way
- the image on QRZ.com for that callsign.

The images themselves would be elsewhere: on a local drive or on the Internet. The thumbnail as shown natively in the DX Keeper display could be clicked to either visit the internet source or open the full sized local image in the users default image editor.

+ If the the Details panel's file textbox contains the name of an image file, double-clicking that textbox will display the contents of that image file using whatever image processing application you've associated with the image file's suffix.

+ There is no guarantee that there will be space available to the right of the Details panel to display an image.r

73,

Dave, AA6YQ

Re: Enhancement Suggestion: image support

w3mmm.radio@...
 

+ If the the Details panel's file textbox contains the name of an image file, double-clicking that textbox will display the contents of that image file using whatever image processing application you've associated with the image file's suffix.

- - Yes, understood and that is helpful.  That's what led me to the thumbnail suggestion, as it allows the picture to come up as defaulted when the QSO record is displayed (assuming the user has DX Keeper open widely enough). 

+ There is no guarantee that there will be space available to the right of the Details panel to display an image.

 - - Understood on this as well, yet the QSO and QSL sections both have content out in that area.  The user may or may not want to see the thumbnail, and if they did, they could open the Log QSOs window wide enough to see it.   The thumbnail wouldn't have to be any bigger than the width of the QSL section key that's already out there.  

Its just a thought.  Fred Lloyd, AA7BQ has spoken about how the simple addition of a picture on the top right of QRZ.com pages made all the difference.  Yours is a different product, but just as personal and a place where hams spend a LOT of time. 

One of the fundamental uses of a log is "did I work this person before" - and when this is done in real time (like we just started another QSO) it would be useful to have a basic image with that log entry (if I provided one) that comes up as default thumbnail, vs doing a click-through and having another application open.  

That's my case - I get that this is outside the norm for this and may be difficult to program within a traditional database application.   
73 and thanks again for the great program

Re: Flex has released SmartSDR 2.5.1 and SmartSDR 3.0.27

w6de
 

This may not be a Flex related problem.  I see something like this once in a while with my Icom 7600 on FT8.  The symptoms are the radio goes into transmit but no tones are sent—to me that seems to implicate WSJTX.  While I think it only happens on a new QSO initiation, it is so infrequent that I haven’t been able to figure out with any certainty the pattern to when/why it happens.

 

73,

Dave, w6de

 

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Kent Olsen
Sent: 13 June, 2019 01:57
To: DXLab@groups.io
Subject: Re: [DXLab] Flex has released SmartSDR 2.5.1 and SmartSDR 3.0.27

 

Dave

 

I think I had a disconnect from Commander while using WSJT-X. I went to transmit and it would not. I then hit Tune on WSJT-X and after a brief hesitation, it started to transmit.

 

Thanks

73

Kent

N6WT

 

 

On Wed, Jun 12, 2019 at 6:46 PM Kent Olsen via Groups.Io <kilo6dko=gmail.com@groups.io> wrote:

I wish I could say that my upgrade from 2.4.9 to 2.5.1 went ok, but it did not. Nothing to do with DXLab yet. 

 

The upgrade screwed up the names for the DAX devices so I had to go thru and change them. All works well now. I will let you know if I have any disconnects from Commander. 

 

Thanks

73

Kent

N6WT

 

 

On Wed, Jun 12, 2019 at 6:14 PM Tom Denio via Groups.Io <n5moa=yahoo.com@groups.io> wrote:

I upgraded? to v2.5.1 on my 6500.

Upgrade went smoothly, I haven't (yet) seen the issues you are having using Commander 14.0.8 and v2.5.1.

  This "TX/MIC Profile Changes: All settings are now saved automatically as the settings are changed.", imo, is stupid. Someone else may, but I see no need/purpose for it. Other than to screw up my settings. Yes I can import my settings again. Why?

I know that isn't a DXLab's issue. I've already vented in the SSDR forum. :-)

If an issue pops up with DXLabs I'll post it.

73, Tom
N5MOA


IC-9700 - WSJT-X and DX Labs

Jeff Schwartz
 

FYI, With Dave's hard work integrating Commander with the new IC-9700 It integrates flawlessly with WSJT-X for FT8 use of the IC-9700. I see where other individuals are going through a variety of challenges trying to make the 9700 work on FT-8 without the use of DX Labs. I feel their pain but Dave has made it an easy get with DX Labs.
Thanks Dave... Jeff / KI0KB/WC7WB

Problem with Path Finder

Julio Peralta
 

Recently I’ve been having a problem with Path Finder. When I click on a spot I get a message from PF that it isn’t logged into QRZ.com.

 

Today I tried to go into PF’s config and when I click on the config button nothing happens. The help button works.

 

I’ve tried shutting down the computer and restarting but it still won’t let me open PF config.

 

Julio, W4HY

Re: Flex has released SmartSDR 2.5.1 and SmartSDR 3.0.27

Dave AA6YQ
 

+ AA6YQ comments below

This may not be a Flex related problem. I see something like this once in a while with my Icom 7600 on FT8. The symptoms are the radio goes into transmit but no tones are sent—to me that seems to implicate WSJTX. While I think it only happens on a new QSO initiation, it is so infrequent that I haven’t been able to figure out with any certainty the pattern to when/why it happens.

+ I've also seen that with my 7800. The radio switches from RX to TX, but no tones are transmitted.

+ Bill G4WJS, is there a way to identify the cause of this behavior?

73,

Dave, AA6YQ

Re: Flex has released SmartSDR 2.5.1 and SmartSDR 3.0.27

Jeffrey griffin
 

I've been seeing the same thing for almost the last year or so with 2 different computers all running WIN10, and 4 different radios. A Flex 6500, Flex VU5K, Elecraft K3, and an Icom IC-9100. I simply shut down WSJT-X and bring it back up again. That fixes it for awhile...

73 Jeff kb2m

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ
Sent: Thursday, June 13, 2019 4:27 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Flex has released SmartSDR 2.5.1 and SmartSDR 3.0.27

+ AA6YQ comments below

This may not be a Flex related problem. I see something like this once in a while with my Icom 7600 on FT8. The symptoms are the radio goes into transmit but no tones are sent—to me that seems to implicate WSJTX. While I think it only happens on a new QSO initiation, it is so infrequent that I haven’t been able to figure out with any certainty the pattern to when/why it happens.

+ I've also seen that with my 7800. The radio switches from RX to TX, but no tones are transmitted.

+ Bill G4WJS, is there a way to identify the cause of this behavior?

73,

Dave, AA6YQ

Re: Problem with Path Finder

Dave AA6YQ
 

+ AA6QY comments below

On Thu, Jun 13, 2019 at 01:22 PM, Julio Peralta wrote:

Today I tried to go into PF’s config and when I click on the config button nothing happens. The help button works.

 

I’ve tried shutting down the computer and restarting but it still won’t let me open PF config.

+ See

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

      73,

            Dave, AA6YQ

 

DXKeeper - Error in QSL command <: malformed command

Ron Rossi
 

Folks,

When submitting a log entry to LotW I get the message from DXKeeper
"Error in QSL command <: malformed command". After clearing the message window the entry is properly sent to LotW.
I get this message when uploading from the logging screen. I do NOT get this message when an FT8 contact is automatically logged through WSJT for example.

I cannot say which version this started with or even if it is version dependent. I had taken a bit of a break from radio and this is the behavior recently. I have made sure TQSL is the most recent and of course rebooted.

thanks
--
73 es God Bless de Ron KK1L <><

Re: DXKeeper - Error in QSL command <: malformed command

Dave AA6YQ
 

+ AA6YQ comments below

When submitting a log entry to LotW I get the message from DXKeeper "Error in QSL command <: malformed command". After clearing the message window the entry is properly sent to LotW.
I get this message when uploading from the logging screen. I do NOT get this message when an FT8 contact is automatically logged through WSJT for example.

I cannot say which version this started with or even if it is version dependent. I had taken a bit of a break from radio and this is the behavior recently. I have made sure TQSL is the most recent and of course rebooted.

+ On the Configuration window's Log tab, please check the "Log Panels" panel's Details box.

+ On the Main window's "Log QSOs" tab, select a logged QSO that produced the "malformed command" error when you attempted to submit it to LoTW. In this tab's Details panel, what is specified in the comment box?

73,

Dave, AA6YQ

Re: Enhancement Suggestion: image support

Dave AA6YQ
 

* AA6YQ comments below

+ If the the Details panel's file textbox contains the name of an image file, double-clicking that textbox will display the contents of that image file using whatever image processing application you've associated with the image file's suffix.

- - Yes, understood and that is helpful. That's what led me to the thumbnail suggestion, as it allows the picture to come up as defaulted when the QSO record is displayed (assuming the user has DX Keeper open widely enough).

* Saving one double-click gesture would not justify the addition of an option that governs the appearance of the picture.


+ There is no guarantee that there will be space available to the right of the Details panel to display an image.

- - Understood on this as well, yet the QSO and QSL sections both have content out in that area. The user may or may not want to see the thumbnail, and if they did, they could open the Log QSOs window wide enough to see it. The thumbnail wouldn't have to be any bigger than the width of the QSL section key that's already out there.

* It's more complicated than that. When the "Display panels in two columns" option is enabled, a panel may appear to the immediate right of the Details panel. It would be better to display the image in a free-standing window, which the user could configure for size and position.

73,

Dave, AA6YQ

Re: DXKeeper - Error in QSL command <: malformed command

Ron Rossi
 

the comments box is empty.

73 es God Bless de KK1L...Ron Rossi (kk1l@...) <><
QTH: Jericho, Vermont
My page: http://kk1l.com

On 6/13/2019 19:27, Dave AA6YQ wrote:
+ AA6YQ comments below

When submitting a log entry to LotW I get the message from DXKeeper "Error in QSL command <: malformed command". After clearing the message window the entry is properly sent to LotW.
I get this message when uploading from the logging screen. I do NOT get this message when an FT8 contact is automatically logged through WSJT for example.

I cannot say which version this started with or even if it is version dependent. I had taken a bit of a break from radio and this is the behavior recently. I have made sure TQSL is the most recent and of course rebooted.

+ On the Configuration window's Log tab, please check the "Log Panels" panel's Details box.

+ On the Main window's "Log QSOs" tab, select a logged QSO that produced the "malformed command" error when you attempted to submit it to LoTW. In this tab's Details panel, what is specified in the comment box?

73,

Dave, AA6YQ


--
73 es God Bless de Ron KK1L <><

Re: DXKeeper - Error in QSL command <: malformed command

Dave AA6YQ
 

+ AA6YQ comments below

the comments box is empty.

+ OK. Please place your log file in a zip archive, attach the zip archive to an email message, and send the email message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ

WSJT-X QSO's to DXKeeper using SpotCollector

Carl - WC4H
 

When I use SpotCollector populate DXKeeper with QSO's from WSJT-X, the rx freq field and the rx band field are not populated.  That causes the Auxiliary box to be checked in the Log QSOs panel and the rx band label to blink in red.

Am I missing a setting somewhere?

Thanks.
Carl - WC4H

Re: WSJT-X QSO's to DXKeeper using SpotCollector

Dave AA6YQ
 

+ AA6YQ comments below

When I use SpotCollector populate DXKeeper with QSO's from WSJT-X, the rx freq field and the rx band field are not populated. That causes the Auxiliary box to be checked in the Log QSOs panel and the rx band label to blink in red.

Am I missing a setting somewhere?

+ An empty "RX Band" item is not invalid if the "RX Freq" item is also empty.

+ Please do the following:

1. on the Configuration window's General tab, check the "Log debugging info" box

2. log a QSO via WSJT-X

3. on the Configuration window's General tab, uncheck the "Log debugging info" box

4. attach the errorlog.txt file from your DXKeeper folder to an email message, and send the message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ