Recent changes to tickets

FT8 swamped by Dxpedition FT8WW

GLENN WILLIAMS — Mon, 02 Jan 2023 21:05:00 -0000

This is my first use of this means to write an opinion and I hope my entire paragraph is permitted.
The demand for Crozet FT8WW in 2022 is crushing the capabilities
of FT8 / MSHV to fulfill the dreams of thousands of amateur radio
operators. Unlike older modes (CW, SSB) where the DX station can only
decode a few signals at a time by ear, it is easy to believe that
a whole waterfall full of callers have their call signs repetitively
displayed twice a minute in the Band Activity window. But many of those
operators will never called back by FT8WW because at best only two or three
completions can be handled per minute and propagation effects will lower
the average rate. This is also a preview of what could happen with Bouvet
later this month. It is probably too late for any major improvements that will
assist in generating higher QSO rates before the end of Crozet or Bouvet. But the
problem should still be studied. Possible improvements could be a generous increase
in the number of streams transmitted by the DXpedition at the risk of dealing with
complaints about band-hogging and fair use. Of course, with MSHV being available for
installation by just about any FT8 operator, there would be the inevitable
concern for legitimate DXpedition use and preventing abuse by home operators.

Decode signal report changing

Michael Black — Sun, 01 Jan 2023 17:03:45 -0000

Was working/watching the Crozet dxpedition. As you can see in the attached FT8WW gave me several TX2 reports with changing dB levels. It would seem necessary for FT8WW to have decoded the TX1 transmission again in order to set a new dB level for TX2 (which I did not repeat TX1) but, if it did decode TX3 then it should have continued sequencing.
So how can a transmitter change dB levels on a TX-2 report without decoding the caller again? I've seen several of these occurring.

Debian Buster compile error

Emmanuel Lomba — Sat, 02 Jan 2021 23:42:01 -0000

Hello,
Trying to compile in Debian 10 buster. Everything goes OK until I get this error, after some time compiling:

/usr/bin/ld: src/Hv_Lib_fftw/lin_x86_64/libfftw3v337_gcc731_thread_posix.a(direct2.o): relocation R_X86_64_32 against .text' can not be used when making a PIE object; recompile with -fPIC /usr/bin/ld: src/Hv_Lib_fftw/lin_x86_64/libfftw3v337_gcc731_thread_posix.a(hc2hc-direct.o): relocation R_X86_64_32 against.text' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: final link failed: nonrepresentable section on output
collect2: error: ld returned 1 exit status
make: *** [Makefile:707: bin/MSHV_x86_64] Error 1

Can't anything helpful on the Internet... I thank anyone who could give a hint.

Best regards,
Emmanuel.

Compile error on Debian Buster

Vittorio Vallero — Tue, 20 Oct 2020 15:30:53 -0000

Trying to compile MSHV_247 on Debian 10 Buster 64 bit I immediately get this error:

vittorio@ik1rac:/tmp/MSHV_247$ make
g++ -c -m64 -pipe -std=gnu++11 -ffast-math -fno-trapping-math -funsafe-math-optimizations -freorder-functions -funroll-all-loops -O2 -Wall -W -D_REENTRANT -D_LINUX_ -DQESP_NO_UDEV -D__linux__ -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtGui -I/usr/include/qt4 -Ibuild -o build/main.o src/main.cpp
In file included from src/HvDecodeList/decodelist.h:52,
from src/main_ms.h:31,
from src/main.cpp:15:
src/HvDecodeList/hvtooltip.h:19:51: error: ‘Q_NULLPTR’ was not declared in this scope
void showText(QPoint,QString,int,QWidget w = Q_NULLPTR);
^~~~~~~~~
make: ** [Makefile:1238: build/main.o] Error 1

Any hint?
Thanks

help value not declare

Jeff — Mon, 12 Dec 2016 19:37:24 -0000

I try to install MSHV on a xubuntu 16 but i have a trouble in the compilation ( withQt4 )
the error is :

src/main_ms.cpp: In constructor ‘Main_Ms::Main_Ms(QWidget*)’:
src/main_ms.cpp:55:20: error: ‘APP_NAME’ was not declared in this scope
setWindowTitle(APP_NAME);
^
src/main_ms.cpp: In member function ‘void Main_Ms::BandChanged(bool)’:
src/main_ms.cpp:857:29: error: ‘APP_NAME’ was not declared in this scope
QString str_t = APP_NAME;

What must i do because i don't find the value APP_Name anywhere ?
Thanks
Jeff

#1 help_bg.html and libasound on Ubuntu 14.04

Wojciech Kazubski — Sun, 20 Dec 2015 19:02:58 -0000

While trying to build MSHV I foud that it is using fixed patch to alsa library
Could you replace it with -lasound?
It should be more universal, and work on every distribution if alsa development packages (alsa-dev or alsa-devel) are installed.

I think that all distributions already have fftw3 library, so there is no need to have local one
It should be sufficient to have:

LIBS = -lasound -lfftw3 ...

73 de SP5SMK

help_bg.html and libasound on Ubuntu 14.04

F5JMH — Mon, 25 May 2015 13:12:08 -0000

Hello, ans sorry for my english...

I'm testing install of MSHV on Ubuntu 14.04 and report you this small problems :

On qmake :
RCC: Error in 'src/HvHelpMs/hvhelpms.qrc': Cannot find file 'url/help_bg.html'
I'm copying help_en.html in help_bg.html and OK

On make :
For libasound library for Ubuntu is situated in /usr/lib/x86_64-linux-gnu/. After correct the file MSHV_x86_64.pro :
Line 101 :
LIBS = /usr/lib/x86_64-linux-gnu/libasound.so src/Hv_Lib_fftw/lin_x86_64/libfftw3v334_gcc482_thread_posix.a src/HvRigControl/qextserialport_1_2rc/lin_x86_64/libqextserialport_gcc482_thread_posix.a

After that make and qmake OK and start MSHV is OK also.

Best 73. Alain