- Users - lists.chirpmyradio.com

[chirp_users] chirp-0.1.9b12.tar.gz on CentOS 5.3
by Adrian 10 May '09

10 May '09

>/ Had to build chirp-0.1.9b12.tar.gz, as with Fedora 10 a few days />/ ago, as the ¨reposted¨beta tar doesn't seem to have made any />/ difference. / >I didn't repost the beta, I reposted the official 0.1.9 release. >Download it from the main directory, not the beta/ section. I believe >that Leo confirmed that it was correct now. Ok sorry I missed that. Of course that worked fine on both fedora 10 and CentOS. That teaches me for not reading all of the previous posts. Good luck in Dayton, will be checking out the wa5kub webcam imbedded in my site; http://vk4tux.no-ip.org vk4tux

2 1

[chirp_users] chirp-0.1.9b12.tar.gz on CentOS 5.3
by Adrian 10 May '09

10 May '09

Still using CentOS 5.3 on Main box here and fedora 10 on laptop (as the kernel supports wireless rf broadband usb cdma cmotech modems now for internet). Had to build chirp-0.1.9b12.tar.gz, as with Fedora 10 a few days ago, as the ¨reposted¨beta tar doesn't seem to have made any difference. Create tools folder in /tmp/chirp-0.1.9b12/chirp-0.1.9b12 (as doesn't exist after extract) Download 3 raw (left menu link) files [up] <http://www.d-rats.com/hg/hgwebdir.cgi/chirp.hg/file/c89c1ab4052b/> drwxr-xr-x file Makefile <http://www.d-rats.com/hg/hgwebdir.cgi/chirp.hg/file/c89c1ab4052b/tools/Make…> 843 -rw-r--r-- file icomsio.sh <http://www.d-rats.com/hg/hgwebdir.cgi/chirp.hg/file/c89c1ab4052b/tools/icom…> 1827 -rwxr-xr-x file serialsniff.c <http://www.d-rats.com/hg/hgwebdir.cgi/chirp.hg/file/c89c1ab4052b/tools/seri…> 9530 -rw-r--r-- into this folder from; http://www.d-rats.com/hg/hgwebdir.cgi/chirp.hg/file/c89c1ab4052b/tools into /tmp/chirp-0.1.9b12/chirp-0.1.9b12/tools Download rpttool (raw file link on left menu)) http://www.d-rats.com/hg/hgwebdir.cgi/chirp.hg/file/c89c1ab4052b/rpttool#l1 into /tmp/chirp-0.1.9b12/chirp-0.1.9b12 Build process incl the original problem; [root@localhost chirp-0.1.9b12]# python setup.py install running install running build running build_py creating build creating build/lib creating build/lib/chirp copying chirp/platform.py -> build/lib/chirp copying chirp/ic2820.py -> build/lib/chirp copying chirp/ic9x_ll.py -> build/lib/chirp copying chirp/chirp_common.py -> build/lib/chirp copying chirp/__init__.py -> build/lib/chirp copying chirp/ic2200_ll.py -> build/lib/chirp copying chirp/generic.py -> build/lib/chirp copying chirp/xml_ll.py -> build/lib/chirp copying chirp/csv.py -> build/lib/chirp copying chirp/memmap.py -> build/lib/chirp copying chirp/idrp.py -> build/lib/chirp copying chirp/ic9x.py -> build/lib/chirp copying chirp/id800_ll.py -> build/lib/chirp copying chirp/ic2200.py -> build/lib/chirp copying chirp/errors.py -> build/lib/chirp copying chirp/ic2820_ll.py -> build/lib/chirp copying chirp/icf.py -> build/lib/chirp copying chirp/convert_icf.py -> build/lib/chirp copying chirp/id800.py -> build/lib/chirp copying chirp/icx8x_ll.py -> build/lib/chirp copying chirp/old_ic9x_ll.py -> build/lib/chirp copying chirp/icx8x.py -> build/lib/chirp copying chirp/util.py -> build/lib/chirp copying chirp/xml.py -> build/lib/chirp running build_scripts creating build/scripts-2.4 error: file 'rpttool' does not exist [root@localhost chirp-0.1.9b12]# python setup.py install running install running build running build_py running build_scripts error: file 'rpttool' does not exist [root@localhost chirp-0.1.9b12]# python setup.py install running install running build running build_py running build_scripts copying and adjusting rpttool -> build/scripts-2.4 changing mode of build/scripts-2.4/rpttool from 644 to 755 running install_lib copying build/lib/chirp/ic9x_ll.py -> /usr/lib/python2.4/site-packages/chirp copying build/lib/chirp/__init__.py -> /usr/lib/python2.4/site-packages/chirp copying build/lib/chirp/ic9x.py -> /usr/lib/python2.4/site-packages/chirp byte-compiling /usr/lib/python2.4/site-packages/chirp/ic9x_ll.py to ic9x_ll.pyc byte-compiling /usr/lib/python2.4/site-packages/chirp/__init__.py to __init__.pyc byte-compiling /usr/lib/python2.4/site-packages/chirp/ic9x.py to ic9x.pyc running install_scripts copying build/scripts-2.4/rpttool -> /usr/bin changing mode of /usr/bin/rpttool to 755 running install_data copying tools/icomsio.sh -> /usr/sbin LOC: [] running install running build running build_py creating build/lib/chirpui copying chirpui/cloneprog.py -> build/lib/chirpui copying chirpui/inputdialog.py -> build/lib/chirpui copying chirpui/__init__.py -> build/lib/chirpui copying chirpui/dstaredit.py -> build/lib/chirpui copying chirpui/shiftdialog.py -> build/lib/chirpui copying chirpui/memedit.py -> build/lib/chirpui copying chirpui/bankedit.py -> build/lib/chirpui copying chirpui/miscwidgets.py -> build/lib/chirpui copying chirpui/mainapp.py -> build/lib/chirpui copying chirpui/common.py -> build/lib/chirpui copying chirpui/clone.py -> build/lib/chirpui copying chirpui/editorset.py -> build/lib/chirpui copying chirpui/importdialog.py -> build/lib/chirpui running build_scripts copying and adjusting chirpw -> build/scripts-2.4 changing mode of build/scripts-2.4/chirpw from 644 to 755 running install_lib copying build/lib/chirpui/mainapp.py -> /usr/lib/python2.4/site-packages/chirpui byte-compiling /usr/lib/python2.4/site-packages/chirpui/mainapp.py to mainapp.pyc running install_scripts copying build/scripts-2.4/chirpw -> /usr/bin changing mode of /usr/bin/rpttool to 755 changing mode of /usr/bin/chirpw to 755 running install_data [root@localhost chirp-0.1.9b12]# Working good on CentOS 5.3 with this procedure. vk4tux

2 1

