Date   

locked Re: Problem with JTAlert 2.16.17

Tom Melvin
 

Norman

UN-Tick the 'Resend WSJT-X UDP Packets' in JTalert.

JTA will automatically work out the settings - having that option ticked will cause a loop.

Tom
GM8MJV


On 24 Feb 2021, at 02:56, Norman Heyen <norman.heyen@...> wrote:

Hi Laurie,
These are the two areas I was asking if they should match IP Address and UDP Port

Like I said, everything works well for v2.16.10 but when I updated to 2.16.17 (and a couple prior versions) it doesn't work. I get an error message. 
Windows info is:
Edition Windows 10 Pro
Version 20H2
Installed on ‎11/‎26/‎2020
OS build 19042.804
Experience Windows Feature Experience Pack 120.2212.551.0
 
WSJTx populates and works like it should but the contacts never populate the JTAlert windows

Thanks for any pointers,
Norman


locked Re: Problem with JTAlert 2.16.17

Norman Heyen
 

Hi Laurie,
These are the two areas I was asking if they should match IP Address and UDP Port

Like I said, everything works well for v2.16.10 but when I updated to 2.16.17 (and a couple prior versions) it doesn't work. I get an error message. 
Windows info is:
Edition Windows 10 Pro
Version 20H2
Installed on ‎11/‎26/‎2020
OS build 19042.804
Experience Windows Feature Experience Pack 120.2212.551.0
 
WSJTx populates and works like it should but the contacts never populate the JTAlert windows

Thanks for any pointers,
Norman


locked Re: Problem with JTAlert 2.16.17

HamApps Support (VK3AMA)
 

On 24/02/2021 8:36 am, Norman Heyen wrote:
Should the UDP Port and IP Address in JTAlert match the 2237 and 127.0.0.1 in WSJT-X ? Or have I messed those up as well?


What JTAlert UDP address & port are you referring to? If it is the Resend UDP settings, definitely DON'T change them to match WSJT-X, doing so will create a feedback loop with received UDP messages being sent back to the input ad infinitum.

An alternative to using 127.0.0.1, is to use a multicast IP address, like 239.255.0.1. See the JTAlert Help File, "WSJT-X / JTDX UDP Setup" topic (at root level of the help).
Missing in that help topic is the need to set JTAlert to use multicast on the loopback interface, via the "Settings -> WSJT-X UDP Multicast on Loopback" menu, make sure it is ticked. AND, due to recent changes in WSJT-X 2.3.0 is the need to ensure a loopback outgoing interface is selected in the UDP Server settings.

eg  my WSJT-X setup.

   

de Laurie VK3AMA


locked Re: JTAlert with JTDX and WSJT-X at the same time.

K0GU
 

  Thanks for the reply. I was afraid of that. I'm working on using two computers and making one a JTDX computer and one a WSJT-X computer. If Q65 gets popular enough to be adopted by JTDX in the future that would fix most of my problem.

thanks

73,  Jay  K0GU


locked Re: Problem with JTAlert 2.16.17

Norman Heyen
 

Hi Laurie,
Sorry for missing that but after changing it, closing out of the programs and rebooting the PC I still get the error message, only the address has changed.

Unable to communicate with the WSJT-X process.
  UDP Port : 2237
  IP Address : 127.0.0.1
  Values read from WSJT-X config file...
    C:\Users\nheye\AppData\Local\WSJT-X\WSJT-X.ini

WSJT-X Detected Instance...
  Process Window Title : WSJT-X   v2.3.0   by K1JT, G4WJS, and K9AN
  Process Command Line : "C:\WSJT\wsjtx\bin\wsjtx.exe"

Decode alerts and logging will be unavailable until corrected.

Should the UDP Port and IP Address in JTAlert match the 2237 and 127.0.0.1 in WSJT-X ? Or have I messed those up as well?

Thanks for your help,
Norman


On Tue, Feb 23, 2021 at 3:13 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 24/02/2021 7:47 am, Norman Heyen wrote:
Thank you for your help Joe,
Unfortunately that is exactly what I have setup. I cannot seem to be able to make it work in any version later than 2.16.10 - works fine there but anything newer opens but gives me the error message.
Any other place that I can look?
Norman

