Comm32 Communications OCX

Introduction
Install Comm32
Why Not MsComm?

Properties
   .Break
   .CDHolding
   .CommEvent
   .CommPort
   .CTSHolding
   .DSRHolding
   .DTREnable
   .EOFEnable
   .Handshaking
   .InBufferCount
   .InBufferSize
   .Input
   .InputLen
   .InputMode
   .NullDiscard
   .OutBufferCount
   .OutBufferSize
   .OutPut
   .ParityReplace
   .PortOpen
   .RThreshold
   .RTSEnable
   .Settings
   .STHreshold

Comm32 Properties
   .DeviceName
   .EOFChar
   .EvtChar
   .EvtCharEnable
   .OutPutEx
   .OutPutMode
   .ParallelEnable
   .TxTimeout

Comm32 Functions
   .getByte
   .GetPortStatus
   .InstalledDrivers
   .putByte
   .PortExists

OnComm Event
Hardware/Cables etc

Use the Comm32 ocx to quickly add Serial Communications capabilities to your applications.
Comm32 is compatible with MSComm in that it uses the same property names, methods and syntax which means that you can quickly add Comm32 to a VB6 project in place of MSComm32 without needing to change any of your code or learn any new syntax. (also works for other languages with minor syntax changes.)

Comm1.CommPort = 23
Comm1.Settings = "9600,n,8,1"
Comm1.PortOpen = True

Comm1.Output = "Hello World"

Do While Comm1.InBufferCount > 0
Text1.Text = Text1.Text & Comm1.Input
Loop

Comm1.PortOpen = False

'// Simple ?

'// Use ANY com port
'// Setup the com port
'// Open the com port

'// Send some data

'// Is there any incoming data ?
'// Receive data

'// Close the port

But why not use MSComm32 ?

Anyone who has used MSCom for even a short length of time will have identified a number of shortcomings - For example. MSCom only supports comports 1 to 16.

But serious developers will eventually notice other, more problematic, 'features' where applications become unresponsive or appear to 'freeze' for extended periods (or forever !) as well as unexplained data loss etc. More Info >

In a many cases we've expanded the range of a property. For example buffer sizes with MSComm are all limited to 32k. In fact if you understand com ports you may not want larger buffers anyway - but you're the developer and if you want to stack a huge file into the transmit buffer and go away and do something productive while Comm32 transmits it all in the background then who are we to argue.

Comm32. Same as MSComm32 but better.

32bit development in VB6 using the Comm32 Communications OCX ?

Or are you looking for a proper .Net Component ?

Carry on using most of the common and well documented MSComm32 syntax but with a proper .net component allowing you to build x86, x64 and AnyCPU projects using Visual Studio 2005, 2008 and 2010.