Socket Spy/32
WinSock Application Trace/Debugger

Listen32
Win32 Serial Data Monitor

Listen32 is a 32-bit version of Listen which includes all the above features plus the ability to launch and monitor communications from separate Win32 processes without being physically connected to the serial cable. It operates much like the Socket Spy applications, hooking the communications API within Windows by launching a target application using the Win32 Debugger API. Listen32 also provides extended buffering operation for longer term data collection and the ability to transmit byte strings to a device for testing protocol response.

Adapt-a-Spy
WinSock API Trace Toolkit

The Adapt-a-Spy toolkit has been proven to work with Windows 95, 98, NT, and Windows 2000. It demonstrates two different techniques for injecting a dll into the process space of a third-party application without violating any Win32 security constraints. All code necessary to set the hooks on each WinSock function is provided for both the WinSock 1.1 and WinSock 2.0 API. Shell routines are provided for each WinSock function which gives you complete control over all parameters passed into and out of the target application. All you have to do is include your custom logic in the function of choice, to access and possibly change data as it's passed back and forth between the application and the WinSock DLL.

ModSim32
Win32 Modbus Simulator with OLE Automation, (single-user license)

ModSim32 is an expanded version of the popular 16-bit application ModSim. It is a Win32 application designed to operate as one or more MODBUS slaves, simulating data which may be accessed from a MODBUS master application. ModSim32 can support direct serial connections to the master application, or operate as a network server to supply data to multiple modbus/TCP-compatible client applications.

MNetSvr
Modbus to TCP/IP Server Application, (single-user license)

MNetSvr is a Windows application designed to operate as a logical bridge between serial modbus devices and networks running the TCP/IP protocol. MNetSvr supports the modbus/TCP, (Modbus API standard for network communications), protocol to service requests for data from connected client applications, (acting as Modbus Masters), to one or more slave devices connected to MNetSvr serially.

MNetMon
Transparent modbus monitor to TCP/IP Server, (single-user license)

MNetMon is based on a very simple concept. Because the RS-232 electrical protocol operates using a, (voltage level), active transmitter connected to a passive receiver, it's generally possible for a second receiving device to tap into and "listen" to the transmitted characters without interfering with the conversation between to orignal devices. By using two comm ports on the eavesdropping machine, both sides of the link may be monitored. This technique has been used for years, (and is the basis for WinTECH Software's Listen & Listen32 Serial Data Link Monitors).