Re: [chirp_users] 91-A with 121 - B bank is fine - A bank does not work
by David Tilson 03 May '09

03 May '09

G'day Roger, Just another thing to check... Can you confirm that when you were trying to do work with Band A in CHIRP that the radio was set to Band B and running in DV mode? As you may / may not be aware a quirk with CHIRP and using the IC-9X radios is that Band B must be selected and the mode set to DV for it to transfer information (even for Band A memories). On the 92AD if you have the radio is set to Band A and you try to "Connect to IC9X - Band A" it will indicate that it is getting 800+ memories, but nothing gets transferred. Hope this helps... Cheers, davidt, VK3UR

1 0

[chirp_users] 91-A with 121 - B bank is fine - A bank does not work
by Roger Kehr 03 May '09

03 May '09

I am sure someone has asked this question but here goes anyway. I purchased a 91-AD and have programmed it's memory banks A and B. I then purchase a 91-A with a 121 chip.. While it was possible to get my B bank into my B bank I am unable to make an excel file of my A bank to get it into my A bank on the 91-A. Is there some way around this or is there a way to print out what is in the A bank on the 91-AD and put it into my excel spread sheet and then export that into my 91-A using CHIRP? Thanks for a great program - at least my "B" bank information transferred over. 73- N3AOQ Roger

2 1

Re: [chirp_users] CHIRP 0.1.9
by Susan Mackay 03 May '09

03 May '09

Dan, Actually the main point of my message was to point out the log_exception() bug, but thanks for the other information as well. Susan

2 1

[chirp_users] chirp-0.1.9b12.tar.gz on Fedora 10
by Adrian 03 May '09

03 May '09

Realised the whole tools folder was missing chirp.hg <http://www.d-rats.com/hg/hgwebdir.cgi/chirp.hg/> directory /tools/ @ 549:c89c1ab4052b find changesets by author, revision, files, or words in the commit message name size permissions [up] <http://www.d-rats.com/hg/hgwebdir.cgi/chirp.hg/file/c89c1ab4052b/> drwxr-xr-x file Makefile <http://www.d-rats.com/hg/hgwebdir.cgi/chirp.hg/file/c89c1ab4052b/tools/Make…> 843 -rw-r--r-- file icomsio.sh <http://www.d-rats.com/hg/hgwebdir.cgi/chirp.hg/file/c89c1ab4052b/tools/icom…> 1827 -rwxr-xr-x file serialsniff.c <http://www.d-rats.com/hg/hgwebdir.cgi/chirp.hg/file/c89c1ab4052b/tools/seri…> 9530 -rw-r--r-- got it running vk4tux

2 1

Re: [chirp_users] CHIRP 0.1.9
by Susan Mackay 03 May '09

03 May '09

Dan, I downloaded 0.1.9 and fired it up OK. Without connecting a radio, I selected the 'Convert ICF' function and selected an ICF file that I had downloaded from the Internet (actually "IC92AD_VK3RWN_C_V19a.icf" which David VK3UR makes available through the Australian D-Star web site - Thanks David) and tried to save it as an img file. The following was logged on the terminal log: Unknown model: 000: 30 66 00 00 00 00 00 00 0f...... Traceback (most recent call last): File "/Users/Susan/Downloads/chirp-0.1.9/chirpui/mainapp.py", line 428, in mh self.do_converticf() File "/Users/Susan/Downloads/chirp-0.1.9/chirpui/mainapp.py", line 364, in do_converticf log_exception() NameError: global name 'log_exception' is not defined The offending lines seem to be: try: convert_icf.icf_to_image(icffile, imgfile) except Exception, e: log_exception() common.show_error("Unable to convert ICF file: %s" % e) The beginning of the ICF file is: 30660000 #Comment= #MapRev=1 #EtcData=2C48 0000100003E9000020830000E400004E657061 0010106C2020200003F4000020830000E40000 002010557A62656B69202000049F0000208300 00301000E40000536C6F76616B20200004A600 The strange thing is that I can see the 'log_exception' function ion common.py! Susan VK3ANZ

2 1

[chirp_users] CHIRP 0.1.9
by Dan Smith 03 May '09

03 May '09

Hi all, I just posted the official CHIRP 0.1.9 on the download page. Although the list of changes looks small, they are pretty significant: - Fixed broken browse button on clone dialog - Fixed an issue with the 2820 which causes spurious DSQL and CSQL flags on the radio - Fixed MacOS to pick up Prolific-based USB serial devices - Fixed initial sort of channel number column - Fixed tone flag parsing on ic2200 - Fixed interpretation of frequency on ic2200 when tuning step is 12.5 - Change the way callsign lists are handled to more closely mimic the radio - Re-write of the ic9x driver for better stability and maintainability - Improved UI responsiveness during long IC-9x operations - Added a multi-level queue to allow background loading of IC-9x radios without preventing UI-initiated changes - Added empty-location tracking to the ic9x cache to improve reload performance - Added UI improvements like icons and keyboard accelerators - Added ICOM D-STAR repeater frequency programming support - Added file types to Save As box to avoid confusion - Added call channel support to ic9x Thanks! -- Dan Smith dsmith#danplanet.com, s/#/@/ www.danplanet.com KK7DS

2 2

[chirp_users] chirp-0.1.9b12.tar.gz on Fedora 10
by Adrian 02 May '09

02 May '09

Found this; http://www.d-rats.com/hg/hgwebdir.cgi/chirp.hg/raw-file/c89c1ab4052b/rpttool placed in /tmp/chirp-0.1.9b12 got; [root@localhost chirp-0.1.9b12]# python setup.py install running install running build running build_py running build_scripts changing mode of build/scripts-2.5/rpttool from 644 to 755 running install_lib copying build/lib/rpttool -> /usr/lib/python2.5/site-packages copying build/lib/chirp/ic9x_ll.py -> /usr/lib/python2.5/site-packages/chirp copying build/lib/chirp/ic9x.py -> /usr/lib/python2.5/site-packages/chirp copying build/lib/chirp/rpttool -> /usr/lib/python2.5/site-packages/chirp copying build/lib/chirp/__init__.py -> /usr/lib/python2.5/site-packages/chirp byte-compiling /usr/lib/python2.5/site-packages/chirp/__init__.py to __init__.pyc running install_scripts copying build/scripts-2.5/rpttool -> /usr/bin changing mode of /usr/bin/rpttool to 755 running install_data error: can't copy 'tools/icomsio.sh': doesn't exist or not a regular file [root@localhost chirp-0.1.9b12]# Not sure where to place this yet. vk4tux

1 0

[chirp_users] chirp-0.1.9b12.tar.gz on Fedora 10
by Adrian 02 May '09

02 May '09

Link please Dan? [root@localhost ~]# cd /tmp/chirp-0.1.9b12 [root@localhost chirp-0.1.9b12]# python setup.py install running install running build running build_py creating build creating build/lib creating build/lib/chirp copying chirp/icf.py -> build/lib/chirp copying chirp/csv.py -> build/lib/chirp copying chirp/old_ic9x_ll.py -> build/lib/chirp copying chirp/util.py -> build/lib/chirp copying chirp/icx8x.py -> build/lib/chirp copying chirp/platform.py -> build/lib/chirp copying chirp/ic9x_ll.py -> build/lib/chirp copying chirp/ic9x.py -> build/lib/chirp copying chirp/icx8x_ll.py -> build/lib/chirp copying chirp/convert_icf.py -> build/lib/chirp copying chirp/ic2200_ll.py -> build/lib/chirp copying chirp/memmap.py -> build/lib/chirp copying chirp/chirp_common.py -> build/lib/chirp copying chirp/xml.py -> build/lib/chirp copying chirp/ic2200.py -> build/lib/chirp copying chirp/ic2820.py -> build/lib/chirp copying chirp/errors.py -> build/lib/chirp copying chirp/id800_ll.py -> build/lib/chirp copying chirp/ic2820_ll.py -> build/lib/chirp copying chirp/id800.py -> build/lib/chirp copying chirp/idrp.py -> build/lib/chirp copying chirp/__init__.py -> build/lib/chirp copying chirp/xml_ll.py -> build/lib/chirp copying chirp/generic.py -> build/lib/chirp running build_scripts creating build/scripts-2.5 error: file 'rpttool' does not exist [root@localhost chirp-0.1.9b12]# Thanks vk4tux

1 0

Re: [chirp_users] CHIRP 0.1.9b12
by David Tilson 02 May '09

02 May '09

G'day, > Well, that's certainly an option. However, I think I'd > rather move towards a set of preferences that lets you > specify whether you want to see them by default or not. That > would be better, no? :) That would be better, yes... I had actually thought about a preferences option, while I was typing my original email, but I thought that I wouldn't push my luck... But now you've raised it, I'll look forward to seeing it in 0.1.10b1 and I'll raise a ticket for you :) Cheers, davidt

1 0

Re: [chirp_users] CHIRP 0.1.9b12
by David Tilson 02 May '09

02 May '09

G'day Dan, > I just posted 0.1.9b12 with a couple of changes: > > - Add call channels for ic9x Confirmed and thank you... Just a suggestion, but as people probably use the Call channels a lot, how about adding them to the normal Memory Range when reading memories (in a future release), rather than having to tick on Special Channels to read them. > - Show a file type on file->save as to make it a little more clear > that you can't change the file type just by saving Confirmed on my 2820. > On my ic9x, CHIRP is incorrectly showing a TONE setting on > one of my call channels, but not the other. I couldn't replicate this on my 92AD. > So, hopefully this looks good enough to call it 0.1.9 final. > Dave, any objections (after you test this)? Nope, good to go from my perspective. I presume this will (probably) be the Dayton release in which case congratulations are in order. CHIRP is only about 9 months old from when you first mentioned the concept to now and I personally consider it a valuable tool. This is especially impressive given your parallel development of D-RATS. Cheers, Davidt, VK3UR

3 3

[chirp_users] CHIRP 0.1.9b12
by Dan Smith 01 May '09

01 May '09

Hi all, I just posted 0.1.9b12 with a couple of changes: - Add call channels for ic9x - Show a file type on file->save as to make it a little more clear that you can't change the file type just by saving On my ic9x, CHIRP is incorrectly showing a TONE setting on one of my call channels, but not the other. I've looked at the memory data and it sure enough has the bits set indicating the tone encoder, even though it does not display on my radio's screen. This seems relatively minor though. So, hopefully this looks good enough to call it 0.1.9 final. Dave, any objections (after you test this)? Thanks! -- Dan Smith dsmith#danplanet.com, s/#/@/ www.danplanet.com KK7DS

1 0

[chirp_users] Local OS Settings and CHIRP
by Juergen Sturhahn 01 May '09

01 May '09

Starting D-Star with an ID-800H I was trying to reduce the work load of manual entering all memory information directly into the radio and installed CHIRP. I have to admit that I run into nearly every possible trap the program offers for a new user. But with the help of Dan I was able to get it up and running at the end. Might be a beginner's guide or a help file within the program could help to reduce the efforts in climbing up the learning curve . (based on my experience I could offer some limited help). There are some issues, however, I consider as worthwhile to discuss in this group: 1. Excel uses the local settings of the OS. Therefore xxx.csv - files created by the export of an xxx.img-files to a xxx.csv cannot be re-opened again by CHIRP once they have been processed and eventually modified in Excel and saved there again as xxx.csv or yyy.csv Reason is that the local settings in the OS (here German instead of English (USA)) create semicolons (;) instead of commas (,) as separator, don't use a dot (.) but a comma (,) for the decimal information etc. . I have tried to modify the file by an editor using search and replace but the editor doesn't save the result in a way CHIRP would finally process. It would be nice if the program could work in a non-English environment as well. 2. After a successful export and import of xxx.csv under English local settings I have tried to do the same with xxx.chirp. This failed, however, with the error notice "Unable to load schema". At the moment I don't know why this happens. 3. I have imported the xxx.csv into Excel (with English settings), saved it as xxx_1.csv and tried to import or open the saved file in CHIRP. Both failed with the error notice list index out of range. I assume there is something I have to set in Excel but unfortunately I don't know what to do here. Might be it's somehow related to my Excel version but not sure. 73 Juergen, DL8LE

2 1

[chirp_users] 2200H?
by Jeffrey Nawrot 01 May '09

01 May '09

I'm having an issue trying to import a CSV into the 2200H program file. I was able to import it into my ID800 and into my 92AD, but when I do it on the 2200H it seems to just lock up. Am I doing something wrong? Tnx in advance

2 1

Re: [chirp_users] CHIRP 0.1.9b10
by David Tilson 29 Apr '09

29 Apr '09

G'day Dan, > I was hoping to go ahead and get it out, yeah. I suppose I > could try to figure out the IC9x special memories bit real > quick. The import/export of them is a separate can of worms > that I don't want to dive into until 0.1.10 I think. Don't stress over the special memories until 0.1.10. I know that there will be a lot of interest in the ID-RPX function, so that is probably more important to the masses at this time. When 0.1.9 is released we can take our time with the special memories, etc. Cheers, Davidt

2 1

Re: [chirp_users] CHIRP 0.1.9b10
by David Tilson 28 Apr '09

28 Apr '09

Hi Dan, > > Also, I think that we should call 0.1.9 official pretty > soon. I want > > to add support for the IC9x special memories and then I > think that's a > > good place to stop. > Anyone have an opinion here? Have people used 0.1.9b11 > enough to call it good as a stable release? I've used b11 a bit, apart from the ID-RPX functions, and haven't had any problems yet. Does that mean you want to release 0.1.9 prior to inclusion of the IC9X special memories into the GUI (and import / export)? If yes, that's fine and we can catch up on those in a later release. If no, I'm happy to do some testing as soon as the special memories are included. Cheers, davidt

2 1

[chirp_users] CHIRP 0.1.9b10
by Dan Smith 28 Apr '09

28 Apr '09

Hi all, I just posted CHIRP 0.1.9b10 with a single change. There is now an additional option in the Radio menu to allow you to set the frequency on a D-STAR repeater module. I have tested this with an ID-RP4000V and an ID-RP2000V with success. If anyone has a repeater module sitting around, I'd appreciate a report. Also, I think that we should call 0.1.9 official pretty soon. I want to add support for the IC9x special memories and then I think that's a good place to stop. The new 9x background load features would be good to get into the hands of regular users before we attack some of the more disruptive things that are currently on the task list. Thoughts? Thanks! -- Dan Smith dsmith#danplanet.com, s/#/@/ www.danplanet.com KK7DS

3 5

[chirp_users] chirp-0.1.9b11.tar.gz in CentOS 5.3
by Adrian 25 Apr '09

25 Apr '09

Thanks Dan all good, [root@localhost ~]# cd /root/download/chirp-0.1.9b11 [root@localhost chirp-0.1.9b11]# python setup.py install LOC: [] running install running build running build_py copying chirp/idrp.py -> build/lib/chirp running build_scripts running install_lib copying build/lib/chirp/idrp.py -> /usr/lib/python2.4/site-packages/chirp byte-compiling /usr/lib/python2.4/site-packages/chirp/idrp.py to idrp.pyc running install_scripts changing mode of /usr/bin/chirpw to 755 running install_data [root@localhost chirp-0.1.9b11]# ./chirpw [root@localhost chirp-0.1.9b11]# GUI up vk4tux

1 0

[chirp_users] chirp-0.1.9b11.tar.gz in CentOS 5.3
by Adrian 25 Apr '09

25 Apr '09

This one not starting up; [root@localhost ~]# cd /root/download/chirp-0.1.9b11 [root@localhost chirp-0.1.9b11]# python setup.py install LOC: [] running install running build running build_py creating build creating build/lib creating build/lib/chirp copying chirp/platform.py -> build/lib/chirp copying chirp/ic2820.py -> build/lib/chirp copying chirp/ic9x_ll.py -> build/lib/chirp copying chirp/chirp_common.py -> build/lib/chirp copying chirp/__init__.py -> build/lib/chirp copying chirp/ic2200_ll.py -> build/lib/chirp copying chirp/generic.py -> build/lib/chirp copying chirp/xml_ll.py -> build/lib/chirp copying chirp/csv.py -> build/lib/chirp copying chirp/memmap.py -> build/lib/chirp copying chirp/ic9x.py -> build/lib/chirp copying chirp/id800_ll.py -> build/lib/chirp copying chirp/ic2200.py -> build/lib/chirp copying chirp/errors.py -> build/lib/chirp copying chirp/ic2820_ll.py -> build/lib/chirp copying chirp/icf.py -> build/lib/chirp copying chirp/convert_icf.py -> build/lib/chirp copying chirp/id800.py -> build/lib/chirp copying chirp/icx8x_ll.py -> build/lib/chirp copying chirp/old_ic9x_ll.py -> build/lib/chirp copying chirp/icx8x.py -> build/lib/chirp copying chirp/util.py -> build/lib/chirp copying chirp/xml.py -> build/lib/chirp creating build/lib/chirpui copying chirpui/cloneprog.py -> build/lib/chirpui copying chirpui/inputdialog.py -> build/lib/chirpui copying chirpui/__init__.py -> build/lib/chirpui copying chirpui/dstaredit.py -> build/lib/chirpui copying chirpui/shiftdialog.py -> build/lib/chirpui copying chirpui/memedit.py -> build/lib/chirpui copying chirpui/bankedit.py -> build/lib/chirpui copying chirpui/miscwidgets.py -> build/lib/chirpui copying chirpui/mainapp.py -> build/lib/chirpui copying chirpui/common.py -> build/lib/chirpui copying chirpui/clone.py -> build/lib/chirpui copying chirpui/editorset.py -> build/lib/chirpui copying chirpui/importdialog.py -> build/lib/chirpui running build_scripts creating build/scripts-2.4 copying and adjusting chirpw -> build/scripts-2.4 changing mode of build/scripts-2.4/chirpw from 644 to 755 running install_lib copying build/lib/chirpui/memedit.py -> /usr/lib/python2.4/site-packages/chirpui copying build/lib/chirpui/mainapp.py -> /usr/lib/python2.4/site-packages/chirpui copying build/lib/chirpui/clone.py -> /usr/lib/python2.4/site-packages/chirpui copying build/lib/chirpui/editorset.py -> /usr/lib/python2.4/site-packages/chirpui copying build/lib/chirp/ic9x_ll.py -> /usr/lib/python2.4/site-packages/chirp copying build/lib/chirp/__init__.py -> /usr/lib/python2.4/site-packages/chirp byte-compiling /usr/lib/python2.4/site-packages/chirpui/memedit.py to memedit.pyc byte-compiling /usr/lib/python2.4/site-packages/chirpui/mainapp.py to mainapp.pyc byte-compiling /usr/lib/python2.4/site-packages/chirpui/clone.py to clone.pyc byte-compiling /usr/lib/python2.4/site-packages/chirpui/editorset.py to editorset.pyc byte-compiling /usr/lib/python2.4/site-packages/chirp/__init__.py to __init__.pyc running install_scripts copying build/scripts-2.4/chirpw -> /usr/bin changing mode of /usr/bin/chirpw to 755 running install_data [root@localhost chirp-0.1.9b11]# ./chirpw Traceback (most recent call last): File "./chirpw", line 27, in ? from chirpui import mainapp File "/root/download/chirp-0.1.9b11/chirpui/mainapp.py", line 30, in ? from chirp import platform, id800, ic2820, ic2200, ic9x, icx8x, xml, idrp ImportError: cannot import name idrp [root@localhost chirp-0.1.9b11]# python setup.py install LOC: [] running install running build running build_py running build_scripts running install_lib running install_scripts changing mode of /usr/bin/chirpw to 755 running install_data [root@localhost chirp-0.1.9b11]# ./chirpw Traceback (most recent call last): File "./chirpw", line 27, in ? from chirpui import mainapp File "/root/download/chirp-0.1.9b11/chirpui/mainapp.py", line 30, in ? from chirp import platform, id800, ic2820, ic2200, ic9x, icx8x, xml, idrp ImportError: cannot import name idrp [root@localhost chirp-0.1.9b11]# vk4tux

2 1

Re: [chirp_users] CHIRP 0.1.9b10
by David Tilson 25 Apr '09

25 Apr '09

G'day again, > Okay, I'm going to re-generate as b11 and post in the right > place. Should be there shortly... Got it that time... Thanks. With the label saying "ID-RPx000V" I'm guessing that excludes the 23cm DV (ID-RP2V) and 23cm DD (ID-RP2D) repeaters at this stage as they would have an extra digit that would need to be added in their frequency range. Cheers, davidt

2 1

Re: [chirp_users] CHIRP 0.1.9b10
by David Tilson 24 Apr '09

24 Apr '09

Howdy Dan, > Aack! I looked in the beta directory to figure out what the > next version number should be, but perhaps I forgot to refresh! Just shows you're human (well sort of) :) > Any chance we can just forget about the other b10? :D I can live with it, but it still looks like the original b10 is still in the beta directory (still with 17 Apr Last Modified date), not this jumped up wanna be b10, that you want us to test :) I just downloaded / re-installed b10 and it looks like the original. I'm guessing it should show up initially in the "Download from Radio" section as I can't see any other spot where it would probably be. BTW, I've got D-RATS b4 connected to the ratflector if you want to do some tests, although I'll be in and out of the shack a bit. Cheers, davidt

2 1

Re: [chirp_users] CHIRP 0.1.9b10
by David Tilson 24 Apr '09

24 Apr '09

G'day Dan, > I just posted CHIRP 0.1.9b10 with a single change. I'm a little confused (not hard to achieve really)... Shouldn't it be 0.1.9b11 ???? According to my records (and the beta directory) b10 was posted on the 17th April, but the changelog shows changes as of a few hours ago. There's no sign of a b11 in the beta directory (yet). Cheers, Davidt, VK3UR

2 1

Re: [chirp_users] CHIRP 0.1.9b10
by David Tilson 18 Apr '09

18 Apr '09

G'day Dan, > I just posted 0.1.9b10 with the following changes: > > - Fix import (and export for that matter) Bingo! Thanks for that. > - Add accelerator keys for a bunch of menu items I've only tested a few so far, but a good addition. Cheers, Davidt

1 0

[chirp_users] CHIRP 0.1.9b10
by Dan Smith 18 Apr '09

18 Apr '09

Hi all, I just posted 0.1.9b10 with the following changes: - Fix import (and export for that matter) - Fix ic9x band A memory storing - Fix ic9x delete memory function - Add radio->stop to flush the queue of all waiting jobs for ic9x - Add GTK stock items to menu (i.e. pretty icons) - Fix ic9x detection of AM as NFM - Add accelerator keys for a bunch of menu items Thanks! -- Dan Smith dsmith#danplanet.com, s/#/@/ www.danplanet.com KK7DS

1 0

Re: [chirp_users] CHIRP 0.1.9b9
by David Tilson 15 Apr '09

15 Apr '09

G'day Dan, > - Fix the ic9x issue with band edges. This was actually much worse in > that it was just requesting the wrong channel numbers from > the radio. Yep, that's better... > It can be accessed here: > > http://chirp.danplanet.com/trac Excellent, it is already at the top of my favourites list, for frequent access :) > Bugs reports and feature requests should be reported there so > we can keep track of them. If you're reporting a > radio-related issue, be sure to attach your radio image, > debug log, and potentially an ICF file if appropriate. Dan, the debug.log files are (in my case) normally larger than 256KB, which is the max attachment size you currently have set for TRAC. I just tried sending a debug.log for issue #2, which is approx 830KB, and TRAC wouldn't accept it. I'll send it separately. > Dave > T, don't forget the web server is a single-processor machine > with a finite amount of storage space :-D Hmm, this could be a problem... You might need to tap into some of your work computers :) > I think CHIRP lends itself even more to the > copy-the-list-on-ticket- status-emails model, so do we want > to enable that here as well? Definitely! Cheers, davidt

2 1

[chirp_users] CHIRP 0.1.9b9
by Dan Smith 15 Apr '09

15 Apr '09

Hi all, Changes are: - Fix the ic9x issue with band edges. This was actually much worse in that it was just requesting the wrong channel numbers from the radio. - Fix TSQL detection in ic2200 (broken for a while it would seem). - Fix incorrect frequency calculation on ic2200 if a non-12.5kHz frequency is stored in a channel with a tune-step of 12.5kHz. Also, at this point I'd like to reveal the CHIRP issue tracker. It's just like the D-RATS one if you're familiar with that. It can be accessed here: http://chirp.danplanet.com/trac Bugs reports and feature requests should be reported there so we can keep track of them. If you're reporting a radio-related issue, be sure to attach your radio image, debug log, and potentially an ICF file if appropriate. Dave T, don't forget the web server is a single-processor machine with a finite amount of storage space :-D I think CHIRP lends itself even more to the copy-the-list-on-ticket- status-emails model, so do we want to enable that here as well? Thanks! -- Dan Smith dsmith#danplanet.com, s/#/@/ www.danplanet.com KK7DS

1 0

Re: [chirp_users] CHIRP 0.1.9b8
by David Tilson 15 Apr '09

15 Apr '09

G'day Dan, > - Fix (hopefully) the mis-numbering of memories from ic9x radios with > the new driver. The fix was simple and obvious. Yep, confirmed... However :) On the IC-92AD Band A, although the status information indicates that CHIRP read all 800 memories, it will only display up to 351. It does not display 352 - 799. On the IC-92AD Band B, the status information indicates that CHIRP read all 400 memories, but it will only display up to 189 and then 0A. It does not display 190 - 399. I tried this a few times with consistent results. I'll send the debug log separately and matching ICF file, as they are too big for the list. I then fired up version 0.1.9b4 as a comparison and it read all of the memories in both Band A and Band B correctly. Cheers, Davidt, VK3UR

2 1

[chirp_users] CHIRP 0.1.9b8
by Dan Smith 14 Apr '09

14 Apr '09

Hi all, I apologize for letting CHIRP work get away from me. The changes are: - Fix (hopefully) the mis-numbering of memories from ic9x radios with the new driver. The fix was simple and obvious. - Fix the import/export function (since the advent of the priority-based queue). - Make an import/export action take priority over the massive and obligatory "background load" to avoid waiting until that completes to allow the import. Thanks! -- Dan Smith dsmith#danplanet.com, s/#/@/ www.danplanet.com KK7DS

1 0

Re: [chirp_users] CHIRP 0.1.9b7
by David Tilson 21 Mar '09

21 Mar '09

> Hmm, I swear it works here. I'll have to take another look. > > This is a CSV of your radio as generated with a known-working > CHIRP, is that right? Yep, I attached it previously as it had 100 memories programmed, so you'd be able to see any gaps in CHIRP. > Thanks :) No dramas. Cheers, davidt

1 0

Re: [chirp_users] CHIRP 0.1.9b7
by David Tilson 20 Mar '09

20 Mar '09

G'day Dan, > I just posted 0.1.9b7 with the following changes: You're not going to like this :( > - Fix memory numbering weirdness in 9x driver Ummm, nope. This does not appear to have changed here. On my radio (Band A) I have Mems 0 - 100 all with content in them, but CHIRP is still reporting Mems 1 - 9 correctly, then skips to show a block from Mem 16 to Mem 25 (but with Radio Mem 10 to Mem 19 content), then skips to another block from Mem 32 to Mem 35 (with Radio Mem 20 - 22 content). It has similar blocks of memory jumping throughout the remainder of the memories, but I think you get the idea. This feature also occurs on Band B as well. > - Make 9x driver cache empty memories to avoid re-checking This function looks like it is now working, as it only loads the memories once :) I've attached a CSV for Band A Mems 0 - 099 which you could import and use to confirm. Cheers, Davidt, VK3UR - still with unresolved issues :)

2 1

[chirp_users] CHIRP 0.1.9b7
by Dan Smith 19 Mar '09

19 Mar '09

Hi all, I just posted 0.1.9b7 with the following changes: - Fix memory numbering weirdness in 9x driver - Make 9x driver cache empty memories to avoid re-checking Hopefully this will actually addres most of Dave's issues. The memory numbering thing was so broken that a number of other things could have been breaking, so I decided to get another version out to test quicker. Thanks a lot to Susan who did some excellent debug work before I even got to it which made the process of fixing it much quicker :) -- Dan Smith dsmith#danplanet.com, s/#/@/ www.danplanet.com KK7DS

2 1

[chirp_users] more on getting OS X working
by Debbie Fligor 18 Mar '09

18 Mar '09

Dan and the group, I'm looking for thoughts on why d-rats works fine, and chirp doesn't for my MacBook Pro. I've tried Susan's path: export PYTHONPATH=/opt/local/lib/python2.5/site-packages using the rest of python as-is in MacOS 10.5.6 (although I might have more installed in site-packages than she does, it's where my ports drats build setup is) and am still getting the same error I do with either my fink or ports full setup (both of which work fine with d-rats). the main window opens, I can choose new, or look at the about box, but not open the serial port. I'm wondering if I've got some cache file somewhere that's messing things up, it seems to always have a problem with "list index out of range" I was pretty sure that at least once I got it to run many versions ago, but I'm not 100% sure on that. If so it was summer time frame. I tried both 1.8 (since Susan had it working on Mac) and the latest beta). Any ideas are appreciated. -debbie, n9dn here's MacOS's python with the path set to the ports site packages: 951 Mnementh> python chirpw Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "RANDR" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Traceback (most recent call last): File "/Users/fligor/bin/chirp-0.1.8/chirpui/mainapp.py", line 391, in mh self.do_open9x(ic9x.IC9xRadioB) File "/Users/fligor/bin/chirp-0.1.8/chirpui/mainapp.py", line 119, in do_open9x rtype="ic9x") File "/Users/fligor/bin/chirp-0.1.8/chirpui/clone.py", line 70, in __init__ self.port = miscwidgets.make_choice(ports, True, ports[0]) IndexError: list index out of range ^CTraceback (most recent call last): File "chirpw", line 37, in <module> gtk.main() here's fink's python that works just fine for d-rats: 991 Mnementh> python2.5 chirpw chirpw:41: PangoWarning: error opening config file '../Resources/etc/ pango/pangorc': No such file or directory a.show() Traceback (most recent call last): File "/Users/fligor/bin/chirp-0.1.9b5/chirpui/mainapp.py", line 391, in mh self.do_open9x(ic9x.IC9xRadioB) File "/Users/fligor/bin/chirp-0.1.9b5/chirpui/mainapp.py", line 119, in do_open9x rtype="ic9x") File "/Users/fligor/bin/chirp-0.1.9b5/chirpui/clone.py", line 70, in __init__ self.port = miscwidgets.make_choice(ports, True, ports[0]) IndexError: list index out of range

2 3

Re: [chirp_users] CHIRP 0.1.9b5
by Susan Mackay 18 Mar '09

18 Mar '09

Dan, I can only see V0.1.8 on the downloads page of your web site. Is this page still waiting to be updated or do I need to go somewhere else to get the latest beta version? Susan

2 1

Re: [chirp_users] CHIRP 0.1.9b6
by David Tilson 18 Mar '09

18 Mar '09

Howdy, > Right, that's the idea. It's downloading them in the > background if there is nothing else to do. No probs with that at all and what I expected. > > I then looked at the contents of Mem 10 (on the radio) and > it matched > > Mem 16 in CHIRP, likewise Mem 11 on the radio matched Mem > 17 in CHIRP, > > etc. I checked Mem 22 (on the radio) as the next break in > the memory > > map and it matched Mem 34 on CHIRP. > > Okay, I'm not sure I understand. Are you saying that unused > memory gaps are resulting in an incorrect ordering in CHIRP? Not quite as there were no memory gaps in the radio... Mems 00 - 100 are all in use in Band A, however CHIRP reported that Mems 10 - 15, 22 - 33, etc had nothing programmed in them and displayed incorrect Memory positions for that data. Not sure if that is clear or not, so I'll try a different description... The data is there in CHIRP, but as indicated earlier, it does not match the Memory location on the radio. CHIRP appears to be putting gaps in to the list. > > One other thing I noticed was that even though CHIRP downloaded the > > entire contents of Band A, without prompting when it was initially > > connected, if I instructed CHIRP to display 00 - 800, it would > > download the entire contents again. > > Hmm, that's not the way it's supposed to work :) I figured that would probably be the case :) > One thing that may be throwing you off is that it (yet) > doesn't cache empty memories, so it will check the radio > again to see if those have been added. Is this perhaps what > you perceived as re-downloading the memories? Understand that. No, that is not what I was seeing. It was downloading all 845 memories each time. > If not, does it do this on Band B? In all honesty, I rarely > test with Band A since Band B has more stuff to go wrong, so > perhaps I broke something with Band A specifically. OK, just tried it on Band B and had the same results, ie CHIRP indicates that Mems 0 - 09, 16 - 21, 34 - 35, 64 - 69 are displayed, whereas the radio shows that Mems 0 - 23, 40 - 45, 50 - 73 are all in use. The data is all there, but the Radio Mems don't line up with the CHIRP Mems. Hope that makes sense :) Cheers

2 1

[chirp_users] CHIRP 0.1.9b6
by David Tilson 18 Mar '09

18 Mar '09

G'day Dan, I've just installed version 0.1.9b6 on WinXP here. First set of tests. Connect to IC-92AD Band A and download memory contents. Even though CHIRP was displaying 00 - 25 as the initial range, it downloaded in excess of 800 memories (I'm guessing the 800 + 45 special mems), however it did not display all of the memories between 00 and 25 as I would have expected. It displayed 0 - 9 and then 16 - 21, followed by 34 - 37. Everything else was missing, however when I looked at the debug log it had read 845 memories. I then looked at the contents of Mem 10 (on the radio) and it matched Mem 16 in CHIRP, likewise Mem 11 on the radio matched Mem 17 in CHIRP, etc. I checked Mem 22 (on the radio) as the next break in the memory map and it matched Mem 34 on CHIRP. I then instructed the CHIRP to read mems 00 - 800 and Mem 100 (on the radio) matched Mem 258 on CHIRP. By the time I got to Mem 799 on the radio I had 1920 memories according to CHIRP. If only it were true, as I could really use the additional memories :) I repeated this exercise twice, after exiting / restarting, with the same results. One other thing I noticed was that even though CHIRP downloaded the entire contents of Band A, without prompting when it was initially connected, if I instructed CHIRP to display 00 - 800, it would download the entire contents again. I'll send the debug log to you directly, but from the few that I checked the memories match up correctly in the log. Regards, David Tilson, VK3UR

2 1

[chirp_users] CHIRP 0.1.9b5 on Cent)S 5.2
by Adrian 14 Mar '09

14 Mar '09

Have found this very good with the 92AD Dan, sorry group re; the D-Rats etc, subject line I used on previous posts. regards Adrian

2 1

[chirp_users] CHIRP 0.1.9b5
by Dan Smith 14 Mar '09

14 Mar '09

Hi all, It has been ages since I got out an update to CHIRP. My apologies for that. Other things have taken priority, as usual. Stuart Tener N3GWG has recently reignited the fire under my, um, keyboard and helped conceive and test some of the following bits. Hopefully with his help, I can go back to getting less sleep and more CHIRP work done! I just posted 0.1.9b5: - Make import action attempt to add callsigns as necessary to the incoming radio - Improve responsiveness during long import actions and offer some visual stimulation to reassure the user we're still working - Fix broken "browse" button on the image clone dialog - Fix a 2820 issue where some extra cleanup is required when moving a channel from FM to DV mode - Add MacOS build support - Pick up Prolific USB device names on MacOS - Change the way the callsign list editor works (to show all slots) - Make the callsign editor use fixed-width font for easier lining up of callsigns - Set the initial sort field to be the location column in memory editor on load - Re-write the 9x driver to be cleaner and more maintainable (shouldn't impact functionality, but plenty of testing is needed to ensure we didn't regress) - Make the radio thread work queue support multiple priorities Please do hammer the 9x driver to make sure nothing (else) was broken after the re-write. Also note that with the 9x, you can now make changes to memories before all of the memory channels have loaded and that the entire list of memories will be fetched in the background for quicker loading, but this does not prevent other activities such as callsign/bank editing, etc. If you're running on MacOS, please try out the new MacOS .app package. I can generate a PPC version if anyone needs it. If it works, thank Stuart for that. You can also thank him for making your serial ports properly populate in the clone box :) Have at it and let us know of any new issues! -- Dan Smith dsmith#danplanet.com, s/#/@/ www.danplanet.com KK7DS

2 3

[chirp_users] D-RATS 0.3.0-alpha5 on CentOS 5.
by Adrian 14 Mar '09

14 Mar '09

>I might've, yeah. Does the callsign editor show numbered callsign slots? Looks like it has Dan ie; http://vk4tux.no-ip.org:81/chirpalpha5.jpg vk4tux

2 1

[chirp_users] D-RATS 0.3.0-alpha5 on CentOS 5.2
by Adrian 13 Mar '09

13 Mar '09

Built this one as per usual python setup.py install method and the result GUI help > about shows; CHIRP 0.1.9b4 Run progarm from the extracted folder with same result. Did you forget to update that to CHIRP 0.1.9b5 Dan? Or is it something I did. vk4tux

2 1

[chirp_users] Hello all
by IT2 Stuart Blake Tener, USNR 05 Mar '09

05 Mar '09

ALCON: Hello all, I am Stuart (N3GWG) and I wanted to kind of introduce myself to the group here. I am a Computer Scientist that has been an Amateur since mid-1988 (16 AUG to be exact is when I got my Novice ticket), and I also have a strong background in radio programming software. When I conducted an initiate review of CHIRP and its capabilities, my first response (as was posted on the list) was, is their a MacOS version? Mainly, because I use a Mac, and am a Unix System Administrator. Since that point, I have familiarized myself with CHIRP and its build process and source code control system, and should have a MacOS version ready within the next day or so (there are additional improvements to CHIRP that we are working on, that I hope to be part of that version). As is many times the case, I hope that the MacOS version will be ahead of the Windows version feature-wise. Just as an aside on MacOS, if you "dual boot" Linux and Windows (as I used to do, granted I have virtualization software also), I found the migration to an Apple environment (Microsoft Office runs natively in MacOS) capable of provisioning all the Unix needs I had as well as running most of the olde Microsoft based software I had run. So, if you do Unix Administration or that, I do truly suggest looking at a Mac. Besides, the hardware is ubber cool too! I own an IC-91AD and an IC-2820, and have been slowly working on understanding CHIRP (on a source code level) so that greater functionality can be apportioned. So keep an eye out for the pronouncement of when and where to get the MacOS version of CHIRP, it will be forthcoming very soon! -- 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

1 0

[chirp_users] Import error
by dave＠proficia.com 05 Mar '09

05 Mar '09

Attempting import from csv file getting the following error message. There was an error opening C:\Documents and Settings\Dave Cooley\Desktop\KR4X-4b.csv: `Tone ' is not in valid list: ['', 'Tone', 'TSQL', 'DTCS', 'DTCS-R', 'TSQL-R'] What is this error message telling me? I place it next to a csv file that WILL import and the fields all look identicle. -- Dave Cooley N4DIB www.tampadstar.com

2 1

[chirp_users] MacOS Version of Chirp
by IT2 Stuart Blake Tener, USNR 03 Mar '09

03 Mar '09

ALCON: I have been a Unix System Administrator for many years, and in fact would be quite capable of testing, compiling, or generating object code on my Intel Mac for the benefit of the community. My understanding of the current Apple Development Kit is that you can generate Intel based code on the PPC, whether it is "Universal" code for any target processor (PPC or Intel), or Intel specific (and optimized) code that is intended for only the Intel chip. Now I understand this is mostly written in Python, anyway, but, just some food for thought here. I saw where someone was speaking of a ".19" version (beta?) but given the open source nature of the software, was surprised to not see it on the download site. One thing I had been working on was a decoder for reading the code plug from an "ICF" file. Now that I see this software is here, I would be willing to try to integrate that into Chirp such that we could at least read and for sure try to shoot for writing "ICF" files compatible with the ICOM software for Windows. -- Very Respectfully, IT2 Stuart Blake Tener, USNR Las Vegas, NV / Beverly Hills, CA / Philadelphia, PA / Washington, DC Amateur Radio Call Sign: N3GWG (Extra) / Marine Radio Operator Permit (MROP) email: teners(a)bh90210.net (also carbon copies to my Blackberry) phone: +(1) 310.358.0202 (Beverly Hills, CA, forwards to mobile phone) phone: +(1) 215.338.6005 (Philadelphia, PA, voice mail only) E-Fax: +(1) 928.437.4505 (Telecopier, fax to email gateway) Military emails (checked monthly until remote NMCI access is secured) NIPRNET: stuart.tener(a)navy.mil NIPRNET: stuart.b.tener(a)us.army.mil NRO: teners(a)nro.mil TS/SCI: tenerstu(a)nro.ic.gov (GWAN) Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and/or privileged information, though strictly at the UNCLASSIFIED level. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the originate message.

3 3

Re: [chirp_users] MacOS Version of Chirp
by Susan Mackay 03 Mar '09

03 Mar '09

I can run Chirp 0.1.8 on Leopard if I do the following: I have installed the python 'serial' and 'gtk' packages through macports. Therefore I need to include the statement: export PYTHONPATH=/opt/local/lib/python2.5/site-packages into my environment startup file. You may have a different place. I also needed to alter a line in 'Platform.py' because of the slightly different names of the USB serial ports. I changed it to: def list_serial_ports(self): return sorted(glob.glob("/dev/ttyS*") + glob.glob("/dev/ ttyUSB*") + glob.glob("/dev/tty.usb*")) (Note the 3rd part - the serial USB ports on my system are all labelled "/dev/tty.usbxxxxx") With those to changes, I 'cd'd to the directory and ran: ./chirpw with success. If you have not played with the default X11 set-up, then X11 should start automatically when needed. (BTW, I'm using the X11-2.3.2.1.dmg X11 distribution if that matters - I doubt it). I have an IC-91AD that connects through an FTDI chip to the USB port. I also have the FTDIUSBSerialDriver_v2_2_10.dmg drivers installed. Hope this helps someone. Susan

2 1

[chirp_users] How to convert from 800-2820 and back?
by dave＠proficia.com 03 Mar '09

03 Mar '09

Please excuse the ignorance. Apparently I was absent the day that we went over this. What is the correct (or succesful) procedure for converting a file from an 800 icf file to a 2820 icf file? I can import into Chirp and save as a Chirp or img file. Is there no way to save as an ICF file that the cs-d800 or cs-2820 software can read other than to load directly into the radio with Chirp then read it back out with the icom software?

2 1

[chirp_users] What it does and how ?
by Steven Samuel Bosshard (NU5D) 03 Mar '09

03 Mar '09

Is there a repository of information about what exactly chirp does and how to use ? It looks like native chirp files do not apply to 91/92 radios. Just looking for a what is what page. Also it seems when I export from a 91 / 92 to csv, then use open office calc to edit the file, that there is a data mismatch error trying to re-open in chirp, even if I don't (knowingly) change anything. TNX and 73, Steve -- "It is a poverty to decide that a child must die so that you may live as you wish." Mother Teresa

2 1

Re: [chirp_users] Info
by Dan Smith 27 Feb '09

27 Feb '09

> Worked EXACTLY as advertised. I did this on band a first - worked just > fine and thanks for the clarification. Steve Wow, even _I'm_ surprised it worked :D -- Dan Smith dsmith#danplanet.com, s/#/@/ www.danplanet.com KK7DS

1 0

[chirp_users] Info
by Steven Samuel Bosshard (NU5D) 27 Feb '09

27 Feb '09

I have both a 91 and 92 here on the desk. The 91 is programmed to my liking. Is there a quick step by step on how to transport the contents (memories) from the 91 to the 92 ? Sorry I am kinda dense on this and please be patient. (both radios communicate with the chirp. I can save and load csv files. I get a schema error trying to load *.chirp files). Thanks, Steve NU5D -- "It is a poverty to decide that a child must die so that you may live as you wish." Mother Teresa

2 1

[chirp_users] Building Chirp under MacOS
by IT2 Stuart Blake Tener, USNR 26 Feb '09

26 Feb '09

ALCON: Ok, I just gave it a try, and found that it is missing a "gtk" library under MacOS. -- Very Respectfully, IT2 Stuart Blake Tener, USNR Las Vegas, NV / Beverly Hills, CA / Philadelphia, PA / Washington, DC Amateur Radio Call Sign: N3GWG (Extra) / Marine Radio Operator Permit (MROP) email: teners(a)bh90210.net (also carbon copies to my Blackberry) phone: +(1) 310.358.0202 (Beverly Hills, CA, forwards to mobile phone) phone: +(1) 215.338.6005 (Philadelphia, PA, voice mail only) E-Fax: +(1) 928.437.4505 (Telecopier, fax to email gateway) Military emails (checked monthly until remote NMCI access is secured) NIPRNET: stuart.tener(a)navy.mil NIPRNET: stuart.b.tener(a)us.army.mil NRO: teners(a)nro.mil TS/SCI: tenerstu(a)nro.ic.gov (GWAN) Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and/or privileged information, though strictly at the UNCLASSIFIED level. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the originate message.

1 0

[chirp_users] MacOS Version of Chirp
by IT2 Stuart Blake Tener, USNR 25 Feb '09

25 Feb '09

ALCON: I have both an ICOM IC-91AD and IC-2820 as well as a MacBook Pro running MacOS 10.5.6, and would like to know when a version of Chirp might be forthcoming for the Mac. Construction of a cable has been completed, and I look forward to having my radio programmable natively under MacOS. 73, Stuart, N3GWG -- Very Respectfully, IT2 Stuart Blake Tener, USNR Las Vegas, NV / Beverly Hills, CA / Philadelphia, PA / Washington, DC Amateur Radio Call Sign: N3GWG (Extra) / Marine Radio Operator Permit (MROP) email: teners(a)bh90210.net (also carbon copies to my Blackberry) phone: +(1) 310.358.0202 (Beverly Hills, CA, forwards to mobile phone) phone: +(1) 215.338.6005 (Philadelphia, PA, voice mail only) E-Fax: +(1) 928.437.4505 (Telecopier, fax to email gateway) Military emails (checked monthly until remote NMCI access is secured) NIPRNET: stuart.tener(a)navy.mil NIPRNET: stuart.b.tener(a)us.army.mil NRO: teners(a)nro.mil TS/SCI: tenerstu(a)nro.ic.gov (GWAN) Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and/or privileged information, though strictly at the UNCLASSIFIED level. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the originate message.

3 3