Date   

locked Re: TCI-Client for Sun SDR #Cat_RigControl

Roger Corbett <roger.corbett@...>
 

Hi Bill,
Just to add another number to the count. I too have a SunSDR and Id love to be able to use TCI directly from WSJT-X.
Currently Im using MacLoggerDX to do the connection which is fine but I’ve never been able to get any sort of doppler correction working with that setup.
Thats not totally true but 100hz steps, which is all I’ve been able to achieve, is useless as a microwave IF.

73
Roger ZL3RC

On 25/11/2021, at 8:43 AM, Charlie Morrison <charlie@...> wrote:

Hi Bill
 
There are a great many users of the SunSDR range, and I for one  would love to see TCI incorporated as a CAT  option…It can also stream the Audio which gets around having to use VAC with its attendant artefacts. Perhaps it could be investigated
 
73, Charlie GI4FUE
 
From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of ????? ??????? via groups.io
Sent: 24 November 2021 17:25
To: main@wsjtx.groups.io
Subject: Re: [WSJTX] TCI-Client for Sun SDR #Cat_RigControl
 
Hi Bill, Mike
This question arose during the discussion on the site forum.qrz.ru of the capabilities of the WSJTX, JTDX and MSHV programs by users of SUN SDR transceivers. Surprised that WSJTX does not use TCI communication technology.
Thanks.
73 Boris UX8IW
Среда, 24 ноября 2021, 0:39 +02:00 от Bill Somerville <g4wjs@...>:
 
On 23/11/2021 19:33, Борис Романов via groups.io wrote:
Hi,
Maybe I don’t know something, but I want to ask.
Is the WSJTX program supposed to control the SDR transceiver (CAT and sound) via the TCI interface?
This control is implemented in the JTDX and MSW programs.
73 Boris UX8IW

Hi Boris,

as far as I am aware, you are the first to ask. No WSJT-X does not currently support that rig control mechanism. If there is enough interest I can look at implementing it, or if anyone wants to contribute an implementation as a pull request I will consider its inclusion in WSJT-X.

73
Bill
G4WJS.



 
 
 
--
Борис Романов
 



locked Re: TCI-Client for Sun SDR #Cat_RigControl

Charlie Morrison
 

Hi Bill

 

There are a great many users of the SunSDR range, and I for one  would love to see TCI incorporated as a CAT  option…It can also stream the Audio which gets around having to use VAC with its attendant artefacts. Perhaps it could be investigated

 

73, Charlie GI4FUE

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of ????? ??????? via groups.io
Sent: 24 November 2021 17:25
To: main@wsjtx.groups.io
Subject: Re: [WSJTX] TCI-Client for Sun SDR #Cat_RigControl

 

Hi Bill, Mike

This question arose during the discussion on the site forum.qrz.ru of the capabilities of the WSJTX, JTDX and MSHV programs by users of SUN SDR transceivers. Surprised that WSJTX does not use TCI communication technology.

Thanks.

73 Boris UX8IW

Среда, 24 ноября 2021, 0:39 +02:00 от Bill Somerville <g4wjs@...>:
 

On 23/11/2021 19:33, Борис Романов via groups.io wrote:

Hi,

Maybe I don’t know something, but I want to ask.

Is the WSJTX program supposed to control the SDR transceiver (CAT and sound) via the TCI interface?

This control is implemented in the JTDX and MSW programs.

73 Boris UX8IW

Hi Boris,

as far as I am aware, you are the first to ask. No WSJT-X does not currently support that rig control mechanism. If there is enough interest I can look at implementing it, or if anyone wants to contribute an implementation as a pull request I will consider its inclusion in WSJT-X.

73
Bill
G4WJS.



 

 

 

--
Борис Романов

 


locked Re: #raspberryPi #install #raspberryPi #install

Karza
 

Thanks for the info Bill.

