[chirp_devel] chirp_devel Digest, Vol 20, Issue 13

[Drew Vonada-Smith]

Dan,

I'm just following the instructions to the best of my ability.  I am not
aware of any other way to run this except from the command line, because
that is what the developer instructions noted.  "python chirpw" from a
Windows command prompt.

I was able to get the log from piping as you noted.  I did not remember how
to do that, as we haven't used anything but an integrated dev env in many
years.   I don't know what is specific to Chirp vs Python vs the OS...  I'm
a hardware guy.  Anyway, I did not see the last address information you
noted, unless End frame (11) means something I am unfamiliar with.  0e80 was
the size I used, and this resulted in:

User selected Icom IC-V80 on port COM10
Clone thread started
Sent clone frame
ICF Size change from 0 to 32 at 0000
End frame (11):
000: 49 63 6f 6d 20 49 6e 63   Icom.Inc
008: 2e 37 34 00 00 00 00 00   .74.....

Last addr: 0e80
Clone thread ended
Exception running RadioJob: list index out of range
-- Exception: --
Traceback (most recent call last):
  File "P:\Chirp\chirp.hg\chirpui\common.py", line 97, in _execute
    result = func(*self.args, **self.kwargs)
  File "P:\Chirp\chirp.hg\chirp\icv80.py", line 95, in get_memory
    mem.ctone = chirp_common.TONES[_mem.ctone - 1]
IndexError: list index out of range

Anyway, you seem to be looking for someone with more experience at this than
I have, so I'd best pass on driver work.  Maybe the info above is useful to
someone...  Thanks for the fine program.

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 01, 2013 15:01
To: chirp_devel at intrepid.danplanet.com
Subject: Re: [chirp_devel] chirp_devel Digest, Vol 20, Issue 13

> No, that only includes debug logs from yesterday before I installed 
> the dev env...

Sorry, I don't mean to get overly blunt, but are you even reading my
messages?

>From your quoted text, I said:

> However, as I said, if you're running from the command line, the 
> contents go to the screen, not the log.

Which implies that the debug log in the profile area is only going to be
from the last time you ran it normally.

This is what you want in order to capture the console output to a file for
later examination:

> In this case "this env" is Windows. The standard way of redirecting 
> the output of a program to a file is all you need:
> 
>   C:\foo\chirp.hg> python chirpw > my_log_file.txt

--
Dan Smith
www.danplanet.com
KK7DS