doityourselfchristmas.com - User contributions [en]

Vixen Plugin Development

2008-07-12T13:44:52Z

Agember:

Although [[Vixen]] provides a standard set of [[Vixen_Plugins|plugins]] for a variety of hardware, individuals with different or custom hardware will need to develop their own plugin. Plugin development requires Microsoft Visual Studio, or another development environment for coding and compilation using Microsoft's .NET framework.

==Example Source Code==
[http://www.vixenlights.com/downloads.html Source code] for the Parallel 12 plugin is available to assist plugin developers. The plugin is written in C# and works with Vixen 1.*.

Modifications are required for the plugin to work with Vixen 2.0:
* Change the <code>Parallel12</code> class to implement the <code>IEventDrivenOutputPlugIn</code>, <code>IOutputPlugIn</code>, <code>IPlugIn</code> interfaces instead of the <code>PlugIn</code> interface.
* Change the first parameter of the the <code>Initialize</code> to <code>IExecutable executable</code>. The <code>List<Channels> Channels</code> property of <code>IExecutable</code> can be used in place of the <code>Channel[] channels</code> parameter.
* In the <code>get</code> method for the <code>HardwareMap</code> property, change the call to <code>new HardwareMap</code> to pass the string constant <code>"Parallel"</code> as its first parameter. The enumeration <code>PortType</code> no longer exists.

==Resources==
*[http://www.vixenlights.com/downloads.html Programmer's Guide] (Only for Vixen 1.*)
*[http://www.vixenlights.com/downloads.html Example Source Code] (Only for Vixen 1.*)

Vixen Plugin Development

2008-07-12T13:29:44Z

Agember:

Vixen Plugin Development

2008-07-12T13:28:34Z

Agember: New page: Although Vixen provides a standard set of Vixen_Plugins plugins for a variety of hardware, individuals with different or custom hardware will need to develop their own plugin. Plu...

Although [[Vixen]] provides a standard set of [[Vixen_Plugins plugins]] for a variety of hardware, individuals with different or custom hardware will need to develop their own plugin. Plugin development requires Microsoft Visual Studio, or another development environment for coding and compilation using Microsoft's .NET framework.

==Resources==
*[http://www.vixenlights.com/files/Vixen%20Programmer%27s%20Guide.zip Programmer's Guide] (Only for Vixen 1.*)
*[http://www.vixenlights.com/files/Parallel12.zip Example Source Code] (Only for Vixen 1.*)

Vixen Plugins

2008-07-12T13:16:56Z

Agember:

A plugin in [[Vixen]] is a file that extends Vixen. They are used to communicated with external [[Electronics_Hardware | hardware]] (controllers), add another User Interface (editor) to Vixen, or handle triggers that fire events in Vixen.

==Hardware Interface==
Plugins that support communication with DIY [[Electronics Hardware]]. Refer to [http://www.vixenlights.com/downloads.html Vixenlights.com] for more details.

===Lights On/Off Only (No Dimming)===
* 8_Line595 - Uses all of the 8 data lines of the parallel port. Note: All controllers on the port must have the same channel count for them to work correctly.
* BasicParallel - 8-channel controller connected to the 8 data lines of a parallel port.
* Hill320 - 320 channel controller by Hill Robertson.
* Icicle - For use with Icicle controllers. This plug-in implements the serial type A, version 2 protocol.
* MCC PCI DIO -
* Olsen595 - Scalable parallel port controller using the 74HC595 latch register. Can use multiple parallel ports. Supports the Grinch controller as well.
* Parallel12 - 12-channel controller connected to the 8 data lines + 4 control lines of a parallel port.
* PSC -
* Simple595 - A simpler plugin for the 595 controller that can only use one parallel port at a time and takes less effort to setup.
* K8055 - NEW! For use with the Velleman K8055 USB interface board.
* N DIO 96 - For use with the National Instruments PCI-DIO-96 card. Requires prior installation of the NI DAQmx driver. Also requires NationalInstruments.DAQmx.dll and NationalInstruments.Common.dll in the Plugins directory.

===Lights - Dimming Capable===
* FGDimmer - Serial PIC based controller designed by FireGod
* Renard - A scalable PIC-based dimming controller that uses a single serial port.
* DMX-512 - For use with the Enttec Open DMX USB module. Also requires the IDMX (in the Plugins directory) and FTD2XX (in the Vixen directory) assemblies.
* DMXUSBPro - For use with the Enttec PRO DMX USB module.
* IDMX - Required for DMX-512 and DMXUSBPro plugins.
* FanslerDimmer - Another 595 controller that is capable of dimming.
* Horning Dimmer - A 595 controller that is capable of dimming.

===Non-Lights applications===
* LedTricksOutput
* AdjustablePreview - A plugin that lets you view the output of your sequences on your screen without needing external hardware connected. It allows you to adjust the pixel resolution and size. It also allows any size picture to be used.
* PGBLED - For use with RGBLED controllers. It only implements a very limited subset of the RGBLED controller currently.
* Launcher - Allows external programs to be launched by triggers contained in a sequence.
* Prop1 - NEW! Get started on a Halloween display using the EFX-TEK Prop-1 controller. Allows for 3 servo and 4 digital outputs. You will need updated firmware from EFX-TEK to allow the Prop-1 to be used with Vixen.
* Prop2 - NEW! Expand your growing Halloween display using the EFX-TEK Prop-2 controller. Allows for 8 servo and 8 digital outputs. You will need updated firmware from EFX-TEK to allow the Prop-2 to be used with Vixen.

==User Interface==
* LedTriksUI - LedTricks Sequence builder.
* Frames - Used to manage frames within the LedTricks sequence builder.
* FrameGenerator
* StardardScript
* StandardSequence
* TriggerResponce

==Trigger Interface==

==See Also==
*[[Vixen Plugin Development]]