On Tue, Feb 23, 2021 at 2:34 PM Joe Subich, W4TV <lists@...> wrote:


 > Unable to communicate with the WSJT-X process.
 >    UDP Port : 2237
 >    IP Address : 127.1.1.1
 >    Values read from WSJT-X config file...
 >      C:\Users\nheye\AppData\Local\WSJT-X\WSJT-X.ini

In WSJTX -> File -> Setting -> Reporting -> UDP Server

Set UDP Server (IP Address) = 127.0.0.1
Set UDP Server port number = 2237
Check "Accept UDP requests" and "notify on accepted UDP request"


Did you change the UDP Server IP address on WSJT-X as suggested. Try 127.0.0.1 rather than 127.1.1.1
You will need to restart JTAlert after any change in UDP Server settings.

de Laurie VK3AMA


locked Re: Issues with PTT not working #FT8

Joe Subich, W4TV
 

This is an issue with WSJTX and RigBlaster. Please take your question
to those organizations as it does not involve JTAlert.

The short answer is that you will need to use hardware PTT (for the
RigBlaster). Since Omni-Rig does not pass DTR through to the interface,
you will need separate serial ports for CAT and PTT. The exact
configuration will depend on your particular RigBlaster model.

You should seek assistance from the WSJTX and/or RigBlaster support
organizations. I suspect RigBlaster would be better positioned to
help.

73,

... Joe, W4TV

On 2021-02-23 3:22 PM, K9MTH@ARRL.NET wrote:
I am running an ICOM 756PROII, with a Rigblaster pro.  I am trying to get WSJT, JTAlert and Log4OMng working together.  Log4OMng seems to need Omnirig for CAT control, along with WSJT.  However if I "key" to CQ in FT8 mode in WSJT, the PTT does not engage in the Rigblaster, The transmit from WSJT does put the radio into XMIT, but without the PTT by the rigblaster, I get no signal from the computer to the radio.
Any thoughts??
Thanks,
Matt Hamm
K9MTH


locked Re: Feature Request for "Alert Types" screen (f1)

HamApps Support (VK3AMA)
 

On 24/02/2021 7:59 am, Mark W2OR via groups.io wrote:
Thank you for the addition several weeks ago of the Alert Types screen (Function key F1).  Unusually helpful.

Background:  I change the continent selection twice daily using Settings (F11), changed once in the morning hours, and once in the evening hours, depending on circumstances. Each change in Settings is the same, every day. Please see below.

Request:  The feature appearing in the Alert Types screen certainly helps matters as it shortens the time to make changes, and is very easy to navigate to.  It might be enhanced even further, and quicken the time it takes to change the selection of the various continents, if there were actually two such selections in the Alert Types screen, that is:  "Wanted Continent Set One" and "Wanted Continent Set Two".  Two of them there would shorten the time it takes to make the twice-daily changes in Settings.  They'd be selected or de-selected daily, depending on East-West propagation changes and morning and evening Grey Line changes.  

Thanks for the consideration.  //Mark

After reading your message twice. I still don't understand what your trying to achieve.

If you have Continents marked as needed, why are you changing them to not-needed depending on the time of day & propagation? If a Continent is needed in the Morning, how can it be not-needed in the Afternoon and then needed again the next morning? It is either needed or it is not, time of day and propagation should not come into it.

Please rephrase your request and explain why time-of-day and propagation is important. Sorry, but I am totally confused.

BTW, the Alerts Types Screen has been part of JTAlert for many years, it is not a recent addition.

de Laurie VK3AMA


locked Re: Problem with JTAlert 2.16.17

Joe Subich, W4TV
 

On 2021-02-23 3:47 PM, Norman Heyen wrote:

Unfortunately that is exactly what I have setup.
No, your IP address is different than what I suggested. 127.1.1.1 is
not the same as 127.0.0.1. Given the different address, it is quite
likely that there is a UDP server mis-match that is causing your
problem.

73,

... Joe, W4TV


On 2021-02-23 3:47 PM, Norman Heyen wrote:
Thank you for your help Joe,
Unfortunately that is exactly what I have setup. I cannot seem to be able to make it work in any version later than 2.16.10 - works fine there but anything newer opens but gives me the error message.
Any other place that I can look?
Norman
On Tue, Feb 23, 2021 at 2:34 PM Joe Subich, W4TV <lists@subich.com <mailto:lists@subich.com>> wrote:
 > Unable to communicate with the WSJT-X process.
 >    UDP Port : 2237
 >    IP Address : 127.1.1.1
 >    Values read from WSJT-X config file...
 >      C:\Users\nheye\AppData\Local\WSJT-X\WSJT-X.ini
