[arm-allstar] How to get FTM-300D working with AllStar voip

[Kevin Custer]

Bill,

I'm glad you got it all working to your satisfaction.  Thank you for the 
follow-up and letting us know!

HamVoIP makes the AllStar part simple with its menu system that's easily 
navigated.

Kevin


On 2/13/2024 5:04 PM, Bill Dornbush wrote:
> Kevin,
> I built a DRA-50 kit and connected it to my FTM-300D using a CT-164, 
> and Raspberry Pi 3, and carefully reviewed the FTM-300D 
> configuration.  After all of that, I have a working node with good audio.
>
> The node 55553 provides excellent feedback on setting my audio.  I 
> connected to it, and used it like a Parrot node, and it played back my 
> audio and also told me if my audio was too low, too high, or just right.
>
> --Bill AA6BD
>
> On Sun, Feb 4, 2024 at 10:49 PM Kevin Custer <kevin at kc-wireless.com> 
> wrote:
>
>     Bill,
>
>     I believe the FTM-300 is going to require the following special
>     attention to work correctly:
>
>     First - watch this video by NA9LE - YouTube; DRA-50 & FTM-300 -
>     https://www.youtube.com/watch?v=8lJDpADFxA4
>     While the video references a DRA-50 - a properly wired DRA-30 will
>     work.  I'll assume you have it all wired up properly.  This video
>     is for a different application, (digital data) but concentrate on
>     how the radio is set-up, so you can duplicate its operation. 
>     Otherwise - COS may not be present.
>
>     Then - continue with what follows below:
>
>     1 - Put the FTM in B+A mode on screen; sub band A visible on
>     screen; data band set to "B-Fixed".
>     2 - Set the DATA speed in radio to 9600.
>     3 - Use the data band for ASL.
>
>     If you're using a Yaesu CT-164 data port adapter cable - use pin 4
>     of the Mini-DIN-6 for receive audio, and pin 6 for COS.
>
>     An amplified radio interface may be necessary to achieve proper
>     transmit deviation for voice.  The DRA-30 will work - but the TX
>     audio may be low.  A DRA-50, CT-164, and male to male Mini-DIN-6
>     are the right combination for this radio making a nearly
>     plug-n-play set-up.
>
>     Kevin W3KKC
>
>
>     On 2/3/2024 9:36 AM, Bill Dornbush wrote:
>>     Kevin,
>>     I tried both cosfrom=usbinvert and cosfrom=usb with the same
>>     result which is no response.  I will try to capture the squelch
>>     signal to be sure it is really there.
>>
>>     Bill AA6BD
>>
>>     On Fri, Feb 2, 2024 at 7:09 PM Kevin Custer
>>     <kevin at kc-wireless.com> wrote:
>>
>>         Bill,
>>
>>         Try using cosfrom=usbinvert
>>
>>         Kevin W3KKC
>>
>>
>>
>>         On 2/2/2024 4:18 PM, Bill Dornbush via ARM-allstar wrote:
>>         > I have a Pi3 with a DRA-30 that I am trying to get to work
>>         with an FTM-300D
>>         > radio.  I have installed the jumpers on the DRA-30 for COS
>>         and CTCSS. I
>>         > wired the FTM-300D squelch control to the COS pin 2 of the
>>         DRA-30.  I set
>>         > the FTM-300D so that the squelch terminal becomes active
>>         when either the TX
>>         > or RX band squelch is open and I set the band programmed to
>>         the frequency
>>         > for the hotspot operation.  I have a FT1-XDR HT programmed
>>         to the same
>>         > frequency.  I can send a DTMF sequence using Supermon and
>>         the node
>>         > responds.  In the simpleusb-tune-menu, I have COSFROM set
>>         to usb and
>>         > CTCSSFROM to no.  I ran Asterisk CLI client, and I see that
>>         simpleusb_read
>>         > reports that it got DTMF characters when I key the HT.  But
>>         the node does
>>         > not act on the DTMF sequence.  What am I missing?
>>         >
>>         > AA6BD
>>         > _______________________________________________
>>         >
>>         > ARM-allstar mailing list
>>         > ARM-allstar at hamvoip.org
>>         > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>         >
>>         > Visit the BBB and RPi2/3/4 web page - http://hamvoip.org
>>
>