Asynchronous Serial Communication ActiveX and components for rs-232, rs-422, rs-485. Protocols ZMODEM, YMODEM, YMODEM-G, XMODEM, XMODEM-1K, KERMIT, MODBUS, 3964, RK512, LSV2. Supporting NET, C#, VB Net
Serial Communication ActiveX and components for asynchronous rs-232, rs-422, rs-485 Supporting NET, C#, VB Net. Protocols ZMODEM, YMODEM, YMODEM-G, XMODEM, KERMIT, MODBUS, 3964, RK512, LSV2.
Access to high numbered COM ports as COM17, overcome error 8020, KB318784. MSComm In Binary Input Mode, replace PDQComm
SuperCom™ ActiveX
ActiveX API for Windows 7, Vista, Windows XP/2000/Server 2003/Server 2008/NT/ME/98/95
Communication Control
The SuperCom RS-232 ActiveX is a professional serial communication component library (OLE Custom Control) for serial communication interfaces (RS-232, RS-422, RS-485). The SuperCom RS-232 ActiveX supports common Windows development environment and provides the programmer with properties, methods and the events in order to develop data communication applications. It's downward compatibility with the MSComm control makes it very easy to integrate into existing applications. See how to replace MSComm with ease.
Time is valuable. Developing communication software with the SuperCom ActiveX is extremely easy and starts by placing the ActiveX icon on a Windows Form.
SuperCom also provides intelligent functions that considerably speed-up the development process and produce fast, reliable solutions avoiding delaying or blocking of your application.
Communications Events
Applications using the SuperCom ActiveX can work event driven. The SuperCom ActiveX reports the events OnComm, OnDataPacket, OnConnect and OnFileInfo. The reported events enable the application to manage other tasks simultaneously while communications or file transfer last.
- The OnComm event reports changes in the status lines e.g. CTS, DSR or RING, when characters were received or when communication errors occur.
- The OnDataPacket event informs about the status of observed data packets for instance if an observed data packet is received.
- The OnConnect event provides information during the setup of a connection (e.g. modem dialup).
- The OnFileInfo event provides status information during the file transfer. A progress dialog and/or file transfer statistics can be updated.
|
Enhanced Communications Events
The SuperCom ActiveX reports about 30 different communications events. The enhanced event reporting mechanism in SuperCom ActiveX enables you to receive events on any defined character (e.g. EOF(26), STX, ACK, NAK, etc).
Polling Mode
The SuperCom ActiveX also supports the polling mode of operation. This means to obtain with methods and properties the state of the status lines and to check the data flow for communication errors without the need to react on events.
File Transfer
High speed file transfers tasks are very easy to accomplish. The following widely used standard protocols ZMODEM, YMODEM/BATCH, YMODEM, YMODEM-G, XMODEM-1K, XMODEM/CRC, XMODEM, KERMIT and ASCII are included. The SuperCom ZMODEM protocol includes important features like "crash recovery", 32bit CRC and "batch file transfer". In fact, these protocols are running very stable since 1991.
MSComm Compatible
The SuperCom ActiveX is compatible with the MSComm control and thus it's very easy to update existing applications using it. Replacing MSComm with SuperCom ActiveX is a fast and smooth operation.
Summary
Using the SuperCom ActiveX up to 255 ports / connections can be opened simultaneously within the same application.
Start as many instances of your application - no limit set.
Lengthy functions like file transfer, connecting or observing the data stream for special data packets or strings are working in background and your application can complete other taks in the meantime. It does not "freeze" waiting on a lengthy function to complete.
|
ActiveX Technology - ActiveX API It's the same ActiveX module shipped with other SuperCom packages too, like SuperCom for TCP/IP, SuperCom for ISDN, SuperCom 3964 Engine, SuperCom Suite,... This is achieved by implementing the SuperCom ActiveX above the portable SuperCom API. Why bother with different tools and different API to solve your communications needs, if you can solve it with one !
|
SuperCom ActiveX API - Features List
Common Features List (valid for Serial, TCP/IP and ISDN )
SuperCom provides intelligent functions that considerably speed-up the development process and produce reliable solutions. More...
- DataPacket1 - Receive data packets based on some definitions. More...
- Trigger1 - Trigger events when custom data packets or strings received. More...
- DataFilter2 - Low level data filtering functions e.g. define ready made data filter or inspect and change data while received or transmited with custom functions. More...
- Data Monitoring2 - Low level data monitoring functions, Integrated Debugging Library
- Event Reporting - Thread-safe event reporting and synchronization with Windows controls or runtime library.
- Threaded File Queue™ 1 - File transmission using queues, working completely in background!
- Connecting in background - The connection attempt is working completely in background. The application does not freeze!
- ZMODEM File Options - Instructions for the file receiver.
- ZMODEM/8k block option and the powerfull ADONTEC extension ZMODEM/32k (ZMODEM/64k shipped on request). More...
- KERMIT Protocol
- Integrated TAPI support.
- Very Large Rx and Tx Buffers - Overcome known limitations.
... and many other functions and protocol extensions.
____
1 Best utilized in a SuperCom DUAL API package
2 Requires a SuperCom DUAL API package (see also Software and Features)
|
Especially for RS-232, RS-422, RS-485
- Up to 255 serial ports opened simultaneously (e.g. COM1 to COM255) and/or up to 255 connections simultaneously
- Supports the MSComm compatible methods and properties. More...
- Powerfull flow control (RTS/CTS, DTR/DSR, XON/FOFF, etc.)
- Any baud rates supported by the hardware e.g. up to 921600 Baud (921,6 Kbps)
 SuperCom accepts any baudrate supported by your hardware. The Windows dialog 'control panel/hardware' may not always provide accurate information on this. Please consult the hardware manual.
