-
Notifications
You must be signed in to change notification settings - Fork 0
refactor: use a error handling similar to CAN #8
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
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still missing handling of "bad length", which is actually the one error we currently have.
And no unit tests.
wvmcastro
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fix: do error handling similarly to CAN is actually IMO a feat
and feat: store validation on it's on method to be used elsewhere
is a refactor or at least a chore
682930a to
27caf70
Compare
d561cfe to
216ad13
Compare
jhonasiv
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The only thing I didnt check was whether the expected packet length is correct for each method. Since you didnt explicitly change any tests regarding this, I think they are right, but this is not passing CI at moment with errors on motors_weg_cvw300, so maybe not. Waiting for updates on that
e2a733a to
ef009d3
Compare
Yep, there was indeed an issue with one of the tests. I'm double checking all the tests using the modbus reference from here: https://www.modbustools.com/modbus.html |
Keep the default constructor as initializing everything with 1 for threshold and increment
AFAIK this is not used, I was able to build everything and it all worked fine. So i'll be removing it and all the tests related to it.
add a new test for UnexpectedReply function code and length
…essage Therefore the response payload should have 4 bytes of size corresponding to the Address High, Address Low, Data High, Data Low
We're assuming the errors won't happen as much
5f539e9 to
bd17faf
Compare
remove c_cpp_properties.json from git tracked files typo `sucess` to `success`
624d59a to
4b0912d
Compare
22db9c4 to
1833dc5
Compare
1833dc5 to
0f1ae27
Compare
Depends on:
What is this PR for
Implement a CAN Similar Error Handling
How I did it
Results, How I tested
Checklist