[chirp_devel] chirp_devel Digest, Vol 20, Issue 13

[Drew Vonada-Smith]

See below

...sent from my cell phone


On Jan 2, 2013, at 11:10, Dan Smith <dsmith at danplanet.com> wrote:

>> 1)  146.52, simplex.  No tone.  Label AAAAA
>> 2)  146.76, offset minus, 600 KHz.  Tone, 88.5.  Label BBBBB
> 
> I thought you said the V80 couldn't do names? Were you just
> talking about bank names?

The manual does not mention ch names.  They do however appear in the icom programming GUI and are saved
> 
>> It appears to me that a memory channel is 16 bytes long.
> 
> Agreed.
> 
>> The first two bytes appear to be frequency / 5000, not three as in IC-T70.
> 
> Could be, but watch out for the case when/where frequencies are 6.25kHz
> step (unless the V80 doesn't support that).

Already noted
> 
>> After that, I can start setting/unsetting bits and figure out the
>> other features.
> 
> Cool! 
> 
>> Is it correct that CTCSS tones are usually enumerated rather than
>> literal values?  Where can I find the enumerations?
> 
> On Icom radios, that is usually the case, yes. The enumerations are in
> chirp_common.TONES, and you should see that array used in the T70
> driver in the same way you'll need to use it.

Ok
> 
>> Also, since this radio does not use memory banks, do I have to strip
>> out any bank code and/or structures from the IC-T70 driver, or does
>> setting:
> 
> You should strip out any code that is not used, yes. Are you sure it
> doesn't even support the low-end bank model of just A-J? If you look at
> something like the IC2200 driver, you'll see that simpler model in use.
> I've not seen any Icom radios in the last ten years that didn't support
> at least that bank model.
> 
I havent a clue or any idea how to find out about banks. The manual doesnt note banks nor does the Icom s/w.

I'll look at the bank code but not sure im up to that.  I dont do python...

>> Making the changes noted to the data structure and bank definitions
>> does not result in the UI showing the correct frequency (it just says
>> ERROR), so I am not clear on what else I am missing.  Any tips
>> appreciated.
> 
> Well, it's probably failing to parse something else. You'll need to
> look at the output on the console while it's trying to parse the image
> to see why. Probably a stack trace that ends in a complain about
> something on a specific line in the code. I would comment out
> everything in get_memory() that you don't have implemented and slowly
> add them back, starting with frequency.
> 
> Good progress, sounds like success is on the horizon :)
> 
> -- 
> Dan Smith
> www.danplanet.com
> KK7DS
> _______________________________________________
> chirp_devel mailing list
> chirp_devel at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
> Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers