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
This might be a pain, but is it worth getting CHIRP to force a case change to upper case for those specific radios?
Yes, that's what I meant. It definitely should, and may already. I'll have to make sure, and fix up the drivers that may not already.
I am getting a file mismatch errror when I try to import a CSV file. Any suggestion on what I am doing wrong?> Date: Sun, 30 Nov 2008 17:01:16 -0800> From: dsmith@danplanet.com> To: chirp_users@lists.danplanet.com> Subject: Re: [chirp_users] csv format> > > This might be a pain, but is it worth getting CHIRP to force a case> > change to upper case for those specific radios?> > Yes, that's what I meant. It definitely should, and may already. I'll> have to make sure, and fix up the drivers that may not already.> > -- > Dan Smith> dsmith#danplanet.com, s/#/@/> www.danplanet.com> KK7DS> _______________________________________________> chirp_users mailing list> chirp_users@lists.danplanet.com> http://lists.danplanet.com/mailman/listinfo/chirp_users _________________________________________________________________ You live life online. So we put Windows on the web. http://clk.atdmt.com/MRT/go/127032869/direct/01/
I am getting a file mismatch errror when I try to import a CSV file. Any suggestion on what I am doing wrong?
What is the exact error, and which version are you using?
There is (now) a "mismatch" error if you try to import a CSV file without the proper header information. This is to help guard against importing a CSV file that doesn't match what the current implementation is expecting.
Do an export to CSV and look at the first line. Make sure that matches the first line in your CSV file exactly before you try to import.
If they are the same, send the debug log.
Thanks!
I am using the latest beta release with a IC-2200H radio. I have it working and there some additional fields the 2200H supports: Name - on/off RF Power - Low, Mid-L, Mid-H, High
Date: Sat, 6 Dec 2008 12:48:00 -0800> From: dsmith@danplanet.com> To: chirp_users@lists.danplanet.com> Subject: Re: [chirp_users] csv format> > > I am getting a file mismatch errror when I try to import a CSV file.> > Any suggestion on what I am doing wrong?> > What is the exact error, and which version are you using?> > There is (now) a "mismatch" error if you try to import a CSV file> without the proper header information. This is to help guard against> importing a CSV file that doesn't match what the current implementation> is expecting.> > Do an export to CSV and look at the first line. Make sure that matches> the first line in your CSV file exactly before you try to import.> > If they are the same, send the debug log.> > Thanks!> > -- > Dan Smith> dsmith#danplanet.com, s/#/@/> www.danplanet.com> KK7DS> _______________________________________________> chirp_users mailing list> chirp_users@lists.danplanet.com> http://lists.danplanet.com/mailman/listinfo/chirp_users
_________________________________________________________________ Send e-mail anywhere. No map, no compass. http://windowslive.com/Explore/hotmail?ocid=TXT_TAGLM_WL_hotmail_acq_anywher...
I am using the latest beta release with a IC-2200H radio. I have it working
Great!
and there some additional fields the 2200H supports: Name - on/off
Yes, I guess I should implement this one, although only the 2200 and 800 support this notion.
RF Power - Low, Mid-L, Mid-H, High
Yeah, I have avoided this as well because radios like the 2820 don't have such a flag. However, I'll figure out some sane way to add that in at some point.
Thanks!
I would also like to suggest that the selection of com ports and radio be remembered. This is more of a nice to have that an issue.> Date: Sat, 6 Dec 2008 14:11:18 -0800> From: dsmith@danplanet.com> To: chirp_users@lists.danplanet.com> Subject: Re: [chirp_users] csv format> > > I am using the latest beta release with a IC-2200H radio. I have it> > working > > Great!> > > and there some additional fields the 2200H supports:> > Name - on/off> > Yes, I guess I should implement this one, although only the 2200 and 800> support this notion.> > > RF Power - Low, Mid-L, Mid-H, High> > Yeah, I have avoided this as well because radios like the 2820 don't> have such a flag. However, I'll figure out some sane way to add that in> at some point.> > Thanks!> > -- > Dan Smith> dsmith#danplanet.com, s/#/@/> www.danplanet.com> KK7DS> _______________________________________________> chirp_users mailing list> chirp_users@lists.danplanet.com> http://lists.danplanet.com/mailman/listinfo/chirp_users _________________________________________________________________ Suspicious message? There’s an alert for that. http://windowslive.com/Explore/hotmail?ocid=TXT_TAGLM_WL_hotmail_acq_broad2_...
I would also like to suggest that the selection of com ports and radio be remembered. This is more of a nice to have that an issue.
Definitely. Until now, I've been focusing on a critical mass of radio support. As I've mentioned a couple times recently, I plan to make the next release one that focuses on features of the actual application. Preferences of port, radio, etc will be top on that list, along with some additional editing functionality, etc.
It is very good to hear what people want in the way of priorities. I use CHIRP in a very different way than most of you, since I'm constantly testing things on many different radios at once.
participants (3)
-
Dan Smith -
David Tilson -
joe camilli