🚀 go-pugleaf

Ramy wrote:

>>CreateFile(...);
>>BuildCommDCB(...)
>>SetCommState(...)
>>SetCommTimeouts(...)
>>
>>What exactly do you say, that i can remove the call for the 
>>SetCommState() function? ( i prefer to use BuildCommDCB() 
>>becouse it's giving me much more control ).
>
>Sorry, i ment to say that i prefer to use 'SetCommState' (not
>BuildCommDCB() as i said ) becouse it's giving me much more 

Yes, use SetCommState, I never ever mentioned not using SetCommState.

>control as you see in the large DCB init part at the begining 
>of the function.

Ok, see all of that "large DCB init part at the begining" ?
That's all going to waste because after that, you are calling
BuildCommDCB() which completely replaces all of those settings.
(Help says it only replaces some of them, but it's pretty obvious that
it is replacing some that you don't want replaced)

You do this ( just a small bit of your code):
my_DCB.BaudRate = SystemInfo.ComInfo.BaudRate;
my_DCB.ByteSize = 8;
my_DCB.Parity   = (char)SystemInfo.ComInfo.Parity;

Then you do this:
BuildCommDCB( "COM1:9600,S,8,1", &my_DCB )
Which internally does this:
my_DCB.BaudRate = 9600;
my_DCB.ByteSize = 8;
my_DCB.Parity   = 4

And, it goes on to reset all of the other settingsin my_DCB to
whatever Bill Gates thinks is best for you.

My suggestion is to either Not use BuildCommDCB at all, because it
just overrides all of your settings, or use it *first*, and then
override the automatic settings with your own.

So...One of these:

my_DCB.BaudRate = SystemInfo.ComInfo.BaudRate;
my_DCB.ByteSize = 8;
my_DCB.Parity   = (char)SystemInfo.ComInfo.Parity;
 . . .  etc . . .
SetCommState

 - - Or - -

BuildCommDCB( "COM1:9600,S,8,1", &my_DCB )
my_DCB.fBinary  = true;
my_DCB.fParity  = 1;
(whatever else you need setting that BuildCommDCB didn't set for you )
SetCommState