cdholding image

comm32 home
comm32 forum
buy comm32

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
   .ReadBytes
   .ReadString
   .WriteBytes
   .WriteString

OnComm Event
Hardware/Cables etc

Handshaking

Sets or Retrieves the Handshaking/flow control method used by the com port

MSComm32 and Comm32 have similar behavior. (See Remarks below)

         Syntax object.Handshaking = value  
       
  object Name of the communications control.  
  value A numerical expression indicating whether flow control is enabled and what method to use.
       
    object.Handshaking = 0 '// Set the value (0 = no flow control)
       
    If object.Handshaking = 0 then
   MsgBox("Handshaking is disabled ")
 Else
   MsgBox("Flow control is enabled")
End If
'// Retrieves the current setting.
       
    This property can be set to one of the following values
  Constants 0 = comNone
1 = comXOnXoff
2 = comRTS
3 = comRTSXOnXOff
'// Flow control is disabled (Default)
'// Use XonXoff
'// Use RTS/CTS
'// Use both

Remarks

Under some Handshaking conditions MSComm32 can cause an application to hang, appear unresponsive or lose data. This is actually a low level comTimeOut problem in the Windows com driver of NT based operating systems, W2000, XP, Vista, Win7 etc. This problem does not occur with Comm32.

 

 

Copyright (c) 2010 Axis Controls Ltd