- Users - lists.chirpmyradio.com

Re: [chirp_users] Special Mode?
by David B. Horvath, CCP 09 Jan '15

09 Jan '15

I'm looking to use the receiver out of those ranges Jim. I can manually program those frequencies into the radio but not via Chirp. - David >On Date: Wed, 7 Jan 2015 22:30:22 -0500, Jim Unroe ><rock.unroe(a)gmail.com> wrote: > >David, > >You can program any valid frequencies within the published band limits >of the radio (136.000-174.000 MHz and 400.000-520.000 MHz). Any >programmed memory can be easily set to RX only by setting the Duplex >field to "off" > >Jim KC9HI

3 2

Re: [chirp_users] Who used CHIRP in linux ubuntu mode ?
by D.J.J. Ring, Jr. 08 Jan '15

08 Jan '15

The poster, y_61 says that he bought a new cable from Baofeng through Amazon.it, and the cable works fine in Windows but when used with the Chirp Live CD based on Ubuntu with upgraded CHIRP to DAILY CHIRP (20150102) with GTK 2.24-10 Pyton 2.7.3 PYGTK 2.24.0, connecting the cable results in the Baofeng UV-5R (BFS 297) going into TRANSMIT mode. The poster, y_61 does not understand why the same cable is working with Windows but not with Ubuntu CHIRP Live CD. The poster, y_61 does not confirm that the version of CHIRP used on Windows is the same DAILY CHIRP or other. Does anyone know why the Baofeng UV-5R is going into transmit. The poster, y_61 does not state at which moment the UV-5R goes into transmit. David On Wed, Jan 7, 2015 at 1:52 PM, y_61(a)libero.it <y_61(a)libero.it> wrote: > I read in a MIKLOR web site that there are some False usb profilic cable > or false profilic pl-2303 . > > > > I have this china (clone ? ) cable, buy by *amazon :* > > > > > http://www.amazon.it/gp/product/B007VMA6TK?psc=1&redirect=true&ref_=oh_aui_… > > > > In how mode I say if is this cable is a FTDI, or Proflic or PL-2303 or > a bad clone ???? > > > > My very big problem is that when I used this clone cable buy by amazon > on windows xp > > All ok, I read and write on my baofeng UV-5R > > > > But when I use a live cd with ubuntu and CHIPR (update today !!! ) *version > is now:* > > > > DAILY (20150102) GTK 2.24-10 Pyton 2.7.3 PYGTK 2.24.0 > > > > The problem is that with ubuntu (linux distro ) the cable not work and the > baofeng always go to TX ! > > > > Why it work well on windows xp , but not work with Chirp on ubuntu live > cd distro ???? > > > > Thanks for help. > > > > > > PS the version on my baofeng UV-5R is BFS 297 buy on july 2014. > > > > > > ----Messaggio originale---- > Da: y_61(a)libero.it > Data: 26-dic-2014 10.42 > A: <y_61(a)libero.it> > Ogg: I: Re: [chirp_users] Who used CHIRP in linux ubuntu mode ? > > > > ----Messaggio originale---- > Da: y_61(a)libero.it > Data: 24-dic-2014 10.23 > A: <y_61(a)libero.it> > Ogg: Re: [chirp_users] Who used CHIRP in linux ubuntu mode ? > > > > ----Messaggio originale---- > Da: n1ea(a)arrl.net > Data: 23-dic-2014 14.46 > A: "y_61(a)libero.it"<y_61(a)libero.it> > Ogg: Re: R: Re: R: Re: Re: R: Re: [chirp_users] Who used CHIRP in linux > ubuntu mode ? > > What version of chirp are you using? > > David > On Dec 23, 2014 8:00 AM, "y_61(a)libero.it" <y_61(a)libero.it> wrote: > >> >> yes, after installal chiro on usb boot pen, i updateat the last issue of >> chirp via internet.... >> >> >> an ham-radio say that this TX on cable connection is a known issue.... >> its true ? >> >> the solution ? >> >> help me.,,, best 73 >> >> >> ----Messaggio originale---- >> Da: n1ea(a)arrl.net >> Data: 22-dic-2014 21.04 >> A: "y_61(a)libero.it"<y_61(a)libero.it> >> Ogg: Re: R: Re: Re: R: Re: [chirp_users] Who used CHIRP in linux ubuntu >> mode ? >> >> Are you using the latest daily build? >> >> Tell me what version. Do NOT program with anything except the latest >> raily build. >> >> David >> On Dec 22, 2014 2:07 PM, "y_61(a)libero.it" <y_61(a)libero.it> wrote: >> >>> ok i update, now chirp is ok . >>> >>> >>> >>> *Hi, arrived the new cable and now the uv-5r is programmed !* >>> >>> >>> >>> *The old cable is dead !* >>> >>> >>> >>> *when I use this new cable with windows , all ok it read and program the >>> memories,* >>> >>> *but if I use the CHIRP on boot in Ubuntu, when I connect to the usb >>> port this cable * >>> >>> *the RTX go on TX !!!* >>> >>> >>> >>> *why ? remember that I use it on windows all ok, help me, best 73* >>> >>> >>> >>> >>> >>> ----Messaggio originale---- >>> Da: n1ea(a)arrl.net >>> Data: 11-dic-2014 20.43 >>> A: "y_61(a)libero.it"<y_61(a)libero.it> >>> Ogg: Re: Re: R: Re: [chirp_users] Who used CHIRP in linux ubuntu mode ? >>> >>> Not yet. >>> >>> Upgrade CHIRP to the latest DAILY BUILD - this is important. >>> >>> In terminal do this - each line is a command. >>> >>> sudo apt-add-repository ppa:dansmith/chirp-snapshots >>> sudo apt-get update >>> sudo apt-get install chirp-daily >>> >>> After chirp-daily is installed, run it. >>> >>> ONLY then can you program your radio. If you do not use the daily build >>> you will have problems. >>> >>> >>> To run the program you can type chirp-daily and it will run. >>> >>> David >>> >>> >>> On Thu, Dec 11, 2014 at 2:33 PM, y_61(a)libero.it <y_61(a)libero.it> wrote: >>> >>>> >>>> ok i downlod the iso and create the boot on usb... >>>> >>>> now, i connect the cable to programm into the usb port and ? >>>> >>>> >>>> there is some works to function the cable to chirp or none ? >>>> >>>> >>>> 73 >>>> >>>> >>>> >>>> ----Messaggio originale---- >>>> Da: n1ea(a)arrl.net >>>> Data: 10-dic-2014 20.44 >>>> A: "y_61(a)libero.it"<y_61(a)libero.it> >>>> Ogg: Re: R: Re: [chirp_users] Who used CHIRP in linux ubuntu mode ? >>>> >>>> I have twice sent you the link for the iso. >>>> >>>> Download Unetbootin anr use the iso I sent you twice before. >>>> >>>> Make sure you upgrade to latest daily build of CHIRP if you have >>>> Baofeng radio. >>>> >>>> CHIRP is available for Windows also. >>>> >>>> David >>>> On Dec 10, 2014 2:18 PM, "y_61(a)libero.it" <y_61(a)libero.it> wrote: >>>> >>>>> >>>>> >>>>> >>>>> sorry i am not expert ? please send to me the link to download the >>>>> chirp ISO to usb pen boot ? >>>>> >>>>> >>>>> help me.... 73 >>>>> >>>>> ----Messaggio originale---- >>>>> Da: n1ea(a)arrl.net >>>>> Data: 9-dic-2014 22.19 >>>>> A: "y_61(a)libero.it"<y_61(a)libero.it> >>>>> Ogg: Re: [chirp_users] Who used CHIRP in linux ubuntu mode ? >>>>> >>>>> See this message for iso. IMPORTANT read #2 link about UV5R first. >>>>> >>>>> David >>>>> On Dec 8, 2014 6:10 PM, "David Ranch" <chirp(a)trinnet.net> wrote: >>>>> >>>>>> >>>>>> Try out Andy's HamRadio ISO: >>>>>> >>>>>> http://sourceforge.net/projects/kb1oiq-andysham/ >>>>>> >>>>>> It has Chirp pre-installed but you'll probably want to upgrade it >>>>>> before >>>>>> you run it. After that, just follow the Chirp documentation. Since >>>>>> you're using a UV-5R, see: >>>>>> >>>>>> http://www.miklor.com/COM/UV_CHIRP.php >>>>>> >>>>>> --David >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On 12/08/2014 02:06 AM, y_61(a)libero.it wrote: >>>>>> > Hi, sorry i have a baofeng UV-5R release BFS 297… ( july 2014 i >>>>>> buy ) >>>>>> > >>>>>> > >>>>>> > >>>>>> > I whant yo create a CHIRP on usb pen boot , I think is work on >>>>>> ubuntu or >>>>>> > linux ? >>>>>> > >>>>>> > PLEASE In how mode I create it ? >>>>>> > >>>>>> > I have the programm unebootin for create with the ISO the boot >>>>>> chirp on the >>>>>> > Usb pen. >>>>>> > >>>>>> > But, where I downoad the CORRECT ISO immage for my baofenf UV-5R >>>>>> > BFS 297 version ? >>>>>> > >>>>>> > I use a comunication cable buy on amazon ( I think is a clone ) in >>>>>> this case >>>>>> > with NO use windows but linux…no driver is request ? >>>>>> > >>>>>> > VERY IMPORTANT , after the boot whith this chirp on usb pen drive >>>>>> in linux, >>>>>> > what I to do to install the driver or start the comunication for >>>>>> the cable to >>>>>> > my pc ??? >>>>>> > >>>>>> > Or I insert the cable in a usb port and is finish ? I oper the >>>>>> chirp program >>>>>> > and select in “radio” and read the data memory ? >>>>>> > >>>>>> > Thanks for help, best 73 >>>>>> > >>>>>> > >>>>>> > _______________________________________________ >>>>>> > chirp_users mailing list >>>>>> > chirp_users(a)intrepid.danplanet.com >>>>>> > http://intrepid.danplanet.com/mailman/listinfo/chirp_users >>>>>> >>>>>> _______________________________________________ >>>>>> chirp_users mailing list >>>>>> chirp_users(a)intrepid.danplanet.com >>>>>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users >>>>>> >>>>> >>>>> >>>>> >>>> >>>> >>> >>> >>> >> >> > > > > > >

1 0

[chirp_users] Special Mode?
by David B. Horvath, CCP 08 Jan '15

08 Jan '15

I want to be able to program in frequencies that aren't in the normal HAM range. My intent is to monitor those frequencies -- I'm not planning on transmitting. I realize this isn't a good choice but better than carrying multiple radios. I can program these frequencies by hand but the software tries to "protect me from myself". UV-5RB Is that possible? - David At 03:00 PM 1/7/2015, chirp_users-request(a)intrepid.danplanet.com wrote: >Send chirp_users mailing list submissions to > chirp_users(a)intrepid.danplanet.com > >To subscribe or unsubscribe via the World Wide Web, visit > http://intrepid.danplanet.com/mailman/listinfo/chirp_users >or, via email, send a message with subject or body 'help' to > chirp_users-request(a)intrepid.danplanet.com > >You can reach the person managing the list at > chirp_users-owner(a)intrepid.danplanet.com > >When replying, please edit your Subject line so it is more specific >than "Re: Contents of chirp_users digest..." > > >Today's Topics: > > 1. Support for Icom IC-7100 (Bob Nielsen) > 2. Feidaxin FD-268A (Richard AG5M) > 3. Re: Support for Icom IC-7100 (Tom Hayward) > 4. Re: Yaesu FT-8100? (Tom Hayward) > 5. Re: Unsupported Firmware (Jim Unroe) > 6. Re: Feidaxin FD-268A (Grant Diffey) > > >---------------------------------------------------------------------- > >Message: 1 >Date: Tue, 6 Jan 2015 12:51:03 -0800 >From: Bob Nielsen <n7xy(a)clearwire.net> >Subject: [chirp_users] Support for Icom IC-7100 >To: Discussion of CHIRP <chirp_users(a)intrepid.danplanet.com> >Message-ID: <D2836824-703E-4DD6-AE4A-9094042BA012(a)clearwire.net> >Content-Type: text/plain; charset=us-ascii > >Is Chirp support planned for the Icom IC-7100? > >Bob, N7XY > > > >------------------------------ > >Message: 2 >Date: Tue, 6 Jan 2015 15:04:36 -0800 >From: Richard AG5M <ag5m(a)yahoo.com> >Subject: [chirp_users] Feidaxin FD-268A >To: Discussion of CHIRP <chirp_users(a)intrepid.danplanet.com> >Message-ID: > <1420585476.96613.YahooMailBasic(a)web164004.mail.gq1.yahoo.com> >Content-Type: text/plain; charset=us-ascii > >How can I request CHIRP to develop the programming for the Feidaxin >FD-286A? I saw no place to make such a request on their website. >Or for that matter, does anyone know of software to program this >little Chinese HT. It's actually quite a nice little >thing. Thanks, Richard AG5M > > >------------------------------ > >Message: 3 >Date: Tue, 6 Jan 2015 15:19:32 -0800 >From: Tom Hayward <tom(a)tomh.us> >Subject: Re: [chirp_users] Support for Icom IC-7100 >To: Discussion of CHIRP <chirp_users(a)intrepid.danplanet.com> >Message-ID: > <CAFXO5Z17caPioWOy9x1X705bTZmpP-X3NjcE=9H+3RQGraekxQ(a)mail.gmail.com> >Content-Type: text/plain; charset=UTF-8 > >On Tue, Jan 6, 2015 at 12:51 PM, Bob Nielsen <n7xy(a)clearwire.net> wrote: > > > > Is Chirp support planned for the Icom IC-7100? > > > > Bob, N7XY > >http://chirp.danplanet.com/issues/1003 > >Looks like none of the developers have an IC-7100. > >Tom KD7LXL > > >------------------------------ > >Message: 4 >Date: Tue, 6 Jan 2015 15:30:58 -0800 >From: Tom Hayward <tom(a)tomh.us> >Subject: Re: [chirp_users] Yaesu FT-8100? >To: Discussion of CHIRP <chirp_users(a)intrepid.danplanet.com> >Message-ID: > <CAFXO5Z1hRxXO=jzXV4DkFMOK+DYQ7-RN3qqP6_VdQfWWXKetSg(a)mail.gmail.com> >Content-Type: text/plain; charset=UTF-8 > >On Mon, Jan 5, 2015 at 6:08 PM, Eric Allen <eric(a)hackerengineer.net> wrote: > > Hey folks, > > > > I recently picked up a Yaesu FT-8100, and I'm looking to program it with > > CHIRP. Has anybody else given this bad boy a shot? It looks to be > > programmable, so I'm hoping to adapt the CHIRP support for one of the other > > Yaesu mobiles, but I'm hoping maybe it's actually easier than that. > >Yaesus are generally pretty easy to write support for. They all use >the same clone "protocol" (really just a dump of their memory with no >protocol per se). Start with a similar model and try a Download From >Radio. If it's an exact match, everything will work fine. If not, an >error will be reported. You'll want to save the .img and inspect it >with a hex editor after the failed download. Tweak memsize to make >sure you get the whole thing. > >This type of conversation is more appropriate for the chirp_devel list: >http://intrepid.danplanet.com/mailman/listinfo/chirp_devel > >Tom KD7LXL > > >------------------------------ > >Message: 5 >Date: Tue, 6 Jan 2015 19:22:18 -0500 >From: Jim Unroe <rock.unroe(a)gmail.com> >Subject: Re: [chirp_users] Unsupported Firmware >To: Greg Hicks <grizhicks(a)yahoo.com>, Discussion of CHIRP > <chirp_users(a)intrepid.danplanet.com> >Message-ID: > <CADnO8U5PqKCTBu_RZGC=YypwT5ZNCB6pNHTWQ57uXkFZbuMjXA(a)mail.gmail.com> >Content-Type: text/plain; charset=UTF-8 > >On Tue, Jan 6, 2015 at 7:30 AM, Greg Hicks <grizhicks(a)yahoo.com> wrote: > > Good Morning to All from new guy.... > > > > Greg here in Indianapolis, and brand new to the group & using CHIRP. Just > > received a BaoFeng BF-F8HP yesterday and have been playing with. I was > > amble to download from radio, but not upload. When I try to upload a new > > 'img' file, I get the following error message: > > > > Unsupported firmware version: N5R3401F8HP-1 > > > > Not sure how to look for this, nor where to find. > > > > Thanks, in advance for any help..... Greg > > > > <===><===><===><===><===> > > Greg Hicks, K9TLA > > Hancock County CERT Program Manager > > 317-501-5389 (cell) > > <===><===><===><===><===> > >Greg, > >You currently should not be using the CHIRP stable build for any >Baofeng/Pofung radios because of memory layout changes in the latest >models. Also, the CHIRP stable build does not support the radios with >3 power levels (see the Support Radios list on the CHIRP home page. >Upgrade to the latest CHIRP daily build and you should be OK. > >Jim KC9HI > > >------------------------------ > >Message: 6 >Date: Wed, 7 Jan 2015 12:37:53 +1100 >From: Grant Diffey <gdiffey(a)gmail.com> >Subject: Re: [chirp_users] Feidaxin FD-268A >To: ag5m(a)yahoo.com, Discussion of CHIRP > <chirp_users(a)intrepid.danplanet.com> >Message-ID: > <CACckToX5Ek4W+TjD4d0UGdcSJUutan0d=Wc_fgt_GbQ9e5qFpg(a)mail.gmail.com> >Content-Type: text/plain; charset="utf-8" > >Richard, > >Did you see: > >http://chirp.danplanet.com/projects/chirp/wiki/FAQ#How-can-I-get-my-radio-s… > > > >On Wed, Jan 7, 2015 at 10:04 AM, Richard AG5M <ag5m(a)yahoo.com> wrote: > > > How can I request CHIRP to develop the programming for the Feidaxin > > FD-286A? I saw no place to make such a request on their website. > > Or for that matter, does anyone know of software to program this little > > Chinese HT. It's actually quite a nice little thing. Thanks, Richard AG5M > > _______________________________________________ > > chirp_users mailing list > > chirp_users(a)intrepid.danplanet.com > > http://intrepid.danplanet.com/mailman/listinfo/chirp_users > > >

