August 2011 - Users - lists.chirpmyradio.com

[chirp_users] Need help with an Alinco DRx35 radio
by Dan Smith 16 Aug '11

16 Aug '11

Hi all, I need some help from someone with an Alinco DRx35 radio (DR135, DR235, DR435, etc). I need to know if the Mode (FM/NFM) setting in chirp is properly reflected in your radio, or if it seems to toggle the power level instead. Also, if you could send me an image where the "scan skip" flag is set on one or more of the memories, that would be very helpful. Thanks! -- Dan Smith www.danplanet.com KK7DS

2 2

[chirp_users] Release 0.1.12 soon?
by Dan Smith 16 Aug '11

16 Aug '11

Hi all, A lot has changed since the 0.1.11 release. Many bugs have been fixed, five new radios are supported, and plenty of core application features have been added. I think it's about time for an 0.1.12 release to the "masses". What do you think? Is anyone sitting on a particular bug or missing piece of functionality that we should address before making a release? Please, let me know what you think! Thanks! -- Dan Smith www.danplanet.com KK7DS

2 2

[chirp_users] New Daily Build
by Dan Smith 16 Aug '11

16 Aug '11

Greetings, A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location: http://trac.chirp.danplanet.com/chirp_daily/daily-08162011/ A list of the changes included in this build (since the last daily) follows: changeset: 1125:8d480df45561 tag: tip user: Dan Smith <dsmith(a)danplanet.com> date: Mon Aug 15 16:55:06 2011 -0700 files: chirp/xml.py description: [xml] Fix valid tone modes on .chirp driver

2 2

[chirp_users] testing new CHIRP with new radios
by jim gibbens 15 Aug '11

15 Aug '11

Hello- Dan has kindly added two new radios to the list at my request: the Yaesu FT-2800m and the Kenwood TH-K2. I also have an Icom W32A and have been testing CHIRP with it. I'm using the 8/11 daily build. My approach to testing is as follows. 1) Use CHIRP to read a "known good" parameter set from the radio and see if the data appears to be correct. 2) Use CHIRP to write the same file back to the radio and see if the radio works as it did with the original parameter set. 3) Use CHIRP to create a common file and write it to all three radios and verify that the radios works correctly with the new file FT-2800m CHIRP appears to pass Step 1&2, have not tried 3 yet TH-K2 CHIRP appear to export the Tone field from the radio correctly, but does not export the Tone field from the radio download to csv or chirp files; in those export files, the Tone field is left blank. IC-W32A The Tone fields as imported by CHIRP from the radio are all changed to 67 Hz, unless the tone is 67 Hz, in which case the Tone field is left blank. I've attached the .img files as downloaded from the radios, the chirp file exported after the download, and .mcp and .icw32 files from the Kenwood and RT systems programs that I have used for the THK@ and W32A in the past. Regards, Jim Givens KJ7F

2 1

[chirp_users] Yaesu FT-857/ft-897 support
by David Ranch 13 Aug '11

13 Aug '11

Hello Dan, Curious, do you think it would be difficult to add support for the FT857/897? --David

2 2

[chirp_users] IC-92ad
by bRADY PALMQUIST 13 Aug '11

13 Aug '11

I'm trying to use Chirp with an ICOM IC-92AD, OPC-1797 and a Kawamall OPC-478 cable. First of all, is that the right hardware? If I use version .1.10, it will run and look like it's getting memories, but they are all blank. If I use version .1.11, it says something to the effect of "Can't determine radio model" I've tried it on my XP and Windows 7 machines. Drivers seem to be loaded OK. I have the GPS settings disabled...(Tx mode and auto tx). What else should I check? Is there a debug or test option available? Brady K0UC

2 1

[chirp_users] New Daily Build
by Dan Smith 12 Aug '11

12 Aug '11

Greetings, A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location: http://trac.chirp.danplanet.com/chirp_daily/daily-08112011/ A list of the changes included in this build (since the last daily) follows: changeset: 1124:36d12727733f tag: tip user: Dan Smith <dsmith(a)danplanet.com> date: Wed Aug 10 16:18:49 2011 -0700 files: chirp/alinco.py description: [drx35] Fix alinco frequency calculation since integral hertz

2 1

[chirp_users] New Daily Build
by Dan Smith 10 Aug '11

10 Aug '11

Greetings, A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location: http://trac.chirp.danplanet.com/chirp_daily/daily-08102011/ A list of the changes included in this build (since the last daily) follows: changeset: 1123:3753d8882cd0 tag: tip user: Dan Smith <dsmith(a)danplanet.com> date: Tue Aug 09 18:34:24 2011 -0700 files: chirp/bitwise.py description: Make bitwise's repr() use os.linesep so that highlighting works on win32 changeset: 1122:8db4b63b4e4b user: Dan Smith <dsmith(a)danplanet.com> date: Tue Aug 09 17:54:04 2011 -0700 files: chirpui/mainapp.py chirpui/memedit.py description: Add Help->Enable Developer Functions This enables two options in the context menu of a memory: 1. Show Raw Memory - Dumps the raw hex or contextual memory information to a dialog box 2. Diff Raw Memories - Dumps two of the above and diff's them in the dialog box I do this constantly when writing and debugging a driver and this makes it a little easier to do small one-off checks. changeset: 1121:1ad41a6245cf user: Dan Smith <dsmith(a)danplanet.com> date: Tue Aug 09 16:59:17 2011 -0700 files: chirp/alinco.py chirp/ft2800.py chirp/ft7800.py chirp/ic2100.py chirp/ic2200.py chirp/ic2720.py chirp/ic2820.py chirp/icq7.py chirp/ict70.py chirp/icw32.py chirp/id800.py chirp/id880.py chirp/vx3.py chirp/vx5.py chirp/vx6.py chirp/vx7.py chirp/vx8.py chirp/wouxun.py description: Make the bitwise-using radios dump contextual raw memories changeset: 1120:4cf7fa80b03f user: Dan Smith <dsmith(a)danplanet.com> date: Tue Aug 09 16:58:41 2011 -0700 files: chirp/bitwise.py description: Fix DeprecationWarning when overflowing the argument to struct.pack() changeset: 1119:99fe3409ea72 user: Dan Smith <dsmith(a)danplanet.com> date: Tue Aug 09 16:46:09 2011 -0700 files: chirp/bitwise.py description: Clean up the bitwise repr() format a bit changeset: 1118:98bb35e175ff user: Dan Smith <dsmith(a)danplanet.com> date: Tue Aug 09 16:09:46 2011 -0700 files: tests/images/ft2800.img description: [ft2800] Add image for testing changeset: 1117:43efd847a8fe user: Dan Smith <dsmith(a)danplanet.com> date: Tue Aug 09 15:50:23 2011 -0700 files: chirp/directory.py chirp/ft2800.py description: [ft2800] Add Yaesu FT-2800M support changeset: 1116:c636d97908ed user: Dan Smith <dsmith(a)danplanet.com> date: Tue Aug 09 15:50:09 2011 -0700 files: chirpui/importdialog.py description: Make the "auto" button on import enumerate only memories we're going to import (instead of counting all the ones we're not. This makes it easier to import a dual-band layout to a single-bander with fewer memories. changeset: 1115:1e9ba9ed3576 user: Dan Smith <dsmith(a)danplanet.com> date: Tue Aug 09 14:47:46 2011 -0700 files: chirp.py description: Make chirp.py print whatever get_raw_memory() returned, if it's all printable changeset: 1114:2cd447dba280 user: Dan Smith <dsmith(a)danplanet.com> date: Tue Aug 09 14:47:12 2011 -0700 files: chirp/bitwise.py description: Support repr() on bitwise data structures for contextual diff'ing changeset: 1113:6f65a3f60bc4 user: Dan Smith <dsmith(a)danplanet.com> date: Mon Aug 08 18:56:44 2011 -0700 files: chirpui/clone.py description: Fix restoring last model

1 0

[chirp_users] Thoughts after looking at the most recent build
by Ron McKenzie 09 Aug '11

09 Aug '11

Dan, I'm testing Chirp with UV-3R files. 1. Why did you delete the Name field? I would find this very helpful for organizing and editing the data in my .CVS file. From our previous email conversation, I understood you were going to retain it in the CSV file and only drop it when writing data to the dual_band.dat file for uploading into the radio? 2. Vero/Baofeng uses one "menu" for manually setting the Tx-Code (transmitted CTSS or DTCCS code) and a second "menu" for manually setting the Rx-Code (received or SQL tone code, either CTSS or DTCCS). Chirp has separate fields for the CTSS (Tone) and the DTCCS (DTCS Code) (defaulting to the lowest code value for whichever code type is not used). In addition, Chirp has a field Tone Mode with values of None, Tone (CTSS Tx only), ToneSql (CTSS Ts & Rx?), and DTCS. The "inputs" suggest that a repeater using CTSS will always have to hear a user's Tx-Code and it may or may not send back using a CTSS code. On the other hand, if the repeater is using DTCCS, then, it will require that code (my Tx-code) and it will always broadcast using that same DTCCS code (my Rx-code). Some questions to help increase my knowledge of current practices: 1. Is the above analysis correct? 2. Is this juxtaposition of data and information types done as a convenience in light of the requirements of earlier radios that Chirp was programmed for? Or, it it something that can be altered? 2. Is a repeater operator precluded from selecting different CTSS or DTCCS codes for Rx and Tx?** 3. Is a repeater operator precluded from selecting CTSS for the user's Tx Code and DTCCS for the user's Rx Code (or vice versa)?** 3. Can an operator set a repeater up to use DTCCS on what it receives (the user's Tx Code) and transmit without a code?** ** (Assuming the operator's choices do not conflict with any other repeaters sharing the frequency pair within a reasonable distance of the subject repeater.) I don't see where the UV-3R uses the DTCS Polarity information at all; it does not appear to be an option as I read my .dat file. Thanks & 73 de KK4DBR, Ron EL98fk Orange Cty Windermere, FL

3 7

[chirp_users] Will Chirp be enhanced to mandle other info in my dat file?
by Ron McKenzie 09 Aug '11

09 Aug '11

At some point will chirp be enhanced let me maintain the following fields in my UV-3R: 1. Squelch level 2. VOX Level 3. TOT (Time Out Timer, limiting Tx time) 4. Battery Saver 5. Key Tone (Beep) 6. BCL (Broadcast Lock Out, prevents me from xmitting if someone with a different PL Tone (CTSS) or DTCCS Code is already using the frequency pair) 7. Scan 8. Back light Thanks & 73 de KK4DBR Ron

2 2