I will open these two things up.

On Mon, May 2, 2011 at 12:00 PM, <chirp_users-request@intrepid.danplanet.com> wrote:

Send chirp_users mailing list submissions to
chirp_users@intrepid.danplanet.com

To subscribe or unsubscribe via the World Wide Web, visit
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
or, via email, send a message with subject or body 'help' to
chirp_users-request@intrepid.danplanet.com

You can reach the person managing the list at
chirp_users-owner@intrepid.danplanet.com

When replying, please edit your Subject line so it is more specific
than "Re: Contents of chirp_users digest..."

Today's Topics:

1. Re: [CHIRP] #89: Not all frequencies showing (Dan Smith)

----------------------------------------------------------------------

Message: 1
Date: Mon, 02 May 2011 10:49:43 -0700
From: Dan Smith <dsmith@danplanet.com>
Subject: Re: [chirp_users] [CHIRP] #89: Not all frequencies showing
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com>
Message-ID: <4DBEEEB7.3030903@danplanet.com>
Content-Type: text/plain; charset=windows-1252; format=flowed

> The bad news is (and I verified by rolling it back to see if this
> existed with the previous version) is when it reads memory channel 12,
> it is displaying a slight difference in the actual setting.

So the older build shows the proper frequency and the new one does not?
That runs contrary to some of my testing, but I also have done some
work on the functions that detect 12.5 and 6.25 step frequencies
recently, so maybe something has changed.

If you could file another bug for this issue, I'd appreciate it. I'll
take a look.

> Another issue that is exhibited is, if a write the 800MHz frequency to
> the channel via the radio key pad, it is masked by VFO B as it isn't a
> supported channel. If I use the SW to write a 800MHz frequency then,
> even though it isn't supported by VFO B, it shows up when moving through
> the VFO B memory channels.
> Also, if I read the memory with the SW. Then write in a new frequency on
> a new memory channel, then write it to the radio, the previously masked
> frequencies stay masked.
> If a change is made to an already existing memory channel, it becomes
> unmasked to VFO B even if it is in that 800MHZ range.

Ah, okay, I know why that is. If you can file a bug for this one too
(just to keep things organized) I'll get this resolved.

Thanks!

--
Dan Smith
www.danplanet.com
KK7DS

------------------------------

_______________________________________________
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users

End of chirp_users Digest, Vol 29, Issue 3
******************************************