- Users - lists.chirpmyradio.com

[chirp_users] UV-17R Pro GPS - Toggle between Name and Frequency
by Dr. Herb Sims 15 Jan '24

15 Jan '24

Is there any way on the UV-17 Pro GPS HT to toggle between the Name and the Frequency in MEMORY entries? Thanks, Herb

5 7

Re: [chirp_users] Wouxon KG-1000G Plus - Unable To Read
by Erdgon Wireless 15 Jan '24

15 Jan '24

Issue resolved. Unplugged everything and restarted everything. The cyber radio gods smiled on me. Thanks. -- Sent with Tuta; enjoy secure & ad-free emails: https://tuta.com Jan 15, 2024, 12:12 by chirp_users(a)intrepid.danplanet.com: > Hello. Seeking a little help with reading a Wouxon KG-1000G Plus, > > CHIRP reports unable to > > I have fully updated > > Ubuntu box with Chirp next-20231223 on Python 3.10.12 wxPython 4.0.7 gtk3 (phoenix) wxWidgets 3.0.5 > > and > > Win10 with Chirp next-20240101 on Python 3.10.8 wxPython 4.2 msw (phoenix) wxWidgets 3.2 > > When connecting the radio to either I receive a driver error warning saying the driver is still a beta. > > I have multiple cables and have tried all > > Ports are identified and set with the "Help Me" feature. I can successfully use this with other radios with no problems. > > Radio is powered up. > > The error I receive when attempting to download radio is: > > "Error communicating with radio." > "Radio did not respond." > > Looking for any suggestions or help on getting this working. Possible I am missing something (nothing new there.). > > Thanks > > > Sent with Tuta; enjoy secure & ad-free emails: > https://tuta.com >

1 0

[chirp_users] Wouxon KG-1000G Plus - Unable To Read
by Erdgon Wireless 15 Jan '24

15 Jan '24

Hello. Seeking a little help with reading a Wouxon KG-1000G Plus, CHIRP reports unable to I have fully updated Ubuntu box with Chirp next-20231223 on Python 3.10.12 wxPython 4.0.7 gtk3 (phoenix) wxWidgets 3.0.5 and Win10 with Chirp next-20240101 on Python 3.10.8 wxPython 4.2 msw (phoenix) wxWidgets 3.2 When connecting the radio to either I receive a driver error warning saying the driver is still a beta. I have multiple cables and have tried all Ports are identified and set with the "Help Me" feature. I can successfully use this with other radios with no problems. Radio is powered up. The error I receive when attempting to download radio is: "Error communicating with radio." "Radio did not respond." Looking for any suggestions or help on getting this working. Possible I am missing something (nothing new there.). Thanks Sent with Tuta; enjoy secure & ad-free emails: https://tuta.com

1 0

[chirp_users] Airband Programming UV-17 Radios
by Anthony (N2KI) 11 Jan '24

11 Jan '24

Is there an update coming that will allow airband frequencies to be entered into the Chirp software for programming capable UV17 radios? Thanks! *Regards,Anthony * * N2KI*

1 0

[chirp_users] email formatting
by Rich NE1EE 11 Jan '24

11 Jan '24

I see inbound emails as the attached image, which are very difficult to parse. It's as if all line feeds and/or carriage feeds are stripped from the email. I don't see this in other emails. Do you all see this? If not, what can I do on my end? Or is there a setting in the chirp mail list that I need to set? 73 Rich NE1EE The Dusty Key On the banks of the Piscataqua

3 3

[chirp_users] Icom IC-2100H, Excel spreadsheet, csv files, chirp-next-20240111-win64
by Rich NE1EE 11 Jan '24

11 Jan '24

GM, all, Thanks for this bit of testing. I intend to do my best to keep track of this topic, because I need to be clear in my docs to the ARES group. As an erstwhile software engineer and programmer, I expect that the record reading routine instantiates a record structure populated with defaults, then proceeds to read the csv, filling in any valid data found. That would seem to create only valid complete records. I've been using chirp-next, so that accounts for some of my success. I see that I am not using URCALL,RPT1CALL,RPT2CALL,DVCODE but I have ,,,, at the end of each line. I am using MS Office 2010, which I have been using for years, though I see that there have been updates to it that I have accepted. 1. In the spreadsheet, I CLEAR all unused cells...I don't just leave them "apparently" empty. I Save As csv file. (all these files are available upon request) 1a. I open an img file from the 2100H, then IMPORT the csv (it IS an option, even if the popup says it isn't recommended), it appears that the img is updated SOMEWHAT correctly. Some memory lines are left blank, and I dont't see why...the csv lines look fine to me. If chirp sees too many commas in a row, does it get tired of processing nothing, and skip the rest of the line? Because I have this 4,EROCK4,147.465000,,,,,,23,NN,23,Tone->Tone,FM,5.00,,50W,EAST ROCK VOICE ONLY,,,, and it is skipped. 2. If I choose to OPEN the csv file, the result is the same...I have blank lines in the csv file tab in chirp. 3. I then filled (spreadsheet) Offset, rToneFreq, cToneFreq with valid data, even though those fields are not used. For example, if a channel is simplex, there is no offset. If no tone option is specified, no tone value is needed. Hence CLEARing the fields in the spreadsheet, rather than leaving them "blank". If I don't CLEAR them, I get spaces twixt commas. I don't know how chirp handles those. 4,EROCK4,147.465000,,0.600000,,88.5,88.5,23,NN,23,Tone->Tone,FM,5.00,,50W,EAST ROCK VOICE ONLY,,,, 3a. I then opened the csv in chirp. The import stopped at line 23, but I suspect that is because the rest of the channels don't match the 2100H freq range (154.9..162.475). I'll check the specs. BUT now all the formerly blank lines are filled. 3b. I copied lines 1..23 from the csv tab to lines 1..23 in the ing tab, and it seems that all lines are correct. *** Unsed fields (see #3 above) are showing blank, as expected. I havna had a chance to load it into a 2100H and then read it, to see how that looks. BUT it seems that chirp is making some decisions I don't understand. I havna run into this before, because I tend to fill all fields, whether used or not, with defaults. 4. I checked the 2100H specs. The RX is listed as 136�174 MHz, BUT *Guaranteed 144�148 MHz only. Nonetheless, the deleted lines contain what seems to me to be valid data. 73 Rich NE1EE The Dusty Key On the banks of the Piscataqua

6 16

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