LinPsk -	a PSK31 Program for Linux

1. Introduction

LinPsk is a PSK program for Linux. It is based on the sources of WinPsk 1.0
by Moe Wheatly, AE4JY.
I took the algorithm and ported it to Linux and rewrote the GUI using the
Qt 2.2 library.

The development was started with KDevelop 1.0 and continued with KDevelop 1.2

KDevelop was a great help for me developing LinPsk. Thanks to the
guys of the KDevelop team , they are doing a great job.

This is my first project in C++ and even the first time that I set up an GUI.

So , if you find there is something to improve in programing, give me a hint.

As I'm rare on time I can only give a brief introduction in using the
program.

You will find an excellent documentation of WinPSk at

http://aintel.bi.ehu.es/psk31.html.

2. System requirements

LinPsk works on a Pentium with 133 MHz and 32 Mb Ram. Perhaps it still
works on a Pentium 90 , but I haven't had the chance to try.

Automake and autoconf have to be installed and Qt 2.2 is needed.

A soundcard and the related Opensound Driver must be installed. But if you
only want to have a look at the demo mode , no soundcard is needed.

LinPsk uses /dev/audio for contacting the soundcard. This special file
normally exists, otherwise you have to make a link.

LinPSk uses MicIn of the soundcard as input and LinOut as nutput. LinPsk is
able to switch the RTS - pin of a Com port to switch the transceiver between
receiving and transmitting.

3. Installation

Unpack the file. Run

./configure

If you get messages like qt - header files not found or some other messages on qt try

./configure --with-qt-dir=<QTDIR>

then run

make

Then there should exist the file linpsk.

If you would like to run

make install

be shure to have the  right for writing to the installation directory -
/usr/local/bin
or change  $bindir in  Makefile.

4. Configuring LinPsk

LinPsk supports two modes:

- Demomode

- normal mode.

On the first start Linpsk is in demomode.

You can run the demomode without soundcard installed.

4.1 Demomode

The distribution should include two files:

psk31.out and qpsk.out.

These files contain demosample computed with the software made by w5xd.

The wanted file has to be loaded using the file menu opening demofile.

Having clicked the RX - button  you should read

Hello World
in the RX- window , if you selected the bpsk.out file and

cq cq cq de DL1KSV , if you selected the qpsk.out file.

At the same time the RX on the button changes to TX.

You can try the impacts of the different buttons in the demo mode.

Clicking now the TX - button you simulates sending. But even if you have
installed a soundcard no output signal would be generated.

4.2 Going on the air

If you are familiar with the handling you can go on the air.

Select the settings Menu and there  choose settings.

Deactivate the demomode by clicking.

Now you can start.

Important:

Set the MicInputlevel appropriate.

Select the input display. If the plot changes to red  then the level is too
high.
You can control the level using a common mixer program or the MicInput Level
field in the setting menu.

More important:

Adjust the output level properly.
You should set the outputlevel as low as the ALC of your transmitter doesn't
respond .

Setting output level too high will result in a broadband signal with much
splatter instead of narrow band signal!!!!!!!!!!!.

4.2.1 Settings Menu /settings

The Button DemoMode activates/ deactivates the Demomode.

In the Callsign Window you enter your callsign.

In the station file you enter the name of file you can transmit pressing
the button " Send Station File".
The file is supposed to be in your home directory, but you may enter an
absolute path with the file, too.

In the  Time offset window you enter the offset from your pc - clock to utc.
This value is used to display the correct time in the status line.

In the window "user defined button" you enter the name the last button down right
should be labeled with.

Pressing this button you can send another file.

In the window "corresponding file" you enter the name of the file to be send if the
user defined button is pressed.

With the input- and outputlevel controls you can change the level for in- and output.
You can use a mixerprogram instead.

Please be careful in selecting the outputlevel!!

With the button "slashed zero" you can select whether the 0 is displayed with a slash
to distinguish the number from the letter. This has only effect on the rx- windows,
the transmitted character will always be the number 0.

In the window "number of Rx windows" you select the number of simultaneously
decoded rx- channels.


There is a small bug: If you 've changed this number the window to select an rx- windows
is not displayed properly. You have to resize LinPsk as a whole.

The  PTT- control should be self explanatory.

The DTR and RTS pins are driven.

4.2.2 Settings Menu/Font settings

Here you find a menu to select the fonts for Rx- windows and the tx- window.
You can select the fonst for the four rx windows and the tx window independently.

4.2.3 Settings Menu / Colour Settings

Here you select the colour for the four rx windows.


4.2.4 Settings Menu / Edit Macros

Defining Macros see 4.3.

But the are some special rules using the macro - buttons:

QSO Start will only be executed if you are in rx - mode ( Receiving is to be displayed in
the statusline) and if in the remote call window a callsign was entered either by
typing it directly or be double clicking in front of a callsign in the rx window.

QSO BTU will only work if you 're in tx -mode (Transmitting is o be displayed in the
statusline) and a remote callsign was entered.

QSO final will be executed both in rx or tx mode if a text was entered for this macro.

At the end of this macro LinPsk will switch to rx- mode.


CQ will be executed if you entered your callsign in the setup box.

The "Send Station File" button and the user defined button are executed in tx mode only.





4.3 Macros

To simplify qso'ing you can define macros.

Select Settings menu , edit Macros.

Here you can define or change Macros.

Beside plain text you can use three variables in the text. Using the macro
will result in replacing the variables by their actual values.

The variables are:

@CALLSIGN@ 						the callsign as defined in the setup.

@THEIRCALL@						the content of the Their CAll box. You can change its
											content by edititing the box by hand or by double clicking in front
											of a callsign in the receive window.

@NAME@								the name of the remote op as defined in the Name field																						
											
@CWID@								will be replaced by "de @CALLSIGN@ kn" and be send in cw.				

Clicking the "send Station File" button you can send a textfile , for instance
including your station data. You edit this file with a texteditor of your
choice.
You configure the name of the file to send in the settings menu, too.

If the file is situated in your home directory, the name of the file suffices,
otherwise you have to specify the whole path and filename.

At last you can define the name of the last button as you wish and the
textfile to be sent if you press this button. Both happen in the settings
menu.	This textfile is to be edited by a texteditor.

4.4 Triggers

LinPsk supports up to 4 Rx- windows (configurable).
For each Rx- window you can define a trigger text and activate the trigger. (default: CQ CQ
trigger not activated)

If the trigger -text is detected you hear a beep and LinPsk switches to the Rx  - window
where the text was detected and the trigger will be deactivated.

In this way you can observe the different windows. The trigger text can be changed . 'Enter'
finishes the input.
The tiggertext is case insensitive.


73 es good DX de DL1KSV .

Please give me a hint if you have problems.

My eMail adress is DL1KSV@gmx.de

But remember it's a hobby, so don't be impatient if I can't respond
immediately.						

==============================================================================
==============================================================================