* 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
* started bug fixes for APA strips with more physical leds than configured
* 1st cut of changes to APA102.
now looks at config for "leds" which is the # of hardware leds in the strip.
This enables us to write the correct trailer length in the packet.
Also fixed a bug where switchoff was writing the wrong # of leds
* removed commented out old code
removed debug printf
* included prebuild test binary for Pi2
* Second attempt at the fix.
BEFORE:
If you have more physcial LEDs than defined in the "leds" "index" section of the config there is random junk added to the end of the strip.
WITH THIS FIX:
In the "device" section specify the number of physical leds with:
"leds" : 212,
If this is greater than the number of led indexes, additional LEDs are set to black
If this is smaller than the number of led indexes, it is ignored
* included test binary
* Clean exit if the device config is missing or a non-supported device type is specified
Former-commit-id: 8ae96188fa74d91b13a921e7d5faf6d6ac1c42ee
This fix the previous limit of 64 APA102 leds, because of too short end frame. Now the end frame is computed accordling to this documentation: https://cpldcpu.wordpress.com/2014/11/30/understanding-the-apa102-superled/. Tested on my 98 leds, it works fine.
I suggest to modify hyperion to allow LED drivers to apply the brightness parameter because APA102 has a parameter for that, without the need to elaborate RGB color to simulate it (result is wrong colors!). Is it possible to introduce such parameter in LED drivers and let the driver apply that?
Former-commit-id: 2d714e6eb075ec57e0973839fe96d2d7a051c57f
