Text signals are defined in additional files whose layout is that of Ini Files. The search for a text signal definition file goes as follows:
1.measurementFolder\measurementFile.extension.enum.ini
2.measurementFolder\measurementFile.enum.ini
3.measurementFolder\enum.ini
4.measurementFolder\{A5CF05C2-E423-487B-AC39-235720F01E96}.enum.ini
5.TemesViewFolder\enum.ini
The identification for a valid text signal definition file is located in section Settings and Key Id:
[Settings]
Id={D1191CE9-6FD2-4050-8E5E-330620BA37A6}
Then, the signal names which represent the text signals can be defined. This is done in groups of signal names, and also sorted in pure signal names and display names.
[SignalNames]
arbitrarySignalNameGroup=SignalName1,SignalName2,SignalName3
[DisplayNames]
arbitraryDisplayNameGroup=DisplayName1,DisplayName2,DisplayName3
Then, the connection between signal group name and the enum entries is defined in section Versions:
[Versions]
arbitraryConnectionEntry=2000-01-01T00:00:00Z,arbitraryDisplayNameGroup,enum0
Note, that the mentioned UTC time point is the first valid time for the corresponding connection. It is therefore possible to define an evolution of enum values distinguished by the start time when the corresponding connection is valid.
Finally, the enum entries are added to the definition file with their corresponding integer values as key, the text definition and an optional comment:
[enum0]
0=FirstEnumValue (0),comment about the first enum value
1=SecondEnumValue (1),comment about the second enum value
3=ThirdEnumValue (3),comment about the third enum value