07-31-2014 11:35 AM
The ADCS package has the capability to translate the raw UDS CAN message to and from physical values using convert to phys.vi and convert from phys.vi. However the ADCS package does not come with functions to determine the type descriptor from the PDX/ODX file to facilitate the conversion to and from the raw message.
Are there any tools or examples available to read an PDX/ODX file to determine the characteristics required to convert a raw message to and from the physical value?
Chris
08-01-2014 04:45 PM
Hi Chris,
It appears that ADCS does not support PDX/ODX files. I could not find any references of support for these files in the documentation or our systems. I would need to confirm with our R&D department this is the case though.
Best Regards,
05-26-2015 12:08 PM
Any updates on this capability? I've got a fairly pressing need to parse ODX files for use with an ADCS-based Veristand Custom Device and I'm running into multiple walls trying to deal with the XML.
12-08-2015 01:54 AM
Hi Matthew,
My name is Balazs Bornyasz, and I've just begun to work with NI ADCS, and I ran into the same question as chrisdefoor ran into on the 31th of July 2014:
I need to be able to handle/parse/use PDX / ODX files in my test environment (TestStand + LabView + CVI + MXI + NI PXI-8513 CAN) that communicates with a Device Undet Test via CAN. On the 1st of August 2014 you've replied to chrisdefoor, that according to your knowledge ADCS does not have any support for these files, but you still need to confirm it with your R&D department. Can I kindly ask you to update me on this topic since I too need a solution to this problem that I have. If it is not your department anymore, then could you refer me to someone else please?
Thank you very much, Best Regards:
Balazs Bornyasz
04-28-2016 12:59 AM
Hai ,
Is ther any update on this Topic ?. I need to use PDX / ODX files in the NI ADCS . Is it Possible?
Regards
Vinoth edison
04-28-2016 10:42 AM
PDX / ODX files remain unsupported in the latest version of the ADCS toolkit (2015). If support for these file types is introduced in the future, it will be documented in the readme for the release.
04-28-2016 12:35 PM
I feel compelled to reply to this thread to bring some closure. In the end, I did not read the ODX/PDX file directly. Instead I defined a data type based on the ADCS blockset. And then parsed the application specific UDS specification to define the datatype. This method was used because I was not intersted in testing an autogenerated ODX/PDX file against the application, instead I wanted to test the application specific UDS specification.
The ODX file is a XML format and the PDX file is a zipped version of the XML. So someone could write a function that would parse the XML and create a dataset required by the ADCS blockset. The XML definition can be found here and other places:
http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=41207