| |
FRB001 > INFO 27.02.17 08:40l 161 Lines 5993 Bytes #999 (0) @ WW
BID : 8070_FRB001
Read: GUEST
Subj: MULTIPSK (4.31.4)
Path: FU0BOX<CB0ESN<FRB024<FRB001
Sent: 170227/0737Z 8070@FRB001.#24.FAQI.FRA.EU.WW BPQ6.0.13
*New release of MULTIPSK (4.31.4)*
**
/Pour les francophones: la version en franηais de ce message se trouve
sur mon site (http://f6cte.free.fr). Il suffit de cliquer sur le lien
"_Principales modifications (courriel avertissant de la sortie de la
nouvelle version)_"./
*
*Hello to all Ham and SWL,
The new release of *MultiPSK (4.31.4) *is on my Web site
(http://f6cte.free.fr).
The mirror site is Earl's, N8KBR:
http://www.eqth.info/f6cte/MULTIPSK_setup.exe
The MD5 signature of the downloaded MULTIPSK_setup.exe file to,
possibly, check (with WinMD5 for example), that the downloading works
without error, is equal to: 6ce0ddb50472209992757f0ad3e6cba5
Multipsk associated to Clock are freeware programs but with functions
submitted to a licence (by user key).
*The main improvement of Multipsk 4.31.4 is an addition of a SDR TCP/IP
interface.*
**
*_Main goal
_*
This new version proposes a SDR TCP/IP interface able to interface SdR
receivers, as the direct or EXTIO interfaces. It is simple and can be
used for an exchange between:
* a client program (Multipsk, for example),
* a SdR (local or remote) able to transmit IQ 16 bits samples, at a
sampling rate of
48000 Hz.
For developers, it is proposed programs permitting a complete simulation
of a server and a client (see below).
This version of Multipsk managed a basic application, i.e. the mandatory
part of the version 0 of the protocol:
* the default sampling frequency (48000 Hz),
* the default hardware type managed: 3 (16 bits, IQ),
* the mandatory procedures (Pversion, HWMPcapa, InitHWMP, Set_HWLO,
Received, Bug_on_P).
The hardware type 4 (with only a frequency control, data coming from a
specific sound card, as for the Funcube) is also managed by Multipsk.
It will be possible to manage either a SDR server located in the same PC
or a remote SDR server. In other words, it would be possible to decode
transmissions from your receiver located in an other place, if autorized
in your country.
*_Typical working for the user_***
In the standard option, the SDR server file must be in the same
directory as Multipsk. As an example, it is proposed, for a test, a
simulation of server SDR_TCP_IP_TEST.exe. This pseudo-server generates
and sends an IQ signal at 6000 Hz (square wave).
After having started Multipsk, push on the pink *SdR TCP/IP*φ button of
the *I/Q interfaces for SdR transceivers*φ panel. Push on the
*Connection*φ button. Once the connection done, the number after *N=*φ
(number of data) increases. Close this TCP/IP window and push on *RX/TX
screen*φ, as usual. The 6000 Hz signal will be visible in the SdR waterfall.
Extract from the manual:
.
- If the "*SDR TCP/IP*" button is pushed, the SdR interface is forced.
Indeed, Multipsk can be a TCP/IP client and exchange data or commands
with a SDR TCP/IP server local or distant ("*Remote*" button). The
standard is a local server (SDR_TCP_IP_xyz.EXE) in "local loop" using
the standard IP address 127.0.0.1 and located in the Multipsk directory
of your PC. However, it is possible to use a remote server via Internet
(with any IP address or DNS).
Moreover, the "*+Speaker*" may be pushed, to listen to the demodulated
sound.
The "*Transceiver*" window on the "RX/TX" screen permits to control the
frequency of the SDR.
.
Click on the button to reach help.
*_For the SdR manufacturer_***
*Now what is proposed is only a simulation
For the ones having a SdR
receiver (except RTL SDR dongles, directly managed by Muktipsk), if you
want to have your SdR directly interfaced to Multipsk (and, perhaps, to
other programs in the future), you have to forward this message to your
SdR manufacturer. Maybe, he will find interest to develop the necessary
server interface, for the satisfaction of his/her clients. *
*__*
_For the SDR manufacturer_, here are presented the different files
necessary to implement the protocol SDR TCP/IP INTERFACE Version 0.
These files are included in the SDR_TCP_IP_INTERFACE_Version_0.ZIP
package, available at this WEB address:
http://f6cte.free.fr/SDR_TCP_IP_INTERFACE_Version_0.ZIP
· The « SDR_TCP_IP_INTERFACE_V_0.docx » file gives the description
of the protocol.
· The « Client_in_C++ » and « Server_in_C++ » files are very
simple programs only able to establish a TCP/IP communication. These
programs are generated in C++ (C++Builder 6 Borland). They are supposed
built in the
C:\SDR_TCP_IP_INTERFACE directory.
· The « Client_in_Delphi » and « Server_in_Delphi » files are very
simple programs only able to establish a TCP/IP communication. These
programs are generated in Delphi 6 (Borland).
· The « Complete simulation of a SDR TCP-IP client in Delphi » file
can be used as a model for a true SDR TCP/IP client program (called «
CP » in the protocol), as for example a decoding program. It is issued
from Multipsk.
· The « Complete simulation of a SDR TCP-IP server in Delphi » file
can be used as a model for a true SDR TCP/IP server program (called
« MP » in the protocol). It is interfaced with the SDR hardware and the
client program.It has the general equivalent role of the EXTIO file.
These two last programs are generated in Delphi 6 (Borland).
_Questions of the SDR manufacturer_can be asked either to the author
(about the protocol) or, in English, to the Multipsk Yahoo group (about
needs of SDR users or feedback).
__
_Note about TLE files_: if you use the "*Satellites*" option, don't
forget to download
(with the "*Downloading*" button) the 5 recent TLE files (amateur.txt,
argos.txt, orbcomm.txt, stations.txt, weather.txt).
_Note about translation of Multipsk.exe and Clock .exe_: the 4.31.3
version of Multipsk has been completly translated to Spanish by Joachin
(EA4ZB), from French. The translation file is on my Web site
(http://f6cte.free.fr/Translation_files.htm).
73
Patrick
Lese vorherige Mail | Lese naechste Mail
| |
