Thanks PRJ, I will try to get a positive answer from ecu, sincerly i don;t exactly what i must to get from serial portbut i will try.
With baud rate i'm wrong i wrote a bad value for 38400 must be 0x50
I have your code from your few posts ago.
I will try and i will inform here if i will make to work.

PS : after few minutes i reedit this post;
I changed the baud rate in dev session
I received rxBuf[0] == 0x50 but after this i remaining in a continously loop in accessTimingParameters after made checksum.
I tried to change 0x14 in 0x50 in byte 6 from accessTimingParrameters , because i thinked this is again the baudrate
 txBuf[0] = 0x07;  //Message Length
  txBuf[1] = 0x83;  //AccessTiming Parameters
  txBuf[2] = 0x03;  //setTimingParametersToGivenValues
  txBuf[3] = 0x00;  //P2min
  txBuf[4] = 0x01;  //P2Max
  txBuf[5] = 0x00;  //P3min
  //txBuf[6] = 0x14;  //P3max
  txBuf[6] = 0x50;  //P3max
  txBuf[7] = 0x00;  //P4min

First ideea was my mc33290 chip doesn't support more than 10400, but, i found in datasheet it can do 56000!


Please tell me in this diagnostic development session can i find the dtc and can i delete them?

PS:

i tried after starting session and acces timing parameter to read dtc
ReadDiagnosticTroubleCodes (0x13)   and ReadDiagnosticTroubleCodesByStatus (0x18)
  txBuf[0] = 0x03;
  txBuf[1] = 0x18;
  txBuf[2] = 0x00;
  txBuf[3] = 0xFF;
  SendDataChksum(4);


I received negative response 0x7F with 10 code - general reject for ReadDiagnosticTroubleCodesByStatus  and 11 code for ReadDiagnosticTroubleCodes  - not supported. The same response if i tried with only 2 bytes and with 8 bytes
  txBuf[0] = 0x01;
  txBuf[1] = 0x18;
  SendDataChksum(2);

and
  txBuf[0] = 0x07;
  txBuf[1] = 0x18;
  txBuf[2] = 0x00;
  txBuf[3] = 0xFF;
  txBuf[4] = 0x00;
  txBuf[5] = 0x00;
  txBuf[6] = 0x00;
  txBuf[7] = 0x00;
  SendDataChksum( 8 )

Some advice please

Something is strange. i tested on 2 ecus , different boot version.
I receive some strange bytes .
With my projet (send to ecu [0x18 ; 0x00 -status ; 0x00 -high byte ; 0x00 lowbyte]) received:
11:04:56.381 -> DTCs: 11
11:04:56.413 -> 58 B 15 23 64 2 43 34 0 10 34 6 0 64 6 0 68 6 0 64 1 2 32 2 38 61 6 87 61 1 13 62 1 18 62
11:04:56.509 -> P1523
11:04:56.509 -> P0243
11:04:56.509 -> P0010 - WRONG
11:04:56.509 -> P0600 - WRONG
11:04:56.541 -> P0600 - WRONG
11:04:56.541 -> P0600 - WRONG
11:04:56.541 -> P0102
11:04:56.541 -> P0238
11:04:56.573 -> P0687
11:04:56.573 -> P0113
11:04:56.573 -> P0118
11:04:56.573 -> Positive Response to Tester Present!

and with VCDS i have the same number of DTC - 11
but 3,4,5,6 DTC looks ok

11 Faults Found:

17931 - Crash Signal from Airbag Controller
            P1523 - 35-00 - Implausible Signal
17956 - Boost Pressure Regulation Valve (N75)
            P1548 - 35-10 - Open Circuit - Intermittent
17939 - Camshaft Timing Adjustment
            P1531 - 35-10 - Open Circuit - Intermittent
18034 - Powertrain Data Bus
            P1626 - 35-00 - Missing Message from TCU
18057 - Powertrain Data Bus
            P1649 - 35-00 - Missing Message from ABS Controller
18058 - Powertrain Data Bus
            P1650 - 35-00 - Missing Message from Instrument Cluster
16486 - Mass Air Flow Sensor (G70)
            P0102 - 35-10 - Signal too Low - Intermittent
16622 - Manifold Pressure / Boost Sensor (G31)
            P0238 - 35-00 - Signal too High
17071 - ECM Power Relay Control Circuit
            P0687 - 35-00 - Short to Plus
16497 - Intake Air Temp. Sensor (G42)
            P0113 - 35-00 - Signal too High
16502 - Engine Coolant Temp. Sensor (G62)
            P0118 - 35-00 - Signal too High

Any suggestions please?

PS: P0600 what i receive is ""Serial Communication Link (Data Bus) Message Missing"" , and appear when the real DTC is something like "Missing Message from " : TCU , ABS, AIBAG, but i don't know how VCDS knows interpret them , maybe use other protocol.