Can these features be individually turned on and off?
Some of them seem like a good idea in general, and some
do not.

It's true that mechanical RTTY setups send constant mark
tone when there is nothing to send - but there are technical
and operational reasons to send diddles. They do annoy the
mechanical TTY users; but one can argue that the solution
to that is to make an electronic box that will keep them from
reaching the machine. The advantages of diddles are (1) you
know it's a RTTY signal, not just some carrier sitting there,
(2) modern demodulators take advantage of having both mark and
space tones preset pretty often, to judge the levels of them.

I'm also unsure of the virtue of the MFSK mode sending one
flop and then settling on one tone. Again there is the problem
that it just sounds like some random carrier, so the guy
tuning around doesn't recognize the signal for what it is.

Apply to a clean extract of gmfsk-hkj50.

Here's what this one does:

DominoEX: adds squelch and secondary text. This is the result of a few experimental diffs flung between myself, W1HKJ and VK3SB a month ago.

MFSK16: On idle, sends one null pattern then settles on the bottom tone.

RTTY: On idle, just sends a constant mark tone. Apparently, this is common behavior for mechanical setups.

FM Hell: On idle, carrier power is reduced by 6 dB, and dots are no longer sent.

-Joe, KD8ATU

Hamish Moffatt wrote:

On Sun, Jul 09, 2006 at 07:12:42AM -0400, Ed wrote:

I was hoping that someone here could help with some details on the 746, since I have never seen or operated one. I looked thru hamlib.org and Ekki's site but didn't really see anything. Google wasn't much better. Evidently he is trying to key the rig thru the CI-V cable rather than a stand alone serial port. I'll suggest that he consider the stand alone. Thanks...73

Ed: well, two things are necessary - hamlib must support PTT on the
IC-746, and gMFSK needs to support PTT via hamlib, not just
serial/parallel. I don't know about the former, but it isn't obvious
from the configuration screens that gMFSK supports the latter anyway.
Another alternative is VOX, if the 746 has it.
Hamish

Evidently hamlib does not support ptt via the ci-v, I found 1 reference to trying to use the parallel port for ptt with gMFSK with the 746. This would be a viable solution, but he is a newbie and followed my suggestion to use vox for now. He has 2 serial ports, ci-v on one and a ups on the other. thanks for your time and help....73

Ed W3NR

开云体育

Ed wrote:

Dave-Hamish

I was hoping that someone here could help with some details on the
746, since I have never seen or operated one. I looked thru hamlib.org
and Ekki's site but didn't really see anything. Google wasn't much
better. Evidently he is trying to key the rig thru the CI-V cable rather
than a stand alone serial port. I'll suggest that he consider the stand
alone. Thanks...73

Ed W3NR

Ed,
You might also want to try the Icom728 program that is on my web site, .? I think that the 746 and 728 share the same i/o code structure.? Check the Icom subdirectory in hamlib and the code for the two rigs should give you a clue.? I will check that later today.? If you want to try the Icom728 code run it first as a stand-alone application to control the rig (freq/mode etc).? It that works ok than recompile the gmfsk-hkj application with the switches set

#define WANT_TENTEC_MOD 1

you might also need:

#define WANT_PTT_MOD 1

if his interface steals power from the RS232 port.

Oh yes.? You must disable the hamlib interface for this compile.? You can only have one i/o selection at the present time, either hamlib or the TENTEC type which is a memory map share between gmfsk and the Icom728 program (and others like it).

So run ./hkjconfigure (without the --want-hamlib directive), before recompiling.

Dave, W1HKJ

On Sun, Jul 09, 2006 at 07:12:42AM -0400, Ed wrote:

I was hoping that someone here could help with some details on the
746, since I have never seen or operated one. I looked thru hamlib.org
and Ekki's site but didn't really see anything. Google wasn't much
better. Evidently he is trying to key the rig thru the CI-V cable rather
than a stand alone serial port. I'll suggest that he consider the stand
alone. Thanks...73

Ed: well, two things are necessary - hamlib must support PTT on the
IC-746, and gMFSK needs to support PTT via hamlib, not just
serial/parallel. I don't know about the former, but it isn't obvious
from the configuration screens that gMFSK supports the latter anyway.

Another alternative is VOX, if the 746 has it.

