Date   

locked Re: Building from source code that is not in a self contained tarball? #install #raspberryPi

Karza
 

Hi David,

On 4.3.2022 1.22, davidlee Lee wrote:
I downloaded wsjtx-2.5.4.tgz and followed the directions in the INSTALL file.
It compiles and runs beautifully on the Pi4/Buster.

Now the fun starts!
I'd like to tinker with the source code. But it appears to be bound up inside a "Self-Contained Source Tarball."
Could you point me to a guide that shows how to extract the source files and compile from them?
Since you used the .tgz, you already have all the sources on your filesystem.

for example: "<youe source prefix>/build/wsjtx-prefix/src/wsjtx/WSJTXLogging.cpp"

I tried, naively, extracting the source files from wsjtx.tgz. This created a directory called wsjtx that contained a
whole bunch of interesting source code.
See above, you do not need to extract the sources again once you compiled the package.

To test my ability to make changes and re-compile, I made a trivial change to WSJTXLogging.cpp.
I changed "Log Start" to "Log Start David".
I then re-ran these steps from INSTALL:
cmake -DWSJT_SKIP_MANPAGES=ON -DWSJT_GENERATE_DOCS=OFF ../wsjtx-2.5.4
cmake --build .
sudo cmake --build . --target install

Everything compiled OK, but when I ran the new executable, The log file showed the old message "Log Start"
rather than my change "Log Start David"

So, I'm not sure how to tell the compilation system to use the individual source files (that I can edit) rather than
the "Self-Contained Source Tarball."4
You can use  the file "wsjtx.patch", see the INSTALL file.

I implement my own changes by copying the relevant source files into another directory and making my changes into those copied files.

I then use "git diff" to create the "wsjtx.patch" file and recompile.

There may be other ways, but that's how I'm doing it.

73's de Kari, oh2gqc


locked Re: #ApacheLabs #Windows07 #wsjt-x-crashing Hard Disk Failure forces Rebuilding System #ApacheLabs #Windows07 #wsjt-x-crashing

William Smith
 

I know you don’t want to hear this, but win7 reached EOL more than 2 years ago, and can’t really be considered ‘upgraded’.

I’d also query the state of the cooling system in a computer that old, could be overheating and crashing as you run more programs.

Just my perspective. Double your money back if not satisfied. 8*]

73, Willie N1JBJ


On Mar 4, 2022, at 4:01 AM, Dick Bingham <dick.bingham@...> wrote:

All of the Windows SW upgrades have been
installed.


locked #ApacheLabs #Windows07 #wsjt-x-crashing Hard Disk Failure forces Rebuilding System #ApacheLabs #Windows07 #wsjt-x-crashing

Dick Bingham
 

Greetings All

I had a hard disk failure on a DELL LATITUDE E6510 laptop running W-7 32-bit OS
The floppy HD has been replaced by a SSD and the OS upgraded to 64-bit plus
an added 4GB of RAM for 8GB total. All of the Windows SW upgrades have been
installed.

Equipment/SW:

ANAN-7000dle
OpenHPSDR mRX PS v3.4.7
WSJT-X v2.5.4
DXKeeper v16.4.5
JTAlert v2.51.0
Voicemeeter Banana

I installed HHD Virtual Serial Port Tools software to create several virtual ports
and after MANY mis-starts began making FT8 QSO's and logging them to LOTW
and DXKeeper.

Everything runs as expected until the system crashes. The formerly "GREEN"
dot in the WSJT-X display turns "RED" and I get an error message rig time-out.
=================================================
RIG CONTROL ERROR

Do you want to reconfigure the radio interface?

clicking on 'yes' results in

Hamlib error -----------------> communications
timed out
rig.c(972)rig_open return
while opening connection to rig

Meanwhile, WSJT-x FT8 continues to decode stations OK
and it appears the worked station WAS logged OK in
DXKeeper

=================================================
I do not think it is RF getting into something ===>

ALL wiring - power/antennas/interconnecting-cables/etc - connecting the ANAN-7000dle
KTA-500/KPA-500//laptop use 2.4"-OD MIX-31 with 7-turns of each wire/cable wound together
to make CM-chokes. As a result the ANAN-7000dle/amp/tuner/laptop/AC-power-to-
everything should be floating/isolated from RF issues.

ALL of the above listed hardware is bonded together and to a outside ground-rod connected
by a 6-foot long wire.. That ground-rod is connected to the mains-input ground-rod located
about 8-feet away.

