Hi,

first of all: Great script - really helpful for our use case 👍

Testing it with several a2l files I noticed a problem with MEASUREMENTS blocks that are using names with brackets. Probably the problem occurs with any kind of block that uses brackets in it's name?

Example: Sb177_Div_T [0]

    /begin MEASUREMENT Sb177_Div_T[0] ""
      FLOAT32_IEEE VOID_SCALING 1 100 -2.5 12.4
      BYTE_ORDER MSB_LAST
      ECU_ADDRESS 0x60012514
      ECU_ADDRESS_EXTENSION 0x0
      FORMAT "%12.6"
      SYMBOL_LINK "Sb177_Div_T" 0
    /end MEASUREMENT

At first I thought names with brackets aren't valid - so your script is 'right' - but then I checked the ASAP / A2L specification which says:

Identifiers are random names which may contain characters A through Z,
a through z, underscore (_), numerals 0 through 9, points (.) and brackets ([, ]) .
However, the following limitations apply: the first character must be a letter or an underscore,
brackets must occur in pairs at the end of a partial string and must contain a number
or an alphabetic string (description of the index of an array element).

My knowledge in Python is unfortunately very poor, otherwise I'd like to extend your script to handle this kind of names. But maybe you could take a look? I'm willing to help in any kind (testing it or providing more examples).

Currently the brackets are simply ignored, but this results - in our case - into MEASUREMENT blocks of the same name.

xml2a2l input.XML output.a2l doesn't work at all