/
Character Response on CoBos device servers
Character Response on CoBos device servers
If I enable Character Response on a CoBos device server by
- setting bit 4 in Connect Mode (e.g. setting Connect Mode to 10) in Setup Mode
- or by choosing Char Response as the Connect Response under Common Options on the Connection Settings page of the web manager
I see this behavior:
- If I make outgoing connections from the serial port (e.g. by using Manual Connection), I get single character responses as documented in Table 7-5 in the UDS1100 User Guide, http://www.lantronix.com/pdf/UDS1100_UG.pdf.
- However, if I open an incoming connection to port 10001, I get a Character Response like CI172.20.192.178, where 172.20.192.178 is the IP address of the host that opened the connection.
Why is this?
This is normal behavior.
For incoming connections, Character Response sends
C when a connection is succesfully established
D when a connection is terminated
N when a connection cannot be established
For incoming connections the Character Responses are:
CI<ip address> when a connecton is established from a host at <ip address>
D when the connection is terminated.
[Originally Published On: 06/16/2011 04:36 PM]
, multiple selections available,
Related content
Connect modes for Cobos based devices
Connect modes for Cobos based devices
More like this
Using Hostname for Outgoing Manual Connections in CoBOS Devices
Using Hostname for Outgoing Manual Connections in CoBOS Devices
More like this
Using UDP Configuration In CoBos Products To Reply To The Last Host Requesting Data
Using UDP Configuration In CoBos Products To Reply To The Last Host Requesting Data
More like this
CoBox & UDS - What TCP port #s should I use to connect to a serial port?
CoBox & UDS - What TCP port #s should I use to connect to a serial port?
More like this
Problems sending data containing 0xFF and-or CR
Problems sending data containing 0xFF and-or CR
More like this
Serial Tunnel using Modem Emulation between two CoBos device servers
Serial Tunnel using Modem Emulation between two CoBos device servers
More like this