inav
inav copied to clipboard
Added Target JHEMU JHEF405A AIO with build in ELRS Serial RX, Baro and BMI IMU
target for the GSF405A-BMI AIO from jhemcu
tested with GPS, DSHOT600, MAG, BARO and ELRS, working with no issues.
Checked this build with the JHEF405PRO and it does not look to be working correctly.
Perhaps this target need to be renamed JHEF405A to avoid confusion?
I have flown it today, works without issueVon meinem iPhone gesendetAm 23.01.2023 um 20:40 schrieb scottrea123 @.***>: Checked this build with the JHEF405PRO and it does not look to be working correctly. Perhaps this target need to be renamed JHEF405A to avoid confusion?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>
You are using a GSF405A-BMI ?
So maybe name it that - JHEF405PRO is a different board.
The GSF405A-BMI uses the JHEF405PRO target.
inav_5.1.0_JHEF405PRO.hex.zip could you try this binary? I have added the mpu6000 as that's maybe the issue, if your board does not use the bmi270
You are using a GSF405A-BMI ?
So maybe name it that - JHEF405PRO is a different board.
could you maybe again test the hex file provided? if there is no problem there is no need to keep the board from official support since all i can say is the board works without any problem discovered (other than a bit of toiletbowling because of Magnetometer placement) since 22nd of january
did you use this board? https://www.banggood.com/de/25_5x25_5mm-JHEMCU-GSF405A-BMI-F4-AIO-Flight-Controller-5A-4in1-ESC-Built-in-ELRS-2_4G-Receiver-for-RC-Drone-FPV-Racing-p-1949329.html?cur_warehouse=CN&rmmds=search
i contacted JHEMCU and it Is the "GSF405A AIO F405 1-2S BLHELIS 5A ESC" Board. i have received a second brand new one, works perfectly.
I have this board on order in hopes of using it with INAV. It looks like these examples are for 5.1, will this target also work with the recently released INAV 6?
I loaded the binary successfully, but I have two outstanding problems:
- My Baro doesn't work.
- I can't seem to correctly switch motor outputs around (using the mixer) as settings won't save. I plan to just rewire my motors and apply some awkward wire routing to remedy the 2nd one but it sure would be nice to get this onto INAV 6 because it is otherwise a great FC. *This FC: https://www.aliexpress.us/item/3256804935437627.html
I have remapped the motors in the mixer and it works. Which baro does your FC use? Maybe you have to enable it? There isn’t much that can go wrong, since hard wired….Von meinem iPhone gesendetAm 26.04.2023 um 17:03 schrieb salukikev @.***>: I loaded the binary successfully, but I have two outstanding problems:
My Baro doesn't work. I can't seem to correctly switch motor outputs around (using the mixer) as settings won't save. I plan to just rewire my motors and apply some awkward wire routing to remedy the 2nd one but it sure would be nice to get this onto INAV 6 because it is otherwise a great FC.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>
I have remapped the motors in the mixer and it works. Which baro does your FC use? Maybe you have to enable it? There isn’t much that can go wrong, since hard wired….Von meinem iPhone gesendetAm 26.04.2023 um 17:03 schrieb salukikev @.>: I loaded the binary successfully, but I have two outstanding problems: My Baro doesn't work. I can't seem to correctly switch motor outputs around (using the mixer) as settings won't save. I plan to just rewire my motors and apply some awkward wire routing to remedy the 2nd one but it sure would be nice to get this onto INAV 6 because it is otherwise a great FC. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.>
It claims to use BMP280, but that is from the aliexpress description, and I have tried each option and none produce a result. The point may be moot for now as I have managed to brick this FC just when it was getting fun. There doesn't seem to be any physical or electrical damage but nothing I've tried will get this into DFU mode. and window's won't recognize it anymore. This is all the result of trying to load a questionably named alternative target from the vendors github. Lesson learned. I was trying to switch back to Betaflight to try to get more info about the baro at the time and determine if it was working there.
On the oficcial website https://www.jhemcu.com/e_productshow/?75-GSF405A-BMI-75.html it says it has the SPL06 barometer
Am 24.07.2023 um 21:07 schrieb Magicsmoke_mit_Lothar @.***>: On the oficcial website https://www.jhemcu.com/e_productshow/?75-GSF405A-BMI-75.html it says it has the SPL06 barometer
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>
Just looked again, seems they changed without notification.
I've fixed this by adding: #define USE_BARO_DSP310 under the #define USE_BARO_BMP280 line in target.h file before building the target. (Also I have removed the USE_BARO_MS5611 line ) Baro icon in inav is now blue.
@ltwin8 are you still working on this ?
@mmosca I would take over if @ltwin8 abandoned this
I have a working fork and installed inav on that board. It’s on my profile.
@ltwin8 why not merge this this then
To be merged, this needs to at least add SKIP_RELEASES as mentioned above.
As it stands, this does not comply with the new hardware policy.
https://github.com/iNavFlight/inav/blob/master/docs/policies/NEW_HARDWARE_POLICY.md
Official targets added