November 2010 - Users - lists.chirpmyradio.com

[chirp_users] [CHIRP] #59: instructions
by CHIRP Tracker 30 Apr '11

30 Apr '11

#59: instructions ---------------------------+------------------------------------------------ Reporter: n4cz@… | Type: Task Status: new | Priority: Functionality Milestone: | Component: Import/Export Version: | Keywords: Platform: Windows | ---------------------------+------------------------------------------------ I just discovered CHIRP and would like to use it for re-ordering the memory locations for a 2820, 91AD, and 92AD. But I must not be using it correctly: 1. I cannot download/upload to the 2820 without changing the memory contents as shown by comparing icf files captured by the CS-2820 program. 2. I cannot read into CHIRP a csv file opened in Excel 2003 and re-saved - the save does not preserve all of the original characters. 3. I cannot see the memory contents when connecting to the 91AD. Exactly what procedure should I be using to do these? -- Ticket URL: <http://trac.chirp.danplanet.com/trac/ticket/59> CHIRP <http://trac.chirp.danplanet.com/trac> CHIRP Development

1 2

[chirp_users] [CHIRP] #70: Would like to have bank field populated in csv export
by CHIRP Tracker 23 Apr '11

23 Apr '11

#70: Would like to have bank field populated in csv export ------------------------------------+--------------------------------------- Reporter: W1GRI@… | Type: Feature Status: new | Priority: Functionality Milestone: | Component: Memory Editor Version: | Keywords: Platform: Windows | ------------------------------------+--------------------------------------- Playing with CHIRP again - last summer the IC-92Ad stuff didn't seem to work, but I'm trying again. ID-880 seems to work. I'm really happy to see that you handle bank & bank index in chirp. Organizing banks is a major pain for me. I was really excited to see the values shown in the chirp screen. But, no joy when I export to a csv file. Seems that the bank values are always empty. I would really love to see the bank id displayed (any form, letter or an index number would be great). I have written some programs in visual foxpro that allow me to make groups pretty easily, but the only way to get them into the radio is to import from a csv file via the Icom software. (With the 92ad this means selecting each bank and doing an import of a csv for that bank) Is there any way you can populate the bank field in the csv file AND, most importantly, allow it to be imported back after changes. Then I could build a customized csv file for each situation and load the whole radio in one step. Thanks for considering this request. -- Ticket URL: <http://trac.chirp.danplanet.com/trac/ticket/70> CHIRP <http://trac.chirp.danplanet.com/trac> CHIRP Development

1 2

[chirp_users] [CHIRP] #61: software does not work with vx-8 after upgrade
by CHIRP Tracker 26 Feb '11

26 Feb '11

#61: software does not work with vx-8 after upgrade --------------------------------+------------------------------------------- Reporter: havmedic26@… | Type: Bug Status: new | Priority: Functionality Milestone: | Component: Import/Export Version: | Keywords: Platform: Windows | --------------------------------+------------------------------------------- Hi! I am writing to tell you that I am having problems with the vx-8 software, and to ask if you have a solution that could help me. I originally had a us version vx-8. It worked fine with your software. your software The vx-8 was then modded. It still worked great with your software. Then I sent it out to yesea to be up graded. When i got it back it did not work with your software. I re-modded it with still no luck. I can not even read the radio. The Message I get it the radio identifier expected was X'4148303239' but the identifier actually recieved was X'4148323944' -- Ticket URL: <http://trac.chirp.danplanet.com/trac/ticket/61> CHIRP <http://trac.chirp.danplanet.com/trac> CHIRP Development

1 5

[chirp_users] more help with Mac OS
by Debbie Fligor 11 Feb '11

11 Feb '11

