fix: add more stringent validation when building _incomingBuffer

PepperDash · Sep 28, 2023 · 892f2b1 · 892f2b1
1 parent f10e70f
commit 892f2b1
Showing 1 changed file with 6 additions and 2 deletions.
diff --git a/epi-display-samsung-mdc/SamsungMdc.cs b/epi-display-samsung-mdc/SamsungMdc.cs
@@ -435,7 +435,6 @@ private void Communication_BytesReceived(object sender, GenericCommMethodReceive
                     // following string format from building unnecessarily on level 0 or 1
                     Debug.Console(DebugLevelVerbose, this, "Received new bytes:{0}", ComTextHelper.GetEscapedText(newBytes));
                 }
-
                 // Get data length
                 if (newBytes.Length >= 6)
                 {
@@ -454,7 +453,7 @@ private void Communication_BytesReceived(object sender, GenericCommMethodReceive
                         return;
                     }
                 }
-                if (newBytes[0] == 0xAA)
+                if (newBytes[0] == 0xAA && newBytes[1] == 0xFF && newBytes[2] == Id)
                 {
                     _incomingBuffer = newBytes;
                     if (Debug.Level == 2)
@@ -467,6 +466,11 @@ private void Communication_BytesReceived(object sender, GenericCommMethodReceive
                 {
                     byte[] clear = { };
                     _incomingBuffer = clear;
+                    if (Debug.Level == 2)
+                    {
+                        // This check is here to prevent following string format from building unnecessarily on level 0 or 1
+                        Debug.Console(DebugLevelVerbose, this, "Unsupported response recieved:{0}", ComTextHelper.GetEscapedText(newBytes));
+                    }
                 }
             }
             catch (Exception ex)