Date   
Re: DXLab Suite - SmartSDR help needed

K4PX K4PX
 

Please let me know when the new version is available so I can try it on my Flex thank you very much hopefully it will fix my problem


On Fri, Apr 19, 2019, 4:46 PM Dave AA6YQ <aa6yq@...> wrote:
As has been reported here several times over the past weeks, the current version of Commander cannot reliably switch SmartSDR version 3 between TX and RX. Jamie WW3S and I are working with Flex personnel to determine why this is happening.

I've already updated the next version of Commander to handle a change in API command syntax in SmartSDR v3 that prevents the current version of Commander from muting a VFO. After we've resolved the "TX-RX" issue and Jamie confirms correct operation, I will make the new version of Commander publicly available.

       73,

             Dave, AA6YQ

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Jeff Schwartz via Groups.Io
Sent: Friday, April 19, 2019 10:27 AM
To: DXLab@groups.io
Subject: Re: [DXLab] DXLab Suite - SmartSDR help needed

Gary,
Congrats on your 6600 purchase. It’s an amazing rig. Version 3.0.19 actually seems to continue to work well with most DX Labs applications as far as I can tell EXCEPT for the biggie TX /RX control. This has only affected WSJT-X and WinWarbler for me. Flex PTT, however, is easily control by creating an SDR CAT port for WSJT-X and an SDR CAT PTT port for WinWarbler. Both WSJT-X and WinWarbler need to be reconfigured to make that work but it is a simple process once you create the two ports mentioned in SDR CAT. WSJT-X needs to be configured for control by Flex instead of controlled by DX. lab Suites. As for CW and SSB PTT WinWarbler did not require any changes for me if I’m sending CW from WinWarbler or using my PTT hand switch plugged into the Flex.

You our are welcome to contact me at ki0kb@... and I can send you pictures on how to set this up.

Jeff Schwartz





Re: DXLab Suite - SmartSDR help needed

Dave AA6YQ
 

+ AA6YQ comments below

Please let me know when the new version is available so I can try it on my Flex thank you very much hopefully it will fix my problem

+ Every public release of every DXLab application is announced here.

73,

Dave, AA6YQ

Re: DXLab Suite - SmartSDR help needed

K4PX K4PX
 

Ok thanks Dave.
Joe

On Fri, Apr 19, 2019, 11:45 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

Please let me know when the new version is available so I can try it on my Flex thank you very much hopefully it will fix my problem

+ Every public release of every DXLab application is announced here.

       73,

               Dave, AA6YQ





Can't Upgrade Most DXLab Suite Apps

KE0CP
 

This may have been covered in a previous thread but I couldn't find it.
When I try to upgrade most apps such as Commander and DXKeeper the downloading window just freezes after downloading the update .exe file. Eventually I have to abort the process. The ErrorLog.txt file shows:
>DXQSLModule.ConfigureQSLTable: Unable to open QSLQueue C:\DXLab\DXKeeper\Databases\KE0CP.mdb<
and the shutsdown.
This seemed to happen after some prior Windows 10 update, as I have not done anything with the DXLab installation. I have removed all of the Suite's components with Windows' Control Panel | Programs and Features function and reinstalled DXLab Suite but when the installer attempts to upgrade each component they still freeze.
Any help would be greatly appreciated.
BTW: I do have the DXLab Suite running on another computer and it upgrades the programs just fine.

Re: Can't Upgrade Most DXLab Suite Apps

Dave AA6YQ
 

+ AA6YQ comments below

This may have been covered in a previous thread but I couldn't find it.
When I try to upgrade most apps such as Commander and DXKeeper the downloading window just freezes after downloading the update .exe file. Eventually I have to abort the process. The ErrorLog.txt file shows:
DXQSLModule.ConfigureQSLTable: Unable to open QSLQueue C:\DXLab\DXKeeper\Databases\KE0CP.mdb<
and the shutsdown.
This seemed to happen after some prior Windows 10 update, as I have not done anything with the DXLab installation. I have removed all of the Suite's components with Windows' Control Panel | Programs and Features function and reinstalled DXLab Suite but when the installer attempts to upgrade each component they still freeze.
Any help would be greatly appreciated.
BTW: I do have the DXLab Suite running on another computer and it upgrades the programs just fine.

+ Please reboot Windows into "Safe Mode with Networking". Then start the Launcher, and attempt to upgrade one of your DXLab applications. Does the upgrade succeed?

73,

Dave, AA6YQ

Commander and N1MM

Chris
 

I'm sure I'm missing something either in DXLabs docs or in the 900 page N1MM manual.  Today I installed N1MM according to their instructions but when I tried to run N1MM with the DXLab Suite running, up popped the error message that "COM4 is in use by another program".  That's very true and obviously N1MM and Commander can't share.  So the question is, how does one get around this situation?  WSJT seems to handle it by allowing Commander to do the controlling but that option doesn't seem to be available in N1MM.  I have a suspicion that this is just the beginning of the challenge or running N1MM with DXLab.  I've got the Gateway installed but that seems to address a different operation.

Thanks for any daylight Dave or another user can shed to get me started down the path.

Chris NØCC

Re: Commander and N1MM

Pete Smith
 

Chris, you need some sort of COM port sharing app.  There are several, but I've had good experience with LP-Bridge by Telepost.  There are a couple of versions so make sure you get the right one for your radio.

73, Pete N4ZR
Check out the Reverse Beacon Network 
at <http://reversebeacon.net>, now 
spotting RTTY activity worldwide. 
For spots, please use your favorite 
"retail" DX cluster.
On 4/20/2019 2:43 PM, Chris wrote:

I'm sure I'm missing something either in DXLabs docs or in the 900 page N1MM manual.  Today I installed N1MM according to their instructions but when I tried to run N1MM with the DXLab Suite running, up popped the error message that "COM4 is in use by another program".  That's very true and obviously N1MM and Commander can't share.  So the question is, how does one get around this situation?  WSJT seems to handle it by allowing Commander to do the controlling but that option doesn't seem to be available in N1MM.  I have a suspicion that this is just the beginning of the challenge or running N1MM with DXLab.  I've got the Gateway installed but that seems to address a different operation.

Thanks for any daylight Dave or another user can shed to get me started down the path.

Chris NØCC

Re: Win 10 ?????

Mike Rhodes
 

John,
  I could be wrong but I don't think the free upgrade to Win10 is available anymore. If not, I would suggest investing in new or reconditioned hardware (including Win10) rather than putting out over $100 for Win10 alone. You can get a reconditioned I5 or I7 based computer, again, with Win10, for a couple hundred dollars. Got my last one thru Walmart and couldn't be happier. I upgraded it to a SSD and maxed the RAM but wouldn't of had to do either.

Mike / W8DN

On 4/19/2019 5:15 PM, n4qwf . wrote:
Thanks for all the comments. Sounds like a clean install would be the way to go. I will still likely wait until I have no choice but move to Win 10. When Dave says he is still holding on to Win 7 that sure impresses me.

When I got the Flex Radio I set it up using a computer that was built especially for the system. It has always preformed excellently. It has handled PowerSDR, DXLab, WSJT-X, N1MM all running at the same time without issue. I do not use it for email and other internet chores even though it is connected to my in house network and the internet.

I guess for now I will follow the advise "if it ain't broke don't fix it".

Thanks <<John N4QWF

Re: Commander and N1MM

Floyd - K8AC
 

Hi Chris.  I run the two together with no problems.  I first set up a pair of virtual com ports to provide a path between N1MM and DXLab Commander.  In my case, the pair is COM14 and COM15.  COM14 is defined in N1MM Configure ports as a TS-480 with parameters 38400,N,8,1. Enable both HW and SW PTT is checked.  COM15 is then defined in Commander config as the Secondary CAT Port with same parameters.  Check the enable box.  Choose Kenwood as rig protocol.  Select "follow and lead primary". That path allows N1MM to access the frequency info from Commander.  One thing not supported that way: if you have a macro in N1MM to set the transceiver RIT to zero, that is not passed to Commander and will be lost. 

73, Floyd - K8AC

Re: Commander and N1MM

Dave AA6YQ
 

+ AA6YQ comments below

I'm sure I'm missing something either in DXLabs docs or in the 900 page N1MM manual. Today I installed N1MM according to their instructions but when I tried to run N1MM with the DXLab Suite running, up popped the error message that "COM4 is in use by another program". That's very true and obviously N1MM and Commander can't share. So the question is, how does one get around this situation? WSJT seems to handle it by allowing Commander to do the controlling but that option doesn't seem to be available in N1MM. I have a suspicion that this is just the beginning of the challenge or running N1MM with DXLab. I've got the Gateway installed but that seems to address a different operation.

Thanks for any daylight Dave or another user can shed to get me started down the path.

+ The only way to have more than one application control the same transceiver is by using a CAT port sharing application. I'm only aware of two reliable implementations of CAT port sharing: Win4IcomSuite and Win4YaesuSuite:

<https://icom.va2fsq.com/>

<https://yaesu.va2fsq.com/>

+ LP Bridge claims to provide this capability for Elecraft radios, but has proven to be unreliable.

+ Low-level port sharing applications like com0com are ignorant of CAT protocols, and thus cannot be used for this purpose.

+ Why do you want to run DXLab and N1MM simultaneously?

+ During contests, many ops run DXKeeper, and use the N1MM-DXKeeper bridge so that QSOs are logged to N1MM are also logged to DXKeeper.

