How To Open Hyperterminal
Related: Using HyperTerminal as your Telnet interface. If you really want the original XP HyperTerminal, do the following: Open the Windows XP media, navigate to the I386 folder, and copy the 4 HYPERTRM.* files (.CH_,.DL_,.EX_ and.HL_) to a local folder; Open a command prompt at the folder where you copied the four files. Related: Using HyperTerminal as your Telnet interface. If you really want the original XP HyperTerminal, do the following: Open the Windows XP media, navigate to the I386 folder, and copy the 4 HYPERTRM.* files (.CH_,.DL_,.EX_ and.HL_) to a local folder; Open a command prompt at the folder where you copied the four files.
So I am trying to connect to a piece of hardware. If I connect and disconnect with hyperterminal first. Then close the connection and the program. Everything works fine. If I don't I receive random characters back from the hardware. I use the same settings in hyperterminal as I do in the code.
baud=9600
parity=n
data=8
stop=1
Hardware flow controls 'ON':
octs=on to=on dtr=on rts=hs
If I then disconnect the hardware and the serial port I will have the same problem again.
Is there anyway I can see how to comport is being configured after hyperterminal open and closes the port? Beyond compare key. I should note I am using a prolific serial to USB adapter.
Below is the code I use to open the com port. Chamak chalo chni kabily.
3 Answers
Please, try Advanced Serial Port Monitor -> Spy mode. http://www.aggsoft.com/serial-port-monitor.htm. It will show all actions that Hyperterminal does on the port. Then you can repeat these settings. It seems that the problem is related with the hardware flow control settings.
Hyperterminal In Windows 7
Below is the code I used to fix my problem. I only ever had to do it this way for one piece of equipment.
BuildCommDCB() fails if 'rts=hs' is included in the control string. This causes lpDCB to be not set correctly, and SetCommState is called with the wrong values.
You can set the RTS control flag in the lpDCB structure after calling BuildCommDCB. (I would include code but I'm not certain on the Basic syntax)
