-
Notifications
You must be signed in to change notification settings - Fork 36
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
BB51 Adaptations #12
BB51 Adaptations #12
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.
Please, when possible could you check those findings? I think that some changes may be necessary
22e1585
to
3e61070
Compare
Alright, I squashed my commits and this is my proposal for the BB51 adaptations. @damosvil and I tested this on the test boards. I would appreciate if @saidinesh5 and @Burdalfis could too. |
@damosvil I now changed gain to 1 and left the old TEMP_LIMIT value of 49. I tested this with the C_X layout and did not notice any difference - could reproduce the exact sasme RPMs at the same current. Would appreciate others testing this too, but I think this PR is now really good to go. |
Here are the build results |
53de18c
to
73e323f
Compare
73e323f
to
87bf7f9
Compare
Rebased on latest develop. H and L hex files are binary matches:
|
Here are the build results |
Alright, so the last commits adjust EDT temp and temp protection for the different values of internal temp sensor on the BB51. To summarize - the 0ºC offset is different on BB2 and BB51 temperature sensor according to data sheet. On BB2 The temp protection only needed the |
…rder to help prevent regressions during cosmetic changes
57b0e1f
to
b847942
Compare
Here are the build results |
* BB51 has internal reference voltage of 1.65V for ADC, thus we use gain of 0.5 to fully scale up back to 3.3V (this is recommended over using different VDD input ranges as ref) * BB51 Temperature sensor has a different 0degC offset. A high byte of 0x01 is NOT an indication that the temperature is 22.5degC (as it does on BB1 and BB2), instead on the BB51 0x0114 is the 0degC offset. * An adjusted `TEMP_LIMIT` is enough for the temp protection to do its job properly since it is ignoring the hi byte anyway (22.5degC and < 0degC are not high enough temps to trigger it in any way)
b847942
to
b6ab8c1
Compare
Here are the build results |
Here are the build results |
83ec164
to
b6ab8c1
Compare
Here are the build results |
Alright, so now a couple users have run this on their BetaFPV AIO's I am feeling rather confident to release this. Or at least pre-release it. @saidinesh5 @damosvil @Burdalfis any objections? |
I think we can have a release. It is working fine on my side |
I plan to test this out on my hardware this Monday and share my details too. |
FWIW this worked on a test board, but the board is no longer functioning. |
Hmm, crap - which Layout was that? |
A-X-5. Got hot, osd stopped working. Suspect a faulty board instead of bad firmware. |
Mhh, I see, so the main MCU is broken - you can't connect with BF, right? |
Can't connect, no led with usb or lipo. |
OK, then I'd safely assume it was not an issue with Bluejay. Worst case with bluejay you would pop some FETs, or kill a motor. |
See #6
Issues: