January 2024 - Users - lists.chirpmyradio.com

Re: [chirp_users] Icom IC-2100H, Excel spreadsheet, csv files, chirp-n ext-20240111-win64
by Nick 11 Jan '24

11 Jan '24

I offer so much thanks for all who work on the CHIRP platform. K7NQB 73 ---------- Original Message ---------- From: Dan Smith via chirp_users <chirp_users(a)intrepid.danplanet.com> To: Discussion of CHIRP <chirp_users(a)intrepid.danplanet.com> Subject: Re: [chirp_users] Icom IC-2100H, Excel spreadsheet, csv files, chirp-next-20240111-win64 Date: Thu, 11 Jan 2024 10:33:11 -0800 > I'm not a CHIRP developer, I merely pointed out that they appear to discourage using CSV files, implying that fixing that facility may be a low priority issue for the team... No, we do not discourage them, and fixing CSV issues is a priority (for me at least) for sure. Jim and others' points are correct that CSV is not *necessary* just to transfer data between different models. CSV may be an unnecessary step if that's all you're using it for. The CSV driver in CHIRP is different from others in that it can basically record any frequency on any band with any set of other attributes (like mode, tone modes, etc) which no real driver would ever allow. It's for that reason that I maintain my master frequency plan in a CSV file because the entire thing isn't accepted by any single radio I own. CSV is perfect for that. The thing about CSV is that it is an _encoding_ and not a format. CHIRP has it's own method of using CSV to encode the data structures it needs to represent, and that of course, doesn't match with any other program. Excel (or other spreadsheet) can edit CSV files in a generic way and thus can be used in place of the CHIRP memory editor in principle. However, the user, or Excel (or both) can easily mess up the structure of the data while preserving the low-level CSV encoding (or could mess up the encoding as well) and make a file no longer readable in CHIRP. Within reason, those sorts of issues may be within the realm of something we want to fix, but of course, we can't and won't be able to read the mind of the person or tool that mangled one of our CSV files into doing the right thing. Rich, you're wrong in your description of how we read a record and construct a memory from it (with respect to "defaults") for reasons I won't go into in depth here. You may (or may not) be right that we're choking on something that should be able to handle and thus could make a change. However, as you can see from the philosophical discussion here - this is probably not the best place to ask the question generically. If you think you've messed up your CSV file and want help with fixing it, then this might be the right forum (although without a sample of what you've got that doesn't work, nobody can provide anything useful). If you think what you've got should be accepted, then please open a bug, attach your log and the file you're trying to import, and let those of us that can do something about it have a look. --Dan _______________________________________________ chirp_users mailing list chirp_users(a)intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Nick at papanick(a)netzero.net To unsubscribe, send an email to chirp_users-unsubscribe(a)intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner(a)intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com

1 0

[chirp_users] New chirp-next build
by donotreply＠chirp.danplanet.com 11 Jan '24

11 Jan '24

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. Unless you have a reason not to, we recommend using the latest build of CHIRP-next at all times. You can get it from here: http://trac.chirp.danplanet.com/chirp_next/ A list of changes since the last build are here: b7f204cd h777: Extend valid_bands upper bound to 490MHz 5c5dbdc6 [UV-K5] warn the user of the radio being in firmware flash mode 94e3c5d3 radtel_t18.py: Baofeng BF-T20 Support Full Band - fixes #9821 9b9abefd mml_jc8810.py: Support Radtel RT-470X Firmware 2.13A - fixes #11027 901e375e th_uv88.py: Retevis RA89 Support Latest Firmware - fixes #11052 5e5f9fa4 Remove unused imports 10fa5182 gmrsv2.py: remove print statements 58c460f1 Update tr_TR.po --

1 0

[chirp_users] programming assistance
by Bobby Creech 10 Jan '24

10 Jan '24

