Date   
Re: Merry Christmas and Happy Hanukkah to all who celebrate

Ivor Lee
 

I also like a Merry Christmas and Happy Hunakkah to everyone on this list and in particular to thank Dave for all his hard work and incredible support.

 

Wishing everyone good DX for 2020 and looking forward to meeting many members of the list on the air.

 

Ivor

MM0IEL

 

Sent from Mail for Windows 10

 

Re: Rsba1 and DXLab

ghassan chammas
 

Ok. So i should set up a virtual port and use win4k suite.
Can you elaborate a bit more on where the dxlab and rsba1 should be connected and how?

Regards and merry christmas
Ghassan
Od5ya



Sent from Samsung tablet.


-------- Original message --------
From: Ed Pflueger <ab4iq@...>
Date: 24/12/2019 00:54 (GMT+02:00)
To: DXLab@groups.io
Subject: Re: [DXLab] Rsba1 and DXLab

I use WIN4K3Suite with com0com and can run 6 different programs into my K3S  My K3 goes into Tom's program as Com5 then I set up 6 pairs 8/9, 10/11, 12/13, 14/15, 16/17 and 18/19 in com0com.  For example WIN4K3Suite pair 8 is for DXBase and I set the com port in DXBase for com9.  That way I can run DXLab on pairs 10/11, N1MM on 12/13, DX4WIN on 14/15, ACLOG on 16/17 and WSJT-X on 18/19.  The reason for the various logging programs is I'm trying to get away from DXBase but I run all of them at the same time.  Friends think I'm nuts and maybe I am.  HI HI..  However so far DXLab is winning the race.  I've already deleted HRD, just not my type of program.

Ed.. AB4IQ

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ
Sent: Monday, December 23, 2019 4:24 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Rsba1 and dxlab

+ AA6YQ comments below

I am installing rsba1, icom remote radio software, on my pc that runs dxlab ans is connected to my icom7300 through com3 via usb.
Can both software coexist without collision?

+ Two different applications cannot simultaneously control the same transceiver.

+ The only reliable way to do that is with an application the provides multiple applications with the ability to interact with a "virtual transceiver", and then keeps the actual transceiver in sync with that "virtual transceiver". That's how Commander's Secondary CAT Port works. Win4KSuite for Icom works this way as well. I don't know if Win4KSuite for Icom would enable both Commander and RSBA1 to simultaneously control your 7300. You could ask its author, Tom VA2FSQ.

         73,

                Dave, AA6YQ










Re: WSJT-X callsign flowing to DXView and DXKeeper

Dave AA6YQ
 

+ AA6YQ comments below

In the past if I was working a station in FT8, during the QSO the call I'm working would display in DXView and also show me past QSO's with that station. Recently I noticed that is not happening anymore until the call is actually logged. I have gone into the JTAlerts and enabled everything under Settings - Applications - DXLab Suite, and everything is checked under DXKeeper, and everything checked under PathFinder & DXView. Under Settings - DXLab DXKeeper I have enabled DXLab DXKeeper Logging as well.

The only time the callsign flows to DXView and the DXKeeper logbook is after I complete the QSO and log the contact. Is there another setting I need to enable in order for this to work properly for me again?

+ The recommended settings when using JT-Alert with WSJT-X and DXLab are here:

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

+ Specifically, see step 2.c.i in the JTAlert section.

73,

Dave, AA6YQ

Re: Refreshing DXKeeper Log Display after logging a QSO

Dave AA6YQ
 

+ AA6YQ comments below

My experience has been that after I log a QSO, the only QSO appearing in my log is the QSO that I just logged.

+ What actions are you taking to log a QSO?

In order to display my full log (including the QSO just recorded) I find it necessary to close and reopen DXKeeper. I know that there must be a much simpler way to do this - but at the moment, I'm stumped.

+ In the Filter panel at the bottom of the Main window's "Log QSOs" tab, click the X button.

+ Then review

<https://www.dxlabsuite.com/dxkeeper/Help/FilterLog.htm>

+ Some apps direct DXKeeper to filter the log Page Display for previous QSOs with a callsign when that callsign is first "captured"; WinWarbler can be configured to do this, for example. Directing DXKeeper to log a QSO does not automatically remove the filtering.

73,

Dave, AA6YQ

Re: Saving Changes to DX Keeper Display Configuration

Dave AA6YQ
 