<https://www.dxlabsuite.com/N1MM-DXKeeper/index.htm>

+ You can also run DXLab components like SpotCollector, DXView, and PropView in parallel with N1MM, though any function dependent on Commander running will not be available.

73,

Dave, AA6YQ

Re: Commander and N1MM

Chris
 

Floyd,

That looks like a pretty clean method. What virtual port software are you using? I’m running Win10 on the station computer,

Chris NØCC


On Apr 20, 2019, at 2:59 PM, Floyd Sense <wj@...> wrote:

Hi Chris.  I run the two together with no problems.  I first set up a pair of virtual com ports to provide a path between N1MM and DXLab Commander.  In my case, the pair is COM14 and COM15.  COM14 is defined in N1MM Configure ports as a TS-480 with parameters 38400,N,8,1. Enable both HW and SW PTT is checked.  COM15 is then defined in Commander config as the Secondary CAT Port with same parameters.  Check the enable box.  Choose Kenwood as rig protocol.  Select "follow and lead primary". That path allows N1MM to access the frequency info from Commander.  One thing not supported that way: if you have a macro in N1MM to set the transceiver RIT to zero, that is not passed to Commander and will be lost. 

73, Floyd - K8AC

Re: Commander and N1MM

Chris
 

Dave,

Excuse me while I execute a classic dope slap. Ha. I was just assuming that since DXKeeper was doing the logging, I would be using the whole suite.  Back to the drawing board, enlightened.  Thanks a million.

Chris NØCC


On Apr 20, 2019, at 3:06 PM, Chris <clcarson@...> wrote:

Floyd,

That looks like a pretty clean method. What virtual port software are you using? I’m running Win10 on the station computer,

Chris NØCC


On Apr 20, 2019, at 2:59 PM, Floyd Sense <wj@...> wrote:

Hi Chris.  I run the two together with no problems.  I first set up a pair of virtual com ports to provide a path between N1MM and DXLab Commander.  In my case, the pair is COM14 and COM15.  COM14 is defined in N1MM Configure ports as a TS-480 with parameters 38400,N,8,1. Enable both HW and SW PTT is checked.  COM15 is then defined in Commander config as the Secondary CAT Port with same parameters.  Check the enable box.  Choose Kenwood as rig protocol.  Select "follow and lead primary". That path allows N1MM to access the frequency info from Commander.  One thing not supported that way: if you have a macro in N1MM to set the transceiver RIT to zero, that is not passed to Commander and will be lost. 

73, Floyd - K8AC

Re: Commander and N1MM

Dave AA6YQ
 

+ AA6YQ comments below

Hi Chris. I run the two together with no problems. I first set up a pair of virtual com ports to provide a path between N1MM and DXLab Commander. In my case, the pair is COM14 and COM15. COM14 is defined in N1MM Configure ports as a TS-480 with parameters 38400,N,8,1. Enable both HW and SW PTT is checked. COM15 is then defined in Commander config as the Secondary CAT Port with same parameters. Check the enable box. Choose Kenwood as rig protocol. Select "follow and lead primary". That path allows N1MM to access the frequency info from Commander. One thing not supported that way: if you have a macro in N1MM to set the transceiver RIT to zero, that is not passed to Commander and will be lost.

+ This is the first I've heard that N1MM will happily run when connected to Commander's Secondary CAT port.

73,

Dave, AA6YQ

Re: Commander and N1MM

ve3ki
 

If you are specifically interested in doing FT8 from WSJT-X with N1MM+ doing the logging (contest operation), I suggest you consult <http://n1mm.hamdocs.com/tiki-index.php?page=WSJT-X+Decode+List&structure=N1MM+Logger+Documentation>, and in particular FAQ 5.1. This is probably not worth the bother for normal non-contest operation, but during a contest the duplicate and multiplier checking from N1MM+ is very worthwhile.

73,
Rich VE3KI


On Sat, Apr 20, 2019 at 02:43 PM, Chris wrote:
I'm sure I'm missing something either in DXLabs docs or in the 900 page N1MM manual.  Today I installed N1MM according to their instructions but when I tried to run N1MM with the DXLab Suite running, up popped the error message that "COM4 is in use by another program".  That's very true and obviously N1MM and Commander can't share.  So the question is, how does one get around this situation?  WSJT seems to handle it by allowing Commander to do the controlling but that option doesn't seem to be available in N1MM.  I have a suspicion that this is just the beginning of the challenge or running N1MM with DXLab.  I've got the Gateway installed but that seems to address a different operation.

Thanks for any daylight Dave or another user can shed to get me started down the path.

Chris NØCC

Re: Commander and N1MM

Chris
 

Good info, Rich, thanks. That will be another layer in the operation.

Chris NØCC


On Apr 20, 2019, at 3:23 PM, ve3ki <ve3iay@...> wrote:

