<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; color: rgb(0, 0, 0);">
<span style="font-family: Arial, Helvetica, sans-serif; font-size: 11pt;">Thank you, Jim. Sorry, but I did not notice your text is actually below my original e-mail in your two replies today. I will address both replies here. Regarding your latest comment
below, I notice that I do not get a green Receive Light, there is no "tail drop" static or anything else on the monitor radio that indicates the transmitter has been keyed by the other radio. I repeated the test just now after walking over 100 yards away
from the monitor radio with similar results.</span></div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; color: rgb(0, 0, 0);">
<span style="font-family: Arial, Helvetica, sans-serif; font-size: 11pt;"><br>
</span></div>
<div class="elementToProof"><span style="font-family: Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">From your previous e-mail, thank you for providing the link to your Menu Reference sheet. I actually have a copy of that, which I downloaded
in 2018 and I use it as a guide regularly. I understand what you said about the preprogrammed channels saving the actual RX and TX frequencies instead of the Duplex and Offset values. That explains why I cannot see those values in the Menu pages. I tried
your tip for the Reverse Mode. Sure enough, an R appears at the top of the display next to the +- indication and the frequency changes to the TX frequency for that channel. For my test channel, the RX and TX frequencies shown are correct for the repeater.
See attached details for the repeater. My radio Menu also shows that R-DCS is OFF, R-CTCS is OFF and T-CTCS is 100.0HZ, which are appropriate for this repeater. Like I mentioned in my original e-mail, I copied the Keystone Peak repeater info directly from
the CHIRP provided Repeater Book .img file and pasted that into the Memories page for my radios. I am not sure if this is relevant, but it does concern me that all of the empty/not used cells for rToneFreq and cToneFreq in the .CSV files I exported have a
value of 88.5 in them. This includes the .CSV file I exported from the regional group of repeaters I selected from the CHIRP Repeater Book .img file. See the first attachment in my original e-mail. Something I am sure is relevant is that I switched my radio
to Frequency mode on both radios and manually entered 444.875 Mhz, an R-DCS value of OFF, an R-CTCS value of OFF, a T-CTCS value of 100.0HZ, a SFT-D value of + and an OFFSET value of 5.000 and the radios still do not work with the repeater in that configuration.</span></div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; color: rgb(0, 0, 0);">
<span style="font-family: Arial, Helvetica, sans-serif; font-size: 11pt;"><br>
</span></div>
<div class="elementToProof"><span style="font-family: Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">I believe it is possible I have an erroneous configuration in my CHIRP Settings page (that have more choices than the Menu pages on the
radios) that is causing this problem. However, I again performed a factory reset of both radios, I switched them to Frequency Mode and manually entered
</span><span style="font-family: Arial, Helvetica, sans-serif; font-size: 14.6667px; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);">444.875 Mhz, an R-DCS value of OFF, an R-CTCS value of OFF, a T-CTCS value of 100.0HZ, a SFT-D value of + and an
OFFSET value of 5.000 and the radios still do not work with the repeater in that configuration.</span><span style="font-family: Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);"> There are other selections in the Settings tab of CHIRP that
do not get erased/replaced during a Reset and we do use some custom settings in there, but I have a feeling they are not relevant to this problem. If there are no other ideas, then this is probably not a CHIRP problem and I will take this off the CHIRP Users
site and figure out how to find a local expert to solicit some help from. Thank you again for your time.</span></div>
<div class="elementToProof"><span style="font-family: Arial, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);"><br>
</span></div>
<div class="elementToProof"><span style="font-family: Arial, Helvetica, sans-serif; font-size: 14.6667px; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);">Alex Boerner</span></div>
<div class="elementToProof"><span style="font-family: Arial, Helvetica, sans-serif; font-size: 14.6667px; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);">KJ7CPZ</span></div>
<div id="appendonsend"></div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; color: rgb(0, 0, 0);">
<span style="font-family: Arial, Helvetica, sans-serif; font-size: 12pt;"></span><span style="font-family: Arial, Helvetica, sans-serif; font-size: 11pt;"><br>
</span></div>
<hr style="display: inline-block; width: 98%;">
<div dir="ltr" id="divRplyFwdMsg"><span style="font-family: Calibri, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);"><b>From:</b> chirp_users-bounces@intrepid.danplanet.com <chirp_users-bounces@intrepid.danplanet.com> on behalf of Jim Unroe <rock.unroe@gmail.com><br>
<b>Sent:</b> Wednesday, February 14, 2024 12:39 PM<br>
<b>To:</b> Discussion of CHIRP <chirp_users@intrepid.danplanet.com><br>
<b>Subject:</b> Re: [chirp_users] Baofeng UV-5R8W Repeater Config Error</span>
<div> </div>
</div>
<div><span style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">Hi Alex,<br>
<br>
On Wed, Feb 14, 2024 at 10:41 AM A Boer <aboertus@gmail.com> wrote:<br>
><br>
> Good day, CHIRP Users! I am having some trouble using CHIRP with some new radios I am trying to program. Simply put, I cannot get the repeater channels to work. I downloaded the .img file from one radio into CHIRP, copied and pasted the repeater configuration
from the CHIRP list of repeaters and pasted it into my .img file, then uploaded the .img file into both radios. The radios will not talk to each other through the repeater. I have gory details with screenshots and radio display pictures in the attached .jpg
files. If anyone has the time to review those details and has some ideas on how to fix this problem, I would certainly appreciate the feedback. Thank you for your time.<br>
><br>
> Alex Boerner<br>
> KJ7CPZ<br>
<br>
I forgot to mention that you cannot monitor yourself talking through a<br>
repeater with another radio close to you. The transmitting radio's<br>
off-frequency and close signal renders the receiver in the monitor<br>
radio deaf during the transmissions. Usually what happens is that when<br>
you release the PTT button, the receiver is no longer deaf and you<br>
hear the repeater's tail drop.<br>
<br>
Jim KC9HI<br>
_______________________________________________<br>
chirp_users mailing list<br>
chirp_users@intrepid.danplanet.com<br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" id="OWAd396f365-7dc1-473f-a7ed-f7834b4d3ffd" class="OWAAutoLink" data-auth="NotApplicable">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
This message was sent to Alex Boerner at aboertus@gmail.com<br>
To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com<br>
To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com<br>
Searchable archive: <a href="https://www.mail-archive.com/chirp_users@intrepid.danplanet.com" id="OWA0f30ac10-acb5-ca13-8f4b-a6ab596cc211" class="OWAAutoLink" data-auth="NotApplicable">
https://www.mail-archive.com/chirp_users@intrepid.danplanet.com</a></span></div>
</body>
</html>