Re: [Hamlib-developer] Controlling FT-857D with Raspberry Pi 2

[Nate B. <n0...@n0...>]

* On 2016 16 Feb 18:52 -0600, Kevin Owens wrote:
> I didn't get any results from "ls -l /dev/ttyUSB*". However, I did notice
> that I had a /dev/AMA0 listed, which I recognized from my google
> searches.

That is odd.  Are you running Raspbian or another distribution?

Are you using a USB to serial adapter (dongle)?

What do you see with 'ls -l tty*' (the list will be long, you can page
back with Shift-PageUp, forward with Shift-PageDown to your prompt)?

> After running the rigctl command with the new device port, I got further:
> 
>  $ sudo rigctl -vvvv -m 122 -r /dev/ttyAMA0
> rigctl, Hamlib 3.0
> Report bugs to <ham...@li...>

> Rig command: f
> ft857: cache invalid
> read_block(): Timed out 0.200263 seconds after 0 chars
> get_freq: error = Communication timed out
> 
> Rig command:
> 
> It brought me to the Rig command: prompt, but I received a communication
> timed out error as a result.  Also, I verified that the user is a member of
> the dialout group.

That port is the internal serial port that acts as an alternate console
device by default on Raspbian.  It is present on the GPIO pins so it's
not likely to be the port your radio is connected to (side note, I have
a Pi using that port with a TNC Pi running as an APRS iGate with APRX).

> Sidenote:  I am new to the mailing list thing.  How do I get these replies
> to show up on the mailing list website archive?

That part is automatic and should appear on the SourceForge site fairly
quickly.  I'm not sure how fast the GMANE site updates.

73, Nate

-- 

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Ham radio, Linux, bikes, and more: http://www.n0nb.us