On 2024-01-11 14:04:, Dan Smith via chirp_users wrote:
>Before we get into a religious war about Rich's 20-year-old mail client, let's
>please go ahead and take this off-list. The 2000+ people subscribed here are
>looking for CHIRP discussion and not any more about this topic.
Good point. Thanks
On 2024-01-11 13:33:, Dan Smith via chirp_users wrote:
> If you think you've messed up your CSV file and want help with fixing it,
No...I am sure I understand the requirements, and thought I had explained that
clearly. Apparently not. But my csv files are "correct".
>If you think what you've go
On 2024-01-11 13:33:, Dan Smith via chirp_users wrote:
>> 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
> Wow, that's horrible.
Yep, they look fine to me and others, as Ken notes.
Before we get into a religious war about Rich's 20-year-old mail client, let's
please go ahead and take this off-list. The 2000+ people subscribed here are
looking for CHIRP discussion and not any more about this topic.
Wow, that's horrible.
I just checked, there are no meaningful options or settings on the Maillist
homepage, just the option to get a digest instead of individual emails (1),
which leads me to believe it is your email client. It looks to me like your
email client, for whatever reason, is parsing
I offer so much thanks for all who work on the CHIRP platform.
K7NQB 73
-- Original Message --
From: Dan Smith via chirp_users
To: Discussion of CHIRP
Subject: Re: [chirp_users] Icom IC-2100H, Excel spreadsheet, csv files,
chirp-next-20240111-win64
Date: Thu, 11 Jan 2024 10:33
In a previous life I was a software tester, that's why I suggested what did
before - to try and identify the source of the issue, but that's doesn't seem
to have been taken up, let's take another stab at this, see below:
> On Jan 11, 2024, at 8:45 AM, Rich NE1EE wrote:
>
> GM, all,
> Thanks f
On 2024-01-11 13:20:, Ken Hansen wrote:
>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... Ken, N2VIP
Thanks for the note. I have a workaround, as I documented in an ea
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 n
> 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' poi
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...
Ken, N2VIP
> On Jan 11, 2024, at 10:26 AM, Rich NE1EE wrote:
>
> On 2024-01-11 10:55:, Ken Hansen wrote:
>> If I unde
On Thu, Jan 11, 2024 at 12:09 PM Lyle Giese wrote:
>
> .img files are radio specific. You can not use a .img file from an Icom
> ID-880H with a Baofeng UV5R for instance.
You sure can. I do this all the time to transfer memories between my
source image (which happens to be from a 12 year old UV-
Lyle. NO.
You save the one radio as an .img file and directly inport that .img file into
the next radio. No .csv needed.
>
> So if you are working with a group that has various makes & models of
> radios, a .CSV file is how you exchange the freq/repeater data.
>
> Lyle W9LRG
>
> On 1/11/2
.img files are radio specific. You can not use a .img file from an Icom
ID-880H with a Baofeng UV5R for instance.
To move data from radio type a to radio type b, you export the data to a
.csv file(which has no radio specific data unlike a .img file). Then
open up an .img file for radio b and
On 2024-01-11 10:55:, Ken Hansen wrote:
>If I understand your issue correctly, it seems you are reporting issues with
>CSV export/import, a facility the CHIRP team discourages using (as noted in
>1a).
If it is discouraged, then remove it from the product. If it remains, then
either tell me what
On 2024-01-11 10:55:, Ken Hansen wrote:
>Have you opened an issue on CHIRP website? That is the proper way to bring
>something to the attention of the CHIRP team.
I thought it best to open a discussion here and get feedback: either someone
points out my mistakes, or recommends I open a problem r
On 2024-01-11 10:55:, Ken Hansen wrote:
>I find your descriptions hard to follow, more a case of information overload
>than a lack of information.
I am used to describing things completely, which is why I wrote in separate
paragraphs. However, I see that the replies are coming back to me a one
I don't think there is a problem assuming your spreadsheet has the correct
number of columns, correctly named and in the required order.
Other software neither names the columns as Chirp does nor contains the
required number of columns in the correct order.
> On 11/01/2024 16:00 GMT Rich NE1E
On 2024-01-11 10:25:, Nigel A. Gunn G8IFF/W8IFF wrote:
>Hi Rich
>
>I've probably missed something.
>Why do you need to use CSV files at all?
>If it's multiple radio types, I believe you can import the .img file from one
>radio into a different radio model.
>The only reason I see to use csv files
Have you opened an issue on CHIRP website? That is the proper way to bring
something to the attention of the CHIRP team.
I find your descriptions hard to follow, more a case of information overload
than a lack of information.
If I understand your issue correctly, it seems you are reporting issu
Hi Rich
I've probably missed something.
Why do you need to use CSV files at all?
If it's multiple radio types, I believe you can import the .img file from one
radio into a different radio model.
The only reason I see to use csv files is if you need to print it to paper.
> On 11/01/2024 14:44 GMT
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
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:
ht
23 matches
Mail list logo
