Ken, I found the problem in the usbradio.conf file. Somehow I set the CTCSS as: ctcssfrom=usbinvert usbinvert is not an option. According to the usbradio.conf file in the asterisk-original folder the options are: no, usb or dsp. ctcssfrom="no" or "usb" works (although usb is not presently supported). I have reset the usbradio.conf to what originally worked: carrierfrom =usbinvert all CTCSS settings are default except as above No CTCSS in the Alinco or HT Alinco not in Data mode. The URI cable instructions were correct (data mode off & usbinvert) except that it said the encode and decode had to be set in the Alinco. It doesn't. I cannot thank you enough for your help and going the extra mile for the PPS . I kept thinking it was the CTCSS because I could RX from AllStar but couldn't TX to it. I didn't fully understand the usbradio.conf but you pointed to it below:
You have CTCSS turned on (usbradio.conf) and no PL on your HT – or the wrong tone
I kept me looking for something until I found it. Have a wonderful day!' George On Apr 28, 2012, at 6:31 PM, Ken wrote:
Hmmm
I assume you are using the DB9 in the back of the Alinco for the connection to the URI (like I am on one of my machines).
When you do that, you need to switch the radio to packet mode.
When it is in packet mode, the Alinco’s speaker is muted.
If you can hear the signal in the Alinco, it is not in packet mode and it is not using the signals in the DB9.
Ken
PS – can I assume you are running half-duplex then? In that case, the only time the LED will turn red is when a signal comes from the internet side, or you do *81 trick or something else that causes the system to talk back.
PPS – if you *did* switch it to packet mode, the other things that can prevent receive audio from activating the asterisk system are:
- Input calibration (“radio tune rxnoise”, “radio tune rxsquelch” etc) - You have CTCSS turned on (usbradio.conf) and no PL on your HT – or the wrong tone - You have hardware COS configured (carrierfrom=usb) and the polarity wrong (usbinvert) - The cable is bad - The URI input is burned out
From: George Zolla [mailto:gazolla@san.rr.com] Sent: Saturday, April 28, 2012 9:04 PM To: Ken Subject: Re: [App_rpt-users] Unable to TX
Actually. when AllStar TX it goes through the radio perfectly and out through the antenna.. It is when I TX to AllStar I have the problem. It doesn't receive the voice or the key transmission. When I TX from an HT with *81, I hear it in my Alinco but it doesn't go through the URI to the computer (AllStar). I can hear the voice or keys at the Alinco but it doesn't seem to make it to the AllStar server. The URI is flashing breen but never goes red. It seems the Alinco can't TX through the 9 pin all the way to the computer or out through the antenna when the URI is connected tot he computer and theh Alinco.
On Apr 28, 2012, at 5:00 PM, Ken wrote:
Ok - let's make sure I understand what is going on.
When the Allstar wants to transmit, it keys up the transmitter, but when you listen (with another radio), all you hear is the carrier and no audio?
The when you did:
radio tune txvoice
it did the same? (transmitter keys up but no modulation?)
(The green light on the URI should be blinking and the red light should turn on for a few seconds.)
What number was showing for the transmit gain?
For example:
current txvoice setting on Channel A is 500
Ken
-----Original Message-----
From: George Zolla [mailto:gazolla@san.rr.com]
Sent: Saturday, April 28, 2012 7:14 PM
To: Ken
Subject: Re: [App_rpt-users] Unable to TX
Tried both - no joy - any other ideas?