2 1

[chirp_users] Yaesu FT-8100?
by Eric Allen 07 Jan '15

07 Jan '15

Hey folks, I recently picked up a Yaesu FT-8100, and I'm looking to program it with CHIRP. Has anybody else given this bad boy a shot? It looks to be programmable, so I'm hoping to adapt the CHIRP support for one of the other Yaesu mobiles, but I'm hoping maybe it's actually easier than that.

5 4

[chirp_users] Unsupported Firmware
by Greg Hicks 07 Jan '15

07 Jan '15

Good Morning to All from new guy.... Greg here in Indianapolis, and brand new to the group & using CHIRP. Just received a BaoFeng BF-F8HP yesterday and have been playing with. I was amble to download from radio, but not upload. When I try to upload a new 'img' file, I get the following error message: Unsupported firmware version: N5R3401F8HP-1 Not sure how to look for this, nor where to find. Thanks, in advance for any help..... Greg <===><===><===><===><===> Greg Hicks, K9TLA Hancock County CERT Program Manager 317-501-5389 (cell) <===><===><===><===><===>

2 1

[chirp_users] Support for Icom ID-51E Special Edition
by Håken Hveem 06 Jan '15

06 Jan '15

Hello, is there any support for the Support for Icom ID-51E Special Edition at the moment, or is this planned ? LA1RMA -- Håken Hveem Gnup/PGP key ID: 45793A72

