Error /dev/ttyAMA0 read timeout. Closing TTY for later re-open.

[W5EVH]

While watching the aprx.log file, I noticed that I keep getting the following errors.

TTY /dev/ttyAMA0 opened
TTY /dev/ttyAMA0 read timeout. Closing TTY for later re-open.

I am using a Raspberry Pi 3b, TNC-pi (Not using I2C mode).

In aprx.conf, I am using:

<interface>
    serial-device /dev/ttyAMA0 19200 8n1 KISS
    tx-ok true
</interface>

Logs show about an hour apart.

Anyone else having this issue?

[Max Harper]

Are you actually receiving any packets through the TNC? If not then aprx may think the port is locked up and is closing and reopening the port to try again. Is this an up and running system or are you just testing? Your Interface statement looks correct to me, but I had to change mine after installing ax.25 which uses the port instead and aprx connects to that.

Just to be clear, no I2C address has been assigned, even though you are not using it, correct?

Max KG4PID

---

From: W5EVH <b...@w5evh.org>
To: Aprx software <aprx-s...@googlegroups.com>
Sent: Thursday, September 21, 2017 6:49 PM
Subject: [Aprx] Error /dev/ttyAMA0 read timeout. Closing TTY for later re-open.

--
You received this message because you are subscribed to the Google Groups "Aprx software" group.
To unsubscribe from this group and stop receiving emails from it, send an email to aprx-softwar...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[W5EVH]

Yes I am receiving packets.  The system works great until that message comes out.  I notice the system becomes quiet for a while, then it starts beaconing.  The errors are spaced exactly an hour apart.  I checked the cron hourly to see if anything was conflicting.  Commented it out and rebooted.  Same thing.  Its so strange because I have another aprx node that works flawlessly.  I actually copied the config from the other one with the same result.  I even tried different TNC-pi's.

I do have as.25 installed but I am not using it.  I thought about using it too.  Haven't tried it yet.

The TNC-pi is in its stock configuration where the i2c address is 0.

What gets me is that it errors exactly one hour.  Something must be doing something to it.

boB

[Max Harper]

I see in the manual where it says "Formerly the timeout was not initialized, since 2.09 it has default value of 60 minutes."

Perhaps a work around would be to manually set "timeout 0m" if that is valid or set it to a really high value so it doesn't do it as often. 

You didn't say what version of the OS and aprx your running so I hope no errors have been introducted into the code recently. Since you have a running system just take an image of it and install it on the problem system and make the nessessary changes to the config file. You could spend a lot of time and never find the real problem.

Wish I could be of more help.

Max KG4PID

---

From: W5EVH <b...@w5evh.org>
To: Aprx software <aprx-s...@googlegroups.com>

Sent: Friday, September 22, 2017 1:52 AM
Subject: Re: [Aprx] Error /dev/ttyAMA0 read timeout. Closing TTY for later re-open.