Features Download
From: Nate Bargmann <n0nb <at> n0nb.us>
Subject: [Fwd: Re: K3 (and K2?) RIT clear in hamlib]
Newsgroups: gmane.linux.hams.hamlib.devel
Date: Friday 27th May 2011 17:59:49 UTC (over 7 years ago)
I will add that Tor's request has merit--a separate API function to
activate/deactivate RIT/XIT rather than automatically do so by setting a
0 Hz value.  The pro side is that setting a 0 Hz value would effectively
clear the RIT/XIT.  The con side is that this constitutes an API change.

Discussion on this is requested.

73, de Nate >>

----- Forwarded message from RT Clay  -----

Date: Fri, 27 May 2011 09:35:56 -0700 (PDT)
From: RT Clay 
To: Nate Bargmann 
Subject: Re: K3 (and K2?) RIT clear in hamlib
X-Mailer: YahooMailClassic/14.0.1 YahooMailWebService/

You can forward this to the hamlib list- I am not subscribed.

The Elecraft manual does not guarantee that all commands work during TX.
But I guess it should not lock up the radio. For most radios in general, I
suspect it is more likely that a RIT clear (just setting offset to zero)
will succeed during transmit, while turning RIT/XIT on/off altogether is
only allowed while the radio is in RX mode. I know in the K3 case that
clearing RIT ("RC" command) works fine while the radio is transmitting.

It seems a little strange that hamlib API will not allow setting the
RIT/XIT offset to zero but leaving RIT/XIT turned on. This is very commonly
done in contest logging programs where you want to zero RIT after each qso,
but leave the choice of RIT/XIT on/off up to the operator. 

If it were me, I would separate the RIT offset setting command and RIT
on/off command. If hamlib doesn't want to separate those in the api at the
moment, then adding a separate command to just clear RIT would be enough
for my app. If a separate clear command (like kenwood "RC") did not exist,
it could just use the same underlying offset-set command.


--- On Fri, 5/27/11, Nate Bargmann  wrote:

> From: Nate Bargmann 
> Subject: Re: K3 (and K2?) RIT clear in hamlib
> To: "RT Clay" 
> Date: Friday, May 27, 2011, 10:51 AM
> * On 2011 27 May 00:25 -0500, RT Clay
> wrote:
> > Nate,
> > 
> > I have run into a problem with the K3 backend in
> hamlib. I haven't checked, but I suspect the same problem
> occurs in the K2 backend.
> > 
> > One feature I use a lot is clearing the RIT. This gets
> placed in a CQ message for example, to clear the RIT to get
> ready for the next caller. In hamlib the only way to clear
> the rit is rig_set_rit. Unfortunately this also turns RIT
> off completely if the offset is zero. I need for it to just
> clear and stay on.
> Hi Tor.
> I'll have to look again, but I believe the default behavior
> for Hamlib
> is to turn off the RIT/XIT when it receives a value of
> 0.  I think
> you'll run into this issue with any Hamlib supported rig,
> not just the
> K3 as this is the defined behavior of the Hamlib API:
> http://hamlib.sourceforge.net/manuals/1.2.13/group__rig.html#ga7eca7917ca3094ed6eec3b3efce1b0a3
> > A side affect of turning RIT off completely is that
> the rig_set_rit command locks up my K3 if it is sent while
> the K3 is in transmit mode.
> That is probably a firmware bug and should be reported to
> Elecraft for
> them to fix.  I can certainly test it against my K3
> with the latest
> stable firmware.
> > On the other hand, just sending "RC" to clear RIT/XIT
> can be done safely while the radio is transmitting. The
> RT0/RT1 commands do not seem to work while the radio is
> transmitting.
> I'm not sure at this moment how we can handle this
> better.  We could
> probably use a custom set extra level command as with
> reading the FI
> data.  This would be custom to the K3 at this point
> and would not be
> shared with any other radio until support is coded for
> them.
> > So I guess I would like to see a way to just clear
> ("RC") RIT without doing anything else. Or the
> offset-setting and on/off functions could be made separate.
> We can do this for radios have the concept clearing RIT
> without shutting
> it off.  Perhaps this is worth discussing on the
> Hamlib list to see if
> we should modify the Hamlib RIT API?
> 73, de Nate >>
> -- 
> "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://www.n0nb.us

----- End forwarded message -----


"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://www.n0nb.us

vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery, 
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now. 
CD: 3ms