Drivers and software - Revision history

Nomis52 at 01:09, 12 July 2009

2009-07-12T01:09:18Z

Beier: corrected links

2009-06-30T09:24:22Z

corrected links

Beier: spelling, rephrasing

2009-05-30T18:08:16Z

spelling, rephrasing

Beier: corrected spelling

2008-11-13T18:51:56Z

corrected spelling

Beier: Category talk:Articles moved to Drivers and software: no-one sees the talk pages, better move the content out.

2008-11-13T14:31:23Z

Category talk:Articles moved to Drivers and software: no-one sees the talk pages, better move the content out.

Beier at 14:29, 13 November 2008

2008-11-13T14:29:29Z

65.57.245.11 at 02:01, 10 January 2007

2007-01-10T02:01:39Z

Beier at 20:42, 9 January 2007

2007-01-09T20:42:14Z

Beier at 20:34, 9 January 2007

2007-01-09T20:34:05Z

Beier at 20:33, 9 January 2007

2007-01-09T20:33:30Z

New page

There is a number of ways to get a controller application to send DMX data to a hardware interface (that can send the data out on your DMX wire).

Sometime the driver is split up i two:
* Hardware driver for sending raw data to and from the hardware
* Protocol driver for translating the codes from the controller app to codes the hardware can understand (both ways)

On linux there exists a system for hardware drivers, which is a kernel driver with a common interface to the controller sofware that is independent of which hardware you choose to use. This is called DMX4Linux.

For various reasons there is as many separate driveres as there is in DMX4Linux.

Most USB interfaces works as a "virual com port", which means that there is a real com port in the hardware, and a driver makes a com interface available i the operating system. Most USB com ports are supported 'out of the box' on both Windows and Linux (nice!), so most USB-to-DMX interfaces just need a protocol driver (easy to make and use)

On Windows it seems that (almost) all controller apps have their own drivers.

If your are looking for a interface to buy, then start with finding your favorite controller app, and find out which drivers and thereby which hardware is supported.

← Older revision		Revision as of 01:09, 12 July 2009
Line 1:		Line 1:
−	~~==Drivers and software==~~
−	~~''This is some old general notes, that was kind of hidden in the wiki''~~
−
−
−
	'''Advice:''' If your are looking for a interface to buy, then start with finding your favorite [[:Category:Controllers \|controller app]], and find out which drivers and thereby which hardware is supported.		'''Advice:''' If your are looking for a interface to buy, then start with finding your favorite [[:Category:Controllers \|controller app]], and find out which drivers and thereby which hardware is supported.

@@ Line 1: / Line 1: @@
 ==Drivers and software==
 ''This is some old general notes, that was kind of hidden in the wiki''
 There is a number of ways to get a controller application to send [[DMX]] data to a hardware interface (that can send the data out on your [[DMX]] wire).
@@ Line 15: / Line 20: @@
 On Linux there exists a system for hardware drivers, which is a kernel module with a common interface to the controller software that is independent of which hardware you choose to use. This is called [[DMX 4 Linux]].
-Many drivers don't need to be in the kernel, and for that, there is a driver framework called [LLA]].
+Many drivers don't need to be in the kernel, and for that, there is a driver framework called [[LLA]].
 Remember that it is possible to send DMX data over a network to an other computer or an Ethernet-to-DMX hardware interface. [[LLA]] is particularly good at this and in routing the signals between different systems and hardware.
 [[Category:Articles]]

@@ Line 6: / Line 6: @@
 Sometime the driver is split up into:
 * Hardware driver for sending raw data to and from the hardware.
-* Protocol driver for translating the codes from the controller app to codes the hardware can understand (both ways).
+* Protocol driver for translating data/instructions between the controller app and the hardware (which uses some kind of protocol).
@@ Line 21: / Line 21: @@
-'''Advise:''' If your are looking for a interface to buy, then start with finding your favorite controller app, and find out which drivers and thereby which hardware is supported.
+'''Advice:''' If your are looking for a interface to buy, then start with finding your favorite controller app, and find out which drivers and thereby which hardware is supported.
 [[Category:Articles]]

