Devices - Revision history

Mcefan: /* What is a Device? */

2016-03-05T11:03:42Z

What is a Device?

←Older revision		Revision as of 11:03, 5 March 2016
Line 6:		Line 6:
	The {{l}} Core is a router that {{l}} system components use to communicate using the DCE protocol. Hardware devices and software without DCE capability can not send and receive communications over the DCE bus. {{l}} solves the problem by creating software "devices" that connect to the DCE bus for the purpose of translating hardware and software native communications into DCE. At the moment, no hardware is manufactured specifically with the DCE protocol. To control a hardware device with LinuxMCE, a corresponding software device is created. Each LinuxMCE system component has a corresponding "device" that it uses to communicate in DCE with the other LinuxMCE system components.		The {{l}} Core is a router that {{l}} system components use to communicate using the DCE protocol. Hardware devices and software without DCE capability can not send and receive communications over the DCE bus. {{l}} solves the problem by creating software "devices" that connect to the DCE bus for the purpose of translating hardware and software native communications into DCE. At the moment, no hardware is manufactured specifically with the DCE protocol. To control a hardware device with LinuxMCE, a corresponding software device is created. Each LinuxMCE system component has a corresponding "device" that it uses to communicate in DCE with the other LinuxMCE system components.

	A device is a software object in LinuxMCE that connects a software or hardware component to the DCE bus to enable it communicate with the other LinuxMCE system components using the DCE protocol~~.<br>~~		A device is a software object in LinuxMCE that connects a software or hardware component to the DCE bus to enable it communicate with the other LinuxMCE system components using the DCE protocol, translating various hardware and software communications into DCE when necessary.
	~~A device enables communication with other system components by~~ translating various hardware and software communications into DCE.

	{{p}}		{{p}}

Mcefan: /* What is a Device? */

2016-03-05T11:01:33Z

What is a Device?

←Older revision		Revision as of 11:01, 5 March 2016
Line 4:		Line 4:
	For the purpose of consistency throughout this documentation, hardware equipment will be called "hardware device". The generic term "device" is used to refer to the software object in LinuxMCE that enables DCE communication between hardware and software components in the LinuxMCE system. {{p}}		For the purpose of consistency throughout this documentation, hardware equipment will be called "hardware device". The generic term "device" is used to refer to the software object in LinuxMCE that enables DCE communication between hardware and software components in the LinuxMCE system. {{p}}

	The {{l}} Core is a router that {{l}} system components use to communicate using the DCE protocol. Hardware devices and software without DCE capability can not send and receive communications over the DCE bus. {{l}} solves the problem by creating software "devices" that connect to the DCE bus for the purpose of translating hardware and software native communications into DCE. At the moment, no hardware is manufactured specifically with the DCE protocol. To control a hardware device with LinuxMCE, a corresponding software device is created ~~as a component of the system~~. Each LinuxMCE system component has a corresponding "device" that it uses to communicate in DCE with the other LinuxMCE system components.		The {{l}} Core is a router that {{l}} system components use to communicate using the DCE protocol. Hardware devices and software without DCE capability can not send and receive communications over the DCE bus. {{l}} solves the problem by creating software "devices" that connect to the DCE bus for the purpose of translating hardware and software native communications into DCE. At the moment, no hardware is manufactured specifically with the DCE protocol. To control a hardware device with LinuxMCE, a corresponding software device is created. Each LinuxMCE system component has a corresponding "device" that it uses to communicate in DCE with the other LinuxMCE system components.

	A device is a software object in LinuxMCE that connects a software or hardware component to the DCE bus to enable it communicate with the other LinuxMCE system components using the DCE protocol.<br>		A device is a software object in LinuxMCE that connects a software or hardware component to the DCE bus to enable it communicate with the other LinuxMCE system components using the DCE protocol.<br>

Mcefan: /* What is a Device? */

2016-03-05T10:58:13Z

What is a Device?

←Older revision		Revision as of 10:58, 5 March 2016
Line 2:		Line 2:

	==What is a Device?==		==What is a Device?==
	For the purpose of consistency throughout this documentation, hardware equipment will be called "hardware device". The generic term "device" is used to refer to the software object in LinuxMCE that enables DCE communication between hardware and software components in the LinuxMCE system.		For the purpose of consistency throughout this documentation, hardware equipment will be called "hardware device". The generic term "device" is used to refer to the software object in LinuxMCE that enables DCE communication between hardware and software components in the LinuxMCE system. {{p}}

	The {{l}} Core is a router that {{l}} system components use to communicate using the DCE protocol. Hardware devices and software without DCE capability can not send and receive communications over the DCE bus. {{l}} solves the problem by creating software "devices" that connect to the DCE bus for the purpose of translating hardware and software native communications into DCE. At the moment, no hardware is manufactured specifically with the DCE protocol. To control a hardware device with LinuxMCE, a corresponding software device is created as a component of the system. Each LinuxMCE system component has a corresponding "device" that it uses to communicate in DCE with the other LinuxMCE system components.		The {{l}} Core is a router that {{l}} system components use to communicate using the DCE protocol. Hardware devices and software without DCE capability can not send and receive communications over the DCE bus. {{l}} solves the problem by creating software "devices" that connect to the DCE bus for the purpose of translating hardware and software native communications into DCE. At the moment, no hardware is manufactured specifically with the DCE protocol. To control a hardware device with LinuxMCE, a corresponding software device is created as a component of the system. Each LinuxMCE system component has a corresponding "device" that it uses to communicate in DCE with the other LinuxMCE system components.

Mcefan: /* What is a Device? */

2016-03-05T10:50:59Z

What is a Device?

←Older revision		Revision as of 10:50, 5 March 2016
Line 2:		Line 2:

	==What is a Device?==		==What is a Device?==
			For the purpose of consistency throughout this documentation, hardware equipment will be called "hardware device". The generic term "device" is used to refer to the software object in LinuxMCE that enables DCE communication between hardware and software components in the LinuxMCE system.

	~~For~~ the ~~purpose of consistency throughout this documentation, hardware equipment will be called "hardware device"~~.~~<br>~~		The {{l}} Core is a router that {{l}} system components use to communicate using the DCE protocol. Hardware devices and software without DCE capability can not send and receive communications over the DCE bus. {{l}} solves the problem by creating software "devices" that connect to the DCE bus for the purpose of translating hardware and software native communications into DCE. At the moment, no hardware is manufactured specifically with the DCE protocol. To control a hardware device with LinuxMCE, a corresponding software device is created as a component of the system. Each LinuxMCE system component has a corresponding "device" that it uses to communicate in DCE with the other LinuxMCE system components.
	~~The generic term~~ "~~device~~" ~~is used to refer~~ to the ~~software object in LinuxMCE that enables~~ DCE ~~communication between~~ hardware and software ~~components in~~ the LinuxMCE system. Each LinuxMCE system component has a corresponding "device" that it uses to communicate in DCE with the other LinuxMCE system components. ~~To control a hardware device with LinuxMCE, a corresponding software device is created as a component of the system.<br>~~

	~~<center><pre>~~		A device is a software object in LinuxMCE that connects a software or hardware component to the DCE bus to enable it communicate with the other LinuxMCE system components using the DCE protocol.<br>
	A "device" is a software ~~component~~ that connects the DCE bus to the ~~software or hardware item that is part of the interaction of the~~ LinuxMCE system.		A device enables communication with other system components by translating various hardware and software communications into DCE.
	~~</pre>~~<~~/center~~>
	A device enables communication ~~between all~~ system components by translating various hardware and software communications to DCE. With DCE, devices can communicate with each other using a set of well defined and accepted commands (On, Off, Volume Up, Volume Down, Mute, Press 0 through 9, etc.). They can also emit events (notify that something happened) and they can hold configuration (this light switch is ON, it connects to port B on the interface, etc.) which we call device DATA.

	~~LinuxMCE devices have three capabilities: Data, Commands, and Events - hence the acronym DCE. They can:~~
	~~:# Set/Retrieve configuration '''data'''~~
	~~:# Perform a '''command''' (turn on, turn off, fast forward, etc.)~~
	~~:# Send/Report '''events''' (e.g. 'motion detected', 'playback started', etc.)~~

	~~A device is a software object in LinuxMCE that connects a software or hardware component to the DCE bus to enable it communicate with the other LinuxMCE system components using the DCE protocol.~~
	{{p}}		{{p}}

Mcefan at 09:52, 5 March 2016

2016-03-05T09:52:06Z

@@ Line 1: / Line 1: @@
 [[Category: Admin Website| ]]
 <p>These wizard pages are used to add devices to your installation.</p>
 <p>The "Interfaces" section is for devices that interface with some sort of master control, or devices that control other non-DCE devices.  For example, a lighting control system, a security alarm panel, or a home automation master controller are all interfaces.  These devices will connect directly to your LinuxMCE system via some interface, like RS232, and then they will control their own devices which are connected to them, such as a light switch, motion detector, etc.  Interface Modules, like the Global Cache GC100, are also added in the "Interfaces" page.</p>

Mcefan at 14:53, 19 October 2012

2012-10-19T14:53:00Z

