What is an A2L file in CANape

Public support

Support request

With ADTF 2 we use a2l files with ASAP version 1.60.
While we are generating the a2l files for Canape with version 1.70.

2. Support multiple conversions (especially names for enumerations)
Currently (ADTF2) most signals can only be recorded or displayed with the "raw_value" setting.
This is still OK for recording, but for live visualization, the display of the interpretation of the numerical values ​​is an important feature for the user.
It can of course also be a topic for the "Signal View".
Digital work ticket.
# 3095 Signals with conversion type eConvSymbolicTable could not be used
# 872 Error parsing FIBEX files with more than one COMPU-METHOD LINEAR

3. Support arrays
In ADTF it should somehow be possible to read out arrays via XCP. Although I can see the variables in the Signal View, the content is not displayed.
The documentation does not go any further at this point. For ADTF3 it would make sense to ensure this right from the start.

solution

Point1)
Currently (ADTF2) most signals can only be recorded or displayed with the "raw_value" setting.
This is still OK for recording, but for live visualization, the display of the interpretation of the numerical values ​​is an important feature for the user.

Let's do it, ACALTB-506 is planned as I said.

Point2)
In general, all 1.7 features should be supported, otherwise there is always the risk that something does not work as expected. The requirement is please simply support 1.7 version. https://www.asam.net/index.php?eID=dumpFile&t=f&f=734&token=aff3202720d0a044bd82491c9354a93b7cf43d61

I can't just do it like that, it's a specific requirement and a bigger topic, please bring that to the customer forum.
Either very specific support for A2L v1.70, or we have to talk about a general requirement to always support the latest standards for everyone.
Either way, there are massive shifts in resources, and unfortunately not everyone can deal with these issues.
We are happy to do a preliminary analysis and try to plan / suggest it.

But then I need a priority, roadmap and timeline from you.
Please also consider that the resources in the special topics are really limited and bus know-how in the backend and spec is required for many topics (keyword CAN, ARXML, etc.)
Unfortunately, this only works to a limited extent in parallel, so please provide specific information here and then we can try to convert and plan the whole thing in PT.
But then something will have to fall differently and when I think of the usability topics, bus topics (especially SOME / IP and co) as well as the distributed system, I don't know how all of this can be done "ASAP" with current means and resources ...
But that will then have to be discussed.
ACALTB-600 created