RE: [dstar_digital] CHIRP: An open-source programming tool for ICOM radios

[Greg Forrest]

..the new kitten on the keyboard

Greg

> 
> Greg,
> 
> If you typed anything in reply, it didn't show up... just blank.
> 
>
> 

Re: [dstar_digital] CHIRP: An open-source programming tool for ICOM radios

[Nate Duehr]

Greg,

If you typed anything in reply, it didn't show up... just blank.

On Jul 25, 2008, at 7:37 PM, Greg Forrest wrote:

>
>
> > -Original Message-
> > From: dstar_digital@yahoogroups.com
> > [mailto:[EMAIL PROTECTED] Behalf Of Nate Duehr
> > Sent: Friday, July 25, 2008 16:05
> > To: dstar_digital@yahoogroups.com
> > Subject: Re: [dstar_digital] CHIRP: An open-source programming  
> tool for
> > ICOM radios
> >
> >
> > John D. Hays wrote:
> >
> > > There is a PERL based 91AD programmer at http://dstarutah.org
> > > <http://dstarutah.org> in the
> > > files section. It may help you figure out some additional  
> parameters.
> >
> > The comments in the Perl are great, by the way... full  
> descriptions of
> > the binary/hex that's going in/out. Good programmer!
> >
> > Nate WY0X
>

> --
>

Nate Duehr
[EMAIL PROTECTED]

RE: [dstar_digital] CHIRP: An open-source programming tool for ICOM radios

[Greg Forrest]

> -Original Message-
> From: dstar_digital@yahoogroups.com
> [mailto:[EMAIL PROTECTED] Behalf Of Nate Duehr
> Sent: Friday, July 25, 2008 16:05
> To: dstar_digital@yahoogroups.com
> Subject: Re: [dstar_digital] CHIRP: An open-source programming tool for
> ICOM radios
> 
> 
> John D. Hays wrote:
> 
> > There is a PERL based 91AD programmer at http://dstarutah.org 
> > <http://dstarutah.org> in the
> > files section. It may help you figure out some additional parameters.
> 
> The comments in the Perl are great, by the way... full descriptions of 
> the binary/hex that's going in/out.  Good programmer!
> 
> Nate WY0X
> 
> 
> 
> Please TRIM your replies or set your email program not to include 
> the original  message in reply unless needed for clarity.  
> ThanksYahoo! Groups Links
> 
> 
> 

Re: [dstar_digital] CHIRP: An open-source programming tool for ICOM radios

[Nate Duehr]

John D. Hays wrote:

> There is a PERL based 91AD programmer at http://dstarutah.org 
>  in the
> files section. It may help you figure out some additional parameters.

The comments in the Perl are great, by the way... full descriptions of 
the binary/hex that's going in/out.  Good programmer!

Nate WY0X

Re: [dstar_digital] CHIRP: An open-source programming tool for ICOM radios

[John D. Hays]

> 
Dan,

There is a PERL based 91AD programmer at http://dstarutah.org in the 
files section. It may help you figure out some additional parameters.
-- 
John D. Hays
Amateur Radio Station K7VE 
PO Box 1223
Edmonds, WA 98020-1223
VOIP/SIP: [EMAIL PROTECTED] 
Phone: 206-801-0820
801-790-0950
Fax: 866-309-6077
In the UK: 08449867545
Email: [EMAIL PROTECTED] 


[Non-text portions of this message have been removed]

Re: [dstar_digital] CHIRP: An open-source programming tool for ICOM radios

[Dan Smith]

> Weeel. yes and no. If I download then upload, everything
> looks as it was. If I download, export, import, and upload, it isn't
> - memories with tone squelch become memories with tone. Looks like
> that's simply because the CSV file only shows tone on or off.

Heh, well, I should have qualified that a bit more :D

Right now, there is (as you can tell) a limit to the comprehension level
of the memory parsing code.

If you'd like to send me your .img file after a fresh download, it will
help me increase my understanding of things.  You have to keep in mind
that this is only about two weeks of (spare time) effort at this point... :)

> Cool program though, it's working well for me.

I should point out that if you trim your CSV file before importing
again, you can just update the memories that are in the CSV, without it
trying to recreate everything from the CSV, which obviously isn't a full
description of a memory channel.

Thanks for the feedback.  I should be ready to post an 0.1.3 soon with
all the fixes we've worked out here, as well as some extra stuff like
support for the A band on the handhelds, etc.

-- 
Dan Smith
dsmith#danplanet.com, s/#/@/
www.danplanet.com
KK7DS

Re: [dstar_digital] CHIRP: An open-source programming tool for ICOM radios

[Brian Mury]

On Thu, 2008-07-24 at 06:32 -0700, Dan Smith wrote:
> > Does this mean if I upload the image file, I'll lose whatever setting I
> > have that you aren't handling? Or was I just messing up your error
> > handling?
> 
> Nope, the download was going just fine, it was just the subsequent 
> parsing of the image that was choking unnecessarily. An upload should 
> work fine.

Weeel. yes and no. If I download then upload, everything looks
as it was. If I download, export, import, and upload, it isn't -
memories with tone squelch become memories with tone. Looks like that's
simply because the CSV file only shows tone on or off.

Cool program though, it's working well for me.

Re: [dstar_digital] CHIRP: An open-source programming tool for ICOM radios

[Dan Smith]

> That fixed it!

Great!

> Does this mean if I upload the image file, I'll lose whatever setting I
> have that you aren't handling? Or was I just messing up your error
> handling?

Nope, the download was going just fine, it was just the subsequent 
parsing of the image that was choking unnecessarily.  An upload should 
work fine.

Thanks!

-- 
Dan Smith
dsmith#danplanet.com, s/#/@/
www.danplanet.com
KK7DS

Re: [dstar_digital] CHIRP: An open-source programming tool for ICOM radios

[Brian Mury]

On Wed, 2008-07-23 at 21:36 -0700, Dan Smith wrote:
> I've tightened that down. If you want to grab a snapshot of my
> development tree and try again, it would be appreciated:

That fixed it!

> Okay, I wasn't masking out enough bits for the tone value. You've got
> something turned on in a memory location that I don't have, and so
> you've got a bit (0x80) turned on that is throwing it out of range.

Does this mean if I upload the image file, I'll lose whatever setting I
have that you aren't handling? Or was I just messing up your error
handling?

Re: [dstar_digital] CHIRP: An open-source programming tool for ICOM radios

[Dan Smith]

>> ./chirp.py -r ic2820 -s /dev/ttyS1 --download-mmap

Okay, you'll want to add "--mmap foo.img" to give it somewhere to save
the image to once it gets there.

> chirp.errors.InvalidDataError: Radio has unknown tone 0x8E

Okay, I wasn't masking out enough bits for the tone value.  You've got
something turned on in a memory location that I don't have, and so
you've got a bit (0x80) turned on that is throwing it out of range.

I've tightened that down.  If you want to grab a snapshot of my
development tree and try again, it would be appreciated:

http://d-rats.danplanet.com/hg/hgwebdir.cgi/chirp.hg/archive/tip.tar.gz

It might be worth taking this off-list for a bit if this doesn't fix it
for you.  Just to avoid boring people with the details :)