3 2

Re: [chirp_users] Raspberry PI rev level.
by Bob Boehme 04 Jan '15

04 Jan '15

Yes you have to go to the chirp site and download the latest.. Raspberry site has a really old version.. From: chirp_users-bounces(a)intrepid.danplanet.com [mailto:chirp_users-bounces@intrepid.danplanet.com] On Behalf Of Chuck Hast Sent: Saturday, January 03, 2015 10:04 AM To: Discussion of CHIRP Subject: [chirp_users] Raspberry PI rev level. I noticed that the rev level for the RasPi is 0.1.12 is there newer rev level for the RasPi? if not what do i need to get to the 0.4.1 rev level for the RasPi?

1 0

[chirp_users] Raspberry PI rev level.
by Chuck Hast 03 Jan '15

03 Jan '15

I noticed that the rev level for the RasPi is 0.1.12 is there newer rev level for the RasPi? if not what do i need to get to the 0.4.1 rev level for the RasPi?

1 0

Re: [chirp_users] UV-5R Says "Radio did not respond"
by Bob Boehme 03 Jan '15

03 Jan '15

The plug does not go all the way in on some of the newer radios... trim a bit off the side with a knife and it will go all the way in.. -----Original Message----- From: chirp_users-bounces(a)intrepid.danplanet.com [mailto:chirp_users-bounces@intrepid.danplanet.com] On Behalf Of Richard Dillman Sent: Friday, January 02, 2015 3:55 PM To: Jim Unroe; Discussion of CHIRP Subject: Re: [chirp_users] UV-5R Says "Radio did not respond" >Hi Richard, > >Since the programming cable already works with your radio, the driver >and programming cable must be OK. This means the problem is that you >are not getting the plug fully engaged in the radio. > >Jim KC9HI Hi Jim. You are always quick to respond with helpful advice. Thanks! Yeah, I encountered that plug seating issue with my own UV-5RA so with the UV-5R radio I really put some pressure on the connector - even trimmed the plug. But no joy. So maybe a defective connector on the radio side. Best, RD ================================= Richard Dillman, T2-GB-061170 Chief Operator, Coast Station KSM Maritime Radio Historical Society http://www.radiomarine.org ================================= _______________________________________________ chirp_users mailing list chirp_users(a)intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users

