- Users - lists.chirpmyradio.com

Re: [chirp_users] CHIRP 0.1.8
by David Tilson 14 Feb '09

14 Feb '09

G'day Dan, > It takes so freaking long to clone the 2820 that I'm always > apt to choose the easiest route that works unless there is a > real problem. It's a pain to debug issues in that thing :) Yep, I understand. The DSQL and Code problem appears to be resolved on the 2820 with 0.1.9b4. Thanks for that. I haven't been able to replicate the lockup of CHIRP when an invalid frequency was entered through a CSV import on the 2820 in 0.1.9b4. I did try something on the 92AD Bank B that had an interesting result. I had a valid frequency entered in Mem 57 of 146.6375 MHz. I performed a CSV import with Mem 57 set to an invalid freq of 136.6375. The import screen showed that the new freq would be 136.6375, however when the import occurred the frequency remained at 146.6375 (unchanged). I then deleted Mem 57 as well as Mem 58 from the radio and did the CSV import again. In the CSV file Mem 57 had the corrupt frequency and Mem 58 had a valid frequency. This time nothing was saved in Mem 57, however Mem 58 imported correctly. > I hope you > are far enough away that you won't have to worry about > endangering yourself, your family, or your home. Be safe and > good luck! Yes, we are safe thanks. The majority of the fires have been at least an hours drive to the north east and approx 2 hours drive to the east. We are still concerned though as there is March is traditionally the month for fires down here. Cheers, davidt

2 1

Re: [chirp_users] CHIRP 0.1.8
by David Tilson 14 Feb '09

14 Feb '09

G'day Nate, Thanks for your concerns, it is appreciated. The koala, who has become known famously around the world as Sam, is now in a wildlife shelter recovering with 3rd degree burns on her paws (Sam is a female koala). They showed a brief reunion with Sam and the firefighter, who gave her a drink, a few nights ago on TV and they now appear to have a special bond... Out of interest Richard VK3JFK, Peter VK3TQ and I flew over the fires last Sunday night, on the way back from demonstrating D-STAR at an interstate hamfest, and from 30'000 feet we could clearly see the enormity of the fire front and the devastation below. Regards, Davidt, VK3UR

1 0

Re: [chirp_users] CHIRP 0.1.8
by David Tilson 14 Feb '09

14 Feb '09

G'day Dan, > 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. OK, thanks for looking at that. I'll try it later today and report back. Interesting though was that the memories that were being affected had previously been DV memories, not FM. In some cases I was overwriting existing DV memories with CHIRP and in other cases I had deleted the contents of the memories with the CS-2820 software prior to importing with CHIRP. Also interesting was the fact that the error was only occurring in memory locations that were being directly written to. > > 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? No probs. I'll try that as well and report back. Thanks also for your concerns regarding the bushfires around Victoria in our off-list emails. The fires started last Saturday after the temp exceeded 46C / 115F with strong winds and the stats so far are: 181 deceased and still expected to rise, more than 1,800 homes destroyed and more than 7,000 people homeless. It has been estimated that over 1,000,000 animals died in the fires. Many people still aren't allowed to return to their properties due to safety reasons and don't know if they have a home to return to. Regards, Davidt, VK3UR

3 2

[chirp_users] CHIRP 0.1.8b8
by Dan Smith 13 Feb '09

13 Feb '09

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! -- Dan Smith dsmith#danplanet.com, s/#/@/ www.danplanet.com KK7DS

3 9

[chirp_users] Data corruption when downloading from radio
by Andrew Hood 10 Feb '09

10 Feb '09

Hi, I have CHIRP version 0.1.8 and using a OPC-478 cable to connect to my IC2200H I find that the download seems to go ok but when I look at the data some of it is corrupted. For example, instead of showing 146.9625 in the frequency it shows 117.5700 73 de Andy VK2EAH

2 1

Re: [chirp_users] CHIRP 0.1.8
by David Tilson 06 Feb '09

06 Feb '09

G'day Dan, > 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 :) No probs at all. I'm just about to hop on a plane to go to the Wyong Hamfest. I was able to work around the problems for the moment anyway, so neither of them were a show stoppers, just a few items for when you get around to them :) Seeya, Davidt, VK3UR

1 0

[chirp_users] CHIRP 0.1.9b2
by Dan Smith 06 Jan '09

06 Jan '09

