Why do the examples not run with my ECU although they run fine with the Test ECU examples?Primary Software: Other NI Software>>ECU Measurement and Calibration ToolkitPrimary Software Version: 1.0 Primary Software Fixed Version: N/A Secondary Software: N/A
Problem: After installing the ECU Measurement and Calibration Toolkit, I can run the accompanying examples against the Test ECU examples (CCPECU, XCPECU). However, if I run the examples against my own ECU, they fail, either with an error message, or they do not show data. Solution: Most probably, if you cannot connect to your own ECU, the communication parameters cannot be read correctly from the A2L file. To check this, go to an Advanced example, e.g. 'Measurement and Calibration Application.vi', select the A2L file in the respective path control, select the protocol and interface, activate the Boolean 'Change conn parameters?' control, and start the example. A dialog box pops up that shows the connection parameters as they have been read from the A2L file. Verify the correct settings and modify any incorrect settings, then click 'Apply'. The example should then run fine. If you are going to program your own application, set those connection parameters that have been read incorrectly manually after ECU Open or ECU Select by issuing appropriate Set Property calls. Background: The A2L file section that specifies the connection parameters is highly manufacturer dependent. Although we tried to cover most cases, from time to time we hit A2L files that cannot be read correctly. If you want to help us improve this product, mail us a copy of the A2L file and an information which parameters have not been read correctly. We will treat the A2L file confidential. Related Links: Attachments:
Report Date: 07/17/2006 Last Updated: 07/31/2006 Document ID: 3ZG4RUE6 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
