CAN XCP DAQ Channel extraction when channel data is split across multiple ODT's

[iiDaveii]

Best ideas on how to extract these data channels and convert them to proper format?

It appears most of the standard VI's are setup for a channel data being contained within 1 ODT

Streaming at 1kHz, so it's got to be quick

AA, BB, CC, DD, EE, GG, HH, II, JJ = Float32's

FF = char (8 byte)

[ZYOng]

Are you using ECU Measurement and Calibration Toolkit or Vehicle Communication Measurement and Calibration Toolkit?

Do you have A2L file?

[iiDaveii]

I have the toolkits available, but no I'm not using them currently, just the XCP palette. 

[ZYOng]

To my knowledge, neither ECU Measurement and Calibration Toolkit or Vehicle Communication Measurement and Calibration Toolkit has an XCP Palette. Both toolkits will handle the parsing of DAQ lists as well. 

Please share the program you are using.

[iiDaveii]

I'm sorry, mis-spoke - I am using the XNET pallete.  No A2L file, using an XNET database we manually created.

The difficulty lies in stitching the data channels back together and getting the conversion correct. 

Looking for the easiest way to go about this.

Will a toolkit feature help to extract the data channels when they are split across ODT frames?

Currently getting the proper ODT's into payload...

Checking for data split across frames and converting to binary... not correctly

[ZYOng]

If you have an A2L file, I highly recommend using the toolkit and not parse the ODT yourself.

If you insist on using XNET only, you can refer to my implementation in NI-ECUMC-XCP-DTO-Id: Workaround library allowing NI ECUMC to support non-DTO_ID with DAQ for XCP_ON_...