+ AA6YQ comments below

I would like to permanently delete the "Auxiliary" and "QSL" fields from the "Log QSO's" tab page of DXKeeper, but even though I uncheck these fields in the DXKeeper "Log QSO's" page and from the DXKeeper Log Configuration page (and save the changes) - those fields keep reappearing and the "Station Call" and "QTH" labels keep blinking at me. I have attempted to control double-click these blinking labels and fill the corresponding fields, but this does not seem to help. I don't use the "Axiliary" and "QSL" fields and would just like to permanently suppress them.

+ To ensure that each new logged QSO includes your Station Callsign, specify yours in the "Station callsign" box in the upper-left corner of the Configuration windows Defaults tab.

+ I assume that it’s the myQTH label that is blinking the QSL panel. To ensure that each new logged QSO includes your "myQTH ID", select a "default myQTH ID" in the "Log Settings" panel on the Configuration window's Log tab.

+ For more information, see

<https://www.dxlabsuite.com/dxkeeper/Help/LogIntegrity.htm>

+ and

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

73,

Dave, AA6YQ

Re: Sending Real CW

Mark Robinson
 

I see that the 7610 has a dedicated cw speed  knob, so adjusting the tx speed with winwarbler in CAT mode is pretty easy to do.

73 Mark N1UK

On 23-Dec-19 6:25 PM, Dave AA6YQ wrote:
+ AA6YQ comments below

I am running through Win4Icom with a Com0Com virtual com port to my IC 7610

+ Win4Icom doesn't convey the "CW Speed" instruction to your radio. I reported this to Tom awhile ago.

73,

Dave, AA6YQ

WSJT-X callsign flowing to DXView and DXKeeper

Scott
 

In the past if I was working a station in FT8, during the QSO the call I'm working would display in DXView and also show me past QSO's with that station. Recently I noticed that is not happening anymore until the call is actually logged. I have gone into the JTAlerts and enabled everything under Settings - Applications - DXLab Suite, and everything is checked under DXKeeper, and everything checked under PathFinder & DXView. Under Settings - DXLab DXKeeper I have enabled DXLab DXKeeper Logging as well. 

The only time the callsign flows to DXView and the DXKeeper logbook is after I complete the QSO and log the contact. Is there another setting I need to enable in order for this to work properly for me again?

Thanks,

Scott/KN3A

Re: Merry Christmas and Happy Hanukkah to all who celebrate

Andrew OBrien
 

Thanks for your hard work Dave . Merry Christmas and Happy Hanukkah to you and yours . Peace in 2020 .

Andy

On Dec 23, 2019, at 2:47 PM, Dave AA6YQ <@AA6YQ> wrote:

I wish you a 2020 full of happiness, excellent health, and good DX!

I could not be happier with the way this discussion group works; your continuing contribution to its friendliness, responsiveness,
and accuracy are greatly appreciated!

73,

Dave, AA6YQ





Re: Merry Christmas and Happy Hanukkah to all who celebrate

Russ Ravella
 

Happy Holidays to you too Dave, and to your family and all your loved ones as well !

And thank you so much for your skillful and patient support and for the amazing DXLab Suite.

Best DX and 73,
Russ, KR6W



On Dec 23, 2019, at 3:15 PM, Björn Ekelund, SM7IUN <bjorn@...> wrote:

I wish you and your family the same, Dave. 

Your contribution to the amateur radio community is second to none.
We are so many who owe you so much.

Björn SM7IUN


Den mån 23 dec. 2019 kl 20:47 skrev Dave AA6YQ <aa6yq@...>:
I wish you a 2020 full of happiness, excellent health, and good DX!

I could not be happier with the way this discussion group works; your continuing contribution to its friendliness, responsiveness,
and accuracy are greatly appreciated!

        73,

              Dave, AA6YQ







Re: Refreshing DXKeeper Log Display after logging a QSO

Bill Pence
 

did you try clicking the "X" (close box) to the right of the text box entry fielsdin the filter window at the bottom of dxkeeper to unfilter the log?


On Mon, Dec 23, 2019 at 7:34 PM <k8grr@...> wrote:
My experience has been that after I log a QSO, the only QSO appearing in my log is the QSO that I just logged. In order to display my full log (including the 
QSO just recorded) I find it necessary to close and reopen DXKeeper. I know that there must be a much simpler way to do this - but at the moment, I'm stumped.

