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.
The I2C block had limited usability as the maximum value of a byte that could be sent was 127.
The inputs of the I2C block are of type UInt32. If I send a single byte of this type over I2C or UART, it sends correctly, the problem occurs when the
ReplaceArraySubset
functions puts together the address of the slave I2C device and the array of bytes to be sent, this is where the capping of the value at 127 happens, I am not sure why. I tried replacing this function withInitializeArray
andBuildArray
, but to no avail as the EV3 threw an error and it didn’t want to run code with these LabView functions.The solution was to change the type of the input value of the byte from UInt32 to Byte in the code of the block, after this change, values larger than 127 can be sent without any issues.