Modbus Master OCX
Win32 Modbus Control, (Developer's License)

Modbus_master.ocx contains a 32-bit custom control which allows Visual Basic and other OLE Container applications to quickly and easily access data points contained in a modbus slave device connected to the PC. The modbus device may be connected directly to a PC COM port or accessed via a network connection using the modbus/TCP, communications protocol standard. Modem connections are also supported using the Win32 TAPI, (Telephony APplication Interface) library. Multiple connections may be made from the application to different COM ports and/or network devices and each connection operates independently, allowing asynchronous operation to multiple devices on multiple modbus networks.

Modbus Slave OCX
Win32 Modbus Control, (Developer's License)

The Modbus_slave control allows your application to easily exchange data with modbus master devices connected either serially or via a TCP/IP network. The control supports up to four simultaneous COM port connections plus the modbus/TCP network connection. Your application simply passes a pointer to one or more data arrays, and the data is immediately accessible to any connected master controller using either the modbus RTU or modbus ASCII transmission mode.

16-bit Modbus Master Driver for Windows 3.x
The following API calls are supported by both the 16-bit Modbus Master Dll and the Win32 Master Dll. The 32-bit version uses a separate thread to handle COM notification events so the last two calls, (ProcessCommNotification() and ProcessTimerNotification()), are not required.

16-bit Modbus Slave Driver for Windows 3.x
The following API calls are supported by both the 16-bit Modbus Slave Dll and the Win32 Slave Dll. The 32-bit version uses a separate thread to handle COM notification events so the last two calls, (ProcessCommNotification() and ProcessTimerNotification()), are not required.

Modbus Master Driver for Win32
(Supports Serial, TAPI & Network Connections)

The expanded version of the Win32 Master Dll supports not only direct serial connections, but also modem connections via the TAPI interface, as well as network connections using the MBAP, (Modbus API for network communications), standard.

Modbus Slave Driver for Win32
(Supports Serial & Network Connections)

The expanded version of the Win32 Slave Dll supports not only direct serial connections, but may also serve as a modbus network server using the MBAP, (Modbus API for network communications), protocol. Only one API call has been added from the basic modbus slave command set.

OPCXchg
Data Exchange Utility for OPC, Modbus & modbus/TCP (Single User License)

OPCXchg is a Windows application that allows you to access data from various third-party devices and utilize this data in a variety of ways to create graphical displays and/or exchange this data with other devices. OPCXchg supports both modbus master and modbus slave devices as well as local and remote OPC connections. Modbus devices may be connected serially via one or more of the PC COMM ports or via a TCP/IP network interface. Data from any connected device, (or OPC application), may be exchanged with any other connected device. A simplified user interface allows data points to be displayed within OPCXchg using a variety of built-in graphical objects. OPCXchg also supports OLE Automation that allows data from connected devices to be accessed from Visual Basic and/or Excel.

OPCtoDDE
OPC To DDE Utility (Single User License)

OPCtoDDE provides a convenient link between data contained in an OPC Server and an Excel spreadsheet. Using OPCtoDDE, you can easily access OPC data items from Excel without generating any Basic code. OPCtoDDE utilizes existing DDE technology contained within Excel, to provide live links with OPC. As data changes, items in the spreadsheet will automatically be updated.

MbOPCsvr
Generic OPC Server for modbus

mbOPCSvr is designed to provide a generic interface between modbus slave devices and Windows applications operating as OPC Clients. MbOPCsvr operates as a standard Windows Multiple Document Interface, (MDI), application. Each document represents a block of data from an addressed modbus slave and is scanned independently based on a user defined clock interval. Each data item configured within a document may be addressed by one or more OPC Client applications. As new data is read from the modbus slave, the OPC Tags are automatically updated. Multiple slaves may be attached to the PC and made available to OPC from any of nine serial ports or via a modbus/TCP connection.

OPC Server DLL
The WinTECH Software Rapid Development DLL for OPC Servers, (WTOPCSvr), provides an easy to use API for integrating custom data with OPC. All the details of COM and OPC are handled by the DLL, which allows an application to present data points to OPC at a high-level, without having to be concerned with the actual implementation of the underlying interfaces. The DLL may be easily integrated with existing applications, or new ones. All required OPC Interfaces are supported for both OPC 1.0 and OPC 2.0 Data Access Standards as well as the Browse Interface.

WTOPCSvr basically operates as a data librarian. The controlling application creates Process Tags by passing a name and value to the DLL. The DLL records the data point and makes it available to any OPC Client application by name. The controlling application may change the value of the data at any time, and all attached clients would be automatically notified. Callback notification is provided for any Process Tag that is modified by an OPC Client connection. (The application has control over which tags are OPC_WRITEABLE.)

OPC Client DLL
The WinTECH Software Rapid Client Development DLL, (WTclient), provides an easy to use API for integrating a custom application with data from any OPC Server. All the details of DCOM and OPC are handled by the DLL, which allows an application to easily obtain data points from a Server, without having to be concerned with the actual implementation of the underlying interfaces. The DLL may be easily integrated with existing applications, or new ones. All required OPC Interfaces are supported for both OPC 1.0 and OPC 2.0 Data Access Standards as well as the Browse Interface. Support for Alarms & Events is also included.

HDA Server DLL
The WinTECH Software Rapid Development DLL for HDA Servers, (WtHDAsvr), provides an easy to use API for integrating custom data with OPC. All the details of COM and OPC are handled by the DLL, which allows an application to present data to OPC at a high-level, without having to be concerned with the actual implementation of the underlying interfaces. The DLL may be easily integrated with existing applications, or new ones.

WtHDAsvr basically operates as a logical wrapper containing support for all the OPC Historical Data Access Interfaces. The controlling application is responsible for defining the item names, attributes and aggregate values that it has available and the dll handles all the actual COM/DCOM Interface calls. As various HDA Clients connect and request historical data, the dll calls back into the application to satisfy the request. The callback mechanism used by the WtHDAsvr dll consists of a C++ object with overloaded functions to read timestamps, item values, attributes and calculations. These function definitions which must be supplied by the application are designed to be easy to implement and of the four, only the timestamp and item value functions are required. Support for Attribute and Agregate values is optional.

HDA Client DLL
The WinTECH Software Rapid HDA Client Development DLL, (WtHDAClient), provides an easy to use API for integrating a custom application with data from any OPC HDA Server. All the details of DCOM, OPC and HDA are handled by the DLL, which allows an application to easily obtain data points from a Server, without having to be concerned with the actual implementation of the underlying interfaces. The DLL may be easily integrated with existing applications, or new ones. All required OPC HDA Interfaces are supported.