<div dir="auto">*CLI> radio key/unkey</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, May 2, 2019, 17:42 Kevin Custer <<a href="mailto:kuggie@kuggie.com">kuggie@kuggie.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<div class="m_-6450100975326485272moz-cite-prefix">James,<br>
<br>
I don't know of any way to tell the application about the presence
of audio without using the COS or CTCSS in simpleusb. In
usbradio, the application looks for the noise level to drop, and
additionally (optionally) the presence of a PL tone. Neither of
them are going to exist on a microphone input. I guess you could
use the VOX function, but that's kind of hokey IMHO.<br>
<br>
One thing you could try is swap the operation to the other
hardware input. Nothing says you need to use the COS hardware
input for COS. You can say "No" in the configuration file for COS
and use the CTCSS input (considering it's not blown up too) but
fed from the radio's COS logic. Maybe you're lucky and only the
COS input is bad. If not, you'll need to replace the FOB. <br>
<br>
Kevin<br>
<br>
<br>
<br>
<br>
<br>
On 5/2/2019 5:54 PM, James WD0JB wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Kevin,
<div><br>
</div>
<div>Thanks for the response. Caught you on the hamvoip list as
well.</div>
<div><br>
</div>
<div>So the primary question of this post still stands. Is
there a way to tell ASL to receive audio from my microphone
without the COS signal? </div>
<div><br>
</div>
<div>Maybe a change of direction. Can I pull discriminator
audio from the UV82 and use usbradio instead of simpleusb? If
I can't get it to work this way with the UV82, I do have some
GM300s I may be able to use with de-emphasized audio. I am
still in the very beginning stages of learning how all of this
gets put together, so if I use some incorrect terminology,
please forgive me. These lists have been very helpful!</div>
<div><br>
</div>
<div>Thanks,</div>
<div><br>
</div>
<div>James</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, May 2, 2019 at 4:45 PM
Kevin Custer <<a href="mailto:kuggie@kuggie.com" target="_blank" rel="noreferrer">kuggie@kuggie.com</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">James,<br>
<br>
From your description, and my extensive knowledge of the
CM119, CM119A <br>
and its variants, I believe the chip is bad. You can try to
add a 10k <br>
pull-up externally to 3.3V from pin 48, but I doubt it'll
work. <br>
Hopefully you are using protection diodes on these hardware
inputs, <br>
otherwise, that's what blew it up. Why? Here's why....<br>
<br>
There is much confusion surrounding the COS and CTCSS inputs
to the <br>
CM1XX chipsets. Here is a dissertation I wrote some time ago,
that <br>
hopefully explains the situation well:<br>
<br>
The COS and PL "hardware" logic inputs on CM1XX based radio
adapters <br>
were originally the volume-up and volume-down functions,
actuated by <br>
manual (push button tactile) switches in a standard audio
adapter <br>
(FOB). These inputs are internally pulled high, to 3.3 V, and
have to <br>
be pulled low enough to become valid. As such the push-button
switches <br>
made a good ground when depressed, as that's what the other
side of the <br>
switch was tied to - ground. Most AllStar radio adapters use
protection <br>
diodes (BAT-43's) that don't allow voltage to be sent into the
CM1XX <br>
chip. If voltage is allowed to be inputted to these pins, the
chip is <br>
destroyed. So - with the diodes in place, it doesn't matter
what voltage <br>
is present on the COS or CTCSS hardware inputs, because
voltage on these <br>
pins doesn't make anything happen, and because of the
protection diodes, <br>
doesn't hurt anything if voltage is present. Pull-up resistors
are <br>
totally unnecessary, because we need a ground to assert the
condition.<br>
<br>
Okay, so the CM108/119's logic inputs are looking for a ground
to be <br>
valid. This "active low" condition is required NO MATTER if
the setting <br>
in the conf file is upright or inverted. So - the setting in
the <br>
configuration file doesn't change the fact that the adapter
needs an <br>
active low to be valid and assert the condition. All this
software <br>
setting does is change if the low condition exists when the
radio is <br>
hearing a valid signal, or when it's not. Using a DMM, you
can read the <br>
voltage on the CM119 side of the BAT-43 diodes to see if the
logic level <br>
is properly changing from 3.3V (2.4 in some instances) to 0.0
(or a few <br>
tenths of a volt).<br>
<br>
Not all radio logic signals are created equal. Some logic
circuits can <br>
source current, but lack the ability to sink. Sometimes active
high <br>
circuits (circuits that provide a voltage when the state
becomes active) <br>
don't have the ability to pull to ground very well. These
circuits may <br>
not have the capability to pull the COS and CTCSS inputs low
enough on <br>
the radio adapter to become valid/active. A pull-down
resistor can <br>
help, but nothing beats a real active low circuit. A 2N2222
(or similar <br>
NPN transistor) with the emitter grounded usually works well.<br>
<br>
Hope this helps...<br>
<br>
Kevin<br>
<br>
<br>
<br>
On 5/2/2019 4:07 PM, James WD0JB wrote:<br>
> All,<br>
><br>
> Is there a way to manually key from the Asterisk
command-line, or <br>
> other, to transmit when using a USB fob without the COS
activated? I <br>
> have a fob that I cannot key with pin48 on CM119, but I
still want to <br>
> use the fob, possibly as a radio-less node with a headset
/ <br>
> microphone. I cannot key with pin48 on the CM119 because
there is not <br>
> the proper voltage on that pin to pull down.<br>
><br>
> If anyone has any suggestions, I am using the SYBA UAUD
compact fob. <br>
> This Amazon link: <a href="https://www.amazon.com/dp/B001MSS6CS" rel="noreferrer noreferrer" target="_blank">https://www.amazon.com/dp/B001MSS6CS</a><br>
><br>
> Also, these fobs (I've tried 2 so far) have an eeprom
chip on them <br>
> (FT93C46A). Any others I've seen used in this manner
from forum posts <br>
> do not appear to have this chip, however, removing the
chip does not <br>
> resolve the issue. One fob has 200mv the other has about
1volt. <br>
> Nothing else connected to the pin.<br>
><br>
> Thanks in advance for any help.<br>
><br>
> James<br>
<br>
</blockquote>
</div>
<br clear="all">
<div><br>
</div>
-- <br>
<div dir="ltr" class="m_-6450100975326485272gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">73,</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">James WD0JB</div>
</div>
</div>
</div>
</blockquote>
<br>
</div>
_______________________________________________<br>
App_rpt-users mailing list<br>
<a href="mailto:App_rpt-users@lists.allstarlink.org" target="_blank" rel="noreferrer">App_rpt-users@lists.allstarlink.org</a><br>
<a href="http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users" rel="noreferrer noreferrer" target="_blank">http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users</a><br>
<br>
To unsubscribe from this list please visit <a href="http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users" rel="noreferrer noreferrer" target="_blank">http://lists.allstarlink.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>