Actually, now I'm wondering about the serial port needing SUDO to have access.
UART is on Pins GPIO 14 and 15, and UART had to be enabled in the RPi.conf program.
Maybe this serial port is used by other background processes and that causes the timeout / conflict error. I would have thought that a half second timeout should trap these types of errors in a recoverable way, but we don't really know what we are doing. And have no responses to errors coded. Naive coders.
Actually I think maybe we need to close the serial port between uses.
So, new question:
Option 1:
* Open Serial
* Get one line.
* Close serial
* Parse that line looking for GGA
* Loop until found
Option2:
* Open Serial
* Get one line.
* Parse that line looking for GGA
* Loop until found
* Close serial
Option 1 has a lot more closing the port.
Option 2 holds the port for potentially a long time.
UART is on Pins GPIO 14 and 15, and UART had to be enabled in the RPi.conf program.
Maybe this serial port is used by other background processes and that causes the timeout / conflict error. I would have thought that a half second timeout should trap these types of errors in a recoverable way, but we don't really know what we are doing. And have no responses to errors coded. Naive coders.
Actually I think maybe we need to close the serial port between uses.
So, new question:
Option 1:
* Open Serial
* Get one line.
* Close serial
* Parse that line looking for GGA
* Loop until found
Option2:
* Open Serial
* Get one line.
* Parse that line looking for GGA
* Loop until found
* Close serial
Option 1 has a lot more closing the port.
Option 2 holds the port for potentially a long time.
Statistics: Posted by gabby SLAMprobe — Sun Jun 01, 2025 5:50 am