Skip to contentSkip to conversation

gMFSK ?

DISCUSSION Erik Jakobsen 3 participants 8 messages Jul 8, 2008 – Jul 9, 2008

lore
Share & tools
lore
#0 lore raw

Hi.

I have installed gMFSK on my openSUSE 11.0.

It works nice, and now I want to set up hamlib.

I have tested the connection to the scanport with rigctl and the command IF:

# rigctl -vvvvv -r /dev/ttyS0 -s 9600 -m 204
rigctl, Hamlib version 1.2.7.1
Report bugs to <[email protected]>

rig:rig_init called
rig: loading backend kenwood
kenwood: _init called
rig_register (213)
rig_register (201)
rig_register (225)
rig_register (203)
rig_register (204)
rig_register (216)
rig_register (224)
rig_register (205)
rig_register (207)
rig_register (209)
rig_register (210)
rig_register (222)
rig_register (214)
rig_register (221)
rig_register (202)
rig_register (211)
rig_register (206)
rig_register (208)
rig_register (215)
rig_register (226)
rig_register (217)
rig_register (220)
rig_register (223)
rig_register (227)
rig_register (228)
rig:rig_open called
TX 3 bytes
0000 49 46 3b IF;
RX 38 characters

0000     49 46 30 30 30 31 34 30 38 30 37 38 30 20 20 20        IF00014080780
0010     20 20 20 30 30 39 30 30 30 20 39 30 30 32 30 30           009000 900200
0020     30 30 30 38 20 3b                                      0008 ;

Opened rig model 204, 'TS-570D'
Backend version: 0.6.1, Status: Stable

Rig command: if
TX 3 bytes
0000 49 46 3b IF;
RX 38 characters

0000     49 46 30 30 30 31 34 30 38 30 37 38 30 20 20 20        IF00014080780
0010     20 20 20 30 30 39 30 30 30 20 39 30 30 32 30 30           009000 900200
0020     30 30 30 38 20 3b                                      0008 ;

TX 4 bytes
0000 46 52 30 3b FR0;
TX 4 bytes
0000 46 54 30 3b FT0;
Tx frequency: 14080780

TX 3 bytes
0000 49 46 3b IF;
RX 38 characters

0000     49 46 30 30 30 31 34 30 38 30 37 38 30 20 20 20        IF00014080780
0010     20 20 20 30 30 39 30 30 30 20 39 30 30 32 30 30           009000 900200
0020     30 30 30 38 20 3b                                      0008 ;

Rig command: Frequency: 14080780

Rig command:

In the gMFSK hamlib setup I have this:

Kenwood TS570D
Port /dev/ttyS0
Speed 9600

What more shal I have in here to get that part to work ?. When I start up gMFSK it complains abot the port settings

Hamlib init: rig_open failed: IO error

What to do here ?

73 de Erik OZ4KK

#1 lore raw
Quoted 52 lines · Erik Jakobsen

Hi.

I have installed gMFSK on my openSUSE 11.0.

It works nice, and now I want to set up hamlib.

I have tested the connection to the scanport with rigctl and the command IF:

# rigctl -vvvvv -r /dev/ttyS0 -s 9600 -m 204
rigctl, Hamlib version 1.2.7.1
Report bugs to <[email protected]>

rig:rig_init called
rig: loading backend kenwood
kenwood: _init called
rig_register (213)
rig_register (201)
rig_register (225)
rig_register (203)
rig_register (204)
rig_register (216)
rig_register (224)
rig_register (205)
rig_register (207)
rig_register (209)
rig_register (210)
rig_register (222)
rig_register (214)
rig_register (221)
rig_register (202)
rig_register (211)
rig_register (206)
rig_register (208)
rig_register (215)
rig_register (226)
rig_register (217)
rig_register (220)
rig_register (223)
rig_register (227)
rig_register (228)
rig:rig_open called
TX 3 bytes
0000 49 46 3b IF;
RX 38 characters
0000 49 46 30 30 30 31 34 30 38 30 37 38 30 20 20 20
IF00014080780
0010 20 20 20 30 30 39 30 30 30 20 39 30 30 32 30 30
009000 900200
0020 30 30 30 38 20 3b 0008 ;
Opened rig model 204, 'TS-570D'
Backend version: 0.6.1, Status: Stable

Quoted 1 line

Rig command: if

This is actually two rigctl commands, i: get_split_freq () and
f: get_freq () and should not be confused with the IF; command
sent to the radio. When you enter a ? at the Rig command: prompt, you will see a list of commands rigctl accepts.

Quoted 26 lines

TX 3 bytes
0000 49 46 3b IF;
RX 38 characters
0000 49 46 30 30 30 31 34 30 38 30 37 38 30 20 20 20
IF00014080780
0010 20 20 20 30 30 39 30 30 30 20 39 30 30 32 30 30
009000 900200
0020 30 30 30 38 20 3b 0008 ;
TX 4 bytes
0000 46 52 30 3b FR0;
TX 4 bytes
0000 46 54 30 3b FT0;
Tx frequency: 14080780

TX 3 bytes
0000 49 46 3b IF;
RX 38 characters
0000 49 46 30 30 30 31 34 30 38 30 37 38 30 20 20 20
IF00014080780
0010 20 20 20 30 30 39 30 30 30 20 39 30 30 32 30 30
009000 900200
0020 30 30 30 38 20 3b 0008 ;
Rig command: Frequency: 14080780

Rig command:

Quoted 7 lines

In the gMFSK hamlib setup I have this:

Kenwood TS570D
Port /dev/ttyS0
Speed 9600

What more shal I have in here to get that part to work ?.

It has been a long time since I used gMFSK that I've forgotten how it is configured.

Quoted 1 line

When I start up gMFSK it complains abot the port settings

You did exit rigctl before starting gMFSK, right?

Quoted 3 lines

Hamlib init: rig_open failed: IO error

What to do here ?

Perhaps you may wish to try Fldigi? It is actively developed and seems to be the successor to gMFSK. See http://www.w1hkj.com

73, de Nate >>

Signature · 4 lines
"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Ham radio, Linux, bikes, and more: http://n0nb.us/index.html
#2 lore raw
Quoted 5 lines · Nate Bargmann

This is actually two rigctl commands, i: get_split_freq () and f: get_freq () and should not be confused with the IF; command
sent to the radio. When you enter a ? at the Rig command: prompt, you will see a list of commands rigctl accepts.

Ok about the ?. I have seen it.

Quoted 28 lines
Quoted 28 lines

TX 3 bytes
0000 49 46 3b IF;
RX 38 characters

0000     49 46 30 30 30 31 34 30 38 30 37 38 30 20 20 20         IF00014080780
0010     20 20 20 30 30 39 30 30 30 20 39 30 30 32 30 30            009000 900200
0020     30 30 30 38 20 3b                                      0008 ;

TX 4 bytes
0000 46 52 30 3b FR0;
TX 4 bytes
0000 46 54 30 3b FT0;
Tx frequency: 14080780

TX 3 bytes
0000 49 46 3b IF;
RX 38 characters

0000     49 46 30 30 30 31 34 30 38 30 37 38 30 20 20 20         IF00014080780
0010     20 20 20 30 30 39 30 30 30 20 39 30 30 32 30 30            009000 900200
0020     30 30 30 38 20 3b                                      0008 ;

Rig command: Frequency: 14080780

Rig command:

In the gMFSK hamlib setup I have this:

Kenwood TS570D
Port /dev/ttyS0
Speed 9600

Quoted 7 lines
Quoted 2 lines

What more shal I have in here to get that part to work ?.

It has been a long time since I used gMFSK that I've forgotten how it is configured.

Ok np.

Quoted 6 lines
Quoted 2 lines

When I start up gMFSK it complains abot the port settings

You did exit rigctl before starting gMFSK, right?

Yes I did.

Quoted 11 lines
Quoted 4 lines

Hamlib init: rig_open failed: IO error

What to do here ?

Perhaps you may wish to try Fldigi? It is actively developed and seems to be the successor to gMFSK. See http://www.w1hkj.com

73, de Nate >>

Maybe I do Nate. I installed it an it's running.
I have downloaded the TS570.xml file and have saved it into the /home/.fldigi folder. I entered the values to match what I prefer:
<PORT>

       <DEVICE>/dev/ttyS0</DEVICE>
       <BAUD>9600</BAUD>
       <STOPBITS>1</STOPBITS>
       <ECHO>false</ECHO>
       <RETRIES>4</RETRIES>
       <TIMEOUT>200</TIMEOUT>
       <WAIT>0</WAIT>
       <DTRINIT>-12</DTRINIT>
       <DTRPTT>false</DTRPTT>
       <RTSINIT>-12</RTSINIT>
       <RTSPTT>false</RTSPTT>
       <RTSCTS>true</RTSCTS>

</PORT>

I f I try to use RigCat, and check the ptt none, as I use a Signalink SL1+, the Rig at the bottom of the fldigi screen is greyed.

Trying to use Hamlib, the Rig opens the RigControl, but I cannot control the tranceivers frequencies.

As mentioned, I can get connected with rigctrl's commands.

What am I missing ?

73 de Erik OZ4KK

#3 lore raw
Quoted 6 lines

Trying to use Hamlib, the Rig opens the RigControl, but I cannot control the tranceivers frequencies.

As mentioned, I can get connected with rigctrl's commands.

What am I missing ?

I found that I was having problems a few years ago with a Kenwood TS-2000 under similar circumstances. rigctl seemed to work OK, but hamlib-equipped applications couldn't read out or control the frequencies or modes.

The problem turned out to be one of command turnaround time. The TS-2000 requires some amount of "quiet time" after the port has been opened, and after it has sent the response to a command, before it's ready to receive / recognize / act on the next command.

When you run rigctl, human reaction time and typing speed limitations provide far more than the required time. When you run hamlib-equipped software, it will often issue commands with little or no delay between, and this tends to overwhelm the rig's microprocessor. The net result is that commands are not recognized properly by the rig, and either elicit no response at all or a "Hunh? Say what?" error of some sort.

My recollection is that there is a usable workaround. The rig definition tables in the hamlib drivers have a "post_write_delay" value which can be set to a suitable number of milliseconds, to slow down the software's issuing of back-to-back commands.

I set the TS-2000 post-write delay to 50 milliseconds, and it made a world of difference.

You may need to download the Hamlib source code, tweak the driver for the rig to include a suitable amount of delay, and rebuild the libraries. If this fixes your problem, please submit a patch to the Hamlib maintainers so that it can be incorporated into the next release.

#4 lore raw
Quoted 24 lines · Dave Platt

I found that I was having problems a few years ago with a Kenwood TS-2000 under similar circumstances. rigctl seemed to work OK, but hamlib-equipped applications couldn't read out or control the frequencies or modes.

The problem turned out to be one of command turnaround time. The TS-2000 requires some amount of "quiet time" after the port has been opened, and after it has sent the response to a command, before it's ready to receive / recognize / act on the next command.

When you run rigctl, human reaction time and typing speed limitations provide far more than the required time. When you run hamlib-equipped software, it will often issue commands with little or no delay between, and this tends to overwhelm the rig's microprocessor. The net result is that commands are not recognized properly by the rig, and either elicit no response at all or a "Hunh? Say what?" error of some sort.

My recollection is that there is a usable workaround. The rig definition tables in the hamlib drivers have a "post_write_delay" value which can be set to a suitable number of milliseconds, to slow down the software's issuing of back-to-back commands.

Quoted 10 lines

