gMFSK/hamlib/parport

gMFSK/hamlib/parport

[Mike Markowski]

Hi all,

A couple questions about the excellent gMFSK 0.6beta2:

	Feature request:
	- Are there any patches that allow gMFSK to use
	  a parport for PTT?  If not, I'll be glad to look into
	  possibly re-using the parport code from soundmodem-0.7.

	Bug report (but maybe in hamlib):
	- I'm using an ICOM 706 MkIIg with hamlib on ttyS0 and
	  PTT to "none" in gMFSK just for the sake of seeing how
	  gMFSK uses hamlib.  When I rotate the rig's tuning knob,
	  gMFSK works for a bit nicely updating the spectrum freqs,
	  but then I get a "Protocol error" and hamlib is disabled.
	  I assume the data out of the rig is changing too rapidly
	  for hamlib to capture it?  Or maybe gMFSK is trying to
	  reread the data too frequently?

I haven't played around with either yet just in case others are already
aware and working on it.

Oh, and I finally looked at gMFSK's "Help".  You know how it goes, when
all else fails read the manual...  I like how you included so many
URLs in there Tomi.  But I notice under the Usage section, it talks
about opening images and how to scroll them.  :-)  Reused text from
something else I guess?

	Thanks for any info,
	Mike  AB3AP

Re: gMFSK/hamlib/parport

[Wilbert Knol]

> 	Bug report (but maybe in hamlib):
> 	- I'm using an ICOM 706 MkIIg with hamlib on ttyS0 and
> 	  PTT to "none" in gMFSK just for the sake of seeing how
> 	  gMFSK uses hamlib.  When I rotate the rig's tuning knob,
> 	  gMFSK works for a bit nicely updating the spectrum freqs,
> 	  but then I get a "Protocol error" and hamlib is disabled.

Try turning off what Icom calls "transceive mode" in the rig.

Having this mode on causes the rig to announce frequency data as you
tune around. It causes bus collisions with Hamlib packets, resulting
in a protocol errors.

Wilbert, ZL2BSJ

Re: gMFSK/hamlib/parport

[Stephane Fillod]

On Wed, Feb 18, 2004, Mike Markowski wrote:
> A couple questions about the excellent gMFSK 0.6beta2:
> 
> 	Feature request:
> 	- Are there any patches that allow gMFSK to use
> 	  a parport for PTT?  If not, I'll be glad to look into
> 	  possibly re-using the parport code from soundmodem-0.7.

	FYI, Hamlib can also control PTT through the parport.

> 	Bug report (but maybe in hamlib):
> 	- I'm using an ICOM 706 MkIIg with hamlib on ttyS0 and
> 	  PTT to "none" in gMFSK just for the sake of seeing how
> 	  gMFSK uses hamlib.  When I rotate the rig's tuning knob,
> 	  gMFSK works for a bit nicely updating the spectrum freqs,
> 	  but then I get a "Protocol error" and hamlib is disabled.

	Traces would be interesting in this case.
	Latest Hamlib version 1.2.0 has retry support for the icom
	backend. This is much useful since the CI-V is a half-duplex bus.


Have fun,

Stephane - F8CFE

Re: gMFSK/hamlib/parport

[Tomi Manninen]

On Wed, 2004-02-18 at 17:27, Mike Markowski wrote:

> 	Feature request:
> 	- Are there any patches that allow gMFSK to use
> 	  a parport for PTT?  If not, I'll be glad to look into
> 	  possibly re-using the parport code from soundmodem-0.7.

There is no direct support available. Like Stephane said, hamlib
can control PTT through the parport.

Direct support would be nice and it shouldn't be difficult. The
biggest work would be implementing the config options and GUI
changes for them... :(

> 	Bug report (but maybe in hamlib):
> 	- I'm using an ICOM 706 MkIIg with hamlib on ttyS0 and
> 	  PTT to "none" in gMFSK just for the sake of seeing how
> 	  gMFSK uses hamlib.  When I rotate the rig's tuning knob,
> 	  gMFSK works for a bit nicely updating the spectrum freqs,
> 	  but then I get a "Protocol error" and hamlib is disabled.
> 	  I assume the data out of the rig is changing too rapidly
> 	  for hamlib to capture it?  Or maybe gMFSK is trying to
> 	  reread the data too frequently?

I have had one similar complaint. I think this is really a hamlib
issue but anyway for the next beta I have relaxed the error checking.
The errors are not considered fatal anymore and messages go to the
status bar instead of annoying popups...

> Oh, and I finally looked at gMFSK's "Help".  You know how it goes, when
> all else fails read the manual...  I like how you included so many
> URLs in there Tomi.  But I notice under the Usage section, it talks
> about opening images and how to scroll them.  :-)  Reused text from
> something else I guess?