Thanks!

-- 
Dan Smith
dsmith#danplanet.com, s/#/@/
www.danplanet.com
KK7DS

Re: [dstar_digital] CHIRP: An open-source programming tool for ICOM radios

[Brian Mury]

On Wed, 2008-07-23 at 06:38 -0700, Dan Smith wrote:
> I wasn't aware that you could do clone operations through the front 
> data port. You can use the CS-2820 through that port?

Yes.

> The serial cable schematics won't, but the CI-V cloning cables will:

Yep, but this isn't a CI-V cable. It's a standard three wire serial
cable.

> Did the radio go into "clone out" mode and take a couple minutes to do
> the clone?

Yes.

> Can you send me the ic2820.img file in the working directory so I can 
> see if it looks like a valid memory image?

There isn't one.

Using chirp.py:

> ./chirp.py -r ic2820 -s /dev/ttyS1 --download-mmap
|==| 100.0% Cloning from radioTraceback (most recent call last):
  File "./chirp.py", line 199, in 
radio.sync_in()
  File "/home/bmury/software/chirp-0.1.2/chirp/ic2820.py", line 62, in sync_in
self.process_mmap()
  File "/home/bmury/software/chirp-0.1.2/chirp/ic2820.py", line 40, in 
process_mmap
self._memories = ic2820_ll.parse_map_for_memory(self._mmap)
  File "/home/bmury/software/chirp-0.1.2/chirp/ic2820_ll.py", line 121, in 
