search

gilestrolab / ethoscope

a platform from monitoring animal behaviour in real time from a raspberry pi
http://lab.gilest.ro/ethoscope/
GNU General Public License v3.0
17 stars 25 forks source link

Ethoscope display issues with Raspberry PI 4 #172

Closed DaveMelkani closed 2 years ago

DaveMelkani commented 2 years ago

Hey Ethoscope Team,

I purchased all the materials for an Ethoscope, but was only able to procure a Raspberry Pi 4. I used the provided beta image and was unable to find my Ethoscope on the Node website. I get a GPIO error when I tried displaying the ethoscope PI on a monitor using the provided beta image. How should I proceed further?

image
pepelisu commented 2 years ago

Hi, The first time that you start the image it makes a series of tasks and sometimes a restart is required. One way to do a soft restart is to ssh into the ethoscope. To do that:

  1. Check the IP assigned to the RPI in your router, the one that is providing the Ethoscope_wifi signal.
  2. Open a terminal in the node and just write: ssh alarm@ip_from_the_step_1 for example ssh alarm@192.168.0.32
  3. Once you are logged in via ssh, you can then do sudo restart and the RPI should restart.
  4. If something of the above fails, you can try a hard reset, just disconnect the RPI from the mains.
ggilestro commented 2 years ago

See the section called Ethoscope does not show up online on the manual.

DaveMelkani commented 2 years ago

Hey Ethoscope Team,

I will try this, but I also had another question. When I tried creating a new ethoscope SD image provided. Building the partitions went well, but in the “SSH session inside the PI” steps, I got stuck on “yaourt -S ethoscope-device.” When I tried running this command, I got an error with picamera package() where it says “ERROR: A failure occurred in package(). Aborting…” I was wondering what I can do about that?

ggilestro commented 2 years ago

Sorry, I am confused now. Did you use the SD image found here? Or did you build the image from scratch? If you build the image from scratch you need to change the PKGBUILD to fix the compatibility issue between picamera and pi4, as explained in that comment.

if picamera is not properly installed the ethoscope will not be working and the node will not be able to find it on the network.

DaveMelkani commented 2 years ago

Okay, I did this where I changed the PKGBUILD to match the one found in #170 and on the last part it says “Install ethoscope-device as normal from AUR but revert all changes in /boot/config.txt before boot. The file should only contain the following line enable_uart=1" which I did. When I then tried running yaourt -S ethoscope-device, I got this new error. What should my next steps be in proceeding?

image
ggilestro commented 2 years ago

Hi Dave - please just use the image that you find linked at the end of that comment. No need to recreate an image from scratch.