{ "numMessagesInTopic": 17, "nextInTime": 83, "senderId": "Irmc8rkw159y_diCU8edUSt3bb3q4jMNMJD2wq5ENG1SOgDiIDP3PgFzoZd0dqrkgF4NyJewE3A_9EOkDPfFLZ8sjXo", "systemMessage": false, "subject": "Re: [GE-Mpa] Re: MPA Squelch Help", "from": "Gary Peterson <NZ5V@...>", "authorName": "Gary Peterson", "msgSnippet": "Mark; I think it was a 628 board in that radio, almost for certian. Didn t show any signs of loosing the flash or personality, but then I didn t use it, I just", "msgId": 82, "profile": "gs79602", "topicId": 72, "spamInfo": { "reason": "12", "isSpam": false }, "replyTo": "LIST", "userId": 157218573, "messageBody": "
\n\nHi Don, Gary, Darin & Morgan,\n \n
\nWhen I mentioned (over the weekend) about the incorrect tracking data
\ninfo vs. radio personality info being written to a radio and the
\nsquelch not functioning, that was when using NORMAL SOFTWARE, not ham
\nflash.
\n
\nHamflash is not that sophisticated, and is quite basic actually
\ncompared to the normal programming software.
\n
\nHamflash only writes one set of tracking data values to cover a
\nlimited frequency range.
\n
\nNormal software to cover the 20 MHz (or greater) frequency range,
\nseveral sets of tracking data values must be written. Think of it
\nlike a graphic equalizer type arrangement, like found on a stereo. A
\nband split is broken-up into smaller sub-bands. Each value controls
\na single sub-band's operation. In the M-PA, this is a bit complex.
\nTracking data is bandsplit specific. If the radio's tracking data is
\nfor a 146-162 MHz bandsplit, and you program it with a 136-150 MHz
\npersonality, the "Fit" will not be correct, performance will suffer.
\nSquelch being the most obvious indicator that something is not
\nright. There is a bunch of background data written to the radio via
\ntracking data, not just what you see on the screen. This is why you
\nsometimes see an error message when you try to program a radio
\nindicating the "model and/or bandsplit does not match", "do you wish
\nto overwrite?".
\n
\nWhereas hamflash is a very simple solution. Only one set of tracking
\ndata values (high tx power, low tx power, deviation, squelch) is
\nwritten to cover a limited bandwidth (2m = 4 MHz, 70cm = 10 MHz,
\netc.) Only the most basic data is written. :o) Simple, but
\neffective. None of the bandsplit sensitive background data and
\nEEPROM mapping format used in normal software. But because it is
\nsimpler (and less efficient), you only get 48 channels with hamflash
\nvs. 192 with regular software.
\n
\nGary (NZ5V) wrote:
\n------------------------
\n> The fellow that he bought the radio from
\n> is me, NZ5V, and that radio was moved from
\n> 403-23 up to 430-450 by me with an hp8754a
\n> network analyzer
\n
\n
\nThe hamflash does not audit or care what bandsplit of hardware is
\nbeing used. I have used hamflash on all bandsplits in testing. Yes,
\nthe defaults are 146/446/921, but if a 420 radio is connected, the
\nradio will show an unlock condition, make a bunch of racket, and the
\ndisplay flash. Program a frequency within the hardware's designed
\nbandsplit (in this case, 420 MHz), the radio will lock on frequency,
\nquit giving error indications and function correctly.
\n
\nGary, I don't think your mod'ing a 420 board up to 440 is the issue
\nhere.
\n
\n
\n
\n...There is one other item which can cause this issue: A Dead
\nmemory battery.
\n
\n
\nIf the Control/Logic board contained within this radio is the older
\n628 style of EDACS control/logic board, it has a 3 volt lithium
\nbattery for retention of tracking data. And like the much older M-
\nPD radios, if this battery dies, the radio looses all tracking data.
\nObserved result: Poor TX output power, poor deviation, and the
\nsquelch slams shut!
\n
\nCheck the voltage on this little pin looking battery. The case is
\n(+) and the little pin is (-). You do not need to remove it from the
\nboard to test. It should be 2.4 volts or stronger. If it is below
\n2.5 volts, I would strongly suggest replacing it. Do not forget to
\nwrite down you tracking data values, as they will be lost when the
\nbattery is removed, and will need to be re-entered for proper
\noperation.
\n
\n
\nNOTE:
\nThe original hard-coded board did not have this memory battery to
\nfail.
\n
\nThe final generation Ø81 boards had a non-volatile memory and did not
\nrequire a battery to retain the tracking data values.
\n
\n
\n
\n
\nMark C. KB4CVN
\n
\n
\n--- In GE-Mpa@yahoogroups.com, Gary Peterson <NZ5V@a...> wrote:
\n> Ok,
\n>
\n> The fellow that he bought the radio from is me, NZ5V, and that
\nradio was
\n> moved from 403-23 up to 430-450 by me with an hp8754a network
\nanalyzer,
\n> checked on my M2550A service monitor, and it was sold to him and
\n> hamflashed at his request, with the disclaimer in the ebay listing\n
\nthat
\n> I didn't warranty hamflash'ed radios for programming problems. \nThe
\n> radio was successfully flashed, radio type changed to UHF, and a
\nreset
\n> was done and the radio was shipped.
\n>
\n> And, I have already offered to re-flash it conventional or EDACS
\nand
\n> program it at no charge for him, if he pays the freight both ways,\n
\nand
\n> supplies the personality file, or uses no more than 8 pairs.
\n>
\n> I suggested he join this group so that he could get the benefit of\n
\nthose
\n> in the group who are Hamflash savy, which I am not. And for the
\nrecord,
\n> if I messed it up, I will fix it.
\n>
\n> Gary
\n> NZ5V
\n>
\n>
\n>
\n>
\n>
\n> Don Colucci wrote:
\n>
\n> > Thanks Mark, im not sure what the problem is the radio was
\nourchased
\n> > on Ebay from a fellow ham who claims no liability for\nprogramming
\n> > issues which is fine but all the help he has offered is to\nread
\nthe
\n> > manual, all i can find in the manual is set the hexidecimal
\nsettings
\n> > which i have no idea what that means. So what can i do to get\nthe
\n> > radio to work, can i reset the radio with out removing\nhamflash or
\n> > the softwware because i do not have any programming\ncapabilities?
\n> >
\n> > --- In GE-Mpa@yahoogroups.com, "Mark Cobbeldick"\n<kb4cvn@y...>
\nwrote:
\n> > > In a 'normal' or non-hamflashed M-PA, the following can\ncause a
\n> > radio
\n> > > to not unmute on a received signal, but show a busy\nindication
\non
\n> > the
\n> > > LCD display:
\n> > >
\n> > > 1- The Squelch tracking data value is set too high, and
\nbasically
\n> > the
\n> > > radio would have trouble receiving a 0 dBm signal\ninjected into
\n> > the
\n> > > antenna connector.
\n> > >
\n> > > 2- The wrong bandsplit is programed into the radio,\ntherefore
\n> > skewing
\n> > > the tracking data settings.
\n> > >
\n> > >
\n> > > EXAMPLES:
\n> > > A radio with a 135-150 MHz RF Deck is programed as a\n146-162
\n> > > bandsplit,
\n> > >
\n> > > A 146-162 radio is programed as a 136-150 unit.
\n> > >
\n> > > Be careful in this area. If in doubt, disassmble the\nradio
\n> > (simply
\n> > > remove the rear cover off the radio) and check the part\nnumber
\nof
\n> > the
\n> > > assembly (or rf deck contained within) against the\nnumbers
\nlisted
\n> > in
\n> > > the parts catalog (in the FILES area), and verify it is\nindeed
\n> > what
\n> > > you THINK IT IS !!!
\n> > >
\n> > > If the "mix" of hardware & programing is incorrect,\na ton of TNT
\n> > > won't get the receiver to open without pressing the blue\nbutton.
\n> > >
\n> > >
\n> > > Now, when it comes to hamflashed radios, I have not come\nacross
\n> > this
\n> > > malady before. Try resetting the radio's hamflash\nconfiguration
\n> > over
\n> > > in SET-UP MODE. This will revert the radio's tracking\ndata back
\n> > to a
\n> > > default level. If it is a 2meter unit, the default\nfrequency
\n> > written
\n> > > to all 48 memories will be 146.520 MHz simplex. In a\nuhf radio
\n> > this
\n> > > will be 446.000. And in a 900 radio, this will be\n921.000. If
\n> > there
\n> > > is nothing wrong with the radio's hardware, it should(?)\nbe able
\n> > to
\n> > > receive signals on the displayed frequency. If it does\nnot,
\nthere
\n> > > could be other issues...
\n> > >
\n> > >
\n> > > 73,
\n> > > Mark C. KB4CVN
\n> > > Monroe, VA
\n> > >
\n> > >
\n> > >
\n> > >
\n> > > --- In GE-Mpa@yahoogroups.com, "Darin Watrous"\n<ke7bbf@c...>
\nwrote:
\n> > > > Thanks Morgan i have already checked that, there is\nno RX
\ntone.
\n> > > > ----- Original Message -----
\n> > > > From: Morgan Welker
\n> > > > To: GE-Mpa@yahoogroups.com
\n> > > > Sent: Sunday, August 07, 2005 1:06 PM
\n> > > > Subject: [GE-Mpa] Re: MPA Squelch Help
\n> > > >
\n> > > >
\n> > > > Don,
\n> > > > It sounds like you may have the radio programmed\nfor recieve
\n> > > channel
\n> > > > guard and the signal you are trying to recieve is\nnot
\n> > > transmitting the
\n> > > > channel guard tone. I'd make sure that you don't\nhave a
\ntone
\n> > > > programmed for recieve channel guard first, then\nworry about
\n> > > squelch
\n> > > > settings.
\n> > > > Good luck,
\n> > > > Morgan KG4BQI
\n> > > >
\n> >
\n> >
\n> >
\n> >
\n> >\n------------------------------------------------------------------
\n------
\n> > YAHOO! GROUPS LINKS
\n> >
\n> > * Visit your group "GE-Mpa
\n> > <http://groups.yahoo.com/group/GE-Mpa>"\non the web.
\n> >
\n> > * To unsubscribe from this group, send an email to:
\n> > GE-Mpa-unsubscribe@yahoogroups.com
\n> > <mailto:GE-Mpa-unsubscribe@yahoogroups.com?
\nsubject=Unsubscribe>
\n> >
\n> > * Your use of Yahoo! Groups is subject to the Yahoo!\nTerms of
\n> > Service <http://docs.yahoo.com/info/terms/>.
\n> >
\n> >
\n> >\n------------------------------------------------------------------
\n------
\n> >
\n
\n
\n
\n \n