parse_map_for_memory
m = get_memory(map, i)
  File "/home/bmury/software/chirp-0.1.2/chirp/ic2820_ll.py", line 56, in 
get_memory
raise errors.InvalidDataError("Radio has unknown tone 0x%02X" % _tonei)
chirp.errors.InvalidDataError: Radio has unknown tone 0x8E

Re: [dstar_digital] CHIRP: An open-source programming tool for ICOM radios

[Dan Smith]

> Well, my guess would be that's because it's downloading information that 
> isn't a normal memory image from the radio.  Thus, when it's done, it 
> still doesn't have a valid image and won't let you try to export it.
> 
> Did the radio go into "clone out" mode and take a couple minutes to do 
> the clone?

Okay, I just tried and it worked through the serial port.  I can't get 
my ID-800 to do that, so I'm guessing it's just a feature of the 2820, 
but I'll have to experiment some more.

I will post a new version this afternoon with the ability to choose 
between a CI-V cable and a straight RS-232 cable.

Brian, my memory image loaded fine through the front data port, so if 
you will send me your image (privately) I'll figure out why it's not 
loading and try to roll the change into the version I post with the 
cable switch.

Thanks!

-- 
Dan Smith
dsmith#danplanet.com, s/#/@/
www.danplanet.com
KK7DS

Re: [dstar_digital] CHIRP: An open-source programming tool for ICOM radios

[Dan Smith]

> No, it's a homebrew cable. I'm using the front data port.

So, someone else mentioned something about this.  I wasn't aware that 
you could do clone operations through the front data port.  You can use 
the CS-2820 through that port?

> Oh? I didn't know that. I found a document online that shows a cable
> schematic, it does not have them connected together.

The serial cable schematics won't, but the CI-V cloning cables will:

   http://uk.geocities.com/blakkekatte/CIVhardware.html

> Yeah, that works. I just did a successful download. It won't let me
> export, import, or upload (those are disabled, and it says "no image",
> even after downloading), but that's a different issue... I'm going to
> play around with the command line tool and see what I can do with that.

Well, my guess would be that's because it's downloading information that 
isn't a normal memory image from the radio.  Thus, when it's done, it 
still doesn't have a valid image and won't let you try to export it.

Did the radio go into "clone out" mode and take a couple minutes to do 
the clone?

Can you send me the ic2820.img file in the working directory so I can 
see if it looks like a valid memory image?

In the meantime, I'll try doing a clone of my 2820 through the front 
data port and see what I get :)

-- 
Dan Smith
dsmith#danplanet.com, s/#/@/
www.danplanet.com
KK7DS

Re: [dstar_digital] CHIRP: An open-source programming tool for ICOM radios

[Brian Mury]

On Tue, 2008-07-22 at 16:48 -0700, Dan Smith wrote:
> It's strange that your cable doesn't seem to be echoing what the PC
> sends. Are you using an OPC-478?

