Dan,
I found where you said to get the debug log from the Windows user profile. Sorry, I had missed it the first time. However, this contains the debug file from the last time I ran CHIRP outside of the dev env. It does not include when I run it from python.
Where can I find the development copy of same?
Drew
-----Original Message----- From: chirp_devel-bounces@intrepid.danplanet.com [mailto:chirp_devel-bounces@intrepid.danplanet.com] On Behalf Of Dan Smith Sent: January 01, 2013 14:30 To: chirp_devel@intrepid.danplanet.com Subject: Re: [chirp_devel] chirp_devel Digest, Vol 20, Issue 13
- Created a driver "icv80.py" by renaming the one for the IC-T70.
That is their identical HT but dual band, so is presumably close
Probably, but not definitely :)
It's possible that they're very similar and that just tweaking the mem_format (or the offset where it starts looking for it) is all that is needed. If so, it may be best to make the V80 driver inherit from the T70, and only change a few things. However, keeping it separate like you have it now is probably the best way to start. If you start making minor tweaks to T70 code, that would be your indication that sharing is warranted.
- Did a download and saw the mode string 0x32 0x54 0x00 0x01. Changed
_model to match and HT seems to now be recognized
Cool.
- Increased _memsize greatly and ran a new download. Where is the
debug log that you speak of? I have no familiarity with this lang or env.
It's not a language or environment thing, it's a CHIRP thing:
http://chirp.danplanet.com/projects/chirp/wiki/How_to_report_issues
There is a section on there for "getting your debug log".
So I have error messages of course, but nothing that shows a last address.
The debug log will give you what you need.
Should this be in the command prompt window that I used to initiate the program? That is where I get error messages. Or is there some debug log somewhere else in Python? I'm familiar with using *nix, but never developed in it.
Oh, you're running from the command-line, then yeah, the debug log contents are just echoed to the console in that case. When the download is complete, you should see it echo the "Last addr:" and "End Frame:" to the console there. It may have scrolled off the screen amidst all the failures to parse the V80 data in T70 format. Might be good to pipe it to a file for perusal or something.
Sounds like you're getting there... :)
-- Dan Smith www.danplanet.com KK7DS