SuperCom™ TCP/IP

---

The Communication Toolkit for TCP/IP in Windows 7, Windows Vista, Windows XP/2000/Server 2003/Server 2008/NT/ME/9x

Communication Solutions by ADONTEC SuperCom Suite DEMO (Serial, ISDN, TCP/IP) trial version ?

Version 6.5 Price List Product Range Call Me Back

Looking for ZMODEM over TCP/IP ?

SuperCom for TCP/IP handles data communication over TCP/IP networks (internet and intranet).

SuperCom for TCP/IP provides an optimized Low Level Engine, which handles concurrent connections, buffers data and generates events. This engine provides maximum functionality but reduces CPU load to a minimum.

The Low Level Engine will trigger only wanted events. Unwanted events can be disabled reducing overhead.

A single application can run up to 255 (please ask if more needed) connections simultaneously. Nearly any combination possible e.g. 1 server and 254 accepted connections, only clients or different server and clients.

The SuperCom functions and protocols are also available over TCP/IP i.e. ZMODEM, YMODEM, XMODEM, XMODEM-1K, KERMIT, ASCII, 3964/R, RK512, MODBUS and LSV/2 (for the use of the 3964/R and/or LSV/2 protocol the SuperCom 3964/R Protocol Engine and/or the LSV/2 Protocol Module is also needed).

The easy to use and portable SuperCom API enables fast implementation of TCP/IP applications. A client or server application can be build in short time. Most functions and features are well known from the Serial and ISDN communication library.

The use of the common SuperCom API enables a move from RS-232 to TCP/IP or from ISDN to TCP/IP to be very smooth and quick. In most cases by simply switching the low level SuperCom DLL.

Complete samples for client and server applications are included in source code and for many developing environments and compilers.

Using the SuperCom Suite enables one single application to handle simultaneously connections through RS-232, TCP/IP and ISDN.

Features & Functions List
A DUAL API is included (DLL API and ActiveX API) .

DLL API	ActiveX API
Features	Features
Functions	Properties

The box includes
 - Dual API for Windows (WIN32)
 - ActiveX and DLL Samples
 - Documentation

Samples
Many Server and Client samples are included in source code for popular compiler incl. VC++ 6, Delphi, C++ Builder, VB6, C#, VB net. A Real world Client/Server project also included (ServerClient.pdf).

See also the the available product range for details.

Check our special offer, the Serial to TCP/IP GateWay software (COMMServer, PortServer) developed with SuperCom. This is Free Bonus software (incl. source code) offered to latest SuperCom Suite owners.

Supported Compilers
C#, C++, Visual Basic net, Visual C++, Visual Basic, Borland C/C++, C++ Builder, Delphi, VBA, LabView, FoxPro and DLL and/or ActiveX capable Windows developing environments (.NET ?).

License Information
Executables developed using SuperCom can be distributed royalty free.

Requirements
Windows 9.x/Me, Windows NT, Windows 2000, Windows Windows 2003, Windows 2008, Windows XP, Vista, Windows 7.

Sample - Connecting

Spending some time with the following sample shows how easy it is to use the SuperCom API. To make the use of SuperCom the same easy as possible within (nearly) any common IDE or programming language was an ultimate goal of our engineers.

DLL API
In order to receive events the application must provide an InfoProc*. The InfoProc is optional but very handy in many situation. Using the InfoProc the application can receive progress information, get informed about the time left to complete a call or even cancel the connection attempt.

   int InfoProc(Com, Action, TimeLeft, Data)
   {
      if (Action==acCONNECT_INFO)
      {
         // Received periodically, while in progress
      }
      if (Action==acCONNECT_OK)
      {
         // Connected !
      }
      if (Action==acCONNECT_FAILED)
      {
         // A connection attempt failed
      }

      return infContinue;

   }
      :
      :
     // init  ...
   ComInit(Com);

     // now connect ...
   Res = RS_ConnectEx(Com, SEC_60, , "www.adontec.com:80",InfoProc);

   Public Function InfoProc(ByVal Com As Byte, _
                            ByVal Action As Integer, _
                            ByVal TimeLeft As Long, _
                            ByVal Data As Long) As Long

      If SComAction = acCONNECT_INFO  Then
         'Received periodically, while in progress
      End If
      If SComAction = acCONNECT_OK  Then
         ' Connected !
      End If
      If SComAction = acCONNECT_FAILED Then
         ' A connection attempt failed
      End If

      InfoProc = infContinue

   End Function
        :
        :
     ' init  ...
   Call ComInit(Com)

     ' now connect ...
   Res = RS_ConnectEx(Com, SEC_60, , "www.adontec.com:80", InfoProc)

   Function InfoProc (Com:Byte; Action:WORD; TimeLeft:TDWORD; Data:PFDATA):Integer;
   Begin
      InfoProc:=infCONTINUE; { Continue }

      If (Action = acCONNECT_INFO) Then
      Begin
         // Received periodically, while in progress
      End;
      If (Action = acCONNECT_OK) Then
      Begin
        // Connected !
      End;
      If (Action = acCONNECT_FAILED) Then
      Begin
        // A connection attempt failed
      End;
        :
   End;
      :
      :
     // init  ...
   ComInit(Com);

     // now connect ...
   Res = RS_ConnectEx(Com, SEC_60, , 'www.adontec.com:80', @InfoProc);

   public int InfoProc(int Com, short Action, int Data, int pNotUsed)
   {
      switch (Action)
      {
         case SuperCom.acCONNECT_INFO:
               // Received periodically, while in progress
              break;
         case SuperCom.acCONNECT_FAILED:
               // A connection attempt failed
              break;
         case SuperCom.acCONNECT_OK:
               // Connected !
              break;
         case SuperCom.acUSERBREAK:
              // break by user
              break;
      }
      return SuperCom.infCONTINUE;
   }
      :
     // init  ...
   SuperCom.ComInit(Com);

     // now connect ...
   Res = SuperCom.RS_ConnectEx(Com,SuperCom.SEC_10,,"www.adontec.com:80",cbConnectInfoFunc);

The connection set-up can run completely in background. The application receives events about the progress.

Want to compare the above code with the one used for serial modem connections or ISDN to see what is different?

ActiveX API

  Private Sub SCom1_OnConnect(ByVal Action As Integer, ByVal TimeLeft As Long)

     If Action = SCOM_CONNECT_FAILED Then
       Form4.CTL_INFO.Text = "CONNECT FAILED"
     End If
               ' successfully
    If Action = SCOM_CONNECT_OK Then
      Debug.Print "CONNECTED ";
    End If
               ' progress...
    If Action = SCOM_CONNECT_INFO Then
      Debug.Print ".";
    End If

  End Sub

      :
      :

  SCom1.PortOpen=True ' setup a link
      :
  SCom1.ConnectAddress="www.adontec.com:80"  ' server address and port
      :
  SCom1.Connect=True ' now connect

      :

Setting up a connection runs completely in background. The application receives events about the progress.

The same sample for Serial or ISDN ?.

No matter what communication type in use (Serial, TCP/IP or ISDN) it requires only one common SuperCom API to use. The learning curve is extremely low with SuperCom!