@@ Line 14: / Line 14: @@
 On Windows it seems that (almost) all controller apps have their own drivers. Probably because no good framework existed.
-On Linux there exists a system for hardware drivers, which is a kernel module with a common interface to the controller software that is independent of which hardware you choose to use. This is called [[DMX4Linux]].
+On Linux there exists a system for hardware drivers, which is a kernel module with a common interface to the controller software that is independent of which hardware you choose to use. This is called [[DMX 4 Linux]].
 Many drivers don't need to be in the kernel, and for that, there is a driver framework called [LLA]].
@@ Line 21: / Line 21: @@
-'''Adwise:''' If your are looking for a interface to buy, then start with finding your favorite controller app, and find out which drivers and thereby which hardware is supported.
+'''Advise:''' If your are looking for a interface to buy, then start with finding your favorite controller app, and find out which drivers and thereby which hardware is supported.
 [[Category:Articles]]

@@ Line 1: / Line 1: @@
-There is a number of ways to get a controller application to send DMX data to a hardware interface (that can send the data out on your DMX wire).
+==Drivers and software==
 Sometime the driver is split up into:
-* Hardware driver for sending raw data to and from the hardware
+* Hardware driver for sending raw data to and from the hardware.
-* Protocol driver for translating the codes from the controller app to codes the hardware can understand (both ways)
+* Protocol driver for translating the codes from the controller app to codes the hardware can understand (both ways).
-On Linux there exists a system for hardware drivers, which is a kernel driver with a common interface to the controller software that is independent of which hardware you choose to use. This is called DMX4Linux.
+Most USB interfaces works as a "virtual com port", which means that there is a real com port in the hardware, and a driver makes a com interface available i the operating system. Most USB com ports are supported 'out of the box' on both Windows and Linux (nice!), so most USB-to-DMX interfaces just need a protocol driver (easy to make and use)
-Most USB interfaces works as a "virtual com port", which means that there is a real com port in the hardware, and a driver makes a com interface available i the operating system. Most USB com ports are supported 'out of the box' on both Windows and Linux (nice!), so most USB-to-DMX interfaces just need a protocol driver (easy to make and use)
+On Windows it seems that (almost) all controller apps have their own drivers. Probably because no good framework existed.
-If your are looking for a interface to buy, then start with finding your favorite controller app, and find out which drivers and thereby which hardware is supported.
+[[Category:Articles]]

← Older revision	Revision as of 14:31, 13 November 2008
(No difference)

← Older revision		Revision as of 20:42, 9 January 2007
Line 14:		Line 14:

	On Windows it seems that (almost) all controller apps have their own drivers.		On Windows it seems that (almost) all controller apps have their own drivers.
		+
		+
		+	Remember that it is possible to send DMX data over a network to an other computer or a ethernet-to-DMX hardware interface


	If your are looking for a interface to buy, then start with finding your favorite controller app, and find out which drivers and thereby which hardware is supported.		If your are looking for a interface to buy, then start with finding your favorite controller app, and find out which drivers and thereby which hardware is supported.

@@ Line 8: / Line 8: @@
 On linux there exists a system for hardware drivers, which is a kernel driver with a common interface to the controller sofware that is independent of which hardware you choose to use. This is called DMX4Linux.
-For various reasons there is as many separate driveres as there is in DMX4Linux.
+For various reasons there is as many separate drivers as there is in DMX4Linux.
-Most USB interfaces works as a "virual com port", which means that there is a real com port in the hardware, and a driver makes a com interface available i the operating system. Most USB com ports are supported 'out of the box' on both Windows and Linux (nice!), so most USB-to-DMX interfaces just need a protocol driver (easy to make and use)
+Most USB interfaces works as a "virtual com port", which means that there is a real com port in the hardware, and a driver makes a com interface available i the operating system. Most USB com ports are supported 'out of the box' on both Windows and Linux (nice!), so most USB-to-DMX interfaces just need a protocol driver (easy to make and use)