←Older revision		Revision as of 14:53, 19 October 2012
Line 1:		Line 1:
			[[Category: Admin Website\| ]]

	<p>These wizard pages are used to add devices to your installation.</p>		<p>These wizard pages are used to add devices to your installation.</p>
	<p>The "Interfaces" section is for devices that interface with some sort of master control, or devices that control other non-DCE devices. For example, a lighting control system, a security alarm panel, or a home automation master controller are all interfaces. These devices will connect directly to your LinuxMCE system via some interface, like RS232, and then they will control their own devices which are connected to them, such as a light switch, motion detector, etc. Interface Modules, like the Global Cache GC100, are also added in the "Interfaces" page.</p>		<p>The "Interfaces" section is for devices that interface with some sort of master control, or devices that control other non-DCE devices. For example, a lighting control system, a security alarm panel, or a home automation master controller are all interfaces. These devices will connect directly to your LinuxMCE system via some interface, like RS232, and then they will control their own devices which are connected to them, such as a light switch, motion detector, etc. Interface Modules, like the Global Cache GC100, are also added in the "Interfaces" page.</p>
Line 17:		Line 19:
	*[[Generic Serial Devices]]		*[[Generic Serial Devices]]
	*[[Floorplans \|Floorplan Wizard]]		*[[Floorplans \|Floorplan Wizard]]
	~~[[Category: Admin Website]]~~

Chris Caven at 15:33, 19 April 2010

2010-04-19T15:33:13Z

←Older revision		Revision as of 15:33, 19 April 2010
Line 2:		Line 2:
	<p>The "Interfaces" section is for devices that interface with some sort of master control, or devices that control other non-DCE devices. For example, a lighting control system, a security alarm panel, or a home automation master controller are all interfaces. These devices will connect directly to your LinuxMCE system via some interface, like RS232, and then they will control their own devices which are connected to them, such as a light switch, motion detector, etc. Interface Modules, like the Global Cache GC100, are also added in the "Interfaces" page.</p>		<p>The "Interfaces" section is for devices that interface with some sort of master control, or devices that control other non-DCE devices. For example, a lighting control system, a security alarm panel, or a home automation master controller are all interfaces. These devices will connect directly to your LinuxMCE system via some interface, like RS232, and then they will control their own devices which are connected to them, such as a light switch, motion detector, etc. Interface Modules, like the Global Cache GC100, are also added in the "Interfaces" page.</p>
	<p>After you add the interface, then you can add the other devices that will use that interface. For example, you may have some X10 light switches in your house. These are not LinuxMCE DCE Devices--LinuxMCE cannot control them directly. LinuxMCE can only control them using an X10 interface module. So, before you can add the X10 light switches, you must first go to the interface section and add an x10 lighting interface. Then you can go to 'lights' and add lights that will use that interface. Similarly if you have a normal, infrared controlled TV, that TV does not communicate directly with the LinuxMCE system. It needs an interface module like the GC100 that LinuxMCE does communicate with, and which then sends the infrared codes to control the TV. So before adding the TV in the AV Section, first add the interface.</p>		<p>After you add the interface, then you can add the other devices that will use that interface. For example, you may have some X10 light switches in your house. These are not LinuxMCE DCE Devices--LinuxMCE cannot control them directly. LinuxMCE can only control them using an X10 interface module. So, before you can add the X10 light switches, you must first go to the interface section and add an x10 lighting interface. Then you can go to 'lights' and add lights that will use that interface. Similarly if you have a normal, infrared controlled TV, that TV does not communicate directly with the LinuxMCE system. It needs an interface module like the GC100 that LinuxMCE does communicate with, and which then sends the infrared codes to control the TV. So before adding the TV in the AV Section, first add the interface.</p>
	<p>The "AV" section is for all your audio/video devices, like ~~TV's~~, DVD ~~Player's~~, Stereo Receivers, Satellite Boxes, etc.</p>		<p>The "AV" section is for all your audio/video devices, like TVs, DVD Players, Stereo Receivers, Satellite Boxes, etc.</p>
	*Core		*Core
	*[[Interfaces]]		*[[Interfaces]]

Rwilson131 at 00:53, 16 October 2007

2007-10-16T00:53:25Z

←Older revision		Revision as of 00:53, 16 October 2007
Line 11:		Line 11:
	*[[Climate]]		*[[Climate]]
	*[[Irrigation Devices]]		*[[Irrigation Devices]]
	*[[Security]]		*[[Devices Security \| Security]]
	*[[Surveillance Cameras]]		*[[Surveillance Cameras]]
	*[[Phone Extensions\| Phones]]		*[[Phone Extensions\| Phones]]

Rwilson131 at 00:29, 16 October 2007

2007-10-16T00:29:49Z