hi, I'm new to this handheld scene. Been using a CB but our group wants to switch to GMRS. Anyway the "radio enthusiast" that is helping out by programming everyone's radio provided a csv file. However he's using RTSystems to program them so the columns don't match. I asked him about it, but he states he is unfamiliar with Chirp and doesn't know how to line them up (I sent him the column headers from the Chirp img file, but I think he ignored it. I would think it wouldn't be too hard for a radio guy to rearrange the columns.). He says I can bring the radio to the next meeting and he will program it. I thought about that, since then I could download it with Chirp and figure it out myself. But I don't really want to wait until the next meeting. Anyone could help me line up the columns if I provide the csv? (is it ok to share a radio csv?, I figure it's all just freqs that have labels added so the user knows what channel is what) Thanks in advance

3 3

Re: [chirp_users] programming assistance
by Rich NE1EE 10 Jan '24

10 Jan '24

On 2024-01-10 08:15:, Jim Unroe wrote: >CHIRP CSV files often have multiple trailing commas at the end of each line due to the URXALL, RPT1CALL, RPT2CALL and DVCODE fields rarely being used. Power,Comment,URCALL,RPT1CALL,RPT2CALL,DVCODE 5.00,,Low,,,,, Excel is known to remove multiple trailing commas at the end of a line. When CHIRP reads the CSV file where the trailing commas have been removed, the trailing data will be read into the wrong fields. Excel always works fine if there is alway something in the last field of each line. I've read that there is a setting that you can enable in excel that tells it to leave trailing commas alone. I don't have excel so I can't verify this. Perhaps it would be possible to have CHIRP always resync with the beginning of the CSV file's next line when a linefeed is encountered? Jim KC9HI // This is the discussion that I need to capture in my notes for the ARES group. // I have been "lucky" not to have run into this in the past. And wrt the present file, all channels end with a comment, so if there are blank fields, the csv will be correctly formatted (IAW your trailing ,,, comment). I will look into Excel settings, but any rate, I need to caution the group. I've never had a problem with chirp, but then I am fairly computer literate, and I don't know how that enhances my chirp experiences. ...and finally... >so I can't verify this. Perhaps it would be possible to have CHIRP always resync with the beginning of the CSV file's next line when a linefeed is encountered? Jim KC9HI Absolutely common sense. Would be surprise were it not already the case... 73 Rich NE1EE The Dusty Key On the banks of the Piscataqua

3 2

Re: [chirp_users] programming assistance
by Rich NE1EE 10 Jan '24

10 Jan '24

Not sure in what way Excel is not compatible with chirp? I am using it as I develop and share a list of Emergency Op Ctr channels. The initial pass consisted of reading from a IC-2100H (most of the local EOCs are using this), saving both img and csv, editing the csv in Excel, and using the results to upload to the 2100. I didn't have a problem...maybe the error is radio-dependent? I think I have asked this before, and I need to develop a process for others in the area to follow, so I am curious about this. 73 Rich NE1EE The Dusty Key On the banks of the Piscataqua On 2024-01-09 20:21:, D.J.J. Ring, Jr. wrote: >csv files are just spreadsheet files - you can edit them with LibreOffice (don't use Excel as it's not compatible� with CHIRP).

4 5

[chirp_users] Quansheng support
by Daniel Oberhausen 08 Jan '24

08 Jan '24

Hi! I don't find any Quansheng entry in the scrolling menu. (Chirp 0.3.0). Regards. Daniel Oberhausen

2 1

[chirp_users] "Failed to communicate with radio: Incorrect ACK on serial port."
by website mail 06 Jan '24

06 Jan '24

I recently got a Yaesu FT-65. I didn't get the programming cable from Yaesu (it's $40), but I did get one that works for it that has the same chip. I'm running Windows 11 and have the latest version of chirp. When I plug the radio in and press read from radio, I get the error message "Failed to communicate with radio: Incorrect ACK on serial port." I've tried different cables, drivers, different modes on the radio, looked through the issues, looked up the error, I even tried it on a spare laptop running Linux to see if Windows was the problem. Same error there. Is it the cable or something else? If anyone knows or had this problem before I'd really appreciate the help! Thanks

4 4