Re: Can you prevent mode switching?

2021-10-28 Thread Thomas Beierlein
Am Thu, 28 Oct 2021 05:03:06 -0500
schrieb Nate Bargmann :

> * On 2021 28 Oct 01:01 -0500, Thomas Beierlein wrote:
> > - Add a new keyword as suggested above.
> > - On bandswitch record not only the old frequency but also the
> > mode. So TLF may start with turning the rig to CW on first start
> > but remember later any changes made directly at the trx.  
> 
> I would ask that even this setting not be performed when the new
> keyword is present.  With the keyword present, Tlf should be
> "passive", only changing its logging mode but not sending any mode
> change to the radio.
> 
> 73, Nate
> 

From my point of view it makes no sense to have both. Either have a
keyword or remember the last mode.

We can put it on the ToDO list.

73, de Tom

-- 
"Do what is needful!"
Ursula LeGuin: Earthsea
--




Re: Can you prevent mode switching?

2021-10-28 Thread Nate Bargmann
* On 2021 28 Oct 01:01 -0500, Thomas Beierlein wrote:
> - Add a new keyword as suggested above.
> - On bandswitch record not only the old frequency but also the mode. So
>   TLF may start with turning the rig to CW on first start but remember
>   later any changes made directly at the trx.

I would ask that even this setting not be performed when the new
keyword is present.  With the keyword present, Tlf should be "passive",
only changing its logging mode but not sending any mode change to the
radio.

73, Nate

-- 
"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819



signature.asc
Description: PGP signature


Re: Can you prevent mode switching?

2021-10-28 Thread Thomas Beierlein
Am Thu, 28 Oct 2021 10:22:13 +0800
schrieb Onno VK6FLAB :

> The mode change is still being populated on band change, even if I
> comment out the band-change rig_set_mode call at the bottom of
> src/gettxinfo.c.
> 
The change mode happens actually in handle_trx_bandswitch in gettxinfo.c
It is called in the same file around line 205. Just comment the call
out. That should help.

> I suspect that the mode change is secretly being sent with the
> frequency change and have been trying to investigate filtering out
> mode changes in the TCP connection to rigctld, but that's a two-way
> stream and using grep/sed on a bidirectional stream is a challenge :-)
> 
No. The frequency change is sent separately. But in the next frequency
reading cycle TLF sees the change in band (bandinx != oldbandinx) and
triggers the mode switch.


In the long term I see two ways to handle it:

- Add a new keyword as suggested above.
- On bandswitch record not only the old frequency but also the mode. So
  TLF may start with turning the rig to CW on first start but remember
  later any changes made directly at the trx.

73, de Tom

> I agree that it needs a config option. I think it should be called
> something like IGNORE_RADIO_MODE to make it explicit.
> 
> o
> 
> On Thu, 28 Oct 2021 at 10:00, Nate Bargmann  wrote:
> 
> > * On 2021 27 Oct 18:23 -0500, Onno VK6FLAB wrote:  
> > > I've just removed (commented out) all rig_set_mode calls in  
> > src/gettxinfo.c  
> > > and the behaviour persists. Not sure where else to look.  
> >
> > Hi Onno,
> >
> > Follow the logic from the parsing of logcfg.dat with the SSBMODE and
> > RTTYMODE keywords.  That should lead you to where the mode is set on
> > startup, at least.
> >  
> > > I agree with Nate, TLF should follow the mode, not set it unless
> > > specifically instructed to do so.  
> >
> > I'm sure some prefer the current behavior (working a single mode
> > event, I can see this preference and would likely use it).  I'd
> > like to see a similar keyword, perhaps RIGMODE is to close to the
> > existing RIGMODEL keyword, maybe FOLLOW_MODE would work, that could
> > be added for Tlf following the radio mode until instructed to
> > change mode.
> >
> > 73, Nate
> >
> > --
> > "The optimist proclaims that we live in the best of all
> > possible worlds.  The pessimist fears this is true."
> > Web: https://www.n0nb.us
> > Projects: https://github.com/N0NB
> > GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819
> >
> >  
> 



-- 
"Do what is needful!"
Ursula LeGuin: Earthsea
--




Re: Can you prevent mode switching?

2021-10-27 Thread Onno VK6FLAB
The mode change is still being populated on band change, even if I comment
out the band-change rig_set_mode call at the bottom of src/gettxinfo.c.

I suspect that the mode change is secretly being sent with the frequency
change and have been trying to investigate filtering out mode changes in
the TCP connection to rigctld, but that's a two-way stream and using
grep/sed on a bidirectional stream is a challenge :-)

