Date   

locked Re: Worked B4 issue

neil_zampella
 

Bill ... when you change the band in WSJT-X, the frequency will be sent to JT-Alert.  If you're just tuning manually, and not using CAT control to the rig, you're going to see that issue.   What you need to do is if you tune manually to a  band, manually change the band showing in WSJT-X to the one you're working.

Neil, KN3ILZ


On Fri, Nov 20, 2020 at 09:40 PM, Bill Parris wrote:

Using WSJT-X with JT Alert.  Stations worked B4 show up in JTAlert in Yellow.  I would like to only have stations worked B4 on the band I am using rather than is the current case, it shows as Worked B4 on any band.  In going to JTAlert under Worked B4 tab I see a note: "If the QRG is not set in WSJT-X, and if the decoded Callsign previously worked, regardless of band, it will be flagged as worked B4"  I have been unable to find anything in WSJT-X to set that has anything to do with Frequency or "QRG".  What do I need to do to only see worked B4 on the band I am using.  Been searching for days on this issue.  Thanks Bill


locked Re: WSJT-X Ver 2.3.0 Rc2 Error Message

Jim Shorney
 

http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.3.0-rc2_en.html#INSTALL_WIN



On Fri, 20 Nov 2020 19:24:24 -0800
"Thomas Webb" <tmwebb@...> wrote:

When I open WSJT-x 2.3.0 Rc2, I get an error message with the following....

Error  Loading LOTW Users Data
Network error - SSL/TLS support not installed,
can not fetch https:// lotw.arrl.org/lotw-user-activity.csv

I click 'OK' to acknowledge it, message goes away, and program functions as advertised.
Did not get this error message with Rc1.

Tom, WA9AFM


locked Re: Worked B4 issue

Reino Talarmo
 

Hi Bill,

This may be a JTAlert issue (I am not using it myself), but in wsjt-x Colors there are selections ‘New XXXX on Band’. Have you selected those?

 

73, Reino OH3mA

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Bill Parris
Sent: 20. marraskuuta 2020 22:30
To: main@WSJTX.groups.io
Subject: [WSJTX] Worked B4 issue

 

Using WSJT-X with JT Alert.  Stations worked B4 show up in JTAlert in Yellow.  I would like to only have stations worked B4 on the band I am using rather than is the current case, it shows as Worked B4 on any band.  In going to JTAlert under Worked B4 tab I see a note: "If the QRG is not set in WSJT-X, and if the decoded Callsign previously worked, regardless of band, it will be flagged as worked B4"  I have been unable to find anything in WSJT-X to set that has anything to do with Frequency or "QRG".  What do I need to do to only see worked B4 on the band I am using.  Been searching for days on this issue.  Thanks Bill


locked WSJT-X Ver 2.3.0 Rc2 Error Message

Thomas Webb
 

When I open WSJT-x 2.3.0 Rc2, I get an error message with the following....

Error  Loading LOTW Users Data
Network error - SSL/TLS support not installed,
can not fetch https:// lotw.arrl.org/lotw-user-activity.csv

I click 'OK' to acknowledge it, message goes away, and program functions as advertised.
Did not get this error message with Rc1.

Tom, WA9AFM


locked Error: Unable to send a datagram UDP server 127.0.0.1:2237

Bob Merrill
 

Hi Folks;

I am getting this message when booting WSJT.  Error: Unable to send a datagram
UDP server 127.0.0.1:2237  Cancel, Retry
If I click Retry the program locks. If I cancel the software appears to work ok.
Is there a setting I need to change, or other change I need to make?

Thanks
Bob
WI1O


locked Re: Hamlib error

Ken Miller <kenmiller2@...>
 

I’m sorry Kevin, what screen pictures do you need?

 

Ken K8HTL

Kenmiller2@...

 

 

 

Sent from Mail for Windows 10

 

From: Kevin Utzy
Sent: Friday, November 20, 2020 2:06 PM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Hamlib error

 

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 Worked B4 issue

Bill Parris
 

Using WSJT-X with JT Alert.  Stations worked B4 show up in JTAlert in Yellow.  I would like to only have stations worked B4 on the band I am using rather than is the current case, it shows as Worked B4 on any band.  In going to JTAlert under Worked B4 tab I see a note: "If the QRG is not set in WSJT-X, and if the decoded Callsign previously worked, regardless of band, it will be flagged as worked B4"  I have been unable to find anything in WSJT-X to set that has anything to do with Frequency or "QRG".  What do I need to do to only see worked B4 on the band I am using.  Been searching for days on this issue.  Thanks Bill


locked Re: problem with cmake

Bill Somerville
 

On 21/11/2020 00:31, Greg Cook via groups.io wrote:
Hi Bill,

Pleased to report that build successful and preliminary look at exe functionality looks ok.
Thanks for your help and I am happy to help out with any further betas on the Pi.

73 Greg g4cui
Hi Greg,

thanks for the update, glad you are up and running.

73
Bill
G4WJS.


locked Re: problem with cmake

Greg Cook
 

Hi Bill,

Pleased to report that build successful and preliminary look at exe functionality looks ok. 
Thanks for your help and I am happy to help out with any further betas on the Pi.

73 Greg g4cui


locked Re: problem with cmake

Greg Cook
 

Hi Bill,

I rebooted the machine that hung and then it ran to 94% and gave same error as the other Pi. Now doing concurrent builds on both Pi's with new patch file.

Greg


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

Amos Sobel 4X4MF
 

OK Jim

I am using 160m FT8 almost every morning. On Oct 28, 2020, had the first
and only one 160m QSO with the USA with a new antenna. I hope for many more.
Starting tomorrow morning , I will be active on FST4 too.

Amos 4X4MF

-----Original Message-----
From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Jim Brown
Sent: Friday, November 20, 2020 11:39 PM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] FST4 on 160m experiment / Calling CQ now! #FT4

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: 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

 

18561 - 18580 of 37039