This website requires JavaScript.
Explore
Help
Sign In
frodovdr
/
hyperion.ng
Watch
1
Star
0
Fork
0
You've already forked hyperion.ng
mirror of
https://github.com/hyperion-project/hyperion.ng.git
synced
2023-10-10 13:36:59 +02:00
Code
Issues
Releases
Wiki
Activity
a960894d14
hyperion.ng
/
hyperiond.test-binary.REMOVED.git-id
1 line
40 B
Plaintext
Raw
Normal View
History
Unescape
Escape
Another option for Ws2812 - direct spi from the pi with 1 wire (#631) * Removed -HUP so the default -TERM signal is sent instead. - hyperiond only listens for TERM and INT. HUP is often used to get an exe to reread its config Changed pgrep to add '-x' so it wont partial match on the exe name. - I have multiple instances with multiple hyperiond-instance1 names - this ensures the service script only kills the right process * reversing errant change to hyperion.systemd.sh * This add a new device type - ws2812spi. I've (ab)used the SPI interface to send the correct timing pulses to keep the ws2812 happy. THE RATE IS IMPORTANT! A FIXED CORE_CLK IS IMPORTANT! Attach the SPI MOSI pin on the Pi to the DIN pin on your ws2812 "device" : { "name" : "MyPi", "type" : "ws2812spi", "colorOrder" : "grb", "output" : "/dev/spidev0.0", "rate" : 3800000 }, * updated hyperiond.test-binary * Updated default SPI speed to the "correct" value. My Pi was undervolted so was dropping the core clock confusing everything * Code cleanups explicitly set the final 3 bytes to 0 * Removed latchtime option - not applicable * updated test binary Former-commit-id: d3c19c8374999f7a554bb25ca181a8a483f86289
2016-05-15 18:39:17 +02:00
23f1b917ec588d71521aa698edf446a2e8c0ea5d
Reference in New Issue
Copy Permalink