I set the TS-2000 post-write delay to 50 milliseconds, and it made a world of difference.

You may need to download the Hamlib source code, tweak the driver for the rig to include a suitable amount of delay, and rebuild the libraries. If this fixes your problem, please submit a patch to the Hamlib maintainers so that it can be incorporated into the next release.

Many tnx Dave for your fast reply :-)

I use openSUSE 11.0 and would uninstall hamlib.
Then there was nothing to do but also let fldigi leave its install.

After I installed hamlib, and the after again I would install the fldigi rpm again. But it would also install the hamlib rpm.

Then I downloaded the fldigi tarball.

But it tells me:

# ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for g++... no
checking for c++... no
checking for gpp... no
checking for aCC... no
checking for CC... no
checking for cxx... no
checking for cc++... no
checking for cl.exe... no
checking for FCC... no
checking for KCC... no
checking for RCC... no
checking for xlC_r... no
checking for xlC... no
checking for C++ compiler default output file name...
configure: error: C++ compiler cannot create executables
See `config.log' for more details.

What am I to do now

Erik OZ4KK

#5 lore raw

Erik Jakobsen wrote:

Hi again..

I installed fldigi and hamlib again, but used the cat from fldigi:

It tells me there's no .xml file in the directory, and this is not correct:

~/.fldigi> fldigi
No rig.xml file present
erikja@erikja:~/.fldigi> ls -l *.xml
-rw-r--r-- 1 erikja users 3827 2008-07-09 12:27 fldigi_def.xml -rw-r--r-- 1 erikja users 4491 2008-07-09 12:27 TS-570.xml

What say ?

73 Erik OZ4KK

#6 lore raw
Quoted 14 lines · Erik Jakobsen

Erik Jakobsen wrote:

Hi again..

I installed fldigi and hamlib again, but used the cat from fldigi:

It tells me there's no .xml file in the directory, and this is not correct:

~/.fldigi> fldigi
No rig.xml file present
erikja@erikja:~/.fldigi> ls -l *.xml

(quoted diff) +0 -2
-rw-r--r-- 1 erikja users 3827 2008-07-09 12:27 fldigi_def.xml
-rw-r--r-- 1 erikja users 4491 2008-07-09 12:27 TS-570.xml
Quoted 1 line

What say ?

Please go to http://groups.yahoo.com/group/linuxham/ and sign up for that mailing list which is the support list for Fldigi. There are many knowledgable members on that list including the Fldigi developers. They can really help you.

As one of the Hamlib developers, I'm puzzled why you're having a problem. As Dave wrote, it could be an obscure setting. Looking at the CVS source for the ts570.c I see that post_write_delay = 30 by default. Since I work with Yaseu code, I'm not much help here either.

Sometimes these things can be maddening as a lot of pieces must work together perfectly. Don't give up and do just the linuxham group.

HTH,

73, de Nate >>

Signature · 4 lines
"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Ham radio, Linux, bikes, and more: http://n0nb.us/index.html
#7 lore raw
Quoted 11 lines · Nate Bargmann

Please go to http://groups.yahoo.com/group/linuxham/ and sign up for
that mailing list which is the support list for Fldigi. There are many knowledgable members on that list including the Fldigi developers. They can really help you.

As one of the Hamlib developers, I'm puzzled why you're having a problem. As Dave wrote, it could be an obscure setting. Looking at the CVS source for the ts570.c I see that post_write_delay = 30 by default. Since I work with Yaseu code, I'm not much help here either.

Quoted 8 lines

Sometimes these things can be maddening as a lot of pieces must work together perfectly. Don't give up and do just the linuxham group.

HTH,

73, de Nate >>

I'm now a member of the group.

I have been inside the ts570.c too, and have edit the value to 50. But at that time I had not in mind, that I have installed openSUSE11.0. I used 10.3 before, and haven't installed th4e gcc :-(
I will try to compile make make install again.
Tnx Nate

73,
Erik, OZ4KK