-
Notifications
You must be signed in to change notification settings - Fork 48
Libmodbuspp ascii support #15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
ccdMuro
wants to merge
21
commits into
epsilonrt:master
Choose a base branch
from
kernelconcepts:libmodbuspp-ascii-support
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Libmodbuspp ascii support #15
ccdMuro
wants to merge
21
commits into
epsilonrt:master
from
kernelconcepts:libmodbuspp-ascii-support
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
e4e748f to
da87df5
Compare
f960c16 to
f6f7c9a
Compare
e521bf9 to
b0ec07e
Compare
Throw exceptions on error instead of silently changing values. Check settings string for given stop bit value. Up until now, the stop bits value was hard coded to be 2 if the parity mode was set to none or 1 if the parity mode was set to even or odd. So a setting of "115200E1" would result in a stop bit value of 1. But "115200E2" would result also in a stop bit value of 1. And "115200N1" would result in a stop bit value of 2. This is not a restriction of libmodbus. The library supports all these modes just fine. In fact they are using 115200N1 in the documentation for modbus_new_rtu(). Rather this is a bug in the string parsing that libmodbuspp introduces in its constructor. libmodbus has no string parsing in modbus_new_rtu() and takes in the arguments as parameters directly. Fixes: b0f3dc4
…calls to ensure the defines are set correctly
…with version 3.1.8; remove dependency in default libmodbus
…h instead (works better with bitbake)
…n INSTALL_TEMPLATES default OFF
…es use of methods and lambda captures
…ke modbus_t a unique_ptr
…tiple instances with a single poll
b0ec07e to
a81892c
Compare
(re-)added virtual destructors to prevent memory leaks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've made a branch with ascii support which depends exclusively on the modbusepsi library with ascii-support (starting with v3.1.8) as the default libmodbus does not support ascii mode.
I also made some modifications to the installation so I can use it with bitbake, but tried not to break the default behavior if used for desktop.