Your comments

Not in the existing versions of IQANdesign, these fields are set as Not available (all bits set to 1)
To avoid having the button Active color overwriting the Text Label, the Label should be placed after the button in the display page order.

One way to implement this is to just have one fixed text label that is always visible. Then it will be slightly different from the Text button text, that automatically changes color with the state of the button.

To replicate that exact behavior with text labels, you will need two text labels, and control visibility on both of them.

See attached example:
Text buttons with labels.ids3
Yes, this is possible. To make the ISO symbols work on the MD3, they must be specified as BMP.

When using a BMP on the MD3, it will be automatically compressed, so size of the image is not that much of an issue.
For the MD4 however, the original file format is kept, and on the MD4 is best to always use PNG.

Although you do specifiy a file format for the ISO sympols, the option to export the images from the project file is grayed out by IQANdesign for these images. This is due to license restrictions.
Hi Axel,
I checked, and my question about version was not that relevant, the settings for the touchdriver has not changed with any IQANdesign SW version.
Do you have any indication of how much noise you get from this generator?
The IQAN-MD4 is tested for electrical transient conducted along supplylines using ISO 7637-2, level 3.
I checked, the maximum voltage that the MC2 VREF is can measure is 6.6V.
If it is shorted to a voltage above 6.6V, it will still report 6.6 in the VREF error. In this case, I suspect that the VREF has been shorted to the 12 V.
Correct, a local fault on the IQAN-MC2 will be reported to the IQAN-MD4 even it the MDGN for MC2 VREF has not been added to the application.
There are no known bugs related to the reporting of module diagnostic faults.

From the MD4 menu system, you should be able to go into the MC2 log and see when the VREF error occured. You can also go in and check the measured value on the MC2 VREF via Info-Modules. (on the current version of sofware, the MD4 only gets the value from the MC2 when you enter the module info page)

I would guess that the MC2 VREF has been shorted to some other signal. I think that the VREF has an upper limit on the voltage it is reporting, even if it is shorted to a higher voltage. I'll check what that level is.
Thanks for the infromation update, knowing that it is MD4-7 loaded from IQANdesign 3.15.16 gives us the information about the firmware for the touchdriver.
That is very interesting.
What model of IQAN-MD4 is it, is this the MD4-7 or the MD4-5?
What software version are you using on the MD4? (paramters in the firmware for the touch driver affects its sensitivity for responding to touch events)
I like this idea. The automatic increment could probably be based on number of saves since you changed the manual version. Since there is no build of the project file, the number of saves could fit the same purpose for version tracking. Adding something else, such as total number of days since created (like for the IQAN PC tools) could increase the chances of having a unique incremental number.