Sending Hex over TCP

Question

1.00/5 (2 votes)

See more:

Hi,

I try to send hex data to a LCD monitor over TCP.But I could not send.
For exampla "32 00 01" is a test hex for monitor.
How can ı send it over tcp.
Thank you

I use this cod but itis not working
do you any other idea
thank you

        m_socClient = new Socket(AddressFamily.InterNetwork, SocketType.Stream, ProtocolType.Tcp);
string szIPSelected  = txtIPAddress.Text;
String szPort = txtPort.Text;
int  alPort = System.Convert.ToInt16 (szPort,10);

System.Net.IPAddress    remoteIPAddress  = System.Net.IPAddress.Parse(szIPSelected);
System.Net.IPEndPoint   remoteEndPoint = new System.Net.IPEndPoint(remoteIPAddress, alPort);
m_socClient.Connect(remoteEndPoint);
        byte[] message = new byte[] { 32, 0, 1 };
        m_socClient.Send(message);

[edit]Code block added - OriginalGriff[/edit]

Posted 28-Mar-11 23:17pm

sabridemirel

Updated 29-Mar-11 0:53am

OriginalGriff

v3

Add a Solution

2 solutions

Solution 2

use byte array to send the Hex data to the Hardware

byte[] mybyte = new byte[] { 32, 0, 1 };

use the above byte array to send data to the LCD Screen

Posted 28-Mar-11 23:25pm

Rajesh Anuhya

Comments

sabridemirel 29-Mar-11 6:45am

I use this cod but itis not working
do you any other idea
thank you

m_socClient = new Socket(AddressFamily.InterNetwork, SocketType.Stream, ProtocolType.Tcp);
String szIPSelected = txtIPAddress.Text;
String szPort = txtPort.Text;
int alPort = System.Convert.ToInt16 (szPort,10);

System.Net.IPAddress remoteIPAddress = System.Net.IPAddress.Parse(szIPSelected);
System.Net.IPEndPoint remoteEndPoint = new System.Net.IPEndPoint(remoteIPAddress, alPort);
m_socClient.Connect(remoteEndPoint);
byte[] message = new byte[] { 32, 0, 1 };
m_socClient.Send(message);

Rajesh Anuhya 29-Mar-11 6:46am

what is the Error Message your are Getting

sabridemirel 29-Mar-11 6:58am

nothing,it seems working but nothing change onthe LCD monitor

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Accepted Answer · 2011-03-28T23:24:00

Solution 1

"Hex" is not something you send, it is just a way of looking at the numbers. For example, 112 is the same number as one hundred and twelve - they are just in different representations.

Instead, use bytes and send those (assuming it is Hex 32 you want to send):

byte start = 0x32;
byte middle = 0x00;
byte end = 0x01;

Now send those bytes and see if it works!

You can create them as an array and send that instead:

byte[] message = new byte[] { 0x32, 0x0, 0x1};

"I use this cod but itis not working
do you any other idea
thank you"

Look at your code, then look at my equivalent:

byte[] message = new byte[] { 32, 0, 1 };

byte[] message = new byte[] { 0x32, 0x0, 0x1};

The "0x" prefix says that the data to follow is Hexadecimal - i.e. base sixteen.
If you do not specify, then decimal is assumed - i.e. base 10.
32 Hex is 50 in decimal!

It's like saying that 112 is the same number as two hundred and seventy-four!
(112 in hexadecimal is 274 in decimal)

Posted 28-Mar-11 23:24pm

OriginalGriff

Updated 29-Mar-11 0:57am

v2

Comments

Rajesh Anuhya 29-Mar-11 5:29am

well explained.., Good one +5

sabridemirel 29-Mar-11 6:42am

I use this cod but itis not working
do you any other idea
thank you

m_socClient = new Socket(AddressFamily.InterNetwork, SocketType.Stream, ProtocolType.Tcp);
String szIPSelected = txtIPAddress.Text;
String szPort = txtPort.Text;
int alPort = System.Convert.ToInt16 (szPort,10);

System.Net.IPAddress remoteIPAddress = System.Net.IPAddress.Parse(szIPSelected);
System.Net.IPEndPoint remoteEndPoint = new System.Net.IPEndPoint(remoteIPAddress, alPort);
m_socClient.Connect(remoteEndPoint);
byte[] message = new byte[] { 32, 0, 1 };
m_socClient.Send(message);

OriginalGriff 29-Mar-11 6:57am

Answer updated

sabridemirel 29-Mar-11 7:05am

I changed the code and try again.
ı send the message like this
byte[] message = new byte[] { 0x32, 0x0, 0x1};
but its not working
thank you for your support but do you any other idea.
i have to do it

