Virtual Connector

Purpose: connect 2 applications/flows.

Connector creates virtual COM port that can be opened two times.

After opening virtual port, the applications can start exchanging data.

Data flow diagram

If you hit issues with connector, please use Virtual Pair.

Some applications may require "Always queue write requests" option to work properly.

Connector settings

• "Emulate baud rate": enable baud rate emulation for read requests.
• "Always queue write requests": if enabled, all write requests will always be put in the queue for delayed processing. Less efficient but may be useful for compatibility with some applications. If enabled, Baud rate emulation is disabled.
• "Do not allow multiple connections from the same application": if enabled, Connector will not allow the same application to open Connector virtual COM port 2 times. This solves problem with some applications.
• "Write requests processing disabled if both clients are not connected": if checked, VSPE will immediately "succeed" write requests if Connector does not have both clients connected. This can be useful if the only connected application writing to the COM port does not use write timeouts and you do not want to block write calls.
• "Notify about remote client connection/disconnection": if checked, VSPE virtual port will generate EV_EVENT1 on remote client connected and EV_EVENT2 on remote client disconnect
• "Allow buffer overruns": if checked, write requests will succeed without writing data if remote input buffer is full
• "Reset modem registers on close": if checked, RTS/DTR modem registers are reset on close and propagated to peer
• "Purge buffers on open": If enabled, virtual COM port buffers will be purged on open
• "Purge buffers on close": If enabled, virtual COM port buffers will be purged on close

You can also define custom pinout for virtual COM port.

See also:

• Transform data in your application using Connector or Pair device
• Pinout settings