In WSJTX -> File -> Setting -> Reporting -> UDP Server
Set UDP Server (IP Address) = 127.0.0.1
Set UDP Server port number = 2237
Check "Accept UDP requests" and "notify on accepted UDP request"
73,
    ... Joe, W4TV
On 2021-02-23 10:47 AM, Norman Heyen wrote:
> I have been having issues with JTAlert versions after version 2.16.10
>
> Version 2.16.10 works well with my setup but it is time to
update. My
> setup is:
> DXLab Suite working with WSJT-X version 2.3.0
> Running Windows 10 20H2 fully patched to current levels
>
> With 2.16.10, everything works fine, logging and all that. But with
> 2.16.17, nothing is filled in the main window and I get
this error message:
> Unable to communicate with the WSJT-X process.
>    UDP Port : 2237
>    IP Address : 127.1.1.1
>    Values read from WSJT-X config file...
>      C:\Users\nheye\AppData\Local\WSJT-X\WSJT-X.ini
>
> WSJT-X Detected Instance...
>    Process Window Title : WSJT-X   v2.3.0   by K1JT, G4WJS, and K9AN
>    Process Command Line : "C:\WSJT\wsjtx\bin\wsjtx.exe"
>
> Decode alerts and logging will be unavailable until corrected.
>
> So I am sure I've missed a step somewhere. Can someone point me
in the
> right direction?
> Thanks!
> Norman
> KC9NVN


locked Re: Issues with PTT not working #FT8

Laurie, VK3AMA
 

On 24/02/2021 7:22 am, K9MTH@ARRL.NET wrote:
Edit: If I uninstall Omnirig and reconfigure WSJT for the radio on "CAT" tab, then it does XMIT and receive as it should but no connectivity to Log4OM and JTAlert.

Any thoughts??

Thanks,
Matt Hamm
K9MTH
JTAlert has no concept of CAT control. It doesn't need it, it simply utilizes the frequency reported by the WSJT-X UDP Status message. Changing CAT configuration in WSJT_X WILL NOT AFFECT JTAlert.

If JTAlert is losing UDP connectivity to WSJT-X when you uninstall Omnirig, then you must be changing something else at the same time that is affecting the UDP setup. JTAlert doesn't use OmniRig or any of the rig control protocols of WSJT-X.

de Laurie VK3AMA


locked Re: JTAlert with JTDX and WSJT-X at the same time.

HamApps Support (VK3AMA)
 

On 23/02/2021 10:09 am, K0GU wrote:
Is there anyway I can make JTAlert work on both program at the same time? I'm using 3x JTDX instances, with 3x JTAlert JTDX, and 1x WSJT-X. JTAlert WSJT-X won't start because apparently because it thinks WSJT-X is the 4th instance of one of the programs?

thanks,

73,  Jay  K0GU

Sorry, JTAlert does not support a mixture of JTDX & WSJT-X concurrent instances. 16 instances are supported, but of only one type at any time, JTDX or WSJT-X.

de Laurie VK3AMA


locked Re: Problem with JTAlert 2.16.17

HamApps Support (VK3AMA)
 

On 24/02/2021 7:47 am, Norman Heyen wrote:
Thank you for your help Joe,
Unfortunately that is exactly what I have setup. I cannot seem to be able to make it work in any version later than 2.16.10 - works fine there but anything newer opens but gives me the error message.
Any other place that I can look?
Norman

On Tue, Feb 23, 2021 at 2:34 PM Joe Subich, W4TV <lists@...> wrote:


 > Unable to communicate with the WSJT-X process.
 >    UDP Port : 2237
 >    IP Address : 127.1.1.1
 >    Values read from WSJT-X config file...
 >      C:\Users\nheye\AppData\Local\WSJT-X\WSJT-X.ini

In WSJTX -> File -> Setting -> Reporting -> UDP Server

Set UDP Server (IP Address) = 127.0.0.1
Set UDP Server port number = 2237
Check "Accept UDP requests" and "notify on accepted UDP request"


Did you change the UDP Server IP address on WSJT-X as suggested. Try 127.0.0.1 rather than 127.1.1.1
You will need to restart JTAlert after any change in UDP Server settings.

de Laurie VK3AMA


