- Developers - lists.chirpmyradio.com

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

29 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 27 Dec '12

27 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

[chirp_devel] [PATCH 0 of 2] Puxing PX777 fixes
by Tom Hayward 20 Dec '12

20 Dec '12

I tried to reprogram a Puxing PX-777 today and ran into a few issues. These fixes resolve them. Tom KD7LXL

2 5

Re: [chirp_devel] [chirp_users] New Daily Build
by Marco IZ3GME 20 Dec '12

20 Dec '12

> Changes for Build #128 > [Dan Smith <dsmith(a)danplanet.com>] Speed up tests by short-circuiting time.sleep() > Thanks Dan, very appreciated :) 73 de IZ3GME Marco

2 1

[chirp_devel] Build directory
by The Silver Fox 11 Dec '12

11 Dec '12

It seems to be missing from the latest source files. Is this an oversight? Alan - W6ARH

2 2