From f8757b352d4bf844aa6ad465711f6859336256ca Mon Sep 17 00:00:00 2001
From: Siegfried Siegert <s.siegert@atb-online.eu>
Date: Mon, 12 May 2025 16:10:40 +0200
Subject: [PATCH] Diag: clear machineEventSet on the begin of DCDiag ...

... not on end.
This is to keep current machineEventSet during normal IDLE process.
---
 src/ATBAPP/DeviceControllerDiag.cpp | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/src/ATBAPP/DeviceControllerDiag.cpp b/src/ATBAPP/DeviceControllerDiag.cpp
index 7778813..7de2550 100644
--- a/src/ATBAPP/DeviceControllerDiag.cpp
+++ b/src/ATBAPP/DeviceControllerDiag.cpp
@@ -61,6 +61,7 @@ void DeviceControllerDiag::diagRequest()
         qCritical() << "DeviceControllerDiag::diagRequest() is already running";
         return;
     }
+    this->machineEventSet.clear();
     this->isRequestRunning = true;
     this->diagRequestTimeoutTimer->start();
 
@@ -452,12 +453,12 @@ void DeviceControllerDiag::sub_componentAssessment()
     this->flagInterruptDiag = false;
 
     this->previousMachineEventSet = machineEventSet;
-    this->machineEventSet.clear();
 
     if (this->isDiagBackgroundTask) {
         this->isDiagBackgroundTask = false;
         this->dbus->finishedBackgroundTask("E255");
     }
+
 }