NavCom Sapphire Rev.J - Manual (Page 426)

Sapphire Technical Reference Manual Rev. J
426
[ETHVCOM] Examples
[ETHVCOM] ON, 192.168.0.2, 4361
Establish a virtual COM port connection with a remote user having an IP address of 192.168.0.2
and port number 4361
[ETHVCOM] ON,0.0.0.0,0
Break current connection (if any), and enable the unit to listen for a connection from the next
remote unit that sends a packet to this unit. This is the proper way for a remote user to
terminate a UDP connection when in UDP2 mode. It will cause the unit to stop sending data,
and listen for a new connection from another user. The mode will remain the same (UDP or
TCP) as the previous session.
[ETHVCOM] ON,0.0.0.0,0,UDP1
Break the current connection (if any) and listen for a UDP1 connection. Any scheduled
messages for this logical port will be silently discarded
[ETHVCOM] OFF
Terminate any current connection, and disable new EVCOM connections on this logical port
(ETH1…ETH4).
[ETHVCOM]
[ETHVCOM] ON, 192.168.0.100, 5042, TCP1, 4361, ETH1
[ETHVCOM] ON, 0.0.0.0, 0, TCP1, 4362, ETH2
[ETHVCOM] OFF, 0.0.0.0, 0, UDP1, 4363, ETH3
[ETHVCOM] ON, 46.153.12.73, 12345, UDP2, 4364, ETH4
Display EVCOM logical port settings (in this case, ETH1 has an active TCP1 mode connection
with remote user at IP 192.168.0.100 port 5042, to local TCP port 4361. EVCOM logical port
ETH2 is listening for a TCP1 mode connection from any remote client. ETH3 is disabled. ETH4
has an active UDP2 mode connection with a remote client at IP address 46.153.12.73 port
12345 on the Solaris UDP port 4364).
[ETHVCOM],,,,,ETH3
[ETHVCOM] ON,0.0.0.0,0,CTRL,4363,ETH3
Display current settings for “ETH3” (Ethernet Virtual COM port enabled, no active connection,
listening on UDP port 4363 for a CTRL mode connection from any remote client).
Defaults: Default settings for unspecified parameters.
Local UDP/TCP port 4361
Mode UDP1
ETHVCOM Application Notes
An EVCOM session may be established for several reasons, such as a StarUtil connection, high
speed data logging, or an OEM application interface.
If client applications schedule messages on an ONTIME basis using the [OUTPUT] command,
they should take care to un-schedule those messages before closing the connection. If not,
then next user that opens a connection to that logical port (ETH1
– ETH4) will receive those
messages even if they are unwanted and not requested. Additionally, it will cause unnecessary