[arm-allstar] Asterisk very slow

[Kevin Custer]

Alan,

The Yaesu FT-8900 outputs a COS logic signal on its Mini-DIN-6 radio 
connector on pin 6.  This pin changes states when a signal of sufficient 
quieting exists on the channel, or when you rotate the squelch control 
counter clockwise sufficiently to open the squelch.  This pin will need 
to be connected to the radio interface (the URI in this case) on the 
hardware COS pin (pin 8 on the DB25). Maybe your cable hasn't properly 
made this connection, or maybe you have the logic inverted and the node 
times-out because of inactivity, instead of the other way around.

----

The EEPROM is required with the CM119B to set and hold certain settings 
that are not reachable otherwise by the software.  While the original 
intention of holding radio tune values in the EEPROM doesn't work, for 
this chip the EEPROM is still required.  The manufacturer has to set 
some values prior to shipping the product, and any attempt to store 
anything to the EEPROM results in a non-working radio adapter.  All 
later model URIxB's ship with a EEPROM that's programmed correctly, and 
you should avoid writing anything to it from the client software, 
otherwise you'll need to send it back to regain operation.

Kevin


On 3/14/2021 2:16 PM, "Alan Bartkowiak via ARM-allstar" wrote:
> Hi Steve and thank you for the reply.
> It looks like we are heading in the right direction. When looking at option
> V in simpleusb I see the following:
>
> COS (composite) Ignore,  COS (input) keyed, COS (test) clear, CTCSS (input)
> ignore, CTCSS (overide) clear, PTT clear.
>
> I have menu option J set for 1. My radio configuration is a Yaesu ft-8900
> with no COS or PL and relying on carrier squelch.
> Changing menu option J and trying the other options renders no DTMF
> decoding in asterisk but does change COS (input ) to clear
> and I'll hear my courtesy tone when the option is changed.
> One thing I will mention is that there is a eeprom in the URIxB but not
> using it and selected no eeprom on first setup. Don't know
> if this will have any effect or not.
>
> N2ZVN
>
> On Sun, Mar 14, 2021 at 1:26 PM "Steve Agee via ARM-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
>> *This is a classic case of an inverted COS signal. You can confirm this
>> by first running menu option 12, then sub-menu option "V" to view what
>> is happening with your signalling. My money says you will see COS active
>> when your node radio's receiver is not receiving a signal. Try keying up
>> with your HT and see if the status changes to CLEAR. If so, press
>> <ENTER> to go back up one menu level. Then run menu item "J" and select
>> the opposite signal and save your changes. Then repeat the V test and
>> see if things work normally for you. If so, don't forget to run menu
>> option "W" to write your changes to the /etc/simpleusb.conf file to
>> store them permanently.
>>
>> N5ZUA *
>>
>> On 3/14/2021 10:47 AM, "Alan Bartkowiak via ARM-allstar" wrote:
>>> I have a new build using hamvoip on a Pi4b with a URIxB.  Also I need to
>>> mention that I am very new to
>>> Allstarlink.
>>> The problem I'm having is:
>>> When asterisk cli is started, I enter a *2 <node#>. The DTMF tones are
>>> decoded as they should and get the ulaw message
>>> that it is being acted on. Looking at the Allstarlink portal shows that I
>>> am connected however there is no audio through my
>>> simplex radio. I do see "hang-up" whenever anyone unkeys from the node
>> that
>>> I am connected to. After about 5 minutes
>>> give or take, I will get the announcement node 53735 connected to node
>>> xxxxx and the audio will now come through. After that
>>> I will get the announcement "53735 timeout" and DTMF tones are no longer
>>> acted upon although they are decoded properly.
>>> I am still shown as being connected to the node and am still getting
>> audio.
>>> The only way to disconnect is to restart Asterisk.
>>> If I enter a *3 <node #> to be in transceiver mode, There is a dead
>> carrier
>>> on the connected node and the only way out of it is to restart asterisk.
>>> Didn't want to tie up the node for 5 minutes to see what happens when
>>> asterisk decides to act.
>>>
>>> Thank you in advance for any assistance to resolve this.
>>> Alan Bartkowiak N2ZVN