Edit Device Template - Revision history

Marie.o: /* Configuration script */

2014-04-10T13:34:42Z

Configuration script

←Older revision		Revision as of 13:34, 10 April 2014
Line 59:		Line 59:
	-i <ip-address> # The IP address for the new device		-i <ip-address> # The IP address for the new device
	-m <mac-address> # The MAC address for the new device		-m <mac-address> # The MAC address for the new device

			If "Device needs reconfiguring" is ticked, Config_Device_Changes.sh runs the script mentioned here. Config_Device_Changes.sh runs on every router reload.

	====Comments====		====Comments====

Marie.o: /* Command line */

2014-04-10T09:35:04Z

Command line

←Older revision		Revision as of 09:35, 10 April 2014
Line 19:		Line 19:

	====Command line====		====Command line====
			The name of the binary located in /usr/pluto/bin that the Launch_Manager will try to start in a screen session.

	====Device Category====		====Device Category====

RayBe at 19:05, 23 January 2014

2014-01-23T19:05:35Z

←Older revision		Revision as of 19:05, 23 January 2014
Line 69:		Line 69:
	If this device can be controlled via infrared, the infrared code for each command will need to be stored or learned. The number of different models for A/V equipment is staggering. However most manufacturers always use the same infrared codes across their whole line. For example, a Sony remote control for 1 TV will control all other Sony TV's too. So rather than requiring the user to add infrared codes for every Sony TV, we just create an infrared group "Sony TV Commands". Then you can add the DCE Command to Infrared Code commands to the group. Later when someone else adds a Device Template for another model of Sony TV, they can just specify that it uses the same Infrared Group. Note that the infrared group should therefore be a superset of all the commands--every command for every Sony TV. Some high-end models may have commands like "Wide screen" vs "Normal", which the low-end models do not support. In this case, the high-end model may have more commands than the low-end model, but all the commands should be in the infrared group. The low-end model will never use the infrared codes that it doesn't support, but at least they will be there and different infrared groups will not be required. When the manufacturer changes the infrared codes their, then a new infrared group will be required.		If this device can be controlled via infrared, the infrared code for each command will need to be stored or learned. The number of different models for A/V equipment is staggering. However most manufacturers always use the same infrared codes across their whole line. For example, a Sony remote control for 1 TV will control all other Sony TV's too. So rather than requiring the user to add infrared codes for every Sony TV, we just create an infrared group "Sony TV Commands". Then you can add the DCE Command to Infrared Code commands to the group. Later when someone else adds a Device Template for another model of Sony TV, they can just specify that it uses the same Infrared Group. Note that the infrared group should therefore be a superset of all the commands--every command for every Sony TV. Some high-end models may have commands like "Wide screen" vs "Normal", which the low-end models do not support. In this case, the high-end model may have more commands than the low-end model, but all the commands should be in the infrared group. The low-end model will never use the infrared codes that it doesn't support, but at least they will be there and different infrared groups will not be required. When the manufacturer changes the infrared codes their, then a new infrared group will be required.

	Places to get the commands for your device:		Places to get the commands for your device:<br/>
	[http://www.remotecentral.com Remote Central]		[http://www.remotecentral.com Remote Central]<br/>
	[http://www.awe-europe.com/ir_232.html Awe Europe]		[http://www.awe-europe.com/ir_232.html Awe Europe]

RayBe: added hyperlinks for device command lookup

2014-01-23T19:01:36Z

added hyperlinks for device command lookup

←Older revision		Revision as of 19:01, 23 January 2014
Line 68:		Line 68:

	If this device can be controlled via infrared, the infrared code for each command will need to be stored or learned. The number of different models for A/V equipment is staggering. However most manufacturers always use the same infrared codes across their whole line. For example, a Sony remote control for 1 TV will control all other Sony TV's too. So rather than requiring the user to add infrared codes for every Sony TV, we just create an infrared group "Sony TV Commands". Then you can add the DCE Command to Infrared Code commands to the group. Later when someone else adds a Device Template for another model of Sony TV, they can just specify that it uses the same Infrared Group. Note that the infrared group should therefore be a superset of all the commands--every command for every Sony TV. Some high-end models may have commands like "Wide screen" vs "Normal", which the low-end models do not support. In this case, the high-end model may have more commands than the low-end model, but all the commands should be in the infrared group. The low-end model will never use the infrared codes that it doesn't support, but at least they will be there and different infrared groups will not be required. When the manufacturer changes the infrared codes their, then a new infrared group will be required.		If this device can be controlled via infrared, the infrared code for each command will need to be stored or learned. The number of different models for A/V equipment is staggering. However most manufacturers always use the same infrared codes across their whole line. For example, a Sony remote control for 1 TV will control all other Sony TV's too. So rather than requiring the user to add infrared codes for every Sony TV, we just create an infrared group "Sony TV Commands". Then you can add the DCE Command to Infrared Code commands to the group. Later when someone else adds a Device Template for another model of Sony TV, they can just specify that it uses the same Infrared Group. Note that the infrared group should therefore be a superset of all the commands--every command for every Sony TV. Some high-end models may have commands like "Wide screen" vs "Normal", which the low-end models do not support. In this case, the high-end model may have more commands than the low-end model, but all the commands should be in the infrared group. The low-end model will never use the infrared codes that it doesn't support, but at least they will be there and different infrared groups will not be required. When the manufacturer changes the infrared codes their, then a new infrared group will be required.

			Places to get the commands for your device:
			[http://www.remotecentral.com Remote Central]
			[http://www.awe-europe.com/ir_232.html Awe Europe]

	===Events===		===Events===

Mcefan: /* Range of MAC */

2012-11-01T05:30:47Z

Range of MAC

←Older revision		Revision as of 05:30, 1 November 2012
Line 75:		Line 75:
	===Plug & Play===		===Plug & Play===
	====Range of MAC====		====Range of MAC====
	The MAC range is ~~needed~~ to ~~detect~~ Plug and Play devices on the network. ~~The numbers are decimals~~, ~~calculated using~~ the /usr/pluto/bin/convert_mac. If the mac address is 00:01:02:03:04:05 ~~of a specific hardware~~, it is ~~quite~~ likely that all devices that start with 00:01:02:03 are part of the same product.		The MAC range is used to implement Plug and Play as devices appear on the network. However, instead of the regular column separated groups of digits, LinuxMCE uses the decimal value of a MAC address. A script has been provided to aid in the conversion of the MAC address from hexadecimal to decimal. Run the <code>/usr/pluto/bin/convert_mac</code> script on your core, and copy the resulting number to your template. <br>
	/usr/pluto/bin/convert_mac 00:01:02:03:00:00
	/usr/pluto/bin/convert_mac 00:01:02:03:FF:FF		If the mac address for your specific hardware is 00:01:02:03:''04:05'', it is likely that all devices that start with 00:01:02:03 are part of the same product. To find the upper and lower limits of the range, run
	~~will give you the upper and lower limit to be entered.~~		:<code>/usr/pluto/bin/convert_mac 00:01:02:03:'''00:00''' </code>
			:<code>/usr/pluto/bin/convert_mac 00:01:02:03:'''FF:FF''' </code>

			{{p}}

	====Vendor Model ID====		====Vendor Model ID====
	The vendor model ID is the PCI ID of the device in question. vendor_id plus product_id. If the PCI card has subvendor and subproduct id, add those too.		The vendor model ID is the PCI ID of the device in question. vendor_id plus product_id. If the PCI card has subvendor and subproduct id, add those too.

Coley: Undo revision 28689 by AHagerty93 (talk) spam

2011-09-27T13:55:23Z

Undo revision 28689 by AHagerty93 (talk) spam

←Older revision		Revision as of 13:55, 27 September 2011
Line 55:		Line 55:

	If the device is detected, the script is being called using the following parameters		If the device is detected, the script is being called using the following parameters
	-d ~~<~~device-id> # The device ID for the new device		-d <device-id> # The device ID for the new device
	-i ~~<~~ip-address> # The IP address for the new device		-i <ip-address> # The IP address for the new device
	-m ~~<~~mac-address> # The MAC address for the new device		-m <mac-address> # The MAC address for the new device

	====Comments====		====Comments====

	===Device data===		===Device data===
	When you specify what '''data parameters''' this device needs, try to use one of the existing data parameters in the list if there is an appropriate one. Which one you choose is unimportant so long as the type is correct (string, integer, etc.). DCE makes no differentiation between the parameters--they are just names. If this device implements DCE, then DCEGen will create member variables for <span class="plainlinks">[http://www.thepiggybackrider.com/ <span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;/CITATION/">kid carrier</span>]</span> setting/accessing all the data parameters for your device, and the names of the members and functions will be the same as the name on the list. Also, when the user adds an instance of this device to his system, either manually or with the wizard, he will be able to fill in a value for this parameter if you check "Allowed to Modify". If you check "Required", then some value will be required and the parameter cannot be empty. If you check "Use Device Template Default", then whatever value you put in here as the default will be used by every device. Note that if you put in a default value, do not check "Allowed to Modify", then the device will be created with the default value. However, if you later change the default value, all the devices values will not change unless you check this "Use Device Template Default" box. In that case, the device really has no local value and just uses the current default every time. If "Set by Device" is checked, then when the DCE class is generated a "set" methods will also be created so the device can set the value itself. Otherwise the data parameter is considered 'read-only' by the device and can only be changed using the .		When you specify what '''data parameters''' this device needs, try to use one of the existing data parameters in the list if there is an appropriate one. Which one you choose is unimportant so long as the type is correct (string, integer, etc.). DCE makes no differentiation between the parameters--they are just names. If this device implements DCE, then DCEGen will create member variables for setting/accessing all the data parameters for your device, and the names of the members and functions will be the same as the name on the list. Also, when the user adds an instance of this device to his system, either manually or with the wizard, he will be able to fill in a value for this parameter if you check "Allowed to Modify". If you check "Required", then some value will be required and the parameter cannot be empty. If you check "Use Device Template Default", then whatever value you put in here as the default will be used by every device. Note that if you put in a default value, do not check "Allowed to Modify", then the device will be created with the default value. However, if you later change the default value, all the devices values will not change unless you check this "Use Device Template Default" box. In that case, the device really has no local value and just uses the current default every time. If "Set by Device" is checked, then when the DCE class is generated a "set" methods will also be created so the device can set the value itself. Otherwise the data parameter is considered 'read-only' by the device and can only be changed using the [[LinuxMCE Admin Website]].

	===Commands===		===Commands===
Line 73:		Line 73:


	===Plug &~~amp;~~ Play===		===Plug & Play===
	====Range of MAC====		====Range of MAC====
	The MAC range is needed to detect Plug and Play devices on the network. The numbers are decimals, calculated using the /usr/pluto/bin/convert_mac. If the mac address is 00:01:02:03:04:05 of a specific hardware, it is quite likely that all devices that start with 00:01:02:03 are part of the same product.		The MAC range is needed to detect Plug and Play devices on the network. The numbers are decimals, calculated using the /usr/pluto/bin/convert_mac. If the mac address is 00:01:02:03:04:05 of a specific hardware, it is quite likely that all devices that start with 00:01:02:03 are part of the same product.

AHagerty93: None

2011-09-27T08:13:29Z

None

←Older revision		Revision as of 08:13, 27 September 2011
Line 55:		Line 55:

	If the device is detected, the script is being called using the following parameters		If the device is detected, the script is being called using the following parameters
	-d <device-id> # The device ID for the new device		-d <device-id> # The device ID for the new device
	-i <ip-address> # The IP address for the new device		-i <ip-address> # The IP address for the new device
	-m <mac-address> # The MAC address for the new device		-m <mac-address> # The MAC address for the new device

	====Comments====		====Comments====

	===Device data===		===Device data===
	When you specify what '''data parameters''' this device needs, try to use one of the existing data parameters in the list if there is an appropriate one. Which one you choose is unimportant so long as the type is correct (string, integer, etc.). DCE makes no differentiation between the parameters--they are just names. If this device implements DCE, then DCEGen will create member variables for setting/accessing all the data parameters for your device, and the names of the members and functions will be the same as the name on the list. Also, when the user adds an instance of this device to his system, either manually or with the wizard, he will be able to fill in a value for this parameter if you check "Allowed to Modify". If you check "Required", then some value will be required and the parameter cannot be empty. If you check "Use Device Template Default", then whatever value you put in here as the default will be used by every device. Note that if you put in a default value, do not check "Allowed to Modify", then the device will be created with the default value. However, if you later change the default value, all the devices values will not change unless you check this "Use Device Template Default" box. In that case, the device really has no local value and just uses the current default every time. If "Set by Device" is checked, then when the DCE class is generated a "set" methods will also be created so the device can set the value itself. Otherwise the data parameter is considered 'read-only' by the device and can only be changed using the ~~[[LinuxMCE Admin Website]]~~.		When you specify what '''data parameters''' this device needs, try to use one of the existing data parameters in the list if there is an appropriate one. Which one you choose is unimportant so long as the type is correct (string, integer, etc.). DCE makes no differentiation between the parameters--they are just names. If this device implements DCE, then DCEGen will create member variables for <span class="plainlinks">[http://www.thepiggybackrider.com/ <span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;/CITATION/">kid carrier</span>]</span> setting/accessing all the data parameters for your device, and the names of the members and functions will be the same as the name on the list. Also, when the user adds an instance of this device to his system, either manually or with the wizard, he will be able to fill in a value for this parameter if you check "Allowed to Modify". If you check "Required", then some value will be required and the parameter cannot be empty. If you check "Use Device Template Default", then whatever value you put in here as the default will be used by every device. Note that if you put in a default value, do not check "Allowed to Modify", then the device will be created with the default value. However, if you later change the default value, all the devices values will not change unless you check this "Use Device Template Default" box. In that case, the device really has no local value and just uses the current default every time. If "Set by Device" is checked, then when the DCE class is generated a "set" methods will also be created so the device can set the value itself. Otherwise the data parameter is considered 'read-only' by the device and can only be changed using the .

	===Commands===		===Commands===
Line 73:		Line 73:


	===Plug & Play===		===Plug & Play===
	====Range of MAC====		====Range of MAC====
	The MAC range is needed to detect Plug and Play devices on the network. The numbers are decimals, calculated using the /usr/pluto/bin/convert_mac. If the mac address is 00:01:02:03:04:05 of a specific hardware, it is quite likely that all devices that start with 00:01:02:03 are part of the same product.		The MAC range is needed to detect Plug and Play devices on the network. The numbers are decimals, calculated using the /usr/pluto/bin/convert_mac. If the mac address is 00:01:02:03:04:05 of a specific hardware, it is quite likely that all devices that start with 00:01:02:03 are part of the same product.

Sambuca: /* Commands */ Remove spam

2010-11-07T12:48:50Z

Commands: Remove spam

←Older revision		Revision as of 12:48, 7 November 2010
Line 65:		Line 65:

	===Commands===		===Commands===
	Because most devices implement lots of '''commands''', and similar devices will always implement similar commands, commands are put into groups and the groups are added to the device template rather than adding the commands manually. A TV, for example, can have 100 "standard" commands--like Volume Up/Down, Channel Up/Down, On/Off, Brightness Up, etc. Rather than having to add every basic ~~[http://www.bestessay.org bestessays]~~ command to every TV, a group called "Standard TV commands" can be created, and you just add the group to the TV. Command Groups use the same categories as the device template themselves. By default, you will only see here the command groups within the same category as the device template to keep the screen clean. Just check the command groups you want. However, there is a pull-down listing every single command group so you can add command groups that are not in the same category. You can also create a new command group and then specify what commands belong to that group. When you create or edit a command group you will have the option of creating/editing the commands, and there you will be able to specify what parameters that command takes.		Because most devices implement lots of '''commands''', and similar devices will always implement similar commands, commands are put into groups and the groups are added to the device template rather than adding the commands manually. A TV, for example, can have 100 "standard" commands--like Volume Up/Down, Channel Up/Down, On/Off, Brightness Up, etc. Rather than having to add every basic command to every TV, a group called "Standard TV commands" can be created, and you just add the group to the TV. Command Groups use the same categories as the device template themselves. By default, you will only see here the command groups within the same category as the device template to keep the screen clean. Just check the command groups you want. However, there is a pull-down listing every single command group so you can add command groups that are not in the same category. You can also create a new command group and then specify what commands belong to that group. When you create or edit a command group you will have the option of creating/editing the commands, and there you will be able to specify what parameters that command takes.

	If this device can be controlled via infrared, the infrared code for each command will need to be stored or learned. The number of different models for A/V equipment is staggering. However most manufacturers always use the same infrared codes across their whole line. For example, a Sony remote control for 1 TV will control all other Sony TV's too. So rather than requiring the user to add infrared codes for every Sony TV, we just create an infrared group "Sony TV Commands". Then you can add the DCE Command to Infrared Code commands to the group. Later when someone else adds a Device Template for another model of Sony TV, they can just specify that it uses the same Infrared Group. Note that the infrared group should therefore be a superset of all the commands--every command for every Sony TV. Some high-end models may have commands like "Wide screen" vs "Normal", which the low-end models do not support. In this case, the high-end model may have more commands than the low-end model, but all the commands should be in the infrared group. The low-end model will never use the infrared codes that it doesn't support, but at least they will be there and different infrared groups will not be required. When the manufacturer changes the infrared codes their, then a new infrared group will be required.		If this device can be controlled via infrared, the infrared code for each command will need to be stored or learned. The number of different models for A/V equipment is staggering. However most manufacturers always use the same infrared codes across their whole line. For example, a Sony remote control for 1 TV will control all other Sony TV's too. So rather than requiring the user to add infrared codes for every Sony TV, we just create an infrared group "Sony TV Commands". Then you can add the DCE Command to Infrared Code commands to the group. Later when someone else adds a Device Template for another model of Sony TV, they can just specify that it uses the same Infrared Group. Note that the infrared group should therefore be a superset of all the commands--every command for every Sony TV. Some high-end models may have commands like "Wide screen" vs "Normal", which the low-end models do not support. In this case, the high-end model may have more commands than the low-end model, but all the commands should be in the infrared group. The low-end model will never use the infrared codes that it doesn't support, but at least they will be there and different infrared groups will not be required. When the manufacturer changes the infrared codes their, then a new infrared group will be required.

ChloeGunn: /* Commands */

2009-12-29T15:10:50Z

Commands

←Older revision		Revision as of 15:10, 29 December 2009
Line 65:		Line 65:

	===Commands===		===Commands===
	Because most devices implement lots of '''commands''', and similar devices will always implement similar commands, commands are put into groups and the groups are added to the device template rather than adding the commands manually. A TV, for example, can have 100 "standard" commands--like Volume Up/Down, Channel Up/Down, On/Off, Brightness Up, etc. Rather than having to add every command to every TV, a group called "Standard TV commands" can be created, and you just add the group to the TV. Command Groups use the same categories as the device template themselves. By default, you will only see here the command groups within the same category as the device template to keep the screen clean. Just check the command groups you want. However, there is a pull-down listing every single command group so you can add command groups that are not in the same category. You can also create a new command group and then specify what commands belong to that group. When you create or edit a command group you will have the option of creating/editing the commands, and there you will be able to specify what parameters that command takes.		Because most devices implement lots of '''commands''', and similar devices will always implement similar commands, commands are put into groups and the groups are added to the device template rather than adding the commands manually. A TV, for example, can have 100 "standard" commands--like Volume Up/Down, Channel Up/Down, On/Off, Brightness Up, etc. Rather than having to add every basic [http://www.bestessay.org bestessays] command to every TV, a group called "Standard TV commands" can be created, and you just add the group to the TV. Command Groups use the same categories as the device template themselves. By default, you will only see here the command groups within the same category as the device template to keep the screen clean. Just check the command groups you want. However, there is a pull-down listing every single command group so you can add command groups that are not in the same category. You can also create a new command group and then specify what commands belong to that group. When you create or edit a command group you will have the option of creating/editing the commands, and there you will be able to specify what parameters that command takes.

	If this device can be controlled via infrared, the infrared code for each command will need to be stored or learned. The number of different models for A/V equipment is staggering. However most manufacturers always use the same infrared codes across their whole line. For example, a Sony remote control for 1 TV will control all other Sony TV's too. So rather than requiring the user to add infrared codes for every Sony TV, we just create an infrared group "Sony TV Commands". Then you can add the DCE Command to Infrared Code commands to the group. Later when someone else adds a Device Template for another model of Sony TV, they can just specify that it uses the same Infrared Group. Note that the infrared group should therefore be a superset of all the commands--every command for every Sony TV. Some high-end models may have commands like "Wide screen" vs "Normal", which the low-end models do not support. In this case, the high-end model may have more commands than the low-end model, but all the commands should be in the infrared group. The low-end model will never use the infrared codes that it doesn't support, but at least they will be there and different infrared groups will not be required. When the manufacturer changes the infrared codes their, then a new infrared group will be required.		If this device can be controlled via infrared, the infrared code for each command will need to be stored or learned. The number of different models for A/V equipment is staggering. However most manufacturers always use the same infrared codes across their whole line. For example, a Sony remote control for 1 TV will control all other Sony TV's too. So rather than requiring the user to add infrared codes for every Sony TV, we just create an infrared group "Sony TV Commands". Then you can add the DCE Command to Infrared Code commands to the group. Later when someone else adds a Device Template for another model of Sony TV, they can just specify that it uses the same Infrared Group. Note that the infrared group should therefore be a superset of all the commands--every command for every Sony TV. Some high-end models may have commands like "Wide screen" vs "Normal", which the low-end models do not support. In this case, the high-end model may have more commands than the low-end model, but all the commands should be in the infrared group. The low-end model will never use the infrared codes that it doesn't support, but at least they will be there and different infrared groups will not be required. When the manufacturer changes the infrared codes their, then a new infrared group will be required.

Marie.o: /* Configuration script */

2009-12-21T08:27:28Z

Configuration script

←Older revision		Revision as of 08:27, 21 December 2009
Line 52:		Line 52:
	====Comm Method====		====Comm Method====
	====Configuration script====		====Configuration script====
	The configuration script is run until it successfully exits. It is run to setup a device initially, like setting up an extension for a new IP phone.		The configuration script is run until it successfully exits. It is run to setup a device initially, like setting up an extension for a new IP phone. It must exist in /usr/pluto/bin.

	If the device is detected ~~based on the MAC address range~~, the script is being called using the following parameters		If the device is detected, the script is being called using the following parameters
	-d <device-id> # The device ID for the new device		-d <device-id> # The device ID for the new device
	-i <ip-address> # The IP address for the new device		-i <ip-address> # The IP address for the new device