Device Templates - Revision history

Mcefan: /* Using device templates */

2012-11-01T15:50:30Z

Using device templates

←Older revision		Revision as of 15:50, 1 November 2012
Line 72:		Line 72:
	:* the device ID is not in the expected range as described above for the MAC address.		:* the device ID is not in the expected range as described above for the MAC address.
	:* there are more than one of the same model of device, and the "only one per md" setting is set.		:* there are more than one of the same model of device, and the "only one per md" setting is set.
	:* the radars are not running, or are not running correctly. A radar in LinuxMCE is a process that scans for available resources. Currently, ~~only~~ hard drives and network shares are ~~scanned~~, ~~in addition to serial device detection~~ scripts. You can see what radars are available by running the command <code>ls /usr/pluto/bin/Radar.sh</code> ~~<br>See [[ssh from windows]] for instructions on using the command prompt~~.		:* the radars are not running, or are not running correctly. A radar in LinuxMCE is a process that scans for available resources. Currently, the system contains serial device detection scripts, hard drives, and network shares scanning radars. These radars are automatically ran by the system and should not generally be run manually, as some are background scripts which would just create multiple instances. You can see what radars are available by running the command <code>ls /usr/pluto/bin/Radar.sh</code>.
	:* the device is compatible with LinuxMCE, but no template has been created for it yet.		:* the device is compatible with LinuxMCE, but no template has been created for it yet.
	~~;Note: The system runs these radars, they should not generally be run manually, as some are backgrounded scripts which would just create multiple instances.~~
	:* the device is not compatible with LinuxMCE, so no template has been created, nor can be created. the device will not work with LinuxMCE and needs to be replaced with a LinuxMCE compatible device.		:* the device is not compatible with LinuxMCE, so no template has been created, nor can be created. the device will not work with LinuxMCE and needs to be replaced with a LinuxMCE compatible device.
	:* unrelated things, like USB just not working under the strain of poll, which should not happen, or any other hardware error.		:* unrelated things, like USB just not working under the strain of poll, which should not happen, or any other hardware error.

Mcefan: /* Template development */

2012-11-01T15:36:05Z

Template development

