I like it! I appreciate the step-by-step copy/paste workflow, but it might also be useful to show the stock_config workflow:

0. Start Chirp 1. Download from Radio 2. Export to CSV in stock_config directory.

0. Start Chirp 1. Open stock config 2. Download from Radio 3. Copy from stock config to radio 4. If clone mode radio, upload to radio

IMHO this is the best workflow for managing a large number of radios with Chirp, and I would like to get people in the habit of doing it this way (or at least know it's possible).

Tom KD7LXL

On Thu, Mar 28, 2013 at 2:22 PM, Marco IZ3GME iz3gme.marco@gmail.com wrote:

Hi Shawn yes I did the presentation last friday, it have been very appreciated.

The link to the slides is

https://docs.google.com/presentation/d/1K4MDTZ2O4uV4kw10l3WukY_hrjr7kCAebdHX...

I suggest you to also look at the speaker notes where I put some suggestions to myself ;)

Hope you like it and, please, should you find any error please let me know.

73 de IZ3GME Marco

On 28/03/2013 20:51, shawn wrote:

...

Did you ever give that presentation that you were preparing for?

if so, can you share? I've been asked to give a similar talk about chirp at my local club.

---

chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers

Well, as I posted in the "issues" system, the CI-V testing tools were useful in figuring out how to access banks B-E (hexadecimal):

E0 70 1A 00 0x 00 yy

Where "x" is the bank number, and "yy" (packed decimal) is the memory location.

That's the good news. The bad news is that I found a package called RumTool7000 (Windows, Linux, Mac) that works (and supports the five banks) seamlessly for me (has very good .CSV file import/export), so my need to spend significant development effort on this issue is near zero.

That having been said, just like with the my effort on the ID-51 (where I also had a good alternate software solution), I would be glad to assist in testing any work done on this issue. It's just that there are Chirp architectural issues (support multiple banks with multiple tabs ???) that need to be decided/coded by someone other than me. Given that the existing Chirp code already supports one bank, I'd think the need for any further radio investigation would be near zero.

------------

By the way, I connect to the serial ports of all my radios (Icom and Yaesu) not via a serial cable from my PC, but via Ethernet to a remote Digi (www.digi.com) "PortServer TS4" 4-port Ethernet-to-serial converter (there are 1, 2, 4, and 8 port versions). In my case the network connection is local, but there is no reason that the connection cannot be via the Internet. Digi provides free software that works on 7 variants of Windows (32 and 64 bit) and over 50 variants of Linux.

For Windows, it's a clean driver install and configuration; for Linux, you build the daemon from the source. I had trepidation about the latter, but it built and installed with just two "RPM" commands (I think it's five commands if you download the tarball package), and configuration was trivial. Chirp, RumTool7000, HamRadioDeluxe, all the Icom software, and even the above CI-V testing tool works across the network.

This would be a very useful tool for you to have for remote testing. I obtained two of them (plus a similar Digi Ethernet-to-USB converter) on eBay for about $50 each. Mine are used regularly, and are not for loan.

So, while I don't think this project needs a remote developer to access my IC-7000, if necessary, I could "port-forward" such remote access to the PortServer if needed. Actually, it would be an interesting thing to try.

Sincerely, Dean

----------------

ps: Most of my access to my radios is on Windows 7 (64-bit), but for my Icom ID-880H radios at my home, I wanted several radio features that required GPS data to be sent to the radio:

1. The radio's internal log of transmissions received, now get timestamps. 2. The radio displays the time. 3. The radio is able to transmit its "GPS" location to other D-Star radios, and they can capture my location and display the distance and direction to me. 4. Similarly, my ID-880H radios can capture the GPS locations of other radios and display the distance and direction to them.

So, I wrote a 4-line bash script and an absolutely trivial NMEA checksum program, and a Linux CRON job sends NMEA data to the radios once a minute. This low serial bandwidth overhead allows other programs on my Windows box to easily capture the serial port when needed.

On 2013-03-30 13:03, Dan Smith wrote:

...

Well, as I posted in the "issues" system, the CI-V testing tools were useful in figuring out how to access banks B-E (hexadecimal):

E0 70 1A 00 0x 00 yy

Where "x" is the bank number, and "yy" (packed decimal) is the memory location.

Cool, easy. I can do this.

I should have made clear two things:

1. "x" as the bank number, is numbered from "1" (for bank "A") to "5" (for bank "E") 2. I showed "yy" as the memory location. In fact, it is "0y yy", with locations 100 and above (eg, can limits, calling channels) common to all banks.

-- Dean