danw
Lifetime Supporting Member
I need to talk to an ASCII device at 7 bits, odd parity, 1 stop bit (7,O,1) directly over RS-232 using Hyperterminal, not over a Modem.
I can connect when I configure a new session, configuring the default COM parameters to what are needed, but I have been unable to save the session as a file to use it subsequently. When saved, the COM parameters don't save properly, they save as 9600 8,N,1, not 7,O,1.
When I configure Hyperterminal in Windows XP SP3, I configure the COM port for 9600, 7, O, 1 no handshake.
I connect OK using my modified settings, do whatever, 'save as' and name that connection session as an .ht file.
When I disconnect, open that same file, it opens in Hyperterminal as 9600 8,N,1, makes the connection, but the ASCII characters are all bolexed up because the bits and parity are wrong.
From the COM setting window, I've tried
- 'apply' button first, then OK.
- OK
in order to try to 'register' the COM settings.
Both produce the same results - the COM settings are not saved as they have properly worked in a session.
Any suggestions?
Dan
I can connect when I configure a new session, configuring the default COM parameters to what are needed, but I have been unable to save the session as a file to use it subsequently. When saved, the COM parameters don't save properly, they save as 9600 8,N,1, not 7,O,1.
When I configure Hyperterminal in Windows XP SP3, I configure the COM port for 9600, 7, O, 1 no handshake.
I connect OK using my modified settings, do whatever, 'save as' and name that connection session as an .ht file.
When I disconnect, open that same file, it opens in Hyperterminal as 9600 8,N,1, makes the connection, but the ASCII characters are all bolexed up because the bits and parity are wrong.
From the COM setting window, I've tried
- 'apply' button first, then OK.
- OK
in order to try to 'register' the COM settings.
Both produce the same results - the COM settings are not saved as they have properly worked in a session.
Any suggestions?
Dan