From: Kristoff Bonne <kristoff.bonne@compaqnet.be>
To: linux-hams@vger.kernel.org
Subject: navtex (amtor-fec/sitor-b)
Date: Wed, 19 Apr 2006 10:05:44 +0200 [thread overview]
Message-ID: <4445EF58.3040608@compaqnet.be> (raw)
[-- Attachment #1: Type: text/plain, Size: 1815 bytes --]
Gegroet,
I don't know if this the correct mailing-list for this, but I have been
trying to decode the broadcasts from the local navtex-station here in
Ostend.
(navtex is a maritime service broadcasting safety-related information on
490 or 518 Khz, 100 baud/170 Hz FSK; see
http://home.cogeco.ca/~dxinfo/navtex.htm)
I seems to have two options:
-> "hfterm", which *sometimes* works with quite a lot of errors in it
and has a lot of problems syncronising to the datastream.
(althou the radio-signal is very good))
Note that I have the same problems using the native soundcard of my
laptop (compaq evo N610c) and using a Griffin iMic (which I use on my mac).
I also have very bad performance when using hfterm on rtty (like the
service from the Deutsche Wetterdienst at 147.3 Khz); so it might be
related to my system or to hfterm itself.
Does anybody have any hints on getting "hfterm" to work correctly? (my
receiver -a sony 7600- only goes as log as 150 Khz, so I cannot use the
"DCF77"-syncronisation test).
-> A second option is to hack the sitor-B/amtor-fec protocol into
another program.
My choice would be gmfsk as it already has a very good GUI
(waterfall-display, AFC); and it works very good for other protocols
(like RTTY). This means it already has the code for FSK-demodulation in it.
It would be nice if there would a way to "hook" code for other protocols
after the demodulation-process (be it FSK, MF, xPSK, ...) and use gmfsk
as "frontend" and write additional protocols or applications on top of
it. (in fact, designing a kind of general "toolkit" of code for
digital-mode programs).
Does anybody know if there is a specialised mailing-list on gmfsk or on
coding digital-mode related ham-programs?
Or is this mailing-list also usable for this?
Cheerio! Kr. Bonne.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3277 bytes --]
reply other threads:[~2006-04-19 8:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4445EF58.3040608@compaqnet.be \
--to=kristoff.bonne@compaqnet.be \
--cc=linux-hams@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).