Date   

locked Re: The package manager is broken #linux

Bill Somerville
 

On 16/02/2021 21:40, Pat Tracy WI0K wrote:
How do I fix this.

Hi Pat,

you cannot mix the Debian package we provide with ones provided by package maintainers. If you want to install the WSJT-X v.2.2.2 package called wsjtx-data from the repo then remove the separately installed wsjtx package first:

sudo dpkg -P wsjtx
sudo apt install wsjtx-data

or conversely:

sudo apt remove wsjtx-data
sudo dpkg -i ~/Downloads/wsjtx-2.3.0_amd64.deb

73
Bill
G4WJS.


locked Re: CQ instead of 73 #FT8

Bill Somerville
 

On 16/02/2021 21:12, Ken WB8UFC wrote:
This doesn't seem right to me...
Mode: FT8
Relevant setting: Auto Seq (checked)
I answer a CQ by d-clicking on a line in the Rx Frequency list box.
The other side sends my signal report.
WSJT-X sends "R-" plus his signal report.
The other side sends RRR.
WSJT-X sends 73 (and advances the Next message to my CQ message).
The other side sends RRR again.
I d-click on his RRR line in the Rx Frequency list box, but after enabling the "Enable Tx" button, WSJT-X sends CQ instead of 73 because it doesn't re-position the "Next" message.
Is this expected behavior (and if so, why)?
At any other point in the QSO, d-clicking on the other side's line in the Rx Frequency list box selects the correct next message.

My best current workaround is to quickly click the radio button for the 73 message and then click on "Halt Tx" and then click on "Enable Tx"
Is there a faster/better way?

As a prophylactic measure I've taken to sometimes re-positioning the "Next" radio button manually back to the 73 message in anticipation of another RRR from the other side, but this seems kinda hokey.

WB8UFC
Hi Ken,

try double-clicking the repeated RRR message.

73
Bill
G4WJS.


locked Re: MSK144 K3 transmit on 6M #transmit

Hasan Schiers N0AN
 

Joe,
I would suggest you not go to 50.275 for MSK144. That freq is in use a lot for Q65-30A in the States. I didn't see a callsign for you, ...

Typically MSK144 alternate frequencies here are 255, 250, 265, even 257 works. 

73, N0AN
Hasan


On Tue, Feb 16, 2021 at 2:54 PM joe gay via groups.io <hamop=protonmail.com@groups.io> wrote:
I recently took a try of meteor scatter on 6M using MSK144 with Ver 2.3.0 - Freq selected by mode was 50.260. It is suggested to switch to another freq to finish QSO i.e. 50.275. I noticed the K3 was set to split with transmit on "B" vfo. I can tune up to 50.275 using main vfo but tx stays at 50.260. It seems like it would be easier to use main vfo for Rx &Tx for this mode. Is there a setting for that?
Joe



locked The package manager is broken #linux

Pat Tracy WI0K
 

How do I fix this.
wptracy@ubuntu:/usr/share/pixmaps$ sudo apt-get install wsjtx-data
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  glib-networking:i386 gstreamer1.0-x:i386 libaa1:i386 libavc1394-0:i386
  libcaca0:i386 libdv4:i386 libgstreamer-plugins-good1.0-0:i386
  libgudev-1.0-0:i386 libiec61883-0:i386 libproxy1v5:i386 libraw1394-11:i386
  libsamplerate0:i386 libshout3:i386 libslang2:i386 libsoup2.4-1:i386
  libtag1v5:i386 libtag1v5-vanilla:i386 libxv1:i386
Use 'sudo apt autoremove' to remove them.
The following NEW packages will be installed:
  wsjtx-data
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 0 B/3,625 kB of archives.
After this operation, 3,832 kB of additional disk space will be used.
(Reading database ... 220225 files and directories currently installed.)
Preparing to unpack .../wsjtx-data_2.2.2+repack-2_all.deb ...
Unpacking wsjtx-data (2.2.2+repack-2) ...
dpkg: error processing archive /var/cache/apt/archives/wsjtx-data_2.2.2+repack-2_all.deb (--unpack):
 trying to overwrite '/usr/share/pixmaps/wsjtx_icon.png', which is also in package wsjtx 2.3.0
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/wsjtx-data_2.2.2+repack-2_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


Check if you are using third party repositories. If so disable them, since they are a common source of problems.
Furthermore run the following command in a Terminal: apt-get install -f
Transaction failed: The package system is broken
 The following packages have unmet dependencies:

