[chirp_users] more help with Mac OS
I'm sure that you're busy with d-rats and getting ready for Dayton, but I finally got back to working on getting Chirp working now that I have a need to move data from an ic-92 to an ic-91 :-)
I snagged the source to 0.1.9 final and tried it both with my fink install and my darwin ports install. neither works, but they do both fail with the exact same error when I pick "Radio -> connect to an ic9x":
a.show() Traceback (most recent call last): File "/Users/fligor/bin/chirp-0.1.9/chirpui/mainapp.py", line 430, in mh self.do_open9x(ic9x.IC9xRadioA) File "/Users/fligor/bin/chirp-0.1.9/chirpui/mainapp.py", line 123, in do_open9x rtype="ic9x") File "/Users/fligor/bin/chirp-0.1.9/chirpui/clone.py", line 70, in __init__ self.port = miscwidgets.make_choice(ports, True, ports[0]) IndexError: list index out of range
I never get the dialog box that lets you choose your radio settings.
I tried A B and B B, neither worked, and I did make sure the radio's main was on the "B" side.
I even get the same message with the Apple's built in python using
export PYTHONPATH=/opt/local/lib/python2.5/site-packages
which worked for another user. It's good that they all fail the same way, it's annoying that they all fail :-)
You'd previously thought you knew what this was and had planned on fixing it, I just got side tracked and never checked. Something about not knowing about a serial port and getting confused. as a work around, is there a config file I can stash somewhere that fills it in about the serial port to get me going?
I couldn't find anything on the config file format at the wiki so that I could just make my own. Let me know if you also want to see this on trac as well.
thanks,
-debbie, N9DN
Hi Debbie,
I'm sure that you're busy with d-rats and getting ready for Dayton, but I finally got back to working on getting Chirp working now that I have a need to move data from an ic-92 to an ic-91 :-)
Yeah, I'm slammed at the moment with a variety of things.
I snagged the source to 0.1.9 final and tried it both with my fink install and my darwin ports install. neither works, but they do both fail with the exact same error when I pick "Radio -> connect to an ic9x":
a.show() Traceback (most recent call last): File "/Users/fligor/bin/chirp-0.1.9/chirpui/mainapp.py", line 430, in mh self.do_open9x(ic9x.IC9xRadioA) File "/Users/fligor/bin/chirp-0.1.9/chirpui/mainapp.py", line 123, in do_open9x rtype="ic9x") File "/Users/fligor/bin/chirp-0.1.9/chirpui/clone.py", line 70, in __init__ self.port = miscwidgets.make_choice(ports, True, ports[0]) IndexError: list index out of range
I never get the dialog box that lets you choose your radio settings.
I tried A B and B B, neither worked, and I did make sure the radio's main was on the "B" side.
I even get the same message with the Apple's built in python using
export PYTHONPATH=/opt/local/lib/python2.5/site-packages
which worked for another user. It's good that they all fail the same way, it's annoying that they all fail :-)
You'd previously thought you knew what this was and had planned on fixing it, I just got side tracked and never checked. Something about not knowing about a serial port and getting confused. as a work around, is there a config file I can stash somewhere that fills it in about the serial port to get me going?
I couldn't find anything on the config file format at the wiki so that I could just make my own. Let me know if you also want to see this on trac as well.
This looks to me like the same issue we've had in the past with MacOS where it doesn't find any ports and croaks on that fact. I fixed it in D-RATS but might have forgotten to fix it in CHIRP as well. If you fool it into thinking there is a serial device, it might be happy.
Something like: "touch /dev/tty.usbserial9" or something will give it something to populate that list with.
Sorry, not much of an answer, but if this doesn't help, I'll try to explain more and/or fix it later on :)
Hi Dan, On May 15, 2009, at 5:40, Dan Smith wrote:
This looks to me like the same issue we've had in the past with MacOS where it doesn't find any ports and croaks on that fact. I fixed it in D-RATS but might have forgotten to fix it in CHIRP as well. If you fool it into thinking there is a serial device, it might be happy.
Something like: "touch /dev/tty.usbserial9" or something will give it something to populate that list with.
well touch doesn't like /dev, but you can use ln -s but adding tty.usbserial9 as a link to tty.KeySerial1 doesn't seem to help any at all.
Sorry, not much of an answer, but if this doesn't help, I'll try to explain more and/or fix it later on :)
sounds good to me!
thanks!
Okay, sometimes I'm just dense.
I made two code changes, which took care of my problem (I probably only needed one, but hey...)
in platform.py on line 219:
return sorted(glob.glob("/dev/ttyS*") + glob.glob("/dev/ttyUSB*") + glob.glob("/dev/cu.usbser*") + glob.glob("/dev/tty.Key*"))
I added the /dev/tty.Key* option to go with the other ones had I looked this up, a symlink to /dev/ttyUSB* (without the "." between tty and USB) would have probably worked too.
and in ic9x.py on line 306 I replaced the default serial port you had listed with mine:
r = IC9xRadioB(serial.Serial(port="/dev/tty.KeySerial1",
I think perhaps that the first one is what the overall code needs, but the second one is what showed up in my serial port choice window (which I got to with no error) and since I found it first and it worked I left it.
On May 17, 2009, at 21:34, Debbie Fligor wrote:
Hi Dan, On May 15, 2009, at 5:40, Dan Smith wrote:
This looks to me like the same issue we've had in the past with MacOS where it doesn't find any ports and croaks on that fact. I fixed it in D-RATS but might have forgotten to fix it in CHIRP as well. If you fool it into thinking there is a serial device, it might be happy.
Something like: "touch /dev/tty.usbserial9" or something will give it something to populate that list with.
well touch doesn't like /dev, but you can use ln -s but adding tty.usbserial9 as a link to tty.KeySerial1 doesn't seem to help any at all.
Sorry, not much of an answer, but if this doesn't help, I'll try to explain more and/or fix it later on :)
sounds good to me!
thanks!
I made two code changes, which took care of my problem (I probably only needed one, but hey...)
in platform.py on line 219:
return sorted(glob.glob("/dev/ttyS*") + glob.glob("/dev/ttyUSB*") + glob.glob("/dev/cu.usbser*") + glob.glob("/dev/tty.Key*"))
I added the /dev/tty.Key* option to go with the other ones had I looked this up, a symlink to /dev/ttyUSB* (without the "." between tty and USB) would have probably worked too.
and in ic9x.py on line 306 I replaced the default serial port you had listed with mine:
r = IC9xRadioB(serial.Serial(port="/dev/tty.KeySerial1",
Ah, great! Yeah, the first one should be the only one you actually needed, but the other won't hurt anything.
Sorry for the lack of response here, I've just been slammed lately. I hope to return to some sort of normalcy later this week or early next week.
On May 19, 2009, at 5:56, Dan Smith wrote:
I made two code changes, which took care of my problem (I probably only needed one, but hey...)
in platform.py on line 219:
return sorted(glob.glob("/dev/ttyS*") + glob.glob("/dev/ttyUSB*") + glob.glob("/dev/cu.usbser*") + glob.glob("/dev/tty.Key*"))
I added the /dev/tty.Key* option to go with the other ones had I looked this up, a symlink to /dev/ttyUSB* (without the "." between tty and USB) would have probably worked too.
and in ic9x.py on line 306 I replaced the default serial port you had listed with mine:
r = IC9xRadioB(serial.Serial(port="/dev/tty.KeySerial1",Ah, great! Yeah, the first one should be the only one you actually needed, but the other won't hurt anything.
Sorry for the lack of response here, I've just been slammed lately. I hope to return to some sort of normalcy later this week or early next week.
So I finally came back to this, and found the same problem. of course I didn't recall the keyspan problem so I busted my python2.6 install messing around :-)
A lot of messing around with python2.6 and a spiffy new python2.7 install later, and it's all good now, once I made the same two changes above to chirp v 0.1.11b4 (although the line numbers are no longer a match)
and a dumb question - having not paid much attention, is there a way to get the "A" side of a 92AD to export?
-debbie
and a dumb question - having not paid much attention, is there a way to get the "A" side of a 92AD to export?
When you "download from radio" on the 92AD, you should get two tabs that pop up. You can select the A tab and then Radio->Export. Is it not behaving?
On Feb 9, 2011, at 20:47, Dan Smith wrote:
and a dumb question - having not paid much attention, is there a way to get the "A" side of a 92AD to export?
When you "download from radio" on the 92AD, you should get two tabs that pop up. You can select the A tab and then Radio->Export. Is it not behaving?
I only got a "B" tab.
-- Dan Smith www.danplanet.com KK7DS _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
On Feb 9, 2011, at 21:15, Dan Smith wrote:
I only got a "B" tab.
Then I need a debug log. I don't think it gets converted to a log file on OSX, so if you could start it from the command line and capture the stdio:
chirpw >/tmp/debug.log 2>&1
Thanks!
same results, this is all the debug.log file had in it:
962 mnementh> more debug.log chirpw:48: PangoWarning: error opening config file '../Resources/etc/pango/pangorc': No such file or directory
a.show() Unexpected response from radio Switching from 4800 to 38400 Auto-detected Icom IC-91/92AD on /dev/tty.KeySerial1 Sending magic Bank Index supported: True Bank supported: True DTCS Code supported: True DTCS Pol supported: True Mode supported: True Offset supported: True Name supported: True Tune Step supported: True Name supported: True ToneSql supported: True Cross Mode supported: False Sending magic
I started chirpw, let it read in all the memories until it finished and then quit from the program. I only got a "B" tab.
-- Dan Smith www.danplanet.com KK7DS _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
I started chirpw, let it read in all the memories until it finished and then quit from the program. I only got a "B" tab.
Huh, strange. I hate to even ask, but could you try on a windows box to see if you get the same result? It doesn't *appear* to be something it's reading from the radio causing it grief, so I can only think of GTK-related issues. It works here...
On Feb 10, 2011, at 8:53, Dan Smith wrote:
Huh, strange. I hate to even ask, but could you try on a windows box to see if you get the same result? It doesn't *appear* to be something it's reading from the radio causing it grief, so I can only think of GTK-related issues. It works here…
I actually have an XP machine in my shack now, so I could. I tried the 92 with the keyspan USB adaptor and without (direct on com1), got the same results, only the "B" tab. Then I quit chirp, and relaunched, tried it with the 91 that's down in the shack, and also only got the "B" tab for it as well.
I grabbed the 0.1.11b4-installer.exe file for windows for the test.
I actually have an XP machine in my shack now, so I could. I tried the 92 with the keyspan USB adaptor and without (direct on com1), got the same results, only the "B" tab. Then I quit chirp, and relaunched, tried it with the 91 that's down in the shack, and also only got the "B" tab for it as well.
Well, that's no good! I'll have to take a look. Thanks for the report!
On Feb 10, 2011, at 17:03, Dan Smith wrote:
Okay, it's a bug that has been fixed since b4. I'll be posting b5 Real Soon Now(tm) so it should work as expected in that one.
b5 does have both tabs. are the memory counts (as memories are read from the radio) supposed to be intermixed, or separate depending on which tab you're on? they were intermixed (flipping back and forth between the A and B counts regardless of which tab was currently selected) and I wasn't sure if that was expected behavior or not.
I did have to add in KeySpan support again before it could bring up the dialog box to set the com port.
-debbie
b5 does have both tabs. are the memory counts (as memories are read from the radio) supposed to be intermixed, or separate depending on which tab you're on? they were intermixed (flipping back and forth between the A and B counts regardless of which tab was currently selected) and I wasn't sure if that was expected behavior or not.
The two tabs share a single connection to the radio, of course, so they kinda fight for access while they're loading. If you are only interested in the A side (for example), you can just hit Esc (or Radio->Stop) on the B side and the A one will finish more quickly. You can always stop a big queued read by pressing Esc on the live radios.
The idea is that it attempts to load the whole radio in the background while you're doing other things. You can always make changes to the memories on the screen or load another range while it's filling in the background. Anything done at the UI takes precedence over the background loading.
I did have to add in KeySpan support again before it could bring up the dialog box to set the com port.
Hmm, that fall out somehow? Or did we ever even have it in CHIRP? I know it was in the D-RATS code...
On Feb 11, 2011, at 0:33, Dan Smith wrote:
The two tabs share a single connection to the radio, of course, so they kinda fight for access while they're loading. If you are only interested in the A side (for example), you can just hit Esc (or Radio->Stop) on the B side and the A one will finish more quickly. You can always stop a big queued read by pressing Esc on the live radios.
The idea is that it attempts to load the whole radio in the background while you're doing other things. You can always make changes to the memories on the screen or load another range while it's filling in the background. Anything done at the UI takes precedence over the background loading.
no problem, just wasn't sure if it was expected behavior.
I did have to add in KeySpan support again before it could bring up the dialog box to set the com port.
Hmm, that fall out somehow? Or did we ever even have it in CHIRP? I know it was in the D-RATS code…
We'd discussed you adding it just before Dayton last year, but things were hectic and I'm not sure you ever did. I didn't download a new version since that one, so I don't know. I can put in a feature request so it's on the list, it's definitely a 20 second mod.
participants (2)
-
Dan Smith -
Debbie Fligor