OriginalGriff 29-Mar-11 7:11am

First, check you are in any form of communication with the device. Is there a way to make it talk to you? If so, then check if it is. If not, then you are down to the manual - is there a fragment which talks about communicating via TCP you could post (not the whole manual, please!)

sabridemirel 29-Mar-11 7:16am

yes,the device has a demo program and ı can use it.ı have manual about communication.where can ı post it to?

OriginalGriff 29-Mar-11 7:19am

If it is PDF, it's probably on the net already - see if it is, or just copy and paste the relevant fragment.
Does the demo have source code?

sabridemirel 29-Mar-11 7:22am

the demo hasn't got source code.if you give me your mail ı can post to you.
ı paste it here if you want i can post it to you by email
MIS1 communication over TCP/IP
In order to exchange information with an LCD controller all data must be wrapped into an MIS1 frame according to the Definition of Host (DoH). The following table shows all transport layers:
# Layer Function
7
Data
MIS1, DoH
6
5
4
Transport
TCP
3
Network
IP
2
Data Link
Ethernet
1
Physical
Table 1: OSI model
In the example below the required MIS1 frames for displaying a given text sequence on the display (command 0x18, see Definition of Host) are illustrated.
1. Sending the command
At first, the host sends the command to the LCD controller with slave address 1 which contains all necessary information:
>>>[19] 0x04 0x81 0x02 0x18 0x01 0x01 0x00 0x00 0x10 0x05 0x00 0x0A
0x00 0x40 0x41 0x42 0x43 0x03 0xB2
Control characters: 0x04 0x02 0x03
Slave address: 0x81 Address 0x01 OR 0x80
Code and Command ID: 0x18 0x01
Data payload: 0x01 Image number, 1
0x00 Font number, 0
0x00 0x05 Horizontal position x, 5px
0x00 0x0A Vertical position y, 10px
0x00 0x40 Text range width w, 64px
0x41 0x42 0x43 Text data, “ABC”
Escape character: 0x10
Checksum: 0xB2
As the data payload byte 0x05 is a control character (ENQ) it has to be escaped with 0x10 (DLE). The checksum is an arithmetic sum counting all bytes after 0x02 (STX) including 0x03 (ETX) – any DLE characters (0x10) must be ignored! Thus the sum can be calculated as:
0x18 + 0x01 + 0x01 + … + 0x42 + 0x43 + 0x03 = 0x0132 OR 0x80 = 0xB2
2. Receiving the acknowledgement
When a command has been sent to a slave controller it immediately replies with either an ACK (0x06, positive) or a NAK (0x15, negative) byte. This returned byte only informs the host about the MIS1 frame syntax, not about the correctness of the command itself.
<<<[1] 0x06
Status byte: 0x06 Command syntax OK
3. Requesting the status
In order to check whether a previously sent command has been accepted or an error occurred, the host can request the status of the client by sending an enquiry.
>>>[3] 0x04 0x81 0x05
Control characters: 0x04 0x05
Slave address: 0x81 Address 0x01 OR 0x80
4. Receiving the error notification
In case the command from the first step did not generate an error the slave controller will simply respond with a single NAK (0x15) byte.
<<<[1] 0x15
Status byte: 0x15 No error available
Otherwise an appropriate error notification message will be returned to the host. For example if the text range width was chosen too small for the transmitted text array the following notification would be sent:
>>>[3] 0x04 0x8C 0x01 0x18 0x01 0x03 0xA9
Control characters: 0x04 0x03
Code and Command ID: 0x8C 0x01 Command ID generating the error
Data payload: 0x18 Code generating the error
0x01 Error code, “CLIPPED”
Checksum: 0xA9

OriginalGriff 29-Mar-11 7:35am

It looks like the socket should provide up to and including layer 4 (TCP), and layer 5 and 6 should be pretty transparent anyway, but the description "In order to exchange information with an LCD controller all data must be wrapped into an MIS1 frame according to the Definition of Host (DoH)" implies that the data you need to send as a packet to the LCD is formatted in a particular way with additional checksums - I could be wrong, but that's the way I read it.
I would suggest at this point that the best thing you can do is contact the LCD panel manufaturers - they may let you have the source for the demo program, or someone who can talk, you through it with the panel and manual in front of him!

Debugging comms from scratch over a message based forum is likely to be a very lengthy process...

Sorry about that, but I think it's time to speak directly to someone who works with your panel!

Good luck!

Sergey Alexandrovich Kryukov 29-Mar-11 11:46am

5 just for patience.
--SA