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

ParallelEnable

Sets or Retrieves the status of the ParallelEnable property. Enables or Disables Comport Parallel IO.

Available at DesignTime and Runtime. ReadOnly when the port is open.

Only available using the Comm32 ocx. Not supported by MSComm32

         Syntax object.ParallelEnable = value
     
  object Name of the communications control.
  value A boolean expression. True or False Enable or Disable Parallel IO (Default True)
     
  Examples  
    object.ParallelEnable = True '// Set the value
       
   

If object.ParallelEnable = True Then
      MsgBox ("Parallel IO is enabled")
   Else
      MsgBox ("Parallel IO is disabled")
End If

'// Retrieves the value
       

Remarks:

When using Microsoft's MSComm32 control with some USB adapters or virtual com ports you may encounter Run-time error '8020' Error reading comm device. The cause of this error appears to be related to an unexpected hardware device driver error ERROR_IO_PENDING lower down in the windows com driver.

In such case MSComm32 would correctly send data but never be able to receive any data. Calling the .Input method triggers a runtime error 8020

Using the same hardware our Comm32 control might also be affected.

Disabling Parallel IO (set .ParallelEnable=False before opening the port) will often fix this problem.

 

We have found the following hardware to be affected.

  • Texas Instruments TUSB3410
  • Some Bluesoleil device(s) (Bluetooth etc) using their virtual com port drivers
 

 

Copyright (c) 2010 Axis Controls Ltd