Re: [RoverLog] Digest for roverlog@googlegroups.com - 3 Messages in 1 Topic

[Bill Schwantes]

Tom,

Thanks for the detailed explaination and your willingness to change.
I see your point though. I wasn't thinking about transverter offsets,
accurate frequencies or the needs of the multi op stations with
networked logging and handoff communications. I'll go back to sleep
on this,

73, Bill
W7QQ DM65sb

On Mon, Jan 28, 2013 at 4:23 AM, <rove...@googlegroups.com> wrote:
> Today's Topic Summary
>
> Group: http://groups.google.com/group/roverlog/topics
>
> Digest for rove...@googlegroups.com - 1 Message in 1 Topic [3 Updates]
>
> Digest for rove...@googlegroups.com - 1 Message in 1 Topic
>
> Tom Mayo <tma...@gmail.com> Jan 27 07:05AM -0500
>
> Bill,
>
> When you QSY in RoverLog, it changes the operating frequency and mode of
> the rig to whatever you used last on the given band. Further, it tracks
> the frequency the rig is on and uses this information to compute the RF
> operating frequency even if you use transverters. And it communicates this
> information to all networked peers.
>
> The root reason why RoverLog performs the QSY action instead of relying on
> the radio's buttons is because of the use of transverters. The radio band
> may not indicate the actual on the air band. For example, your IF radio
> may be on 145 MHz and transverters convert this to 903, 1296, 2304 MHz and
> so on.. This is unique for VHF/UHF/Microwave contests and I don't think
> it's an issue for lower bands where the radio does it all.
>
> I did a lot of work that depends on this paradigm to make sure RoverLog
> restores the operating frequency with each band change and can communicate
> the operating frequency to networked operators. In spite of all this work,
> I would be willing to change how RoverLog operates if the overwhelming
> majority of users want it to operate the way you say. I would encourage
> all list subscribers to respond to this e-mail thread and voice their
> opinion.
>
> If I do change it, it's important to me to retain support for transverters.
> If you respond to this favoring the change, please consider providing
> suggestions for how to accommodate the case I mentioned above. This has
> been discussed at length before, but I think the result was that the
> majority either didn't care or agreed to the current implementation.
>
> Tom.
>
>
>
>
>
> "John D'Ausilio" <jdau...@gmail.com> Jan 27 09:57AM -0500
>
> Indeed we've discussed this before :)
>
> I've been running with a hacked version for a couple of years that
> attempts to work both ways (mostly successfully) .. if you change the
> band on the keyboard, the radion correctly changes bands, and if you
> change the radio band Roverlog follows. The problem you mention is not
> an issue for me (K2 has transverter support so displays actual freq
> minus GHz digits, which are unique).
>
> You might consider adding the feature but leaving it disabled, with a
> big warning to those who turn it on ..
>
>
>
>
> Ken <ke...@cs.com> Jan 27 10:19AM -0500
>
> same for the K3 of course...
>
> Ken
>
> I2/KE2N
>
>
>
> -----Original Message-----
> From: John D'Ausilio <jdau...@gmail.com>
> To: roverlog <rove...@googlegroups.com>
> Sent: Sun, Jan 27, 2013 3:57 pm
> Subject: Re: [RoverLog] Digest for rove...@googlegroups.com - 1 Message in
> 1 Topic
>
>
> Indeed we've discussed this before :)
>
> I've been running with a hacked version for a couple of years that
> attempts to work both ways (mostly successfully) .. if you change the
> band on the keyboard, the radion correctly changes bands, and if you
> change the radio band Roverlog follows.
>
>
>
> You received this message because you are subscribed to the Google Group
> roverlog.
> You can post via email.
> To unsubscribe from this group, send an empty message.
> For more options, visit this group.
>
> --
> You received this message because you are subscribed to the Google Groups
> "RoverLog" group.
> To post to this group, send email to rove...@googlegroups.com.
> To unsubscribe from this group, send email to
> roverlog+u...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>