No, it's a homebrew cable. I'm using the front data port.

> In the ICOM (and I think all other)
> cables, the TX and RX pins are tied together in the db9 connector,

Oh? I didn't know that. I found a document online that shows a cable
schematic, it does not have them connected together.

> If you want, edit chirp/icf.py, and in the send_clone_frame()
> function,
> put "return frame" right after the "pipe.write(frame)" line. This
> should stop it from eating and comparing the echo.

Yeah, that works. I just did a successful download. It won't let me
export, import, or upload (those are disabled, and it says "no image",
even after downloading), but that's a different issue... I'm going to
play around with the command line tool and see what I can do with that.

Thanks for the help!

Brian

Re: [dstar_digital] CHIRP: An open-source programming tool for ICOM radios

[Dan Smith]

> Tried that, no change.

It's strange that your cable doesn't seem to be echoing what the PC
sends.  Are you using an OPC-478?  In the ICOM (and I think all other)
cables, the TX and RX pins are tied together in the db9 connector, so
that the computer sees everything that it sends, plus the radio data.

If you want, edit chirp/icf.py, and in the send_clone_frame() function,
put "return frame" right after the "pipe.write(frame)" line.  This
should stop it from eating and comparing the echo.

The response you're getting is the radio reporting its version number,
so the two-way communication seems to be happy.

-- 
Dan Smith
dsmith#danplanet.com, s/#/@/
www.danplanet.com
KK7DS

Re: [dstar_digital] CHIRP: An open-source programming tool for ICOM radios

[Brian Mury]

On Tue, 2008-07-22 at 06:34 -0700, Dan Smith wrote:
> Okay, this is strange because the echo comes from the wiring in the 
> clone cable. Can you post the output of "stty -F /dev/ttyS1" ?

speed 9600 baud; line = 0;
min = 0; time = 0;
-brkint -icrnl -imaxbel
-opost
-isig -icanon -iexten -echo -echoe -echok -echoctl -echoke

0:4:cbd:0:3:1c:7f:15:4:0:0:0:11:13:1a:0:12:f:17:16:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0

> and the compressed version is:
> 
> 0:4:8bd:80:3:1c:7f:15:fd:0:0:0:11:13:1a:0:12:f:17:16:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0
> 
> Which you should be able to pass to stty to set yours the same. I 

Tried that, no change.

Re: [dstar_digital] CHIRP: An open-source programming tool for ICOM radios

[Dan Smith]

> Cool! The Icom CS-2820 doesn't work properly in WINE or virtualized
> Windows.

That's *one* of the reasons for doing this... :)

> chirp.errors.RadioError: Radio did not echo frame

Okay, this is strange because the echo comes from the wiring in the 
clone cable.  Can you post the output of "stty -F /dev/ttyS1" ?

For reference, mine is:

   % stty -F /dev/ttyUSB0
   speed 9600 baud; line = 0;
   eof = M-}; min = 0; time = 0;
   -brkint -icrnl -imaxbel
   -opost
   -isig -icanon -iexten -echo -echoe -echok noflsh -echoctl -echoke

and the compressed version is:

0:4:8bd:80:3:1c:7f:15:fd:0:0:0:11:13:1a:0:12:f:17:16:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0

Which you should be able to pass to stty to set yours the same.  I 
completely forgot, but I haven't rebooted my system since I started 
this, and I did have to tweak some of the serial parameters to get it to 
behave correctly.

-- 
Dan Smith
dsmith#danplanet.com, s/#/@/
www.danplanet.com
KK7DS

Re: [dstar_digital] CHIRP: An open-source programming tool for ICOM radios

[Brian Mury]

On Mon, 2008-07-21 at 13:11 -0700, Dan Smith wrote:
> - Program as many ICOM radio models as possible with a single app
> - Be open-source
> - Be cross-platform
> - Support open data formats

Cool! The Icom CS-2820 doesn't work properly in WINE or virtualized
Windows.

