+1

Popup (alarm messages) deactivation should be related to the alarm severity level

Simone Delfitto 4 weeks ago in IQANdesign 0

Deactivation (on User Interface à System dialog boxes) can consider the dialog priority info. It can be implemented in different ways.

Deactivation should be an integer instead of {No, Yes}. The application can assign an integer channel to the Deactivation with the following logic:

  • Deactivation = 0: equivalent to “No”
  • Deactivation = 1: equivalent to “Yes” for all popups
  • Deactivation = 2: equivalent to “Yes” for all popups with dialog priority level lower than the Information (so the deactivation is active only for Message)
  • Deactivation = 3: equivalent to “Yes” for all popups with dialog priority level lower than the Confirmation (so the deactivation is active only for Message and Information)
  • Deactivation = 4: equivalent to “Yes” for all popups with dialog priority level lower than the Warning
  • Deactivation = 5: equivalent to “Yes” for all popups with dialog priority level lower than the Alarm
  • Deactivation = 6: equivalent to “Yes” for all popups with dialog priority level lower than the Error
  • Deactivation = 7: equivalent to “Yes” for all popups with dialog priority level lower than the Critical (so the deactivation is active for ALL except Critical)


This integer value can be connected an integer parameter (adjustable) on the Master display.

The idea is to delegate to our Service or dealer the possibility to decide from which severity level the driver acknowledge is mandatory.

Every customer/dealer wants to have a different approach.


If a subsystem raises a DTC with low severity level, the driver confirmation should be not required.

  • i.e. to inform the driver that the required function is temporarily unavailable because an interlock is active:
    • it should be visible until the function is requested or the interlock is active
    • and the message should be hidden automatically. If we don’t close automatically, for the driver it is a source of distraction and the interaction to close the message is very annoying for our customers. If we don’t show the message to inform about the interlock, they claim because they don’t understand the reason of loss of functionality.

But if the DTC is critical for safety reasons or to avoid a component damage or if an analogue signal is disconnected/short to GND o Vbat, we MUST require a driver confirmation.

So, they can understand the seriousness of the situation and they call the service/maintenance to fix it.