PixelController - a matrix control project by Michael Vogt , (c) 2010-2013. The main goal of this application is to create an easy to use matrix controller software which creates stunning visuals!
Primary Website: http://www.pixelinvaders.ch
My Blog: http://www.neophob.com
Facebook: https://www.facebook.com/PixelInvaders
Prerequisite:
- Java Runtime, v1.6+
Run PixelController.jar to start the application.
Make sure your led matrix connected to you computer before the application is started and you configured your output hardware in
the data/config.properties file.
You can download PixelController on Google Code: http://code.google.com/p/pixelcontroller/downloads/
Check out https://vimeo.com/61141493, http://vimeo.com/27453711 and http://vimeo.com/32580251 to see PixelController in action on two PixelInvaders panels.
PixelController supports different (LED) matrix hardware devices:
- PixelInvaders 3D Panels serial device (see Readme.PixelInvaders, http://www.pixelinvaders.ch)
- PixelInvaders 3D Panels network device (see Readme.PixelInvaders, http://www.pixelinvaders.ch)
- Seeedstudios Rainbowduino V2 (see Readme.rainbowduinoV2)
- Seeedstudios Rainbowduino V3 (Using this firmware: https://code.google.com/p/rainbowduino-v3-streaming-firmware)
- ArtNet Devices, multiple universe are supported,510 Channels (170 RGB Pixels) per universe
- MiniDmx Devices (like the SEDU board of http://www.led-studien.de)
- Element Labs Stealth LED panel. No longer in production (http://cled.barcousa.com/support/STEALTH/STEALTH_Users_Guide.pdf)
- Generic UDP Devices (for example Raspberry Pi, check out the PixelPi Software)
- TPM2 Serial devices (see http://ledstyles.de for more information)
- TPM2 Net devices (see http://ledstyles.de for more information)
- E1.31 devices (see http://www.opendmx.net/index.php/E1.31)
Check out the integration/ArduinoFW directory, all Arduino based firmware files are stored there.
There are different frontends for PixelController:
- Native Java: the default frontend is started when PixelController starts.
- PixConCli: Command Line Interface for PixelController, works also remote. The CLI tool is called
PixConCli.cmdon Windows andPixConCli.shon Linux/OSX. - PureData: PureData frontend (http://puredata.info/ download the extended Version), very flexible, extensible (OSC, MIDI). The PureData file is called
PixelController.pd.
##INTERFACES
- OSC interface, default listening port 9876. Processing examples included how to communicate with PixelController via OSC protocol
- FUDI interface, default listening port 3448, used to communicate with PureData
Valid commands:
CHANGE_GENERATOR_A # of parameters: 1 <INT> change first generator for current visual
CHANGE_GENERATOR_B # of parameters: 1 <INT> change first generator for current visual
CHANGE_EFFECT_A # of parameters: 1 <INT> change first effect for current visual
CHANGE_EFFECT_B # of parameters: 1 <INT> change second effect for current visual
CHANGE_MIXER # of parameters: 1 <INT> change mixer for current visual
CURRENT_VISUAL # of parameters: 1 <INT> select actual visual
CURRENT_COLORSET # of parameters: 1 <INT> select actual ColorSet
CHANGE_OUTPUT_VISUAL # of parameters: 1 <INT> change visual for current output
CHANGE_OUTPUT_FADER # of parameters: 1 <INT> change fader for current output
CHANGE_ALL_OUTPUT_VISUAL # of parameters: 1 <INT> change visual for all outputs
CHANGE_ALL_OUTPUT_FADER # of parameters: 1 <INT> change fader for all outputs
CURRENT_OUTPUT # of parameters: 1 <INT> select current output
BLINKEN # of parameters: 1 <STRING> file to load for the blinkenlights generator
IMAGE # of parameters: 1 <STRING> image to load for the simple image generator
TEXTDEF # of parameters: 1 <INT> select texture deformation option, 1-11
ZOOMOPT # of parameters: 1 <INT> select zoom options 1-4
COLOR_SCROLL_OPT # of parameters: 1 <INT> select color scroll fading direction, 1-14
TEXTWR # of parameters: 1 <STRING> update text for textwriter generator
TEXTWR_OPTION # of parameters: 1 <INT> set mode textwriter (pingpong scroller, left scroller)
CHANGE_BRIGHTNESS # of parameters: 1 <INT> output brightness 0 .. 100
OSC_GENERATOR1 # of parameters: 1 <BLOB> contains 4096 bytes (64x64x8bpp) or 12288 bytes (64x64x24bpp) of image data (depending on internal size)
OSC_GENERATOR2 # of parameters: 1 <BLOB> contains 4096 bytes (64x64x8bpp) or 12288 bytes (64x64x24bpp) of image data (depending on internal size)
CHANGE_THRESHOLD_VALUE # of parameters: 1 <INT> select current threshold for the threshold effect, 0-255
CHANGE_ROTOZOOM # of parameters: 1 <INT> select angle for the rotozoom effect, -127-127
STATUS # of parameters: 0 <NO PARAM> refresh whole gui
STATUS_MINI # of parameters: 0 <NO PARAM> just refresh parts of the gui
CHANGE_PRESENT # of parameters: 1 <INT> select current present id
CHANGE_SHUFFLER_SELECT # of parameters: 15 <INT>, parameter contains 15 nibbles to enable or disable the shuffler option (gets changed in the random mode), 0=OFF, 1=ON, example: 0 0 0 0 0 1 1 1 1 1 0 0 0 0 0
SAVE_PRESENT # of parameters: 0 <NO PARAM> save current present settings
LOAD_PRESENT # of parameters: 0 <NO PARAM> load current present settings
RANDOM # of parameters: 1 <ON|OFF> enable/disable random mode
RANDOM_PRESET_MODE # of parameters: 1 <ON|OFF> enable/disable random preset mode
RANDOMIZE # of parameters: 0 <NO PARAM> one shot randomizer
PRESET_RANDOM # of parameters: 0 <NO PARAM> one shot randomizer, use a pre-stored present
JMX_STAT # of parameters: 0 <NO PARAM> show JMX runtime statistic, default port: 1337 (use the -p switch)
SCREENSHOT # of parameters: 0 <NO PARAM> save screenhot
FREEZE # of parameters: 0 <NO PARAM> toggle pause mode
TOGGLE_INTERNAL_VISUAL # of parameters: 0 <NO PARAM> show/hide internal visual to save CPU
Try to understand WHAT does not work, which component? is it the frontend? PixelController itself? or no output?
Here are some common errors:
- Did you forgot to edit the configuration file
config.properties. Take a look at the config.examples subdirectory! - Did you flash the correct firmware to you Arduino/Teensy?
- PixelInvaders panels: Make sure that the Panel shows an animated rainbow pattern when the panels are powered on (make sure that you also power the Arduino/Teensy board). If you don't see a animated rainbow, make sure the directon of the modules is correct and that the Arduino/Teensy, LED modules and PSU share common ground. Verify the Arduino IDE don't spit out errors when you upload the firmware to the teensy
- PixelInvaders panels: A User reported that the PixelInvader firmware did not work on a new Arduino UNO r3 board. I think the reason for this is the big serial latency. However using a Arduino UNO r1 worked flawlessly. Technically this is not a big deal, as the timeout value cold be adjusted in the firmware.
- Make sure you're using an up-to date Java Runtime (JRE), this usually helps if the JVM crashes.
- If you use an extra long USB Cable (more than 5 meter) you might discover strange issues, try to use a short cable especially if you're uploading a firmware.
Prerequisite:
- Maven v2.x (if you use Maven 3, make sure to read http://neophob.com/2011/11/maven-3-is-evil/ first!)
- JDK 1.6+
Then run
# mvn initialize
to install the needed packages in your local repo and
# mvn clean package
to build PixelController, the distribution directory is "target/assembly/PixelController-VERISON/".
Hint: if you're using eclipse and you see an error like this
java.lang.NoClassDefFoundError: Could not initialize class gnu.io.RXTXVersionjava.lang.NoClassDefFoundError: Could not initialize class gnu.io.RXTXVersion
make sure you add the lib/serial directory as "Native library location"
It should be pretty simple to add support for new hardware. All Output code should go into the com.neophob.sematrix.output package (src/main/java/com/neophob/sematrix/output directory). All you need to do in the Output class is, take an array of int's (one int is used to store the 24 bpp) and send this buffer to your output device (via serial port, ethernet, bluetooth...). Maybe you need to reduce the color depth, flip each second scanline due hardware wiring, such helper methods should go into the OutputHelper.java class.
As a string point, add your hardware in the OutputDeviceEnum.java class and have a look where the other entries are referenced. Take a look at the existing Output classes, this should help you!
With the JMX interface you can monitor the status of your PixelController instance in real time. This will provide you with useful data such as required time for each layer (generator, effect, mixer…), the frame rate of your instance, allowing you to diagnose problems or performance issues. To read the JMX data, you will need to use a JMX client or the PixConCli util.
Example how to use PixConCli:
localhost:PixelController-1.3-SNAPSHOT michu$ ./PixConCli.sh -c JMX_STAT -p 1337
Create an RMI connector client and connect it to the RMI connector server 127.0.0.1:1337
Get an MBeanServerConnection...
Generic:
server version : 1.1
current fps : 20,036 (100% of configured fps: 20)
frame count : 1771
running since : 0:01:28.980
The following average times have been collected during the last 10.007 seconds:
generator : 0,310ms
effect : 0,000ms
output schedule : 0,140ms
fader : 0,000ms
debug window : 15,210ms
output prepare wait : 0,005ms
output update wait : 0,005ms
matrix emulator window: 0,440ms
Ouput-specific average times for output #1: NULL (NullDevice)
prepare : 1,550ms
update : 0,000ms
Close the connection to the server
- Michael Vogt: Project Lead, Main Developer
- Markus Lang: Maven enhancements, Output enhancements, Performance enhancements, Rainbowduino V3 support
- McGyver666: Contributor
- Rainer Ostendorf: Artnet Output
- Pesi: miniDMX Output, Tester
- Scott Wilson: Arduino/Rainbowduino Howto
- Noxx6: Bugfixes
- Psykon: Example Visuals
- okyeron: Stealth output device
- Dr. Stahl: Documentation, Tester