- Users - lists.chirpmyradio.com

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 17 Mar '09

17 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