Hamish
--
Hamish Moffatt VK3SB <hamish@...> <hamish@...>

Dave-Hamish

I was hoping that someone here could help with some details on the 746, since I have never seen or operated one. I looked thru hamlib.org and Ekki's site but didn't really see anything. Google wasn't much better. Evidently he is trying to key the rig thru the CI-V cable rather than a stand alone serial port. I'll suggest that he consider the stand alone. Thanks...73

Ed W3NR

On Sat, Jul 08, 2006 at 05:36:18PM -0000, Jerry W wrote:

If he is using one of the Debian based distro's like MEPIS, Knoppix,
Unbuntu, Kubuntu, Xbuntuntu etc. Using the Synaptic Package Manager
there are some programs for Icom, supposed to be for CI-V control. I
am not sure if they work with gMFSK however. There is a ham radio
users group on Debian email lists. If you highlight the Icom program
in Synaptic, below the in the description window it gives some
information about the Debian ham users.

There is a standalone icom program, but hamlib provides rig-control
functions to be used in applications. gMFSK has that capability and IS
built with it enabled (at least as packaged by Debian).

The OP could use PTT by direct keying from a serial port, rather than
doing it over CI-V (if that is even supported). Sure to work then.

Hamish
--
Hamish Moffatt VK3SB <hamish@...> <hamish@...>

开云体育

Ed wrote:

I'm trying to help someone with an IC746 get PTT to work in gMFSK. He is
using the CI-V17 converter. Anyone here that can help, so I can pass the
information on. TIA

Ed W3NR

He has a working hamlib, just no PTT

Ed,? Please provide a little more info on the CI-V17 converter.? Does it steal power from the Rs-232 port?

How have you set up the hkj-config.h file?? Your problem may be there.

Dave

Ed,

If he is using one of the Debian based distro's like MEPIS, Knoppix,
Unbuntu, Kubuntu, Xbuntuntu etc. Using the Synaptic Package Manager
there are some programs for Icom, supposed to be for CI-V control. I
am not sure if they work with gMFSK however. There is a ham radio
users group on Debian email lists. If you highlight the Icom program
in Synaptic, below the in the description window it gives some
information about the Debian ham users.

I am a Kenwood user, so can't be of much more help.

HTH,

Jerry - K0HZI

I'm trying to help someone with an IC746 get PTT to work in gMFSK. He is using the CI-V17 converter. Anyone here that can help, so I can pass the information on. TIA

Ed W3NR

He has a working hamlib, just no PTT

Dave,

Thanks for the info. I "Googled" tgz. Most of the stuff was about
how it worked etc and never explained how to uncompress as simple as
you have.

Thanks,

Jerry - K0HZI

This is an extract of the file README-hkj.txt contained in the directory "gmfsk-hkj.50"

/**
/ README-hkj.txt
/
**/

The source files for gmfsk.hkj are compatible with gmfsk-0.71pre1.

Revision gmfsk.hkj.50


The configuration, compilation and installation are the same as for gmfsk.

Please run the configuration using the hkjconfigure script. The automake needs to be fixed to properly generate the references to the dependency files for dominoex. In the meantime the hkjconfigure script will properly create the necessary files for proper compilation. Just "cat hkjconfigure" to see what it is doing. You can pass the same parameters to this script that you would pass to configure, ie: --enable-hamlib.

After running the ./configure file be sure that you have the hamlib directives
properly set. Then edit the source header file src/hkj-config.h. You set up which modifications to the original source you want to include by setting the define statements in the header file.

The interface and callback source files have been edited separately from the
gtk interface design tool, "glade2". If you open the gmfsk.glade file and
create a new set of source files you will destroy the changes included in this
set of modifications. If you do this you will have to restore those files from
the tarball.

Revision .50 adds the following new operating modes to gmfsk:

FM-Hell and FM-Hell 105
DominoEX 4, 5, 8, 11, 16 and 22
Modified Olivia
Bug fix for qpsk coming up in the reverse mode on USB
The changes to the Olivia modem allow you to select the operating center audio frequency for that mode, negating the 500 Hz lock on the lowest Olivia tone.

The gmfsk user community is deeply indebted to Joe Veldhuis, KD5ATU, and Hamish Moffatt, VK3SB, for their respective contributions to the Hell-Olivia and DominoEX modems.

