User Manual - Revision history

Mcefan: /* How to get started with LinuxMCE */

2016-03-22T01:59:00Z

How to get started with LinuxMCE

←Older revision		Revision as of 01:59, 22 March 2016
Line 172:		Line 172:
	== How to get started with LinuxMCE ==		== How to get started with LinuxMCE ==
	Next, go to the [[How to get started with LinuxMCE]] to learn how to install, and start using the system.		Next, go to the [[How to get started with LinuxMCE]] to learn how to install, and start using the system.

			{{p}}

Mcefan: /* The DCE protocol */

2016-03-06T02:22:52Z

The DCE protocol

←Older revision		Revision as of 02:22, 6 March 2016
Line 151:		Line 151:
	:# Send/Report ''''''<big>E</big>'''vents''' (e.g. 'motion detected', 'playback started', etc.)		:# Send/Report ''''''<big>E</big>'''vents''' (e.g. 'motion detected', 'playback started', etc.)

	For a list of protocols {{l}} supports, see [[Automation#Automation protocols\|Automation protocols]]		For a list of the protocols {{l}} supports, see [[Automation#Automation protocols\|Automation protocols]]
	{{p}}		{{p}}

Mcefan: /* The DCE protocol */

2016-03-06T02:22:05Z

The DCE protocol

←Older revision		Revision as of 02:22, 6 March 2016
Line 150:		Line 150:
	:# Perform a ''''''<big>C</big>'''ommand''' (turn on, turn off, fast forward, etc.)		:# Perform a ''''''<big>C</big>'''ommand''' (turn on, turn off, fast forward, etc.)
	:# Send/Report ''''''<big>E</big>'''vents''' (e.g. 'motion detected', 'playback started', etc.)		:# Send/Report ''''''<big>E</big>'''vents''' (e.g. 'motion detected', 'playback started', etc.)

			For a list of protocols {{l}} supports, see [[Automation#Automation protocols\|Automation protocols]]
	{{p}}		{{p}}

Mcefan: /* The DCE protocol */

2016-03-06T00:21:58Z

The DCE protocol

←Older revision		Revision as of 00:21, 6 March 2016
Line 138:		Line 138:

	===The DCE protocol===		===The DCE protocol===
	DCE is the protocol used by {{l}} system components to interact. With DCE, hardware and software of different native protocols 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~~ 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.~~ The acronym DCE comes from the three major operations performed using the protocol: Data, Commands, and Events. <br>		DCE is the protocol used by {{l}} system components to interact. With DCE, hardware and software of different native protocols 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.)
			* emit events to notify that something happened
			* hold configuration (this light switch is ON, it connects to port B on the interface, etc.)


			The acronym DCE comes from the three major operations performed using the protocol: Data, Commands, and Events. <br>

	A DCE device can:		A DCE device can:
	:# Set/Retrieve configuration '''~~data~~'''		:# Set/Retrieve configuration which we call device ''''''<big>D</big>'''ata'''
	:# Perform a '''~~command~~''' (turn on, turn off, fast forward, etc.)		:# Perform a ''''''<big>C</big>'''ommand''' (turn on, turn off, fast forward, etc.)
	:# Send/Report '''~~events~~''' (e.g. 'motion detected', 'playback started', etc.)		:# Send/Report ''''''<big>E</big>'''vents''' (e.g. 'motion detected', 'playback started', etc.)
	{{p}}		{{p}}

Mcefan: /* Understanding LinuxMCE operation */

2016-03-05T11:01:39Z

Understanding LinuxMCE operation

←Older revision		Revision as of 11:01, 5 March 2016
Line 136:		Line 136:
	At its core, LinuxMCE is a router connected to a bus, running with a communication protocol called DCE. You can think of a LinuxMCE installation as a stack of devices that connect to the bus to communicate to the DCE Router using the DCE protocol.		At its core, LinuxMCE is a router connected to a bus, running with a communication protocol called DCE. You can think of a LinuxMCE installation as a stack of devices that connect to the bus to communicate to the DCE Router using the DCE protocol.
	{{p}}		{{p}}

	~~=== Devices ===~~
	~~{{#lsth:Devices\|What is a Device?}}~~


	===The DCE protocol===		===The DCE protocol===
	DCE is the protocol used by {{l}} system components to interact. With DCE, hardware and software of different native protocols 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 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. The acronym DCE comes from the three major operations performed using the protocol: Data, Commands, and Events. <br>		DCE is the protocol used by {{l}} system components to interact. With DCE, hardware and software of different native protocols 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 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. The acronym DCE comes from the three major operations performed using the protocol: Data, Commands, and Events. <br>
	DCE ~~devices~~ can:		A DCE device can:
	:# Set/Retrieve configuration '''data'''		:# Set/Retrieve configuration '''data'''
	:# Perform a '''command''' (turn on, turn off, fast forward, etc.)		:# Perform a '''command''' (turn on, turn off, fast forward, etc.)
	:# Send/Report '''events''' (e.g. 'motion detected', 'playback started', etc.)		:# Send/Report '''events''' (e.g. 'motion detected', 'playback started', etc.)
	{{p}}		{{p}}

			=== Devices ===
			{{#lsth:Devices\|What is a Device?}}

	=== Scenarios ===		=== Scenarios ===

Mcefan: /* Devices */

2016-03-05T10:23:57Z

Devices

←Older revision		Revision as of 10:23, 5 March 2016
Line 139:		Line 139:
	=== Devices ===		=== Devices ===
	{{#lsth:Devices\|What is a Device?}}		{{#lsth:Devices\|What is a Device?}}


			===The DCE protocol===
			DCE is the protocol used by {{l}} system components to interact. With DCE, hardware and software of different native protocols 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 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. The acronym DCE comes from the three major operations performed using the protocol: Data, Commands, and Events. <br>
			DCE devices 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.)
			{{p}}

	=== Scenarios ===		=== Scenarios ===

Mcefan: /* Understanding LinuxMCE operation */

2016-03-05T09:53:55Z

Understanding LinuxMCE operation

←Older revision		Revision as of 09:53, 5 March 2016
Line 134:		Line 134:

	== Understanding LinuxMCE operation ==		== Understanding LinuxMCE operation ==
	LinuxMCE~~'s main concepts are [[Devices]]~~, ~~Commands (aka [[Scenarios]], or, Activities), and [[Events]]~~.		At its core, LinuxMCE is a router connected to a bus, running with a communication protocol called DCE. You can think of a LinuxMCE installation as a stack of devices that connect to the bus to communicate to the DCE Router using the DCE protocol.

	~~This section explains the roles~~ of ~~Devices, Scenarios, and Events in~~ the ~~operation of~~ the ~~LinuxMCE system, and, their interactions that constitute~~ the ~~operation of LinuxMCE~~.
	{{p}}		{{p}}

	=== Devices ===		=== Devices ===
	~~For the purpose of consistency throughout this documentation, hardware equipment will be called "hardware device".<br>~~		{{#lsth:Devices\|What is a 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. At its core, LinuxMCE is a bus and the communication protocol running on it is DCE. 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 component that connects the DCE bus to the software or hardware item that is part of the interaction of the LinuxMCE system.~~
	~~</pre></center>~~
	A device enables communication between all system components by translating various hardware and software communications to DCE. You can think of a LinuxMCE installation as a stack of devices that connect to the DCE Router to communicate using the DCE protocol. 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~~}}

	=== Scenarios ===		=== Scenarios ===
Line 166:		Line 149:

	=== Interactions ===		=== Interactions ===
	Commands (usually groups of commands) are arranged in Scenarios that control devices in the home when activated. Orbiters ("remote controls") load user interfaces that have buttons (Scenarios) used to send commands to the system. Devices will report events to the Core, which will then uses the information to send predefined commands (Scenarios) and setup the state of the system through the house. The Core coordinates interaction between devices. Each device responds to commands based on its' intent and the magic of automation happens.		Commands (usually groups of commands) are arranged in Scenarios that control devices in the home when activated. Orbiters ("remote controls") load user interfaces that have buttons (Scenarios) used to send commands to the system. Devices will report events to the Core, which will then uses the information to send predefined commands (Scenarios) and setup the state of the system through the house. The Core coordinates interaction between devices. Each device responds to commands based on its intent and the magic of automation happens.

	{{p}}		{{p}}

Mcefan: /* Devices */

2016-03-05T09:23:03Z

Devices

←Older revision		Revision as of 09:23, 5 March 2016
Line 141:		Line 141:
	=== Devices ===		=== Devices ===
	For the purpose of consistency throughout this documentation, hardware equipment will be called "hardware device".<br>		For the purpose of consistency throughout this documentation, hardware equipment will be called "hardware device".<br>
	The generic term "device" is used to refer to the LinuxMCE ~~software component~~ that enables DCE communication between hardware and software components in the LinuxMCE system. At its core, LinuxMCE is a bus and the communication protocol running on it is DCE. Each LinuxMCE system component has a corresponding "device" that it uses to communicate in DCE with the other LinuxMCE system components.~~<br>~~		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. At its core, LinuxMCE is a bus and the communication protocol running on it is DCE. 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>
	~~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.<br>
	A device enables communication between all system components by translating various hardware and software communications to DCE. You can think of a LinuxMCE installation as a stack of devices, that all connect to the DCE Router to communicate using the DCE protocol. 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.

	~~Devices~~ have three capabilities: Data, Commands, and Events hence the ~~accronym~~ DCE. They can:		<center><pre>
			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.
			</pre></center>
			A device enables communication between all system components by translating various hardware and software communications to DCE. You can think of a LinuxMCE installation as a stack of devices that connect to the DCE Router to communicate using the DCE protocol. 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'''		:# Set/Retrieve configuration '''data'''
	:# Perform a '''command''' (turn on, turn off, fast forward, etc.)		:# Perform a '''command''' (turn on, turn off, fast forward, etc.)
	:# Send/Report '''events''' (e.g. 'motion detected', 'playback started', 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: /* Devices */

2016-03-04T08:14:26Z

Devices

←Older revision		Revision as of 08:14, 4 March 2016
Line 143:		Line 143:
	The generic term "device" is used to refer to the LinuxMCE software component that enables DCE communication between hardware and software components in the LinuxMCE system. At its core, LinuxMCE is a bus and the communication protocol running on it is DCE. Each LinuxMCE system component has a corresponding "device" that it uses to communicate in DCE with the other LinuxMCE system components.<br>		The generic term "device" is used to refer to the LinuxMCE software component that enables DCE communication between hardware and software components in the LinuxMCE system. At its core, LinuxMCE is a bus and the communication protocol running on it is DCE. Each LinuxMCE system component has a corresponding "device" that it uses to communicate in DCE with the other LinuxMCE system components.<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.<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.<br>
	A device enables communication between all system components by translating various hardware and software communications to DCE. You can think of a LinuxMCE installation as a stack of devices, that all connect to the DCE Router to communicate using the DCE protocol.		A device enables communication between all system components by translating various hardware and software communications to DCE. You can think of a LinuxMCE installation as a stack of devices, that all connect to the DCE Router to communicate using the DCE protocol. 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.

			Devices have three capabilities: Data, Commands, and Events hence the accronym 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.)

	~~All devices have three sets of features known as "DCE" (Data, Commands, Events):~~

	~~# Set/Retrieve configuration '''data'''~~
	~~# Perform a '''command''' (turn on, turn off, fast forward, etc.)~~
	~~# Send/Report '''events''' (e.g. 'motion detected', 'playback started', etc.)~~
	{{p}}		{{p}}

Mcefan: /* Devices */

2016-03-04T08:02:14Z

Devices

←Older revision		Revision as of 08:02, 4 March 2016
Line 143:		Line 143:
	The generic term "device" is used to refer to the LinuxMCE software component that enables DCE communication between hardware and software components in the LinuxMCE system. At its core, LinuxMCE is a bus and the communication protocol running on it is DCE. Each LinuxMCE system component has a corresponding "device" that it uses to communicate in DCE with the other LinuxMCE system components.<br>		The generic term "device" is used to refer to the LinuxMCE software component that enables DCE communication between hardware and software components in the LinuxMCE system. At its core, LinuxMCE is a bus and the communication protocol running on it is DCE. Each LinuxMCE system component has a corresponding "device" that it uses to communicate in DCE with the other LinuxMCE system components.<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.<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.<br>
	A device enables communication between all system components by translating various hardware and software communications to DCE.		A device enables communication between all system components by translating various hardware and software communications to DCE. You can think of a LinuxMCE installation as a stack of devices, that all connect to the DCE Router to communicate using the DCE protocol.