locked Feature Request for "Alert Types" screen (f1)

Mark W2OR
 

Thank you for the addition several weeks ago of the Alert Types screen (Function key F1).  Unusually helpful.

Background:  I change the continent selection twice daily using Settings (F11), changed once in the morning hours, and once in the evening hours, depending on circumstances. Each change in Settings is the same, every day. Please see below.

Request:  The feature appearing in the Alert Types screen certainly helps matters as it shortens the time to make changes, and is very easy to navigate to.  It might be enhanced even further, and quicken the time it takes to change the selection of the various continents, if there were actually two such selections in the Alert Types screen, that is:  "Wanted Continent Set One" and "Wanted Continent Set Two".  Two of them there would shorten the time it takes to make the twice-daily changes in Settings.  They'd be selected or de-selected daily, depending on East-West propagation changes and morning and evening Grey Line changes.  

Thanks for the consideration.  //Mark


locked Re: Problem with JTAlert 2.16.17

Norman Heyen
 

Thank you for your help Joe,
Unfortunately that is exactly what I have setup. I cannot seem to be able to make it work in any version later than 2.16.10 - works fine there but anything newer opens but gives me the error message.
Any other place that I can look?
Norman


On Tue, Feb 23, 2021 at 2:34 PM Joe Subich, W4TV <lists@...> wrote:


 > Unable to communicate with the WSJT-X process.
 >    UDP Port : 2237
 >    IP Address : 127.1.1.1
 >    Values read from WSJT-X config file...
 >      C:\Users\nheye\AppData\Local\WSJT-X\WSJT-X.ini

In WSJTX -> File -> Setting -> Reporting -> UDP Server

Set UDP Server (IP Address) = 127.0.0.1
Set UDP Server port number = 2237
Check "Accept UDP requests" and "notify on accepted UDP request"


73,

    ... Joe, W4TV


On 2021-02-23 10:47 AM, Norman Heyen wrote:
> I have been having issues with JTAlert versions after version 2.16.10
>
> Version 2.16.10 works well with my setup but it is time to update. My
> setup is:
> DXLab Suite working with WSJT-X version 2.3.0
> Running Windows 10 20H2 fully patched to current levels
>
> With 2.16.10, everything works fine, logging and all that. But with
> 2.16.17, nothing is filled in the main window and I get this error message:
> Unable to communicate with the WSJT-X process.
>    UDP Port : 2237
>    IP Address : 127.1.1.1
>    Values read from WSJT-X config file...
>      C:\Users\nheye\AppData\Local\WSJT-X\WSJT-X.ini
>
> WSJT-X Detected Instance...
>    Process Window Title : WSJT-X   v2.3.0   by K1JT, G4WJS, and K9AN
>    Process Command Line : "C:\WSJT\wsjtx\bin\wsjtx.exe"
>
> Decode alerts and logging will be unavailable until corrected.
>
> So I am sure I've missed a step somewhere. Can someone point me in the
> right direction?
> Thanks!
> Norman
> KC9NVN








locked Re: Problem with JTAlert 2.16.17

Joe Subich, W4TV
 

Unable to communicate with the WSJT-X process.
UDP Port : 2237
IP Address : 127.1.1.1
Values read from WSJT-X config file...
C:\Users\nheye\AppData\Local\WSJT-X\WSJT-X.ini
In WSJTX -> File -> Setting -> Reporting -> UDP Server

Set UDP Server (IP Address) = 127.0.0.1
Set UDP Server port number = 2237
Check "Accept UDP requests" and "notify on accepted UDP request"


73,

... Joe, W4TV


On 2021-02-23 10:47 AM, Norman Heyen wrote:
I have been having issues with JTAlert versions after version 2.16.10
Version 2.16.10 works well with my setup but it is time to update. My setup is:
DXLab Suite working with WSJT-X version 2.3.0
Running Windows 10 20H2 fully patched to current levels
With 2.16.10, everything works fine, logging and all that. But with 2.16.17, nothing is filled in the main window and I get this error message:
Unable to communicate with the WSJT-X process.
  UDP Port : 2237
  IP Address : 127.1.1.1
  Values read from WSJT-X config file...
    C:\Users\nheye\AppData\Local\WSJT-X\WSJT-X.ini
WSJT-X Detected Instance...
  Process Window Title : WSJT-X   v2.3.0   by K1JT, G4WJS, and K9AN
  Process Command Line : "C:\WSJT\wsjtx\bin\wsjtx.exe"