←Older revision		Revision as of 00:29, 16 October 2007
Line 3:		Line 3:
	<p>After you add the interface, then you can add the other devices that will use that interface. For example, you may have some X10 light switches in your house. These are not LinuxMCE DCE Devices--LinuxMCE cannot control them directly. LinuxMCE can only control them using an X10 interface module. So, before you can add the X10 light switches, you must first go to the interface section and add an x10 lighting interface. Then you can go to 'lights' and add lights that will use that interface. Similarly if you have a normal, infrared controlled TV, that TV does not communicate directly with the LinuxMCE system. It needs an interface module like the GC100 that LinuxMCE does communicate with, and which then sends the infrared codes to control the TV. So before adding the TV in the AV Section, first add the interface.</p>		<p>After you add the interface, then you can add the other devices that will use that interface. For example, you may have some X10 light switches in your house. These are not LinuxMCE DCE Devices--LinuxMCE cannot control them directly. LinuxMCE can only control them using an X10 interface module. So, before you can add the X10 light switches, you must first go to the interface section and add an x10 lighting interface. Then you can go to 'lights' and add lights that will use that interface. Similarly if you have a normal, infrared controlled TV, that TV does not communicate directly with the LinuxMCE system. It needs an interface module like the GC100 that LinuxMCE does communicate with, and which then sends the infrared codes to control the TV. So before adding the TV in the AV Section, first add the interface.</p>
	<p>The "AV" section is for all your audio/video devices, like TV's, DVD Player's, Stereo Receivers, Satellite Boxes, etc.</p>		<p>The "AV" section is for all your audio/video devices, like TV's, DVD Player's, Stereo Receivers, Satellite Boxes, etc.</p>
			*Core
			*[[Interfaces]]
			*[[AV Devices\| A/V Equipment]]
			*[[Media Directors]]
	*[[Orbiters]]		*[[Orbiters]]
	*[[Interfaces]]
	*[[Devices Security]]
	*[[Lights]]		*[[Lights]]
	*[[Media Directors]]
	*[[Climate]]		*[[Climate]]
	*[[AV Devices]]		*[[Irrigation Devices]]
	**[[Infrared Codes]]		*[[Security]]
	***[[Learning/typing my own code]]
	**[[AV Properties]]
	**[[TOAD vs Discrete Codes]]
	*[[~~Floorplans~~]]
	*[[Surveillance Cameras]]		*[[Surveillance Cameras]]
			*[[Phone Extensions\| Phones]]
	*[[Phone Lines]]		*[[Phone Lines]]
	*[[~~Phone Extensions~~]]		*[[Generic Serial Devices]]
	*[[~~EIB~~]]		*[[Floorplans \|Floorplan Wizard]]
	[[Category: Admin Website]]		[[Category: Admin Website]]

Rwilson131 at 04:11, 15 October 2007

2007-10-15T04:11:11Z

←Older revision		Revision as of 04:11, 15 October 2007
Line 3:		Line 3:
	<p>After you add the interface, then you can add the other devices that will use that interface. For example, you may have some X10 light switches in your house. These are not LinuxMCE DCE Devices--LinuxMCE cannot control them directly. LinuxMCE can only control them using an X10 interface module. So, before you can add the X10 light switches, you must first go to the interface section and add an x10 lighting interface. Then you can go to 'lights' and add lights that will use that interface. Similarly if you have a normal, infrared controlled TV, that TV does not communicate directly with the LinuxMCE system. It needs an interface module like the GC100 that LinuxMCE does communicate with, and which then sends the infrared codes to control the TV. So before adding the TV in the AV Section, first add the interface.</p>		<p>After you add the interface, then you can add the other devices that will use that interface. For example, you may have some X10 light switches in your house. These are not LinuxMCE DCE Devices--LinuxMCE cannot control them directly. LinuxMCE can only control them using an X10 interface module. So, before you can add the X10 light switches, you must first go to the interface section and add an x10 lighting interface. Then you can go to 'lights' and add lights that will use that interface. Similarly if you have a normal, infrared controlled TV, that TV does not communicate directly with the LinuxMCE system. It needs an interface module like the GC100 that LinuxMCE does communicate with, and which then sends the infrared codes to control the TV. So before adding the TV in the AV Section, first add the interface.</p>
	<p>The "AV" section is for all your audio/video devices, like TV's, DVD Player's, Stereo Receivers, Satellite Boxes, etc.</p>		<p>The "AV" section is for all your audio/video devices, like TV's, DVD Player's, Stereo Receivers, Satellite Boxes, etc.</p>
			*[[Orbiters]]
			*[[Interfaces]]
			*[[Devices Security]]
			*[[Lights]]
			*[[Media Directors]]
			*[[Climate]]
			*[[AV Devices]]
			**[[Infrared Codes]]
			***[[Learning/typing my own code]]
			**[[AV Properties]]
			**[[TOAD vs Discrete Codes]]
			*[[Floorplans]]
			*[[Surveillance Cameras]]
			*[[Phone Lines]]
			*[[Phone Extensions]]
			*[[EIB]]
			[[Category: Admin Website]]