I use CM-chokes (the above mentioned ferrite material and size) right at the feed-coax/antenna
interface for every antenna.

After every failure everything has to be shut down, the laptop re-ststarted, programs started
and begin again fresh.

The last restart I did something different - NOT loading JTAlert - and entering each QSO into
DXKeeper manually. Slow operation not being automated BUT it seems to be stable now for
nearly 30-minutes without JTAlert running.

Then I added JTAlert again and ran low power - 50-watts - for a while working/logging Q's and
after an hour or so experienced the same failure. So, no progress being made.

For several years I was using two/three year old SW and 32-bit W7 OS and Com0Com to
create extra virtual COM# ports. Had trouble with Com0Com during the rebuild so used
HHD Virtual Serial Port Tools software.

Losing QSO's during a crash is not good and I never know when this failure-mode is going
to bite me.

Also. is it possible to recover about 13K of logged QSO's from what I thought was a complete
backup of my system from an external Seagate HD ? As of now, I have about 40 new Q's in
DXKeeper !

73 Dick/w7wkr


locked Building from source code that is not in a self contained tarball? #install #raspberryPi

David Lee
 

I downloaded wsjtx-2.5.4.tgz and followed the directions in the INSTALL file.
It compiles and runs beautifully on the Pi4/Buster.

Now the fun starts!
I'd like to tinker with the source code. But it appears to be bound up inside a "Self-Contained Source Tarball."
Could you point me to a guide that shows how to extract the source files and compile from them?

I tried, naively, extracting the source files from wsjtx.tgz. This created a directory called wsjtx that contained a
whole bunch of interesting source code.

To test my ability to make changes and re-compile, I made a trivial change to WSJTXLogging.cpp.
I changed "Log Start" to "Log Start David".
I then re-ran these steps from INSTALL:
cmake -DWSJT_SKIP_MANPAGES=ON -DWSJT_GENERATE_DOCS=OFF ../wsjtx-2.5.4
cmake --build .
sudo cmake --build . --target install

Everything compiled OK, but when I ran the new executable, The log file showed the old message "Log Start"
rather than my change "Log Start David"

So, I'm not sure how to tell the compilation system to use the individual source files (that I can edit) rather than
the "Self-Contained Source Tarball."

I spend my days in front of Eclipse IDE, so this low level cmake stuff is a bit of a mystery to me.

Cheers,
David


locked Why am I not able to receive my own transmits? #raspberryPi #WSPR #SDR #NewUser

Alan Kilian
 

Earlier today I built a Raspberry PI WSPR transmitter and with no filtering, and just a 10-inch length of wire on the transmitter pin (to try and keep the noise in the band down) I could decode my own transmissions using an Airspy RTL-SDR V3 in direct-conversion mode connected to an EFHW antenna in front of my house.

There was so much splatter that I decoded sometimes 4 transmissions all on slightly different frequencies moving up and down multiples of 120Hz from my transmit frequency.

I built the output filter according to: https://n4mz.com/misc/WSPR_Presentation.pdf

After that there was a LOT less splatter (Although there is still some at +/1 120 Hz from my transmit frequency)

Now I'm not decoding my own transmissions at all.
I'm connected to a rod antenna now and I'm seemingly getting a clear signal.
I can see it clearly in the waterfall diagram.
Screenshots are at: https://photos.app.goo.gl/X7NUAQwWuACDpnYg6
I changed the transmit frequency up and down in the shots to make sure it was my transmitter I'm seeing.

Both Windows 10 computers have their clocks synced using Net Time from https://timesynctool.com/ and time.is says EXACT for both.

Any help would be appreciated for this beginner.

-Alan

73 KC1QHV


locked Re: K3S stopped transmitting on WSJT-X #Elecraft #stopped_working #Windows10

Elan Paim
 

And this is why better to move to iOS

On 3 Mar 2022, at 11:24, K1dj via groups.io <k1dj@...> wrote:

I am having a hard time navigating Windows to the point where I would be able to try to adjust the transmit audio level. Last night, I succeeded only in causing the receive audio to go haywire to the point where it is far into the red on WSJT-X. Is there a clear step by step explanation out there?
Thanks again.
Rich, K1DJ





locked Re: #install #MacOS #macOS #install #macOS

Steve Golson
 

