[chirp_users] IMG file format
Is there a spec available for the format of the IMG file that Chirp uses to same configuration values to?
Thanks,
Eric
Eric,
The IMG files are like photographic snapshots of the radio's memory channels, they are unique to each version AND model of a manufacturer's transceiver.
CHIRP works with this unique file type which is why it is extremely important to upon the first time using CHIRP to download the IMG from your transceiver, save and safeguard it from loss. You can use this unique IMG file to restore your transceiver to factory settings which is especially important if user error causes your transceiver to be unresponsive, or "bricked".
Each model and make of transceiver has a unique IMG file.
Your question shows a lack of understanding of how CHIRP works, please read the documentation and follow the instructions!
Failure to do so may result in irreversible injury to your radio equipment.
If this happens, contact this list for possible restoration measures using someone else's IMG file.
Best wishes,
David N1EA
On Tue, Oct 5, 2021, 14:54 Eric chirp@brunsen.com wrote:
Is there a spec available for the format of the IMG file that Chirp uses to same configuration values to?
Thanks,
Eric _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to D.J.J. Ring, Jr. at n1ea@arrl.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
Of course his question shown a lack of understanding or he wouldn't have needed to ask a question. We can't all be as knowlegable as you.
Although the .img file contains a memory dump from the radio, there must be some commonality between img files or it wouldn't be possible to import an img file into ANY other radios Chirp editor. The memory dump is only a small part og the img file format. Having said that, I'm one of the many that doesn't understand the inner workings of Chirp.
On 05/10/2021 15:11 D.J.J. Ring, Jr. n1ea@arrl.net wrote:
Your question shows a lack of understanding of how CHIRP works, please read the documentation and follow the instructions!
David
i think your response is somewhat harsh and condescending
On Tue, 5 Oct 2021 at 20:12, D.J.J. Ring, Jr. n1ea@arrl.net wrote:
Eric,
The IMG files are like photographic snapshots of the radio's memory channels, they are unique to each version AND model of a manufacturer's transceiver.
CHIRP works with this unique file type which is why it is extremely important to upon the first time using CHIRP to download the IMG from your transceiver, save and safeguard it from loss. You can use this unique IMG file to restore your transceiver to factory settings which is especially important if user error causes your transceiver to be unresponsive, or "bricked".
Each model and make of transceiver has a unique IMG file.
Your question shows a lack of understanding of how CHIRP works, please read the documentation and follow the instructions!
Failure to do so may result in irreversible injury to your radio equipment.
If this happens, contact this list for possible restoration measures using someone else's IMG file.
Best wishes,
David N1EA
On Tue, Oct 5, 2021, 14:54 Eric chirp@brunsen.com wrote:
Is there a spec available for the format of the IMG file that Chirp uses to same configuration values to?
Thanks,
Eric _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to D.J.J. Ring, Jr. at n1ea@arrl.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Nicola Jayne at nicola.jayne.hodson@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
I'm sorry it came off like that, it wasn't meant that way, I usually answer questions with a lot of understanding, probably I didn't do as well this time, for that and for any offense I inadvertently made I apologize.
No harshness was meant, if such came across, it was my regrettable choice of words.
If you spoke to me that wouldn't come across, written communications is lacking in nuance or at least good writers, and in this, I have failed this time.
To the original poster, I am sorry if my message seemed harsh, it was supposed to be a URGENT warning to not hurt your radio, not meant to hurt your feelings, or convey a lack of support from me or more importantly, this list. I think the urgency of my warning to protect your radio from harm got in the way of my otherwise better explanation and expression, again my apologies.
Best regards,
DR N1EA
On Tue, Oct 5, 2021 at 3:44 PM Nicola Jayne Hodson < nicola.jayne.hodson@gmail.com> wrote:
David
i think your response is somewhat harsh and condescending
On Tue, 5 Oct 2021 at 20:12, D.J.J. Ring, Jr. n1ea@arrl.net wrote:
Eric,
The IMG files are like photographic snapshots of the radio's memory channels, they are unique to each version AND model of a manufacturer's transceiver.
CHIRP works with this unique file type which is why it is extremely important to upon the first time using CHIRP to download the IMG from your transceiver, save and safeguard it from loss. You can use this unique IMG file to restore your transceiver to factory settings which is especially important if user error causes your transceiver to be unresponsive, or "bricked".
Each model and make of transceiver has a unique IMG file.
Your question shows a lack of understanding of how CHIRP works, please read the documentation and follow the instructions!
Failure to do so may result in irreversible injury to your radio equipment.
If this happens, contact this list for possible restoration measures using someone else's IMG file.
Best wishes,
David N1EA
On Tue, Oct 5, 2021, 14:54 Eric chirp@brunsen.com wrote:
Is there a spec available for the format of the IMG file that Chirp uses to same configuration values to?
Thanks,
Eric _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to D.J.J. Ring, Jr. at n1ea@arrl.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Nicola Jayne at nicola.jayne.hodson@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to D.J.J. Ring, Jr. at n1ea@arrl.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
Didn't sound harsh or condescending to me. One line was perhaps direct.
On 10/5/2021 1:00 PM, D.J.J. Ring, Jr. wrote:
I'm sorry it came off like that, it wasn't meant that way, I usually answer questions with a lot of understanding, probably I didn't do as well this time, for that and for any offense I inadvertently made I apologize.
No harshness was meant, if such came across, it was my regrettable choice of words.
If you spoke to me that wouldn't come across, written communications is lacking in nuance or at least good writers, and in this, I have failed this time.
To the original poster, I am sorry if my message seemed harsh, it was supposed to be a URGENT warning to not hurt your radio, not meant to hurt your feelings, or convey a lack of support from me or more importantly, this list. I think the urgency of my warning to protect your radio from harm got in the way of my otherwise better explanation and expression, again my apologies.
Best regards,
DR N1EA
On Tue, Oct 5, 2021 at 3:44 PM Nicola Jayne Hodson <nicola.jayne.hodson@gmail.com mailto:nicola.jayne.hodson@gmail.com> wrote:
David i think your response is somewhat harsh and condescending On Tue, 5 Oct 2021 at 20:12, D.J.J. Ring, Jr. <n1ea@arrl.net <mailto:n1ea@arrl.net>> wrote: Eric, The IMG files are like photographic snapshots of the radio's memory channels, they are unique to each version AND model of a manufacturer's transceiver. CHIRP works with this unique file type which is why it is extremely important to upon the first time using CHIRP to download the IMG from your transceiver, save and safeguard it from loss. You can use this unique IMG file to restore your transceiver to factory settings which is especially important if user error causes your transceiver to be unresponsive, or "bricked". Each model and make of transceiver has a unique IMG file. Your question shows a lack of understanding of how CHIRP works, please read the documentation and follow the instructions! Failure to do so may result in irreversible injury to your radio equipment. If this happens, contact this list for possible restoration measures using someone else's IMG file. Best wishes, David N1EA On Tue, Oct 5, 2021, 14:54 Eric <chirp@brunsen.com <mailto:chirp@brunsen.com>> wrote: Is there a spec available for the format of the IMG file that Chirp uses to same configuration values to? Thanks, Eric _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com <mailto:chirp_users@intrepid.danplanet.com> http://intrepid.danplanet.com/mailman/listinfo/chirp_users <http://intrepid.danplanet.com/mailman/listinfo/chirp_users> This message was sent to D.J.J. Ring, Jr. at n1ea@arrl.net <mailto:n1ea@arrl.net> To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com <mailto:chirp_users-unsubscribe@intrepid.danplanet.com> _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com <mailto:chirp_users@intrepid.danplanet.com> http://intrepid.danplanet.com/mailman/listinfo/chirp_users <http://intrepid.danplanet.com/mailman/listinfo/chirp_users> This message was sent to Nicola Jayne at nicola.jayne.hodson@gmail.com <mailto:nicola.jayne.hodson@gmail.com> To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com <mailto:chirp_users-unsubscribe@intrepid.danplanet.com> _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com <mailto:chirp_users@intrepid.danplanet.com> http://intrepid.danplanet.com/mailman/listinfo/chirp_users <http://intrepid.danplanet.com/mailman/listinfo/chirp_users> This message was sent to D.J.J. Ring, Jr. at n1ea@arrl.net <mailto:n1ea@arrl.net> To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com <mailto:chirp_users-unsubscribe@intrepid.danplanet.com>
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Jonathan at jpeakall@madlabs.info To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
David,
Thanks. Re-reading your message with this explanation makes perfect sense.
I understand the ease of misunderstanding when it comes to email (and texting is even worse).
The reason for my wanting this tool, is that I have somehow become the “go to” person for programming other folks radios,
and I like to keep a record of what changes were made, when and why.
At this time, I track these things in a spreadsheet, and it works, but it would be much easier to automate the process rather than copy/paste.
Thanks again,
Eric
From: chirp_users-bounces@intrepid.danplanet.com chirp_users-bounces@intrepid.danplanet.com On Behalf Of D.J.J. Ring, Jr. Sent: Tuesday, October 5, 2021 3:01 PM To: Discussion of CHIRP chirp_users@intrepid.danplanet.com Subject: Re: [chirp_users] IMG file format
I'm sorry it came off like that, it wasn't meant that way, I usually answer questions with a lot of understanding, probably I didn't do as well this time, for that and for any offense I inadvertently made I apologize.
No harshness was meant, if such came across, it was my regrettable choice of words.
If you spoke to me that wouldn't come across, written communications is lacking in nuance or at least good writers, and in this, I have failed this time.
To the original poster, I am sorry if my message seemed harsh, it was supposed to be a URGENT warning to not hurt your radio, not meant to hurt your feelings, or convey a lack of support from me or more importantly, this list. I think the urgency of my warning to protect your radio from harm got in the way of my otherwise better explanation and expression, again my apologies.
Best regards,
DR
N1EA
On Tue, Oct 5, 2021 at 3:44 PM Nicola Jayne Hodson <nicola.jayne.hodson@gmail.com mailto:nicola.jayne.hodson@gmail.com > wrote:
David
i think your response is somewhat harsh and condescending
On Tue, 5 Oct 2021 at 20:12, D.J.J. Ring, Jr. <n1ea@arrl.net mailto:n1ea@arrl.net > wrote:
Eric,
The IMG files are like photographic snapshots of the radio's memory channels, they are unique to each version AND model of a manufacturer's transceiver.
CHIRP works with this unique file type which is why it is extremely important to upon the first time using CHIRP to download the IMG from your transceiver, save and safeguard it from loss. You can use this unique IMG file to restore your transceiver to factory settings which is especially important if user error causes your transceiver to be unresponsive, or "bricked".
Each model and make of transceiver has a unique IMG file.
Your question shows a lack of understanding of how CHIRP works, please read the documentation and follow the instructions!
Failure to do so may result in irreversible injury to your radio equipment.
If this happens, contact this list for possible restoration measures using someone else's IMG file.
Best wishes,
David N1EA
On Tue, Oct 5, 2021, 14:54 Eric <chirp@brunsen.com mailto:chirp@brunsen.com > wrote:
Is there a spec available for the format of the IMG file that Chirp uses to same configuration values to?
Thanks,
Eric
_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to D.J.J. Ring, Jr. at n1ea@arrl.net mailto:n1ea@arrl.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com
_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Nicola Jayne at nicola.jayne.hodson@gmail.com mailto:nicola.jayne.hodson@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com
_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to D.J.J. Ring, Jr. at n1ea@arrl.net mailto:n1ea@arrl.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com
Agreed, a very worthy project, perhaps it can be posted as a development feature, especially if you would be willing to let others develop it with you, everyone might find it very useful in maintaining CHIRP and supporting the many transceivers it works with.
Best wishes and thanks again for your kind message.
73 DR N1EA
On Tue, Oct 5, 2021 at 10:29 PM Eric chirp@brunsen.com wrote:
David,
Thanks. Re-reading your message with this explanation makes perfect sense.
I understand the ease of misunderstanding when it comes to email (and texting is even worse).
The reason for my wanting this tool, is that I have somehow become the “go to” person for programming other folks radios,
and I like to keep a record of what changes were made, when and why.
At this time, I track these things in a spreadsheet, and it works, but it would be much easier to automate the process rather than copy/paste.
Thanks again,
Eric
*From:* chirp_users-bounces@intrepid.danplanet.com < chirp_users-bounces@intrepid.danplanet.com> *On Behalf Of *D.J.J. Ring, Jr. *Sent:* Tuesday, October 5, 2021 3:01 PM *To:* Discussion of CHIRP chirp_users@intrepid.danplanet.com *Subject:* Re: [chirp_users] IMG file format
I'm sorry it came off like that, it wasn't meant that way, I usually answer questions with a lot of understanding, probably I didn't do as well this time, for that and for any offense I inadvertently made I apologize.
No harshness was meant, if such came across, it was my regrettable choice of words.
If you spoke to me that wouldn't come across, written communications is lacking in nuance or at least good writers, and in this, I have failed this time.
To the original poster, I am sorry if my message seemed harsh, it was supposed to be a URGENT warning to not hurt your radio, not meant to hurt your feelings, or convey a lack of support from me or more importantly, this list. I think the urgency of my warning to protect your radio from harm got in the way of my otherwise better explanation and expression, again my apologies.
Best regards,
DR
N1EA
On Tue, Oct 5, 2021 at 3:44 PM Nicola Jayne Hodson < nicola.jayne.hodson@gmail.com> wrote:
David
i think your response is somewhat harsh and condescending
On Tue, 5 Oct 2021 at 20:12, D.J.J. Ring, Jr. n1ea@arrl.net wrote:
Eric,
The IMG files are like photographic snapshots of the radio's memory channels, they are unique to each version AND model of a manufacturer's transceiver.
CHIRP works with this unique file type which is why it is extremely important to upon the first time using CHIRP to download the IMG from your transceiver, save and safeguard it from loss. You can use this unique IMG file to restore your transceiver to factory settings which is especially important if user error causes your transceiver to be unresponsive, or "bricked".
Each model and make of transceiver has a unique IMG file.
Your question shows a lack of understanding of how CHIRP works, please read the documentation and follow the instructions!
Failure to do so may result in irreversible injury to your radio equipment.
If this happens, contact this list for possible restoration measures using someone else's IMG file.
Best wishes,
David N1EA
On Tue, Oct 5, 2021, 14:54 Eric chirp@brunsen.com wrote:
Is there a spec available for the format of the IMG file that Chirp uses to same configuration values to?
Thanks,
Eric
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to D.J.J. Ring, Jr. at n1ea@arrl.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Nicola Jayne at nicola.jayne.hodson@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to D.J.J. Ring, Jr. at n1ea@arrl.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to D.J.J. Ring, Jr. at n1ea@arrl.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
David,
So do you know if there is a file format spec for the img files that CHIRP writes?
It would guess that even if the format differs between radio vendors/models, there would be similarities to the keys/values that could be interpreted.
Thanks,
Eric
From: chirp_users-bounces@intrepid.danplanet.com chirp_users-bounces@intrepid.danplanet.com On Behalf Of D.J.J. Ring, Jr. Sent: Tuesday, October 5, 2021 11:37 PM To: Discussion of CHIRP chirp_users@intrepid.danplanet.com Subject: Re: [chirp_users] IMG file format
Agreed, a very worthy project, perhaps it can be posted as a development feature, especially if you would be willing to let others develop it with you, everyone might find it very useful in maintaining CHIRP and supporting the many transceivers it works with.
Best wishes and thanks again for your kind message.
73
DR
N1EA
On Tue, Oct 5, 2021 at 10:29 PM Eric <chirp@brunsen.com mailto:chirp@brunsen.com > wrote:
David,
Thanks. Re-reading your message with this explanation makes perfect sense.
I understand the ease of misunderstanding when it comes to email (and texting is even worse).
The reason for my wanting this tool, is that I have somehow become the “go to” person for programming other folks radios,
and I like to keep a record of what changes were made, when and why.
At this time, I track these things in a spreadsheet, and it works, but it would be much easier to automate the process rather than copy/paste.
Thanks again,
Eric
From: chirp_users-bounces@intrepid.danplanet.com mailto:chirp_users-bounces@intrepid.danplanet.com <chirp_users-bounces@intrepid.danplanet.com mailto:chirp_users-bounces@intrepid.danplanet.com > On Behalf Of D.J.J. Ring, Jr. Sent: Tuesday, October 5, 2021 3:01 PM To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com > Subject: Re: [chirp_users] IMG file format
I'm sorry it came off like that, it wasn't meant that way, I usually answer questions with a lot of understanding, probably I didn't do as well this time, for that and for any offense I inadvertently made I apologize.
No harshness was meant, if such came across, it was my regrettable choice of words.
If you spoke to me that wouldn't come across, written communications is lacking in nuance or at least good writers, and in this, I have failed this time.
To the original poster, I am sorry if my message seemed harsh, it was supposed to be a URGENT warning to not hurt your radio, not meant to hurt your feelings, or convey a lack of support from me or more importantly, this list. I think the urgency of my warning to protect your radio from harm got in the way of my otherwise better explanation and expression, again my apologies.
Best regards,
DR
N1EA
On Tue, Oct 5, 2021 at 3:44 PM Nicola Jayne Hodson <nicola.jayne.hodson@gmail.com mailto:nicola.jayne.hodson@gmail.com > wrote:
David
i think your response is somewhat harsh and condescending
On Tue, 5 Oct 2021 at 20:12, D.J.J. Ring, Jr. <n1ea@arrl.net mailto:n1ea@arrl.net > wrote:
Eric,
The IMG files are like photographic snapshots of the radio's memory channels, they are unique to each version AND model of a manufacturer's transceiver.
CHIRP works with this unique file type which is why it is extremely important to upon the first time using CHIRP to download the IMG from your transceiver, save and safeguard it from loss. You can use this unique IMG file to restore your transceiver to factory settings which is especially important if user error causes your transceiver to be unresponsive, or "bricked".
Each model and make of transceiver has a unique IMG file.
Your question shows a lack of understanding of how CHIRP works, please read the documentation and follow the instructions!
Failure to do so may result in irreversible injury to your radio equipment.
If this happens, contact this list for possible restoration measures using someone else's IMG file.
Best wishes,
David N1EA
On Tue, Oct 5, 2021, 14:54 Eric <chirp@brunsen.com mailto:chirp@brunsen.com > wrote:
Is there a spec available for the format of the IMG file that Chirp uses to same configuration values to?
Thanks,
Eric
_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to D.J.J. Ring, Jr. at n1ea@arrl.net mailto:n1ea@arrl.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com
_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Nicola Jayne at nicola.jayne.hodson@gmail.com mailto:nicola.jayne.hodson@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com
_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to D.J.J. Ring, Jr. at n1ea@arrl.net mailto:n1ea@arrl.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com
_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to D.J.J. Ring, Jr. at n1ea@arrl.net mailto:n1ea@arrl.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com
I'm not the person to ask, but I'd just assume that all the img files are completely different, and it's chirp's job to access it and that it does this by selecting the different model of radio. When I run chirp and select my manufacturer and model, I assume that it takes the IMG file and interfaces with it in a unique way particular to th radio, but I'm just guessing what's being done.
One of the developers would know but I don't, I'm just a user who occasionally helps users when no answer is given because I love that people use chirp because I think it's a great program.
I'm also working with the developer of SLINT the multi language and acccessible Slackware operating system, what a fabulous distribution it is.
We have several visually challanged hams on the support list!
73 DR N1EA
Eric wrote: Wed, Oct 06, 2021 at 02:34:21PM -0500
David,
So do you know if there is a file format spec for the img files that CHIRP writes?
It would guess that even if the format differs between radio vendors/models, there would be similarities to the keys/values that could be interpreted.
Thanks,
Eric
From: chirp_users-bounces@intrepid.danplanet.com chirp_users-bounces@intrepid.danplanet.com On Behalf Of D.J.J. Ring, Jr. Sent: Tuesday, October 5, 2021 11:37 PM To: Discussion of CHIRP chirp_users@intrepid.danplanet.com Subject: Re: [chirp_users] IMG file format
Agreed, a very worthy project, perhaps it can be posted as a development feature, especially if you would be willing to let others develop it with you, everyone might find it very useful in maintaining CHIRP and supporting the many transceivers it works with.
Best wishes and thanks again for your kind message.
73
DR
N1EA
On Tue, Oct 5, 2021 at 10:29 PM Eric <chirp@brunsen.com mailto:chirp@brunsen.com > wrote:
David,
Thanks. Re-reading your message with this explanation makes perfect sense.
I understand the ease of misunderstanding when it comes to email (and texting is even worse).
The reason for my wanting this tool, is that I have somehow become the “go to” person for programming other folks radios,
and I like to keep a record of what changes were made, when and why.
At this time, I track these things in a spreadsheet, and it works, but it would be much easier to automate the process rather than copy/paste.
Thanks again,
Eric
From: chirp_users-bounces@intrepid.danplanet.com mailto:chirp_users-bounces@intrepid.danplanet.com <chirp_users-bounces@intrepid.danplanet.com mailto:chirp_users-bounces@intrepid.danplanet.com > On Behalf Of D.J.J. Ring, Jr. Sent: Tuesday, October 5, 2021 3:01 PM To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com > Subject: Re: [chirp_users] IMG file format
I'm sorry it came off like that, it wasn't meant that way, I usually answer questions with a lot of understanding, probably I didn't do as well this time, for that and for any offense I inadvertently made I apologize.
No harshness was meant, if such came across, it was my regrettable choice of words.
If you spoke to me that wouldn't come across, written communications is lacking in nuance or at least good writers, and in this, I have failed this time.
To the original poster, I am sorry if my message seemed harsh, it was supposed to be a URGENT warning to not hurt your radio, not meant to hurt your feelings, or convey a lack of support from me or more importantly, this list. I think the urgency of my warning to protect your radio from harm got in the way of my otherwise better explanation and expression, again my apologies.
Best regards,
DR
N1EA
On Tue, Oct 5, 2021 at 3:44 PM Nicola Jayne Hodson <nicola.jayne.hodson@gmail.com mailto:nicola.jayne.hodson@gmail.com > wrote:
David
i think your response is somewhat harsh and condescending
On Tue, 5 Oct 2021 at 20:12, D.J.J. Ring, Jr. <n1ea@arrl.net mailto:n1ea@arrl.net > wrote:
Eric,
The IMG files are like photographic snapshots of the radio's memory channels, they are unique to each version AND model of a manufacturer's transceiver.
CHIRP works with this unique file type which is why it is extremely important to upon the first time using CHIRP to download the IMG from your transceiver, save and safeguard it from loss. You can use this unique IMG file to restore your transceiver to factory settings which is especially important if user error causes your transceiver to be unresponsive, or "bricked".
Each model and make of transceiver has a unique IMG file.
Your question shows a lack of understanding of how CHIRP works, please read the documentation and follow the instructions!
Failure to do so may result in irreversible injury to your radio equipment.
If this happens, contact this list for possible restoration measures using someone else's IMG file.
Best wishes,
David N1EA
On Tue, Oct 5, 2021, 14:54 Eric <chirp@brunsen.com mailto:chirp@brunsen.com > wrote:
Is there a spec available for the format of the IMG file that Chirp uses to same configuration values to?
Thanks,
Eric
chirp_users mailing list chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to D.J.J. Ring, Jr. at n1ea@arrl.net mailto:n1ea@arrl.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Nicola Jayne at nicola.jayne.hodson@gmail.com mailto:nicola.jayne.hodson@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to D.J.J. Ring, Jr. at n1ea@arrl.net mailto:n1ea@arrl.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to D.J.J. Ring, Jr. at n1ea@arrl.net mailto:n1ea@arrl.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to D.J.J. Ring, Jr. at n1ea@arrl.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
On Wed, Oct 6, 2021 at 3:36 PM Eric chirp@brunsen.com wrote:
David,
So do you know if there is a file format spec for the img files that CHIRP writes?
It would guess that even if the format differs between radio vendors/models, there would be similarities to the keys/values that could be interpreted.
Thanks,
Eric
There is no spec. An "image" is just an extraction, or picture, of a radio's memory. Each radio is different. Each CHIRP driver has to be designed to each individual "image". That is why you can only upload and image into the same type of radio that it was downloaded from.
Jim KC9HI
Jim, Thanks.
Eric
-----Original Message----- From: chirp_users-bounces@intrepid.danplanet.com chirp_users-bounces@intrepid.danplanet.com On Behalf Of Jim Unroe Sent: Wednesday, October 6, 2021 6:45 PM To: Discussion of CHIRP chirp_users@intrepid.danplanet.com Subject: [SPAM] Re: [chirp_users] IMG file format
On Wed, Oct 6, 2021 at 3:36 PM Eric chirp@brunsen.com wrote:
David,
So do you know if there is a file format spec for the img
files that CHIRP writes?
It would guess that even if the format differs between radio
vendors/models, there would be similarities to the keys/values that could be interpreted.
Thanks,
Eric
There is no spec. An "image" is just an extraction, or picture, of a radio's memory. Each radio is different. Each CHIRP driver has to be designed to each individual "image". That is why you can only upload and image into the same type of radio that it was downloaded from.
Jim KC9HI _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Eric at chirp@brunsen.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
David, I do understand how Chirp works and have been using is successfully for quite a while now.
I was asking because I was considering creating a tool that would allow me to read the contents of the file and export it to a human-readable file for reference purposes.
I can do that now with Memory files through Chirp, but cannot do it with settings from the radio.
Thanks,
Eric
From: chirp_users-bounces@intrepid.danplanet.com chirp_users-bounces@intrepid.danplanet.com On Behalf Of D.J.J. Ring, Jr. Sent: Tuesday, October 5, 2021 2:12 PM To: Discussion of CHIRP chirp_users@intrepid.danplanet.com Subject: Re: [chirp_users] IMG file format
Eric,
The IMG files are like photographic snapshots of the radio's memory channels, they are unique to each version AND model of a manufacturer's transceiver.
CHIRP works with this unique file type which is why it is extremely important to upon the first time using CHIRP to download the IMG from your transceiver, save and safeguard it from loss. You can use this unique IMG file to restore your transceiver to factory settings which is especially important if user error causes your transceiver to be unresponsive, or "bricked".
Each model and make of transceiver has a unique IMG file.
Your question shows a lack of understanding of how CHIRP works, please read the documentation and follow the instructions!
Failure to do so may result in irreversible injury to your radio equipment.
If this happens, contact this list for possible restoration measures using someone else's IMG file.
Best wishes,
David N1EA
On Tue, Oct 5, 2021, 14:54 Eric <chirp@brunsen.com mailto:chirp@brunsen.com > wrote:
Is there a spec available for the format of the IMG file that Chirp uses to same configuration values to?
Thanks,
Eric
_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to D.J.J. Ring, Jr. at n1ea@arrl.net mailto:n1ea@arrl.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com
On Tue, Oct 5, 2021 at 3:55 PM Eric chirp@brunsen.com wrote:
David, I do understand how Chirp works and have been using is successfully for quite a while now.
I was asking because I was considering creating a tool that would allow me to read the contents of the file and export it to a human-readable file for reference purposes.
I can do that now with Memory files through Chirp, but cannot do it with settings from the radio.
Thanks,
Eric
What you are wanting to create is something similar to Baoclone.
Jim KC9HI
Jim, Thanks, I have never heard of Baoclone before, I'll take a look at it.
Thanks again,
Eric
-----Original Message----- From: chirp_users-bounces@intrepid.danplanet.com chirp_users-bounces@intrepid.danplanet.com On Behalf Of Jim Unroe Sent: Tuesday, October 5, 2021 6:27 PM To: Discussion of CHIRP chirp_users@intrepid.danplanet.com Subject: [SPAM] Re: [chirp_users] IMG file format
On Tue, Oct 5, 2021 at 3:55 PM Eric chirp@brunsen.com wrote:
David, I do understand how Chirp works and have been using is
successfully for quite a while now.
I was asking because I was considering creating a tool that would allow me
to read the contents of the file and export it to a human-readable file for reference purposes.
I can do that now with Memory files through Chirp, but cannot do it with
settings from the radio.
Thanks,
Eric
What you are wanting to create is something similar to Baoclone.
Jim KC9HI _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Eric at chirp@brunsen.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
The Chirp source code is available on GIT.
Download and take a look at it.
You'll find all sorts of neat info buried within it.
I did this to create my own tool to program/clone radios with an Arduino.
73 - Bill KA8VIT/W8COD
On 10/05/2021 3:53 PM Eric <chirp@brunsen.com> wrote: David, I do understand how Chirp works and have been using is successfully for quite a while now. I was asking because I was considering creating a tool that would allow me to read the contents of the file and export it to a human-readable file for reference purposes. I can do that now with Memory files through Chirp, but cannot do it with settings from the radio. Thanks, Eric
==================================== Bill Chaikin, KA8VIT Chief Radio Operator WW2 Submarine USS COD SS-224 (NECO) USS COD Amateur Radio Club - W8COD
ka8vit@ka8vit.com http://ka8vit.com http://www.usscod.org ====================================
participants (8)
-
Bill KA8VIT
-
D.J.J. Ring, Jr.
-
David J. J. Ring, Jr.
-
Eric
-
Jim Unroe
-
Jonathan Peakall
-
Nicola Jayne Hodson
-
Nigel A. Gunn G8IFF/W8IFF