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

InbufferSize

Sets or Retrieves the size of the Input (receive) buffers.

Available at Design time and Runtime. Read Only While the port is open.

MSComm32 and Comm32 have Similar but not identical behavior See Remarks below

         Syntax object.InbufferSize = value
     
  object Name of the communications control.
  value A numerical expression indicating the size of the receive buffer.
     
  Examples  
    object.InbufferSize = 4096 '// Set the value
       
    Text1.Text = object.InbufferSize '// Retrieves the current size of the buffer
       

Remarks:

When set before the port is opened. This value takes effect (memory is allocated) when the port is opened.

Differences in behavior between MSComm32 and Comm32

MSComm32
Maximum value is a (short) integer. (32k)

Comm32
Maximum Buffersize is a Long Integer

Important: If removing MSComm32 from an existing project and replacing it with Comm32 remember that MSComm32 limited this property to a 32k “Short” Integer value. If using larger buffers you will of course remember to use variables of a larger data type to receive/process return values etc.

 

 

 

 

Copyright (c) 2010 Axis Controls Ltd