Hi all, I just posted CHIRP 0.1.9b2 with a single bugfix. Jeff reported an issue with importing into a 2200, which turned out to be an issue with the 2200 driver improperly handling large duplex offset values. I've fixed that, and have also fixed the bug that caused him not to not see a reasonable error message as a result. So, if you were experiencing this issue, you might be interested in 0.1.9b2. Thanks! -- Dan Smith dsmith#danplanet.com, s/#/@/ www.danplanet.com KK7DS

1 0

[chirp_users] 2200H?
by J lists 05 Jan '09

05 Jan '09

I'm having an issue trying to import a CSV into the 2200H program file. I was able to import it into my ID800 and into my 92AD, but when I do it on the 2200H it seems to just lock up. Am I doing something wrong? Tnx in advance

2 1

Re: [chirp_users] csv format
by David Tilson 06 Dec '08

06 Dec '08

> Correct, the ID800, IC2200, and IC?82 radios will only accept > uppercase characters. I thought that might be the case with a few of the radios, but didn't know which models. I'll update the wiki later to reflect this. > The individual radio drivers should coerce them to upper > case, but I'm not confident that they all do that in a > consistent manner :D This might be a pain, but is it worth getting CHIRP to force a case change to upper case for those specific radios? Cheers, davidt

3 7

Re: [chirp_users] CHIRP 0.1.8b7
by David Tilson 04 Dec '08

04 Dec '08

G'day Dan, > I just posted b7 with the following changes: All of this testing is on my IC-92AD... > - Fixed up setting bank back to None Confirmed. Just a thought... If the Bank is set back to "none" is it worth forcing the Bank Index to "-1" so that the number is available for reuse. Currently it looks like you can only set the Bank Index back to "-1" manually. It may also make things cleaner if you sort the list based on Bank Index in the GUI. BTW, I worked out yesterday why the Bank was only displaying as "A-", "B-", etc and the same with the drop down Bank list when the field was selected, instead of just showing "A", "B", etc in the GUI. It was simply that the default width for the Bank field in the GUI was truncating any Bank names that had been entered. I should have checked that earlier, but simply widening that field in the GUI showed the additional information. Having the GUI display the Bank name, which you have done, makes it easier to choose the appropriate bank. > - Fix ic9x bank index being 0 instead of -1, thus avoiding auto-set Confirmed and the auto-set feature now works on the IC-92AD if the Bank Index was originally "-1". > - Add a "Special Memories" check box at the top to show/hide them Confirmed. > - Make all radios return all special memory locations all the time I presume you mean when the check box is enabled. If yes, confirmed. > - Improve automatic bank index selection Not sure what you have changed here. However, I did notice in the last couple of betas that in the Banks tab I can enter a long Bank Name which appears to be OK while CHIRP is running, but then gets truncated to 8 chars when you exit / restart CHIRP. Would it be better to limit the field to 8 chars (or whatever the radio can handle) at the point of entering the Bank name? This could probably wait until you attack the GUI in 0.1.9. > - Avoid loading the callsign lists at startup for radios that don't > require them. Instead load on the first attempt to show the D-STAR > tab. YAY!!! This makes the loading much faster. The only question is if you perform an export, for example to .chirp format, and you haven't pressed the D-STAR tab to load the callsign lists, will CHIRP grab this info and include it in the export? > I still haven't added the special memory support to > import/export, nor have I added the conversion of bank index > to letters. Nor have I added the bank index collision detection. No dramas. > Dave T, I hope you appreciate the last item in the changed > list. I got so tired of waiting for those big lists to > download *every* time I opened up the 92 :) Yep, see above :) > I think I'm going to fix up bank-index-to-letter bit for > import/export and then call 0.1.8 good, barring any other > actual bugs. I haven't come across any other bugs in this version, based on my testing with the IC-92AD, that would stop release once the bank-index-to-letter and import / export are addressed. I'll update the wiki Data Model on the wiki to reflect the Special Memories section and link it to the main CHIRP wiki page. > I wanted to release 0.1.8 a while ago with > mostly just individual memory field completeness, but the > special memory support has been quite a can of worms. Yeah, but it was such a simple and harmless request to include them in this release :) > We've > got a lot of things to fix that are all GUI-related that I > want to tackle in 0.1.9, and thus want to avoid the scope of > 0.1.8 creeping any further. Agree. Cheers, Davidt, VK3UR

2 1