- Users - lists.chirpmyradio.com

[chirp_users] [CHIRP] #88: saved files are unreadable
by CHIRP Tracker 23 Apr '11

23 Apr '11

#88: saved files are unreadable ------------------------------+--------------------------------------------- Reporter: iz5fsa@… | Type: Bug Status: new | Priority: Stability Milestone: | Component: Import/Export Version: | Keywords: csv chirp img Platform: Linux | ------------------------------+--------------------------------------------- I've created my own csv downloading from radio IC2820. I've also saved file as CHIRP and IMG format. Then I've created a new file to import memories to uplpoad to a ICE80D but when I read again the CSV file it was UNREADBLE!!!! I've re-opened IMG and CHIRP file with the same UREADBLE error! I attach CSV IMG and CHIRP files of the encountered error. I attach also memories.csv that contains memories I want to upload on ICE2820s, ICE92Ds, ICE80Ds and ICE880Ds of our DSTAR GROUP here in Scandicci, Florence... if you can solve the problem. -- Ticket URL: <http://trac.chirp.danplanet.com/trac/ticket/88> CHIRP <http://trac.chirp.danplanet.com/trac> CHIRP Development

1 4

[chirp_users] [CHIRP] #82: Support for Wouxun KG-UV2D
by CHIRP Tracker 23 Apr '11

23 Apr '11

#82: Support for Wouxun KG-UV2D ---------------------------+------------------------------------------------ Reporter: n9dn@… | Type: Feature Status: new | Priority: Would be nice Milestone: | Component: Memory Editor Version: | Keywords: Platform: MacOS | ---------------------------+------------------------------------------------ We just got a Wouxun KG-UV2D and would love to be able to sync to that from our other radios via CHIRP. They're getting a lot of sales, it is a very functional dual band HT for $120. -- Ticket URL: <http://trac.chirp.danplanet.com/trac/ticket/82> CHIRP <http://trac.chirp.danplanet.com/trac> CHIRP Development

2 3

[chirp_users] [CHIRP] #86: Chirp v0.1.11b7-win32 gives 'Entry Point Not Found' dialog
by CHIRP Tracker 23 Apr '11

23 Apr '11

#86: Chirp v0.1.11b7-win32 gives 'Entry Point Not Found' dialog -----------------------+---------------------------------------------------- Reporter: anonymous | Type: Bug Status: new | Priority: Stability Milestone: | Component: Memory Editor Version: | Keywords: Platform: Linux | -----------------------+---------------------------------------------------- Using Chirp v0.1.11b-win32 on WinXP SP3 with KeySpan USA-19QW USB-to- SerialPort, and running chirpw.exe from the unpacked ZIP. Upon start-up of chirp, I am presented the following dialog... TitleBar: chirpw.exe - Entry Point Not Found Message: The procedure entry point libivonv_set_relocation_prefix cound not be located in the dynamic link library iconv.dll. ..three times before the Chirp application window appears. I get the same dialog once more when I click the RADIO menu choice. Windows (software) Data Execution Prevention is enabled. Attached are the system's environment variables list in file 'set.pdf'. The locations that copies of iconv.dll are found is also attached. If you want the System Information printout, ask for it--it is 5.5 Mb as a PDF. 73 de Daniel KB3MUN -- Ticket URL: <http://trac.chirp.danplanet.com/trac/ticket/86> CHIRP <http://trac.chirp.danplanet.com/trac> CHIRP Development

1 9

[chirp_users] Chirp question
by Jay Marcucci 22 Apr '11

22 Apr '11

Hi Quick question - I ran the software against my Wouxun UV2D as well as my Yaesu FT7900. The column marked bank showed up on the Wouxun but not on the Yaesu file. Strange since UV2D doesn¹t do banks and the 7900 does. Also I tried it on the MAC side but terminal window opens and then says it needed a gtx file Not too important as I run it on the Windows side of my iMac Regards, Jay KC2YSK

2 1

[chirp_users] running the chrip_osx.sh script?
by Justin Mann 22 Apr '11

22 Apr '11

Hi there, When run the chirp_osx.sh script in terminal I get permission denied. Is there something that I need to do in mac osx to make this work?

2 2

[chirp_users] OSX and the TH-D72 with CHIRP
by Mark Cohen 22 Apr '11

22 Apr '11

Greetings, I've had an interesting ride with CHIRP so far! I'm glad it's being worked on.. My question is two fold.. 1. Has there been a patch for the TH-D72 2. Does this patch include support for the serial device (cu.SLAB_USBtoUART) that is presented to the OS when the TH-D72 is plugged in? I'd love to not have to use the Kenwood application on Windows if at ALL possible! 73 de K6EF

4 16

[chirp_users] chirp in mac osx?
by Justin Mann 21 Apr '11

21 Apr '11

Hi there, I don't suppose that there is anyway to get chirp to use the actual aqua interface that is native to the mac is there? Unfortunately Voiceover the screen-reader in the mac doesn't work with anything that is using .gtk Thanks,

5 7

[chirp_users] How to load under Linux?
by doc＠kd4e.com 21 Apr '11

21 Apr '11

I was referred to CHIRP from the Kenwood TH-D72 list. What are the dependencies to run CHIRP in Linux, please? I have downloaded and uncompressed CHIRP. I generally use the Fluppy version of Puppy Linux (it's optimized to be full-featured, small, and functional on Netbooks, Notebooks, and desktops). Thanks! -- Thanks! & 73, KD4E David Colburn http://kd4e.com SE-GA Tailgate - April 9th, 2011 Have an http://ultrafidian.com day I don't google I SEARCH! http://ixquick.com Shop Freedom-Friendly http://kd4e.com/of.html

4 7

[chirp_users] Latest version Chirp with Wouxun KG-UVD1P
by John Wilkerson 09 Apr '11

09 Apr '11

From what I can see at this point, the software and radio play well together. It appears previous difficulties have been solved. Thanks Dan! Your software allows me to program ALL my radios now :) Will check out my Icom(s) 2100 and 2200. From what I can see the Wouxun addition is fine :)

2 1

[chirp_users] [CHIRP] #81: Linux RPM may be missing support files
by CHIRP Tracker 09 Apr '11

09 Apr '11

#81: Linux RPM may be missing support files --------------------------+------------------------------------------------- Reporter: n0so@… | Type: Bug Status: new | Priority: Functionality Milestone: | Component: Import/Export Version: | Keywords: Platform: Linux | --------------------------+------------------------------------------------- While attempting to load a previously saved .chirp file for my IC-92AD, the error message "Schema missing" was displayed and the file failed to load. This occurred when running version 0.1.11b4 installed from the yum repository on a Fedora FC14 Linux system. Running from the chirp source directory, the error did not occur and the file was able to be edited, saved and uploaded to the radio. The rpm file in the yum repository is apparently not able to access some of the necessary support files, or the files are missing. As a work around: run chirp from source until another RPM can be uploaded to the yum repository. -- Ticket URL: <http://trac.chirp.danplanet.com/trac/ticket/81> CHIRP <http://trac.chirp.danplanet.com/trac> CHIRP Development

1 2

[chirp_users] CHIRP Windows XP Executable?
by W4ZAU 09 Apr '11

09 Apr '11

My OS is W-XP/SP3. I just downloaded the latest version of Chirp for Windows. Assuming the executable was chirpw.exe I "clicked" on same. I received the error message below. After clicking on OK about three times a window opened up that looked like it might be the application - common drop-downs at the top, etc. However if I clicked on "File" or any of the drop-downs, I got the same error message. Anybody run into this or did I miss a step - though I downloaded and installed twice, just in case? TNX in advance for any suggestions. Dave W4ZAU

2 1

Re: [chirp_users] chirp 0.1.11 and Kenwood TM-V71A
by KE7FJM 05 Apr '11

05 Apr '11

Thanks for the clarification, I understand no how it works and it works great. Bill KE7FJM

2 1

[chirp_users] CHIRP 0.1.11b7
by Dan Smith 05 Apr '11

05 Apr '11

Hi all, I just posted v0.1.11b7 with the following changes: - Add Icom IC-W32A support (Thanks to Daniel for the loan) - Add Icom IC-T70A support (Thanks to John for the loan) - Fix the CSV driver ignoring D-STAR fields. Unless anyone can find a show-stopper bug in this, I'm going to release it as the official 0.1.11, hopefully before next week. If you're an "official tester" for a specific model, please, now is the time to give your "thumbs up" or "thumbs down" on this version's ability to work with your radio. Even if you're not an official tester, feel free to run through these tips and let us know how it works for you: http://chirp.danplanet.com/content/testing-guidelines Thanks! -- Dan Smith www.danplanet.com KK7DS

4 20

[chirp_users] chirp 0.1.11 and Kenwood TM-V71A
by KE7FJM 04 Apr '11

04 Apr '11

Hello, nice to see support for the Kenwood TM-V71A, I downloaded 0.1.11 and tested it on a netbook running Ubuntu (10.10). The download feature worked great, it figured out my radio type and did the right thing. I saw the note live update and save a CSV copy, edited it and when I tried to upload the CSV file to the radio, it detects my COM port just fine, senses a Kenwood radio, but defaults to 'Generic' and does not let me change it. An upload attempt fails complaining about not being able to connect to generic. Is this know? If not I can log this an issue and can also test any updates if you need a TM-V71A tester. Bill KE7FJM

2 1

[chirp_users] TH-F6A Help
by joe camilli 03 Apr '11

03 Apr '11

I have a Kenwood Th-F6A and I am using W7 64 bit. I know for sure the program is communicating with the radio because I can DL the current memories with any problems. I then following these instructions: When done you have to import the file radionew.csv by clicking on Radio --> Import from File. The pop up window requests you to either mark or uncheck the checkbox at the different memory locations or select either all, nothing or inverse and click OK when you want to proceed with the import. Otherwise click at cancel. Save the import save the file as mynewradiodata.img using the File drop down menu. Upload the file to your radio using the Radio --> Upload to Radio Clone function. Enjoy the new settings of your radio! And end up with the following error: Thanks Joe N7QPP

3 6

[chirp_users] RELEASE: 0.1.11
by Dan Smith 30 Mar '11

30 Mar '11

Hi all, I just posted the official version 0.1.11 on the website. Many thanks to all the people that contributed code and loaned radios to support the effort. This release brings almost three times as many supported radios as version 0.1.10 had! The abbreviated list of changes from 0.1.10 is on the download page: http://chirp.danplanet.com/downloads If you are on a mailing list for one of the supported radios or another community that might be interested, be sure to share this link around. More users means more bug reports and then (eventually) fewer bugs :) Thanks! -- Dan Smith www.danplanet.com KK7DS

2 1

[chirp_users] D710 programing: beyond memories.. internal settings
by David Ranch 29 Mar '11

29 Mar '11

