[chirp_users] CHIRP 0.1.8b8
Hi all,
I just posted 0.1.8b8 which I hope we can call the official 0.1.8. I didn't add import/export of the special memories because it's going to require some additional logic in the actual import process than I really want to do at this point. Since that's more GUI-related, I want to push that off to 0.1.9. The changes from b7 are:
- Improved Linux packaging - CSV file includes bank letter instead of number
Linux users will likely want to use the new install procedure. To do so, grab and unpack the tar file as usual. Then do:
$ cd chirp-0.1.8b8 $ python setup.py install
This should put an icon in your applications menu (under HamRadio) and install CHIRP to the regular system locations. I'd appreciate some reports from linux users on what distro they're using and about any problems they're facing.
Thanks!
hi
i have been trying to get this to work but it cant seem to find the "serial" port is there a way to fix this as i am using ubuntu 8.10 and then i can let ya know how it goes
doug vk3kay
Dan Smith wrote:
Hi all,
I just posted 0.1.8b8 which I hope we can call the official 0.1.8. I didn't add import/export of the special memories because it's going to require some additional logic in the actual import process than I really want to do at this point. Since that's more GUI-related, I want to push that off to 0.1.9. The changes from b7 are:
- Improved Linux packaging
- CSV file includes bank letter instead of number
Linux users will likely want to use the new install procedure. To do so, grab and unpack the tar file as usual. Then do:
$ cd chirp-0.1.8b8 $ python setup.py install
This should put an icon in your applications menu (under HamRadio) and install CHIRP to the regular system locations. I'd appreciate some reports from linux users on what distro they're using and about any problems they're facing.
Thanks!
i have been trying to get this to work but it cant seem to find the "serial" port is there a way to fix this as i am using ubuntu 8.10 and then i can let ya know how it goes
If you're using a built-in serial port, then it will be /dev/ttyS0 (or 1, 2, etc). If you're using a USB-to-serial adapter, then it will be /dev/ttyUSB0 (or 1, 2, etc).
When you go to download from the radio, it should populate that box with available serial ports. Does it not? What radio and cable are you using?
hi dan
the main problem s that it just wont load the gui and have found theres a error so i dont get to the stage of doing the comports etc
heres the error:
/# chirpw Traceback (most recent call last): File "/usr/bin/chirpw", line 22, in <module> from chirpui import mainapp File "/usr/lib/python2.5/site-packages/chirpui/mainapp.py", line 24, in <module> import serial ImportError: No module named serial
as i have installed it by the way you suggest as recons it installed ok but do i need to do it another way and im using a IC92ad with the icom serial cable as have had no probs with the windows versions with them
doug vk3kay
Dan Smith wrote:
i have been trying to get this to work but it cant seem to find the "serial" port is there a way to fix this as i am using ubuntu 8.10 and then i can let ya know how it goes
If you're using a built-in serial port, then it will be /dev/ttyS0 (or 1, 2, etc). If you're using a USB-to-serial adapter, then it will be /dev/ttyUSB0 (or 1, 2, etc).
When you go to download from the radio, it should populate that box with available serial ports. Does it not? What radio and cable are you using?
ImportError: No module named serial
Yep, the problem is that you're missing some supporting packages that aren't part of chirp, but that are used by it. The easiest thing might be to follow the install instructions for D-RATS that pertain to your Linux distro. Don't actually install D-RATS, but install all of the same packages before you try running chirp. The instructions are here:
http://d-rats.danplanet.com/wiki/InstallPage
Just scroll down to the Linux section...
hi dan
all works now so will have a go and let ya know
thanks doug vk3kay
Dan Smith wrote:
ImportError: No module named serial
Yep, the problem is that you're missing some supporting packages that aren't part of chirp, but that are used by it. The easiest thing might be to follow the install instructions for D-RATS that pertain to your Linux distro. Don't actually install D-RATS, but install all of the same packages before you try running chirp. The instructions are here:
http://d-rats.danplanet.com/wiki/InstallPage
Just scroll down to the Linux section...
G'day Dan,
I realise that you are currently working on a 0.1.9beta at the moment, but I've come across a couple of small problems with the release version of 0.1.8 which I don't think have been identified or addressed in the recent change logs.
When importing a CSV file into an IC-2820 with CHIRP all looks fine, however if you then open it up with the CS-2820 program some, not all, of the DSQL fields display "error" and the CODE field displays "127" instead of "00". This is occuring on some DV memory channels, but fairly consistently. I cleaned up a ICF file, then went through the process a couple of times importing a CSV file through CHIRP and it happened on each occasion.
I can't replicate the problem on my IC-92AD, so it may only be isolated to the IC-2820H.
Unfortunately I'm not in a position to send you a dodgy icf file or chirp csv file at the moment.
On a secondary issue, I discovered yesterday when importing a CSV file into the IC-92AD, with CHIRP 0.1.8, that if a frequency is out of range (example: 136.6375, instead of 146.6375) then CHIRP locked up and had to be killed / restarted.
Regards,
David Tilson, VK3UR Web: www.daves-portal.com Web: www.DazzlingLights.com <--- Christmas Lights E-mail: dave@daves-portal.com Tel: 0407-854-647
Hi Dave,
I realise that you are currently working on a 0.1.9beta at the moment, but I've come across a couple of small problems with the release version of 0.1.8 which I don't think have been identified or addressed in the recent change logs.
When importing a CSV file into an IC-2820 with CHIRP all looks fine, however if you then open it up with the CS-2820 program some, not all, of the DSQL fields display "error" and the CODE field displays "127" instead of "00". This is occuring on some DV memory channels, but fairly consistently. I cleaned up a ICF file, then went through the process a couple of times importing a CSV file through CHIRP and it happened on each occasion.
I can't replicate the problem on my IC-92AD, so it may only be isolated to the IC-2820H.
Unfortunately I'm not in a position to send you a dodgy icf file or chirp csv file at the moment.
On a secondary issue, I discovered yesterday when importing a CSV file into the IC-92AD, with CHIRP 0.1.8, that if a frequency is out of range (example: 136.6375, instead of 146.6375) then CHIRP locked up and had to be killed / restarted.
Just so you don't think you're being ignored, this is in my pipeline to look at. There are just a lot of things there already :)
Thanks!
When importing a CSV file into an IC-2820 with CHIRP all looks fine, however if you then open it up with the CS-2820 program some, not all, of the DSQL fields display "error" and the CODE field displays "127" instead of "00". This is occuring on some DV memory channels, but fairly consistently. I cleaned up a ICF file, then went through the process a couple of times importing a CSV file through CHIRP and it happened on each occasion.
Okay, I was able to reproduce this issue and I have a fix for it. It's not actually something CHIRP was doing, but rather something it wasn't doing that was the problem. Apparently when you switch to DV mode on the radio or CS-2820, there is a bit of logic to clear/reset/initialize two of the bytes in the memory location that pertain to the DSQL/CSQL/code values. CHIRP wasn't doing that, and thus whatever garbage was there before remained, and CS-2820 didn't like it.
So, I've got a fix to clear those values *if* we're setting a non-DV memory to DV mode. The reason I'm doing this instead of blindly resetting them is so that if you've set the values in your radio (since CHIRP doesn't support them), I don't want to clobber them. Thus, to see this fix, you'll need to do something like reset your radio and re-import from CSV or some such (let me know if that doesn't make any sense).
Anyway, give 0.1.9b4 a shot and let me know if it fixes the issue for you.
On a secondary issue, I discovered yesterday when importing a CSV file into the IC-92AD, with CHIRP 0.1.8, that if a frequency is out of range (example: 136.6375, instead of 146.6375) then CHIRP locked up and had to be killed / restarted.
I have not been able to replicate this with 0.1.9b3. Can you? If you can, perhaps you can send me the CSV file you're importing, and perhaps an ICF of your radio that I can import into mine before I try the import.
Also, if you have a debug log of this particular scenario, it might have something useful in it.
Thanks!
participants (3)
-
Dan Smith -
David Tilson -
vk3kay