<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=iso-8859-15"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Andrew Errington wrote:
<blockquote
cite="mid:10380.125.248.153.122.1323046651.squirrel@webmail01.lancs.ac.uk"
type="cite">
<pre wrap="">On Mon, December 5, 2011 09:23, Larry wrote:
</pre>
<blockquote type="cite">
<pre wrap="">A Newbie here with a problem.
I'm still trying to grasp the ins and out of Astrisk and App-rpt etc.
I'm trying to connect a USB FOB to my RC-210. I do grasp the reverse
RC-210 wiring process. However I found no way to force pin 13 high to
activate PTT pin from the FOB for testing purposes.
Any suggestions on how or if I'm doing something wrong?
I have added a PTT LED for monitoring the output logic from pin 13 but
have never been able to get it to turn with any function I've tried other
than forcing a voltage at the junction feeding it and the base resistor of
the 2N4401. My RC-210 will work at that point but I'm not certain if I
have an issue with the USB FOB PTT output.
Am I am missing something or perhaps I don't understand the logic of the
different functions.
I'm not against reading but jumping all around to find different
materials has left the mind in a jumble. Can anyone enlighten me as to
when in the sequence PTT output becomes active and the voltage I should
find on that pin when it does?
</pre>
</blockquote>
<pre wrap=""><!---->
Hi,
I don't know about app_rpt, but I have played a bit with USB audio devices.
What is the model number of the USB audio chip on your audio fob? If you
can't read it, then please report what is the USB vendor ID and product ID
for the device (you can see this appear in /var/log/messages when you plug
the USB device in)?
How it's supposed to work is this:
The GPIO pin (let's say it's pin 13) will be low when the software doesn't
need to transmit. When the software wants to transmit, it will drive the
GPIO high (which will turn on the NPN transistor that drives PTT). The
software will wait for a short time to allow the radio to key up, then it
will drive an audio signal for the data to be transmitted on to the audio
output of the device (which is hooked up to the audio input of the radio).
When the audio data is finished the software will wait for another short
time then de-assert the GPIO which will turn off PTT.
If you are having trouble you could try the latest version of Thomas
Sailer's soundmodem. I added support for USB-controlled PTT. You could
compile the code and configure soundmodem for your USB device then use the
soundmodem test software to turn PTT on and off. I also wrote an
extremely poor piece of software that dumps HID control packets to the
device to drive the GPIO lines. Basically you write HID data to
/dev/hidrawX
73,
Andrew
ZL3AME
</pre>
</blockquote>
Andrew,<br>
<br>
Thanks for the great info.<br>
<br>
First ... I'll comment on the USB unit.... The chip within is covered
by a blob but it detects as a CM-109 and appears to function properly
as far as audio and COS ... only the PTT logic has failed to output
during my limited testing. <br>
<br>
My assumption about the actual sequence within the chip process was in
line with your great explanation. What I lacked is understanding if
there is a way to force the software into a transmit mode for testing
purposes. Doing so, as you explain should activate the PTT logic.<br>
<br>
Your info about Thomas Sailer's soundmodem
is something I am very interested in. I had another project in mind and
decided to venture into Asterisk and App-rpt in order to to utilize USB
sound modules. <br>
<br>
Your information may very well be a solution to another problem I would
like to tackle. I will definitely have a look.<br>
<br>
Thanks Much<br>
<br>
Larry - N7FM<br>
<br>
<br>
<br>
<br>
<br>
<br>
</body>
</html>