Date   

locked Re: FST4 on 160m experiment / Calling CQ now! #FT4

Jim Brown
 

On 11/20/2020 11:03 AM, Amos Sobel 4X4MF wrote:
Join me in FST4 160m. This evening 19:00-22:00 UTC I will call CQ and listen:
1. Using WSJT-X v2.3.0 rc2
2. Mode=FST4 Single Decode
3. Frequency=1839.00 KHz
This period looks promising within EU, AF, and AS, but not for NA. How about 1 hour +/- your sunrise, which allows for propagation to NA and SA?

I'd love to see all 160M operation move from FT8 to FST4. K1JT has observed that FST4-60 is 1.7 dB more sensitive than JT9. I've missed a lot of FT8 QSOs to EU from my QTH near San Francisco that these new modes have the potential to complete!

73, Jim K9YC


locked Re: problem with cmake

Bill Somerville
 

On 20/11/2020 20:17, Greg Cook via groups.io wrote:
Hi Bill,

The build failed at the output below

[ 94%] Building CXX object CMakeFiles/wsjtx.dir/main.cpp.o
/home/pi/Downloads/build/wsjtx-prefix/src/wsjtx/main.cpp: In function ‘void {anonymous}::safe_stream_QVariant(boost::log::v2_mt_posix::record_ostream&, const QVariant&)’:
/home/pi/Downloads/build/wsjtx-prefix/src/wsjtx/main.cpp:79:50: error: no matching function for call to ‘QByteArray::toHex(char)’
         os << "0x" << v.toByteArray ().toHex (':').toStdString ();
                                                  ^
In file included from /usr/include/arm-linux-gnueabihf/qt5/QtCore/qstring.h:49:0,
                 from /usr/include/arm-linux-gnueabihf/qt5/QtCore/qobject.h:47,
                 from /usr/include/arm-linux-gnueabihf/qt5/QtCore/qsharedmemory.h:43,
                 from /usr/include/arm-linux-gnueabihf/qt5/QtCore/QSharedMemory:1,
                 from /home/pi/Downloads/build/wsjtx-prefix/src/wsjtx/main.cpp:11:
/usr/include/arm-linux-gnueabihf/qt5/QtCore/qbytearray.h:361:16: note: candidate: QByteArray QByteArray::toHex() const
     QByteArray toHex() const;
                ^~~~~
/usr/include/arm-linux-gnueabihf/qt5/QtCore/qbytearray.h:361:16: note:   candidate expects 0 arguments, 1 provided
Hi Greg,

getting closer. Apologies for not doing this all in one go, I currently do not have space for a new Linux VM. Attached a revised patch file that should fix that compilation error.

73
Bill
G4WJS.


locked Re: odd bunch of signals on top band now

Ken - K4XL
 

Using Fox/Hounds.

On Fri, Nov 20, 2020 at 3:02 PM Russ Ravella via groups.io <rus5=me.com@groups.io> wrote:
Russian DXPedition to Malawi Africa






On Nov 20, 2020, at 11:13 AM, geoff wiggins via groups.io <g4xmj@...> wrote:

Hi Group.

There is an extraordinary group of signals on top band now that are FT8 around 1.836 Mhz. Looks like a Russian station is working about 25 stations at the same time! Anyone know what's going on? The call is 7Q7RU.

73 Geoff.










--
Ken - K4XL
BoatAnchor Manual Archive
BAMA - http://bama.edebris.com


locked Re: problem with cmake

Greg Cook
 

Hi Bill,

The build failed at the output below

[ 94%] Building CXX object CMakeFiles/wsjtx.dir/main.cpp.o
/home/pi/Downloads/build/wsjtx-prefix/src/wsjtx/main.cpp: In function ‘void {anonymous}::safe_stream_QVariant(boost::log::v2_mt_posix::record_ostream&, const QVariant&)’:
/home/pi/Downloads/build/wsjtx-prefix/src/wsjtx/main.cpp:79:50: error: no matching function for call to ‘QByteArray::toHex(char)’
         os << "0x" << v.toByteArray ().toHex (':').toStdString ();
                                                  ^
In file included from /usr/include/arm-linux-gnueabihf/qt5/QtCore/qstring.h:49:0,
                 from /usr/include/arm-linux-gnueabihf/qt5/QtCore/qobject.h:47,
                 from /usr/include/arm-linux-gnueabihf/qt5/QtCore/qsharedmemory.h:43,
                 from /usr/include/arm-linux-gnueabihf/qt5/QtCore/QSharedMemory:1,
                 from /home/pi/Downloads/build/wsjtx-prefix/src/wsjtx/main.cpp:11:
/usr/include/arm-linux-gnueabihf/qt5/QtCore/qbytearray.h:361:16: note: candidate: QByteArray QByteArray::toHex() const
     QByteArray toHex() const;
                ^~~~~
