LG 42LB5D - Revision history

RayBe: Added category: GSD

2016-07-07T13:51:45Z

Added category: GSD

←Older revision		Revision as of 13:51, 7 July 2016
Line 3:		Line 3:
	[[Category: Video]]		[[Category: Video]]
	[[Category: Displays]]		[[Category: Displays]]
			[[Category: GSD]]

	{\| align="right"		{\| align="right"

B4rney: /* 'Add Ruby snippets to commands' */

2010-10-04T15:36:51Z

'Add Ruby snippets to commands'

←Older revision		Revision as of 15:36, 4 October 2010
Line 271:		Line 271:
	log('Sending the Following Command: kf 01 '+ilevel.to_s(16)+'\r')		log('Sending the Following Command: kf 01 '+ilevel.to_s(16)+'\r')
	<$"kf 01 "+ilevel.to_s(16)+"\r"$>		<$"kf 01 "+ilevel.to_s(16)+"\r"$>
	SetDeviceDataInDB( device_.devid_, 158, ilevel .to_s)		SetDeviceDataInDB( device_.devid_, 158, ilevel.to_s)
	# 158 = DEVICEDATA_Volume_Level_CONST # "volume and corresponding device data set\n"		# 158 = DEVICEDATA_Volume_Level_CONST # "volume and corresponding device data set\n"
	#90 Vol Down		#90 Vol Down

Zaerc at 16:18, 28 September 2010

2010-09-28T16:18:25Z

←Older revision		Revision as of 16:18, 28 September 2010
Line 1:		Line 1:
			[[Category: Hardware]]
	{{Versioninfo}}		{{Versioninfo}}
	[[Category: Video]]		[[Category: Video]]

Wierdbeard65 at 08:19, 3 May 2010

2010-05-03T08:19:38Z

←Older revision		Revision as of 08:19, 3 May 2010
Line 1:		Line 1:
			{{Versioninfo}}
	[[Category: Video]]		[[Category: Video]]
	[[Category: Displays]]		[[Category: Displays]]

Sedgington at 16:29, 25 March 2010

2010-03-25T16:29:04Z

←Older revision		Revision as of 16:29, 25 March 2010
Line 341:		Line 341:

	/usr/pluto/bin/MessageSend dcerouter -r 0 $1 806 224 $2 13 "$4" 44 1905(this is the template id for the devicetemplate you created above)		/usr/pluto/bin/MessageSend dcerouter -r 0 $1 806 224 $2 13 "$4" 44 1905(this is the template id for the devicetemplate you created above)


			=====================================


			==
			'''== Adapting these instructions for other LG rs232 TVs == =='''



			This seems to be a good template for LG TVs with serial ports. Some of the command need to be changed for later models <$xb 01 90\r$> instead of <$kb 01 07\r$> for inputing HDMI 1 for example, but generally a good guide for adapting it to your TV.

			The major problem is undocumented above but is critical to making this work: You need to look up the device id number of your LG TV from the Wizard \ Devices \ AV Equipment in the upper left hand corner and replace the number "158" in all the scripts above with this number (for example, in my case 310). This allows the script to process successfully.

			Otherwise it will cause a compile error in 7.10 in the "follow log" on the "advanced" link of the A/V device and will not allow your template to run. The compile error will state that it found a "kend" and was expecting "$end".

			The code that breaks it is:

			----------------------------
			#355 Process Initialize
			for iRetry in 0...4
			print "Initializing unit\n"
			conn_.Send("ke 01 01\r") # Send UnMute Command
			buf = conn_.Recv(30,200) # Expected Return # ke 01 01\r\ne 00 OK01x\r\n
			if !buf.nil? && buf.include?("OK")
			print "Initialized ok\n"
			print "Setting volume to 30%\n"
			cmd_313(15)
			SetDeviceDataInDB( device_.devid_, 158, "15" )
			# 158 = DEVICEDATA_Volume_Level_CONST
			return
			end
			print "Failed to initialize. Wait 1 secs and try again\n"
			sleep(1)
			end

			-------------------------------
			which is also necessary for the volume set, volume up and volume down commands the way they are written.
			Carefully replacing "158" with the LG TV device ID number on your setup in the extended editor will make all these commands functional.

			Please note that the description for the plug and play implementation discussed above has not been tested with this fix.

Newacct at 09:56, 2 February 2010

2010-02-02T09:56:45Z

←Older revision		Revision as of 09:56, 2 February 2010
Line 135:		Line 135:
	#350 Process Incoming Data		#350 Process Incoming Data
	buff = ''		buff = ''
	~~while(true)~~		loop do
	buff=conn_.Recv(30,200)		buff=conn_.Recv(30,200)
	if(buff.~~length() == 0)~~		if buff.empty?
	log('Nothing Received')		log('Nothing Received')
	break		break
	end		end
	log('Received: ' + Regexp.escape(buff.to_s))		log('Received: ' + Regexp.escape(buff.to_s))
	if !buff.~~index~~("OK")~~.nil?~~		if buff.include?("OK")
	log(Regexp.escape(buff.to_s) + ': Command Processed Successfully')		log(Regexp.escape(buff.to_s) + ': Command Processed Successfully')
	elsif !buff.~~index~~("NG")~~.nil?~~		elsif buff.include?("NG")
	log(Regexp.escape(buff.to_s) +': Command Processed Unsuccessfully')		log(Regexp.escape(buff.to_s) +': Command Processed Unsuccessfully')
	end		end
Line 153:		Line 153:
	conn_.Send("ke 01 01\r") # Send UnMute Command		conn_.Send("ke 01 01\r") # Send UnMute Command
	buf = conn_.Recv(30,200) # Expected Return # ke 01 01\r\ne 00 OK01x\r\n		buf = conn_.Recv(30,200) # Expected Return # ke 01 01\r\ne 00 OK01x\r\n
	if !buf.nil? && !buf.~~index~~("OK")~~.nil?~~		if !buf.nil? && buf.include?("OK")
	print "Initialized ok\n"		print "Initialized ok\n"
	print "Setting volume to 30%\n"		print "Setting volume to 30%\n"
Line 257:		Line 257:
	Sound & Volume		Sound & Volume
	#97 Mute		#97 Mute
	if(@mute)		if @mute
	<$"ke 01 00\r"$>		<$"ke 01 00\r"$>
	else		else

PeteK: Changed Ruby commands to put log commands and sends on different lines, as putting them on the same line in the Ruby code fields causes errors

2009-11-27T03:36:39Z

Changed Ruby commands to put log commands and sends on different lines, as putting them on the same line in the Ruby code fields causes errors

Show changes

Ray N at 18:48, 13 August 2009

2009-08-13T18:48:50Z

←Older revision		Revision as of 18:48, 13 August 2009
Line 19:		Line 19:
	* A touch blurry with low-end sources ([[S-Video]], RF) like older game systems, but still a fairly good overall picture; I have yet to test other signal methods with my game systems (requires special cables I don't yet have).		* A touch blurry with low-end sources ([[S-Video]], RF) like older game systems, but still a fairly good overall picture; I have yet to test other signal methods with my game systems (requires special cables I don't yet have).
	===Usability===		===Usability===
	* The [[OSD]] [[UI]] and remote are excellent. Both the menus and the buttons are laid out sensibly, and the system incorporates a great idea for settings that are cyclic (most are): the first time you press a button (e.g. [[aspect ratio]]), it brings up an [[OSD]] reminder of the current setting; subsequent presses will cycle through the available options. It's simple, and effective at preventing accidental setting changes by a single inadvertent button press on the remote.		* The [[OSD]] UI and remote are excellent. Both the menus and the buttons are laid out sensibly, and the system incorporates a great idea for settings that are cyclic (most are): the first time you press a button (e.g. [[aspect ratio]]), it brings up an [[OSD]] reminder of the current setting; subsequent presses will cycle through the available options. It's simple, and effective at preventing accidental setting changes by a single inadvertent button press on the remote.
	Resolutions:		Resolutions:
	* 1024x768		* 1024x768

Ray N at 01:28, 11 August 2009

2009-08-11T01:28:33Z

←Older revision		Revision as of 01:28, 11 August 2009
Line 1:		Line 1:
	~~[[Category: Hardware]]~~
	[[Category: Video]]		[[Category: Video]]
	[[Category: Displays]]		[[Category: Displays]]

Rwilson131: add more information

2008-02-24T19:20:18Z

add more information

Show changes