> there are plenty of errors at this point. However, if you'd like to
> give it a try and report back, it would be much appreciated. If you

I'm trying it with my 2820, running Fedora 9.

csvdump.py gives me this when I click on the download button:

Bad response:
000: fe fe ef ee e1 29 70 00   .)p.
008: 01 20 20 20 20 20 20 20   
016: 20 20 20 20 20 20 20 20   
024: 20 00 0e 03 00 06 33 30   ..30
032: 30 41 30 2e 30 30 fd 00   0A0.00..
Sent:
000: fe fe ee ef e0 00 00 00   
008: 00 fd 00 00 00 00 00 00   


Trying chirp.py instead:

> ./chirp.py -r ic2820 -s /dev/ttyS1 --download-mmap
Bad response:
000: fe fe ef ee e1 29 70 00   .)p.
008: 01 20 20 20 20 20 20 20   
016: 20 20 20 20 20 20 20 20   
024: 20 00 0e 03 00 06 33 30   ..30
032: 30 41 30 2e 30 30 fd 00   0A0.00..
Sent:
000: fe fe ee ef e0 00 00 00   
008: 00 fd 00 00 00 00 00 00   

Traceback (most recent call last):
  File "./chirp.py", line 199, in 
radio.sync_in()
  File "/home/bmury/software/chirp-0.1.2/chirp/ic2820.py", line 61, in sync_in
self._mmap = icf.clone_from_radio(self)
  File "/home/bmury/software/chirp-0.1.2/chirp/icf.py", line 151, in 
clone_from_radio
md = get_model_data(radio.pipe)
  File "/home/bmury/software/chirp-0.1.2/chirp/icf.py", line 31, in 
get_model_data
send_clone_frame(pipe, 0xe0, model, raw=True)
  File "/home/bmury/software/chirp-0.1.2/chirp/icf.py", line 91, in 
send_clone_frame
raise errors.RadioError("Radio did not echo frame")
chirp.errors.RadioError: Radio did not echo frame

Re: [dstar_digital] CHIRP: An open-source programming tool for ICOM radios

[Dan Smith]

> Are you using Python 2.5.2 for your compiling?

The nature of Python is that it's not compiled in the conventional
sense.  But yes, it's using a Python 2.5.2 runtime

-- 
Dan Smith
dsmith#danplanet.com, s/#/@/
www.danplanet.com
KK7DS

Re: [dstar_digital] CHIRP: An open-source programming tool for ICOM radios

[Dan Smith]

> Okay I have the software installed, and when I use the csvdump.exe 
> file.  I am not seeing a good gui.  What kind of graphics are you 
> using?  Are they bitmap graphics?  If so can you make this a windows 
> standard diwlogue?  This would make it easier for those who are 
> totaly blind to use.

There are no graphics being displayed, just normal widgets.  As I
understand it, the GTK widgets are near-native on Windows, but don't
always use the Win32 widgets on the screen.  I don't really know much
about the Windows API, so I can't tell you much more than that.

I use GTK so that it can be cross-platform.  I have zero interest in
writing Windows-only applications :)

-- 
Dan Smith
dsmith#danplanet.com, s/#/@/
www.danplanet.com
KK7DS

Re: [dstar_digital] CHIRP: An open-source programming tool for ICOM radios

[Justin Mann]

Okay I have the software installed, and when I use the csvdump.exe file.  I am 
not seeing a good gui.  What kind of graphics are you using?  Are they bitmap 
graphics?  If so can you make this a windows standard diwlogue?  This would 
make it easier for those who are totaly blind to use.  
  - Original Message - 
  From: Dan Smith 
  To: dstar_digital@yahoogroups.com 
  Sent: Monday, July 21, 2008 2:48 PM
  Subject: Re: [dstar_digital] CHIRP: An open-source programming tool for ICOM 