/usr/include/arm-linux-gnueabihf/qt5/QtCore/qbytearray.h:361:16: note:   candidate expects 0 arguments, 1 provided
CMakeFiles/wsjtx.dir/build.make:903: recipe for target 'CMakeFiles/wsjtx.dir/main.cpp.o' failed
make[5]: *** [CMakeFiles/wsjtx.dir/main.cpp.o] Error 1
CMakeFiles/Makefile2:1486: recipe for target 'CMakeFiles/wsjtx.dir/all' failed
make[4]: *** [CMakeFiles/wsjtx.dir/all] Error 2
Makefile:149: recipe for target 'all' failed
make[3]: *** [all] Error 2
CMakeFiles/wsjtx-build.dir/build.make:60: recipe for target 'wsjtx-prefix/src/wsjtx-stamp/wsjtx-build' failed
make[2]: *** [wsjtx-prefix/src/wsjtx-stamp/wsjtx-build] Error 2
CMakeFiles/Makefile2:388: recipe for target 'CMakeFiles/wsjtx-build.dir/all' failed
make[1]: *** [CMakeFiles/wsjtx-build.dir/all] Error 2
Makefile:83: recipe for target 'all' failed
make: *** [all] Error 2
pi@raspberrypi:~/Downloads/build $

Greg


locked Re: odd bunch of signals on top band now

Russ Ravella
 

Russian DXPedition to Malawi Africa

On Nov 20, 2020, at 11:13 AM, geoff wiggins via groups.io <g4xmj@...> wrote:

Hi Group.

There is an extraordinary group of signals on top band now that are FT8 around 1.836 Mhz. Looks like a Russian station is working about 25 stations at the same time! Anyone know what's going on? The call is 7Q7RU.

73 Geoff.






locked Re: problem with cmake

Greg Cook
 

Hi Bill,

Thanks for all your work on this.

Tried building rc2 with new patch. Version errors no longer flagged, but the build appears to hang at the following line with the 'disk' light on full time, although the system is still running (albeit slowly):

[  1%] Building CXX object CMakeFiles/qcp.dir/qcustomplot-source/qcustomplot.cpp.o

I have an identical Pi3 so have tried an identical build, and this one gets past this point, and is still running even as we speak it's done 14%. I'll keep you posted and try to figure out why the Pi3's aren't identical after all and see if I have anything running differently....

73's Greg g4cui


locked Re: Hamlib error

Kevin Utzy
 

Ken,
If you could send me the screen pictures as well.  I was fine with my settings until the 2.2.3-rc releases. I screwed up something.
Thank you.
73,
Kevin
KX4KU


locked Re: FST4 on 160m experiment / Calling CQ now! #FT4

Amos Sobel 4X4MF
 

Calling CQ now!

 

From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Amos Sobel 4X4MF
Sent: Friday, November 20, 2020 5:24 PM
To: main@WSJTX.groups.io
Subject: [WSJTX] FST4 on 160m experiment #FT4

 

Hi Folks!

Join me in FST4 160m. This evening 19:00-22:00 UTC I will call CQ and listen:
1. Using WSJT-X v2.3.0 rc2
2. Mode=FST4 Single Decode
3. Frequency=1839.00 KHz
4. Tx=Rx=1500 Hz
5. F Tol=100 Hz
6. T/R=60 Sec
7. Radio bandpass filter=3000 Hz
8/ Please call me and report if I do not answer. I will report what I hear.
73's
Amos 4X4MF


locked Re: Auto Antenna Tune TX- WSPR

bud Thompson N0IA
 

Thanks for your comment.

I doubt that many external auto tuners these days would fail in the early years by being used intermittently for a month or so 24/7 every once in a while.  There are several mechanical relays involved, the rest is electronic components.  It is possible that the manufacturers have data (or educated guesses) on failure rate vs use.  Most mechanical relays have such stats.  Last month one of the first "HD TVs" I'd had for 12 years failed. That TV was on a lot over the years.  There use to be a colloquial saying about these 'modern electronics devices:'  If you turn your TV on and off several times a day it will last about six or seven years.  If you leave it on 24/7 it will last about six or seven years.

In my case, I'm 83 years old - and hope to out live my remote auto tuner.

bud N0IA

 


locked Re: v.2.3.0-rc2 sequencing not correct #IssueReport

Carl - WC4H
 

The thing is that there have been sequencing errors creeping in.

Here's another where I should have been going to CQ but a 73 was sent.


locked Re: odd bunch of signals on top band now

geoff wiggins
 

Ignore, just worked it out, cluster.

73.

On 20/11/2020 18:13, geoff wiggins via groups.io wrote:
Hi Group.

There is an extraordinary group of signals on top band now that are FT8 around 1.836 Mhz. Looks like a Russian station is working about 25 stations at the same time! Anyone know what's going on? The call is 7Q7RU.

73 Geoff.





locked Re: v.2.3.0-rc2 sequencing not correct #IssueReport

Carl - WC4H
 

Hi Kevin.

I highlighted the wrong error... if you see the line below the RR73, my system sent a CQ.. I had to hit the 73 manually.  I posted it after having saved the screen and looked at it crossed eye.

Still a sequencing error.

Thanks.
Carl - WC4H


locked odd bunch of signals on top band now

