Add support for the remaining sensors from the OI spec, and create request functions to better support encoder outputs. #28
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.
Hi @AtsushiSakai, thanks for this awesome library!
This PR adds the remainder of the sensor packets from the Roomba Open Interface to the Sensors dict, so that they may be queried.
I need to use encoder data for my project, so I also added a few functions to make requesting the distance and angular displacement from the Roomba a bit cleaner. I also updated the examples that I thought were relevant.
I did a couple of tests with my 630 and distance and angle measurements were low by about 10% (though I do have a non-stock roomba).
The spec does contain the following note about the distance packet and a similar one is present for the angle packet:
Create 2 and Roomba 500/600 firmware versions prior to 3.3.0 return an incorrect value for
sensors measured in millimeters. It is recommended that you read the left and right encoder counts
directly (packets IDs 43 and 44) and do the unit conversion yourself.
This doesn't effect my Roomba, but in the future if it's of interest I could add a function (or change
request_angle
andrequest_distance
) to do the calculation there from the encoder counts so we know it's correct.