Most of the contents are bogus ie. left-overs from the Gnome 
documentation project sample documents (which in turn are actually
Eye of Gnome (eog) docs...).

Thanks to Carl VK1KCM the next beta will have a bit more relevant
content.

-- 
Tomi Manninen / OH2BNS / KP20ME04

Re: gMFSK/hamlib/parport

[Mike Markowski]

First, thanks to everyone for the very helpful responses.
I'll try them tonight after work and see how it goes.

On Wed 18-Feb-04 at 1512 EST, Tomi Manninen wrote:
> On Wed, 2004-02-18 at 17:27, Mike Markowski wrote:
> 
> > 	Feature request:
> > 	- Are there any patches that allow gMFSK to use
> > 	  a parport for PTT?  If not, I'll be glad to look into
> > 	  possibly re-using the parport code from soundmodem-0.7.
> 
> There is no direct support available. Like Stephane said, hamlib
> can control PTT through the parport.

As far as I know (which isn't much!), there isn't a hamlib config
file.  It seems that rigctl lets you test hamlib but doesn't let
you create a permanent file with settings.  If that's true, I need to
set the PTT device in gMFSK.

So to specify /dev/parport0 as the PTT device, would I in gMSFK
first set Settings/Preferences/Devices/PTT to /dev/parport0
and then enable PTT in the hamlib menu??  I have a feeling I'm
missing something...

	Thanks again,
	Mike  AB3AP

Re: gMFSK/hamlib/parport

[Tomi Manninen]

On Thu, 2004-02-19 at 18:58, Mike Markowski wrote:

> On Wed 18-Feb-04 at 1512 EST, Tomi Manninen wrote:
> > On Wed, 2004-02-18 at 17:27, Mike Markowski wrote:
> > 
> > > 	Feature request:
> > > 	- Are there any patches that allow gMFSK to use
> > > 	  a parport for PTT?  If not, I'll be glad to look into
> > > 	  possibly re-using the parport code from soundmodem-0.7.
> > 
> > There is no direct support available. Like Stephane said, hamlib
> > can control PTT through the parport.
> 
> As far as I know (which isn't much!), there isn't a hamlib config
> file.  It seems that rigctl lets you test hamlib but doesn't let
> you create a permanent file with settings.  If that's true, I need to
> set the PTT device in gMFSK.

Umm... You're right. There is no support in gMFSK for setting the
required hamlib options for this. I should have engaged my brain 
before posting...

-- 
Tomi Manninen / OH2BNS / KP20ME04

Re: gMFSK/hamlib/parport

[Alex V Flinsch]

On Wed, 2004-02-18 at 10:27, Mike Markowski wrote:
> Hi all,
> 
> A couple questions about the excellent gMFSK 0.6beta2:
> 

Execllent? I consider it to be a step above excellent!

> 
>       Bug report (but maybe in hamlib):
>       - I'm using an ICOM 706 MkIIg with hamlib on ttyS0 and
>         PTT to "none" in gMFSK just for the sake of seeing how
>         gMFSK uses hamlib.  When I rotate the rig's tuning knob,
>         gMFSK works for a bit nicely updating the spectrum freqs,
>         but then I get a "Protocol error" and hamlib is disabled.
>         I assume the data out of the rig is changing too rapidly
>         for hamlib to capture it?  Or maybe gMFSK is trying to
>         reread the data too frequently?
> 

I just tried this on my system (Yaesu FT100,gMFSK-0.6beta2,
hamlib-1.2.0) and this does not occur, if there is a problem, it might
be in the IC-706 implementation in hamlib, what version of hamlib are
you using? 


BTW I have only had one problem with gMFSK, and that has been happening
for quite sometime (I think it started around version 0.5). Sometimes
(that's the killer) the program will lock up when switching modes. Has
anyone else had that problem?




-- 
Alex / AB2RC 
Yaesu FT100 software for Linux http://www.qsl.net/kc2ivl
Why do they call Radio "Wireless", between my shack and antennas
I must have over 1500 feet of wire!