Serial Comm Component

[Padu]

Hi Everybody,

I'm a newcomer from the Delphi world and I'm going to start developing my
new project (a robot control app) in C#. One of the requirements is to
communicate using RS232 (well, RS485, but the app doesn't care really).

I was googling a bit and I saw a couple of good articles using P/Invoke, and
I'll probably do that, unless I find something like Turbopower's Async (find
them on sourceforge.net). It is a very powerful communication package
designed for delphi that I've been using for many years. They don't have it
for .net (well, they have an activeX package, but I prefer something that is
native to the framework). Do you know of any package for .net that is
comparable? Async is free, so if I could find a free package here too,
that'd be a bliss.

Cheers

Padu

 

[Gabriel Magaña]

A couple things:

- .net 2.0 (vs 2005) contains a built-in class to access serial ports

- Delphi 8 and above can compile .NET, so theoretically you could download
the source to AsyncPro and compile it for .net.

 

[Bob]

Hi Padu
Try
http://www.hardandsoftware.com/
Richard Grier has done a lot of work on serial comms and there is a
NetCom.ocx that he has available free.

..Net release 2 has System.IO.Ports.SerialPort class

HTH
Bob

 

[Padu]

A couple things:

- .net 2.0 (vs 2005) contains a built-in class to access serial ports

- Delphi 8 and above can compile .NET, so theoretically you could download
the source to AsyncPro and compile it for .net.

Aha... just looked at the poster that came with VS2005, and here it is...
System.IO.Ports.SerialPort, and an orange "NEW!" besides it. Thanks

Regarding the delphi conversion, I doubt it will work, since Async is a VCL
package. I have Delphi 2005, I'll try it though.

Cheers

Padu

 

[Gabriel Magaña]

Regarding the delphi conversion, I doubt it will work, since Async is a

VCL package. I have Delphi 2005, I'll try it though.

Well, delphi does VCL under .NET... At least if the Indy project could be
ported to .NET, then AsyncPro should be portable as well, it seems to be a
simpler project than Indy... Anyway, I would use the built-in class though,
nothing's better than the real thing...

 

[Lee]

Gabriel Magaqa enlightened me by writing:

Well, delphi does VCL under .NET... At least if the Indy project
could be ported to .NET, then AsyncPro should be portable as well, it
seems to be a simpler project than Indy... Anyway, I would use the
built-in class though, nothing's better than the real thing...

Yeah, I've been using Indy with Delphi for a few years and I'm a big
fan. But in .net, I'm using System.Net. Although I may give
NSoftware's IPWorks .net package a try. I used their quickbooks VCL in
a Delphi app a couple years ago and was very happy with it.

--
Warm Regards,
Lee

"Upon further investigation it appears that your software is missing
just one thing. It definitely needs more cow bell..."

 

[Floyd Burger]

APRO won't build in Delphi.NET, there are too many pointers, assembly
blocks...heck, it hardly compiled in Delphi<g> Some of the TurboPower guys
formed a .NET component company, and their TransPort library is is pretty
good (I've been using it for about 2 years in everything from motor
controllers, scanners, card readers all the way down to modems). their site
is www.componentscience.net, they don't have a free version, but it's been
well worth my investment.

 

[Padu]

"Floyd Burger"

APRO won't build in Delphi.NET, there are too many pointers, assembly
blocks...heck, it hardly compiled in Delphi<g> Some of the TurboPower
guys formed a .NET component company, and their TransPort library is is
pretty good (I've been using it for about 2 years in everything from motor
controllers, scanners, card readers all the way down to modems). their
site is www.componentscience.net, they don't have a free version, but it's
been well worth my investment.

That's very nice to know. I could recognize a few components from APRO
there. The nice thing about packages like this one is the ability to send
and receive packets. You don't have to worry about cumbersome state
machines.
The only thing is that I'm going to use it for my thesis project, and not
here at the office where I work, so $500 out of my pocket is seldom
justifiable in this case.

Thanks!

Padu