Generic Serial Device - Revision history

RayBe: Added category: GSD

2016-07-03T10:40:10Z

Added category: GSD

←Older revision		Revision as of 10:40, 3 July 2016
Line 2:		Line 2:
	\| __TOC__		\| __TOC__
	\|}		\|}
			[[Category: GSD]]
	Generic_Serial_Device (also known as '''GSD''') is a LinuxMCE device that allows end-user to do simple programming for RS232, serial USB (See [[Serial Hack]] for details on getting USB to serial adapters identified properly in the admin panel!) or network connected devices.		Generic_Serial_Device (also known as '''GSD''') is a LinuxMCE device that allows end-user to do simple programming for RS232, serial USB (See [[Serial Hack]] for details on getting USB to serial adapters identified properly in the admin panel!) or network connected devices.
	:Note : The information is not quite complete because I'm not the original author.		:Note : The information is not quite complete because I'm not the original author.

Coley: Undo revision 28675 by AHagerty93 (talk) spam

2011-09-27T13:47:30Z

Undo revision 28675 by AHagerty93 (talk) spam

AHagerty93: None

2011-09-27T08:08:53Z

None

Burgiman at 11:22, 27 January 2010

2010-01-27T11:22:21Z

←Older revision		Revision as of 11:22, 27 January 2010
Line 9:		Line 9:
	The main idea is instead of programming a device in C++, compile, link with proper libraries you can edit (in a webpage) few lines of code in ruby which will be executed when device receives that command. It exports several objects into ruby so you'll have access to devicedata, device hierarchy, established connection and so on.		The main idea is instead of programming a device in C++, compile, link with proper libraries you can edit (in a webpage) few lines of code in ruby which will be executed when device receives that command. It exports several objects into ruby so you'll have access to devicedata, device hierarchy, established connection and so on.

	The ruby code for each device template is stored somewhere in ''InfraredGroup_Command'' table. To edit the code go to Wizard> Devices > Generic_Serial_Devices on [[~~Centersonic Admin Website~~]] website. You have to add a device from a device template in order to see anything in that page.		The ruby code for each device template is stored somewhere in ''InfraredGroup_Command'' table. To edit the code go to Wizard> Devices > Generic_Serial_Devices on [[LinuxMCE-admin]] website. You have to add a device from a device template in order to see anything in that page.

	Select the device, and click "RubyCodes" button to be able to edit code that will be executed.		Select the device, and click "RubyCodes" button to be able to edit code that will be executed.

Burgiman at 11:21, 27 January 2010

2010-01-27T11:21:48Z

←Older revision		Revision as of 11:21, 27 January 2010
Line 2:		Line 2:
	\| __TOC__		\| __TOC__
	\|}		\|}
	~~[[Category: Programmer's Guide]]~~
	~~[[Category: Serial]]~~
	~~[[Category: GSD]]~~

	Generic_Serial_Device (also known as '''GSD''') is a LinuxMCE device that allows end-user to do simple programming for RS232, serial USB (See [[Serial Hack]] for details on getting USB to serial adapters identified properly in the admin panel!) or network connected devices.		Generic_Serial_Device (also known as '''GSD''') is a LinuxMCE device that allows end-user to do simple programming for RS232, serial USB (See [[Serial Hack]] for details on getting USB to serial adapters identified properly in the admin panel!) or network connected devices.
	:Note : The information is not quite complete because I'm not the original author.		:Note : The information is not quite complete because I'm not the original author.
Line 13:		Line 9:
	The main idea is instead of programming a device in C++, compile, link with proper libraries you can edit (in a webpage) few lines of code in ruby which will be executed when device receives that command. It exports several objects into ruby so you'll have access to devicedata, device hierarchy, established connection and so on.		The main idea is instead of programming a device in C++, compile, link with proper libraries you can edit (in a webpage) few lines of code in ruby which will be executed when device receives that command. It exports several objects into ruby so you'll have access to devicedata, device hierarchy, established connection and so on.

	The ruby code for each device template is stored somewhere in ''InfraredGroup_Command'' table. To edit the code go to Wizard> Devices > Generic_Serial_Devices on [[~~LinuxMCE-admin~~]] website. You have to add a device from a device template in order to see anything in that page.		The ruby code for each device template is stored somewhere in ''InfraredGroup_Command'' table. To edit the code go to Wizard> Devices > Generic_Serial_Devices on [[Centersonic Admin Website]] website. You have to add a device from a device template in order to see anything in that page.

	Select the device, and click "RubyCodes" button to be able to edit code that will be executed.		Select the device, and click "RubyCodes" button to be able to edit code that will be executed.
Line 176:		Line 172:
	* [[Serial Hack]] - A quick and dirty hack to fix the USB to Serial adapter problem! (Device not showing the correct block device on the admin panel)		* [[Serial Hack]] - A quick and dirty hack to fix the USB to Serial adapter problem! (Device not showing the correct block device on the admin panel)
	* [[How to add your own GSD device]]		* [[How to add your own GSD device]]

			[[Category: Programmer's Guide]]

Newacct at 08:44, 27 January 2010

2010-01-27T08:44:25Z

←Older revision		Revision as of 08:44, 27 January 2010
Line 119:		Line 119:
	11:		11:
	12:fix_path=device_.devdata_[2];		12:fix_path=device_.devdata_[2];
	13:fix_path='/'+fix_path if(fix_path[0]!='/'[0]);		13:fix_path='/'+fix_path if fix_path[0]!='/'[0];
	14:		14:
	15:s = "GET "+fix_path+" HTTP/1.0\r\n"		15:s = "GET "+fix_path+" HTTP/1.0\r\n"
Line 128:		Line 128:
	20:conn_.Send(s)		20:conn_.Send(s)
	21:recv=""		21:recv=""
	22:~~while(true)~~		22:loop {
	23: buff=conn_.Recv(16384, 5000)		23: buff=conn_.Recv(16384, 5000)
	24: if(buff.~~length() == 0)~~		24: if buff.empty?
	25: break		25: break
	26: end		26: end
	27: recv = ~~recv +~~ buff		27: recv += buff
	28:~~end~~		28:}
	29:if (recv=~ /^HTTP[^\r\n]+200\sOK.+?\r\n\r\n(.+)$/m)		29:if recv=~ /^HTTP[^\r\n]+200\sOK.+?\r\n\r\n(.+)$/m
	30: data_set($1)		30: data_set($1)
	31: format_set('jpg')		31: format_set('jpg')

Ray N at 01:14, 11 August 2009

2009-08-11T01:14:27Z

←Older revision		Revision as of 01:14, 11 August 2009
Line 4:		Line 4:
	[[Category: Programmer's Guide]]		[[Category: Programmer's Guide]]
	[[Category: Serial]]		[[Category: Serial]]
	~~[[Category: LinuxMCE_Devices]]~~
	[[Category: GSD]]		[[Category: GSD]]

Rwilson131 at 17:34, 29 November 2008

2008-11-29T17:34:34Z

←Older revision		Revision as of 17:34, 29 November 2008
Line 1:		Line 1:
			{\| align="right"
			\| __TOC__
			\|}
	[[Category: Programmer's Guide]]		[[Category: Programmer's Guide]]
	[[Category: Serial]]		[[Category: Serial]]

Zaerc: moved categories

2007-10-05T12:27:33Z

moved categories

@@ Line 1: / Line 1: @@
 Generic_Serial_Device (also known as '''GSD''') is a LinuxMCE device that allows end-user to do simple programming for RS232, serial USB (See [[Serial Hack]] for details on getting USB to serial adapters identified properly in the admin panel!) or network connected devices.
 :Note : The information is not quite complete because I'm not the original author.
@@ Line 169: / Line 174: @@
 * [[Serial Hack]] - A quick and dirty hack to fix the USB to Serial adapter problem! (Device not showing the correct block device on the admin panel)
 * [[How to add your own GSD device]]

Trout: /* Useful Pages */

2007-09-29T11:46:05Z

Useful Pages

←Older revision		Revision as of 11:46, 29 September 2007
Line 168:		Line 168:
	== Useful Pages ==		== Useful Pages ==
	* [[Serial Hack]] - A quick and dirty hack to fix the USB to Serial adapter problem! (Device not showing the correct block device on the admin panel)		* [[Serial Hack]] - A quick and dirty hack to fix the USB to Serial adapter problem! (Device not showing the correct block device on the admin panel)
			* [[How to add your own GSD device]]

	[[Category: GSD]]		[[Category: GSD]]
	[[Category: LinuxMCE_Devices]]		[[Category: LinuxMCE_Devices]]
	[[Category: Programmer's Guide]]		[[Category: Programmer's Guide]]

←Older revision		Revision as of 13:47, 27 September 2011
Line 21:		Line 21:
	* standard ruby code (check [http://www.ruby-lang.org/en/] and [http://poignantguide.net/ruby/] for syntax, references and programming guides)		* standard ruby code (check [http://www.ruby-lang.org/en/] and [http://poignantguide.net/ruby/] for syntax, references and programming guides)
	* short form for '''conn_.Send'''		* short form for '''conn_.Send'''
	~~<~~$"PWON\r"$>		<$"PWON\r"$>
	:which simply will send the string ''"PWON\r"'' to device.		:which simply will send the string ''"PWON\r"'' to device.

Line 31:		Line 31:

	require 'Ruby_Generic_Serial_Device'		require 'Ruby_Generic_Serial_Device'
	class Command ~~<~~ Ruby_Generic_Serial_Device::RubyCommandWrapper		class Command < Ruby_Generic_Serial_Device::RubyCommandWrapper
	end		end
	class Device_DevID ~~<~~ Ruby_Generic_Serial_Device::RubySerialWrapper		class Device_DevID < Ruby_Generic_Serial_Device::RubySerialWrapper
	def cmd_CmdID1(paramlist)		def cmd_CmdID1(paramlist)
	@returnParamArray.clear		@returnParamArray.clear
Line 66:		Line 66:
	=== Command details ===		=== Command details ===
	When the command from DCE arrives it is routed to specific device and ''cmd_XXX'' is run. The commands are run one by one, meaning that you cannot run 2 commands simultaneously. This limitation is implied by embedded ruby interpretor which fails if run from multiple threads.		When the command from DCE arrives it is routed to specific device and ''cmd_XXX'' is run. The commands are run one by one, meaning that you cannot run 2 commands simultaneously. This limitation is implied by embedded ruby interpretor which fails if run from multiple threads.
	DCE commands may have return parameters (well known GetVideoFrame), as ruby can return only 1 parameter the ''@returnParamArray'' <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/">child carrier</span>]</span> was added. You can see that in each method we insert '''@returnParamArray.clear''' then the real code and then '''return @returnParamArray'''. Also some setters are generated (like the one from above) for code readability.		DCE commands may have return parameters (well known GetVideoFrame), as ruby can return only 1 parameter the ''@returnParamArray'' was added. You can see that in each method we insert '''@returnParamArray.clear''' then the real code and then '''return @returnParamArray'''. Also some setters are generated (like the one from above) for code readability.

	Beside usual DCE command you'll see some ''Internal Commands''. Here goes a small list and what they do:		Beside usual DCE command you'll see some ''Internal Commands''. Here goes a small list and what they do:
Line 103:		Line 103:
	Here is a short example from ''Panasonic IP Camera'':		Here is a short example from ''Panasonic IP Camera'':
	0:require 'Ruby_Generic_Serial_Device'		0:require 'Ruby_Generic_Serial_Device'
	1:class Command ~~<~~ Ruby_Generic_Serial_Device::RubyCommandWrapper		1:class Command < Ruby_Generic_Serial_Device::RubyCommandWrapper
	2:end		2:end
	3:class Device_47 ~~<~~ Ruby_Generic_Serial_Device::RubySerialWrapper		3:class Device_47 < Ruby_Generic_Serial_Device::RubySerialWrapper
	4:#### 84 ####################################################################		4:#### 84 ####################################################################
	5:def cmd_84(data, format, disable_aspect_lock, streamid, width, height)		5:def cmd_84(data, format, disable_aspect_lock, streamid, width, height)

←Older revision		Revision as of 08:08, 27 September 2011
Line 21:		Line 21:
	* standard ruby code (check [http://www.ruby-lang.org/en/] and [http://poignantguide.net/ruby/] for syntax, references and programming guides)		* standard ruby code (check [http://www.ruby-lang.org/en/] and [http://poignantguide.net/ruby/] for syntax, references and programming guides)
	* short form for '''conn_.Send'''		* short form for '''conn_.Send'''
	<$"PWON\r"$>		<$"PWON\r"$>
	:which simply will send the string ''"PWON\r"'' to device.		:which simply will send the string ''"PWON\r"'' to device.

Line 31:		Line 31:

	require 'Ruby_Generic_Serial_Device'		require 'Ruby_Generic_Serial_Device'
	class Command < Ruby_Generic_Serial_Device::RubyCommandWrapper		class Command < Ruby_Generic_Serial_Device::RubyCommandWrapper
	end		end
	class Device_DevID < Ruby_Generic_Serial_Device::RubySerialWrapper		class Device_DevID < Ruby_Generic_Serial_Device::RubySerialWrapper
	def cmd_CmdID1(paramlist)		def cmd_CmdID1(paramlist)
	@returnParamArray.clear		@returnParamArray.clear
Line 66:		Line 66:
	=== Command details ===		=== Command details ===
	When the command from DCE arrives it is routed to specific device and ''cmd_XXX'' is run. The commands are run one by one, meaning that you cannot run 2 commands simultaneously. This limitation is implied by embedded ruby interpretor which fails if run from multiple threads.		When the command from DCE arrives it is routed to specific device and ''cmd_XXX'' is run. The commands are run one by one, meaning that you cannot run 2 commands simultaneously. This limitation is implied by embedded ruby interpretor which fails if run from multiple threads.
	DCE commands may have return parameters (well known GetVideoFrame), as ruby can return only 1 parameter the ''@returnParamArray'' was added. You can see that in each method we insert '''@returnParamArray.clear''' then the real code and then '''return @returnParamArray'''. Also some setters are generated (like the one from above) for code readability.		DCE commands may have return parameters (well known GetVideoFrame), as ruby can return only 1 parameter the ''@returnParamArray'' <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/">child carrier</span>]</span> was added. You can see that in each method we insert '''@returnParamArray.clear''' then the real code and then '''return @returnParamArray'''. Also some setters are generated (like the one from above) for code readability.

	Beside usual DCE command you'll see some ''Internal Commands''. Here goes a small list and what they do:		Beside usual DCE command you'll see some ''Internal Commands''. Here goes a small list and what they do:
Line 103:		Line 103:
	Here is a short example from ''Panasonic IP Camera'':		Here is a short example from ''Panasonic IP Camera'':
	0:require 'Ruby_Generic_Serial_Device'		0:require 'Ruby_Generic_Serial_Device'
	1:class Command < Ruby_Generic_Serial_Device::RubyCommandWrapper		1:class Command < Ruby_Generic_Serial_Device::RubyCommandWrapper
	2:end		2:end
	3:class Device_47 < Ruby_Generic_Serial_Device::RubySerialWrapper		3:class Device_47 < Ruby_Generic_Serial_Device::RubySerialWrapper
	4:#### 84 ####################################################################		4:#### 84 ####################################################################
	5:def cmd_84(data, format, disable_aspect_lock, streamid, width, height)		5:def cmd_84(data, format, disable_aspect_lock, streamid, width, height)