geoff wiggins
 

Hi Group.

There is an extraordinary group of signals on top band now that are FT8 around 1.836 Mhz. Looks like a Russian station is working about 25 stations at the same time! Anyone know what's going on? The call is 7Q7RU.

73 Geoff.


locked Re: LoTW User Error .. WAS: [WSJTX] main@WSJTX.groups.io

neil_zampella
 

I suspect you've gone from the 32 bit version to the 64 bit version (or vice versa).   The answer is you need to install the proper Open SSL library for the program type you're using.    The URL to download is listed in the WSJT-X User Guide

Neil, KN3ILZ

On 11/20/2020 10:32 AM, Cliff Lumpkin wrote:

Error Loading LoTW User Data

 

Network Error - SSL/TLS support not installed, cannot fetch: ‘https://lotw.arrl.org/lotw-user-activity.csv

 

Not an issue when loading 2.2.2.

 

KC4AIF

Cliff





locked Re: No tones on transmit- no power out on transmit.

KEN G4APB
 

Hi Bill,
I had a similar problem, I did report the text below but received no reply but I think it is related.:-
I found that in FST4W mode, if I select Tx Enable and Tx Next, although the PTT is activated, there are no transmit tones. If I select TUNE, all is well. 

It seems I have to wait for the NEXT tx cycle before the tones come through. I reported this in -rc1.
Rig is Yaseu FT897D, Windows 7 home laptop. running wsjt-x v2.3.0-rc2. Cat control and audio via laptop mic and headphone sockets. 
I actually connected a scope to the audio out from my laptop and observed no tx tones during ptt enabled and first transmission, my Tx was on but no output power (as in USB mode). When I got to the 2nd transmission (quite a lot later as I was trying FST4W 300 on 80m), tones were produced for the 300 seconds although I was unable to decode myself on a second receiver and 2nd laptop, At the end of transmission, ptt went off but there was a single tone still coming out of the audio socket, seen on the ‘scope. I had an evening of transmitting FST4W on 80m with no-one spotting me. A 2nd QRP Tx of mine running WSPR was heard all over Europe on the same evening.
hope this helps you diagnose the problem.
73 Ken G4apb 


locked Re: 2.3.0 rc2 Unexpected behavior

JP Tucson, AZ
 

Hi Tony,

The only problem with your theory is that it (wsjtx) calls on you respond & log as it starts sending out the RR73 (TX4) message. 

What you are suggesting can only be done manually, and this discussion is about the AUTO-sequencer not operating quite right.

Personally, I think the issue comes down to 2 different & apparently incompatible philosophies about the RRR vs. RR73  response & the logic bug it creates; both in software & practice. Perhaps the best choice is for wsjtx to pick one & offer only that  one choice.

Since I see about 90-95% of users use RR73... I think we should go with that.

73 - John - N7GHZ

On Fri, Nov 20, 2020, 9:07 AM Tony Collett via groups.io <tony.nbs=btinternet.com@groups.io> wrote:
I think Reino explanation is correct but not worded so that you understood?

The program only sent CQ because you had logged the QSO and cleared the fields.
If you had waited and not logged the QSO until after you saw his 73 message it would have behaved as you expected.

Perhaps there is a difference in behaviour in how it works with RRR or RR73 endings but so few now use RRR sequence that I can't be sure!

73
Tony G4NBS



locked main@WSJTX.groups.io

Cliff Lumpkin
 

Error Loading LoTW User Data

 

Network Error - SSL/TLS support not installed, cannot fetch: ‘https://lotw.arrl.org/lotw-user-activity.csv

 

Not an issue when loading 2.2.2.

 

KC4AIF

Cliff


locked Re: 2.3.0 rc2 Unexpected behavior

Tony Collett
 

I think Reino explanation is correct but not worded so that you understood?

The program only sent CQ because you had logged the QSO and cleared the fields.
If you had waited and not logged the QSO until after you saw his 73 message it would have behaved as you expected.

Perhaps there is a difference in behaviour in how it works with RRR or RR73 endings but so few now use RRR sequence that I can't be sure!

73
Tony G4NBS


locked Re: Intermittent choppy TX audio on macOS Big Sur (11.0.1)

Ross Wardrup
 
Edited


locked Re: FST4 on 160m experiment #FT4

Bruce
 

Ror NA, 160 just starts to open at 2200z. Could you please run later? I thank you in advance. Bruce, W8HW in Florida, USA

On 11/20/2020 10:24 AM, Amos Sobel 4X4MF wrote:
Hi Folks!

Join me in FST4 160m. This evening 19:00-22:00 UTC I will call CQ and listen:
1. Using WSJT-X v2.3.0 rc2
2. Mode=FST4 Single Decode
3. Frequency=1839.00 KHz
4. Tx=Rx=1500 Hz
5. F Tol=100 Hz
6. T/R=60 Sec
7. Radio bandpass filter=3000 Hz
8/ Please call me and report if I do not answer. I will report what I hear.
73's
Amos 4X4MF



18481 - 18500 of 36948