[chirp_users] Direct connect from Pi to Yaesu FT-4 succeeds

Dan Clemmensen danclemmensen at gmail.com
Tue Apr 9 17:53:15 PDT 2019


Chuck, The huge problem with the NanpPi Duo,  and all of the teensy boards
from FriendlyELEC or anyone except Raspberry, is the lack of a large
support base. With the Raspberry PI, you get the entire massive user base
that will give you help if you need it, in many different forums. If you
have lots of free time and really enjoy problem solving on Linux systems,
the NanoPi is OK. In my case, my desire for absolutely minimizing the SWaP
(Size, Weight, and Power) justifies the extra effort. If it were just
CHIRP, then no, but I'm also running Direwolf, and I therefore need audio
input. Audio input on a Raspberry Pi needs a USB audio dongle. The dongle
and its cabling are larger and heavier than the entire NanoPi. The NanoPi
itself is about half the size of a Raspberry Pi Zero. The Zero only has a
singe CPU, which may be a bit weak for Direwolf, While the NanoPi has 4
CPUs. In my application (support for a CERT field team) I will also be
running a web server, Openstreetmap, and some specialized applications.
CHIRP is important if the team gets deployed on loan to a different city
with a different set of repeaters.

On Tue, Apr 9, 2019 at 3:14 PM Chuck Hast <kp4djt at gmail.com> wrote:

> Those are beautiful pieces of art... Gotta get me one.... Still love my
> Pi's though...
>
>
> On Tue, Apr 9, 2019 at 1:37 PM Dan Clemmensen <danclemmensen at gmail.com>
> wrote:
>
>> Here is the requested diagram for the FT-4. Note that the Baofang uses a
>> different cable.
>>
>> WARNING: Please do not blindly adapt this for other radios. This entire
>> scheme can probably be adapted for any radio that uses a 3.3V setial
>> connection, but if you plug in an older radio that uses higher voltages,
>> you can fry you little computer, and/or your radio.
>>
>> NOTE: if you use a serial port that is configured as a login port (a
>> "console") you OS can spew lots of stuff to the port. This can in theory
>> confuse your radio. This is true of any serial port the CHIRP uses in any
>> OS, but it may be more important to think about this when using itty-bitty
>> computers, since they tend to configure at least one serial port as a
>> "console" port.
>>
>> This scheme "should" work on any itty-bitty computer that can support
>> CHIRP and that has a 3.3V serial port. On a Raspberry Pi, your OS will be
>> richer. You will not need the X-over-SSH trick, and if you do use it you
>> will need less setup.  On a Raspberry Pi, you use pins (6,8,10) as
>> (GND,TxD,RxD), and your OS will see the port as /dev/ttyS0).
>>
>> My NanoPi Duo is running the sun8xi linux distro provided by FrendlyELEC,
>> who manufactures the NanoPi. the distro is  based on Ununtu, so you use
>> apt-get to install packages as needed. To support CHIRP, I installed xorg,
>> since the supplied image uses something strange. To actually use CHIRP, I
>> use ssh -Y from my Linux desktop computer to allow CHIRP to present its X
>> window to my desktop computer's screen via the magic of X-over-SSH.
>>
>> I'm connecting the radio to NanoPi's second serial port, which is on pins
>> labelled RX1 (pin 20) and TX1 (pin 22)  and of course GND (pin 6) on the
>> NanoPi headers. This port is known to the OS as /dev/ttyS1.
>> Here is he requested diagram:
>>
>> NanoPi                                                             FT-4
>> MIC plug
>> pin 6  (GND)----------------------------------------------------------
>> sleeve
>> pin 20 (RX1)----------------+-----------------------------------------tip
>>                             |
>> pin 22 (TX1)---2K resistor--+
>>
>>
>> On Tue, Apr 9, 2019 at 10:33 AM <dropkick23 at gmail.com> wrote:
>>
>>> Dan,
>>>
>>> I'm a little brain dead when it comes to hardware. Would you post a
>>> simple diagram of how you wired FT4 to NanoPi? Witch OS are you running on
>>> the NanoPi?
>>>
>>> Thanks
>>> Fred
>>> _______________________________________________
>>> chirp_users mailing list
>>> chirp_users at intrepid.danplanet.com
>>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>>> This message was sent to Dan Clemmensen at danclemmensen at gmail.com
>>> To unsubscribe, send an email to
>>> chirp_users-unsubscribe at intrepid.danplanet.com
>>
>> _______________________________________________
>> chirp_users mailing list
>> chirp_users at intrepid.danplanet.com
>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>> This message was sent to Chuck Hast at kp4djt at gmail.com
>> To unsubscribe, send an email to
>> chirp_users-unsubscribe at intrepid.danplanet.com
>
>
>
> --
> Chirp + Editcp + MD380Tools on Linux
> Celestial!!!
> Chuck -- KP4DJT
> _______________________________________________
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> This message was sent to Dan Clemmensen at danclemmensen at gmail.com
> To unsubscribe, send an email to
> chirp_users-unsubscribe at intrepid.danplanet.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20190409/5fbf81c2/attachment-0002.html 


More information about the chirp_users mailing list