🚀 go-pugleaf

Ramy wrote:


>Hi, i don't know what's happened but suddenly it's stoped working,
>few hours ago i checked it and it wokred just fine, the parity
>flag 'fParity' was '1' ( = Enabled ) and i saw on the scope 
>device the parity bit, but suddenly it stoped working, here is 
>my code, near it's bottom you can see the line "k = k;" , just 
>after i sucessfuly read the state of the port, when the
>program reach to the breakpoint that i put on this line, i can 
>see in the watch that 'my_DCB.fParity' value is zero ( 0 = 
>Disabled )although that as you can see at the beginning of the
>function i set "my_DCB.fParity  = 1;", so how come it's suddenly
>changing to '0' ??
>
>
>  my_DCB.DCBlength= sizeof( my_DCB );                                          // Sizeof(DCB)
>  my_DCB.BaudRate = SystemInfo.ComInfo.BaudRate;                               // Current baud rate
>  my_DCB.fBinary  = true;                                                      // Binary mode, no EOF check

{big snip}

>  if ( my_DCB.fParity == 1 )                                                   // If Parity Checking Enabled 
>  {
>    switch( my_DCB.Parity )                                                    // Switch By Parity Value 
>    {
>      case SPACEPARITY:
>        strcat( com_params, ", S, 8, 1" );                                     // Set Parity to '1' 
>       break;
>
>      case MARKPARITY:
>        strcat( com_params, ", M, 8, 1" );                                     // Set Parity to '0'   
>       break;
>    }
>  }

>  if ( !BuildCommDCB( com_params, &my_DCB ) )                                  // Fills DCB Structure with Com Values
>   return FAIL;

Well, now, this is at least the third time I'm telling you not to do
that.
BuildComDCB replaces all of your hard work up at the top, with
whatever Bill Gates thinks is best for you.
If you really need to use that function (and I don't think you do),
then use it to set defaults, and *then* override them with your
indiviual settings (such as fParity=1)

IOW, you already set the baud rate, the parity settings, seems like
everything has been set manually in my_DCB, and then you throw it all
away with a call to BuildCommDCB() ?