* Handle Exceptions in main & Pythoninit
* Have SSDPDiscover generic again
* Have SSDPDiscover generic again
* Change Info- to Debug logs as technical service messages
* Nanoleaf - When switched on, ensure UDP mode
* Include SQL Database in Cross-Compile instructions
* Fix Clazy (QT code checker) and clang Warnings
* Stop LedDevice:write for disabled device
* Nanoleaf: Fix uint printfs
* NanoLeaf: Fix indents to tabs
* NanoLeaf - Add debug verbosity switches
* Device switchability support, FileDevice with timestamp support
* Nanoleaf Light Panels now support External Control V2
* Enhance LedDeviceFile by Timestamp + fix readyness
* Stop color stream, if LedDevice disabled
* Nanoleaf - remove switchability
* Fix MultiColorAdjustment, if led-range is greater lednum
* Fix logging
* LedFileDevice/LedDevice - add testing support
* New "Led Test" effect
* LedDeviceFile - Add chrono include + Allow Led rewrites for testing
* Stabilize Effects for LedDevices where latchtime = 0
* Update LedDeviceFile, allow latchtime = 0
* Distangle LinearColorSmoothing and LEDDevice, Fix Effect configuration updates
* Updates LedDeviceFile - Initialize via Open
* Updates LedDeviceNanoleaf - Initialize via Open, Remove throwing exceptions
* Updates ProviderUDP - Remove throwing exceptions
* Framebuffer - Use precise timer
* TestSpi - Align to LedDevice updates
* Pretty Print CrossCompileHowTo as markdown-file
* Ensure that output is only written when LedDevice is ready
* Align APA102 Device to new device staging
* Logger - Remove clang warnings on extra semicolon
* Devices SPI - Align to Device stages and methods
* Fix cppcheck and clang findings
* Add Code-Template for new Devices
* Align devices to stages and methods, clean-up some code
* Allow to reopen LedDevice without restart
* Revert change "Remove Connect (PriorityMuxer::visiblePriorityChanged -> Hyperion::update) due to double writes"
* Remove visiblePriorityChanged from LedDevice to decouple LedDevice from hyperion logic
* Expose LedDevice getLedCount and align signedness
* Started implementing artnet/DMX support
It compiles, but certainly wont work just yet
* Fix up packet data and length
correct default udp port
The data looks ok in wireshark
* Code cleanup
Sequence runs from 1..255 not 0
fix universe > 255
* code cleanups and force even number of channels
* Fix potential endianness issue
* added support for 'x' channels per fixture with zero padding
its very basic support for now - it needs better multi universe support
* std::string -> qstring part 1
* more string migration
* more string migration ...
* ...
* more qstring mogrations
add sysinfo via json
* remove unneccessary includes
* integrate sysinfo into webui
* Adding support for sk6822 timing
This isnt complete, but should be a good starting point for others to learn from.
1) Here is where the led device source is located:
cd libsrc/leddevice
2) Find the files that need changing:
root@loungepi:libsrc/leddevice# grep -ri 2812spi *
CMakeLists.txt: ${CURRENT_SOURCE_DIR}/LedDeviceWs2812SPI.h
CMakeLists.txt: ${CURRENT_SOURCE_DIR}/LedDeviceWs2812SPI.cpp
LedDeviceFactory.cpp: #include "LedDeviceWs2812SPI.h"
LedDeviceFactory.cpp: REGISTER(Ws2812SPI);
LedDeviceSchemas.qrc: <file alias="schema-ws2812spi">schemas/schema-ws2812spi.json</file>
LedDeviceWs2812SPI.cpp:#include "LedDeviceWs2812SPI.h"
LedDeviceWs2812SPI.cpp:LedDeviceWs2812SPI::LedDeviceWs2812SPI(const QJsonObject &deviceConfig)
LedDeviceWs2812SPI.cpp:LedDevice* LedDeviceWs2812SPI::construct(const QJsonObject &deviceConfig)
LedDeviceWs2812SPI.cpp: return new LedDeviceWs2812SPI(deviceConfig);
LedDeviceWs2812SPI.cpp:bool LedDeviceWs2812SPI::init(const QJsonObject &deviceConfig)
LedDeviceWs2812SPI.cpp:int LedDeviceWs2812SPI::write(const std::vector<ColorRgb> &ledValues)
LedDeviceWs2812SPI.h:class LedDeviceWs2812SPI : public ProviderSpi
LedDeviceWs2812SPI.h: LedDeviceWs2812SPI(const QJsonObject &deviceConfig);
3) Copy the existing files as a starting point:
cp LedDeviceWs2812SPI.cpp LedDeviceSk6822SPI.cpp
cp LedDeviceWs2812SPI.h LedDeviceSk6822SPI.h
cp schemas/schema-ws2812spi.json schemas/schema-sk6822spi.json
4) Do some search and replacing:
:%s/Ws2812SPI/Sk6822SPI/g
5) edit the other files (see the diffs in this commit)
* Added wait time and reset time
* Fixed up debugging output and commented it out.
* switch rs232 provider to completly async transfer
* start of implementing a seperate init function for leddevices
* rename setconfig to init
* more fixes
* implement missing code
* fix code style
* remove debug code
* remove debug stuff
* set loglevel to original state
* Started work on DMX512 rs232 device
cloned from sedu - no actual changes yet
* Implemented DMX protocol
Added baudrate debugging to ProviderRs232
* Added support for multiple DMX fixture types
* initial tpm2net rewrite - doesnt compile yet
* new tpm2.net drive compiles.
rename old tmp2net typos to tpm2net
fixed compiler warning in ws2812b
* added packetsize calculations and the end of frame character.
Output looks good on tcpdump
* removed old tpm2net driver
renamed tpm2netnew to tpm2net
* commit debug code to save it due to merge
* migrate first devices to new device registry and configure on runtime
* fadecandy and rs232 resets device if config is set
* try to hunt crash on osx
* test commit if this works with osx
* refactor spi devices
* cleanup
* refactor leddevices file, tinkerforge and ws2812b
* refactor raw usb devices
* refactor udp devices
* - add tpm2net driver
- remove old udp driver from build (files left in place for reference for new udp driver)
- json serverinfo shows available leddevices
* finish rework part 2 of leddevices
* add schemas for leddevices.
currently only compiled in, but not usedx
* Add support for > 170 leds. These are send as multiple packets
Change default latchtime to be smaller
* code cleanup
* more code tidying
added *.swp to gitignore
* Started on support for sACN/E1.31/DMX512
Just a clone of udpraw for now
* It's ALIVE!!
This adds somewhat working DMX512/sACN/E1.31 support.
I've tested it against an ESPixelStick but have no other "real" hardware
TODO:
configure universe#
configure universe and led offset
configure source names (all hard coded now...)
* oops.... forgot that dmx element 0 isnt rgb data but needs to be zero
* added universe support in the config
assorted code cleanups
* start ledclone
* led cloning: clone scan areas from original led
main: show exceptions, better exit
* tune json schema for new option. somwe cleanup
* fix warnings and bug for framebuffer selection. thx to clang brought by new osx buikld on travis
* make ledclone feature work flawlessly for effects too. Effect sees the ledstring without cloned leds.
cloned leds will be inserted just before sending to leddevice
additional: remove warnings and fix code style
* fix warning
* - implement framegrabber type option
- framegrabber autoselect
- integrate x11 grabber in hyperiond
* add doxy
* v4l: select device by name
hyperiond: fix x11 grabber connection to kodichecker
config: tune default prios of boblight and v4l
* make v4l name finding case insensitive
* multi fix commit
- refactoring leddevicefactory
- adalight: default for "delayAfterConnect" is 1s now - needed for most arduino's because of there special behaviour on open
- fadecandy: new option for disabling configuration send - if you want to keep your fadecandy defaults
- Hyperion.cpp: simplify createSmoothing discussed in #105
- smoothing:
-- add option for continuous output
-- when updatedelay>0 and continousOutput is disabled, buffer is flushed correctly after no input is detected
* add doxygen to travis
* fix code
* fix compile fir ws281x pwm
* remove git merge stuff
* fix compile
* multi fix commit
- refactoring leddevicefactory
- adalight: default for "delayAfterConnect" is 1s now - needed for most arduino's because of there special behaviour on open
- fadecandy: new option for disabling configuration send - if you want to keep your fadecandy defaults
- Hyperion.cpp: simplify createSmoothing discussed in #105
- smoothing:
-- add option for continuous output
-- when updatedelay>0 and continousOutput is disabled, buffer is flushed correctly after no input is detected
* add doxygen to travis
* common ledbuffer for color transform
hyperion class uses a common buffer for all operations on ledColors got from muxer
all color transforms uses new ledBuffer instead of making copies of ledbuffer
other fixes:
fix compile bug in profiler
update doxygen config
* migrate logging for color transform classes
* prepare new logger in hyperion class
* implement hwledcount
* Update Hyperion.cpp
Fix off color
* remove ledscount equivalent from apa102
migrate logging in hyperion.cpp
remove unused and duuplicate colorcorrection - but same is available through tempertature
* remove colorcorrection completly
fix compile
* set colororder back to static
* in remote: using correction is the same as using temperature - correction is obsolete, command not delete atm for compat reasons
* switch to new logger for folowing led devices:
LedDeviceAtmo
LedDeviceFactory
LedDeviceFadeCandy
LedDeviceHyperionUsbasp
LedDeviceLightpack-hidapi
LedDevicePiBlaster
LedDeviceWS281x
LedRs232Device
leddevice base class defines logger already as protected member _log
* migrate to new logger for led devices.
still todo:
LedDeviceWS2812b
LedDeviceWs2812SPI
LedDeviceTinkerforge
LedDeviceLightpack
LedDeviceMultiLightpack
* migrate serialport to qt5 serialport
* remove old serialport
add logging to serialport
* remove try catch - qt serialport uses plain return values
* tiny fix, but not working atm
* make it work, tested with adalight
* cleanup: remove ambiled device
as written at the forum this is no longer supported. All people should move to adalight. They just need to flash a new sketch.
* fix typo
* 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
* adding support for SK6812 - not working yet
* Changed rpi_ws281x submodule to be penfold42's fork
* Set White to zero for now
* starting on the code to make the White led do stuff
* Added some basic whie led calculation
white = min(r,g,b)
r-=w, g-=w, b-=w
* cleaned up a couple of compiler warnings
* updated strip type to use corrected RGBW strip type
(the SK6812RGBW datasheet is wrong)
* moved bitpair_to_byte initialiser to (hopefully) work with older GCC
* compiler warning in udp driver
removed some tabs in ws2812b.cpp
* formatting - spaces to tabs
* moved rpi_281x to tag sk6812-v1.0
* attempt #3 at migrating the rpi_281x submodule to my fork/branch
* moving to my fork of rpi_281x
* Started implementing multiple RGB to RGBW conversion options
a quick hack has been implemented inside WS281x.cpp but ive started
moving this to RgbToRgbw.cpp for reuse by other led device types
* migrated RGB to RGBW conversion to RgbToRgbw.cpp
Former-commit-id: ff8e9038c4bb8203b71b42d12bf23be4abcc0b3b
* 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
* cleaned up a couple of compiler warnings
* moved bitpair_to_byte initialiser to (hopefully) work with older GCC
* compiler warning in udp driver
removed some tabs in ws2812b.cpp
* formatting - spaces to tabs
* moved rpi_281x to tag sk6812-v1.0
* moving to my fork of rpi_281x
* half way thru re merging the newudp support
* Whoops.... dont know how it compiled before..
* Removed debugging that was commented out
Former-commit-id: ac4330422f93f3d594dfcba5593759288298d25e
* 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
* 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
* 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
* Experimental changes to piblaster code to work how i think it should
It is now assumed that the PWM pins in groups of 3 correspond to RGB channels of the led.
"assignment" : "rgbrgbrgb",
Would result in:
//Channel number GPIO number Led channel
// 0 4 0 red
// 1 17 0 green
// 2 18 0 blue
// 4 27 1 red
// 5 21 1 green
// 6 22 1 blue
// 7 23 2 red
// 8 24 2 green
// 9 25 2 blue
* Ammend pwm channel mapping comments to match the code
* 1st cut of the new more flexible piblaster pin mapping support
it works but is still rough
* removed old "assignment" handling
- prints an error messaage if found and terminates
fixed the switchoff method
* removing iPins hard coded list of valid GPIO pins
* removed iPins array for switchOff function
* code cleanups
input validation
* Handle catching (and ignoring) SIGPIPE.
You can now kill and restart pi-blaster daemon and hyperiond will gracefully recover
* added a binary for testing
* Added sample config and my modified pi-blaster version to support more GPIOs
* moved hyperiond
* removed testing binaries
move sample configuration to the configs directory
* re enabled device config display
* removed sample configuration
Former-commit-id: 95e4d4ea2fb7cb5439e8cd597883a638da61a574
* Updated smoothing options for AtmoOrb, can now choose between Orb external or Hyperion's internal smoothing.
With skipSmoothingDif you can set the maximum allowed color difference before overriding / clearing Orb smoothing during faster color change like for instance color <-> black.
* Updated inline documentation.
* Fixed command type typo in AtmoOrb device.
* Corrected variable spelling in AtmoOrb device.
* Make smoothing also match equal values for AtmoOrb smoothing differential
Former-commit-id: 3eede43c2f76fa324f0144aeac0526b8125ad149
No functional changes, but
- files have been renamed
- the device name is now "file" not "test"
Former-commit-id: 3fbc03c3fe1d764654c1d28ebb80562ce6276ab1
2. Adds support for level shifters that invert the data
Config option - "invert" (integer)
if omitted, do not invert
if == 0, do not invert
if !=0, invert
Former-commit-id: fd5b2863a85b11ac3a8444d1e02822f852feb556
The RPi 2 and 3 have two PWM channels and 3 PWM pins available to the
gpio header. BCM18 and BCM12 run on PWM channel 0. BCM13 runs on PWM
channel 1. This change allows BCM13 to be used by allowing the PWM
channel to be specified.
Former-commit-id: 3693ab438c2b369e6307c262d32bba509409e5b9
LordGrey
Portisch
Paulchen-Panther
redPanther
penfold42
brindosch
Rick van Hattem
Rick164
Mark Walker