I should have known... :(

'Kari

On 24.11.2021 19.15, Bill Somerville wrote:
Hi Karl,

the default with no '-j' argument is a serial build, equivalent to '-j1'.

73
Bill
G4WJS.

On 24/11/2021 17:13, Karza wrote:
Hi Edd,

perhaps you could try to use the -j parameter to reduce the number of parallelism of the compile process. ( Even down to 1 )

Of course the compile will then take ( a lot ) more time, but might actually succeed.

( Once upon a time I was too eager and pecified too large number for -j which then caused compile failure. )

73's de Kari, oh2gqc




On 24.11.2021 18.30, Edward Seeliger wrote:
Good afternoon Bill - thanks.
I did not add any suffixes (-j) / options to the build command except as specified in the tarball instructions. But that is what I suspect is happening.
I will have to research (learn again) how to change (temporaily) the memory allotment on the RPI and see if that works.
Thanks.
Edd - KD5M







locked Re: TCI-Client for Sun SDR #Cat_RigControl

Борис Романов
 

Hi Bill, Mike
This question arose during the discussion on the site forum.qrz.ru of the capabilities of the WSJTX, JTDX and MSHV programs by users of SUN SDR transceivers. Surprised that WSJTX does not use TCI communication technology.
Thanks.
73 Boris UX8IW
Среда, 24 ноября 2021, 0:39 +02:00 от Bill Somerville <g4wjs@...>:
 
On 23/11/2021 19:33, Борис Романов via groups.io wrote:
Hi,
Maybe I don’t know something, but I want to ask.
Is the WSJTX program supposed to control the SDR transceiver (CAT and sound) via the TCI interface?
This control is implemented in the JTDX and MSW programs.
73 Boris UX8IW

Hi Boris,

as far as I am aware, you are the first to ask. No WSJT-X does not currently support that rig control mechanism. If there is enough interest I can look at implementing it, or if anyone wants to contribute an implementation as a pull request I will consider its inclusion in WSJT-X.

73
Bill
G4WJS.



 
 
 
--
Борис Романов
 


locked Re: #raspberryPi #install #raspberryPi #install

Bill Somerville
 

Hi Karl,

the default with no '-j' argument is a serial build, equivalent to '-j1'.

73
Bill
G4WJS.

On 24/11/2021 17:13, Karza wrote:
Hi Edd,

perhaps you could try to use the -j parameter to reduce the number of parallelism of the compile process. ( Even down to 1 )

Of course the compile will then take ( a lot ) more time, but might actually succeed.

( Once upon a time I was too eager and pecified too large number for -j which then caused compile failure. )

73's de Kari, oh2gqc




On 24.11.2021 18.30, Edward Seeliger wrote:
Good afternoon Bill - thanks.
I did not add any suffixes (-j) / options to the build command except as specified in the tarball instructions. But that is what I suspect is happening.
I will have to research (learn again) how to change (temporaily) the memory allotment on the RPI and see if that works.
Thanks.
Edd - KD5M



locked Re: #raspberryPi #install #raspberryPi #install

Karza
 

Hi Edd,

perhaps you could try to use the -j parameter to reduce the number of parallelism of the compile process. ( Even down to 1 )

Of course the compile will then take ( a lot ) more time, but might actually succeed.

( Once upon a time I was too eager and pecified too large number for -j which then caused compile failure. )

73's de Kari, oh2gqc




On 24.11.2021 18.30, Edward Seeliger wrote:
Good afternoon Bill - thanks.
I did not add any suffixes (-j) / options to the build command except as specified in the tarball instructions. But that is what I suspect is happening.
I will have to research (learn again) how to change (temporaily) the memory allotment on the RPI and see if that works.
Thanks.
Edd - KD5M


locked Re: #raspberryPi #install #raspberryPi #install

Bill Somerville
 

On 24/11/2021 16:30, Edward Seeliger wrote:
Good afternoon Bill - thanks.
I did not add any suffixes (-j) / options to the build command except as specified in the tarball instructions. But that is what I suspect is happening.
I will have to research (learn again) how to change (temporaily) the memory allotment on the RPI and see if that works.
Thanks.
Edd - KD5M
Hi Edd,

OK. Make sure you don't have other unnecessary applications running while the build is running. I have not tried a build on a Pi Zero, I believe the Pi Zero 2 W only has 1/2 Gbyte of RAM and that may well not be enough. Do you have another Pi system with more memory you can build on?

73
Bill
G4WJS.


locked Re: #raspberryPi #install #raspberryPi #install

Edward Seeliger
 

Good afternoon Bill - thanks.
I did not add any suffixes (-j) / options to the build command except as specified in the tarball instructions. But that is what I suspect is happening.
I will have to research (learn again) how to change (temporaily) the memory allotment on the RPI and see if that works.
Thanks.
Edd - KD5M


locked #FST4 Coding #FST4

Andy Talbot
 

Just curious:
Why is the compacted data for FST4 scrambled whereas the other LDPC modes FT4/8 and  MSK144 are not?   The latters' compressed data conveniently appears directly in the  symbols.


locked Re: #raspberryPi #install #raspberryPi #install

Bill Somerville
 

Willie,

the INSTALL instructions are a lot easier if you follow them, hi!

There is no need to build Hamlib separately if you use the WSJT-X sources tarball we provide, in fact it is pointless as the sources tarball already includes Hamlib and the build script builds Hamlib and statically links it into WSJT-X.

73
Bill
G4WJS.

On 24/11/2021 15:24, William Smith wrote:
The instructions in the source tarall are much easier to parse if you already know what you are doing.  🤷‍♂️

I got some hints from http://www.kk5jy.net/wsjtx-build/

Here's what I did:

From a clean Bullseye install (11.1) via Raspberry Pi Imager

sudo apt-get install cmake

export CXXFLAGS='-O2 -march=native -mtune=native'
export CFLAGS='-O2 -march=native -mtune=native'

sudo apt-get install emacs-nox (or your favorite editor to build the script below)
build a script from the webpage above and execute it (takes a long time)

wget https://github.com/Hamlib/Hamlib/releases/download/4.3.1/hamlib-4.3.1.tar.gz
tar xvzf <that>
cd <there>
/configure --prefix=/usr/local --enable-static
make
sudo make install
sudo ldconfig
rigctl --version shows: rigctl Hamlib 4.3.1 Mon Sep 13
which rigctl returns: /usr/local/bin/rigctl
reboot to confirm somehting doesn't break
Success!

----------  Now for wsjt-x

export CXXFLAGS='-O2 -march=native -mtune=native'
export CFLAGS='-O2 -march=native -mtune=native'

wget https://physics.princeton.edu/pulsar/k1jt/wsjtx-2.5.2.tgz
tar xvzf <that>
cd <there>
cd src
[Aha!  This is where hamlib 4.4 comes from!]
tar -zxvf wsjtx.tgz
mkdir build
cd build
cmake ../wsjtx
make
sudo make install


Hope this helps!

73, Willie N1JBJ

On Nov 24, 2021, at 10:17 AM, Edward Seeliger <eseeliger@...> wrote:

I have attempted to build wsjtx-2.5.2 for Raspian Bullseye (32 GB card) from source for the RPI Zero W2 following the recipe contained in the source tarball.
The build fails (crashes the RPI Zero W2) at the 61% location (Performing build step for 'wsjtx'). There are no error messages.
I must restart the RPI Zero W2 to recover operation.
The recipe builds hamlib without errors.
I have installed all the dependencies as listed and installed CMake using snap - CMake version 3.22.0 --Classic version. All the dependencies exceed the minimum required versions.
Any suggestions on how to proceed / correct the error are appreciated.
Edd - KD5M



locked Re: #raspberryPi #install #raspberryPi #install

William Smith
 

The instructions in the source tarall are much easier to parse if you already know what you are doing.  🤷‍♂️

I got some hints from http://www.kk5jy.net/wsjtx-build/

Here's what I did:

From a clean Bullseye install (11.1) via Raspberry Pi Imager

sudo apt-get install cmake

export CXXFLAGS='-O2 -march=native -mtune=native'
export CFLAGS='-O2 -march=native -mtune=native'

sudo apt-get install emacs-nox (or your favorite editor to build the script below)
build a script from the webpage above and execute it (takes a long time)

wget https://github.com/Hamlib/Hamlib/releases/download/4.3.1/hamlib-4.3.1.tar.gz
tar xvzf <that>
cd <there>
/configure --prefix=/usr/local --enable-static
make
sudo make install
sudo ldconfig
rigctl --version shows: rigctl Hamlib 4.3.1 Mon Sep 13
which rigctl returns: /usr/local/bin/rigctl
reboot to confirm somehting doesn't break
Success!

----------  Now for wsjt-x

export CXXFLAGS='-O2 -march=native -mtune=native'
export CFLAGS='-O2 -march=native -mtune=native'

wget https://physics.princeton.edu/pulsar/k1jt/wsjtx-2.5.2.tgz
tar xvzf <that>
cd <there>
cd src
[Aha!  This is where hamlib 4.4 comes from!]
tar -zxvf wsjtx.tgz
mkdir build
cd build
cmake ../wsjtx
make
sudo make install


Hope this helps!

73, Willie N1JBJ

On Nov 24, 2021, at 10:17 AM, Edward Seeliger <eseeliger@...> wrote:

I have attempted to build wsjtx-2.5.2 for Raspian Bullseye (32 GB card) from source for the RPI Zero W2 following the recipe contained in the source tarball.
The build fails (crashes the RPI Zero W2) at the 61% location (Performing build step for 'wsjtx'). There are no error messages.
I must restart the RPI Zero W2 to recover operation.
The recipe builds hamlib without errors.
I have installed all the dependencies as listed and installed CMake using snap - CMake version 3.22.0 --Classic version. All the dependencies exceed the minimum required versions.
Any suggestions on how to proceed / correct the error are appreciated.
Edd - KD5M




locked Re: #raspberryPi #install #raspberryPi #install

Bill Somerville
 

On 24/11/2021 15:17, Edward Seeliger wrote:
I have attempted to build wsjtx-2.5.2 for Raspian Bullseye (32 GB card) from source for the RPI Zero W2 following the recipe contained in the source tarball.
The build fails (crashes the RPI Zero W2) at the 61% location (Performing build step for 'wsjtx'). There are no error messages.
I must restart the RPI Zero W2 to recover operation.
The recipe builds hamlib without errors.
I have installed all the dependencies as listed and installed CMake using snap - CMake version 3.22.0 --Classic version. All the dependencies exceed the minimum required versions.
Any suggestions on how to proceed / correct the error are appreciated.
Edd - KD5M
Hi Ed,

you may be running out of memory during the build. Make sure you do not add a '-j' option to the build command as parallel building will surely use too much memory.

73
Bill
G4WJS.


locked #raspberryPi #install #raspberryPi #install

Edward Seeliger
 

I have attempted to build wsjtx-2.5.2 for Raspian Bullseye (32 GB card) from source for the RPI Zero W2 following the recipe contained in the source tarball.
The build fails (crashes the RPI Zero W2) at the 61% location (Performing build step for 'wsjtx'). There are no error messages.
I must restart the RPI Zero W2 to recover operation.
The recipe builds hamlib without errors.
I have installed all the dependencies as listed and installed CMake using snap - CMake version 3.22.0 --Classic version. All the dependencies exceed the minimum required versions.
Any suggestions on how to proceed / correct the error are appreciated.
Edd - KD5M


locked Re: Unsupported command sent to IC-746 #Cat_RigControl

Dean Souleles
 

On Tue, Nov 23, 2021 at 05:41 AM, Bill Somerville wrote:
I think you are using MS Windows, in that case all you need do is replace the libhamlib-4.dll file with the latest one from the link Mike provided. There's no need to re-build WSJT-X.
Thanks so much Bill, that's good to know.  For future reference - when I built WSJT-X from source I used the MSYS2 menu to pull and build the hamlib master branch.  I then built WSJT-X and made an installation package and used that to install WSJT-X.  I noted that the version string on the About string was unchanged from the 2.5.2 release - which I presume is because the WSJT-X source was pulled from the 2.5.2 release branch and not the current development branch.  But I still got new hamlib dll with the installation package since Mike made the change to the master branch.

Is that about right? 

And, out of curiosity more than anything else if I wanted to pull the current development build of WSJT-X how would I do that - or is that not a thing?

By the way, gents, true confession - I am a 40 year +software guy - and truly impressed.  Whomever built the JTSDK64 has my admiration and respect. 
that is quite a feat to get a complex development chain like that correct - and it worked fine business.  No to mention the overall ambition of hamlib to support all of these under-documented rigs and, of course, the wonder of WSJT-X itself. I was ready for a long night slog and it just worked.
 
Thanks Bill and Mike for everything you do for the hobby and 73,
Dean
KK4DAS


locked Re: WSJTX FT8 intermittent decode of my call on receive #TechnicalHelpQuestion #FT8

Martin G0HDB
 

On Tue, Nov 23, 2021 at 03:43 PM, ka2qit wrote:
Martin,
Yes I did disable the xmission as I kept sending the same sig rpt. While I assume the other station continued confirming, (due to sig strength). I do have a high noise level and will try another sequence with the noise blanker engaged, and run an uninterrupted sequence.
Hi again Bob, you haven't said what make and model of rig you're using, but are you operating it with AGC on or off?

If your rig is an Icom IC-7600 or IC-7610, or maybe some other make and model, then operating with AGC off is not always the optimum approach especially when there are large signals on the band.  More specifically, when operated with AGC off the audio output from an IC-7600 and an IC-7610 starts to become severely distorted at quite modest input signal levels, eg. around S4.  The presence of such distortion on the audio being fed into WSJT-X can really screw up the decoding.

If you are operating your rig, whatever make and model it is, with AGC off then I'd suggest you try turning AGC on and setting the audio levels to give a reading of in the region of 65dB, instead of 30dB, on the WSJT-X audio level bargraph when you're receiving only band noise.  In addition, I'd adjust your rig's input attenuator, if it has one, and/or the RF gain control so that you get an S-meter reading in the region of S0 to S1 when receiving only band noise - this will help ensure that there's little or no AGC action caused by your local noise.  There's no point at all in having the noise causing an S-meter reading in the region of, for example, S5-6 (or higher!).

--
Martin G0HDB


locked Re: WSJTX FT8 intermittent decode of my call on receive #TechnicalHelpQuestion #FT8

SA5QED/David
 

I am sometimes experiencing similar QSO patterns. 
Is it possible that QU does not have Autosequencing checked?

73
SE5M
David


locked Re: TS-590SG and WSJTX errors

Bob McGraw - K4TAX <rmcgraw@...>
 

Yes, and per Jim's K9YC document. grounding does NOT help RFI issues.   OCFD antennas {i.e. Carolina Windom} are noted to have high levels of common-mode current.  Grounding does not correct or cure common mode current issues.   Don't believe "old wives tails" or better yet "old ham lore" on grounding.  Most were incorrect to start with and the telling get worse, not better.   

Jim, K9YC, has great information on common mode current issues and how to address them.  Thus grounding I don't recall as being a solution.  Now, bonding of all equipment cases is the first start in solution to the issue.   Use of proper RF chokes is next. 

73
Bob, K4TAX


locked Re: #txaudio #linux WSJT-X No TX audio issue #txaudio #linux

Doug
 

Oh and just in case it helps anyone else, the radio (Yaesu FTDX5000) was being controlled via a 'true' RS232 port (/dev/ttyS0) not a USB converter.


locked Re: #txaudio #linux WSJT-X No TX audio issue #txaudio #linux

Doug
 

Thanks Bill, the stream was not being created when using WSJT-x but was with the aforementioned app's, WSJT-x wasn't even keying the radio.
So after some digging I found a new version of hamlib available in the hamradio repository and installed that and now it (WSJT-x), JS8call and JTDX all transmit as expected :)
The 'vanilla' install of hamlib that SuSE installed appeared to be rather old (version 3.3-bp153) and once I found and installed the version from the hamradio repository (version 4.3.1-lp153.32) WSJT-x started to transmit.

Thanks for responding

Doug
N7BFS


locked Re: Runaway TX watchdog #macOS

Martin G0HDB
 

On Tue, Nov 23, 2021 at 01:00 AM, Jeremy Stark wrote:
After 11 TX attempts with no reply I get a Runaway TX watchdog alert. Is this expected behaviour?

--
Jeremy G7BHB
Yes, it is expected behaviour.

You can set the Tx watchdog time-out period via the Settings > General tab, but the time-out period you specify doesn't apply when you're operating as a DXpedition-mode Hound - the Guide states:

"You will need to re-activate Enable Tx (or hit Enter on the keyboard) at least once every two minutes.  (This restriction is to ensure that an operator is present and paying attention.)"

--
Martin G0HDB

6801 - 6820 of 36850