<div dir="ltr">HI Chuck,<div><br></div><div>Yes, set the define in harfwareprofile.h.</div><div><br></div><div>I'll go dig out the schematic for this repeater a double check what is in the path for the discriminator.</div><div><br></div><div>I believe the change to the alternate squelch/RSSI has virtually eliminated the squelch tail, but the jury is still out until I listen some more to actual traffic.</div><div><br></div><div><br></div><div>Lee</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Jun 5, 2016 at 9:35 AM, Chuck Henderson <span dir="ltr"><<a href="mailto:rpt2@chuck.midlandsnetworking.com" target="_blank">rpt2@chuck.midlandsnetworking.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">If anyone if off frequency a little bit that will make the voice talk off worse. Double check that the repeater and the users are all on frequency. Don't use narrow bandwidth on the repeater receiver. Make sure that the discriminator audio is not rolled off even a little bit at the high end. There should not be resistors in series or capacitors to ground between the discriminator chip output pin and the voter board input, for best results. I tried DSPBEW a couple of times but don't use it on any of my repeaters. <div>Did you uncomment line 64 in HardwareProfile.h to get both of my changes?</div><div>One change is to the squelch action and the other is to how RSSI is calculated.</div><div>Also, I comment out </div><div><font color="#ff0000">;thresholds =</font></div><div>and set </div><div><font color="#ff0000">linger = 0</font></div><div>in /etc/asterisk/voter.conf</div><div>Chuck, WB9UUS</div><span class=""><div><br></div><div><br><div><br><div><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jun 3, 2016 at 7:04 PM, Lee Woldanski <span dir="ltr"><<a href="mailto:ve7fet@tparc.org" target="_blank">ve7fet@tparc.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr">I am in the process of deploying my first of a few VOTER (through hole) boards in the conversion of one of my local repeater to add voting.<div><br></div><div>My master receiver with transmit is running on an ICOM FR5000, using discriminator out, carrier squelch (no PL), with a VOTER (of course).</div><div><br></div><div>I've got a couple questions that hopefully someone can answer for me.</div><div><br></div><div><br></div><div>1) I've noticed with the default (v1.50) firmware running, I am getting nasty squelch crashes when a user un-keys.</div><div><br></div><div>Watching it in Allmon2, there looks like there is a LOT of flutter on the signals, going from near 255 all the way down to the hundreds. The flutter seems to be co-incident with voice peaks. Looking in the source code, this appears it should have been fixed... yet I still see the artifacts?</div><div><br></div><div>The squelch crash seems to be co-incident with the RSSI dropping near 0 when the user un-keys. Which would be fine for the 2-level squelch action, if it were true... but the users seem to have a strong signal otherwise.</div><div><br></div><div>2) Would DSPBEW help with this? Anyone running an FR5000 want to comment on their configuration?</div><div><br></div><div>3) I've compiled and loaded "Chuck Squelch" on it, and it is definitely an improvement. We'll see if I like the change. </div><div><br></div><div>Related to that, do I need to do the diode/squelch calibration routines every time I re-flash the firmware, or will those settings be retained in EEPROM (and would they be the same between the different firmware)?<br></div><div><br></div><div><br></div><div>So far I am liking the opportunities this change from a hardware controller is enabling. A BIG thanks to everyone who has put their time and effort in developing the hardware and software to get to where it is today.</div><div><br></div><div><br></div><div>Cheers!<span><font color="#888888"><br clear="all"><div><br></div>-- <br><div data-smartmail="gmail_signature">Lee Woldanski, AScT<br>VE7FET</div>
</font></span></div></div>
<br>_______________________________________________<br>
App_rpt-users mailing list<br>
<a href="mailto:App_rpt-users@ohnosec.org" target="_blank">App_rpt-users@ohnosec.org</a><br>
<a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users" rel="noreferrer" target="_blank">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a><br>
<br>
To unsubscribe from this list please visit <a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users" rel="noreferrer" target="_blank">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a> and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"<br>
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. <br></blockquote></div><br></div></span></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">Lee Woldanski, AScT<br>VE7FET</div>
</div>