Any tips would be appreciated.

Thanks, Brian K8GRR

Refreshing DXKeeper Log Display after logging a QSO

Brian Deuby
 

My experience has been that after I log a QSO, the only QSO appearing in my log is the QSO that I just logged. In order to display my full log (including the 
QSO just recorded) I find it necessary to close and reopen DXKeeper. I know that there must be a much simpler way to do this - but at the moment, I'm stumped.

Any tips would be appreciated.

Thanks, Brian K8GRR

Saving Changes to DX Keeper Display Configuration

Brian Deuby
 

I would like to permanently delete the "Auxiliary" and "QSL" fields from the "Log QSO's" tab page of DXKeeper, but even though I uncheck these fields in the 
DXKeeper "Log QSO's" page and from the DXKeeper Log Configuration page (and save the changes) - those fields keep reappearing and the "Station Call" and "QTH" labels keep blinking at me. I have attempted to control double-click these blinking labels and fill the corresponding fields, but this does not seem to help. I don't use the 
"Axiliary" and "QSL" fields and would just like to permanently suppress them.

Thanks, 

Brian K8GRR

Re: Sending Real CW

Ron Rosson
 

Tom (Win4Icom Author) recommends a winkeyer from K1EL or build your own.

I love my winkeyer and it works perfectly with both DXLab and Win4Icom.

--
73 de KF5JRA
Ron
kf5jra at oneinsane dot org

On Dec 23, 2019, at 1:47 PM, Dave Fugleberg <davefugleberg@...> wrote:

Mark, you mentioned you're using Win4Icom. If that works like Win4K3, that may be your issue.
I used to use DTR keying for CW on my K3, but found that it didn't work through Win4K3. I checked with Tom, VA2FSQ, and he told me that the virtual  radio com ports in Win4K3 do not pass those handshake lines. You might check with him to see if that's true with Win4Icom as well.
I worked around the problem by adding a Winkeyer clone to my station.

On Mon, Dec 23, 2019 at 2:27 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

Thank you for the information

Looking at my WW configuration

All I have set in the CW' Keying Section is

PTT port (com8):  DTR


So maybe it is defaulting to CAT control ?

 It works well.

My Icom control ports are Com 7 and Com 8

+ That means WinWarbler is wiggling the DTR signal on COM8 to generate dots and dashes. Assuming you have Commander running, you might try switching that panel to "Xcvr Ctrl App" to see if you like it better.

         73,

                Dave, AA6YQ





Re: Sending Real CW

Mark Robinson
 

OK thanks Dave,

Glad we sorted this out.

I did get WW taking to my RigBlaster through a Com port but although the RB front led was flashing the rig was not keying. I think the RB switching transistor must be damaged but it isn't something that I will use right now.

I hope Win4Icom gets 'fixed" sometime in the future.

Thanks for all your help.   It looks like I should get a WinKey as a good interface device for all these cw programs.

73 Mark N1UK

Re: Sending Real CW

Tom Schaefer NY4I
 

To answer Dave’s thought about others using it, TR4W uses the CW by serial port feature. I added what I call CWBYCAT to the TR4W contest logger. Mostly Elecraft, late Icom and Kenwood rigs. All done with serial port commands natively generated by the program (versus hard coded command sequences in macros).

Tom NY4I

Principal Solutions Architect
Better Software Solutions, Inc.
727-437-2771

Re: Sending Real CW

Dave AA6YQ
 

+ AA6YQ comments below

I am running through Win4Icom with a Com0Com virtual com port to my IC 7610

+ Win4Icom doesn't convey the "CW Speed" instruction to your radio. I reported this to Tom awhile ago.

73,

Dave, AA6YQ

On 23-Dec-19 6:15 PM, Dave AA6YQ wrote:
Thanks, Mark.

The errorlog shows that Commander is not receiving a response to the "change CW speed" CAT commands it is sending to your IC-7700, for example:

2019-12-23 22:26:48.707 > CIVModule.DisplayLine: Port = P, Hex = FE FE 98 E0 14 C 0 67 FD
2019-12-23 22:26:48.707 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 1
2019-12-23 22:26:48.737 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 2
2019-12-23 22:26:48.770 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 3
2019-12-23 22:26:48.800 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 4
2019-12-23 22:26:48.830 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 5
2019-12-23 22:26:48.863 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 6
2019-12-23 22:26:48.895 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 7
2019-12-23 22:26:48.924 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 8
2019-12-23 22:26:48.955 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 9
2019-12-23 22:26:48.988 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 10
2019-12-23 22:26:48.988 > response timeout SetCWSpeed