js8call: Depends: wsjtx-data but it is not installed
         Depends: libc6 (>= 2.29) but 2.32-0ubuntu3 is installed
         Depends: libfftw3-single3 (>= 3.3.5) but 3.3.8-2ubuntu6 is installed
         Depends: libgcc-s1 (>= 3.0) but 10.2.0-13ubuntu1 is installed
         Depends: libgfortran5 (>= 10) but 10.2.0-13ubuntu1 is installed
         Depends: libgomp1 (>= 4.2.1) but 10.2.0-13ubuntu1 is installed
         Depends: libhamlib2 (>= 3.1) but 3.3-10build1 is installed
         Depends: libqt5core5a (>= 5.14.1) but 5.14.2+dfsg-6 is installed
         Depends: libqt5gui5-gles (>= 5.14.1) but it is not installed
         Depends: libqt5multimedia5 (>= 5.6.0~beta) but 5.14.2-3 is installed
         Depends: libqt5network5 (>= 5.0.2) but 5.14.2+dfsg-6 is installed
         Depends: libqt5serialport5 (>= 5.6.0) but 5.14.2-2 is installed
         Depends: libqt5widgets5 (>= 5.14.1) but 5.14.2+dfsg-6 is installed
         Depends: libsqlite3-0 (>= 3.5.9) but 3.33.0-1ubuntu0.1 is installed
         Depends: libstdc++6 (>= 5.2) but 10.2.0-13ubuntu1 is installed

wptracy@ubuntu:/usr/share/pixmaps$ sudo apt-get install -f
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
  glib-networking:i386 gstreamer1.0-x:i386 libaa1:i386 libavc1394-0:i386
  libcaca0:i386 libdv4:i386 libgstreamer-plugins-good1.0-0:i386
  libgudev-1.0-0:i386 libiec61883-0:i386 libproxy1v5:i386 libraw1394-11:i386
  libsamplerate0:i386 libshout3:i386 libslang2:i386 libsoup2.4-1:i386
  libtag1v5:i386 libtag1v5-vanilla:i386 libxv1:i386
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  wsjtx-data
The following NEW packages will be installed:
  wsjtx-data
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 0 B/3,625 kB of archives.
After this operation, 3,832 kB of additional disk space will be used.
Do you want to continue? [Y/n]
(Reading database ... 220225 files and directories currently installed.)
Preparing to unpack .../wsjtx-data_2.2.2+repack-2_all.deb ...
Unpacking wsjtx-data (2.2.2+repack-2) ...
dpkg: error processing archive /var/cache/apt/archives/wsjtx-data_2.2.2+repack-2_all.deb (--unpack):
 trying to overwrite '/usr/share/pixmaps/wsjtx_icon.png', which is also in package wsjtx 2.3.0
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/wsjtx-data_2.2.2+repack-2_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
wptracy@ubuntu:/usr/share/pixmaps$



locked Re: #Cat_RigControl #Cat_RigControl

Lutz-DL9DAN
 

Hi Bill,

I guess maybe no - the test cat is not the problem I assume. Because if I use the button or not the problem ´update from rig missing´ appears when starting WSJT-X already.

 

So now with this sequence I do not need the test cat as it works perfect.

but thanks for your reply - it was a long afternoon testing but now I am happy and can focus on the next topic.

 

73 Lutz

 

Von: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] Im Auftrag von Bill Somerville
Gesendet: Dienstag, 16. Februar 2021 21:39
An: main@WSJTX.groups.io
Betreff: Re: [WSJTX] #Cat_RigControl

 

Lutz,

 

perhaps you could have saved yourself some time by checking the WSJT-X User Guide FAQ section, item 6:

 

 

73
Bill
G4WJS.

 

On 16/02/2021 20:35, Lutz-DL9DAN wrote:

Hi Gene,

finally I found a sequence to work with!!

 

Its funny, but:


1) Make sure that no OMNIRIG 32bit process is running!

 

2) Start the microham router with the virtual ports

3) Start WSJT-X with OMNIRIG selected
     It may result in an error for the first time and close,
     try again and it works!

 

4) Start SDRCONSOLE and all digi modes are present and work, the rig works with CAT for both programs

 

It seems to me that WSJT-X is calling the OMNIRIG up on its own and cannot see that it is always running.

 

I have tested and confirmed this behavior now several times!

 

Its like fishing - you need patience sitting behind the rod!

 

Thanks

Lutz/DL9DAN

 

Von: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] Im Auftrag von RVnRadio
Gesendet: Samstag, 13. Februar 2021 19:23
An: main@WSJTX.groups.io
Betreff: Re: [WSJTX] #Cat_RigControl

 

