What is VSPE?
Description
Virtual Serial Ports Emulator (VSPE) was developed as a solution to help engineers and software developers to create/debug/test applications that use serial ports.
Unlike regular serial ports, virtual COM ports may have special capabilities: for example, VSPE can create virtual port which be opened by multiple applications.
VSPE can share existing serial port with multiple applications (split/merge data), send serial port traffic over network (TCP or UDP protocol), transform data, create connected virtual ports and so on.
Key features
- Virtual Connector creates virtual COM port which can be opened by two applications to exchange data.
- Virtual Pair creates two connected virtual COM ports.
- Virtual Splitter creates multiple virtual COM ports connected to existing COM port in order to share it with many applications.
- Mapper redirects requests from one COM port to another COM port (useful if you want to redirect traffic from legacy application which cannot be re-configured).
- TcpServer shares COM port over network (listening to local TCP port). Data can be modified/filtered with Transformers.
- TcpClient shares COM port over network (connecting to remote TCP port). Data can be modified/filtered with Transformers.
- Serial Redirector redirects data between two COM ports. Data can be modified/filtered with Transformers.
- UDP Manager shares COM port over network using UDP protocol. Data can be modified/filtered with Transformers.
- Bridge connects two generic data streams (COM port, TcpServer, TcpClient, Named Pipe, File). Data can be modified/filtered with Transformers.
- Transformers can filter/transform live traffic flowing through some of VSPE devices above. For example, you can configure multiple TcpClients to receive only specific data from TcpServer.
- Native x86, x86_64 and arm64 platforms support.
- VSPE service can automatically restore last known VSPE configuration on Windows startup (if enabled in settings).
- Translated to 15 languages.
- No telemetry/usage data collection.
Latest BETA/Preview version: 1.5.0.88
This version contains new features and changes based on user feedback.
Your existing license key will work for this version.
Highlights:
- Virtual ports are now visible in Device Manager and to all applications
- VSPE service (running with minimum privileges on local computer) is now automatically loading last known configuration on startup (if enabled in settings)
- Native ARM64 platform support
- Introducing transformers for user-mode devices to filter/modify/control consistency of the data flows
- Virtual Splitter device: legacy mode with single shared virtual port or new mode with multiple virtual ports for better data flow control
- Fixed unicode characters localization and added new languages
.. more changes and fixes below:
- All kernel devices: fixes for Read/Write timeouts, supporting additional serial port events
- Virtual Splitter: internal data flow is fully re-written to make Splitter more reliable
- Virtual Connector/Pair: fixed baud rate emulation, resetting DTR/RTS registers on disconnect
- Virtual Splitter/Connector adding option to limit connections from the same application to the same virtual port
- Redirector, UdpManager, TcpServer, TcpClient, Bridge (Serial Port): switched to async read mode for better performance
- Transformers: Added LineSplitter and TextFilter transformers, adding multiple transformers for all supported user-mode devices
- Bridge: added NamedPipe client/server
- Serial Redirector: fixed issue with incorrect settings for device 2
- UdpManager: added read-only and write-only settings for COM port
- User interface: Added Start/Stop/Clone commands for devices
- User interface: "Open with terminal" menu now works for all virtual ports and TcpServer
- User interface: Terminal: fixed new lines, scrolling
- User interface: COM port selection drop list is now correctly pre-filled with existing COM port names
- Installer: validating for x32 platform installer when installing on x64 operating system because it caused driver installation issues
- Removed non-relevant settings (delete devices on quit, set as service helper etc) and command line parameters
- Deprecated: HttpServer is deprecated and removed
- Removed kernel devices data flow monitoring (it will be replaced with better monitoring solution in future version)
- VSPE documentation is fully re-written
- TcpServer: fixed bug with not setting keep alive settings for connected sockets
- TcpServer: added option to Close/Open COM port based on TCP connection state (number of connected clients)
- TcpServer: added maximum number of connections configuration setting
- TcpClient: fixed reconnection timeout setting
- TcpClient, Bridge: moved connection logic to separate thread to avoid lag when creating device
- TcpServer, TcpClient now can have only modem registers control connections (no data connections)
- Bridge file data source: input file is opened with share write permissions, allowing input file to be updated
- Bridge file data source: added option to read file from end
Latest released version: 1.4.7.634
Whats new?
- Introduced initial DTR/RTS states in serial port settings
- Fixed initial DTR/RTS states for TcpServer and TcpClient depending on connection status
- Removed deprecated python 2.7 python bindings
- Added buffer size in Bridge configuration (Tcp flow)
- Bridge device: not displaying error if initialization failed, allowing it to re-connect
- Fixed ReadIntervalTimeout kernel driver bug
- UdpManager: fixed receiver with datagram size > 1024
- Keyboard navigation UI fixes
- Few UI tweaks and improvements
Virtual Serial Ports Emulator for 64 bit operating systems
- For 64 bit (x86_64 and arm64) Windows operating systems. Requires license.
- Before ordering the license, feel free to validate if VSPE works for your scenarios.
Virtual Serial Ports Emulator for 32 bit operating systems
For 32 bit (x86) Windows operating systems. Does not require license (free).
VSPE license types
Evaluating Virtual Serial Ports Emulator
Before purchasing VSPE license, you can download and install any version of VSPE available on this page to check if it is suitable for your scenario.
The unregistered version of VSPE may have some limitations, but those limitations should not prevent you from validating your scenario.
Additionally, you can always contact us and request VSPE evaluation license, which will unlock all features for a limited period of time.
Standard VSPE License
- Allows to run VSPE on one computer on on all platforms we support: x86, x86_64 and arm64 (see special case below in this section).
- To run VSPE on more computers, you can either close VSPE on previous computers or buy more Standard license keys.
- The license is valid for current VSPE major version (first number) and for all previous supported major versions. It means that your license for 1.5.0.100 will keep working for VSPE versions like 1.6.0.0, 1.9.9.999, 0.9.0.0 etc but will not work for 2.0.0.0.
- When VSPE major version switch happens you will have the option to upgrade your existing license with discount or you can keep using old VSPE version.
- The license does not expire. There is no subscription, you do not have to pay again.
- Please note that this license does not grant access to VSPE API.
- Special case: It is OK to run VSPE on two computers (with the same license key) at the same time if:
- Both computers belong to the same user and
- Both VSPE applications are part of the same data flow (for example, connected by TcpServer/TcpClient devices)
- Standard VSPE License price is $24.95 + VAT/TAX. If applicable, volume discount will be applied automatically.
We are currently experiencing issues with payments. We are actively working on a solution.
We apologize for the inconvenience.
In the meantime you can contact us to request evaluation license key.
Free VSPE License for 32 bit Windows (for x86 platform only)
- Free to use in any 32 bit Windows operating system (for example, Windows 10/7/XP 32 bit).
-
(For developers) API key included in txt file. You can use VSPE API create and manage VSPE devices.
Please note, that this key is valid for the current version only.
After installing new VSPE version, you should replace old key with a new key.
Additional information
Refund policy
You have a right of withdrawal from your purchase within 14 days of the purchase.
Support
We will do our best to support you. If you have any problems with VSPE or need help configuring it for your scenario, please contact us.
Technical information
Supported operating systems
- Officially supported by Microsoft Windows operating system: x86 (32 bit)/x86_64 and arm64 (64 bit)
- Windows 11 ARM64 kernel driver support added starting from version 1.1.6.760
- Windows 10 (32/64), Windows 11 (64/ARM64) or Windows Server 2019/2022 (but can work on some other versions as well)
- Legacy operating systems require latest Windows updates/service packs to be installed: applicable to Windows XP, Windows Vista, Windows 7 and Windows 8. In some cases (for Windows XP for example) you will have to use previous VSPE version - see "Legacy operating systems support" section below.
- Latest VSPE versions kernel driver digital signature is not compatible with officially deprecated by Microsoft x64 systems such as Windows 7 x64 and Windows 8 x64. You can either use older VSPE version (1.1.5.458) or (as temporary workaround) disable driver signature verification in your system. x32 platforms do not have such limitation and can still work with latest VSPE releases. We are aware of this problem and working on it by going through re-certification process for legacy systems, but it takes time.
- Before every release, VSPE is thoroughly validated by combination of manual and automated tests on different operating systems. Automated test run is validating VSPE core functionality like creating/deleting devices, sending data in parallel, updating timeouts, updating modem registers etc. Automated test run on one system takes more than two hours and in addition to that we frequently run automated tests in a loop.
Operating system |
Platform |
Test run performed? |
Supported by latest VSPE version? |
VSPE license required? |
Windows 11 |
x86_64 (64 bit) |
Yes |
Yes |
Yes |
Windows 11 |
arm64 (64 bit) |
Yes |
Yes |
Yes |
Windows 10 |
x86_64 (64 bit) |
Yes |
Yes |
Yes |
Windows 10 |
x86 (32 bit) |
Yes |
Yes |
No |
Windows Server 2025 Preview |
x86_64 (64 bit) |
Yes |
Yes |
Yes |
Windows Server 2022 |
x86_64 (64 bit) |
Yes |
Yes |
Yes |
Windows Server 2019 |
x86_64 (64 bit) |
Yes |
Yes |
Yes |
Windows Server 2016 |
x86_64 (64 bit) |
Yes |
Test signing mode only |
Yes |
Windows Server 2012 |
x86_64 (64 bit) |
Yes |
Test signing mode only |
Yes |
Windows 8 |
x86_64 (64 bit) |
Yes |
Test signing mode only |
Yes |
Windows 8 |
x86 (32 bit) |
Yes |
Yes |
No |
Windows 7 |
x86_64 (64 bit) |
Yes |
Test signing mode only |
Yes |
Windows 7 |
x86 (32 bit) |
Yes |
Yes |
No |
Windows XP |
x86_64 (64 bit) |
No |
No. Use older VSPE version |
Yes |
Windows XP |
x86 (32 bit) |
No |
No. Use older VSPE version |
No |
Legacy operating systems
To avoid any problems with kernel driver signature verifications (manifesting as error 241 due to missing root certificate), please ensure that legacy Windows system has all the latest updates installed.
If you are using Windows operating system which is not officially supported by Microsoft (Windows XP, Vista etc), you can hit issues with loading VSPE kernel driver. In this case you can try to using older release which is compatible to those systems:
VSPE_0.937.4.747
Please note that Windows 7/8 x64 (officially deprecated by Microsoft) currently are not able to verify latest VSPE kernel driver signature. x32 platforms do not have this problem.
We are working to mitigate this but it takes time - as we need to go through different kernel driver re-verification procedure.
As a workaround, you can either disable this verification or use VSPE version which uses legacy-compatible drivers:
VSPE_1.1.5.458
Windows 7 x64
Please note that Windows 7 is officially not supported by Microsoft anymore and it is recommended to use up-to-date version of Windows.
VSPE requires Windows 7 x64 to have Service Pack 1 + all security updates to be installed.
If for some reason you prefer not to install Service Pack 1, you can download old VSPE version below which works on unpatched Windows 7 verison:
VSPE_0.937.4.747
Known issues and workarounds
-
Upgrading VSPE fails from 0.xxx to 1.xxx version.
When upgrading from 0.xxx version, VSPE sometimes cannot start kernel driver when executed for the first time, and VSPE will suggeste few ways to fix this if it happens.
The easiest way to avoid this issue is to uninstall old version first, reboot and install new version.
-
Autostart as Windows Service command bug generated by "Helpers -> Set up as Windows Service" (VSPE version: <= 1.1.5.458)
Make sure that the service creation command ends like this (with extra double quotes):
\"" start= auto
and not this (as default):
\" start= auto
Previous versions
SetupVSPE_Full zip files contain installation packages for all supported platforms.