I'm sure that you're busy with d-rats and getting ready for Dayton, but I finally got back to working on getting Chirp working now that I have a need to move data from an ic-92 to an ic-91 :-) I snagged the source to 0.1.9 final and tried it both with my fink install and my darwin ports install. neither works, but they do both fail with the exact same error when I pick "Radio -> connect to an ic9x": a.show() Traceback (most recent call last): File "/Users/fligor/bin/chirp-0.1.9/chirpui/mainapp.py", line 430, in mh self.do_open9x(ic9x.IC9xRadioA) File "/Users/fligor/bin/chirp-0.1.9/chirpui/mainapp.py", line 123, in do_open9x rtype="ic9x") File "/Users/fligor/bin/chirp-0.1.9/chirpui/clone.py", line 70, in __init__ self.port = miscwidgets.make_choice(ports, True, ports[0]) IndexError: list index out of range I never get the dialog box that lets you choose your radio settings. I tried A B and B B, neither worked, and I did make sure the radio's main was on the "B" side. I even get the same message with the Apple's built in python using export PYTHONPATH=/opt/local/lib/python2.5/site-packages which worked for another user. It's good that they all fail the same way, it's annoying that they all fail :-) You'd previously thought you knew what this was and had planned on fixing it, I just got side tracked and never checked. Something about not knowing about a serial port and getting confused. as a work around, is there a config file I can stash somewhere that fills it in about the serial port to get me going? I couldn't find anything on the config file format at the wiki so that I could just make my own. Let me know if you also want to see this on trac as well. thanks, -debbie, N9DN

2 16

[chirp_users] Testing Guidelines
by Dan Smith 30 Nov '10

30 Nov '10

Hi all, Thanks to those who have volunteered to be testers. There are still a bunch of unfilled spots on the list, so please let me know if you're interested in "owning" the testing of one of the drivers: http://chirp.danplanet.com/content/chirp-qa In order to help make the process more consistent, I have put together a page of guidelines and procedures. Included on this page is some general overview information about how CHIRP works and some bug-like behavior to look for specifically. It also has some suggestions for things to try to verify that CHIRP is operating properly for the radio model you're testing. If you are signed up to test a specific model, or are thinking about doing so, please take a look at the following page: http://chirp.danplanet.com/content/testing-guidelines It would be great if the people assigned to specific drivers could go through that document and give me a "thumbs up" or "thumbs down" report on the currently-available beta version. This will get us rolling a bit, and I'm sure will uncover some issues. Thanks! -- Dan Smith www.danplanet.com KK7DS

1 0

[chirp_users] Looking for help testing specific radios...
by Dan Smith 28 Nov '10

28 Nov '10

