07-28-2009 10:28 AM
Hello,
If it was posted in someother place please excuse me.
Here it is my problem.
I have an a2l file from where I read certain variables (characteristiques). I am using for this the VI's found on ECU measurement and calibration toolkit.
The used VI is "MC Characteristic Read.vi"
For a few variables I get the error:
///Error -301033 occurred at MC Get Prop Char Dimension.vi
Possible reason(s):
ECU Measurement and Calibration Toolkit: (Hex 0xFFFB6817) The definition of the characteristic could not be found in the A2L file. Most likely, the name of the characteristic is misspelled or otherwise invalid, or the A2L database file has been corrupted. Solution: Make sure that the name of the Characteristic is spelled correctly and that the A2L database file is valid.///
I am 100% sure that the variable is defined because I find it with search function in the a2lf ile. The others variables I can read them without errors.
Also I have created a unittest vi where I am using the "raw" reading with succes. I am able to read the values which I expect from the right provided address giving me a momentary workaround.
This one is using "MC generic.vi" with send "CONNECT" (0x1) command and also the is using the "MC upload.Vi" with exactly the addres of variable, and finding the values which I am expecting.
As you guess I don't want to use in my project the addresses (dependent of each release) but the names.
Did anybody encountered the same problem?
Best regards,
Vincent
Solved! Go to Solution.
07-29-2009 06:57 AM
Hello,
you are able to read another CHARACTERISTIC using the A2L file? If so, I think there might be some problem within your CHARACTERISTIC declaration in the A2L file.
In that case, it might be helpful to enable some logging if parsing A2L files. Please, look at the following file:
"C:\Documents and Settings\All Users\Documents\National Instruments\ECU Measurement and Calibration Toolkit\A2LReaderConfig.a2l"
Set the ENABLE flag to 1. Save your file, and read your A2L file (this will be done if using your VI). The logfile is created where your A2L file is located. The extension is "txt". Take a look on that file, and tell me about if there is some error message.
It might be also helpful if you send me your A2L file or at least parts of the file.
Especially, you can remove all MEASUREMENTs and CHARACTERISTICs except the CHARACTERISTICs / MEASUREMENTs raising the problems. But, do not remove the following blocks:
- "A2ML" from the "MODULE" (declaring the data model being used to read in the ECUparameters)
- "IF_DATA ASAP1B_CCP" from the "MODULE" (declaring the ECU communication parameters, such as the ECU address)
Then, I can try to help you.
Andreas
07-29-2009 07:13 AM
Hey,
Vincent, by the way, you can reply to
leimrute2 ~-at-~ web.de
Andreas
07-29-2009 08:48 AM
Hello Andreas,
I just sent you an email to the indicated mail addres.
Regards,
Vincent
08-04-2009 04:34 AM
To all who may concern....
Be carefull to capital letters!!! Upper case...lower case... I spent a lot of time due to not paying attention to this.
When reading from a2l file the values are CASE SENSITIVE.
A lot of thanks to Andreas who guided me and making me realize the mistake.
Thanks again and good luck!
Vincent
08-04-2009 04:39 AM