December 2012 - Developers - lists.chirpmyradio.com

[chirp_devel] ICOM V-80 driver
by Drew Vonada-Smith 31 Dec '12

31 Dec '12

Team, I now have the development env installed on a Win32 PC machine and it seems to be working. One note: Win32 env instructions say to add C:\Python27\bin to the path. I see no bin directory, it looks like it should just be C:\Python27. After this, it worked. What is my next step to work on a IC-V80 driver? 73, Drew K3PA

2 1

[chirp_devel] [PATCH 1 of 2] bitwise: add get_raw() method to arrayDataElement. For #363
by Tom Hayward 29 Dec '12

29 Dec '12

# HG changeset patch # User Tom Hayward <tom(a)tomh.us> # Date 1356758619 28800 # Node ID 56749d29e5506922a6a9e930f76438c74be6ed66 # Parent 37b042d567412f3abdceea513a39e13aef344caa bitwise: add get_raw() method to arrayDataElement. For #363 diff -r 37b042d56741 -r 56749d29e550 chirp/bitwise.py --- a/chirp/bitwise.py Fri Dec 28 07:58:20 2012 -0800 +++ b/chirp/bitwise.py Fri Dec 28 21:23:39 2012 -0800 @@ -174,6 +174,9 @@ def get_value(self): return list(self.__items) + def get_raw(self): + return "".join([item.get_raw() for item in self.__items]) + def __setitem__(self, index, val): self.__items[index].set_value(val)

2 2

[chirp_devel] Chirp LiveCD update
by B Giff 29 Dec '12

29 Dec '12

I am currently uploading a new version of the Chirp LiveCD. It should be available for download by 1900GMT. http://sourceforge.net/projects/chirplivecd I've added a few new features to make the CD even more useful. First is an updater for Chirp. You will see an orange icon on the desktop titled Chirp Updater. Double click it and follow the on screen instructions to update Chirp to the latest release. Please note that if you are running from a CD, the changes will NOT be retained. When you reboot the computer, you will be back to the old version of Chirp. If you plan to use the liveCD more than a time or two, I recommend you make a bootable USB drive (LiveUSB). Instructions are located in the project's wiki. The LiveUSB will retain the updated Chirp and any files you save. For the Chirp developers out there, mercurial is included in this release. For digital mode users, Fldigi is included in this release. Note to all, I will be unable to push out another release until February. Bob

1 0

[chirp_devel] [PATCH] [px777] fix no-tone identifier. Fixes #363
by Tom Hayward 28 Dec '12

28 Dec '12

# HG changeset patch # User Tom Hayward <tom(a)tomh.us> # Date 1356733619 28800 # Node ID 54eeec36d292bff0f8ca298fc26e7735d9d9652a # Parent 37b042d567412f3abdceea513a39e13aef344caa [px777] fix no-tone identifier. Fixes #363 diff -r 37b042d56741 -r 54eeec36d292 chirp/puxing.py --- a/chirp/puxing.py Fri Dec 28 07:58:20 2012 -0800 +++ b/chirp/puxing.py Fri Dec 28 14:26:59 2012 -0800 @@ -204,7 +204,7 @@ return True def _is_no_tone(field): - return field[0].get_raw() == "\xFF" + return int(field) in [0, 16665] def _get_dtcs(value): # Upper nibble 0x80 -> DCS, 0xC0 -> Inv. DCS

2 4

[chirp_devel] Development env?
by Drew Vonada-Smith 28 Dec '12

28 Dec '12

All installed. OK up to: python chirpw Python: can't open file 'chirpw': [Errno 2] No such file or directory I'm not seeing where chirp source was installed in the procedure.

5 29

Re: [chirp_devel] Development env?
by Drew Vonada-Smith 26 Dec '12

26 Dec '12

OK, envir all installed. OK up to: python chirpw Python: can't open file 'chirpw': [Errno 2] No such file or directory I'm not seeing where chirp source was installed in the procedure. Can anyone help? Thanks, Drew

1 0

[chirp_devel] New developer for IC-V80
by Drew Vonada-Smith 24 Dec '12

24 Dec '12

Hi, I'd like to help by working on a driver for my IC-V80 HT. How to start? Thanks es 73, Drew K3PA

2 1

[chirp_devel] New Developer Documentation
by Dan Smith 24 Dec '12

24 Dec '12

Hi all, We've got (at least) a couple new folks joining who are looking to help out. They're going to have questions about the process for doing things, and I figure it's about time to codify some of that for easy access. I have added a general "process" overview, as well as instructions on how to get a Win32 development environment set up to the top-level developers page: http://chirp.danplanet.com/projects/chirp/wiki/Developers Comments and suggestions are very much welcomed from veterans as well as new folks trying to follow them. If they're not helpful or confusing (or I left something out) please speak up! Thoughts? -- Dan Smith www.danplanet.com KK7DS

1 0

Re: [chirp_devel] Mods for the UV-5R
by Dan Smith 23 Dec '12

23 Dec '12

Since this is new-plans stuff, I'm going to drag you over to the devel mailing list. Let's continue the discussion there. > Unfortunately Baofeng didn't just tack new settings on the end. They > inserted 20.0K in between 12.5K and 25.0K. I can easily change it by > adding the 2 additional selections, but I'm afraid someone selecting > 20.0K on an older firmware will actually get 25.0K. I would need help > knowing how to make two lists and then selecting the correct one based > on the firmware version being used. Right, so there's a method on the driver called "_is_orig()" that will return True if it is the "original" style of firmware, or False if it's the newer kind. So, you can do something like this: tuning_steps = list(STEP_LIST) # Make a copy of the main list if not self._is_orig(): tuning_steps.insert(5, 20.0) # Insert 20.0 at index 5 tuning_steps.insert(...) Then just change the initialization of the setting to use the tuning_steps list instead of the global constant one. > I would like to add most of the rest of the settings that would go on > the Settings tabs. That should be fairly easy for me to do. I believe > that, with your excellent guidence, I have a good start on that. Yep, sounds like you've got a good handle on that part. > Then what I would like to do is tackle some of the 'per channel' > settings like Busy Channel Lockout, S-CODE, PTT-ID (if that is even > possible). Yep, that's good. Anything that the Memory class has in it should be supported that way (i.e. the Memory class in chirp_common.py). However, features not supported there can be added to the "extra" field in Memory. This field lets you stuff settings (just like you've been doing for the radio-wide settings) that are specific to a memory channel in there, which are exposed to the user via the Right-click->Edit dialog box. See the ft817.py driver for an example. Look in get_memory() and set_memory() for where mem.extra is manipulated. Thanks Jim! -- Dan Smith www.danplanet.com KK7DS

3 3

[chirp_devel] Chirp support for Alinco DJ-G7E
by Luchezar Georgiev 21 Dec '12

21 Dec '12

Hello, I had few emails with Alinco and they send to me full programming info for Alinco DJ-G7E. My initial intentions was to write some piece of software to import repeater channels from my QTH to handheld from CVS file. Stock software is very instable, etc. Unfortunately I will be very busy next few months and have no time and experience to add this radio to chirp. So, if anyone wants to help I will share information with him, also I can provide remote acces to some machine, using Windows or Linux and radio connected via ERW-7 cable. Keep up the good work LZ1LGG

1 0