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. http://slint.fr 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-boun...@intrepid.danplanet.com > <chirp_users-boun...@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 <ch...@brunsen.com > <mailto:ch...@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-boun...@intrepid.danplanet.com > <mailto:chirp_users-boun...@intrepid.danplanet.com> > <chirp_users-boun...@intrepid.danplanet.com > <mailto:chirp_users-boun...@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.hod...@gmail.com <mailto:nicola.jayne.hod...@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. <n...@arrl.net > <mailto:n...@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 <ch...@brunsen.com <mailto:ch...@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 n...@arrl.net > <mailto:n...@arrl.net> > To unsubscribe, send an email to > chirp_users-unsubscr...@intrepid.danplanet.com > <mailto:chirp_users-unsubscr...@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.hod...@gmail.com > <mailto:nicola.jayne.hod...@gmail.com> > To unsubscribe, send an email to > chirp_users-unsubscr...@intrepid.danplanet.com > <mailto:chirp_users-unsubscr...@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 n...@arrl.net > <mailto:n...@arrl.net> > To unsubscribe, send an email to > chirp_users-unsubscr...@intrepid.danplanet.com > <mailto:chirp_users-unsubscr...@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 n...@arrl.net > <mailto:n...@arrl.net> > To unsubscribe, send an email to > chirp_users-unsubscr...@intrepid.danplanet.com > <mailto:chirp_users-unsubscr...@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 n...@arrl.net > To unsubscribe, send an email to > chirp_users-unsubscr...@intrepid.danplanet.com
signature.asc
Description: PGP signature
_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to arch...@mail-archive.com at arch...@mail-archive.com To unsubscribe, send an email to chirp_users-unsubscr...@intrepid.danplanet.com