If you are specifically interested in doing FT8 from WSJT-X with N1MM+ doing the logging (contest operation), I suggest you consult <http://n1mm.hamdocs.com/tiki-index.php?page=WSJT-X+Decode+List&structure=N1MM+Logger+Documentation>, and in particular FAQ 5.1. This is probably not worth the bother for normal non-contest operation, but during a contest the duplicate and multiplier checking from N1MM+ is very worthwhile.

73,
Rich VE3KI


On Sat, Apr 20, 2019 at 02:43 PM, Chris wrote:
I'm sure I'm missing something either in DXLabs docs or in the 900 page N1MM manual.  Today I installed N1MM according to their instructions but when I tried to run N1MM with the DXLab Suite running, up popped the error message that "COM4 is in use by another program".  That's very true and obviously N1MM and Commander can't share.  So the question is, how does one get around this situation?  WSJT seems to handle it by allowing Commander to do the controlling but that option doesn't seem to be available in N1MM.  I have a suspicion that this is just the beginning of the challenge or running N1MM with DXLab.  I've got the Gateway installed but that seems to address a different operation.

Thanks for any daylight Dave or another user can shed to get me started down the path.

Chris NØCC

Re: Win 10 ?????

n4qwf .
 

Thanks Mike, That sounds like a viable solution. I will keep it in mind for the future.

73<<John

Re: Commander and N1MM

Floyd - K8AC
 

I'm using VSP Manager from K5FR.  If you're a licensed ham, k5FR will send you a free copy.  You could also use VSPE and there are a couple of others as well.

Re: Commander and N1MM

Floyd - K8AC
 

Yes - works just fine.   It would be perfect if Commander would only pass the RIT reset command through to the connected transceiver via the secondary CAT port.  Any chance of that?

Re: Commander and N1MM

Joe Subich, W4TV
 

On 2019-04-20 3:05 PM, Dave AA6YQ wrote:
+ The only way to have more than one application control the same transceiver is by using a CAT port sharing application. I'm only aware of two reliable implementations of CAT port sharing:
Win4IcomSuite and Win4YaesuSuite:

<https://icom.va2fsq.com/>

<https://yaesu.va2fsq.com/>
Also Win4K3Suite for Elecraft K3, K3S, KX3 and KX2 ...

https://va2fsq.com/

73,

... Joe, W4TV


On 2019-04-20 3:05 PM, Dave AA6YQ wrote:
+ AA6YQ comments below
I'm sure I'm missing something either in DXLabs docs or in the 900 page N1MM manual. Today I installed N1MM according to their instructions but when I tried to run N1MM with the DXLab Suite running, up popped the error message that "COM4 is in use by another program". That's very true and obviously N1MM and Commander can't share. So the question is, how does one get around this situation? WSJT seems to handle it by allowing Commander to do the controlling but that option doesn't seem to be available in N1MM. I have a suspicion that this is just the beginning of the challenge or running N1MM with DXLab. I've got the Gateway installed but that seems to address a different operation.
Thanks for any daylight Dave or another user can shed to get me started down the path.
+ The only way to have more than one application control the same transceiver is by using a CAT port sharing application. I'm only aware of two reliable implementations of CAT port sharing: Win4IcomSuite and Win4YaesuSuite:
<https://icom.va2fsq.com/>
<https://yaesu.va2fsq.com/>
+ LP Bridge claims to provide this capability for Elecraft radios, but has proven to be unreliable.
+ Low-level port sharing applications like com0com are ignorant of CAT protocols, and thus cannot be used for this purpose.
+ Why do you want to run DXLab and N1MM simultaneously?
+ During contests, many ops run DXKeeper, and use the N1MM-DXKeeper bridge so that QSOs are logged to N1MM are also logged to DXKeeper.
<https://www.dxlabsuite.com/N1MM-DXKeeper/index.htm>
+ You can also run DXLab components like SpotCollector, DXView, and PropView in parallel with N1MM, though any function dependent on Commander running will not be available.
73,
Dave, AA6YQ

Re: Win 10 ?????

Floyd - K8AC
 

A clean install is the best thing to do.
Nothing at all wrong with a clean install, but I wouldn't agree that it's the best thing to do.  My Win 10 system started out as a Win 7 system years ago and I've done nothing but upgrades to the system over that time.  I allow Windows to manage the updates and apply them as they come out.  My system is rather complex and in all that time I've had just a single problem and that was a short time ago when an update added the feature of restricting application access to sound cards.  Other than that, there have been zero problems.  I've run most of the common and a few uncommon radio applications with no glitches.  Could be I'm just incredibly lucky, but I think most radio folks are needlessly clinging to the past Windows versions.  It would be interesting to know exactly what the leftover trash is that people often mention.  I routinely manage what's installed on the system and remove any programs I don't want or need and clean the Registry every now and then.