I was suggesting that he start off with the simplest implementation possible:
No interrupts (RThreshold=0)
No Handshaking

After he gets it working there, then he can add the other stuff as needed.

-Adam

Heinz Czychun wrote:
>
> Hi Joe,
>
> At 3:48 PM 3/2/2000, M. Adam Davis wrote:
> >I have dealt with the MSCOMM control in VB quite a bit, and there really isn't
> >much to go wrong, but here are a few ideas:
> >
> >First, make sure your PIC is transmitting soething, tie an LED to the tx or
> >something.
> >
> >Check to make sure the aires are going in all the correct places (tx-rx rx-tx,
> >etc)
> >
> >Make sure the following settings are correct on your MSCOMM control:
> >mscomm.Handshaking = 0          'comNone, ie no handshaking
> >mscomm.Settings = "9600,n,8,1"  'or set it according to your needs
> >mscomm.Inputmode = 0            'Use text input mode unless you know
> >                                'what you are doing
> >mscomm.InputLen = 0             'When you call mscomm.input, get the
> >                                'entire buffer
> >mscomm.RThreshold = 0           'Poll the port for characters, don't try to
> >                                'do interrupts untill you are receiving well
>
> I'm not sure if this has anything to do with interrupts, but I've been
> working on a MFC C++ terminal emulation example and it has a comment about
> the RThreshold property;
>
> // Set Rthreshold proprty to 1. THe default RThreshold value (0)
> // causes the OnComm event to NOT fire when a character is detected
> // in the serial port.
>
> >mscomm.NullDiscard = False      'Don't let VB throw 0x00 away.
> >
> ...<snip>...
>
> Heinz