If you make the resultsvariable something like "sharpsays"
and put a textbox with "Sharp LCD says: %variable>sharpsays%" (without the quotes) on the control screen that you are executing your event from, you'll be able to see what the sharp is displaying - if xlobby is talking to the sharp, you should at least get "ERR" as a response, may not solve your problem, but it's a place to start. You can test to make sure the xlobby is "getting" a response with the variable by adding the same event to another working 232 command just to make sure the feedback variable you created is working properly.
To make sure that the info you are seeing on the screen is current, you may want to set the variable to "Idle..." by adding a set variable command before whatever connand that sends the 232 to the screen.
The event you want to use to set %variable>sharpsays% is found in events under xlobby and is called "set variable" (without the quotes) you just put "sharpsays" (without the quotes) in the box for variable, and put "Idle..." in the "information" box.
- maybe?
I hope this helps.
Samson