Hey Dan, fellow Chip users, I was curious if it would be possible to add the ability to program in extra information into the D710 beyond just memories. Things like the following that's available in the Kenwood MCP-2A program. I personally need the "Data Terminal" menu to set the levels for the external TNC. --David Memory channels Call Channel Weather Channel Program Scan Memory VFO Menu - audio - Transmit / Receive - memory - DTMF - Repeater - Aux - PF key - Band Mask - APRS / Navitra - Sky command II DTMF memory Echolink Memory Data Terminal

2 1

[chirp_users] Help on libiconv DLL issue
by Dan Smith 25 Mar '11

25 Mar '11

Hi all, If you are experiencing the DLL warning message with CHIRP on your Windows box, I need to talk to you to determine why it's happening. If you are seeing this, could you please reply with the following details: 1. The version of CHIRP you're using 2. How you are running it (zip or installer) 3. What version and service pack of Windows you're on 4. What other software you have installed on the system that may also ship that DLL (Pidgin and Gimp come to mind) I just tried CHIRP on a completely fresh install of WinXP (both installer and zip versions). I'm unable to reproduce the issue, so I need some help to get this either resolved or documented before I post 0.1.11 final. Thanks! -- Dan Smith www.danplanet.com KK7DS

1 0

[chirp_users] IC-T70E
by John (Jack) Bramham 24 Mar '11

24 Mar '11

2 1

[chirp_users] Chirp test with Wouxun.
by John Wilkerson 22 Mar '11

22 Mar '11

Will load and and upload fine with no glitches during file transfer. Software shows NFM when downloaded profile is displayed onscreen.... HOWEVER, when re-uploading to radio, the setting STILL shiws wide, as previously programmed. Also, Scan skip is displayed onscreen, yet when sent back to the radio, again, previously programmed settings stick. I reset the radio to factory settings and uploaded. Same situation. Chirp perfectly downloads and uploads file correctly. Editing settings: I changed some settings... BUT.. when uploading them to the radio they did NOT stick. My obervations is that the program at this time can only download a file for observation. Data communication is fine; but for some reason, the program cannot change any info. Program currently cannot load .tw files, so I can't load another profile.

2 6

Re: [chirp_users] CHIRP 0.1.11b7
by Robbie Kieffer 20 Mar '11

20 Mar '11

IC-2200H tested with the 0.1.11.b7 beta...No issues noticed... One item I tried with this beta was attempting to put in punctuation in the alpha (I used 2#$%6 as the test case)...The radio (apparently) won't display them so it didn't try...The data was stored in the radio (cycled power, restarted Chirp, redownloaded the radio data), but the radio just displayed whatever frequency I had put behind that tag. Nothing broke with it though. 73, N0REK Robbie

2 1

[chirp_users] CVS conversion
by IZ5FSA 18 Mar '11

18 Mar '11

Hi Dan, I'm working on my 2820 and I tried to export italian rpeater list into a csv file. I've modified the fields to accomplish to the CSV format readed by chirp but I see that chirpw don't read my cvs... i've saved a native chirp file to a csv and I've imported it again with no success. I think managing CSV files will be a good thing when you have lots of rows to edit. Can you document CSV managemet by chirp or give a chance to use csv for import? 73 de Leo IZ5FSA

2 10

[chirp_users] CHIRP 0.1.11b6
by Dan Smith 10 Mar '11

10 Mar '11

Hi all, I just posted 0.1.11b6 with the following changes: - Added VX8 power level support - Added Keyspan USB serial enumeration on MacOS (Debbie) - Added Wouxun KG-UVD1P support - Added a error reporting framework - Added desktop and man page files (Steve) - Fixed enter key activating OK button on clone dialog - Fixed false notice that all radios are live Feedback on the Wouxun driver would be appreciated. Thanks! -- Dan Smith www.danplanet.com KK7DS

1 0

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

27 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] [CHIRP] #83: exporting to CSV generates a List Error
by CHIRP Tracker 14 Feb '11

14 Feb '11

#83: exporting to CSV generates a List Error ---------------------------+------------------------------------------------ Reporter: n9dn@… | Type: Bug Status: new | Priority: Functionality Milestone: | Component: Import/Export Version: | Keywords: Platform: MacOS | ---------------------------+------------------------------------------------ I tried to export my A bank (IC-92AD) to CSV, and got an error. I tried again from a saved .chirp file, and got the same error (in a pop up diaglog): There was an error during export: 'list' object has no attribute 'InvalidMemoryLocation' and the "Preparing memory list" popup window never goes away. things still seem to work once I close it by hand though. 0.1.11b5 Here's the exception text from the window I ran it in: -- Exception: -- Traceback (most recent call last): File "/Users/fligor/bin/chirp-0.1.11b5/chirpui/editorset.py", line 247, in do_export dst_rthread) File "/Users/fligor/bin/chirp-0.1.11b5/chirpui/editorset.py", line 176, in _do_import_locked dialog = dlgclass(src_radio, dst_rthread.radio, self.parent_window) File "/Users/fligor/bin/chirp-0.1.11b5/chirpui/importdialog.py", line 531, in __init__ self.populate_list() File "/Users/fligor/bin/chirp-0.1.11b5/chirpui/importdialog.py", line 458, in populate_list except errors.InvalidMemoryLocation, e: AttributeError: 'list' object has no attribute 'InvalidMemoryLocation' -- Ticket URL: <http://trac.chirp.danplanet.com/trac/ticket/83> CHIRP <http://trac.chirp.danplanet.com/trac> CHIRP Development

1 1

[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] CHIRP 0.1.11b5
by Dan Smith 11 Feb '11

11 Feb '11

Hi all, I just posted version 0.1.11b5 with the following changes: - Add Icom IC-2720H support - Add Kenwood TM-D710 support - Add Yaesu FT-8800R support - Add Yaesu FT-8900R support - Add Yaesu VX5 support - Add Alinco DR135/235/435 support - Add Jetstream JT220M support - Add power level support (for radios capable of this) - Add a configuration store to remember certain settings - Add support for power levels on VX7 - Add support for power levels on IC2200 - Add support for power levels on VX3 (Rick) - Add command-line slash image manipulation tool (Vernon) - Make CSV import use the header row to determine what order the columns are in and tolerate missing columns - Show an initial warning/info dialog about "live mode radios" - Show actual progress during import/export preparation phase - Fix checksum calculation on VX8 - Fix long-standing erroneous DCS code (Rick) - Fix memory name fetching on Kenwood F6A/D7/D700 - Fix deleting empty locations on Kenwood live radios - Fix caching of empty locations on Kenwood live radios This beta brings a lot of new radio drivers, so please help out with testing and verifying this new functionality if you can. The list of "soon to be supported" radios on the website is longer than the "already supported" one, so we need to make an official drop pretty soon. Please hammer this and file your bugs soon! Thanks to Rick and Vernon for code contributions, Scott, Daron, and Marko for lending radios to be supported, and of course the many people filing bugs and reporting issues! -- Dan Smith www.danplanet.com KK7DS

1 0

[chirp_users] [CHIRP] #77: Want bulk delete or CSV importing of blank channels
by CHIRP Tracker 11 Feb '11

11 Feb '11

#77: Want bulk delete or CSV importing of blank channels ---------------------------+------------------------------------------------ Reporter: n7ss@… | Type: Feature Status: new | Priority: Would be nice Milestone: | Component: Memory Editor Version: 0.1.9 | Keywords: Platform: Windows | ---------------------------+------------------------------------------------ Let's say I have a template with channels 0-199 filled. I want to create a new template with only channels 0-99 in that same radio. How do I get rid of the old channels 100-199? I can delete them individually - time-consuming and complicated if the new template has unused channels in the middle (because the old ones still appear in the blanks). I could do a factory reset on the radio and download the empty radio to use as a starting point for all my templates. That is also complicated for managing multiple radio models that may have other setting I want to retain. I suppose I could directly edit the IMG file and remove the channels I don't want but that invites error. A cleaner solution would be to allow deletion of a range of channels or even import of blank channels via CSV. Thanks! -- Ticket URL: <http://trac.chirp.danplanet.com/trac/ticket/77> CHIRP <http://trac.chirp.danplanet.com/trac> CHIRP Development

1 2

[chirp_users] [CHIRP] #80: Unable to export vx-8r file to csv
by CHIRP Tracker 11 Feb '11

11 Feb '11

#80: Unable to export vx-8r file to csv -------------------------------+-------------------------------------------- Reporter: gdiffey@… | Type: Bug Status: new | Priority: Functionality Milestone: | Component: Import/Export Version: | Keywords: Platform: Linux | -------------------------------+-------------------------------------------- I've successfully downloaded and uploaded from chirp however I'm unable to export to csv format for editing. I suspect the problem is to do with independant offset memory entries. where the uplink and downlink are completely independant. I'm using version 0.1.10 which doesn't appear in the version dropdown list. -- Ticket URL: <http://trac.chirp.danplanet.com/trac/ticket/80> CHIRP <http://trac.chirp.danplanet.com/trac> CHIRP Development

1 5

[chirp_users] [CHIRP] #78: Error on writing to an empty memory slot
by CHIRP Tracker 09 Feb '11

09 Feb '11

#78: Error on writing to an empty memory slot -------------------------------+-------------------------------------------- Reporter: chirp@… | Type: Bug Status: new | Priority: Stability Milestone: | Component: Memory Editor Version: | Keywords: write empty RadioJob KeyError Platform: Linux | -------------------------------+-------------------------------------------- When I was doing some testing (I think I accidentally tried to write to an empty memory slot: -- Exception running RadioJob: 54 -- Exception: -- Traceback (most recent call last): File "/usr/src/archive/Chirp/chirp-0.1.11b4/chirpui/common.py", line 70, in execute result = func(*self.args, **self.kwargs) File "/usr/src/archive/Chirp/chirp-0.1.11b4/chirp/kenwood_live.py", line 174, in erase_memory del self.__memcache[number] KeyError: 54 ------ -- Ticket URL: <http://trac.chirp.danplanet.com/trac/ticket/78> CHIRP <http://trac.chirp.danplanet.com/trac> CHIRP Development

1 1

[chirp_users] [PATCH 1/2] allow flashing by block numbers on THD-72
by Vernon Mauery 07 Feb '11

07 Feb '11

The current thd72.py module already can flash by block numbers based on a dirty block list maintained by the memory editor, but this adds the ability to do the same from the command line. This allows intrepid users to manually (or programatically) modify an image and flash back those individual blocks. This is especially useful for doing things that the gui doesn't do yet, like modifying the startup splash screen. Signed-off-by: Vernon Mauery <vernon(a)mauery.com> --Vernon N7OH

2 3

[chirp_users] TH-D72A setup
by Paul Campbell 07 Feb '11

07 Feb '11

Does Chirp connect via the TH-D72A usb port ? Is there setup information? ( I looked back a couple of months in archives and also looked at beginners guide)

3 2

[chirp_users] Thoughts on TH-F6A support and looking for D710 support
by David Ranch 06 Feb '11

06 Feb '11

Hello Everyone, KI6ZHD here. I just discovered Chirp as I was looking for some way of synchronizing the memories across my F6A, two D710s, and a VX5 in a Linux-only environment. I did some tests and it seems that the Kenwood TH-F6A support is close but it's missing the memory's NAME which is very important to me. I then tried the Kenwood D710 which communicated but didn't support and a Yaesu VX5 didn't work at all. I also noticed I couldn't save any downloaded data nor upload anything back to the radios (see below). The F6A and D710 are the priority radios for me and the VX5 is a backup. Any thoughts on getting the F6A and the D710 working? Taking it a step further, I'm ideally looking for is a memory syncronization tool across different radios. I'm not looking for full backups (though that would be nice like Kenwood's Windows applications) but memories is good enough. Any possibility of coming up with a system that would: - load multiple radio's data at the same time - merge and navigate conflicts (move memories I added in the Car or at Home) and allow me to move them into free slots - come up with a new master file - program them back into each of the radios I know that I could manually do this with Chirp with say CSV files but I think a merging feature like this would be a fantastic. --David Chirp 0.11.b4 Running on Centos 5.5 GTK 2.10.4 PyGTK 2.10.1 Three radios here are tested - Kenwood TH-F6A - Kenwood TM-D710 - Yaesu VX-5 ------------------------------------------- Kenwood TH-F7A ------------------------------------------- Recognizes TH-F6A fine !! does NOT download memory's names !! cannot select File --> Save As !! cannot Radio --> Upload to radio recognition sequence -- [dranch@hampacket chirp-0.1.11b4]$ ./chirpw PC->V71: ID V71->PC: ID TH-F6 PC->D7: ID D7->PC: ID TH-F6 Talking to a TH-F6 PC->D7: AI 0 D7->PC: ? Starting memedit Bank Index supported: False Bank supported: False DTCS Code supported: True DTCS Pol supported: False Mode supported: True Offset supported: True Name supported: True Tune Step supported: True Name supported: True ToneSql supported: True Cross Mode supported: False Started PC->D7: MR 0,000 D7->PC: N PC->D7: MR 0,001 D7->PC: MR 0,001,00145390000,0,2,0,1,0,0,12,08,000,000600000,0,0 PC->D7: MNA MNA 0,001 . . . -- ------------------------------------------- Yaesu VX5 (non-R) ------------------------------------------- Selecting Radio VX3 Program reports 000: 98 80 06 18 78 86 80 60 ....x..` 008: 78 06 00 00 00 00 00 00 x....... Selection of VX3, VX6, and VX7 does not work: VX5 commander (Windows) DOES work for me: http://www.kc8unj.com/vx5.html --> Cancel does NOT work program shows -- Traceback (most recent call last): File "/usr/src/archive/Chirp/chirp-0.1.11b4/chirpui/cloneprog.py", line 58, in <lambda> cancel_b.connect("clicked", lambda b: cancel()) File "/usr/src/archive/Chirp/chirp-0.1.11b4/chirpui/clone.py", line 200, in cancel self.kill(CloneCancelledException) File "/usr/src/archive/Chirp/chirp-0.1.11b4/chirp/chirp_common.py", line 765, in kill import ctypes ImportError: No module named ctypes -- ------------------------------------------- Kenwood D710 ------------------------------------------- PC->V71: ID V71->PC: PC->V71: ID V71->PC: PC->V71: ID V71->PC: ID TM-D710 --- Exception Dialog: Unsupported model `TM-D710' --- Traceback (most recent call last): File "/usr/src/archive/Chirp/chirp-0.1.11b4/chirpui/clone.py", line 153, in run cs.radio_class = detect.DETECT_FUNCTIONS[vendor](cs.port) File "/usr/src/archive/Chirp/chirp-0.1.11b4/chirp/detect.py", line 117, in detect_kenwoodlive_radio raise errors.RadioError("Unsupported model `%s'" % r_id) RadioError: Unsupported model `TM-D710' ----------------------------

3 13

[chirp_users] [CHIRP] #79: Memory merging and conflict resolution
by CHIRP Tracker 06 Feb '11

06 Feb '11

#79: Memory merging and conflict resolution -------------------------------+-------------------------------------------- Reporter: chirp@… | Type: Feature Status: new | Priority: Functionality Milestone: | Component: Memory Editor Version: | Keywords: Platform: Linux | -------------------------------+-------------------------------------------- I've been looking for a Linux tool that could syncronize my various radios's memories while keeping some data unique. I realize that I can do this manually with CSV files but having this in Chirp would be fantastic. Some ideas for the UI could include: - When a radio's data is downloaded, load it's data into the table but have say the first column naming which radio it came from - When the next radio's data is downloaded, merge that into the table. If a given row is identical from both radios, change the 1st row cell's name to reflect both radios - If a given row (memory slot) are different (conflict), add an additional row reflecting the 2nd radio's name, it's data, and maybe put it in a different color - alternatively, maybe these radios have a unique ID like a serial number, user setable name, etc. so use that - offer a pulldown for this conflict row and ideally REMEMBER this decision (maybe this remembering would be more troublesome than what it's worth): - override the master row - move to memory slot: ### (drag and drop would be slick but that might be hard in Python) - keep unique to this radio - delete The reason for the "keep unique to this radio" would be say on my two D710s, one has an APRS SSID of "KI6ZHD" and another that has "KI6ZHD-9". If I could use this tool to merge data while keeping some settings unique would be ideal. -- Ticket URL: <http://trac.chirp.danplanet.com/trac/ticket/79> CHIRP <http://trac.chirp.danplanet.com/trac> CHIRP Development

1 0

[chirp_users] CHIRP 0.1.11b4
by Dan Smith 05 Feb '11

05 Feb '11

Hi all, I just posted CHIRP 0.1.11b4 with a bunch of changes. This posting includes contributions from Vernon Mauery, Richard Farina, as well as myself. If support for the VX-3R or TH-D72 interests you, be sure to thank these guys :) Changes are: - Fix IC9x detection and baud rate selection - Fix IC9x crashing the whole application - Fix VX-6 not reporting valid tone modes - Fix VX-7 tone field (Richard) - Changes to the status bar text (Richard) - Improved checksum calculation and validation on Yaesu radios - Default VX-7 memory power levels to high (Richard) - Silence the "this will take a long time" warning on file-based radios - Add Kenwood TH-F6A support - Add Kenwood TH-D72 support (Vernon) - Add ICOM IC-2100H support - Add Yaesu VX-3R support (Richard) Like always, I'll be looking for testing and validation of the new drivers listed above, as well, as reports from our model-assigned testers. As a reminder, get the latest beta here: http://chirp.danplanet.com/download/beta Thanks! -- Dan Smith www.danplanet.com KK7DS

5 6

[chirp_users] [PATCH 2/2] add THD-72 splash image manipulation tool
by Vernon Mauery 05 Feb '11

05 Feb '11

This adds a command-line based slash image manipulation tool for the THD-72. It takes as inputs an image file and a NVRAM image and mashes them together so you can upload the modified portions back to the radio and change the two splash screens. This is a useful tool to have until we can come up with a way to integrate this in the GUI. Signed-off-by: Vernon Mauery <vernon(a)mauery.com> --Vernon N7OH

1 0

[chirp_users] [CHIRP] #75: Import poblem between 880H and VX-7R
by CHIRP Tracker 01 Feb '11

01 Feb '11

#75: Import poblem between 880H and VX-7R -----------------------------------+---------------------------------------- Reporter: KN0N@… | Type: Bug Status: new | Priority: Functionality Milestone: | Component: Import/Export Version: | Keywords: Platform: Linux | -----------------------------------+---------------------------------------- 0.1.11.b4 is working very well. I have been running edits and transfers with little issue. I am puzzled why, when editing my 880 image and importing from the VX7 image, some of the 880 memory lines are grayed out. They should be valid and importable. Going the other direction (from 880 file to VX7) Everything looks good, and the D-STAR stuff is the only thing that is (properly)gray. I am attaching my 880 and VX-7 images. Thanks Dan! -- Ticket URL: <http://trac.chirp.danplanet.com/trac/ticket/75> CHIRP <http://trac.chirp.danplanet.com/trac> CHIRP Development

1 7

[chirp_users] [CHIRP] #71: CSV Format Mismatch with DV code
by CHIRP Tracker 31 Jan '11

31 Jan '11

#71: CSV Format Mismatch with DV code ---------------------------+------------------------------------------------ Reporter: kk7ds | Owner: Type: Bug | Status: new Priority: Stability | Milestone: Component: Import/Export | Version: Keywords: | Platform: Linux ---------------------------+------------------------------------------------ The CSV header does not include the "code squelch" header for DV mode, and chokes if the (appropriate) trailing comma is included -- Ticket URL: <http://trac.chirp.danplanet.com/trac/ticket/71> CHIRP <http://trac.chirp.danplanet.com/trac> CHIRP Development

1 3

[chirp_users] [CHIRP] #76: Populate blank fields during CSV import
by CHIRP Tracker 31 Jan '11

31 Jan '11

#76: Populate blank fields during CSV import ---------------------+------------------------------------------------------ Reporter: N7SS | Type: Feature Status: new | Priority: Stability Milestone: | Component: Import/Export Version: | Keywords: Platform: Windows | ---------------------+------------------------------------------------------ I have a master spreadsheet I use as a template. I prefer to leave unused fields blank because it's easier to spot errors. This complicates bringing CSV data into Chirp because it allows only some fields to be blank (name, tone mode, duplex, skip, bank, urcall, rtptcall, rpt2call, digital code). Other fields like Tone, ToneSQL, DTCS Code, DTCS Pol, Offset, Tune Step and Bank Index are not always used and could be defaulted to some value if not specified. That would make imports a bit easier. Thanks! -- Ticket URL: <http://trac.chirp.danplanet.com/trac/ticket/76> CHIRP <http://trac.chirp.danplanet.com/trac> CHIRP Development

1 2

[chirp_users] [CHIRP] #74: TSQL and Duplex save setting
by CHIRP Tracker 24 Jan '11

24 Jan '11

#74: TSQL and Duplex save setting ----------------------------------+----------------------------------------- Reporter: TheSndGy@… | Type: Bug Status: new | Priority: Functionality Milestone: | Component: Memory Editor Version: | Keywords: Platform: Windows | ----------------------------------+----------------------------------------- When setting a tone mode of TSQL but leaving Duplex as "None", the file will not save properly; upon opening, the value is set to "-". IC-2820 -- Ticket URL: <http://trac.chirp.danplanet.com/trac/ticket/74> CHIRP <http://trac.chirp.danplanet.com/trac> CHIRP Development

1 3

Re: [chirp_users] Kenwood TH-D72 and Linux
by Vernon Mauery 03 Jan '11

03 Jan '11

On Thu, Dec 16, 2010 at 8:53 AM, Dan Smith <dsmith(a)danplanet.com> wrote: > Hey Vernon, > > Wow, super-awesome. Thanks a bunch :) > >> In the process of trying to understand the radio, I found that I can >> do partial reads and writes. This opens up a lot in the way of faster >> syncing with the radio. I am hoping to find a way to mark blocks of >> the mmap as 'dirty' and only flush those dirty blocks out to the >> radio. > > Hmm, okay, well, that would be pretty different than how most of the > other stuff works. Perhaps you need to model it more as a LiveRadio > than a mmap-ed one. The UI changes behavior in some areas depending on > whether it thinks the radio is live or not (like warning the user about > long-running operations). Well, for now I am just going to leave it as a clone radio. >> In addition, the windows MCP-4A program offers a lot more than just >> editing the memories. I would like to be able to modify some of the >> other behaviors on the radio from the GUI as well. But I am not sure >> UI-wise the best way to go at this. A new tab or a new popup window >> or something. This is still a ways out since I am still trying to >> figure out memory offsets and data formats for all the settings. > > Yeah, so, the thing is: all radios have memories, and they're all fairly > similar. The problem comes when you have a ton of other little > radio-specific things to change that it becomes harder to make the tool > universal. > > I'm definitely not opposed to this, but I think we need to do some > thinking on how best to model it internally. The UI already has > multiple tabs on some of the radios (like the D-STAR radios, for setting > callsigns and stuff). It shouldn't be too hard to do the same for > specific radio features. I agree that some discussion needs to take place. That is one reason I didn't just jump right in. The other is that I don't have much in the way of pygtk know-how. > Maybe we should come up with a subset of non-memory things we want to > support for all radios first? Things like display color, power-off > time, etc? I'm not sure how far down the rabbit hole you want to go :) 1) Compile a list of all the options all the supported radios have 2) Find the subset of common options 3) Come up with a nice UI for that. I think that steps one and two are the ones that will take the most work. >> +CROSS_CODES = [ >> + "DCS->Off", >> + "Tone->DCS", >> + "DCS->CTCSS", >> + "Tone->CTCSS", >> +] > > Hmm, would you consider splitting (or letting me split) the patch into > one for the D72 and one for the "cross code" thing? This version has that split out. > Am I correct in saying that this lets you transmit DCS but receive Tone, > or something like that? Does the MCP call it "cross code"? The MCP interface has a choice of which method to use (Tone/CTCSS/DCS/Cross) and then if Cross is selected, the "Tx Cross Tone" and "Rx Cross Tone" fields are enabled. The manual calls it Cross Mode, so that is what I have altered it to be. >> +# memory channel >> +# 0 1 2 3 4 5 6 7 8 9 a b c d e f >> +# [freq ] ? mode tmode rtone ctone dtcs cmode [offset] ? >> +POS_MODE = 5 >> +POS_DUP = 6 >> +POS_TMODE = 6 >> +POS_RTONE = 7 >> +POS_CTONE = 8 >> +POS_DTCS = 9 >> +POS_CMODE = 10 >> +POS_OFFSET = 11 >> + >> +MEM_LOC_BASE = 0x1500 >> +MEM_LOC_SIZE = 16 >> +MEM_TAG_BASE = 0x5e00 >> +MEM_FLG_BASE = 0x0C00 > > So, you may hate me for this, but I think you might want to take a look > at some of the other radios that I've been porting to a new way of doing > things. > > Look, for example, at the vx8.py driver. I've defined a little > mini-language that lets you define things like you did in the comment > block above, but in a way that lets the code automate a bunch for you. > I haven't converted the V71 driver because I don't own one and don't > want to port it to the new model until I have one handy to test with. > > Anyway, I definitely think it's the "way forward" with this stuff, and > makes the code much smaller and simpler. Not that I wouldn't take the > patch as it is, but at least take a look first and let me know what you > think. I took a look at the vx8 driver and modified the thd72 driver to work with the bitwise parser. It took some time, but since this was the first day of my end-of-the-year holiday, I didn't have anything else to do. It worked out nicely. I used hg record to break apart my changes and then used hg export to create the patch. Is this the preferred method of submission or should I do something else next time? I have never used hg before, so I am breaking new ground all over the place with this project. --Vernon > Otherwise, thanks a ton for doing this work! > > -- > Dan Smith > www.danplanet.com > KK7DS >

2 2

[chirp_users] chirp RPMs for Fedora FC13 and FC14 Available
by Mike Heitmann 03 Dec '10

03 Dec '10

All, If you are running chirp on Fedora Linux, rpm packages are now available in the the d-rats yum repository. (Also known now as the KK7DS-Ham-Apps Software Repository). To set it up, please look at the instructions: http://www.d-rats.com/component/content/article/30-d-rats-yum-repository/ or just install the repository definition rpm by running: rpm --install http://d-rats.com/yum/f11/d-rats-repo-0.1.3-1.fc12.noarch.rpm as root. There are two repositories: KK7DS Ham Apps Software KK7DS Ham Apps Beta Software The chirp beta versions are in the "Beta Software" repository, which is disabled by default. To enable it, go to: System->Administration->Software Sources and check the box next to it. Please note: there are two rpms for each version: one for FC13 (which used python version 2.6) and one for FC14 (the latest Fedora version, which used python 2.7). Please pick the one that matches your system. 73, and enjoy! Mike, N0SO

1 0

[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 16 Nov '10

16 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 09 Nov '10

09 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

[chirp_users] ICF Importation
by IT2 Stuart Blake Tener, USNR 03 Nov '10

03 Nov '10

ALCON, Indeed it is worthy of notation that the ability to provision a capability for the importation of ICF files is a very welcome addition. Will CHIRP be able to write out, for export, ICF files in addition? -- IT2 Stuart Blake Tener, USNR, N3GWG (Extra), MROP Beverly Hills, CA / Las Vegas, NV / Philadelphia, PA / Washington, DC mobile: (310) 358-0202 Nextel: 124*233172*14 (direct connect) e-mail: teners(a)bh90210.net

2 1

[chirp_users] Vx7 having the upload problem form Tom@K3WS.com
by tom＠k3ws.com 02 Nov '10

02 Nov '10

communications error / invalid character “0A” should have been NACK/ACK try again. Still having the upload problem. I enabled the mods settings in vx7 commander software no joy there either. when trying to upload with the rt systems software the error that pops up is as follows ( communications error / invalid character “0A” should have been NACK/ACK try again. Please send any feedback on how to fix this to tom(a)k3ws.com 73's all. 73's from Tom K3WS node # 377671 & K3WS.com Echolink# K3WS-L 377672 & K3WS-R 377673 Echolink now on iPhone echolink.org Host of HF Remote Stations MD and PA K3WS Repeater 147.060+ PL 167.9 Cambria County ARES EC Sent from K3WS BlackBerry by AT&T -----Original Message----- From: chirp_users-request(a)intrepid.danplanet.com Sender: chirp_users-bounces(a)intrepid.danplanet.com Date: Tue, 02 Nov 2010 12:00:01 To: <chirp_users(a)intrepid.danplanet.com> Reply-To: chirp_users(a)intrepid.danplanet.com Subject: chirp_users Digest, Vol 23, Issue 1 Send chirp_users mailing list submissions to chirp_users(a)intrepid.danplanet.com To subscribe or unsubscribe via the World Wide Web, visit http://intrepid.danplanet.com/mailman/listinfo/chirp_users or, via email, send a message with subject or body 'help' to chirp_users-request(a)intrepid.danplanet.com You can reach the person managing the list at chirp_users-owner(a)intrepid.danplanet.com When replying, please edit your Subject line so it is more specific than "Re: Contents of chirp_users digest..." Today's Topics: 1. Re: [CHIRP] #69: Cannot import an IC-92AD ICF file (Gary Bechtold) 2. Re: [CHIRP] #69: Cannot import an IC-92AD ICF file (Dan Smith) ---------------------------------------------------------------------- Message: 1 Date: Tue, 2 Nov 2010 09:37:07 -0700 From: Gary Bechtold <ki4vlh(a)gmail.com> Subject: Re: [chirp_users] [CHIRP] #69: Cannot import an IC-92AD ICF file To: donotreply(a)danplanet.com, Discussion of CHIRP <chirp_users(a)intrepid.danplanet.com> Message-ID: <AANLkTi=4E_UrmpVhLAj2-bQjeBF8hdhHKG9V1tqMA22v(a)mail.gmail.com> Content-Type: text/plain; charset="windows-1252" I to will be glad to wait for this little/big fix, Gary KI4VLH On Wed, Oct 27, 2010 at 6:42 AM, CHIRP Tracker <donotreply(a)danplanet.com>wrote: > #69: Cannot import an IC-92AD ICF file > -------------------------------------+-------------------------------------- > Reporter: W1GRI@? | Owner: kk7ds > Type: Bug | Status: accepted > Priority: Functionality | Milestone: > Component: Memory Editor | Version: > Resolution: | Keywords: > Platform: Windows | > > -------------------------------------+-------------------------------------- > Changes (by kk7ds): > > * owner: => kk7ds > * status: new => accepted > > > Comment: > > This is a well-known limitation because the ICF files for 91/92 radios are > completely different than the others. I do, however, have some code from > AE7Q to use to add this support. I will leave this open until I get it > added. > > -- > Ticket URL: <http://trac.chirp.danplanet.com/trac/ticket/69#comment:1> > CHIRP <http://trac.chirp.danplanet.com/trac> > CHIRP Development > _______________________________________________ > chirp_users mailing list > chirp_users(a)intrepid.danplanet.com > http://intrepid.danplanet.com/mailman/listinfo/chirp_users > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20101102/c7… ------------------------------ Message: 2 Date: Tue, 02 Nov 2010 09:39:55 -0700 From: Dan Smith <dsmith(a)danplanet.com> Subject: Re: [chirp_users] [CHIRP] #69: Cannot import an IC-92AD ICF file To: Discussion of CHIRP <chirp_users(a)intrepid.danplanet.com> Message-ID: <4CD03EDB.6080007(a)danplanet.com> Content-Type: text/plain; charset=windows-1252; format=flowed > I to will be glad to wait for this little/big fix, Gary KI4VLH Thanks. I've actually finished adding it to the code and made a lot of progress towards simplifying the process of using ICF files with CHIRP. You can now import directly from an ICF instead of converting it first, which unifies the path for all types of those files. That will be available in the next beta, which hopefully won't be too far off. Stay tuned! -- Dan Smith www.danplanet.com KK7DS ------------------------------ _______________________________________________ chirp_users mailing list chirp_users(a)intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users End of chirp_users Digest, Vol 23, Issue 1 ******************************************

2 1