bool realTASBot ist set to true (it is by default)If you experience an error, that a shared library can't be loaded, try to execute ldconfig to update your library chache (and maybe reboot).
The program looks within its current working directory, for a folder called gifs and subdirectories within it.
| Path | Explanation |
|---|---|
./gifs/others |
Here go all the general animations. The program is choosing randomly animations from here |
./gifs/blinks |
Here are all blinking animations, the program can choose from |
./gifs/base.gif |
The animation, TASBots eye returns to between the animations and blinks |
./gifs/startup.gif |
The animation, that gets played exactly once, when the program starts |
It can be defined, how many times at most TASBot blinks between every random animation, but at least always once (if pattern is not making skipping them, e.g. 0-x-y). It can also be defined, how long are the periods are between the blinks.
Example: 3-4-6
3: Maximum amount of blinks between blinks4: At least 4 seconds between each blink...6: ...but at most 6 seconds.The actual amount of seconds the program sleeps between the blinks is randomly generated in milliseconds. In this example, TASBot could wait 4581 ms, just as 5987 ms. He could blink at least once, but at most 3 times, before the next random animation
See the build-in -h option or arguments.c:28 to get an overview of all available arguments. There are some for changing the playback speed, setting the data pin, playing a specific animation and many more!
Color palettes are the random colors TASBot can choose from when playing a monochrome animation and colorful mode is activated. To create a color palette, you can either:
E78587 (no '#' in front). One color per line. BECAUSE creates .tbp files, but those are just text files. File extension not required.To inject any animation :warning: that is already stored on TASBot :warning: send a UDP datagram to 8080. An abstract payload could look like T;./path/to/animation.gif.
T is the playback type, how the animation gets played. It can either be:
Q for queueing the animation by adding it on top of the current animation stack. It will be the next animation to be played after the blinks.I for immediate playback. Stops the current animation and plays this. :warning: Not implemented yet!animation.gif is a locally, already on TASBot stored animation! Full or relative paths are supported, as long as the file exists on TASBot!To make injecting animations easier, you can use the Animation Injectoar (aNinja) from the TASBot-Eyes-Toolkit if you want to.
The centered "nose" LEDs can be controlled in real time with the -U argument. It's based on the WLED UDP realtime control protocol, see here. Right now, only the DRGB mode is supported, also known as mode 2.
It covers an area of 48 LEDs in total in a 8x6 matrix.
ColorChord 2 by CNLohr supports WLED instances. In order to be able to use the realtime control with ColorChord, make sure to add something like this section to your ColorChord config file:
leds = 48
lightx = 8
lighty = 6
wled_realtime = 1
port = 19446 # Default port for UDP realtime
address = x.x.x.x # TASBot IP
wled_timeout = 2 There's also an example ColorChord config file (colorchord.conf) in the misc folder of this repository.
-c argument). However, the color that is used to overwrite isn't adjusting to the brightness of the given color within the frame. Right now it's flat overwriting the same color to all pixels, that just aren't black. Use the method getLuminance() for that.