Decode alerts and logging will be unavailable until corrected.
So I am sure I've missed a step somewhere. Can someone point me in the right direction?
Thanks!
Norman
KC9NVN


locked Issues with PTT not working #FT8

K9MTH@...
 
Edited

I am running an ICOM 756PROII, with a Rigblaster pro.  I am trying to get WSJT, JTAlert and Log4OMng working together.  Log4OMng seems to need Omnirig for CAT control, along with WSJT.  However if I "key" to CQ in FT8 mode in WSJT, the PTT does not engage in the Rigblaster, The transmit from WSJT does put the radio into XMIT, but without the PTT by the rigblaster, I get no signal from the computer to the radio.

Edit:  If I uninstall Omnirig and reconfigure WSJT for the radio on "CAT" tab, then it does XMIT and receive as it should but no connectivity to Log4OM and JTAlert.

Any thoughts??

Thanks, 
Matt Hamm
K9MTH


locked Problem with JTAlert 2.16.17

Norman Heyen
 

I have been having issues with JTAlert versions after version 2.16.10

Version 2.16.10 works well with my setup but it is time to update. My setup is:
DXLab Suite working with WSJT-X version 2.3.0
Running Windows 10 20H2 fully patched to current levels

With 2.16.10, everything works fine, logging and all that. But with 2.16.17, nothing is filled in the main window and I get this error message:
Unable to communicate with the WSJT-X process.
  UDP Port : 2237
  IP Address : 127.1.1.1
  Values read from WSJT-X config file...
    C:\Users\nheye\AppData\Local\WSJT-X\WSJT-X.ini

WSJT-X Detected Instance...
  Process Window Title : WSJT-X   v2.3.0   by K1JT, G4WJS, and K9AN
  Process Command Line : "C:\WSJT\wsjtx\bin\wsjtx.exe" 

Decode alerts and logging will be unavailable until corrected.

So I am sure I've missed a step somewhere. Can someone point me in the right direction?
Thanks!
Norman
KC9NVN


locked JTAlert with JTDX and WSJT-X at the same time.

K0GU
 

Is there anyway I can make JTAlert work on both program at the same time? I'm using 3x JTDX instances, with 3x JTAlert JTDX, and 1x WSJT-X. JTAlert WSJT-X won't start because apparently because it thinks WSJT-X is the 4th instance of one of the programs?

thanks,

73,  Jay  K0GU


locked Re: FLEX 6600 four slices HELP

asobel@...
 

Tom

 

I am just following a thread that was started yesterday on this group by Frank I2DMI. There is no way to restart it on another group.

I have reproduced the whole thread for you

 

Amos 4X4MF

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Tom Job
Sent: Monday, February 22, 2021 8:16 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] FLEX 6600 four slices HELP

 

Wouldn’t this be better served on the WSJT-X group, Amos??  This group is for HamApps.

 

Just sayin’….

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of asobel@...
Sent: February 22, 2021 11:27
To: Support@HamApps.groups.io
Subject: Re: [HamApps] FLEX 6600 four slices HELP

 

Mike

 

Thank you for your comments.

I am not familiar with the internals of WSJT-X and JTAlert. Please explain the role of Hamlib.

I did create 6 instances of WSJT-X only 4 working concurrently. Lately I did create 7th and 8th instances but they did not work. Any explanation?

How many concurrent WSJT-X instances are you able to use?

I am facing the same problem as Frank, I2DMI, which is important because of its interaction with my StepIR antenna which is dangerous to the power amplifier.

In addition,  starting Tx on two instances makes 6600/SSDR Tx alternately on 2 slices.

 

Any thoughts will be welcome

 

Amos 4X4MF

 

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of m_scot_alex
Sent: Monday, February 22, 2021 2:03 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] FLEX 6600 four slices HELP

 

Amos -

I didn't write that WSJT-X  doesn't work with SSDR - I run two 6700s, one of which feeds eight instances of WSJT-X and JTA. What I did write is that Hamlib doesn't fully support SSDR - it only supports "VFO A" and "VFO B" - it has no concept of switching between SSDR panadapters and/or slices, so it can't designate a specific slice for transmitting without resorting to COM port emulation for each slice. This was a bigger issue before SSDR and SmartCAR implemented 'Auto TX Switiching' but still causes some operational issues (as you noted) and I'm corresponding with the developers about how to implement a complete solution.

And, as I said, this should be moved to WSJT-X list.

73,

Mike - N8MSA

 

=====================================

Frank

 

I am too, using Flex 6600 and 4x WSJT-X and JTAlert and I have the same problem.

Even worse, I am using a StepIR antenna which does start to tune, by command from SmartSDR,  only after  Tx is started.

I did complain on this issue to Flex support but so far, they did not come out with a solution.

 

Amos 4X4MF

 

==================================

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of i2dmi frank
Sent: Sunday, February 21, 2021 12:10 AM
To: Support@HamApps.groups.io
Subject: [HamApps] FLEX 6600 four slices HELP

 

Hello.
for FT8 dxing activity I'm using a FLEX 6600 with 4  WSJT instances (win10).
Which way can I have the "active slice" (A-B-C-D) changed when I single-click over one of the other WSJT's window?
I mean: if I'm on 40mt and active slice is B; If I want to change to 80mt., I click over WSJT A window but actually active slice doesn't move from B to A! No changes until the transmission is activated. 
Please Help. 
73 Frank i2dmi 
(apologies for mistakes)

_._,_._,_


Groups.io Links:

You receive all messages sent to this group.

View/Reply Online (#33374) | Reply To Group | Mute This Topic | New Topic
Your Subscription | Contact Group Owner | Unsubscribe [asobel@...]

 


locked Re: FLEX 6600 four slices HELP

Gregg E. McArthur
 

Amish, I use the flex 6700 and it works very effectively with four slices on ft8. Since I have a multi-band antenna that is resonant on the five high bands, I am able to monitor ft8 on four of the high bands. It takes a few moments to switch from one ft 8 to the next but after going through all of the DX stations on 20 m, it is easy to quickly switch to 17 m. Unfortunately, I have to use an antenna tuner for the low bands I have slices set for 30 and 40 m or for 40 and 80 m at night and so that it is easy to see the signals on the lower bands but when I switch from one slice to another, like from 40 to 80 m, I need to switch to a very low output on CW to retune the multi-band off center fed dipole antenna before I can begin transmitting on that lower frequency band. I can usually go through most of the DX stations in about an hour before I switch to the next band to see what is going on there.


On Mon, Feb 22, 2021, 11:16 AM Tom Job <ve3ii@...> wrote:

Wouldn’t this be better served on the WSJT-X group, Amos??  This group is for HamApps.

 

Just sayin’….

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of asobel@...
Sent: February 22, 2021 11:27
To: Support@HamApps.groups.io
Subject: Re: [HamApps] FLEX 6600 four slices HELP

 

Mike

 

Thank you for your comments.

I am not familiar with the internals of WSJT-X and JTAlert. Please explain the role of Hamlib.

I did create 6 instances of WSJT-X only 4 working concurrently. Lately I did create 7th and 8th instances but they did not work. Any explanation?

How many concurrent WSJT-X instances are you able to use?

I am facing the same problem as Frank, I2DMI, which is important because of its interaction with my StepIR antenna which is dangerous to the power amplifier.

In addition,  starting Tx on two instances makes 6600/SSDR Tx alternately on 2 slices.

 

Any thoughts will be welcome

 

Amos 4X4MF

 

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of m_scot_alex
Sent: Monday, February 22, 2021 2:03 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] FLEX 6600 four slices HELP

 

Amos -

I didn't write that WSJT-X  doesn't work with SSDR - I run two 6700s, one of which feeds eight instances of WSJT-X and JTA. What I did write is that Hamlib doesn't fully support SSDR - it only supports "VFO A" and "VFO B" - it has no concept of switching between SSDR panadapters and/or slices, so it can't designate a specific slice for transmitting without resorting to COM port emulation for each slice. This was a bigger issue before SSDR and SmartCAR implemented 'Auto TX Switiching' but still causes some operational issues (as you noted) and I'm corresponding with the developers about how to implement a complete solution.

And, as I said, this should be moved to WSJT-X list.

73,

Mike - N8MSA




Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com



locked Re: AutoIT Error - RESOLVED

ke4s@...
 

Already sent my thanks privately, but wanted to do so publicly.  Thanks, Laurie. Problem solved, all is working as it should. Pilot error!
Dave KE4S

3201 - 3220 of 36373