You have to parse the command.

You can use the udata_overlay directive to create some meanful variables  to
overlay your (input) buffer.  Then use them via xor to check for equality in
certain places.
Then pull your important data in here and there.  Unless you do some string
compares
or tokenizing of your buffer, I believe, the above is the only way to do it.
That's
the way I do it and seems OK.

You may check for your terminating char in your interrupt comms routine.
You can do a bit of sanity checking on the fly in the intterupt routine too.

It sorta depends on how time critical the various aspects of your system are
as to where you do what checks.

GL,
Walt.....

-----Original Message-----
From: David VanHorn [mailto:dvanhorn@CEDAR.NET]
Sent: Tuesday, March 28, 2000 6:03 PM
To: PICLIST@MITVMA.MIT.EDU
Subject: Re: Command interpreters


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

At 02:46 PM 3/28/00 -0800, Mark Newland wrote:
>You didn't say if you were watching for this on a PIC or on your PC.  If on
>your PC thu the serial port, Telix or Procomm or some other terminal
program
>with a built-in programing language may do.

The PC would be easy, but no, it's got to go in the little black chips :)

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.2 for non-commercial use <http://www.pgp.com>

iQA/AwUBOOFkT4FlGDz1l6VWEQKyxACeMsJXgXM8GbJbl4PMi8hpvgUgb0oAn39Z
qvJPco8oAC6a6D9aLmxoAyHG
=+Ked
-----END PGP SIGNATURE-----