Serial NET class library, Serial Communication Library for Windows, ActiveX Component, MSComm replacement, NET class library,rs485, Zmodem file transfer, Protocol, xmodem, xmodem/crc, xmodem-1k, SIEMENS Simatic 3964 Protocol LSV2 RK512 LSV/2 Protocol Ymodem, tcp/ip Isdn Capi, Delphi Pascal builder Visual Basic vba C++ c# GSM/GPRS Modem and TAPI, .NET Visual Studio serial component, 64 bit, Kermit Protocol Modbus, serial library toolkit, 64 bit software

Q: What is the SuperCom .NET Class Library ?
A: The SuperCom .NET Class Library unfolds the SuperCom functionality under NET. The SuperCom .NET Class Library is offering a native way of using SuperCom under a .NET development environment.

Q: Is it a lite version of some SuperCom package ?
A: Absolutely not! The SuperCom .NET Class Library is DUAL API and may provide even more functionality in some areas than the ActiveX control or the DLL API on it's own. You get access not only to standard protocols (XMODEM, YMODEM, ZMODEM, KERMIT, ASCII,...) but also to any other industrial protocol (e.g. MODBUS, 3964, RK512, AS511, LSV/2), if included with the SuperCom license you own.

The SuperCom .NET Class Library can control serial lines, TAPI, ISDN, TCP/IP connections based on the SuperCom license you own. If included within your license, you can control it (see Software and Features).

Q: How is it comparing to SerialPort ?
A: The SuperCom TSCom class is way ahead of SerialPort. With SuperCom you get a professional data communication library which includes most wanted data communication functions, file transfer protocols, sophisticated background control, intelligent data collectors, event driven data communications, one API for Serial, TCP/IP, ISDN, ... With SuperCom you avoid the many known limitations and issues when using SerialPort e.g. Encoding issues, data throughput, timing and latency, hardware and driver compatibility issues and many more. SuperCom is a specialist on data communications, actively developed and supported. A SerialPort clone class is also included on a "as-is" basis without support.

Q: Can I use that SerialPort clone included ?
A: The SerialPort clone class is a research project and included with source code only to be used for tests and research. It is not supported. Using the class TSCom or SuperCom is the only way to get the advanced features of SuperCom.

Q: Why is it not offered separately ?
A: This would definitely limit you on the type of library, API and compiler you can use (More). Based on it's content, it would not be priced differently than the SuperCom package containing it now.