I agree that it needs a config option. I think it should be called
something like IGNORE_RADIO_MODE to make it explicit.

o

On Thu, 28 Oct 2021 at 10:00, Nate Bargmann  wrote:

> * On 2021 27 Oct 18:23 -0500, Onno VK6FLAB wrote:
> > I've just removed (commented out) all rig_set_mode calls in
> src/gettxinfo.c
> > and the behaviour persists. Not sure where else to look.
>
> Hi Onno,
>
> Follow the logic from the parsing of logcfg.dat with the SSBMODE and
> RTTYMODE keywords.  That should lead you to where the mode is set on
> startup, at least.
>
> > I agree with Nate, TLF should follow the mode, not set it unless
> > specifically instructed to do so.
>
> I'm sure some prefer the current behavior (working a single mode event,
> I can see this preference and would likely use it).  I'd like to see a
> similar keyword, perhaps RIGMODE is to close to the existing RIGMODEL
> keyword, maybe FOLLOW_MODE would work, that could be added for Tlf
> following the radio mode until instructed to change mode.
>
> 73, Nate
>
> --
> "The optimist proclaims that we live in the best of all
> possible worlds.  The pessimist fears this is true."
> Web: https://www.n0nb.us
> Projects: https://github.com/N0NB
> GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819
>
>

-- 
73, de Onno VK6FLAB

Listen to the Foundations of Amateur Radio Podcast
 or check out the eBooks
.


Re: Can you prevent mode switching?

2021-10-27 Thread Nate Bargmann
* On 2021 27 Oct 18:23 -0500, Onno VK6FLAB wrote:
> I've just removed (commented out) all rig_set_mode calls in src/gettxinfo.c
> and the behaviour persists. Not sure where else to look.

Hi Onno,

Follow the logic from the parsing of logcfg.dat with the SSBMODE and
RTTYMODE keywords.  That should lead you to where the mode is set on
startup, at least.

> I agree with Nate, TLF should follow the mode, not set it unless
> specifically instructed to do so.

I'm sure some prefer the current behavior (working a single mode event,
I can see this preference and would likely use it).  I'd like to see a
similar keyword, perhaps RIGMODE is to close to the existing RIGMODEL
keyword, maybe FOLLOW_MODE would work, that could be added for Tlf
following the radio mode until instructed to change mode.

73, Nate

-- 
"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819



signature.asc
Description: PGP signature


Re: Can you prevent mode switching?

2021-10-27 Thread Onno VK6FLAB
I've just removed (commented out) all rig_set_mode calls in src/gettxinfo.c
and the behaviour persists. Not sure where else to look.

I agree with Nate, TLF should follow the mode, not set it unless
specifically instructed to do so.

On Thu, 28 Oct 2021 at 02:25, Nate Bargmann  wrote:

> IMO, Tlf should follow the rig mode and NOT set it unless the operator
> specifically issues a mode change command in the call field.
>
> I've intended to look into it but haven't made it that far.
>
> 73, Nate
>
> --
> "The optimist proclaims that we live in the best of all
> possible worlds.  The pessimist fears this is true."
> Web: https://www.n0nb.us
> Projects: https://github.com/N0NB
> GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819
>
>

-- 
73, de Onno VK6FLAB

Listen to the Foundations of Amateur Radio Podcast
 or check out the eBooks
.


Re: Can you prevent mode switching?

2021-10-27 Thread Nate Bargmann
IMO, Tlf should follow the rig mode and NOT set it unless the operator
specifically issues a mode change command in the call field.

I've intended to look into it but haven't made it that far.

73, Nate

-- 
"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819



signature.asc
Description: PGP signature


Re: Can you prevent mode switching?

2021-10-27 Thread Thomas Beierlein
Am Wed, 27 Oct 2021 09:54:38 +0800
schrieb Onno VK6FLAB :

> When I change bands, TLF automatically changes the mode (CW/LSB/USB),
> even if I don't want it to do that. Can I decouple the TLF mode from
> the radio mode without losing rig control?
> 
> Specifically I want to leave TLF in CW mode, but have the radio in SSB
> (LSB/USB per band as appropriate).
> 
> 

Hi Onno,

If I remember correctly these question came out some years ago. I do
not remember the solution - (if there was one at all). I have to look up
the code for details.

73, de Tom DL1JBE


-- 
"Do what is needful!"
Ursula LeGuin: Earthsea
--