[App_rpt-users] Fwd: COR signal getting confused
Doug Crompton
doug at crompton.com
Fri Sep 26 16:49:37 UTC 2014
From: doug at crompton.com
To: kf7mbk at w7ara.net
Subject: RE: [App_rpt-users] Fwd: COR signal getting confused
Date: Fri, 26 Sep 2014 12:46:14 -0400
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.
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.
Also I assume you are not using any rxdelay?
73 Doug
WA3DSP
http://www.crompton.com/hamradio
From: kf7mbk at w7ara.net
Date: Fri, 26 Sep 2014 08:50:51 -0700
To: app_rpt-users at ohnosec.org
Subject: [App_rpt-users] Fwd: COR signal getting confused
Resending since my initial post has been pending moderation for 2 days now and got no reply from the list owner email.
I have modified an HT to bring out the receive LED signal and use it
as the COR input to a DMK URI. It is a digital signal as viewed on a
scope (i.e. very short slope in the transitions) This seems like it
would work well and it does on strong signals. But on marginal signals
where the LED may blink on and off quickly (like during picket
fencing), it seems to confuse the URI (or the software) were it will
start off good, but then a quick dropout of the COR signal will cause
the software to no longer detect carrier, even though the signal on
the COR input has been restored. Even if the input is solid high (or
low in my case, I'm using usbinvert) it will not detect a carrier
until there is another dropout of adequate time to "reset" it.
I've tried putting a simple RC on the input but it didn't really help
much. Seems the URI (or software) needs a significant minimum time
between transitions to properly detect them, long enough that it would
delay the carrier detection too much without a circuit more complex
than an RC (i.e. something that would allow instant keyup, but delay
the key down.)
Linked is a scope image.
https://lh5.googleusercontent.com/-CsJ9autUTAE/VCWK-uNJJpI/AAAAAAAAPSM/VsVvbPVvuEA/s800/20140923_184107.jpg
Carrier was detected until this signal
dropout event. Ch A is my RC filtered signal sent to the URI, Ch B is
the signal out of the radio. Carrier was not detected after the 5th
dropout even though the signal remained low.
Anyone ever experience this and/or have ideas on how to fix it?
Thanks.
Mike
KF7MBK
_______________________________________________
App_rpt-users mailing list
App_rpt-users at ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20140926/9b43e0fb/attachment.html>
More information about the App_rpt-users
mailing list