It's working fine for me, on my 2018 Mac mini, Monterey 12.2.1

Did the plist file get copied properly? What's the result from this command:

/bin/ls -l /Library/LaunchDaemons/*wsj*

73
Steve
W1SEG


locked Re: #install #MacOS #macOS #install #macOS

Randy Diddel
 

Hi David,

The following has worked for me in the past from the command line:

Kill any running WSJTX

1. Open Terminal
2. Type: sudo rm -rf /Library/LaunchDaemons/com.wsjtx.sysctl.plist
3. Authenticate with your Admin password when prompted. Verify that /Volumes/WSJT-X/com.wsjtx.sysctl.plist is no longer in that directory
4. Reboot
5. RE-Mount the wsjtx.dmg when your machine is back up again
6. Copy over the latest version to /Applications (just to be sure it is the latest in /Applications)
7. Run sudo cp /Volumes/WSJT-X/com.wsjtx.sysctl.plist /Library/LaunchDaemons (again)
8. Test by launching WSJX.

I found that the Daemon cannot be overwritten while it is in use (loaded). Hence the delete/reboot/try again.

73!

--
Randy Diddel
K5RHD
DM79ku
Arvada, CO


locked Re: Significance of "F Tol" in cqlibrqtion mode #Yaesu

Joe
 

On Tue, Mar 1, 2022 at 10:52 PM, Tim Dawson wrote:

Perhaps this is my doing something incorrectly, but I have been unable to get
calibration to work on my WSJTX 2.5.4 deployment. This is a source build on
Linux with a Yaesu FT1000MPV-Field behind it, with Signallink interface (but
using CAT TX control).

For the longest time, I would collect the fmt.all file, and then hit the
button to compute, and get the utterly useless "fmt.all format error" (or
whatever it is . . . ) which gives *nothing* to go on. After much research, I
have found that that error results from being more than 2Hz off on the
measured tones (why it can't actually *SAY* that is another topic . . . ).

Looking, the files were showing 45 to 50 Hz off . . . which makes no sense,
since this radio is TCXO based, and I am sending and receiving fine.

To make a long story short, I found that with "F Tol" set to 50 (where it had
defaulted), I always got the errant readings. When I set "F Tol" to 1, I am
then within tenths of a Hz, as expected.

Very little is said in the docs regarding F Tol in calibration mode - is this
to be expected, or ? ? ?

Thanks,
Hi OM,

Messages in this thread suggest strongly that you haven't read and understood Section 13.1 of the WSJT-X User Guide:
https://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.5.4.html#_frequency_calibration
and the companion document linked there, https://physics.princeton.edu/pulsar/k1jt/FMT_User.pdf.

In Frequency Calibration mode, RxFreq and FTol together set the range of frequencies searched for your chosen calibration signals. As shown in the waterfall screen shot in Section 13.1 of the User Guide, a typically useful value for FTol is 50 Hz. You want FTol to be large enough for the software to find all trustworthy calibration signals you will use, but no so large that other interfering signals might be found instead. Again, the screen shot should help you to understand this logic.

User Guide instructions tell you to "check and edit the file fmt.all in the log directory and delete any spurious or outlier measurements." This is important! If you want good results, human judgment about data quality is essential.

I'm not sure what warning message you found to be "utterly useless" or "gives *nothing* to go on." The message presented when the calibration fitting algorithm suspects the presence of invalid data in your fmt.all seems pretty clear to me:
Calibration Error
Check fmt.all for
possible bad data.

File fmt.all contains a line of data for every 2.5 s of your measurements. With T/RE sequence time 30 s you will get 12 lines for each calibration signal in your list of FCal frequencies. Here are the first three lines of fmt.all for a calibration run at W2PU (column headings have been added):

UTC FkHz Offset fMeas DF S/N
----------------------------------------------------------------------------
21:52:04 660 1 1500 1502.589 2.589 -11.5 52.7
21:52:06 660 1 1500 1502.589 2.589 -11.7 53.0
21:52:09 660 1 1500 1502.588 2.588 -8.3 49.8

Notice that S/N is large -- this is a strong AM broadcast station -- and that the measured frequencies all agree to within a fraction of 1 Hz. Similar examples with more description can be found in https://physics.princeton.edu/pulsar/k1jt/FMT_User.pdf.

As as aid to the user, measurements with low S/N are flagged in fmt.all with an end-of-line asterisk. As a general rule these should be deleted from the file. You should also delete "outlier" measurements -- those that differ from others of the same signal of from the trend shown by all of your calibration signals by more than, say, 1 Hz. These are most likely spurious measurements. Again, more details can be found in the linked document.

After you have edited fmt.all, invoke "Tools -> Solve for calibration parameters" again. Valid results will NOT be changed by on your setting of FTol.

If you still need help, please provide your fmt.all file.

-- 73, Joe, K1JT


locked Re: yaesu FT100MP MkV set up problem for FT 8 #WSJTX_config #windows11

Joe Subich, W4TV
 

The issue is that the MP and MK V do not support "User Mode" in CAT.

IF I suddenly decide to go CW and use split operation with VFO B, the
software will display "Rig control error", correct. If I now press
"Retry" by mistake I most of the time must do a CPU-reset on the
FT1000 and edit my personal settings.
Most likely because the VFOs are not set up "normally" when using
"USER MODE" and the CPU gets into a bad state. I doubt there is
anything that hamlib can do in this case. I would disable CAT in
WSJTX if using "USER MODE" with the old MP or MK V.

73,

... Joe, W4TV


On 2022-03-03 8:17 AM, Michael Black via groups.io wrote:
Seems to me the solution to this is to shut down WSJT-X when doing CW.  Sounds like they don't play well together.
The only thing WSJTX should be doing is querying the frequency and mode which SHOULD be harmless.
Mike W9MDB
On Thursday, March 3, 2022, 03:40:05 AM CST, Goran <sm7dlk@...> wrote:
I use the following settings in my FT-1000MP Field.
Settings in Menu 8-6
nodE = PAc-Lo
dSP = oFSt=0
r-PLL=1500
r-CAr=453.500
t-PLL=1500
t_cAr=453.500
rtty-SFt=0
To enter FT8-Mode Press "PKT" twice (PKT and LSB will then lit)
Michael perhaps you remember that you helped me when my FT1000 hang. We had to do a CPU-reset on the Rig. I still have this problem from time to time if I dont pay attention.
IF I suddenly decide to go CW and use split operation with VFO B, the software will display "Rig control error", correct. If I now press "Retry" by mistake I most of the time must do a CPU-reset on the FT1000 and edit my personal settings. Not sure if this problem is solved in later DLL-version, as long as I pay attention to it I can live with it.
73
Goran SM7DLK
,


locked Re: K3S stopped transmitting on WSJT-X #Elecraft #stopped_working #Windows10

Michael Black
 

FYI...for Tx we had to set the MIC GAIN on the K3S to "3" and turn down the audio Playback level to -1.7 dB to get the 4 bars + 5th tickle setting.
The LIN OUT setting was adjusted to get 30dB on a quiet spot for Rx.

Mike W9MDB

On Thursday, March 3, 2022, 07:54:51 AM CST, K1dj via groups.io <k1dj@...> wrote:





With help from Mike W9MDB, this problem has been FIXED.  Thanks all.73 - Rich, K1DJ


locked Re: K3S stopped transmitting on WSJT-X #Elecraft #stopped_working #Windows10

K1dj
 

With help from Mike W9MDB, this problem has been FIXED.  Thanks all.73 - Rich, K1DJ


locked Re: yaesu FT100MP MkV set up problem for FT 8 #WSJTX_config #windows11

Goran
 

Correct... but easy to forget, hi.,

There are obviously differnt ways to set up the old Yaesu FT-1000MP.
I learned by reading these two pages.
http://ot1a.blogspot.com/2018/02/ft8-on-air-finally-yaesu-ft1000mp-mkv.html
https://www.microham.com/contents/en-us/d151.html
/Goran


locked Re: yaesu FT100MP MkV set up problem for FT 8 #WSJTX_config #windows11

Michael Black
 

Seems to me the solution to this is to shut down WSJT-X when doing CW.  Sounds like they don't play well together.

The only thing WSJTX should be doing is querying the frequency and mode which SHOULD be harmless.

Mike W9MDB

On Thursday, March 3, 2022, 03:40:05 AM CST, Goran <sm7dlk@...> wrote:





I use the following settings in my FT-1000MP Field.

Settings in Menu 8-6
nodE = PAc-Lo
dSP = oFSt=0
r-PLL=1500
r-CAr=453.500
t-PLL=1500
t_cAr=453.500
rtty-SFt=0

To enter FT8-Mode Press "PKT" twice (PKT and LSB will then lit)

Michael perhaps you remember that you helped me when my FT1000 hang. We had to do a CPU-reset on the Rig. I still have this problem from time to time if I dont pay attention.
IF I suddenly decide to go CW and use split operation with VFO B, the software will display "Rig control error", correct. If I now press "Retry" by mistake I most of the time must do a CPU-reset on the FT1000 and edit my personal settings. Not sure if this problem is solved in later DLL-version, as long as I pay attention to it I can live with it.
73
Goran SM7DLK
,


locked Re: K3S stopped transmitting on WSJT-X #Elecraft #stopped_working #Windows10

Dennis Wage <dwage@...>
 

Rich,

Microsoft, in an attempt to make it easier to navigate has made it harder
for us 'seasoned' Windows users.

As soon as I get out to the shack I'll try to send step by
step instructions.

On Thu, Mar 3, 2022 at 4:24 AM K1dj via groups.io <k1dj@...>
wrote:

I am having a hard time navigating Windows to the point where I would be
able to try to adjust the transmit audio level. Last night, I succeeded
only in causing the receive audio to go haywire to the point where it is
far into the red on WSJT-X. Is there a clear step by step explanation out
there?
Thanks again.
Rich, K1DJ






locked Re: error when Rig Control Error #Cat_RigControl #Windows10

Victor Reijs
 

Oops, had not realised that. Sorry.
I downloaded it and put it in the directory, now waiting for the event to
happen.

THANKS for the help.

All the best,

Victor

Op do 3 mrt. 2022 om 11:59 schreef Tom Melvin <tom@...>:

Victor

There is a dropbox link in the mail from Mike. That is the file he is
talking about it is:

https://www.dropbox.com/s/t52ngcalsgnpm8m/wsjtx_log_config.ini?dl=0


Tom
Tom@...




On 3 Mar 2022, at 00:26, Michael Black via groups.io <mdblack98=
yahoo.com@groups.io> wrote:

https://www.dropbox.com/s/t52ngcalsgnpm8m/wsjtx_log_config.ini?dl=0





locked Re: error when Rig Control Error #Cat_RigControl #Windows10

Tom Melvin
 

Victor

There is a dropbox link in the mail from Mike. That is the file he is talking about it is:

https://www.dropbox.com/s/t52ngcalsgnpm8m/wsjtx_log_config.ini?dl=0


Tom
Tom@...

On 3 Mar 2022, at 00:26, Michael Black via groups.io <mdblack98@...> wrote:

https://www.dropbox.com/s/t52ngcalsgnpm8m/wsjtx_log_config.ini?dl=0


locked Re: K3S stopped transmitting on WSJT-X #Elecraft #stopped_working #Windows10

K1dj
 

I am having a hard time navigating Windows to the point where I would be able to try to adjust the transmit audio level. Last night, I succeeded only in causing the receive audio to go haywire to the point where it is far into the red on WSJT-X. Is there a clear step by step explanation out there?
Thanks again.
Rich, K1DJ


locked Re: error when Rig Control Error #Cat_RigControl #Windows10

Victor Reijs
 

Hello Mike,

Op do 3 mrt. 2022 om 01:26 schreef Michael Black via groups.io <mdblack98=
yahoo.com@groups.io>:

Please place this file in
Which file do I need to put in C:\Users\[username]\AppData\Local\WSJT-X?

All the best,

Victor


locked Re: yaesu FT100MP MkV set up problem for FT 8 #WSJTX_config #windows11

Goran
 

I use the following settings in my FT-1000MP Field.

Settings in Menu 8-6
nodE = PAc-Lo
dSP = oFSt=0
r-PLL=1500
r-CAr=453.500
t-PLL=1500
t_cAr=453.500
rtty-SFt=0

To enter FT8-Mode Press "PKT" twice (PKT and LSB will then lit)

Michael perhaps you remember that you helped me when my FT1000 hang. We had to do a CPU-reset on the Rig. I still have this problem from time to time if I dont pay attention.
IF I suddenly decide to go CW and use split operation with VFO B, the software will display "Rig control error", correct. If I now press "Retry" by mistake I most of the time must do a CPU-reset on the FT1000 and edit my personal settings. Not sure if this problem is solved in later DLL-version, as long as I pay attention to it I can live with it.
73
Goran SM7DLK
,

7581 - 7600 of 39870