Open kb1lqc opened 6 years ago
faraday-proxy
and similar commands were NOT installed even when no errors were observed with a pip install -e .
command. I had to run the command with sudo to get it to actually install.faraday-proxy --init-config
results in error:
faraday-proxy --init-config
failed because I was not in the project root directory. I remember this being an issue we've known about with editable installs. You cannot run the software outside root.
sudo faraday-proxy --start
with a properly configured Proxy to get /dev/ttyUSB0
to be connected toaprslib
to the requirements file for python pip.
Interesting, when starting faraday-aprs
connection was refuse to telemetry...
Solved the /stations
telemetry connection issue by killing the telemetry program with sudo kill -9 <pid>
and then starting it up in root with sudo faraday-telemetry --start
.
However I get another error now.
OK it looks like the SQlite database is locked... therefore no data is sent from telemetry and the aprs program will timeout:
Hmm this could be a big problem for Raspberry Pi. Googling suggests it could be a speed issue and we'd need to move to mysql or similar. I'm not sure, this seems ridiculous that it wouldn't work...
Just noticed that I needed to install with --force on latest Raspbian!
https://stackoverflow.com/questions/39280326/python-entry-point-console-scripts-not-found
Also noting that on the RPI using a fast SD card makes all the difference. Just started using a level 10 SD card and the RPI is snappy compared to my old level 4 card!
Summary
I'm installing faraday software on a Raspberry Pi 3 from github sources in editable mode i.e.
pip install -e .
. This issue ticket will collect some of my observations and nuances as we explore creating base stations with Faraday.Problem Explanation
PRetty much all stated in the summary.
Environment
Software
Hardware
-Faraday Rev D1
Supporting Information