Skip to content

MB_PORT_COMMON: vMBMasterRunResRelease(194): Resource release failure. #2

Answered by alisitsyn
jbsaibes asked this question in Q&A
Discussion options

You must be logged in to vote

@jbsaibes,

This answer is too late but just in case please update the component to the latest version. I guess the issues are fixed long time ago.

  1. The related issue for master to use different communication options for each slave may partly address the issue with the parity.
  2. The extended data types feature may help to work with the slave which use different endianness options.

Replies: 2 comments 3 replies

Comment options

You must be logged in to vote
1 reply
@jbsaibes
Comment options

Comment options

You must be logged in to vote
2 replies
@jbsaibes
Comment options

@alisitsyn
Comment options

Answer selected by alisitsyn
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants