[chirp_users] Chirp IndexError
I've installed chirp as per the instructions for OS X. It starts up, however when following the beginner's guide I get the following error when selecting Radio, Download from Radio. This doesn't appear to be a known issue. Are there any suggestions to get this working?
$ sh chirp_osx.sh chirpw:55: PangoWarning: error opening config file '../Resources/etc/pango/pangorc': No such file or directory
a.show() Wed May 4 12:28:28 burakkuhoru.local Python[49616] <Error>: CGContextSetFont: invalid context 0x0 Wed May 4 12:28:28 burakkuhoru.local Python[49616] <Error>: CGContextSetFontSize: invalid context 0x0 Wed May 4 12:28:28 burakkuhoru.local Python[49616] <Error>: CGContextSetTextMatrix: invalid context 0x0 Wed May 4 12:28:28 burakkuhoru.local Python[49616] <Error>: CGContextClearRect: invalid context 0x0 Wed May 4 12:28:28 burakkuhoru.local Python[49616] <Error>: CGContextSetRGBFillColor: invalid context 0x0 Wed May 4 12:28:28 burakkuhoru.local Python[49616] <Error>: CGContextShowGlyphsAtPoint: invalid context 0x0 Traceback (most recent call last): File "/Users/benkrueger/CHIRP/chirp-0.1.11/chirpui/mainapp.py", line 552, in mh self.do_download(*args) File "/Users/benkrueger/CHIRP/chirp-0.1.11/chirpui/mainapp.py", line 283, in do_download d = clone.CloneSettingsDialog(parent=self) File "/Users/benkrueger/CHIRP/chirp-0.1.11/chirpui/clone.py", line 140, in __init__ self.__make_ui(settings) File "/Users/benkrueger/CHIRP/chirp-0.1.11/chirpui/clone.py", line 115, in __make_ui self.__port = self.__make_port(settings and settings.port or None) File "/Users/benkrueger/CHIRP/chirp-0.1.11/chirpui/clone.py", line 61, in __make_port port = ports[0] IndexError: list index out of range
Running OS X 10.6.7 $ uname -a Darwin burakkuhoru.local 10.7.0 Darwin Kernel Version 10.7.0: Sat Jan 29 15:17:16 PST 2011; root:xnu-1504.9.37~1/RELEASE_I386 i386
I've installed chirp as per the instructions for OS X. It starts up, however when following the beginner's guide I get the following error when selecting Radio, Download from Radio. This doesn't appear to be a known issue. Are there any suggestions to get this working?
I'm pretty sure this was fixed in a recent daily build, but that's not accessible via that script of course.
Could you download the latest .tar.gz from here:
http://trac.chirp.danplanet.com/chirp_daily
and then do this:
$ tar xzf chirp*gz $ cd chirp*gz $ /opt/kk7ds/bin/python2.5 chirpw
I guess I need to modify that script to let you specify the daily version :)
That did the trick. Any suggestions on what serial port to use with the suggested eBay USB cable to a VX-6?
On May 4, 2011, at 1:56 PM, Dan Smith wrote:
I've installed chirp as per the instructions for OS X. It starts up, however when following the beginner's guide I get the following error when selecting Radio, Download from Radio. This doesn't appear to be a known issue. Are there any suggestions to get this working?
I'm pretty sure this was fixed in a recent daily build, but that's not accessible via that script of course.
Could you download the latest .tar.gz from here:
http://trac.chirp.danplanet.com/chirp_daily
and then do this:
$ tar xzf chirp*gz $ cd chirp*gz $ /opt/kk7ds/bin/python2.5 chirpw
I guess I need to modify that script to let you specify the daily version :)
-- Dan Smith www.danplanet.com KK7DS
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
That did the trick. Any suggestions on what serial port to use with the suggested eBay USB cable to a VX-6?
I'm sure that's a Prolific 2303 chip, but I'm not sure if you need a driver for it or not. I'm not sure what device it shows up as under MacOS. Something like /dev/cu.usbserial or similar. Hopefully you can google/poke around for details on that brand/model and find what you need.
On Wed, May 4, 2011 at 15:37, Dan Smith dsmith@danplanet.com wrote:
That did the trick. Any suggestions on what serial port to use with the suggested eBay USB cable to a VX-6?
I'm sure that's a Prolific 2303 chip, but I'm not sure if you need a driver for it or not. I'm not sure what device it shows up as under MacOS. Something like /dev/cu.usbserial or similar. Hopefully you can google/poke around for details on that brand/model and find what you need.
If it's Prolific (or one of the Chinese counterfeit Prolific chips that are so common these days), it'll be something like /dev/cu.pl2303-xxxx, I think. Once you have the drivers installed, and plug in the USB cable, you can find it with this command:
ls -t /dev/cu.* | head -n 1
That lists your serial ports in order of most recent to oldest, and returns only the first one in the list. If you just now plugged in the USB cable, it will surely be the newest serial port on the system.
Tom KD7LXL
It is the Prolific chipset and the drivers appear to work, having created /dev/cu.usbserial. I'm sad to report that this is helpful, but I'm still at a point where things don't work. The beginner's guide perhaps assumes that the radio is already set up to be cloned? I've tried cloning with the radio off, on, in clone mode, and in clone mode ready to TX. All of these results fail. The VX-6R is a pretty common radio, so I can't be the first user to have tried this and run into issues. I'm looking for further suggestions, and I'd be happy to update the beginner's guide to be more comprehensive for new users.
On May 4, 2011, at 2:46 PM, Tom Hayward wrote:
On Wed, May 4, 2011 at 15:37, Dan Smith dsmith@danplanet.com wrote:
That did the trick. Any suggestions on what serial port to use with the suggested eBay USB cable to a VX-6?
I'm sure that's a Prolific 2303 chip, but I'm not sure if you need a driver for it or not. I'm not sure what device it shows up as under MacOS. Something like /dev/cu.usbserial or similar. Hopefully you can google/poke around for details on that brand/model and find what you need.
If it's Prolific (or one of the Chinese counterfeit Prolific chips that are so common these days), it'll be something like /dev/cu.pl2303-xxxx, I think. Once you have the drivers installed, and plug in the USB cable, you can find it with this command:
ls -t /dev/cu.* | head -n 1
That lists your serial ports in order of most recent to oldest, and returns only the first one in the list. If you just now plugged in the USB cable, it will surely be the newest serial port on the system.
Tom KD7LXL _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
It is the Prolific chipset and the drivers appear to work, having created /dev/cu.usbserial. I'm sad to report that this is helpful, but I'm still at a point where things don't work. The beginner's guide perhaps assumes that the radio is already set up to be cloned? I've tried cloning with the radio off, on, in clone mode, and in clone mode ready to TX. All of these results fail. The VX-6R is a pretty common radio, so I can't be the first user to have tried this and run into issues. I'm looking for further suggestions, and I'd be happy to update the beginner's guide to be more comprehensive for new users.
Well, first off, the beginner's guide comes from a time where CHIRP only supported Icom radios. Unlike Yaesu radios, Icom radios require no special incantation to get them to initiate their clone, so the procedure is purely software. It definitely needs some updating.
The procedure you need to follow is this:
1. Turn on the radio in clone mode 2. In chirp, go to "download from radio", choose your serial port, and hit okay. Wait for the box with the yet-to-be-filled progress bar to appear 3. Hit the button on your VX-6 that puts it into TX mode. 4. Beer (hopefully)
The trick is to make sure that the receiving side is "ready" before you start the transmitter. When programming back to the radio, reverse the steps and make sure that the radio is in RX mode before you hit okay on the chirp window to start the procedure.
Unfortunately, Yaesus are quite intolerant of deviations in the procedure and don't provide either side with an indication of the state of the other. Makes it kinda clunky.
Let me know how you make out!
On May 4, 2011, at 4:02 PM, Dan Smith wrote:
It is the Prolific chipset and the drivers appear to work, having created /dev/cu.usbserial. I'm sad to report that this is helpful, but I'm still at a point where things don't work. The beginner's guide perhaps assumes that the radio is already set up to be cloned? I've tried cloning with the radio off, on, in clone mode, and in clone mode ready to TX. All of these results fail. The VX-6R is a pretty common radio, so I can't be the first user to have tried this and run into issues. I'm looking for further suggestions, and I'd be happy to update the beginner's guide to be more comprehensive for new users.
Well, first off, the beginner's guide comes from a time where CHIRP only supported Icom radios. Unlike Yaesu radios, Icom radios require no special incantation to get them to initiate their clone, so the procedure is purely software. It definitely needs some updating.
The procedure you need to follow is this:
- Turn on the radio in clone mode
- In chirp, go to "download from radio", choose your serial port, and hit okay. Wait for the box with the yet-to-be-filled progress bar to appear
- Hit the button on your VX-6 that puts it into TX mode.
- Beer (hopefully)
That was my best guess for the proper procedure.
After clicking Okay, it reports "Cloning" and I direct the radio to start "TX". The console reports "Clone thread started". After a moment, the radio shows "ERROR", and Chirp shows "Cloning from radio" and waits for a few minutes.
After a few minutes, an error popup reports "An error has occured, ord() expected a character, but string of length 0 found". Here's the entire console stack trace:
Clone thread started
-- Exception: -- Traceback (most recent call last): File "/Users/benkrueger/CHIRP/chirp-daily-05042011/chirpui/clone.py", line 217, in run self.__radio.sync_in() File "/Users/benkrueger/CHIRP/chirp-daily-05042011/chirp/yaesu_clone.py", line 178, in sync_in self._mmap = clone_in(self) File "/Users/benkrueger/CHIRP/chirp-daily-05042011/chirp/yaesu_clone.py", line 69, in clone_in data += chunk_read(pipe, block, radio.status_fn) File "/Users/benkrueger/CHIRP/chirp-daily-05042011/chirp/yaesu_clone.py", line 53, in chunk_read status.cur = len(data) CloneCancelledException ------ Clone failed: Clone thread ended Clone thread started
Clone completed in 269 seconds -- Exception: -- Traceback (most recent call last): File "/Users/benkrueger/CHIRP/chirp-daily-05042011/chirpui/clone.py", line 217, in run self.__radio.sync_in() File "/Users/benkrueger/CHIRP/chirp-daily-05042011/chirp/yaesu_clone.py", line 179, in sync_in self.check_checksums() File "/Users/benkrueger/CHIRP/chirp-daily-05042011/chirp/yaesu_clone.py", line 172, in check_checksums if checksum.get_existing(self._mmap) != \ File "/Users/benkrueger/CHIRP/chirp-daily-05042011/chirp/yaesu_clone.py", line 140, in get_existing return ord(mmap[self._address]) TypeError: ord() expected a character, but string of length 0 found ------ Clone failed: ord() expected a character, but string of length 0 found Clone thread ended --- Exception Dialog: ord() expected a character, but string of length 0 found --- None ---------------------------- Wed May 4 16:09:04 burakkuhoru.local Python[2727] <Error>: CGContextSetFont: invalid context 0x0 Wed May 4 16:09:04 burakkuhoru.local Python[2727] <Error>: CGContextSetFontSize: invalid context 0x0 Wed May 4 16:09:04 burakkuhoru.local Python[2727] <Error>: CGContextSetTextMatrix: invalid context 0x0 Wed May 4 16:09:04 burakkuhoru.local Python[2727] <Error>: CGContextClearRect: invalid context 0x0 Wed May 4 16:09:04 burakkuhoru.local Python[2727] <Error>: CGContextSetRGBFillColor: invalid context 0x0 Wed May 4 16:09:04 burakkuhoru.local Python[2727] <Error>: CGContextShowGlyphsAtPoint: invalid context 0x0
After a few minutes, an error popup reports "An error has occured, ord() expected a character, but string of length 0 found". Here's the entire console stack trace:
That sounds like either (a) you're not using the right device for that serial port, or (b) the connector isn't fully seated into the radio and thus you're getting no data through.
You might open a serial console on that device. At any baud rate, you should see an echo of every key you type. If local echo is enabled in your terminal, then you'll see double.
If you keep the terminal at 19200 baud and hit the clone TX button on your radio, you should see it fire "AH021" or something similar to the terminal. If it doesn't, then you know that it's between your machine and the radio somewhere and not CHIRP-related.
On May 4, 2011, at 4:23 PM, Dan Smith wrote:
After a few minutes, an error popup reports "An error has occured, ord() expected a character, but string of length 0 found". Here's the entire console stack trace:
That sounds like either (a) you're not using the right device for that serial port, or (b) the connector isn't fully seated into the radio and thus you're getting no data through.
You might open a serial console on that device. At any baud rate, you should see an echo of every key you type. If local echo is enabled in your terminal, then you'll see double.
If you keep the terminal at 19200 baud and hit the clone TX button on your radio, you should see it fire "AH021" or something similar to the terminal. If it doesn't, then you know that it's between your machine and the radio somewhere and not CHIRP-related.
Well, I get characters echoed, but no output from the radio in TX mode. I'll have to dig out another machine to see if this is a driver issue or cable issue. Thanks for the help!
Well, I get characters echoed, but no output from the radio in TX mode. I'll have to dig out another machine to see if this is a driver issue or cable issue. Thanks for the help!
Okay, well, if you're getting characters echoed, that should mean that the USB bit (and drivers) are working, as well as the USB-to-serial chip inside that hood. The TX and RX lines on the RS232 side are tied together, which makes it echo. So, that should eliminate everything up until the bit of cable that runs to the connector and the radio. I'd say it's clear that it's something in one of those pieces.
Hopefully you can get that resolved, and I look forward to hearing about it :)
On May 4, 2011, at 5:05 PM, Dan Smith wrote:
Well, I get characters echoed, but no output from the radio in TX mode. I'll have to dig out another machine to see if this is a driver issue or cable issue. Thanks for the help!
Okay, well, if you're getting characters echoed, that should mean that the USB bit (and drivers) are working, as well as the USB-to-serial chip inside that hood. The TX and RX lines on the RS232 side are tied together, which makes it echo. So, that should eliminate everything up until the bit of cable that runs to the connector and the radio. I'd say it's clear that it's something in one of those pieces.
Hopefully you can get that resolved, and I look forward to hearing about it :)
Got it. Cheap chinese parts often have "loose" tolerances. I had the cable turned finger tight in the radio, but it needed to be uncomfortably cranked down nearly another complete turn. All good now. Thanks for the troubleshooting!
Got it. Cheap chinese parts often have "loose" tolerances. I had the cable turned finger tight in the radio, but it needed to be uncomfortably cranked down nearly another complete turn. All good now. Thanks for the troubleshooting!
Yeah, but at least they're cheap :P
Excellent news!
participants (3)
-
Benjamin Krueger -
Dan Smith -
Tom Hayward