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

FAQ

Qt versions
QSSTV Output messsages
QSSTV 8.1.X Installation on Centos
QSSTV 8.1.X Installation on openSUSE
QSSTV 8.1.X Installation on Fedora
Serial ports and  serial USB
Rules for udev
Credits

 

Warning

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

Qt Versions

In version 7.1.3 QSSTV is now also compatible with Qt 4.6. The preferred version will remain Qt 4.7.
QSSTV 8.1 has been compiled and tested on
- Ubuntu 12.10 and Qt version 4.8.3
- Ubuntu 13.10 and Qt version  5.1  and  5.2
- Centos  6.5 and Qt version 4.6.2
As the software is delivered in source format and compiled locally on your PC, other (higher) version have a good chance to work without problem.
If there are any problems compiling this version , please let me know.
QSSTV version 8.2.x released

QSSTV Output messsages

If you start QSSTV 8.X in a terminal window you can see the following messages:
Card 0 name: HDA Intel PCH 
queue opened: id= 0
warning: component data type mismatch
warning: superfluous BPCC box

The first two messages are pure information.
The warning messages are coming from the Jasper library.
They are just warnings, not a bugs. I can't stop them from appearing in the output.


Installation
of Qt 8.1.x on Centos 6.5

Installation has been tested on Qt4.8 and Qt5.1 and
Qt5.2


Centos 6.5 x86_64 on Qt4.6.2

su -c 'yum install gcc-c++ qt-devel fftw-devel jasper-devel'
su -c 'yum install alsa-lib-devel hamlib-devel'

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



Centos 6.5 x86_64 on Qt5.1

su -c 'yum install gcc-c++ qt5-qtbase qt5-qtbase-devel fftw-devel jasper-devel'
su -c 'yum install alsa-lib-devel hamlib-devel'

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



Installation
of Qt 8.1.x on openSuse

Make sure you updated openSUSE to the latest
versions.

With Yast, add a new repository.:

download.opensuse.org/repositories/hamradio/openSUSE_xx.x/

(replace xx.x with the appropriate version).



Then with "Yast install software" select the following packages

libqt4-devel

fftw3-devel

libjasper-devel

hamlib-devel

alsa-devel



Download the latest version of qsstv_8.1.x and proceed as in the installation section of the
manual.



Installation
of Qt 8.1.x on Fedora


Tested on Fedora 14 and Fedora 20.
su -c 'yum install gcc-c++ qt-devel fftw-devel jasper-devel'
su -c 'yum install alsa-lib-devel hamlib-devel'



Download the latest version of qsstv_8.1.x and proceed as in the installation section of the
manual but use qmake-qt4 instead of qmake.



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 



Credits


A lot of people have helped me developing
this program. I will try not to forget anyone.

Pre-alpha:


ON4CDY, ON4AWV, ON7VQ, ON4CDQ, ON4VT, ON1DNF, PA3CGX,  PA0EHA,
KA2HZO


Early adopters and testers for QSSTV 7.1

DC0EV,2E0LGL, DO5MKN, KI6ZHD,N2FYE, VE9MB, EA4TV, ON4BAG, ON6RR,KD5MKV


QSSTV 8.1

PA0MBO (Ties) for giving me a big jump start with HAMDRM and VK4AES
(Erik) for his program Easypal I used extensively during testing.
BSR and Hybrid mode have been made compatible with Easypal. (all
credits to Erik).
And some early testers of QSSTV 8.x.x
David (KI6ZHD), Guido (ON4BAG), Franco (IW2DHW), Richard (KF5OIM)
Gilles (VE2GQF) , Murry (VE9MB), Claude (F5BAI), Al (W2ADS) and a lot more ...
Thanks also for the many suggestions to add some features to QSSTV.