Q: Why not use the ActiveX control instead of this class library ?
A: This is definitely your choice. We provide you with all kind of libraries (DLL, ActiveX, .NET Class) and you decide which one to use. We provide you with tools and libraries that are not bound to a specific compiler or development environment. You are free to use the compiler that fits better or even combine some in order to get the best result (e.g. C++ to create a DLL, Delphi, Visual Basic or C# to build the GUI).

Q: What are the limitations using it instead of using the SuperCom ActiveX control?
A: None. The SuperCom .NET Class Library offers the same amount of functions, protocols, events, methods, properties as the SuperCom DLL API and the SuperCom ActiveX API. The SuperCom .NET Class Library is DUAL API and may provide even more functionality in some areas than the ActiveX control or the DLL API on it's own. Using the ActiveX API included with the class library (class TSCom) offers the same and more as the ActiveX control.

Q: Does it offer similar events as the ActiveX control ?
A: Yes. The same amount of events and even more details are available. Due the different kind of interfaces there are some minor differences in the declaration (see some .NET samples).

Q: Is it possible to replace the MSComm control with the SuperCom .NET Class Library ?
A: Yes. The same methods, properties, events offered. Some minors changes may be required due the different kind of interfaces but this is not really time consuming. Small projects may replace within a few minutes.

Q: Is it possible to replace the SerialPort class with the SuperCom .NET Class Library ?
A: The SuperCom .NET Class Library does also include a SerialPort class offering similar functions (a subset of).

Q: Is it possible to develop console application ?
A: Yes, the SuperCom .NET Class Library can be used within a console application. Many samples are available.

Show a short console app.

The following sample is using the ActiveX API like class "TSCom" of the SuperCom .NET Class Library within a console application.

Establish a serial file transfer (Tx, Rx)

C# console sample


using ADONTEC.Comm;  // see C# source in SComClass.cs
                     // VB Net references the class DLL

namespace CSharpTxRxFileConsole
{
   class Program
   {
      public class MYSCOM : TSCom
      {
         public MYSCOM(int CommId) : base(CommId)
         {
         }

         // Optional but handy event functions
         protected override void OnComm(OnCommEventArgs e) [OnComm +-]
         {
            base.OnComm(e); // call base class

            int SComEvent = (int)e.EventCode;

            if ((SComEvent & SuperCom.EV_RXCHAR) == SuperCom.EV_RXCHAR)
            {
               // Rx data available, do any further processing here
            }
            if ((SComEvent & SuperCom.EV_TXEMPTY) == SuperCom.EV_TXEMPTY)
            {
               // Tx buffer empty, do any further processing here
            }
            if ((SComEvent & SuperCom.EV_TRIGGER) == SuperCom.EV_TRIGGER)
            {
                // a file receive (or transmit) request
                // or a special user data packet received ?
                // Start receiver or handle data packet
               TriggerSignaled nTriggerId = this.TriggerSignaled; // which one?
               if (nTriggerId == TriggerSignaled.SCOMM_TRIGGER_IS_ZMODEM)
               {      // start zmodem receiver to run in background
                     SCom.FileName = "";
                     SCom.Protocol = Protocol.PROTOCOL_ZMODEM;
                     SCom.FileReceive = true; // go get it - no blocking!
               }

               :

            }

            :
            :

         } // OnComm
         protected override void OnFile(OnFileEventArgs e) [OnFile +-]
         {
            base.OnFile(e); // call base class

            switch (e.Action)
            {
               case SuperCom.acFILENAME:
                  s = "OnFile-Name=" + e.FileName;
                  break;

               case SuperCom.acRXING: // Rxed one data packet
                  s = "acRXING, at " + (e.Data).ToString();
                  break;
               case SuperCom.acTXING: // Txed one data packet
                  s = "acTXING, at " + (e.Data).ToString();
                  break;

               case SuperCom.acRXFIN: // Rx complete
                  s = "acRXFIN" +  "(" + TFQFileCount.ToString() + ")";
                  break;
               case SuperCom.acTXFIN: // Tx complete
                  s = "acTXFIN" + "(" + TFQFileCount.ToString() + ")";
                  break;

               case SuperCom.acUSERBREAK:
                  s = "acUSERBREAK" + "(" + TFQFileCount.ToString() + ")";
                  break;
               case SuperCom.acQUEUEFIN: // All queued files Txed or Rxed
                  s = "acQUEUFIN" + "(" + TFQFileCount.ToString() + ")";
                  break;

                  :
                  :
            }

            Console.WriteLine("OnFile-Event=" + s + Environment.NewLine);
         } // OnFile

      }  // MYSCOM


      static void Main(string[] args)
      {
         Console.WriteLine(" CSharpTxRxFileConsole " + Environment.NewLine);

         MYSCOM SCom = new MYSCOM( SuperCom.COM_1); // create instance

         // Set some comm parameters
         SCom.ComType = ComType.COMTYPE_RS232; // *) serial, TAPI, TCP/IP, ISDN
         SCom.Settings = "115200,N,8,1";
         SCom.Handshaking = Handshaking.SCOMM_HANDSHAKE_NONE;

         Console.WriteLine("Opening port/channel" + Environment.NewLine);
         SCom.PortOpen = true; // // Ready to start action...

         if (SCom.PortOpen == false)
         {
            Console.WriteLine(" failed to open port/channel." + Environment.NewLine);
            SCom = null;
            return;
         }

         // OK so far we own an open port/channel now prepare environment e.g. DownLoadDir
         SCom.FileDownLoadDir = @"c:\adtmp";

           // Any Trigger to add for automated receive of files ?
         SCom.TriggerAction = TriggerAction.SCOMM_TRIGGER_ADD_ZMODEM;
         SCom.TriggerAction = TriggerAction.SCOMM_TRIGGER_ADD_KERMIT;


           // prepare for file transmission
         SCom.Protocol = Protocol.PROTOCOL_ZMODEM;
         SCom.FileName = "c:\\sales*2012.txt";

         Console.WriteLine("Starting transmition of " + SCom.FileName + Environment.NewLine);

         SCom.FileTransmit = true;  // send now

              :
              :

         // Lets assume we want also to receive file(s)
         // While we do a simple busy wait here SuperCom may receive files in background
         ConsoleKeyInfo cki;
         do
         {
             Console.WriteLine(".. now waiting to receive file(s). ");
             Console.WriteLine("Start Sender or press 'E' key to end .. " + Environment.NewLine);
             cki = System.Console.ReadKey();
         } while (cki.Key != ConsoleKey.E);

         :
         :

         Console.WriteLine(Environment.NewLine + "Closing the port...");

         SCom.PortOpen = false; // close port/channel, free communication index

         Console.WriteLine(" .. done." + Environment.NewLine);

         :
      }

   }
}

* One point to select the desired communication type!.

Q: Is the source code of the SuperCom .NET Class Library included ?
A: Yes! The SuperCom .NET Class Library is included completely with its C# source code. The source code offers a huge source of insights and informations and also ensures your investment - you can use it as is or recompile with any .NET CLR (e.g. CLR 1.x, 2.0, 3.x, ...)!
It may contain nearly 10,000 lines of C# code, but, don't fool yourself, it contains only the source code of the .NET class library and not the complete SuperCom library!

Q: Why are you bundling that much in each SuperCom package ? «
A: Well, we offer tools for professionals, not for the hobbyist, even if a lot of them are also using it and we're really happy about it.
With software you have no extra cost shipping some MB more and the intention is to give to software developers the freedom to choose the library, functions, protocols and even the compiler that will produce the best results. Finaly no one is using 100% of any software.
With SuperCom we're working on building bridges, not boundaries. The product is fairly priced since the audience are not only Fortune 100 Companies but also Small IT Business, Engineers and Freelancers.
We love to get the call from customers requesting updates for software running out in the field for more than ten years!

Q: Why don't you offer trial version?
A: We do a lot more. We provide ready-made DEMO software that show nearly all of what is possible, saving you time while you're testing for hardware, operating system or protocol compatibility. The source code of the DEMO is also included with the product. Many samples for many compiler, on this web site, show functions an how to use.
If you are novice in software development or just unsure which product to select, we gladly assist. eMail your requirements and we will return to you fast. What we offer is guaranteed to work as documented and we provide fast and accurate technical support to our customers.
We cannot provide that service for playing around with trial software, sorry!

Q: What kind of NET samples are included ?
A: The SuperCom .NET Class Library includes many samples mainly for C#, C/C++ and Visual Basic NET. Depending on the owned SuperCom package, it may include samples for Serial, Modem, TAPI, TCP/IP client/server, Modem & TAPI server, server for multiple type of connections (Serial, Modem, TAPI, TCP/IP, ISDN), samples transmitting files, handling trigger, collecting data packets, monitoring data, samples for industrial protocols (e.g. (S5) 3964, RK512, AS511, LSV2, MODBUS, SuperCom Heidenhain Library, S7 ISO-on-TCP).

Some of the NET Samples:

CSharp, VBNet, CSharpOnComm, CSharpOnFile, CSharpSuiteOnComm, CSharpOnCommConsole, CSharpTxRxFileConsole, VBNetOnConnect, VBNetServer, VBNetClient, CSharpTcpServer, CSharpTcpServerConsole, CSharpTcpOnFile, AppMultiServer, AppMultiServerDLLAPI, CSharpModemServerConsole, CSharpGateWay, VBNetXFile, ...

Some of the above samples are originating or were used in real-world applications.
The manuals do also present small samples and code slices.

SuperCom for the .NET FrameWork FAQ Data Communications

SuperCom for the .NET FrameWork FAQ
Data Communications