Thank you for your response. I hope this gets to who it needs too

I have attached two IMG files that I got from the radio. The one titled "radio read" is how the radio reads as programmed. The other file titled "Actual" shows the frequencies where they are. Basically memories 7-12 (there is also one on 6 but it is similar to the others) are where the 800MHz freq are. One "feature" of the VX8R that I have noticed is that when a frequency is programmed into the radio that can only be received on channel A, it is masked and skipped when moving through the memory channels with channel B selected. This is a nice feature in that the user isn't tuning to a non receivable freq on the B channel. What I notice is that the CHIRP software does not see these entries just like the channel B does not see them. But if you enter the frequencies into CHIRP and send them to the radio, they appear on both the A & B channels even though Channel B cannot actually tune to those frequencies. It is as if the software is reading and writing to the B channel of the radio. I do not know how the radio handles its memories. There must be something in the firmware that makes the radio mask the frequencies from the B channel that it cannot tune.

Thank you for a good product and I do hope my feedback helps to further the usefulness of this product.

Dan KF7ICX

On Fri, Apr 22, 2011 at 2:14 PM, CHIRP Tracker donotreply@danplanet.comwrote:

#89: Not all frequencies showing

--------------------------------------+------------------------------------- Reporter: dan.my.studio@… | Owner: Type: Feature | Status: new Priority: Stability | Milestone: Component: Memory Editor | Version: Resolution: | Keywords: Platform: Windows |

--------------------------------------+-------------------------------------

Comment (by kk7ds):

Please attach an image and describe where the 800MHz frequencies are (i.e. which channels they're stored in)

Thanks!

-- Ticket URL: http://trac.chirp.danplanet.com/trac/ticket/89#comment:1 CHIRP http://trac.chirp.danplanet.com/trac CHIRP Development

Sorry about this. I was dealing with some family issues this weekend. Will test this first thing in the morning Monday. Thanks Dan

On Apr 29, 2011, at 7:31 PM, "CHIRP Tracker" donotreply@danplanet.com wrote:

#89: Not all frequencies showing --------------------------------------+------------------------------------- Reporter: dan.my.studio@… | Owner: kk7ds Type: Feature | Status: accepted Priority: Stability | Milestone: Component: Memory Editor | Version: Resolution: | Keywords: Platform: Windows | --------------------------------------+------------------------------------- Changes (by kk7ds):

• owner: => kk7ds
• status: new => accepted

Comment:

Fixed in changeset:906. Please grab tonight's daily build and confirm the fix tomorrow. Daily builds are here:

http://trac.chirp.danplanet.com/chirp_daily/

Also, is there anything else different about those memories, other than being 800MHz?

Thanks!

-- Ticket URL: http://trac.chirp.danplanet.com/trac/ticket/89#comment:2 CHIRP http://trac.chirp.danplanet.com/trac CHIRP Development

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!