So ... you need to execute

./hkjconfigure

instead of

./configure

to create the dominoex subdirectory ".PO" and its associated files.

Dave, W1HKJ

开云体育

Jerry W wrote:

tTrying to uncompress

Have done plain tar.gz with the Terminal, but can not figure out how
to uncompress tgz?

Linux newbie

TIA,

Jerry - K0HZI

xxxx.tar.gz or xxxx.tgz are both used as descriptive suffixes for the same type of file, a gzipped archive (tar) file.

so you could do the following from the command line:

tar xzf xxxx.tgz

Dave, W1HKJ

Used Extract from Konqueror to get gmfsk.hjk.50 files and then did
configure using the Terminal.

Now after make I get these errors;
Making all in dominoex
make[3]: Entering directory
`/home/jerry/download/gmfsk.hkj.50/src/dominoex'
Makefile:243: .deps/dominoex.Po: No such file or directory
Makefile:244: .deps/dominoexrx.Po: No such file or directory
Makefile:245: .deps/dominoextx.Po: No such file or directory
Makefile:246: .deps/varicode.Po: No such file or directory
make[3]: *** No rule to make target `.deps/varicode.Po'. Stop.

Do I need to install gmfsk 7.0 pre1 first?

TIA,

Jerry - K0HZI

tTrying to uncompress

Have done plain tar.gz with the Terminal, but can not figure out how
to uncompress tgz?

Linux newbie

TIA,

Jerry - K0HZI

I'm trying to setup serial numbers for the upcoming DominoEX contest. But I'm not having much luck. Earlier this year Dave walked me through getting a 3 digit serial number with more than 1 output to gMFSK. Well I dug back through the archives, tried what he suggested, but I can only get a 4 digit number 1 time. I get the same results from the terminal also. Whatever the cure/fix was, Dave must have sent it via a personal email. What I need is something like this:

"ur 599 001 001 001 "

TIA
Ed W3NR

Dave,

I use the CW offset set to 500 at all times, so I guess I wouldn't see
what you commented about. I have compared both the CAT and 505.exe Freq
Cal's and find them identical to the ear. I have nothing set up to
actually measure the Delta Fo.

Tom (frg)

Aubrey,

You need to also thank Jim Haynes, W6JVE, who has kindly placed his
second transceiver at my mercy during the development process. He
even had to repair it after I blew out the RS232 port. Fortunately
that was a singular event and Jim has excellent technical skills. He
also had faith in my ability to continue the work and returned the
transceiver to me after he repaired the damaged port. The user
interface really represents my personal preference for operating. I
hope that it proves useful and serviceable to the Kachina owners who
chose to use it. The original goal was to allow a Linux user to have
access to the transceiver from that OS. It quickly became apparent
that the Windows community might also be well served by the new user
interface.

Dave (hkj)

At 12:29 PM 6/11/2006, you wrote:

I've just checked the KC505.EXE reference frequency performance
against the KachinaCAT running on Windows XP and then on Linux. The
KachinaCAT program gives identical results. I did find that the
transceiver was able to make the internal adjustments better if the CW
offset was set to 500 Hz. I recommend setting the CW offset to 500
just before calibration and then returning it to your normal CW ops
after the calibration.

I would appreciate some feedback on your observation of the effect of
the CW offseet on the calibration function.

The next revision of KachinaCAT will include changing the offset to
500 and then returning it to your default at the conclusion of the
calibration run.

Dave, (hkj)

Dave,
You continue to amaze me. We in the Kachina family are very blessed with your
continued efforts and accomplishments on our behalf.
Kudos and Thanks.
73 de Aubrey.W6ODG
San Marcos, CA

I've just checked the KC505.EXE reference frequency performance
against the KachinaCAT running on Windows XP and then on Linux. The
KachinaCAT program gives identical results. I did find that the
transceiver was able to make the internal adjustments better if the CW
offset was set to 500 Hz. I recommend setting the CW offset to 500
just before calibration and then returning it to your normal CW ops
after the calibration.

I would appreciate some feedback on your observation of the effect of
the CW offseet on the calibration function.

The next revision of KachinaCAT will include changing the offset to
500 and then returning it to your default at the conclusion of the
calibration run.

Dave, (hkj)