Your IC-7700 occasionally does not respond to a "read meter" request:

2019-12-23 22:26:47.849 > CIVModule.SendCommand: FE FE 98 E0 15 11 FD
2019-12-23 22:26:47.879 > CIVModule.DisplayLine: Port = P, Hex = FE FE 98 E0 15 11 FD
2019-12-23 22:26:47.879 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 1
2019-12-23 22:26:47.910 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 2
2019-12-23 22:26:47.941 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 3
2019-12-23 22:26:47.974 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 4
2019-12-23 22:26:48.005 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 5
2019-12-23 22:26:48.038 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 6
2019-12-23 22:26:48.065 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 7
2019-12-23 22:26:48.098 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 8
2019-12-23 22:26:48.128 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 9
2019-12-23 22:26:48.159 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 10
2019-12-23 22:26:48.159 > response timeout Request meter

Is your computer connected directly to the radio, or is there an "intermediary"?

73,

Dave, AA6YQ




Re: Sending Real CW

Mark Robinson
 

I am running through Win4Icom with a Com0Com virtual com port to my IC 7610

Mark N1UK

On 23-Dec-19 6:15 PM, Dave AA6YQ wrote:
Thanks, Mark.

The errorlog shows that Commander is not receiving a response to the "change CW speed" CAT commands it is sending to your IC-7700, for example:

2019-12-23 22:26:48.707 > CIVModule.DisplayLine: Port = P, Hex = FE FE 98 E0 14 C 0 67 FD
2019-12-23 22:26:48.707 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 1
2019-12-23 22:26:48.737 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 2
2019-12-23 22:26:48.770 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 3
2019-12-23 22:26:48.800 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 4
2019-12-23 22:26:48.830 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 5
2019-12-23 22:26:48.863 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 6
2019-12-23 22:26:48.895 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 7
2019-12-23 22:26:48.924 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 8
2019-12-23 22:26:48.955 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 9
2019-12-23 22:26:48.988 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 10
2019-12-23 22:26:48.988 > response timeout SetCWSpeed

Your IC-7700 occasionally does not respond to a "read meter" request:

2019-12-23 22:26:47.849 > CIVModule.SendCommand: FE FE 98 E0 15 11 FD
2019-12-23 22:26:47.879 > CIVModule.DisplayLine: Port = P, Hex = FE FE 98 E0 15 11 FD
2019-12-23 22:26:47.879 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 1
2019-12-23 22:26:47.910 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 2
2019-12-23 22:26:47.941 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 3
2019-12-23 22:26:47.974 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 4
2019-12-23 22:26:48.005 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 5
2019-12-23 22:26:48.038 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 6
2019-12-23 22:26:48.065 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 7
2019-12-23 22:26:48.098 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 8
2019-12-23 22:26:48.128 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 9
2019-12-23 22:26:48.159 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 10
2019-12-23 22:26:48.159 > response timeout Request meter

Is your computer connected directly to the radio, or is there an "intermediary"?

73,

Dave, AA6YQ



Re: Sending Real CW

Dave AA6YQ
 

Thanks, Mark.

The errorlog shows that Commander is not receiving a response to the "change CW speed" CAT commands it is sending to your IC-7700, for example:

2019-12-23 22:26:48.707 > CIVModule.DisplayLine: Port = P, Hex = FE FE 98 E0 14 C 0 67 FD
2019-12-23 22:26:48.707 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 1
2019-12-23 22:26:48.737 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 2
2019-12-23 22:26:48.770 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 3
2019-12-23 22:26:48.800 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 4
2019-12-23 22:26:48.830 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 5
2019-12-23 22:26:48.863 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 6
2019-12-23 22:26:48.895 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 7
2019-12-23 22:26:48.924 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 8
2019-12-23 22:26:48.955 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 9
2019-12-23 22:26:48.988 > CIVModule.ExecuteNextXcvrCmd awaiting response from SetCWSpeed, count = 10
2019-12-23 22:26:48.988 > response timeout SetCWSpeed

Your IC-7700 occasionally does not respond to a "read meter" request:

2019-12-23 22:26:47.849 > CIVModule.SendCommand: FE FE 98 E0 15 11 FD
2019-12-23 22:26:47.879 > CIVModule.DisplayLine: Port = P, Hex = FE FE 98 E0 15 11 FD
2019-12-23 22:26:47.879 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 1
2019-12-23 22:26:47.910 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 2
2019-12-23 22:26:47.941 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 3
2019-12-23 22:26:47.974 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 4
2019-12-23 22:26:48.005 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 5
2019-12-23 22:26:48.038 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 6
2019-12-23 22:26:48.065 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 7
2019-12-23 22:26:48.098 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 8
2019-12-23 22:26:48.128 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 9
2019-12-23 22:26:48.159 > CIVModule.ExecuteNextXcvrCmd awaiting response from Request meter, count = 10
2019-12-23 22:26:48.159 > response timeout Request meter

Is your computer connected directly to the radio, or is there an "intermediary"?

73,

Dave, AA6YQ

Re: SC not showing spots

Rod Greene
 

Thanks Dave, I'm pretty sure I have it working well now. Was the port # that I had wrong. Thanks Ron for spotting that.

73 and best Holiday Wishes to all. Sure appreciate your excellent support Dave!    - Rod/w7zrc

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

On Monday, December 23, 2019, 12:05:27 PM MST, Dave AA6YQ <aa6yq@...> wrote:


+ AA6YQ comments below

+ Assuming that a spot arrives from one of SpotCollector's connected Spot Sources, there are several reasons why it might not be used to update your Spot Database -- either by creating a first Spot Database Entry for the spotted station (on the spotted band in the spotted mode) or by updating an existing Spot Database Entry for that station (on the spotted band in the spotted mode):

1. the spot is "too old"

1a. check the "Maximum Age of incoming spots" setting on the Configuration window's "Spot Database" tab; I recommend 60 (minutes)

1b. check that your computer's time and time zone have been set correctly (often the root cause of "no spot database entries" disease after installing SpotCollector on a new computer)

2. the spotted callsign is listed in SpotCollector's "Special Callsign" list with no tag (meaning "ignore incoming spots of this callsign")

3. the callsign of the station that generated the spot is listed in SpotCollector's "Special Callsign" list with a "badsource" tag (meaning "ignore incoming spots generated by this callsign")


+ If an incoming spot does create or update an entry in the Spot Database, its visibility in the Spot Database Display is governed by your filter settings, as described in

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


+ Unless the caption of the Filter panel at the bottom of SpotCollector's Main window is "Filter: None", your view of the Spot Database is being filtered.

+ To remove all filtering from the Spot Database Display, depress the CTRL key while clicking the Filter panel's X button.


+ For more information, see

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


          73,


                Dave, AA6YQ






Re: Rsba1 and DXLab

Ed Pflueger <ab4iq@...>
 

I use WIN4K3Suite with com0com and can run 6 different programs into my K3S My K3 goes into Tom's program as Com5 then I set up 6 pairs 8/9, 10/11, 12/13, 14/15, 16/17 and 18/19 in com0com. For example WIN4K3Suite pair 8 is for DXBase and I set the com port in DXBase for com9. That way I can run DXLab on pairs 10/11, N1MM on 12/13, DX4WIN on 14/15, ACLOG on 16/17 and WSJT-X on 18/19. The reason for the various logging programs is I'm trying to get away from DXBase but I run all of them at the same time. Friends think I'm nuts and maybe I am. HI HI.. However so far DXLab is winning the race. I've already deleted HRD, just not my type of program.

Ed.. AB4IQ

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ
Sent: Monday, December 23, 2019 4:24 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Rsba1 and dxlab

+ AA6YQ comments below

I am installing rsba1, icom remote radio software, on my pc that runs dxlab ans is connected to my icom7300 through com3 via usb.
Can both software coexist without collision?

+ Two different applications cannot simultaneously control the same transceiver.

+ The only reliable way to do that is with an application the provides multiple applications with the ability to interact with a "virtual transceiver", and then keeps the actual transceiver in sync with that "virtual transceiver". That's how Commander's Secondary CAT Port works. Win4KSuite for Icom works this way as well. I don't know if Win4KSuite for Icom would enable both Commander and RSBA1 to simultaneously control your 7300. You could ask its author, Tom VA2FSQ.

73,

Dave, AA6YQ