if you don't see this page in a frame then click Home

FAQ

Qt versions
QSSTV 9.0.x Installation on Fedora
QSSTV 9.0.x on Raspberry Pi 2
QSSTV 9.0.x on Banana Pi
Settings for the Spectrum and Waterfall Display
Compiler Errors
Serial ports and  serial USB
Rules for udev
Audio file recording and playback
DRM Hybrid Setup

Warning

Remember: SSTV has a 100% duty-cycle, so run at reduced power with the ALC at its minimum

Qt Versions

QSSTV has been developped and tested under Qt 5.
It also complies under Qt 4.8 (as of version 9.0.3)

Installation

For installation on Ubuntu and alikes, see the manual.

QSSTV 9.x on Fedora 22


Qt vesrion 4.8.6
sudo dnf gcc-c++ fftw3-devel qt-devel jasper-devel alsa-lib-devel 
sudo dnf pulseaudio-libs-devel hamlib-devel libv4l-devel

Proceed as in the installation section  of the manual but use qmake-qt4 instead of qmake.


QSSTV 9.x on Raspberry Pi B

I've not been successful at installing QSSTV 9.0 on a B version. This is a single core ARM processor that simply does not have enough processing power.


QSSTV 9.x on Raspberry Pi 2

Rasbian (Debian 7.8 Wheezy)
sudo apt-get install g++ libfftw3-dev libqt4-dev libpulse-dev
sudo apt-get install hamlib-dev libasound2-dev libjasper1 libjasper-dev libv4l-dev
This results in:
>qmake --version
QMake version 2.01a
Qt version 4.8.2

Ubuntu Mate 15.04

Proceed exactly as described in the  installation section

Banana Pi
Tested on Debian 7.8 (wheezy)

Upgrade so that you have the latest release
sudo apt-get update
sudo apt-get upgrade





Settings for the Spectrum and Waterfall Display

When you start using QSSTV, check if you have the following settings to start with:
spectrum settings

Depending on your souncard input value settings you can experiment with these values.

Compiler Errors

Users sometimes report compiler errors (such as symbol not found, unknown functions etc...). Sending the following information wil be a great help:

What distribution are you using: (e;g; Ubuntu  15.04, Fedora 22,  Mint 17 etc ..)
What is the version of Qt you compiling against:
type the following command:
qmake --version
It will give you something like:
QMake version 3.0
Using Qt version 5.4.1 in /usr/lib/x86_64-linux-gnu
Then 
make clean
make >> makelog.txt 2>&1
and send me the file  makelog.txt as  an attachement to  the mail at on4qz@telenet.be
 

Serial ports and serial USB

On some systems, the users are not added to the dialout  group. If
that case you won't be able to connect to the CAT interface.

Add your user to the dialout group.

Rules for udev

I find it easy to add my custom udev rules so that if I plug and unplug
USB devices they always get the same meaningful device name.

Therefore I create a file  99-persistent-usb.rules
under /etc/udev/rules.d
directory with the following content

SUBSYSTEM=="tty", ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="ea60", ATTRS{serial}=="IC-7600 0402350", SYMLINK+="icom7600"
SUBSYSTEM=="tty", ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="ea60", ATTRS{serial}=="0001", SYMLINK+="icom7000"
SUBSYSTEM=="tty", ATTRS{idVendor}=="04d8", ATTRS{idProduct}=="000a", ATTRS{serial}=="1234", SYMLINK+="gps"
I have 3 devices:

- An Icom 7600

- An Icom 7000 via a external USB adapter

- A custom GPS disciplined clock with a Microchip processor.

You can see that the build-in USB port of the Icom 7000 and 7600 both
uses the same chip, hence idVendor and idProduct are the same.

We can however made the distinction based on the  serial number.

>lsusb
Bus 003 Device 004: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light
Bus 003 Device 005: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light


gives us the information about the two icoms (idVendor:idProduct). They
look exactly the same. To find out the serialnumber we use the
following commands

>udevadm info -a -n /dev/ttyUSB0 | grep {serial} | head -n1
ATTRS{serial}=="IC-7600 0402350"
>udevadm info -a -n /dev/ttyUSB1 | grep {serial} | head -n1
ATTRS{serial}=="0001"

The only thing we need to add is the symbolic name of our interface.

SYMLINK+="icom7600"
SYMLINK+="icom7000"

The next time you reboot, the system will create a symbolic link:

/dev/icom7600-> /dev/ttyUSB0
/dev/icom7000-> /dev/ttyUSB1

That's much easier to remember 

Audio file recording and playback

Audacity is the easiest way to record audiofiles for later decoding by QSSTV.
Set Audacity to Stereo 48K samplerate and save it as a wav file. This way you can go to the configuration menu and select Sound Input ->From file.
When you hit the start button in the Receive window, it will ask for the file name.

When you made your recordings in another format, you can use Audacity to do format and rate conversions.
Open your recording and export the file as  Stereo 48000 sample rate.

DRM Hybrid Setup

There seems to be some confusion on how to setup the Hybrid configuration in QSSTV.
Here are some basic rules.
First we need a ftp server. This used to be the ftp server of VK4AES, but it has been desactivated since Erik past away.
You can use your own server, but here we will use an ftp server on qsl.net.
Go to www.qsl.net and request a web server (with ftp access)
Once you have your ftp server on qsl.net:
ftp to www.qsl.net and login with your username and password.
!! I M P O R T A N T -- M A N D A T  O R Y !!
Create 3 directories in the root.
1) HybridFiles1
2) RxOkNotifications1
3) OnlineCallsigns1 (for compatibility with EasyPal, not used at this moment by QSSTV)

The configuration would then be:

hybrid config

There has been some issues with filenames containing foreign charachters not being accepeted by the ftp servers.
(i.e.  ü, ä  etc..). This is not an issue with QSSTV, but rather with the settings on the ftp server site.