Often used standard PC bit-rates i.e. 5, 50, 110, 150, 300, 600, 1200, 4800, 7200, 9600, 12800, 14400, 19200, 23040, 38400, 57600, 115200 bps and through add-on serial cards 230400, 460800 and 921600 bps. Other serial hardware may support additional bit rates.
- Dial-up connections using Modem (Hayes compatible)
- Dial-up connections using TAPI (Windows Telephony API)
- Dial-up connections using USB Modem
- Dial-up connections using GSM/GPRS Modem
- Supports USB to RS-232 / RS-485 adapters / converters
- Redirected ports through the Windows Remote Desktop Protocol (RDP)
 Serial ports located on a remote computer.
- Support for Virtual serial ports e.g. COMM ports routed to an Ethernet PortServer/CommServer.
|
|
Some SuperCom ActiveX - Properties
Note: The ComTypes RS-232, RS-422, RS-485 and TAPI are included in the SuperCom RS-232 ActiveX. The ComTypes TCP/IP Server and TCP/IP Client are included in the SuperCom for TCP/IP for Windows
. The ComType ISDN is included in the SuperCom for ISDN for Windows
. All ComTypes listed above are included in the SuperCom Suite
.
Please also see the chart of Software and Features and the available product range for more details.
Example 1
(The following briefly shows a simple example of the control operation using Visual Basic)
Visual Basic Sample
Sub Form_Load()
' Select COM2
SCom.CommPort = 2
' is it available ?
If SCom.PortPresent(SCom.CommID) <> SCOM_PORT_AVAILABLE_READY Then
Exit Sub ' COM2 not available
End If
' set comm params
SCom.Settings = "115200,N,8,1"
' activate comm port
SCom.PortOpen = True
' send data
SCom.Output = "Hello World"
' receive data
s = SCom.Input
:
' close comm port
SCom.PortOpen = False
End Sub
Private Sub SCom_OnComm() 'Event function
Dim scEvent As Integer
' get the event code
scEvent = SCom.CommEvent()
If scEvent = SCOMM_EV_SEND Then ' or comEvSend
' all data sent, buffer is empty
End If
If scEvent = SCOMM_EV_RECEIVE Then ' or comEvReceive
' call SCom.Input to collect the received data,...
Call ReadChars
End If
If scEvent = SCOMM_EV_CHAR Then
' User defined special char received e.g. EOF (26), NAK, STX
Call HandleSpecialData
End If
:
:
End Sub
Private Sub SCom_OnDataPacket(Action, Data)
' The parameter Action informs about the current status.
' The parameter Data delivers the captured data packet
' OK, data available
If Action = SCOMM_DATAPACKET_OK Then sAction = "DATAPACKET OK"
' failed but some captured data may be available
If Action = SCOMM_DATAPACKET_NOK Then sAction = "DATAPACKET NOK"
' error e.g. some property values provided was wrong
' check values of used "DP..." properties
If Action = SCOMM_DATAPACKET_ERR Then sAction = "DATAPACKET ERR"
:
:
End Sub
Private Sub SCom_OnFileInfo(Action, Data)
Select Case Action
Case SCOM_RXING
S1 = "RXING"
Case SCOM_TXING
S1 = "TXING"
Case SCOM_RXFIN
S1 = "RXFIN"
Case SCOM_TXFIN
S1 = "TXFIN"
Case SCOM_QUEUEFIN
:
:
End Select
End Sub
Private Sub SCom_OnConnect(Action, TimeLeft)
If Action = SCOM_CONNECT_FAILED Then
Debug.Print "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
|
Example 2
(Setup connection)
ActiveX: Client Connection - OnConnect
Visual Basic Sample
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
Form4.CTL_INFO.Text = "CONNECTED"
End If
' progress...
If Action = SCOM_CONNECT_INFO Then
Form4.CTL_INFO.Text = "CONNECT INFO ..."
End If
End Sub
:
:
SCom1.PortOpen=True ' setup a link
:
SCom1.ConnectAddress="555-1234"
:
SCom1.Connect=True ' now connect
:
|
See the same for TCP/IP or ISDN.
The connection setup runs completely in background. The application receives events about the progress. It does not matter which communication link it uses (Serial, TCP/IP or ISDN) it will require one common SuperCom API to use. The learning curve is extremely low with SuperCom!
Content of "627, SuperCom 6 RS-232 ActiveX"
- ActiveX incl. runtime DLLs for serial communication (RS-232/422/485 and TAPI)
- Samples and Documentation
See also the the available product range for more available packages and details.
Compatibility
The SuperCom ActiveX can be used with any Windows 32 Bit ActiveX enabled development environment including Visual C++, C#, C++Builder, Delphi, MS Office (VBA), FoxPro, LabView, PowerBuilder, Visual Basic, Visual Basic .net etc.
The SuperCom ActiveX seamless intergrates with Visual Basic, Visual C++, C++ Builder, Delphi, VBA (e.g. Access, Excel, Word), FoxPro, LabView, PowerBuilder, C#, Visual Basic .net, MS .NET and other ActiveX enabled development environment.
Sample Applications
Complete sample applications written for Visual C++, Visual Basic, VBA (Visual Basic for Applications), C++ Builder, Delphi, C#, Visual Basic .net, PowerBuilder etc. are included in full source code.
Executables developed using the SuperCom ActiveX can be distributed royalty free.
System requirements
Windows 95, Windows 98, Windows Me, Windows NT, Windows 2000, Windows Server 2003, Windows Server 2008, Windows XP, Windows Vista, Windows 7.
The alternative to MSComm and PDQComm 
Steps to replace MSComm
Replacing the control
- Remove the MSComm icon from the form or dialog it was on
- Drag an Drop the SuperCom ActiveX icon onto the form or dialog
- Update the Name property of the SuperCom ActiveX from SCom1 to reflect the name used with the MSComm e.g. MSComm1
- Compile the application
FAQ on MSComm ?
How to replace PDQComm
Is it possible to replace
PDQComm also ?
The
SuperCom ActiveX is also used to replace PDQComm. In most cases it's the same procedure as with the
MSComm. The
PDQComm contains much more functions than the
MSComm. Some functions may be named differently in
SuperCom or use a different number of paramerers. Thus a small rework may be needed to complete.
PDQComm may also include functions or protocols that may not be included in
SuperCom ActiveX. Even if you don't use them a detail check helps to better estimate the amount of rework required.
Replacing the control
- Remove the PDQComm icon from the form or dialog it was on
- Drag an Drop the SuperCom ActiveX icon onto the form or dialog
- Update the Name property of the SuperCom ActiveX from SCom1 to reflect the name used with the PDQComm e.g. Comm1
- Compile the application and locate what's missing
- If required, change function name or constant names
- If required, replace function, ..., Compile, ....