Hi all, I would like to propose the idea of a formal list of radio testers, to help ensure that future releases of CHIRP go out without significant model-specific regressions. What I would like is one or two volunteers per radio to test beta versions in a timely manner. This would mean that when I post a beta version (or especially right before a regular release), you would test the latest with your assigned radio to make sure that it functions as expected. We could get a "tester's plan" developed with specific things to test each time to make it consistent and meaningful. I would expect a "thumbs up or down" response within, say, a week of posting a new beta version. In return, you would have my (and others') gratitude, a mention on the website as being responsible for "QA" of your model, and hopefully a better tool in the long run as a result. I can't personally purchase and own every model that CHIRP supports. As the list grows, it becomes harder and harder to make changes without knowing if obscure models are being negatively affected. So, any volunteers? Please reply and let me know which radio you'd be willing to help test and I'll get a list started on the website. Thanks! -- Dan Smith www.danplanet.com KK7DS

3 5

[chirp_users] CHIRP 0.1.11b3 (with lots of changes)
by Dan Smith 15 Nov '10

15 Nov '10

Hi all, I just posted 0.1.11b3 with a fairly extensive set of changes. In addition to support for a few new radios, this beta release has a lot of usability and stability fixes. If you haven't tried CHIRP in a while, take a look. If you're good at breaking things, help me out by pointing to what you find. Support for new models: - Add ICOM IC-Q7A support - Add ICOM CI-V radio support and preliminary IC-7200 driver - Hopefully at least IC-7000, IC-706 support coming soon - Add Yaesu FT-7900 support Usability enhancements: - Performance improvements in the memory editor - Import dialog improvements: - Color collisions in yellow - Color invalid locations in red - Grey-out memories that can't be imported into the current model - Better error handling and reporting - Allow multi-select in the memory editor (and thus multi-delete) - Add Edit menu with Cut/Copy/Paste and overwrite notification - Hide more columns when not supported by a given model - Offer radio's supported modes and tone modes in UI - Improve per-radio validation of input Stability/Fixes: - Fix memory editor not actually saving single changes to a memory in some cases - Fix exposing some internal-use column names in View->Columns - Fix open/import of CSV files - Port IC-2200 module to new driver model - Port VX-7 module to new driver model - Port FT-7800 module to new driver model - Fix a 2820 bug after download - Fix VX-8 checksum calculation There are a lot of new features being added here and I want to get them out to "regular users" in a formal release soon. I'd really appreciate some testing of this stuff, even if you report back with what you've done and that "it worked". Thanks! -- Dan Smith www.danplanet.com KK7DS

1 0

[chirp_users] CHIRP 0.1.11b2
by Dan Smith 08 Nov '10

08 Nov '10

Hi all, I just posted 0.1.11b2. I'd like to thank Ben Smith and Richard Farina for their contributions as part of this round of changes. They're working on VX7 and VX8 enhancements and I'm very happy to have them helping out. The changes this time are: - Catch and report errors when failing to save [Ben] - Remove faulty FT-50R clone support for the time being - Add support for opening, importing, and saving to VX7Commander files [Rick] - Allow canceling a clone in progress - Add odd-split support for the Yaesu radios [Rick] - Allow importing from IC9x .ICF files - Allow opening .ICF files directly (read-only) - Add a warning pop-up if you try to "convert" an IC9x .ICF file - Fix ID880 callsign lists and DV callsign editing per-location - Add a new common data parsing base (currently used by vx8, id880, ic2820 drivers) I would very much appreciate some testing of the new IC9x .ICF file functions from those that asked for it. Also, the vx8, id880, and ic2820 are now using a new method for accessing the memory map that should help reduce the potential for errors and clean up the code a lot. Since this is the first release with that subsystem, there are likely to be some issues. If you have one of these radios, please exercise this version in those areas and report any issues you may encounter. Thanks! -- Dan Smith www.danplanet.com KK7DS

1 1

[chirp_users] [CHIRP] #64: Repeater and Mycall corruption in 880 file
by CHIRP Tracker 08 Nov '10

08 Nov '10

#64: Repeater and Mycall corruption in 880 file -----------------------------------+---------------------------------------- Reporter: kn0n@… | Type: Bug Status: new | Priority: Functionality Milestone: 0.1.10b2 | Component: Callsign Editor Version: | Keywords: Platform: Windows | -----------------------------------+---------------------------------------- Sorry it took me so long to get back to testing. There is corruption in the Repeater Callsign and My Callsign fields on the D-STAR tab. Occurs with both radio dump and icf conversion of an 880 radio/file. Perhaps a counting error or missed field separator, as in some cases the last character is pushed to the beginning of the following field. Also if you scroll way down the Repeater Callsign column you will see a lot of gibberish. The Callsign field looks fine. Chirp 0.1.11b1 -- Ticket URL: <http://trac.chirp.danplanet.com/trac/ticket/64> CHIRP <http://trac.chirp.danplanet.com/trac> CHIRP Development

1 2

[chirp_users] [CHIRP] #69: Cannot import an IC-92AD ICF file
by CHIRP Tracker 07 Nov '10

07 Nov '10

#69: Cannot import an IC-92AD ICF file ------------------------------------+--------------------------------------- Reporter: W1GRI@… | Type: Bug Status: new | Priority: Functionality Milestone: | Component: Memory Editor Version: | Keywords: Platform: Windows | ------------------------------------+--------------------------------------- Get unsupported model error when converting a 92AD icf file. Version is 0.1.10 -- Ticket URL: <http://trac.chirp.danplanet.com/trac/ticket/69> CHIRP <http://trac.chirp.danplanet.com/trac> CHIRP Development

3 4