Sunny
05-11-2003, 01:58 AM
Dear Richard Grier,
Thanks a lot. I have attempted to use your first suggestion, but failed.
BTW, my computer is connected with serial hardwares of our facility via the
serial port. This method may bring some garbage to other devices, and produce
some negative impact. So, I think, this is not good idea. Therefore, I try
to check the further information about the NETComm.ocx on your homepage (www.hardandsoftware.net),
but failed. My browser told this site is invalid. Would you give me a hand?
Sunny,
Zhiwen_hu@etang.com
----------------------------------------------------------------------
"**** Grier" <****_grier@msn.com> wrote:
>Hi,
>
>If you can send a command and wait for a response from the microscope, or
if
>the microscope outputs data continuously, then this is easy. You just open
>each port in sequence and look for the data you expect. Close the port
and
>move on, if you don't get a response. Save any valid port number (use
>GetSetting SaveSetting to make this easy), to provide the most likely
>starting point.
>
>You have to look into the microscope communications protocol to see what
are
>the required details. I have lots of examples of this sort of thing in
my
>book (see below). However.... None deal specifically with the device that
>you are using, so you'd have to extrapolate.
>
>BTW, perhaps the easiest way to send and receive data in .NET is to download
>NETComm.ocx from my homepage. It is free, and will provide all that you
>need from the serial port interface side.
>
>****
>
>--
>Richard Grier (Microsoft Visual Basic MVP)
>
>See www.hardandsoftware.net for contact information.
>
>Author of Visual Basic Programmer's Guide to Serial Communications, 3rd
>Edition ISBN 1-890422-27-4 (391 pages) published February 2002.
>
>
Thanks a lot. I have attempted to use your first suggestion, but failed.
BTW, my computer is connected with serial hardwares of our facility via the
serial port. This method may bring some garbage to other devices, and produce
some negative impact. So, I think, this is not good idea. Therefore, I try
to check the further information about the NETComm.ocx on your homepage (www.hardandsoftware.net),
but failed. My browser told this site is invalid. Would you give me a hand?
Sunny,
Zhiwen_hu@etang.com
----------------------------------------------------------------------
"**** Grier" <****_grier@msn.com> wrote:
>Hi,
>
>If you can send a command and wait for a response from the microscope, or
if
>the microscope outputs data continuously, then this is easy. You just open
>each port in sequence and look for the data you expect. Close the port
and
>move on, if you don't get a response. Save any valid port number (use
>GetSetting SaveSetting to make this easy), to provide the most likely
>starting point.
>
>You have to look into the microscope communications protocol to see what
are
>the required details. I have lots of examples of this sort of thing in
my
>book (see below). However.... None deal specifically with the device that
>you are using, so you'd have to extrapolate.
>
>BTW, perhaps the easiest way to send and receive data in .NET is to download
>NETComm.ocx from my homepage. It is free, and will provide all that you
>need from the serial port interface side.
>
>****
>
>--
>Richard Grier (Microsoft Visual Basic MVP)
>
>See www.hardandsoftware.net for contact information.
>
>Author of Visual Basic Programmer's Guide to Serial Communications, 3rd
>Edition ISBN 1-890422-27-4 (391 pages) published February 2002.
>
>