[chirp_devel] chirp_devel Digest, Vol 20, Issue 13

[Drew Vonada-Smith]

I stripped out the bank code, no idea if done correctly.  Latest code is
attached.

I really have no idea how to debug past this.  No knowing Python or this
code, all I can do is capture the errors and pass along out.txt.  I've tried
commenting out the majority of the code and still get the same errors.  

If I can get a working UI, I am capable of setting items bit wise and
teasing apart the structure.  But I will need someone to look at the code.

73,
Drew K3PA 

-----Original Message-----
From: chirp_devel-bounces at intrepid.danplanet.com
[mailto:chirp_devel-bounces at intrepid.danplanet.com] On Behalf Of Dan Smith
Sent: January 02, 2013 14:15
To: chirp_devel at intrepid.danplanet.com
Subject: Re: [chirp_devel] chirp_devel Digest, Vol 20, Issue 13

> The manual does not mention ch names.  They do however appear in the 
> icom programming GUI and are saved

Page 28 in the manual. It also gives the character set, so you can declare
the correct set of supported glyphs in rf.valid_characters.

> I havent a clue or any idea how to find out about banks. The manual 
> doesnt note banks nor does the Icom s/w.

Yeah, looks like the radio doesn't support it, that's interesting!
So, yeah, you can just nix all the bank-related code from the driver.

--
> 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? 

> 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).

> 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.

> 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.

> 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: icv80.py
Type: application/octet-stream
Size: 5237 bytes
Desc: not available
Url : http://intrepid.danplanet.com/pipermail/chirp_devel/attachments/20130102/1021bb18/attachment-0001.obj 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: out.txt
Url: http://intrepid.danplanet.com/pipermail/chirp_devel/attachments/20130102/1021bb18/attachment-0001.txt