I will add to the response "It sounds like more than one program is trying to access the same port", except my suffix will be "for sure" instead of maybe.  At least that is my assessment. here is what I do, which I think is just a bigger version of what your trying to accomplish.

I run WSJT-X, DXLab Commander (multi-rig CAT controller program and use a RIGblaster Advantage for sound, and for CW/FSK PTT control with my TS-590SG, all through one USB physical port.  I setup VSPE Serial port emulator (freeware but 64 bit version is reasonable price) running to provide a port Splitter device configured to take the COM port my radio claims in Device Manager, and splits it to add a virtual COM port. My WSJT-X program is configured to use this particular virtual COM port number.  As for PTT control, I have WSKJT-X set to use VOX, with my RB Advantage switch-selected to VOX, TX control.  Works like a peach.

Besides WSJT-X, I use a number of other ham software programs.  I also have  DXLab Commander multirig CAT control for two radios.  I chose to use one of these two radios with all of my software programs.  The Multirig tab in Commander needed that radio to also change from the physical COM port number, to the same Virtual COM port number.  Some of these programs needed some additional control signals like FSK for RTTY as well as PTT control needed by WSJT-X.  For that, I have another serial port utility provided by WEST MOUNTAIN with the RB Advantage with it's "Port Split",that provides that PTT control, or I can use VOX control. Yeah, it gets a bit deep in my case.

Not that its important to this thread but I also have an IC-7300 tied into DXLab Commander as a secondary radio.  Everything the TS-590SG does for Band, Freq and Mode changes, the 7300 follows which is of course connected to the PC with its own physical USB cable and COM port.   If I change Band, Freq and Mode on the 7300, even using the touch screen on its band scope, the 590SG follows those commands.  The Commander program ties these radios together for Band, Freq and Mode interaction while at the same time, VSPE and WM Port Split provide the other software programs the ability to work with the 590SG which is my choice to use as the tranciever.  7300 doesn't meet my demands for a transceiver.  I instead use it mostly as a sound-muted secondary receiver, either in sync with, or separated from the 590. With some mechanical switching and RF isolation, this secondary receiver meets my needs for having a band scope for the 590SG that is either totally in sync, and using the same antenna.  Or I can put the 7300 on a different antenna for diversity reception.  Or I can stop CAT program interaction so that I can roam bands, modes and frequencies independently.  In other words, my TS-590SG effectively has a built in 2nd receiver and a band scope via software control and some switching. All of this while multiple software programs co-exist to allow me to log, operate digital modes including AFSK or FSK (the  latter because of the RB Advantage), use the 7300's TTY decoder, use the band scope for the 590 or independent of the 590. Just about anything a dual receiver built into one more expensive rig can do, or a TS-890S linked to a TS-590SG.

The point here is while my setup is a more complex version of what your presently trying to do. Same thing though;
This is just like two, or more cars traveling in the same lane in the same direction, and never colliding with each other.
And then another lane in the opposite direction with cars also not wrecking.   

I will admit it was a brain twister for me to get all of the software programs configured to play nice on the inbound and outbound freeway lanes.  I humbly approached WEST MOUNTAIN support for some help because a lot of this involved their RB device.  A particular support guy with WM was incredibly helpful for me.  I imagine MICROHAM can lend a hand if you purchased your micro KEYER III new from then.  I think your interface needs are fundamentally similar to my RB even though my RB is phsyically connected to my PC on a separate physical USB cable & port, but yours has lot more functions and features. Ask their support about what your trying to do with one program on the same USB physical port line as your micro KEYER III & radio are connected via "passthru", or daisy chained cabling.  

Meanwhile, you have command and data whizzing duplex between the radio and the computer and then when a program is launched its like stacking two cars in the same spot in one direction and two more cars on top of each other in the other direction.  You just need to space the cars in these two lanes so that the data/commands come and go to their destinations without running into each other.

I would suggest copy/pasting this reply text into Word or other document to have on the table.  maybe underline or highlight somethings unless this info just doesn't fit your issue at all.

Gene / K7TXO

 


locked CQ instead of 73 #FT8

Ken WB8UFC
 

This doesn't seem right to me...
 
Mode: FT8
Relevant setting: Auto Seq (checked) 
 
I answer a CQ by d-clicking on a line in the Rx Frequency list box.
The other side sends my signal report.
WSJT-X sends "R-" plus his signal report.
The other side sends RRR.
WSJT-X sends 73 (and advances the Next message to my CQ message).
The other side sends RRR again.
 
I d-click on his RRR line in the Rx Frequency list box, but after enabling the "Enable Tx" button, WSJT-X sends CQ instead of 73 because it doesn't re-position the "Next" message.
Is this expected behavior (and if so, why)?
 
At any other point in the QSO, d-clicking on the other side's line in the Rx Frequency list box selects the correct next message.

My best current workaround is to quickly click the radio button for the 73 message and then click on "Halt Tx" and then click on "Enable Tx"
Is there a faster/better way?

As a prophylactic measure I've taken to sometimes re-positioning the "Next" radio button manually back to the 73 message in anticipation of another RRR from the other side, but this seems kinda hokey.

WB8UFC


locked Re: PWR slider behaviour #transmit

Bill Somerville
 

On 16/02/2021 21:06, Nico Ebbendorf wrote:
Hi,

Trying to control the TX output with the PWR slider. My transceiver is a FTDX101D. Coding and decoding FT8 is working and also the transceiver freq. control

Observation:
Set TX power at 40 Watt using the transceiver power control knop. Then sliding the PWR control down will reduce output power but this increases automatically within a second or so to the maximum power that is set by the transceiver (in this case 40 Watt). So the power output is always the maximum that is set by the transceiver regardles the PWR slider position.

Is there anything to set in the software to correct this or do I need to go into the transceiver menu?

73, Nico PA3ADU
Hi Nico,

non-linear behaviour of the WSJT-X Pwr slider is usually a sign that you have too much audio level into your rig. It also is a sign that you may be transmitting a poor quality signal. Find the data mode input gain in your rig's menu and reduce it until the unwanted behaviour stops. See this post for a recipe for setting Tx audio levels correctly:

https://wsjtx.groups.io/g/main/message/13890

73
Bill
G4WJS.


locked PWR slider behaviour #transmit

Nico Ebbendorf
 

Hi,

Trying to control the TX output with the PWR slider. My transceiver is a FTDX101D. Coding and decoding FT8 is working and also the transceiver freq. control

Observation:
Set TX power at 40 Watt using the transceiver power control knop. Then sliding the PWR control down will reduce output power but this increases automatically within a second or so to the maximum power that is set by the transceiver (in this case 40 Watt). So the power output is always the maximum that is set by the transceiver regardles the PWR slider position.

Is there anything to set in the software to correct this or do I need to go into the transceiver menu?

73, Nico PA3ADU


locked Re: Q65 on Six Meter 50.275 #Q65

Bob K4RCG
 

Jim, I've been using Q65/30A on 50.275.  50.235 is said to be for 120/A.  And finally, I believe  DX/EU is on .305.  Lots of fun.

73
Bob K4RCG

On Tue, Feb 16, 2021 at 6:30 PM ve4cy <jwt@...> wrote:
I notice on PSK Reporter, there are quite a few stations running Q65 on Six Meters.

The only thing I can't seem to figure out is what duration, and which submode they are using..   I'm assuming submode A, but Is it 15 second or 30 second?

73 de Jim VE4CY



locked Re: MSK144 K3 transmit on 6M #transmit

Bill Somerville
 

On 16/02/2021 20:53, joe gay via groups.io wrote:
I recently took a try of meteor scatter on 6M using MSK144 with Ver 2.3.0 - Freq selected by mode was 50.260. It is suggested to switch to another freq to finish QSO i.e. 50.275. I noticed the K3 was set to split with transmit on "B" vfo. I can tune up to 50.275 using main vfo but tx stays at 50.260. It seems like it would be easier to use main vfo for Rx &Tx for this mode. Is there a setting for that?
Joe
Hi Joe,

WSJT-X has a feature that allows easy operation with MSK144 to call on a calling frequency but carry out QSOs on a different working frequency. This is only available if you have working CAT control and enable one of the "Settings->Radio->Split Operating" options. Check the checkbox to the right of the "Tx CQ 260" spin box, then tune your VFO to a free working frequency. WSJT-X will automatically amend the CQ message to inform repliers of your working frequency, make CQ calls on the .260 (or whatever kHz offset you set the spin box to) calling frequency, and proceed with any QSOs on your working frequency. When your QSO is completed the next CQ call you make will be back on the calling frequency. To make a QSO double-click a decode of any station that replies to your CQ.

None of the above will happen if you do not check the checkbox mentioned above.

73
Bill
G4WJS.


locked MSK144 K3 transmit on 6M #transmit

joe gay
 

I recently took a try of meteor scatter on 6M using MSK144 with Ver 2.3.0 - Freq selected by mode was 50.260. It is suggested to switch to another freq to finish QSO i.e. 50.275. I noticed the K3 was set to split with transmit on "B" vfo. I can tune up to 50.275 using main vfo but tx stays at 50.260. It seems like it would be easier to use main vfo for Rx &Tx for this mode. Is there a setting for that?
Joe


locked Re: Q65 on Six Meter 50.275 #Q65

Hasan Schiers N0AN
 

In the current 2.4.0 RC1 we discovered that the number of observable decodes is greater with Enable Averaging OFF.

The next release will take care of this. In the mean time, if you are just monitoring the band for possible decodes, turn Enable Averaging OFF.

When in QSO, turn it back on, as it permits better sensitivity under certain conditions. 

73, N0AN
Hasan


On Tue, Feb 16, 2021 at 2:35 PM W4AS <w4as@...> wrote:
Why disable Averaging?

73 de Sebastian, W4AS




> On Feb 16, 2021, at 1:49 PM, Hasan Schiers N0AN <hbasri.schiers6@...> wrote:
>
> The vast majority of us are running :
>
> Q65-30A on 50.275
> That is 30 sec T/R and Submode A
>
> For lower power, super weak signals we are using
>
> Q65-120E on 50.235
> T/R 120 seconds and Submode E
>
> These were chosen for an absence of LAN spikes and WiFi Spikes that are common to heavily populated neighborhoods. The are just current watering holes, not 'official' assignments.
>
> If you want to monitor, Q65-30A 50.275 is your best bet for a place to find activity.
>
> Settings:
> Decode : FAST (deep off); Enable Averaging OFF
> F Tol 20 Hz (be sure to set rx to the qso partner freq)
>
> 73, N0AN
>





locked Re: #Cat_RigControl #Cat_RigControl

Bill Somerville
 

Lutz,

perhaps you could have saved yourself some time by checking the WSJT-X User Guide FAQ section, item 6:


73
Bill
G4WJS.

On 16/02/2021 20:35, Lutz-DL9DAN wrote:

Hi Gene,

finally I found a sequence to work with!!

 

Its funny, but:


1) Make sure that no OMNIRIG 32bit process is running!

 

2) Start the microham router with the virtual ports

3) Start WSJT-X with OMNIRIG selected
     It may result in an error for the first time and close,
     try again and it works!

 

4) Start SDRCONSOLE and all digi modes are present and work, the rig works with CAT for both programs

 

It seems to me that WSJT-X is calling the OMNIRIG up on its own and cannot see that it is always running.

 

I have tested and confirmed this behavior now several times!

 

Its like fishing - you need patience sitting behind the rod!

 

Thanks

Lutz/DL9DAN

 

Von: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] Im Auftrag von RVnRadio
Gesendet: Samstag, 13. Februar 2021 19:23
An: main@WSJTX.groups.io
Betreff: Re: [WSJTX] #Cat_RigControl

 

I will add to the response "It sounds like more than one program is trying to access the same port", except my suffix will be "for sure" instead of maybe.  At least that is my assessment. here is what I do, which I think is just a bigger version of what your trying to accomplish.

I run WSJT-X, DXLab Commander (multi-rig CAT controller program and use a RIGblaster Advantage for sound, and for CW/FSK PTT control with my TS-590SG, all through one USB physical port.  I setup VSPE Serial port emulator (freeware but 64 bit version is reasonable price) running to provide a port Splitter device configured to take the COM port my radio claims in Device Manager, and splits it to add a virtual COM port. My WSJT-X program is configured to use this particular virtual COM port number.  As for PTT control, I have WSKJT-X set to use VOX, with my RB Advantage switch-selected to VOX, TX control.  Works like a peach.

Besides WSJT-X, I use a number of other ham software programs.  I also have  DXLab Commander multirig CAT control for two radios.  I chose to use one of these two radios with all of my software programs.  The Multirig tab in Commander needed that radio to also change from the physical COM port number, to the same Virtual COM port number.  Some of these programs needed some additional control signals like FSK for RTTY as well as PTT control needed by WSJT-X.  For that, I have another serial port utility provided by WEST MOUNTAIN with the RB Advantage with it's "Port Split",that provides that PTT control, or I can use VOX control. Yeah, it gets a bit deep in my case.

Not that its important to this thread but I also have an IC-7300 tied into DXLab Commander as a secondary radio.  Everything the TS-590SG does for Band, Freq and Mode changes, the 7300 follows which is of course connected to the PC with its own physical USB cable and COM port.   If I change Band, Freq and Mode on the 7300, even using the touch screen on its band scope, the 590SG follows those commands.  The Commander program ties these radios together for Band, Freq and Mode interaction while at the same time, VSPE and WM Port Split provide the other software programs the ability to work with the 590SG which is my choice to use as the tranciever.  7300 doesn't meet my demands for a transceiver.  I instead use it mostly as a sound-muted secondary receiver, either in sync with, or separated from the 590. With some mechanical switching and RF isolation, this secondary receiver meets my needs for having a band scope for the 590SG that is either totally in sync, and using the same antenna.  Or I can put the 7300 on a different antenna for diversity reception.  Or I can stop CAT program interaction so that I can roam bands, modes and frequencies independently.  In other words, my TS-590SG effectively has a built in 2nd receiver and a band scope via software control and some switching. All of this while multiple software programs co-exist to allow me to log, operate digital modes including AFSK or FSK (the  latter because of the RB Advantage), use the 7300's TTY decoder, use the band scope for the 590 or independent of the 590. Just about anything a dual receiver built into one more expensive rig can do, or a TS-890S linked to a TS-590SG.

The point here is while my setup is a more complex version of what your presently trying to do. Same thing though;
This is just like two, or more cars traveling in the same lane in the same direction, and never colliding with each other.
And then another lane in the opposite direction with cars also not wrecking.   

I will admit it was a brain twister for me to get all of the software programs configured to play nice on the inbound and outbound freeway lanes.  I humbly approached WEST MOUNTAIN support for some help because a lot of this involved their RB device.  A particular support guy with WM was incredibly helpful for me.  I imagine MICROHAM can lend a hand if you purchased your micro KEYER III new from then.  I think your interface needs are fundamentally similar to my RB even though my RB is phsyically connected to my PC on a separate physical USB cable & port, but yours has lot more functions and features. Ask their support about what your trying to do with one program on the same USB physical port line as your micro KEYER III & radio are connected via "passthru", or daisy chained cabling.  

Meanwhile, you have command and data whizzing duplex between the radio and the computer and then when a program is launched its like stacking two cars in the same spot in one direction and two more cars on top of each other in the other direction.  You just need to space the cars in these two lanes so that the data/commands come and go to their destinations without running into each other.

I would suggest copy/pasting this reply text into Word or other document to have on the table.  maybe underline or highlight somethings unless this info just doesn't fit your issue at all.

Gene / K7TXO



locked Re: #Cat_RigControl #Cat_RigControl

Kenneth Williams
 

Hello Jacques

Maybe you should update your WSJT-X to 2.4 rc1.

While you may not like this response, I have had a recent experience where this was indeed the proper solution.
I am mentioning this because I have a TS-570S, and while it is not a 590 as you have, these radios may share some of the problem causing behavior.

OK, here is some boring detail:
I started using FT8 with version 2.2.  WSJT-X would frequently report loss of communication with the radio although I did not need to reboot my computer, I did suffer this kind of problem.  It was suggested that I update to V2.3.  This did not completely resolve the problem.  v2.4 solved the problem.

The problem:  In my case, my radio would occasionally respond to an 'IF' (information query) command with an answer that was one or two bytes shorts.  Hamlib, the library that is used to interface with the various radios, would reject the responses that were one byte too short (in v2.3) but responses that were two bytes too short would cause hamlib to report loss of communication.
I know this because when validating the problem, mostly for my own curiosity, I instrumented the serial interface to my rig and I could see the short responses come out of the radio.

With WSJT-X v2.2, I saw a loss of communication message frequently (once every few hours).  With v2.3, the messages were less frequent (once or twice a day).  Since running v2.4 for almost a week, I have not seen that problem at all (except when I tripped the circuit breaker to my radio, but I do not think that this event counts)

Good luck

Ken
KC6PUQ


locked Re: #Cat_RigControl #Cat_RigControl

Lutz-DL9DAN
 

Hi Gene,

finally I found a sequence to work with!!

 

Its funny, but:


1) Make sure that no OMNIRIG 32bit process is running!

 

2) Start the microham router with the virtual ports

3) Start WSJT-X with OMNIRIG selected
     It may result in an error for the first time and close,
     try again and it works!

 

4) Start SDRCONSOLE and all digi modes are present and work, the rig works with CAT for both programs

 

It seems to me that WSJT-X is calling the OMNIRIG up on its own and cannot see that it is always running.

 

I have tested and confirmed this behavior now several times!

 

Its like fishing - you need patience sitting behind the rod!

 

Thanks

Lutz/DL9DAN

 

Von: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] Im Auftrag von RVnRadio
Gesendet: Samstag, 13. Februar 2021 19:23
An: main@WSJTX.groups.io
Betreff: Re: [WSJTX] #Cat_RigControl

 

I will add to the response "It sounds like more than one program is trying to access the same port", except my suffix will be "for sure" instead of maybe.  At least that is my assessment. here is what I do, which I think is just a bigger version of what your trying to accomplish.

I run WSJT-X, DXLab Commander (multi-rig CAT controller program and use a RIGblaster Advantage for sound, and for CW/FSK PTT control with my TS-590SG, all through one USB physical port.  I setup VSPE Serial port emulator (freeware but 64 bit version is reasonable price) running to provide a port Splitter device configured to take the COM port my radio claims in Device Manager, and splits it to add a virtual COM port. My WSJT-X program is configured to use this particular virtual COM port number.  As for PTT control, I have WSKJT-X set to use VOX, with my RB Advantage switch-selected to VOX, TX control.  Works like a peach.

Besides WSJT-X, I use a number of other ham software programs.  I also have  DXLab Commander multirig CAT control for two radios.  I chose to use one of these two radios with all of my software programs.  The Multirig tab in Commander needed that radio to also change from the physical COM port number, to the same Virtual COM port number.  Some of these programs needed some additional control signals like FSK for RTTY as well as PTT control needed by WSJT-X.  For that, I have another serial port utility provided by WEST MOUNTAIN with the RB Advantage with it's "Port Split",that provides that PTT control, or I can use VOX control. Yeah, it gets a bit deep in my case.

Not that its important to this thread but I also have an IC-7300 tied into DXLab Commander as a secondary radio.  Everything the TS-590SG does for Band, Freq and Mode changes, the 7300 follows which is of course connected to the PC with its own physical USB cable and COM port.   If I change Band, Freq and Mode on the 7300, even using the touch screen on its band scope, the 590SG follows those commands.  The Commander program ties these radios together for Band, Freq and Mode interaction while at the same time, VSPE and WM Port Split provide the other software programs the ability to work with the 590SG which is my choice to use as the tranciever.  7300 doesn't meet my demands for a transceiver.  I instead use it mostly as a sound-muted secondary receiver, either in sync with, or separated from the 590. With some mechanical switching and RF isolation, this secondary receiver meets my needs for having a band scope for the 590SG that is either totally in sync, and using the same antenna.  Or I can put the 7300 on a different antenna for diversity reception.  Or I can stop CAT program interaction so that I can roam bands, modes and frequencies independently.  In other words, my TS-590SG effectively has a built in 2nd receiver and a band scope via software control and some switching. All of this while multiple software programs co-exist to allow me to log, operate digital modes including AFSK or FSK (the  latter because of the RB Advantage), use the 7300's TTY decoder, use the band scope for the 590 or independent of the 590. Just about anything a dual receiver built into one more expensive rig can do, or a TS-890S linked to a TS-590SG.

The point here is while my setup is a more complex version of what your presently trying to do. Same thing though;
This is just like two, or more cars traveling in the same lane in the same direction, and never colliding with each other.
And then another lane in the opposite direction with cars also not wrecking.   

I will admit it was a brain twister for me to get all of the software programs configured to play nice on the inbound and outbound freeway lanes.  I humbly approached WEST MOUNTAIN support for some help because a lot of this involved their RB device.  A particular support guy with WM was incredibly helpful for me.  I imagine MICROHAM can lend a hand if you purchased your micro KEYER III new from then.  I think your interface needs are fundamentally similar to my RB even though my RB is phsyically connected to my PC on a separate physical USB cable & port, but yours has lot more functions and features. Ask their support about what your trying to do with one program on the same USB physical port line as your micro KEYER III & radio are connected via "passthru", or daisy chained cabling.  

Meanwhile, you have command and data whizzing duplex between the radio and the computer and then when a program is launched its like stacking two cars in the same spot in one direction and two more cars on top of each other in the other direction.  You just need to space the cars in these two lanes so that the data/commands come and go to their destinations without running into each other.

I would suggest copy/pasting this reply text into Word or other document to have on the table.  maybe underline or highlight somethings unless this info just doesn't fit your issue at all.

Gene / K7TXO


locked Re: Sudden blindness to sound card and ports windows 10 #AudioIssues #Cat_RigControl #IssueReport

Bill Somerville
 

On 16/02/2021 19:36, Chris wrote:
I think it would be better to focus on the bigger issue which is the sound card problem.
Note this capture.  The correct card shows initially as "not found".  If I click on the pick list (which I did on the bottom output list) No cards show up.
I'm pretty sure this is due to some corruption in the WSJT-X installation, but un installing and re installing does not fix it.  I'm hoping someone with good knowledge of the "under the hood" areas might shed some light on this.
To restate, all other programs see and work it the card just fine, and WSJT-X worked fine until a bit over a week ago.  This was a sudden and unexpected change.
Chris, AB6QK
Hi Chris,

the (Not found) annotation means exactly what it says. The underlying Qt framework functionality we use to enumerate audio devices did not list the one you last used in WSJT-X. If the drop down list is also empty then no audio devices are available to WSJT-X.

MS Windows has several audio sub-systems, the one we have access to is called MME (Multi-Media Extensions). If MME is unable to enumerate your audio devices then the problem lies within MS Windows and your best source of support is probably with Microsoft support. A basic question like "I am using an application that uses MME audio and it can't see any audio devices, what should I do?" seems pertinent.

If you are happy to download and run a pre-built executable from me, the following application will enumerate the audio devices seen by MME using just MS system library code without any of the framework layers we use in WSJT-X, it would be interesting to see the output:

https://www.dropbox.com/s/kidxhnb8w20j7w4/audio_devices_enumeration.exe?dl=1

The source code is here if you want to know what it does or prefer to build it yourself:

https://www.dropbox.com/s/6mj0f68q7xd07h4/audio_devices_enumeration.zip?dl=1

73
Bill
G4WJS.


locked Re: Q65 on Six Meter 50.275 #Q65

W4AS
 

Why disable Averaging?

73 de Sebastian, W4AS

On Feb 16, 2021, at 1:49 PM, Hasan Schiers N0AN <hbasri.schiers6@...> wrote:

The vast majority of us are running :

Q65-30A on 50.275
That is 30 sec T/R and Submode A

For lower power, super weak signals we are using

Q65-120E on 50.235
T/R 120 seconds and Submode E

These were chosen for an absence of LAN spikes and WiFi Spikes that are common to heavily populated neighborhoods. The are just current watering holes, not 'official' assignments.

If you want to monitor, Q65-30A 50.275 is your best bet for a place to find activity.

Settings:
Decode : FAST (deep off); Enable Averaging OFF
F Tol 20 Hz (be sure to set rx to the qso partner freq)

73, N0AN


locked Re: #Q65 Q65 and EME observations for discussion. #Q65

K0GU
 

On 2/16/2021 12:20 PM, Chris Hannagan wrote:

I see that Call 1st is broken and it will not start the auto sequence when a legitimate mycall hiscall sequence is received.

The sequencing never moves to tx6 even after the QSO is logged and continues to send 73 until manually changed.


  Yep, I have those same problems with terrestrial operations.

73,  Jay  K0GU


locked Re: Sudden blindness to sound card and ports windows 10 #AudioIssues #Cat_RigControl #IssueReport

Chris
 

I think it would be better to focus on the bigger issue which is the sound card problem.
Note this capture.  The correct card shows initially as "not found".  If I click on the pick list (which I did on the bottom output list) No cards show up.
I'm pretty sure this is due to some corruption in the WSJT-X installation, but un installing and re installing does not fix it.  I'm hoping someone with good knowledge of the "under the hood" areas might shed some light on this.
To restate, all other programs see and work it the card just fine, and WSJT-X worked fine until a bit over a week ago.  This was a sudden and unexpected change.
Chris, AB6QK


locked #Q65 Q65 and EME observations for discussion. #Q65

Chris Hannagan
 

I have run some tests with a friend in ZL and I see a few shortcomings and I don't know whether there is input from the EME community to the developers.

I see that Call 1st is broken and it will not start the auto sequence when a legitimate mycall hiscall sequence is received.

The sequencing never moves to tx6 even after the QSO is logged and continues to send 73 until manually changed.

The single tone shorthand messages are referenced against the carrier frequency only not the transmitting stations DF.

Envisage some  EME DXpeditions where you have stations every plus/minus 200 Hz for 1000Hz bandwidth each way and someone misses a transmission and the DX moves on to the next station.
You can imagine what a mess it will be when you have multiple stations calling all referenced to the dial frequency and someone misses a response and you have multiple stations using shorthand messages on the same frequency.

I'm sure the old SH messages referenced to the sync frequency are probably much more effective way to avoid the confusion.

I don't think I'm game to try shorthand for EME in a situation where there might be more than one caller and going to the FT8 style TX3 TX4 TX5 messages (probably) defeats the extra sensitivity...

I presume (maybe wrongly) the single tone for a CQ message when SH is checked is a feature for microwave users to find each other's signal?
Perhaps the CQ message should remain there and microwavers can use the Tune button to search.
DX stations usually use a normal CQ message even when they are using shorthand for for the other QSO information.

73
Chris zl7dx

14701 - 14720 of 36850