radios


  > I have the 91ad. I've just downloaded the software, and am trying to
  > install the stuff. I'm looking in the wiki, and don't see anything 
  > as of yet as to what happens after you download the file.

  Assuming you're on Windows, there is a csvdump.exe in the zip file. Run
  that and you'll get a GUI that lets you select your radio and serial
  port. With the 91AD, you can go straight to the bottom and choose a
  filename and hit export to dump it out.

  > The reason for such excitement is that i am totaly blind, and this
  > rs91 software that I am using is not verry useful. I can kinda sorta
  > edit memories, but as for having any kind of functionality it
  > doesn't. The idea of an alternative really has me excited
  > particularly if I can use the thing!!!

  Well, I should point out that there is also a command-line tool in the
  package that lets you do things without a GUI. Right now, it doesn't
  have an option to dump the data to CSV, but I'll gladly add it. It's
  the chirp.exe binary in the zip file. If you're comfortable running
  that from a command-line, it may work better for you with a screen reader.

  -- 
  Dan Smith
  dsmith#danplanet.com, s/#/@/
  www.danplanet.com
  KK7DS



   

[Non-text portions of this message have been removed]

Re: [dstar_digital] CHIRP: An open-source programming tool for ICOM radios

[Dennis Rogers]

Are you using Python 2.5.2 for your compiling?
I'll take a look at this program and thanks.

More on D-rats later. Still having issues and need to send you my settings
and all.

Dennis

On Mon, Jul 21, 2008 at 3:11 PM, Dan Smith <[EMAIL PROTECTED]> wrote:

>   Hi all,
>
> I've been working on a tool that aims to accomplish the following goals:
>
> - Program as many ICOM radio models as possible with a single app
> - Be open-source
> - Be cross-platform
> - Support open data formats
>
> The result is CHIRP (CHIRP Handles Icom Radio Programming) and is
> reasonably functional at this point. It supports the following radios:
>
> - IC-2820H
> - IC-2200H
> - ID-800H
> - IC-91AD
> - IC-92AD
>
> Currently, it just imports/exports the memory contents to a CSV file,
> with attributes like Name, Frequency, Tone, and Duplex. More will come
> in the future, but I think this is a good start.
>
> It's very rough, and probably very buggy. I have reverse-engineered the
> clone protocol and memory formats by just sniffing the wire, so I'm sure
> there are plenty of errors at this point. However, if you'd like to
> give it a try and report back, it would be much appreciated. If you
> have the ICOM-supplied program for your radio, it wouldn't hurt to make
> a backup before you play.
>
> It's not much yet, but I feel confident that I can turn it into a
> reasonable replacement for the jumble of commercial options available.
> If you're interested, check it out here:
>
> http://chirp.danplanet.com
>
> I'm posting this here because people have expressed a desire for this
> functionality in this forum. If you know of other places that would be
> appropriate for an announcement, please let me know.
>
> Thanks!
>
> --
> Dan Smith
> dsmith#danplanet.com, s/#/@/
> www.danplanet.com
> KK7DS
>
>  
>



-- 
Regards,

Dennis, N5VRP
[EMAIL PROTECTED]

Dstar User / Gateway Admin / D-PRS Provider(soon)
ARRL Member
Cactus-Intertie Member
AMSAT Member, President's Club

73's from SATX, EL09rk


[Non-text portions of this message have been removed]

Re: [dstar_digital] CHIRP: An open-source programming tool for ICOM radios

[Justin Mann]

Unfortunately the command line access for a screen-reader is going by the way 
side... Sad but true.  
 

Re: [dstar_digital] CHIRP: An open-source programming tool for ICOM radios

[Dan Smith]

> I have the 91ad.  I've just downloaded the software, and am trying to
> install the stuff.  I'm looking in the wiki, and don't see anything 
> as of yet as to what happens after you download the file.

