Connecting Two Devices Using Hyper Terminal

Don't type the < and > characters in hyperterminal. For example, if the command is BOB and the data is 1234, then type

STXBOB(1234)XSMETX

If the command is BOB with no data, type

STXBOB!XSMETX

Hope that helps.

Thank for your comment. I had tried but still cannot connect to device. I wonder that as manual "All of the serial commands begin with an ASCII 2 character <STX> and end with an ASCII 3 character <ETX>." do I have change the text that I type in hyper terminal to ASCII code?

at First I couldn't see the character I typed on hyper so when I ticked in "send line ends with line feed" and "Echo typed characters locally" in ASCII setup tab in Hyper then I could see the character on hyper window but nothing happen.

Thank for your help.

First try rechecking Hyperterminal's settings:

Which COM port?

Speed and Format

Is the program in Send or in Receive setting.

Are you using RTS/CTS - XON/XOFF - None?

Also, are you using a direct connect cable (2-2, 3-3) or a 2-3, 3-2 cable? Some control connections prefer one, others prefer the other.

as I said above , all the comport, speed and format I did as manual, 38400 b/s; no parity, 8 data bits, 1 stop bit (38400,N, 8, 1).and I tried one after the other hard ware, XON/XOFF and none and cable is straight through serial cable.

as per your statement your reciver is dedicated one (may be microcontroller base or pc base) and it have lcd display or its out put input display,

your are connecting this controller reciver with pc with stright controller, and how can you monitor your instruction on it.

in normal case you have to check controller output on hyper terminal. els you need supprorting software for the same from controller /reciver supplier.

most of the dedicated controller require such software and data cable for the same.

as you are considering only tX and rX what about cts rts and dsr line as so many controller required that lines.

if establish link between reciver and pc and config your system for perticular compport and reciver is capable to communicate ( i mean sutabel protocol and software) at list it will show some thing may be unreadeble data.

check it

Try replacing the "STX with "ALT002" and the "ETX" with "ALT003". Or maybe only one zero after the "ALT" key. Also, you may have to try both "ALT" keys on your keyboard- some systems interpret them as two separate keys, others see them as the same.

Do u have a 25 pin or 9 pin connector. U'll need a null modem in between a 9->25 pin connector change or vice versa. Otherwise u gotta tell ht which serial port ur connected to. You also need to make sure your serial port is active in your computer's BIOS.

ASCII characters below ASCII(31) do not print. ASCII (32) is the space character. I have written some programs using Visual Basic to control production equipment. What you want to do seems easy and I am prepared to make a small program that will enable you to send commands to your device and display the responses. To achieve this I will need additional information regarding what you device echoes back. For example, when you send a command 'Are you there?, is that command echoed back 'Are you there? Yes

If you would like me to help please advise me. I would need a copy of the manual or to see the commands, responses, formats, handshaking and so on.

I do not quite understand I think, but I use rs232 communications semi-regularly. First off I get the pin out diagrams of the two ports to connect together. Then I make sure the cable(I make my own) connects the appropriate pins of each port together. Then I configure the COM Port on the PC(usually do not have to configure the nonPC port). I then connect the devices with the cable and reboot the PC. Depending on the devices sometimes proprietary software is required or hyper terminal alone will work.

If all is configured/crafted properly the devices should talk. The most common problem I have come across with PC to other device rs232 communication are:

1) the 'other' device (ie nonPC) does not have a standard pin out diagram.

2) the communication link does not automatically re-establish itself when the nonPC device is powered off then back on or the cable is disconnected and reconnected.

3) the cable is not the right type (refer to #1).

My advice double check your pin outs make sure the cable is the correct cable for the job. Double check your configuration of the PC COM port. reboot your PC after everything is connected and configured properly.