←Older revision		Revision as of 15:36, 1 November 2012
Line 91:		Line 91:

	Device templates are not all mythical beasts with 9 heads. Adding a remote control is pretty easy if you know our codes (which you can explore by looking at the template for another remote) and you can use [http://linux.die.net/man/1/xev xev]. For instance, all that is necessary for an IR remote, is to adjust the mapping to correspond with the code emitted when pushing the buttons. Many things, like adding a capture card, are harder, and template development for some devices is an advanced topic that requires too many skills to be covered in this documentation. Some do require and expert level knowledge of the device to add, how it communicates, the protocols it uses, the Linux software it uses, the ability to write drivers, etc<!--and too many other things to list, all advanced-->. That is not to say that you can not work with templates at all. If you are willing to do the research, have some time to experiment with the various settings, and feel you have the skills to do so, please help us expand our set of templates. If you are just dealing with a basic device, and just need to make adjustments, please read on.		Device templates are not all mythical beasts with 9 heads. Adding a remote control is pretty easy if you know our codes (which you can explore by looking at the template for another remote) and you can use [http://linux.die.net/man/1/xev xev]. For instance, all that is necessary for an IR remote, is to adjust the mapping to correspond with the code emitted when pushing the buttons. Many things, like adding a capture card, are harder, and template development for some devices is an advanced topic that requires too many skills to be covered in this documentation. Some do require and expert level knowledge of the device to add, how it communicates, the protocols it uses, the Linux software it uses, the ability to write drivers, etc<!--and too many other things to list, all advanced-->. That is not to say that you can not work with templates at all. If you are willing to do the research, have some time to experiment with the various settings, and feel you have the skills to do so, please help us expand our set of templates. If you are just dealing with a basic device, and just need to make adjustments, please read on.
			{{p}}

	====Making Changes to Templates====		====Making Changes to Templates====

Mcefan: /* Template development */

2012-11-01T15:35:09Z

Template development

←Older revision		Revision as of 15:35, 1 November 2012
Line 90:		Line 90:
	Sometimes, you may need to edit a template to add a MAC address or identifier. This is a matter of adding the values. In the event you need to create a template, it is usually very helpful to look at one that performs a function similar to that of the device you are adding, copy the settings, and edit the fields by making some educated guesses, or exploring through trial and error by using a process of elimination. Please beware that changing setting in templates may make the corresponding devices inoperable. Always make note of what you are changing, and why, and keep track of the changes you make in order to be able to revert them in case you break something. A short ink mark lasts longer than a long memory.		Sometimes, you may need to edit a template to add a MAC address or identifier. This is a matter of adding the values. In the event you need to create a template, it is usually very helpful to look at one that performs a function similar to that of the device you are adding, copy the settings, and edit the fields by making some educated guesses, or exploring through trial and error by using a process of elimination. Please beware that changing setting in templates may make the corresponding devices inoperable. Always make note of what you are changing, and why, and keep track of the changes you make in order to be able to revert them in case you break something. A short ink mark lasts longer than a long memory.

	Device templates are not all mythical beasts with 9 heads. Adding a remote control is pretty easy if you know our codes (which you can ~~check~~ by looking at the template for another remote) and you can use xev. For instance, all that is necessary for an IR remote, is to adjust the mapping to correspond with the code emitted when pushing the buttons. Many things, like adding a capture card, are harder, and template development for some devices is an advanced topic that requires too many skills to be covered in this documentation. Some do require and expert level knowledge of the device to add, how it communicates, the protocols it uses, the Linux software it uses, the ability to write drivers, etc<!--and too many other things to list, all advanced-->. That is not to say that you can not work with templates at all. If you are willing to do the research, have some time to experiment with the various settings, and feel you have the skills to do so, please help us expand our set of templates. If you are just dealing with a basic device, and just need to make adjustments, please read on.		Device templates are not all mythical beasts with 9 heads. Adding a remote control is pretty easy if you know our codes (which you can explore by looking at the template for another remote) and you can use [http://linux.die.net/man/1/xev xev]. For instance, all that is necessary for an IR remote, is to adjust the mapping to correspond with the code emitted when pushing the buttons. Many things, like adding a capture card, are harder, and template development for some devices is an advanced topic that requires too many skills to be covered in this documentation. Some do require and expert level knowledge of the device to add, how it communicates, the protocols it uses, the Linux software it uses, the ability to write drivers, etc<!--and too many other things to list, all advanced-->. That is not to say that you can not work with templates at all. If you are willing to do the research, have some time to experiment with the various settings, and feel you have the skills to do so, please help us expand our set of templates. If you are just dealing with a basic device, and just need to make adjustments, please read on.

	====Making Changes to Templates====		====Making Changes to Templates====

Mcefan: /* Template development */

2012-11-01T07:21:45Z

Template development

←Older revision		Revision as of 07:21, 1 November 2012
Line 88:		Line 88:
	=Template development=		=Template development=

	Sometimes, you may need to edit a template to add a MAC address or identifier. In the event you need to ~~do so~~, it is usually very helpful to look at one that performs a function similar to that of the device you are adding, copy the settings, and edit the fields by making some educated guesses, or exploring through trial and error by using a process of elimination. Please beware that changing setting in templates may make the corresponding devices inoperable. Always make note of what you are changing, and why, and keep track of the changes you make in order to be able to revert them in case you break something. A short ink mark lasts longer than a long memory.		Sometimes, you may need to edit a template to add a MAC address or identifier. This is a matter of adding the values. In the event you need to create a template, it is usually very helpful to look at one that performs a function similar to that of the device you are adding, copy the settings, and edit the fields by making some educated guesses, or exploring through trial and error by using a process of elimination. Please beware that changing setting in templates may make the corresponding devices inoperable. Always make note of what you are changing, and why, and keep track of the changes you make in order to be able to revert them in case you break something. A short ink mark lasts longer than a long memory.

	Device templates are not all mythical beasts with 9 heads. Adding a remote control is pretty easy if you know our codes (which you can check by looking at the template for another remote) and you can use xev. For instance, all that is necessary for an IR remote, is to adjust the mapping to correspond with the code emitted when pushing the buttons. Many things, like adding a capture card, are harder, and template development for some devices is an advanced topic that requires too many skills to be covered in this documentation. Some do require and expert level knowledge of the device to add, how it communicates, the protocols it uses, the Linux software it uses, the ability to write drivers, etc<!--and too many other things to list, all advanced-->. That is not to say that you can not work with templates at all. If you are willing to do the research, have some time to experiment with the various settings, and feel you have the skills to do so, please help us expand our set of templates. If you are just dealing with a basic device, and just need to make adjustments, please read on.		Device templates are not all mythical beasts with 9 heads. Adding a remote control is pretty easy if you know our codes (which you can check by looking at the template for another remote) and you can use xev. For instance, all that is necessary for an IR remote, is to adjust the mapping to correspond with the code emitted when pushing the buttons. Many things, like adding a capture card, are harder, and template development for some devices is an advanced topic that requires too many skills to be covered in this documentation. Some do require and expert level knowledge of the device to add, how it communicates, the protocols it uses, the Linux software it uses, the ability to write drivers, etc<!--and too many other things to list, all advanced-->. That is not to say that you can not work with templates at all. If you are willing to do the research, have some time to experiment with the various settings, and feel you have the skills to do so, please help us expand our set of templates. If you are just dealing with a basic device, and just need to make adjustments, please read on.

Mcefan: /* Template development */

2012-11-01T07:14:00Z

Template development

←Older revision		Revision as of 07:14, 1 November 2012
Line 87:		Line 87:

	=Template development=		=Template development=

	Template development is an advanced topic that requires too many skills to be covered in this documentation. It requires and expert level knowledge of the device to add, how it communicates, the protocols it uses, the Linux software it uses, the ability to write drivers, and too many other things to list, all advanced. That is not to say that you can not work with templates at all. If you are willing to do the research, have some time to experiment with the various settings, and feel brave enough to do so, you can help us expand our set of templates.

	Sometimes, you may need to edit a template to add a MAC address or identifier. In the event you need to do so, it is usually very helpful to look at one that performs a function similar to that of the device you are adding, copy the settings, and edit the fields by making some educated guesses, or exploring through trial and error by using a process of elimination. Please beware that changing setting in templates may make the corresponding devices inoperable. Always make note of what you are changing, and why, and keep track of the changes you make in order to be able to revert them in case you break something. A short ink mark lasts longer than a long memory.		Sometimes, you may need to edit a template to add a MAC address or identifier. In the event you need to do so, it is usually very helpful to look at one that performs a function similar to that of the device you are adding, copy the settings, and edit the fields by making some educated guesses, or exploring through trial and error by using a process of elimination. Please beware that changing setting in templates may make the corresponding devices inoperable. Always make note of what you are changing, and why, and keep track of the changes you make in order to be able to revert them in case you break something. A short ink mark lasts longer than a long memory.

			Device templates are not all mythical beasts with 9 heads. Adding a remote control is pretty easy if you know our codes (which you can check by looking at the template for another remote) and you can use xev. For instance, all that is necessary for an IR remote, is to adjust the mapping to correspond with the code emitted when pushing the buttons. Many things, like adding a capture card, are harder, and template development for some devices is an advanced topic that requires too many skills to be covered in this documentation. Some do require and expert level knowledge of the device to add, how it communicates, the protocols it uses, the Linux software it uses, the ability to write drivers, etc<!--and too many other things to list, all advanced-->. That is not to say that you can not work with templates at all. If you are willing to do the research, have some time to experiment with the various settings, and feel you have the skills to do so, please help us expand our set of templates. If you are just dealing with a basic device, and just need to make adjustments, please read on.

	====Making Changes to Templates====		====Making Changes to Templates====

Mcefan: /* Using device templates */

2012-11-01T06:53:04Z

Using device templates

←Older revision		Revision as of 06:53, 1 November 2012
Line 69:		Line 69:
	The point of the device template structure is that you should not typically need to add them, as they are installed when the appropriate device makes an appearance to the system. It is possible to add them manually, but if you have to, something typically went wrong. In LinuxMCE, device addition is supposed to be Plug And Play. However, you may have a need to create a template for a device not recognized by the system. <br>		The point of the device template structure is that you should not typically need to add them, as they are installed when the appropriate device makes an appearance to the system. It is possible to add them manually, but if you have to, something typically went wrong. In LinuxMCE, device addition is supposed to be Plug And Play. However, you may have a need to create a template for a device not recognized by the system. <br>
	This can happen when:		This can happen when:
	:* the device's MAC address is not in the range that is currently set for the device. Unfortunately, manufacturers are not required to publish the range of identifiers they assign to each device model they produce, and finding them is not straight forward. If you happen to have a device that you know to be compatible with LinuxMCE but does not get detected, you can add the range of your specific device the template. You will find instructions that will help you accomplish that in the [[Edit_Page#Plug_.26_Play\|Plug & Play]] section of the [[Edit Device Template]] page.		:* the device's MAC address is not in the range that is currently set for the device. Unfortunately, manufacturers are not required to publish the range of identifiers they assign to each device model they produce, and finding them is not straight forward. If you happen to have a device that you know to be compatible with LinuxMCE but does not get detected, you can add the range of your specific device to the template. You will find instructions that will help you accomplish that in the [[Edit_Page#Plug_.26_Play\|Plug & Play]] section of the [[Edit Device Template]] page.
	:* the device ID is not in the expected range as described above for the MAC address.		:* the device ID is not in the expected range as described above for the MAC address.
	:* there are more than one of the same model of device, and the "only one per md" setting is set.		:* there are more than one of the same model of device, and the "only one per md" setting is set.

L3mce: /* Making Changes to Templates */

2012-11-01T06:39:01Z

Making Changes to Templates

←Older revision		Revision as of 06:39, 1 November 2012
Line 96:		Line 96:
	<!--{{red}}The "My Devices" page... {{c}}-->		<!--{{red}}The "My Devices" page... {{c}}-->

	If you make changes to the Device Template, this will affect your local system only. However, if you have fixed some errors, added functionality to an existing Device Template or created your own Device Template, you can use [[sqlCVS]] to ~~merge~~ those changes back into the master database so everyone can benefit from them. The same is true with everything in your local database--the user interface, even the online documentation you are reading now is editable. When you check-in changes using sqlCVS, sqlCVS will isolate those changes and notify the developer who is responsible for quality assurance for that section. Once the developer has confirmed the changes, he can have the changes merged back into LinuxMCE's main development database, which will eventually get propagated to the testing and release databases if the changes pass the tests.		If you make changes to the Device Template, this will affect your local system only. However, if you have fixed some errors, added functionality to an existing Device Template or created your own Device Template, you can use [[sqlCVS]] to submit a template for approval to fold those changes back into the master database so everyone can benefit from them. The same is true with everything in your local database--the user interface, even the online documentation you are reading now is editable. When you check-in changes using sqlCVS, sqlCVS will isolate those changes and notify the developer who is responsible for quality assurance for that section. Once the developer has confirmed the changes, he can have the changes merged back into LinuxMCE's main development database, which will eventually get propagated to the testing and release databases if the changes pass the tests.

	{{p}}		{{p}}

L3mce: /* Using device templates */

2012-11-01T06:35:04Z

Using device templates

←Older revision		Revision as of 06:35, 1 November 2012
Line 67:		Line 67:
	===Using device templates===		===Using device templates===

	The point of the device template structure is that you should not typically need to add them, as they are installed when the appropriate device makes an appearance on the ~~network~~. It is possible to add them manually, but if you have to, something is wrong. In LinuxMCE, device addition is supposed to be Plug And Play. However, you may have a need to create a template for a device not recognized by the system. <br>		The point of the device template structure is that you should not typically need to add them, as they are installed when the appropriate device makes an appearance to the system. It is possible to add them manually, but if you have to, something typically went wrong. In LinuxMCE, device addition is supposed to be Plug And Play. However, you may have a need to create a template for a device not recognized by the system. <br>
	This can happen when:		This can happen when:
	:* the device's MAC address is not in the range that is currently set for the device. Unfortunately, manufacturers are not required to publish the range of identifiers they assign to each device model they produce, and finding them is not straight forward. If you happen to have a device that you know to be compatible with LinuxMCE but does not get detected, you can ~~duplicate the template and~~ add the range ~~that~~ your device ~~belongs to~~. You will find instructions that will help you accomplish that in the [[Edit_Page#Plug_.26_Play\|Plug & Play]] section of the [[Edit Device Template]] page.		:* the device's MAC address is not in the range that is currently set for the device. Unfortunately, manufacturers are not required to publish the range of identifiers they assign to each device model they produce, and finding them is not straight forward. If you happen to have a device that you know to be compatible with LinuxMCE but does not get detected, you can add the range of your specific device the template. You will find instructions that will help you accomplish that in the [[Edit_Page#Plug_.26_Play\|Plug & Play]] section of the [[Edit Device Template]] page.
	:* the device ID is not in the expected range as ~~decribed~~ above for the MAC address.		:* the device ID is not in the expected range as described above for the MAC address.
	:* there are more than one of the same model of device, and the "only one per md" setting is set.		:* there are more than one of the same model of device, and the "only one per md" setting is set.
	:* the radars are not running, or are not running correctly. A radar in LinuxMCE is a process that scans for available resources. Currently, only hard drives and network shares are scanned. You can see what radars are available by running the command <code>ls /usr/pluto/bin/Radar.sh</code> <br>See [[ssh from windows]] for instructions on using the command prompt.		:* the radars are not running, or are not running correctly. A radar in LinuxMCE is a process that scans for available resources. Currently, only hard drives and network shares are scanned, in addition to serial device detection scripts. You can see what radars are available by running the command <code>ls /usr/pluto/bin/Radar.sh</code> <br>See [[ssh from windows]] for instructions on using the command prompt.
	:* the device is compatible with LinuxMCE, but no template has been created for it yet.		:* the device is compatible with LinuxMCE, but no template has been created for it yet.
			;Note: The system runs these radars, they should not generally be run manually, as some are backgrounded scripts which would just create multiple instances.
	:* the device is not compatible with LinuxMCE, so no template has been created, nor can be created. the device will not work with LinuxMCE and needs to be replaced with a LinuxMCE compatible device.		:* the device is not compatible with LinuxMCE, so no template has been created, nor can be created. the device will not work with LinuxMCE and needs to be replaced with a LinuxMCE compatible device.
	:* unrelated things, like ~~usb~~ just working under the strain of poll, which should not happen, or any other hardware error.		:* unrelated things, like USB just not working under the strain of poll, which should not happen, or any other hardware error.


	;Note: once committed, a template can not be deleted from the system.		;Note: once committed by someone with credentials, a template can not be deleted from the system.

	<!--		<!--

Mcefan at 06:24, 1 November 2012

2012-11-01T06:24:05Z

←Older revision		Revision as of 06:24, 1 November 2012
Line 20:		Line 20:

	These software modules are called templates because they serve as patterns used to add devices. When a new device is added to the system, it is created as an instance of the parent template that defines it, which makes it inherit the data in the template. While some of this is shared between all device instances and can not be changed, the per device data populated in the new device from the template can be edited at will after creation. <br>		These software modules are called templates because they serve as patterns used to add devices. When a new device is added to the system, it is created as an instance of the parent template that defines it, which makes it inherit the data in the template. While some of this is shared between all device instances and can not be changed, the per device data populated in the new device from the template can be edited at will after creation. <br>
	A simple way to understand the concept is by looking at ~~templates~~ as '''~~blueprints~~''', and ~~devices~~ as ~~the buildings~~ made from that blueprint.		A simple way to understand the concept is by looking at a template as a '''blueprint''', and a device as a building made from that blueprint.

	For example, there will only be one Device Template for the "Sony XYZ-123" Television. You, and several other users may have this TV, and each of you will have your own "Device" that you have named, which may have some settings of its own. Everyone can install the "Sony XYZ-123" from the same template, because it is available. The system will detect it, and ask you if you would like to install it in your home. There is only one "Device Template" for that type of device, but there will be as many devices as users have installed. You can install multiple devices of the same kind using the one template that has been developed for it. <br>		For example, there will only be one Device Template for the "Sony XYZ-123" Television. You, and several other users may have this TV, and each of you will have your own "Device" that you have named, which may have some settings of its own. Everyone can install the "Sony XYZ-123" from the same template, because it is available. The system will detect it, and ask you if you would like to install it in your home. There is only one "Device Template" for that type of device, but there will be as many devices as users have installed. You can install multiple devices of the same kind using the one template that has been developed for it. <br>

Mcefan at 06:17, 1 November 2012

2012-11-01T06:17:37Z

←Older revision		Revision as of 06:17, 1 November 2012
Line 13:		Line 13:
	A device template is a definition of everything necessary for a device to operate within a LinuxMCE system. It is a container for all the information that LinuxMCE needs to know about a device. All the data in a template is stored in the database, and queried as needed throughout the system. <br>		A device template is a definition of everything necessary for a device to operate within a LinuxMCE system. It is a container for all the information that LinuxMCE needs to know about a device. All the data in a template is stored in the database, and queried as needed throughout the system. <br>

	In LinuxMCE, a template defines what the device is called, how it relates to other devices in the house, where it should be created on the device tree (its parent), how to find the device (the plug and play information), '''what software package is needed to be installed for it to work''', or what software package contains the software needed to use it, what commands it supports, what events it can emit, etc. <br>		In LinuxMCE, a template defines what the device is called, how it relates to other devices in the house, where it should be created on the device tree (its parent), how to find the device (the plug and play information), '''what software package is needed to be installed for it to work''', or what software package contains the software needed to use it, how to install it, what commands it supports, what events it can emit, how it should interact with messenger, etc. <br>

	{{p}}		{{p}}
Line 20:		Line 20:

	These software modules are called templates because they serve as patterns used to add devices. When a new device is added to the system, it is created as an instance of the parent template that defines it, which makes it inherit the data in the template. While some of this is shared between all device instances and can not be changed, the per device data populated in the new device from the template can be edited at will after creation. <br>		These software modules are called templates because they serve as patterns used to add devices. When a new device is added to the system, it is created as an instance of the parent template that defines it, which makes it inherit the data in the template. While some of this is shared between all device instances and can not be changed, the per device data populated in the new device from the template can be edited at will after creation. <br>
	A simple way to understand the concept is by looking at ~~a template~~ as a '''~~blueprint~~''', and ~~a device~~ as ~~a building~~ made from that blueprint.		A simple way to understand the concept is by looking at templates as '''blueprints''', and devices as the buildings made from that blueprint.

	For example, there will only be one Device Template for the "Sony XYZ-123" Television. You, and several other users may have this TV, and each of you will have your own "Device" that you have named, which may have some settings of its own. Everyone can install the "Sony XYZ-123" from the same template, because it is available. The system will detect it, and ask you if you would like to install it in your home. There is only one "Device Template" for that type of device, but there will be as many devices as users have installed. You can install multiple devices of the same kind using the one template that has been developed for it. <br>		For example, there will only be one Device Template for the "Sony XYZ-123" Television. You, and several other users may have this TV, and each of you will have your own "Device" that you have named, which may have some settings of its own. Everyone can install the "Sony XYZ-123" from the same template, because it is available. The system will detect it, and ask you if you would like to install it in your home. There is only one "Device Template" for that type of device, but there will be as many devices as users have installed. You can install multiple devices of the same kind using the one template that has been developed for it. <br>
Line 72:		Line 72:
	:* the device ID is not in the expected range as decribed above for the MAC address.		:* the device ID is not in the expected range as decribed above for the MAC address.
	:* there are more than one of the same model of device, and the "only one per md" setting is set.		:* there are more than one of the same model of device, and the "only one per md" setting is set.
	:* the radars are not running, or are not running correctly. A radar in LinuxMCE is a process that scans for available resources. Currently, only hard drives and network shares are scanned.		:* the radars are not running, or are not running correctly. A radar in LinuxMCE is a process that scans for available resources. Currently, only hard drives and network shares are scanned. You can see what radars are available by running the command <code>ls /usr/pluto/bin/Radar.sh</code> <br>See [[ssh from windows]] for instructions on using the command prompt.
	:* the device is compatible with LinuxMCE, but no template has been created for it yet.		:* the device is compatible with LinuxMCE, but no template has been created for it yet.
	:* the device is not compatible with LinuxMCE, so no template has been created, nor can be created. the device will not work with LinuxMCE and needs to be replaced with a LinuxMCE compatible device.		:* the device is not compatible with LinuxMCE, so no template has been created, nor can be created. the device will not work with LinuxMCE and needs to be replaced with a LinuxMCE compatible device.
	:* unrelated things, like usb just working under the strain of poll, which should not happen, or any other hardware error.		:* unrelated things, like usb just working under the strain of poll, which should not happen, or any other hardware error.


			;Note: once committed, a template can not be deleted from the system.

			<!--
			{{red}}To use a device template, you simply select it from the list of available templates when creating a device. {{c}}
			-->
	{{p}}		{{p}}

	=Template development=		=Template development=

			Template development is an advanced topic that requires too many skills to be covered in this documentation. It requires and expert level knowledge of the device to add, how it communicates, the protocols it uses, the Linux software it uses, the ability to write drivers, and too many other things to list, all advanced. That is not to say that you can not work with templates at all. If you are willing to do the research, have some time to experiment with the various settings, and feel brave enough to do so, you can help us expand our set of templates.

			Sometimes, you may need to edit a template to add a MAC address or identifier. In the event you need to do so, it is usually very helpful to look at one that performs a function similar to that of the device you are adding, copy the settings, and edit the fields by making some educated guesses, or exploring through trial and error by using a process of elimination. Please beware that changing setting in templates may make the corresponding devices inoperable. Always make note of what you are changing, and why, and keep track of the changes you make in order to be able to revert them in case you break something. A short ink mark lasts longer than a long memory.


	====Making Changes to Templates====		====Making Changes to Templates====
			<!--{{red}}The "My Devices" page... {{c}}-->

	If you make changes to the Device Template, this will affect your local system only. However, if you have fixed some errors, added functionality to an existing Device Template or created your own Device Template, you can use [[sqlCVS]] to merge those changes back into the master database so everyone can benefit from them. The same is true with everything in your local database--the user interface, even the online documentation you are reading now is editable. When you check-in changes using sqlCVS, sqlCVS will isolate those changes and notify the developer who is responsible for quality assurance for that section. Once the developer has confirmed the changes, he can have the changes merged back into LinuxMCE's main development database, which will eventually get propagated to the testing and release databases if the changes pass the tests.		If you make changes to the Device Template, this will affect your local system only. However, if you have fixed some errors, added functionality to an existing Device Template or created your own Device Template, you can use [[sqlCVS]] to merge those changes back into the master database so everyone can benefit from them. The same is true with everything in your local database--the user interface, even the online documentation you are reading now is editable. When you check-in changes using sqlCVS, sqlCVS will isolate those changes and notify the developer who is responsible for quality assurance for that section. Once the developer has confirmed the changes, he can have the changes merged back into LinuxMCE's main development database, which will eventually get propagated to the testing and release databases if the changes pass the tests.