[chirp_users] New Daily Build
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-10262011/
A list of the changes included in this build (since the last daily) follows:
changeset: 1202:2201c2864c35 tag: tip user: Dan Smith dsmith@danplanet.com date: Tue Oct 25 11:55:54 2011 -0700 files: chirp/kenwood_live.py description: [kenwood] Fix some of the kenwood MODEL definitions so that they match what gets returned during detection.
changeset: 1201:faf37496599c user: Dan Smith dsmith@danplanet.com date: Tue Oct 25 09:45:55 2011 -0700 files: chirp/ft60.py description: [ft60] Make sure to enable display of the memory name on the ft60 if one is set.
On Oct 26, 2011, at 6:01 AM, Dan Smith dsmith@danplanet.com wrote:
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:
All,
Linux Fedora RPMs for the latest chirp-daily build are now available in the KK7DS Ham-Apps yum repository.
To add the repository as a software source, please follow these instructions: http://www.d-rats.com/component/content/article/30-d-rats-yum-repository/
I know it says d-rats, the chirp files are in the same repository
After setting up the repository, open the "Add/Remove Software" tool and go to "software sources" under the system menu. Make sure the "KK7DS Ham Apps Beta Software" line is checked (enabled).
For some reason, the Fedora package manager likes the beta versions better that the daily builds, so you may not see the daily release in the list the first time you update. If you don't see it, open a terminal window and enter: yum update chirp-daily_10262011
Or, If you are running Fedora fc13 or earlier, enter: yum update chirp-daily_10262011-1.fc13
That should install the latest daily build.
Happy Testing! Mike, N0SO
Been awhile but am now having trouble getting a D7A(g) read by chirp. Says the radio is not recognized. Any pointers or know last working version of Chirp would be appreciated.
Kurt KC9LDH
Been awhile but am now having trouble getting a D7A(g) read by chirp. Says the radio is not recognized. Any pointers or know last working version of Chirp would be appreciated.
Hi Kurt, I'm glad you stumbled on this. I don't have a D7 and need someone who does to send me the debug log after the radio isn't recognized. If you could do that, I'd appreciate it.
Thanks!
I'll try to fish it out. Incidentally, I'm running both the Linux and Windows version. The Windows version is XP in a Vbox window running under Linux!. I loaded the specialized driver for the USB port for a D72A into XP and fired up Chirp. It works fine with the D72A in this emulated window! I did program the D7A(g) with a past version of Chirp but ole' Stupidhead here deleted that version. I remember there was a problem before and you said Dan that is was a real simple programming fix.
Kurt KC9LDH
--- On Fri, 10/28/11, Dan Smith dsmith@danplanet.com wrote:
From: Dan Smith dsmith@danplanet.com Subject: Re: [chirp_users] trouble with D7 To: "Discussion of CHIRP" chirp_users@intrepid.danplanet.com Date: Friday, October 28, 2011, 9:57 AM
Been awhile but am now having
trouble getting a D7A(g) read by chirp. Says the radio is not recognized. Any pointers or know last working version of Chirp would be appreciated.
Hi Kurt, I'm glad you stumbled on this. I don't have a D7 and need someone who does to send me the debug log after the radio isn't recognized. If you could do that, I'd appreciate it.
Thanks!
-- Dan Smith www.danplanet.com KK7DS _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
I'll try to fish it out. Incidentally, I'm running both the Linux and Windows version. The Windows version is XP in a Vbox window running under Linux!.
Ah, okay, well, if you run CHIRP from the terminal in Linux, it's even easier to get the debug log:
chirpw > ~/Desktop/debug.log
Then it's on your desktop when you're done. Either that or the log from the Windows box will do just fine.
I loaded the specialized driver for the USB port for a D72A into XP and fired up Chirp. It works fine with the D72A in this emulated window!
Nice!
I did program the D7A(g) with a past version of Chirp but ole' Stupidhead here deleted that version. I remember there was a problem before and you said Dan that is was a real simple programming fix.
Well, this bug is just about the identification of the radio, so it's very good that you're helping me fix this so that you and others will be able to use the latest version (with the latest features) with your radio :)
Thanks!
Here's one:
PC->V71: ID V71->PC: ID TH-D7G --- Exception Dialog: Unsupported model `TH-D7G' --- Traceback (most recent call last): File "/home/ksaves2/chirp-daily-10262011/chirpui/clone.py", line 167, in run cs.radio_class = detect.DETECT_FUNCTIONS[vendor](cs.port) File "/home/ksaves2/chirp-daily-10262011/chirp/detect.py", line 113, in detect_kenwoodlive_radio raise errors.RadioError("Unsupported model `%s'" % r_id) RadioError: Unsupported model `TH-D7G' ----------------------------
Here's another:
The first line I had the wrong port selected. The second is the correct port.
CHIRP daily-10262011 on Linux - PC->V71: ID V71->PC: PC->V71: ID V71->PC: PC->V71: ID V71->PC: PC->V71: ID V71->PC: --- Exception Dialog: Unable to probe radio model --- Traceback (most recent call last): File "/home/ksaves2/chirp-daily-10262011/chirpui/clone.py", line 167, in run cs.radio_class = detect.DETECT_FUNCTIONS[vendor](cs.port) File "/home/ksaves2/chirp-daily-10262011/chirp/detect.py", line 103, in detect_kenwoodlive_radio raise errors.RadioError("Unable to probe radio model") RadioError: Unable to probe radio model ---------------------------- PC->V71: ID V71->PC: ID TH-D7G --- Exception Dialog: Unsupported model `TH-D7G' --- Traceback (most recent call last): File "/home/ksaves2/chirp-daily-10262011/chirpui/clone.py", line 167, in run cs.radio_class = detect.DETECT_FUNCTIONS[vendor](cs.port) File "/home/ksaves2/chirp-daily-10262011/chirp/detect.py", line 113, in detect_kenwoodlive_radio raise errors.RadioError("Unsupported model `%s'" % r_id) RadioError: Unsupported model `TH-D7G' ----------------------------
--- On Fri, 10/28/11, Dan Smith dsmith@danplanet.com wrote:
From: Dan Smith dsmith@danplanet.com Subject: Re: [chirp_users] trouble with D7 To: "Discussion of CHIRP" chirp_users@intrepid.danplanet.com Date: Friday, October 28, 2011, 10:09 AM
I'll try to fish it out.
Incidentally, I'm running both the Linux
and Windows version. The Windows version is XP
in a Vbox window
running under Linux!.
Ah, okay, well, if you run CHIRP from the terminal in Linux, it's even easier to get the debug log:
chirpw > ~/Desktop/debug.log
Then it's on your desktop when you're done. Either that or the log from the Windows box will do just fine.
I loaded the specialized driver for the USB port for a
D72A into XP
and fired up Chirp. It works fine with the D72A
in this emulated
window!
Nice!
I did program the D7A(g) with a past version of Chirp but ole' Stupidhead here deleted that
version. I
remember there was a problem before and you said Dan
that is was a
real simple programming fix.
Well, this bug is just about the identification of the radio, so it's very good that you're helping me fix this so that you and others will be able to use the latest version (with the latest features) with your radio :)
Thanks!
-- Dan Smith www.danplanet.com KK7DS _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
--- Exception Dialog: Unsupported model `TH-D7G' ---
Okay, got it. I've pushed a change up which will go out in tomorrow's daily build. If you could try that and report back, I'd appreciate it.
Thanks!
D7Ag is back online with the 10/29 version. Linux version is fine and the Windows version works on my XP system. Using Vbox on a Slackware system so even though XP is in a Linux environment, Chirp runs fine.
Kurt KC9LDH
--- On Fri, 10/28/11, Dan Smith dsmith@danplanet.com wrote:
Unsupported model `TH-D7G' ---
Okay, got it. I've pushed a change up which will go out in tomorrow's daily build. If you could try that and report back, I'd appreciate it.
Thanks!
-- Dan Smith www.danplanet.com KK7DS
I've got this error on a previously tested PC (last time was at June). Latest daily build on. D-RATS works fine.
Here is the debug.log:
CHIRP daily-10312011 on WinXP Auto-detected Icom IC-2820H on COM2 Clone thread started -- Exception: -- Traceback (most recent call last): File "chirpui\clone.pyo", line 224, in run File "chirp\icf.pyo", line 403, in sync_in File "chirp\icf.pyo", line 213, in clone_from_radio File "chirp\icf.pyo", line 132, in get_model_data RadioError: Unexpected response from radio ------ Clone failed: Unexpected response from radio Clone thread ended --- Exception Dialog: Unexpected response from radio --- None ----------------------------
I've missed something?
73 de Leo IZ5FSA
Hi Dan. I'm using the data port. I've always used it and I've never had this problem. D-RATS works fine, CHIRP don't work. I've tried to look at my menu configuration (such as DATA TX and GPS) but it still don't work! I don't think its a CHIRP problem... with CS-2820 I have the same problem.
73 de Leo IZ5FSA
Il 04/11/2011 00:30, Dan Smith ha scritto:
RadioError: Unexpected response from radio
Hmm, seems to work here (I just tested). Are you using the data port or the speaker jack?
participants (4)
-
Dan Smith -
IZ5FSA＠gmail -
Kurt Savegnago -
Mike Heitmann