Assuming you're on Windows, there is a csvdump.exe in the zip file.  Run
that and you'll get a GUI that lets you select your radio and serial
port.  With the 91AD, you can go straight to the bottom and choose a
filename and hit export to dump it out.

> The reason for such excitement is that i am totaly blind, and this
> rs91 software that I am using is not verry useful.  I can kinda sorta
> edit memories, but as for having any kind of functionality it
> doesn't. The idea of an alternative really has me excited
> particularly if I can use the thing!!!

Well, I should point out that there is also a command-line tool in the
package that lets you do things without a GUI.  Right now, it doesn't
have an option to dump the data to CSV, but I'll gladly add it.  It's
the chirp.exe binary in the zip file.  If you're comfortable running
that from a command-line, it may work better for you with a screen reader.

-- 
Dan Smith
dsmith#danplanet.com, s/#/@/
www.danplanet.com
KK7DS

Re: [dstar_digital] CHIRP: An open-source programming tool for ICOM radios

[Justin Mann]

I have the 91ad.  I've just downloaded the software, and am trying to install 
the stuff.  I'm looking in the wiki, and don't see anything as of yet as to 
what happens after you download the file.  The reason for such excitement is 
that i am totaly blind, and this rs91 software that I am using is not verry 
useful.  I can kinda sorta edit memories, but as for having any kind of 
functionality it doesn't.  The idea of an alternative really has me excited 
particularly if I can use the thing!!!

Re: [dstar_digital] CHIRP: An open-source programming tool for ICOM radios

[Dan Smith]

> You have no idea how much you have just made my afternoon!!!

Well, hold off on that until it works for you, okay? :)

> Do I need any speciffic cabling, or can I use the standard cable that
> plugs in to the data port?

It depends on the radio.  If you have an IC-91AD or IC-92AD, you can use
your normal data cable.  If you have one of the others, you need the
cable that interfaces with the speaker/clone jack.  The ICOM cloning 
cable will work, or you can make your own.  There are schematics 
available all over the place (and I'm sure people will chime in with 
their favorite).

-- 
Dan Smith
dsmith#danplanet.com, s/#/@/
www.danplanet.com
KK7DS

[ED: Is that a new callsign? + http://cobalt.n5zpr.com/dstar2.html)

Re: [dstar_digital] CHIRP: An open-source programming tool for ICOM radios

[Justin Mann]

You have no idea how much you have just made my afternoon!!!  Do I need any 
speciffic cabling, or can I use the standard cable that plugs in to the data 
port?  

[dstar_digital] CHIRP: An open-source programming tool for ICOM radios

[Dan Smith]

Hi all,

I've been working on a tool that aims to accomplish the following goals:

  - Program as many ICOM radio models as possible with a single app
  - Be open-source
  - Be cross-platform
  - Support open data formats

The result is CHIRP (CHIRP Handles Icom Radio Programming) and is
reasonably functional at this point.  It supports the following radios:

  - IC-2820H
  - IC-2200H
  - ID-800H
  - IC-91AD
  - IC-92AD

Currently, it just imports/exports the memory contents to a CSV file,
with attributes like Name, Frequency, Tone, and Duplex.  More will come
in the future, but I think this is a good start.

It's very rough, and probably very buggy.  I have reverse-engineered the
clone protocol and memory formats by just sniffing the wire, so I'm sure
there are plenty of errors at this point.  However, if you'd like to
give it a try and report back, it would be much appreciated.  If you
have the ICOM-supplied program for your radio, it wouldn't hurt to make
a backup before you play.

It's not much yet, but I feel confident that I can turn it into a
reasonable replacement for the jumble of commercial options available. 
If you're interested, check it out here:

  http://chirp.danplanet.com

I'm posting this here because people have expressed a desire for this 
functionality in this forum.  If you know of other places that would be 
appropriate for an announcement, please let me know.

Thanks!

-- 
Dan Smith
dsmith#danplanet.com, s/#/@/
www.danplanet.com
KK7DS