Byte swapped version of the chip was unable to get the test point voltages above 150mV on either TX or RX, so I presume I have the byte order correct :-)
Data for the chip was generated with KPG21D (the programming software for this repeater) and validated with the formula from a 3rd party document detailing the frequency to hex code calculation. The binary data saved by KPG21D was edited with a hex editor to extract the 128 bytes needed for the frequency eeprom. _____ From: Repeater-Builder@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of DCFluX Sent: Wednesday, November 21, 2007 5:29 PM To: Repeater-Builder@yahoogroups.com Subject: Re: [Repeater-Builder] TKR-820 Reciever Issues Did you calculate the correct LO frequency? Also you may try reversing the high byte and low byte figures of the receive frequency. On 11/21/07, John Barrett <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> net > wrote: This one is for folks that know the Kenwood TKR-820 repeater :-) Or how to modify a VCO frequency range :-) I have a known working on 451.125/456.125 TKR-820 UHF repeater that I'm attempting to move down to 441.350/446.350. I've got the chip reprogrammed and the transmit VCO had no problems retuning to the target frequency (441.350). The receive VCO is another story. The manual says that PLL/VCO lock happens when the voltage from the PLL's integrator is between 4 and 5 volts, with a target of 4.5 volts. After adjusting the VCO's variable capacitor (the only adjustment available), the best I can get is 2.5 volts, and I'm getting a slow sawtooth on the integrator output from the PLL. This is surprising to me since it seems the RX and TX use identical PLL and VCO modules, and the RX VCO only has to tune down to 446.350. 5mhz higher than the TX. In any case.. the 2.5v control voltage is obviously incorrect since I cannot key the repeater with my HT at that adjustment. I have pulled the CTCSS configuration chip as recommended in one set of retuning instructions so I should be able to key the repeater without a PL (the repeater controller will be handling that in any case, so that chip will likely never be reinstalled). Any ideas what I might be doing wrong, or any tricks on how to get everything tuned up ??
