<div dir="ltr">The scope image in the OP shows there doesn't appear to be a problem with pulling hi or low, The transitions (without the RC) are very clean and go all the way to ground.. It seems like the URI is doing edge detection instead of level detection, and it's just missing fast edges. Wasn't sure if this was something that could be tweaked in software or if I'll have to put some external debounce logic on the line.<div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Sep 26, 2014 at 10:07 AM, Doug Crompton <span dir="ltr"><<a href="mailto:doug@crompton.com" target="_blank">doug@crompton.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div dir="ltr"><font color="#000000" face="Tahoma,sans-serif">Mike,<br><br> Before you change any timing make sure as Jon pointed out that your COS signal is going hard high and low on signal and non-signal. You might need a pullup. The URI is kind of weak in that regard. It should be TTL levels <.5 volt low and >2.5 volt high and preferably rail to rail.<br></font><span class=""><br><br><b><font style="font-size:16pt" size="4">73 Doug</font><font style="font-size:16pt" size="4"><br></font><font style="font-size:16pt" size="4">WA3DSP</font><font style="font-size:16pt" size="4"><br></font><font style="font-size:16pt" size="4"><a href="http://www.crompton.com/hamradio" target="_blank">http://www.crompton.com/hamradio</a></font></b><font style="font-size:16pt" size="4"><br></font><br><br></span><div><hr>From: <a href="mailto:kf7mbk@w7ara.net" target="_blank">kf7mbk@w7ara.net</a><br>Date: Fri, 26 Sep 2014 09:56:21 -0700<br>Subject: Re: [App_rpt-users] Fwd: COR signal getting confused<br>To: <a href="mailto:doug@crompton.com" target="_blank">doug@crompton.com</a><br>CC: <a href="mailto:app_rpt-users@ohnosec.org" target="_blank">app_rpt-users@ohnosec.org</a><div><div class="h5"><br><br><div dir="ltr">Doug,<div><br></div><div>First: thanks for the excellent writeup on getting allstar running on the BBB. I used it to get up and running very quickly and is the setup I am having this issue with.</div><div><br></div><div>I am running duplex =1 as well. I have not changed any timing values, (I'm essentially running the as-installed setup from the install image on your site) but I will take a look at them and see if I can make some changes for the better.</div><div><br></div><div>Thanks!</div><div>-Mike</div><div><br></div><div><br></div><div><br></div><div><br></div></div><div><br><div>On Fri, Sep 26, 2014 at 9:49 AM, Doug Crompton <span dir="ltr"><<a href="mailto:doug@crompton.com" target="_blank">doug@crompton.com</a>></span> wrote:<br><blockquote style="border-left:1px #ccc solid;padding-left:1ex">
<div><div dir="ltr"><hr>From: <a href="mailto:doug@crompton.com" target="_blank">doug@crompton.com</a><br>To: <a href="mailto:kf7mbk@w7ara.net" target="_blank">kf7mbk@w7ara.net</a><br>Subject: RE: [App_rpt-users] Fwd: COR signal getting confused<br>Date: Fri, 26 Sep 2014 12:46:14 -0400<br><br>
<div dir="ltr"><font color="#000000" face="Tahoma,sans-serif">That is very strange. Have you changed any of the default timing values? Are you using simplex/duplex? Courtesy tone? Timing values could effect that. <br><br>I use simplex with courtesy tone (duplex=1 in rpt.conf) on several nodes and I have never seen that problem. I have one user who has a signal like you describe. He walks in a park with a handheld and he is often in and out.<br><br>Also I assume you are not using any rxdelay?<br></font><br><b><font style="font-size:16pt" size="4">73 Doug</font><font style="font-size:16pt" size="4"><br></font><font style="font-size:16pt" size="4">WA3DSP</font><font style="font-size:16pt" size="4"><br></font><font style="font-size:16pt" size="4"><a href="http://www.crompton.com/hamradio" target="_blank">http://www.crompton.com/hamradio</a></font></b><font style="font-size:16pt" size="4"><br></font><br><br><div><hr>From: <a href="mailto:kf7mbk@w7ara.net" target="_blank">kf7mbk@w7ara.net</a><br>Date: Fri, 26 Sep 2014 08:50:51 -0700<br>To: <a href="mailto:app_rpt-users@ohnosec.org" target="_blank">app_rpt-users@ohnosec.org</a><br>Subject: [App_rpt-users] Fwd: COR signal getting confused<div><div><br><br><div dir="ltr"><div>Resending since my initial post has been pending moderation for 2 days now and got no reply from the list owner email.<br><br>I have modified an HT to bring out the receive LED signal and use it<br>
as the COR input to a DMK URI. It is a digital signal as viewed on a<br>
scope (i.e. very short slope in the transitions) This seems like it<br>
would work well and it does on strong signals. But on marginal signals<br>
where the LED may blink on and off quickly (like during picket<br>
fencing), it seems to confuse the URI (or the software) were it will<br>
start off good, but then a quick dropout of the COR signal will cause<br>
the software to no longer detect carrier, even though the signal on<br>
the COR input has been restored. Even if the input is solid high (or<br>
low in my case, I'm using usbinvert) it will not detect a carrier<br>
until there is another dropout of adequate time to "reset" it.<br>
<br>
I've tried putting a simple RC on the input but it didn't really help<br>
much. Seems the URI (or software) needs a significant minimum time<br>
between transitions to properly detect them, long enough that it would<br>
delay the carrier detection too much without a circuit more complex<br>
than an RC (i.e. something that would allow instant keyup, but delay<br>
the key down.)<br>
<br>
Linked is a scope image. </div><div><br></div><div><a href="https://lh5.googleusercontent.com/-CsJ9autUTAE/VCWK-uNJJpI/AAAAAAAAPSM/VsVvbPVvuEA/s800/20140923_184107.jpg" target="_blank">https://lh5.googleusercontent.com/-CsJ9autUTAE/VCWK-uNJJpI/AAAAAAAAPSM/VsVvbPVvuEA/s800/20140923_184107.jpg</a></div><div><br></div><div>Carrier was detected until this signal<br>
dropout event. Ch A is my RC filtered signal sent to the URI, Ch B is<br>
the signal out of the radio. Carrier was not detected after the 5th<br>
dropout even though the signal remained low.<br>
<br>
Anyone ever experience this and/or have ideas on how to fix it?<br>
<br>
Thanks.<br>
<br>
Mike<br>
KF7MBK<br>
</div><br></div>
<br></div></div><span>_______________________________________________
App_rpt-users mailing list
<a href="mailto:App_rpt-users@ohnosec.org" target="_blank">App_rpt-users@ohnosec.org</a>
<a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users" target="_blank">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a>
To unsubscribe from this list please visit <a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users" 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"
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.</span></div></div>
</div></div>
</blockquote></div><br></div></div></div></div> </div></div>
</blockquote></div><br></div>