Samsung LCD TV RS232 Protocols

Jorde_VJorde_V UX ScientistPosts: 393
Been trying to find them, have found some. But I'm curious if they also hold true for the LE40A656 series and the LE32A330 series. I've found this protocol posted here by the guy with the One Piece avatar (Luffy), sorry that I don't remember your name :P.

(check attachment)

Comments

  • depsdeps Junior Member Posts: 27
    Are there any way to get feedback from tv? Power state, volume level?

    Thanx
  • cmasoncmason Junior Member Posts: 123
    Jorde_V wrote: »
    Been trying to find them, have found some. But I'm curious if they also hold true for the LE40A656 series and the LE32A330 series. I've found this protocol posted here by the guy with the One Piece avatar (Luffy), sorry that I don't remember your name :P.

    (check attachment)

    I used this spreadsheet to program a Samsung UN40H5203 I bought a month ago.
    I've seen 2 different protocol types for Samsung TVs in my search. The PDF you attached is inline with the attached spreadsheet.
    The spreadsheet is a little more straight forward (and a bit robust).

    I poked around changing just the command byte and found some more updated codes that were not included in the spreadsheet (SMART TV functions and such).
    There were some that I know work for different menus by I really only gleaned these from the main menu screen.
    VOLATILE INTEGER SOURCE_APPS_TOG	=	67	// 08,22,0d,00,00,93,36
    VOLATILE INTEGER SOURCE_APPS_DISCRETE	=	68	// 08,22,0d,00,00,A6,23
    VOLATILE INTEGER SOURCE_SMART_HUB	=	69	// 08,22,0d,00,00,79,50
    VOLATILE INTEGER SOURCE_MEDIA_PLAY	=	70	// 08,22,0d,00,00,8C,3D
    VOLATILE INTEGER SOURCE_SEARCH		=	71	// 08,22,0d,00,00,73,56
    VOLATILE INTEGER SOURCE_WEB_BROWSER	=	72	// 08,22,0d,00,00,37,92
    VOLATILE INTEGER SOURCE_CABLE_TOG	=	73	// 08,22,0d,00,00,36,93
    VOLATILE INTEGER SOURCE_E_MANUAL	=	74	// 08,22,0d,00,00,3F,8A
    VOLATILE INTEGER BUTTON_CAPTION		=	100	// 08,22,0d,00,00,25,A4
    VOLATILE INTEGER BUTTON_TOOLS		=	119	// 08,22,0d,00,00,4B,7E
    VOLATILE INTEGER BUTTON_KEYPAD		=	120	// 08,22,0d,00,00,D2,F7
    VOLATILE INTEGER BUTTON_PIC_MODE	=	121	// 08,22,0d,00,00,28,A1
    VOLATILE INTEGER BUTTON_PIC_SIZE	=	122	// 08,22,0d,00,00,3E,8B
    VOLATILE INTEGER BUTTON_ENERGY_SAVE	=	123	// 08,22,0d,00,00,77,52
    VOLATILE INTEGER BUTTON_CLOCK_SET	=	124	// 08,22,0d,00,00,87,42
    
    VOLATILE INTEGER TEST_CODE		=	236
    VOLATILE INTEGER TEST_CODE_UP		=	237
    VOLATILE INTEGER TEST_CODE_DN		=	238
    
    (* Other Codes that I found -
    VOLATILE INTEGER SOURCE_PWR_OFF		=	0	// 08,22,0d,00,00,02,C7
    VOLATILE INTEGER SOURCE_MENU		=	0	// 08,22,0d,00,00,1A,AF
    VOLATILE INTEGER SOURCE_INFO		=	0	// 08,22,0d,00,00,E9,E0
    VOLATILE INTEGER SOURCE_TV		=	0	// 08,22,0d,00,00,1B,AE
    VOLATILE INTEGER SOURCE_HDMI1		=	0	// 08,22,0d,00,00,03,C6
    VOLATILE INTEGER SOURCE_HDMI2		=	0	// 08,22,0d,00,00,BE,0B
    VOLATILE INTEGER SOURCE_COMPONENT	=	0	// 08,22,0d,00,00,86,43
    VOLATILE INTEGER SOURCE_AV		=	0	// 08,22,0d,00,00,84,45
    VOLATILE INTEGER SOURCE_URC_SETUP	=	0	// 08,22,0d,00,00,D4,F5
    VOLATILE INTEGER SOURCE_U_R_?		=	0	// 08,22,0d,00,00,F0,D9
    VOLATILE INTEGER SOURCE_U_R_?		=	0	// 08,22,0d,00,00,E0,E9
    VOLATILE INTEGER SOURCE_U_R_?		=	0	// 08,22,0d,00,00,B7,12
    VOLATILE INTEGER SOURCE_U_R_?		=	0	// 08,22,0d,00,00,72,57
    *)
    
    

    If you're really interested, I can post the Netlinx module I wrote for it, but for now I'll attach the spreadsheet.
  • cmasoncmason Junior Member Posts: 123
    deps wrote: »
    Are there any way to get feedback from tv? Power state, volume level?

    Thanx

    The commands I posted do generate replies, but they seem to be fairly inconsistent hex strings.
    I suspect there might be a problem with the RX on the port. I'll know for sure this weekend when I get a replacement unit. The original one has a dead pixel in the middle of the screen, hardly noticeable, but knowing it's there is enough to make me want a replacement. ;)
  • a_riot42a_riot42 AMX Wizard Posts: 1,619
    cmason wrote: »
    The commands I posted do generate replies, but they seem to be fairly inconsistent hex strings.
    I suspect there might be a problem with the RX on the port. I'll know for sure this weekend when I get a replacement unit. The original one has a dead pixel in the middle of the screen, hardly noticeable, but knowing it's there is enough to make me want a replacement. ;)

    From what I've seen all you get is a yay/nay hex string. I can't remember what the characters are off the top of my head but there was no quantitative feedback from these, just a thanks or no thanks.
    Paul
  • fogled@mizzou[email protected] h4x354x0r Posts: 549
    I just happen to be working on the same thing right now, using EX-LINK on Samsung displays; the Power OFF reply is a consistent 3-byte code, but the Power ON reply is several long strings of random garbage. I've watched it 20 times and never been able to identify any consistency in the strings I get back. But since all I'm doing is Power ON and Power OFF, I can trap for the OFF reply, and then pretty much anything else is a power ON reply. Crude and goofy, but it seems to be working for now.
  • cmasoncmason Junior Member Posts: 123
    I just happen to be working on the same thing right now, using EX-LINK on Samsung displays; the Power OFF reply is a consistent 3-byte code, but the Power ON reply is several long strings of random garbage. I've watched it 20 times and never been able to identify any consistency in the strings I get back. But since all I'm doing is Power ON and Power OFF, I can trap for the OFF reply, and then pretty much anything else is a power ON reply. Crude and goofy, but it seems to be working for now.

    Yes, I agree. Just a whole lot of $FFs with a smattering of other hex bytes. I first thought it was my display, but I received a replacement and the responses are the same.
Sign In or Register to comment.