Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Raspberry Pi 3 Pip Install Editable Mode Observations #270

Open
kb1lqc opened this issue Sep 10, 2017 · 10 comments
Open

Raspberry Pi 3 Pip Install Editable Mode Observations #270

kb1lqc opened this issue Sep 10, 2017 · 10 comments

Comments

@kb1lqc
Copy link
Member

kb1lqc commented Sep 10, 2017

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

  • Faraday-Software, starting with kb1lqc@83ae953 but also using Master at times.
  • Raspbian OS

Hardware

-Faraday Rev D1

  • Raspberry PI Model 3

Supporting Information

This is a handy spot to post any screenshots or file outputs in order to better support this issue. We want to keep the top of the ticket clutter-free as possible.

@kb1lqc
Copy link
Member Author

kb1lqc commented Sep 10, 2017

  • 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:
    • image

@kb1lqc
Copy link
Member Author

kb1lqc commented Sep 10, 2017

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.

  • image

@kb1lqc
Copy link
Member Author

kb1lqc commented Sep 10, 2017

  • Needed to run sudo faraday-proxy --start with a properly configured Proxy to get /dev/ttyUSB0 to be connected to

@kb1lqc
Copy link
Member Author

kb1lqc commented Sep 10, 2017

@kb1lqc
Copy link
Member Author

kb1lqc commented Sep 10, 2017

Interesting, when starting faraday-aprs connection was refuse to telemetry...

image

@kb1lqc
Copy link
Member Author

kb1lqc commented Sep 10, 2017

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.

image

@kb1lqc
Copy link
Member Author

kb1lqc commented Sep 10, 2017

OK it looks like the SQlite database is locked... therefore no data is sent from telemetry and the aprs program will timeout:
image

@kb1lqc
Copy link
Member Author

kb1lqc commented Sep 10, 2017

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...

@kb1lqc
Copy link
Member Author

kb1lqc commented Oct 6, 2017

Just noticed that I needed to install with --force on latest Raspbian!

https://stackoverflow.com/questions/39280326/python-entry-point-console-scripts-not-found

@kb1lqc
Copy link
Member Author

kb1lqc commented Oct 6, 2017

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant