Skip to content

Fix for binary communication error false positives - #79

Merged
kmpeters merged 6 commits into
masterfrom
issue72
Jan 14, 2026
Merged

kmpeters merged 6 commits into
masterfrom
issue72

Conversation

@kmpeters

@kmpeters kmpeters commented Dec 19, 2025

Copy link
Copy Markdown
Contributor

Significantly improved binary error checking so that messages that happen to have "?" and "\r" in the same locations of the reply as error messages are no longer incorrectly interpreted as error messages with invalid error numbers. Human-readable error strings are now printed along with the error number when real errors occur.

Fixes #72

The binaryErrorCheck method now does a more thorough validation
of the reply from the controller.  It checks the following:

* reply length
* command prefix/suffix
* body start/end characters
* error number characters

All of the checks must pass for the message to be determined
to be an error message.
…s the error number, but not the human-readable error string.
…ks but still causes deadlocks when called from binaryErrorCheck for unknown reasons
@kmpeters
kmpeters merged commit 8a87d25 into master Jan 14, 2026
3 checks passed
@kmpeters
kmpeters deleted the issue72 branch January 14, 2026 16:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

binaryErrorCheck: Binary command error #0

1 participant