Note;
this guide is only for the basic OS that you can install on your Raspberry, its not nessecary for Hyperbian OS because that has already build-in Hyperion.NG
Note;
this guide is only for the basic OS that you can install on your Raspberry, its not nessecary for Hyperbian OS because that has already build-in Hyperion.NG
installing Hyperion.NG on Raspbian / Debian Buster and others
because i had to find out myself i wrote it down for others to use as a guideline
1. Download a image for RaspberryPI > Raspbian / Debian buster, whichever one you want online.
2. Write this image to a clean SD card, do not format!
3. slide it into your PI and boot it up onto the installation wizard
4. make correct settings and enable VNC / SPI / SSH and other things, you can (also) do this in sudo raspi-config
5. Write down the IP address of the PI, then reboot
6. On your PI, go to https://github.com/hyperion-project/hyperion.ng/releases and pick out a version that has this >> Hyperion-x.x.x-alpha.x-Linux-armv7hf-rpi.deb it can be a new or older version .deb package
7. Download this and put it in your PI directory, eg home / pi / test folder
8. Open your terminal on your PI via SSH-putty or via VNC program (VNC explanation will follow later)
9. enter;
sudo apt-get update
sudo apt-get upgrade
sudo apt-get install git cmake build-essential qtbase5-dev libqt5serialport5-dev libqt5sql5-sqlite libqt5svg5-dev libqt5x11extras5-dev libusb-1.0-0-dev python3-dev libcec-dev libxcb-dev libqt5sql5-sqlite libqt5svg5-dev libqt5x11extras5-dev libusb-1.0-0-dev python3-dev libcec-dev libxcb-dev libqt5sql5-dev lcb-imagecb-util-lib0-dev shm0-dev libxcb-render0-dev libxcb-randr0-dev libxrandr-dev libxrender-dev libavahi-core-dev libavahi-compat-libdnssd-dev libjpeg-dev libturbojpeg0-dev libssl-dev zlib1g-dev
sudo apt-get install libraspberrypi-dev
run all this libraries and wait, you may not need them all but too much is ok
10. install the deb.file >> sudo dpkg -i /path/to/Hyperion-x.x.x-alpha.x-Linux-armv7hf-rpi.deb
if your file is for example on home / pi / testmap then the code is: sudo dpkg -i /home/pi/testmap/Hyperion-x.x.x-alpha.x-Linux-armv7hf-rpi.deb
if you have it installed it should work.
11. Reboot system and Hyperion.NG should start automatically.
12. go to your localip: 8090 and make your changes!
note; VNC server (on e.g. Raspbian buster full) is for remote desktop function, if you want to use it then you have to install VNC viewer on your pc and create an account> when you have done this and run the installation wizard you can edit your pi if it were brought to you as a second screen.
so you can see your desktop of your Pi (if it has one) and do all the installation very easily. )
True, but in this case the most important pice of equipment seems to be broke. Now it is just Ambi without light
:ninja:
why did i have spi mode 4 and you had spi mode 0 ?
I have no clue maybe for max attempts or line of tested output
do you know what spi mode is
SPI mode is the kind of signal you just tested on the GPIO's, 0 is spi device0 > thats the first device output for SPI devices
you have also SPI 0.1 but that's almost never in use because default is 0
sounds very nice
thank you so much for troubleshooting with me
I will get back here sometime next week, when the new LED stripe arrived
no problem man,
I have the same setup almost but i am running Rasbian Buster full with Hyperion.NG 2.1 as .deb package
did all the updates and upgrades
APA102 and WS2801 works out of the box on RPI3b, no resistors or Arduino or levelshifters needed.
I see it like this always; the less equipment you need the less can go broke or offline
see you then
Now I am pretty shure the LED stripe is broke.
All pins are connected right and die SPI output is working
And also the software is up to date
just bc I´m interrested: what do you do for a living? you know so lot about all this stuff xD
i am a technician overall in electronics and secure systems, but also work alot with software and hardware sollutions.
The Raspberry for me was a new platform when i was introduced by Hyperion, but i already knew some Linux OS
and played with that before.
So i burried myself in it the same what i always do to get to bottom of things.
just alot interest a electronical background and perseverance
they are working now, so now with Hyperion?
SPI GPIO MOSI to MISO is putting out and reading data.
so must work now with Hyperion we hope, or ledstrip is broke
something else is going on then, do the updates first its look like GPIO's isn't putting out anything also when hyperion isn't using GPIO output
did you connect the pins together? GPIO 9 and 10
do you mean with the other raspberry? I didn´t do it for the Hyperbian one, I thought that all this stuff should be preinstalled
do it anyway i would say, it can't do harm mate
I will try it. So MOSI and MISO should be pin 19 and 21 on raspberry Pi3 right?
yes they are, 19 and 21
btw;
did you run a few commands before installation in the terminal like
sudo apt-get update
sudo apt-get upgrade
sudo apt-get install git cmake build-essential qtbase5-dev libqt5serialport5-dev libqt5sql5-sqlite libqt5svg5-dev libqt5x11extras5-dev libusb-1.0-0-dev python3-dev libcec-dev libxcb-image0-dev libxcb-util0-dev libxcb-shm0-dev libxcb-render0-dev libxcb-randr0-dev libxrandr-dev libxrender-dev libavahi-core-dev libavahi-compat-libdnssd-dev libjpeg-dev libturbojpeg0-dev libssl-dev zlib1g-dev
sudo apt-get install libraspberrypi-dev
Troubleshooting
Loopback test
This can be used to test SPI send and receive. Put a wire between MOSI and MISO. It does not test CE0 and CE1.
wget https://raw.githubusercontent.…ntation/spi/spidev_test.c
gcc -o spidev_test spidev_test.c
./spidev_test -D /dev/spidev0.0
spi mode: 0
bits per word: 8
max speed: 500000 Hz (500 KHz)
FF FF FF FF FF FF
40 00 00 00 00 95
FF FF FF FF FF FF
FF FF FF FF FF FF
FF FF FF FF FF FF
DE AD BE EF BA AD
F0 0D
example of output after command, source https://www.raspberrypi.org/do…raspberrypi/spi/README.md
smothing is off
I think Hyperbian should work as its only job is to run Hyperion
I just installed Raspbian on another Raspberry and used python with code from a tuturial to try it out and it also didn´t work
yes i think that too.
only thing you can do is measure GPIO output dataflow, i look up the schematics for you
Alles anzeigenHi Thommy,
Mijn setup is als volgt:
Ik heb een Raspberry Pi met OSCM geinstalleerd. Deze zit achter mijn monitor geplakt en is aan een ledstrip verbonden. Via wifi heb ik hier met behulp van HyperCon op Windows een configuratie gezet. Op mijn PC draait zowel Windows als Ubuntu. Op Windows gebruik ik HyperionScreenCap om mijn scherm te grabben, welke vervolgens wordt doorgestuurd naar de JSON server van mijn Raspberry Pi (192.168.1.6:19444).
Nu wil ik hetzelfde ook op Ubuntu werkend krijgen. Hiervoor heb ik Hyperion 2.0.0 (https://github.com/hyperion-pr…eleases/tag/2.0.0-alpha.9) geinstalleerd. Als ik deze app opstart, open ik de web-interface (http://localhost:8090/). Hier heb ik echter geen idee wat ik kan doen om mijn scherm te grabben en deze door te sturen naar mijn Raspberry Pi...
dat doet Hyperion ook niet, die ontvangt alleen images over netwerkprotocol via poort FLATBUFFER 19400 of PROTO 19445 en zet die om in een aansturing naar de leds.
Voor zover ik kan zien en weet grabt" Hyperion.NG en Hypercon alleen de images/beelden van een interne dispmanx en een externe USB grabber of ontvangt deze via het netwerk vanaf bovenvermelde poorten en protocol.
er zou dan een Hyperion additioneel programma moeten zijn voor Raspbian die je screen "grabt" vanuit je Ubuntu en deze dan verstuurt naar de 19445 server van je hyperion die op je PI draait.
Hyperion kan wel de aansturing van leds via netwerkprotocol verzenden naar bridges en hubs, naar bijv Wled maar een beeld/image versturen kan Hyperion.NG gewoon niet.
Where is this setting? What is tab remote?
Is there a program you can recommend?
Ik, that was the reason why i choose it. I will get a new on from the seller next week.
the setting is on [remote] tab at localip:8090, you can switch modules on or off here.
Smoothing was causing problems before so maybe this helps to disable and test again.
its also possible your GPIO doesn't want to fire because there is something with authorisations on Hyperion which steers the GPIO outputs.
however i don't use Hyperbian so i don't know exactly if it sets the config by itself in every build.
I'm not sure what is restarting. The light switches to a color preset for about 3-5 seconds, then I see the startup rainbow colors for about 3 Sec and then it's working again.
Edit: how do I Find out what restarts?
you can see that on your PI's led lights the green and red, if they switch off or not and start flickering
Anyone here who can analyze my logfile?
what is rebooting,
-the PI software completely
-or only Hyperion systemd?