-
Couldn't load subscription status.
- Fork 28
New profile Shifting/Shifter. Initial checkin. #13
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
New profile Shifting/Shifter. Initial checkin. #13
Conversation
Repo uses 4 space indentation, even in 2019 indentation conversion is still hard :P thank you sublime text for saving us.
This will unpack the data and build it into the API so profiles can handle the patterns easier.
This should fix up everything.
Add to build so its compile tested all the time
Convert all tabs to spaces
Decoding not yet completly tested (TODOS added)
Gotta have a driver to reset the hardware.
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.
Looking good, excellent first start. Let's add the Travis CI change, that way we can get a compile test done. As long as it compiles and doesn't contain debug code and is correct then I have no problem doing incremental merges 😃
src/Profiles/Shifting/Shifter/ANTPLUS_ProfileShiftingShifter.cpp Outdated Show resolved Hide resolved
src/Profiles/Shifting/Shifter/ANTPLUS_ProfileShiftingShifter.cpp Outdated Show resolved Hide resolved
src/Profiles/Shifting/Shifter/ANTPLUS_ProfileShiftingShifter.cpp Outdated Show resolved Hide resolved
src/Profiles/Shifting/DataPages/Base/ANTPLUS_ShiftingBaseMainDataPageMsg.h Outdated Show resolved Hide resolved
src/Profiles/Shifting/DataPages/Base/ANTPLUS_ShiftingBaseMainDataPageMsg.h Outdated Show resolved Hide resolved
| Oh also can you amend that commit so it mentions what it is changing so when people look through the git log they know what the change is without looking at the diff? |
| Looks like you only changed the pull request, not the commit, no worries, I can change it after its submitted, we may have to deal with some merge conflicts after. Its not the easiest thing to change, if you think you are up for it you can read up on here otherwise I will fix it up after the PR lands :) |
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.
Bit math looks good, only a few changes left then this will be ready for merge :)
src/Profiles/Shifting/DataPages/Base/ANTPLUS_ShiftingBaseMainDataPageMsg.h Show resolved Hide resolved
src/Profiles/Shifting/DataPages/Base/ANTPLUS_ShiftingBaseMainDataPageMsg.h Outdated Show resolved Hide resolved
src/Profiles/Shifting/DataPages/Base/ANTPLUS_ShiftingBaseMainDataPageMsg.h Outdated Show resolved Hide resolved
src/Profiles/Shifting/DataPages/Base/ANTPLUS_ShiftingBaseMainDataPageMsg.cpp Outdated Show resolved Hide resolved
src/Profiles/Shifting/Shifter/ANTPLUS_ProfileShiftingShifter.cpp Outdated Show resolved Hide resolved
| also bit math looks good 👍 |
Add datapage 81 to the mix
Add datapage 80 for TX
| You can fetch and merge the branch core/base-master and you will get the ProductInformationMsg and ManufacturersInformationMsg which you can use to replace the temp data buffers. |
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.
Looking good but it looks like you merged your copy of develop which had both lev and moxy in the branch, I want to keep them isolated still till I have time to fully flesh out the profile. If its easier for you I can merge this, rebase the commits so the proper merge happens and then force push the branch, then you will just have to force sync on your end. Up to you :) Otherwise the shifting stuff looks great :)
| .DS_Store | ||
| .tags* | ||
| tags | ||
| examples/BikeSensorConverter/arduino_secrets.h |
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.
Accidental add?
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.
Yes, this was accidentally. Sorry.
| @@ -0,0 +1,352 @@ | |||
| /********************************************** | |||
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.
Not sure if you meant to commit your project to the examples. If you want to commit this to the repo we should do it not on the shifting branch since it uses multiple profiles :) The project is looking good, you will have to tell me more about what it does.
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.
This happened by mistake. Can you remove it from the pull request ? We can talk about adding it to the examples, when it is thoroughly tested.
| @@ -0,0 +1 @@ | |||
| #define SECRET_ANTNETWORK_KEY {0x00, 0x11, 0x22, 0x33, 0x44, 0x55, 0x66, 0x77} | |||
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.
Accidental commit?
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.
Yes, accidental.
| @@ -0,0 +1,206 @@ | |||
| /********************************************** | |||
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.
There was no merge from the LEV branch so I am not sure how this got in here.
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.
Pooh. Seems I need to work at my understanding for github...
| @@ -0,0 +1,60 @@ | |||
| /********************************************** | |||
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.
there was no merge from the MOxy branch, accidental merge into develop?
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.
Yes, accidental. See above.
| // setup shifting monitor | ||
| shift.createShiftingSystemStatusMsg(shiftCreateMsgHandler); | ||
| shift.createShiftingManufacturerInformationMsg(shiftCreateManufacturerInformationMsg); | ||
| shift.createShiftingProductInformationMsg(shiftCreateProductInformationMsg); |
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.
Looking good, I forgot to implement batterystatus which needs a TODO here :)
Yes, would be great, if you could properly merge to the profile branches and throw the unwanted sources out. Thank. Next time, I will try to be more thorough. |
| Ok sounds good, I'll merge this, then force push a rebased version. Your local copy will likely complain that you are out of sync and try and merge your local branch into my new branch, you don't want to do that since it will add all the bugs back. You will want to delete your local shifting branch and re-create it on top of my branch once I have pushed it. I will send you an email once that is done. |
Dont't know, if you really want to merge this code in such an early state. For my purpose, it is sufficient, I do not plan to make it more sophisticated (except bug fixing).