1 0

[chirp_users] Account signup and FT1D
by Bret Palsson 03 Jan '15

03 Jan '15

Hi fellow CHIRP users/developers! Account signup: I never got my account verification email when registering. :( http://chirp.danplanet.com/login FT1D: I own this radio and I see support is being developed for it, just recently. I have already written a python program to dump the memory and I have decompiled the adms binary to source. I have the MemoryDataBase offsets, meanings, and code to generate the memory. Anyway I’d like to help out, I’m an software engineer with motivation to get my radio working. ;) -Bret public byte[] eepromDataArray = new byte[130496]; public Memory memData = new Memory(); public SetMode setData = new SetMode(); public Comment CommentData = new Comment(); private int memDtbsCpuType = 0; public const int EEPROM_ARRAY_SIZE = 130496; public const int EEPROM_MEM_BAND_COMMON_DATA_SIZE = 64; public const int EEPROM_MEM_BAND_SINGLE_DATA_SIZE = 128; public const int EEPROM_VFO_HONE_MEM_COMMON_DATA_SIZE = 32; public const int EEPROM_SP_TONE_SQL_DATA_SIZE = 1; public const int EEPROM_JR_SQL_DATA_SIZE = 1; public const int EEPROM_MEM_BANK_CH_NUM_DATA_SIZE = 2; public const int EEPROM_MEM_CH_DIR_DATA_SIZE = 1; public const int EEPROM_WX_MEM_AN_DATA_SIZE = 18; public const int EEPROM_BANK_NAME_DATA_SIZE = 18; public const int EEPROM_DTMF_MEM_DATA_SIZE = 16; public const int EEPROM_STATUS_TEXT_DATA_SIZE = 60; public const int EEPROM_WIRES_X_DATA_SIZE = 16; public const int EEPROM_GM_GROUP_NAME_DATA_SIZE = 16; public const int EEPROM_GM_MEMBER_NAME_DATA_SIZE = 15; public const int EEPROM_GM_MEMBER_NAME_RSV_DATA_SIZE = 5; public const int EEPROM_GM_MSG_SAVE_DATA_SIZE = 80; public const int EEPROM_GPS_POSITION_DATA_SIZE = 28; public const int EEPROM_DIGITAL_CALL_SIGN_DATA_SIZE = 10; public const int EEPROM_APRS_MYCALL_SSID_BIN_DATA_SIZE = 7; public const int EEPROM_APRS_MYCALL_SSID_STR_DATA_SIZE = 9; public const int EEPROM_APRS_MYCALL_STR_DATA_SIZE = 6; public const int EEPROM_APRS_SSID_STR_DATA_SIZE = 2; public const int EEPROM_APRS_DIGIPATH_DATA_SIZE = 8; public const int EEPROM_APRS_MSG_TEXT_DATA_SIZE = 16; public const int EEPROM_APRS_MSG_SET_DATA_SIZE = 9; public const int EEPROM1_RCV1_OFFSET = 0; public const int EEPROM1_BAND_INDIVIDUAL_BAK_A_OFFSET = 64; public const int EEPROM1_BAND_INDIVIDUAL_BAK_B_OFFSET = 576; public const int EEPROM1_SET_MODE_OFFSET = 1088; public const int EEPROM1_BAND_COMMON_OFFSET = 1472; public const int EEPROM1_BAND_COMMON_BAK_OFFSET = 1536; public const int EEPROM1_ABAND_INDIVIDUAL_OFFSET = 1600; public const int EEPROM1_ABAND_INDIVIDUAL_BAK_OFFSET = 1728; public const int EEPROM1_BBAND_INDIVIDUAL_OFFSET = 1856; public const int EEPROM1_BBAND_INDIVIDUAL_BAK_OFFSET = 1984; public const int EEPROM1_RBAND_INDIVIDUAL_OFFSET = 2112; public const int EEPROM1_RBAND_INDIVIDUAL_BAK_OFFSET = 2240; public const int EEPROM1_DTMF_MEM_OFFSET = 2368; public const int EEPROM1_RCV2_OFFSET = 2624; public const int EEPROM1_WX_MEM_AN_OFFSET = 3648; public const int EEPROM1_BANK_NAME_OFFSET = 3828; public const int EEPROM1_HOME_CH_OFFSET = 4288; public const int EEPROM1_ABAND_VFO_OFFSET = 4672; public const int EEPROM1_BBAND_VFO_OFFSET = 5056; public const int EEPROM1_MEM_BANK_CH_NUM_OFFSET = 5440; public const int EEPROM1_MEM_CH_DIR_OFFSET = 10240; public const int EEPROM1_MEM_CH_NORM_OFFSET = 11584; public const int EEPROM1_MEM_CH_SKIP_OFFSET = 40384; public const int EEPROM1_MEM_CH_RCV_OFFSET = 43552; public const int EEPROM1_MEM_CH_PMS_OFFSET = 43584; public const int EEPROM1_RCV3_OFFSET = 46784; public const int EEPROM1_SPTONE_SQL_OFFSET = 47744; public const int EEPROM1_JR_SQL_OFFSET = 47808; public const int EEPROM1_RCV4_OFFSET = 47872; public const int EEPROM1_APRS_OFFSET = 48832; public const int EEPROM1_GPS_POSI_OFFSET = 49472; public const int EEPROM1_STATUS_TEXT_OFFSET = 49760; public const int EEPROM1_RCV5_OFFSET = 50064; public const int EEPROM1_DIGITAL_OFFSET = 52928; public const int EEPROM1_RCV6_OFFSET = 53312; public const int EEPROM1_RCV7_OFFSET = 57024; public const int EEPROM1_POWER_SW_OFFSET = 65214; public const int EEPROM2_APRS_BEACON_DIR_OFFSET = 65216; public const int EEPROM2_APRS_BEACON_DATA_OFFSET = 67136; public const int EEPROM2_APRS_MESSAGE_DIR_OFFSET = 77696; public const int EEPROM2_APRS_MESSAGE_DATA_OFFSET = 79616; public const int EEPROM2_RCV1_OFFSET = 88256; public const int EEPROM2_GM_OFFSET = 114112; public const int EEPROM2_WIRES_X_OFFSET = 122304; public const int EEPROM2_RCV2_OFFSET = 126400; public const int MEMORY_NORM_DIR_OFFSET = 0; public const int MEMORY_SKIP_DIR_OFFSET = 900; public const int MEMORY_PMS_DIR_OFFSET = 1000; public const int MEMORY_WX_DIR_OFFSET = 1100; public const int MEMORY_JR_SQL_DIR_OFFSET = 1110; public const int MEMORY_INTERNATIONAL_VHF_DIR_OFFSET = 1130; public const int MEMORY_SPTONE_SQL_DIR_OFFSET = 1190; public const int MEMORY_WIRELESS_C_DIR_OFFSET = 1210; public const int MEMORY_EMERGENCY_DIR_OFFSET = 1230; public const int MEMORY_FIRE_DIR_OFFSET = 1250; public const int MEMORY_RCV_DIR_OFFSET = 1336; public const int GROUP_NAME_ORIGINAL_TBL_OFFSET = 160;

2 1