I was,

I gave up and used IR as all I needed was on/off/inputs/color/aspects. Had to handle power tracking with a system variable, but figured it was better than the buggy samsung 232. When I was getting responses, it would drop from time to time or go back to the debug mode and I would lose connection. I figured that it just wasn't reliable enough to put into a clients home. I have the IR file for AMX if you would like

Jason

Well I am at the same point as Rolo. I have confirmed the Service Menu needs to be on RS232. The Debug selection justs streams data. I also am using AMX. I recieved some newer documentation today from Samsung and it does not really help. (just updates my old docs) All I newly discovered is that one will recieve a 0x03 0x0C 0xFF for a NAK. I am unable to get a good ACK code out of the set. (0x03 0x0C 0xF1) After each parameter sent, one should receive either an ACK or NAK. All I get are NAKs. So the problem does appear to be in the Checksum as the TV will respond after each and every parameter string. If you have a totally bad parameter string the TV will not respond at all. (I have on purpose attempted a short parameter string (only 6 bytes) and the TV does not respond.

to find out the TV response, simply look at the device buffer variable in debug mode. That is how I am determining if the TV is responding to my commands.

The example in the documentation does NOT work....Are we missing a command or something???

FYI... I am sending
SEND_STRING DLP_SERIAL,"$08,$01,$00,$00,$00,$00,$E6"

Has any one gotten an ACK out of the TV??

Bump

Anyone yet?

Does anyone have the protocol documents listed above? I tried the links but they are broken. I am having the same types of problems with an HL-S5087W. I set the port to RS232 but I get little to no response.

I am interested as well

One trick is hookup hyperterminal with cable attached and turn on the TV. This help me find the right baud rate with info feedback. Most of the time with TVs like this you will see some English words with firmware version etc.

I am using Crestron Viewport 3.99 to try and decipher the protocol. I was getting a TON of hex back when the set was in debug mode, nothing remotely resembling english. Since I have put it in RS232 mode, I get only minimal response. The document titled "RS232_PROTOCAL" says that the set will only issue an ACK of 03 0C F1, and no NACK for invalid commands or comm errors, but my experience varies. Crestron doesn't seem to have a driver in their database, does anyone have the AMX database?

Using Viewport without the processor connected to the TV.

ONLY when the TV was turned on was I seeing words on bootup. After that hex.