Closed krizw closed 2 years ago
Issue-Label Bot is automatically applying the label Feature request
to this issue, with a confidence of 0.56. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!
Links: app homepage, dashboard and code for this bot.
I have contacted a retailer in the UK (cheapdrone.co.uk), that sells this board, and they are interested in supporting my target request by sending a board to a developer, Where and who is willing to assist?
@digitalentity ?
I hope this board will be able to run with INAV too.
I have this board and it is very capable. I also would like to see an inav target for hifionrc f7 pro v2.
Retailer in the UK (cheapdrone.co.uk) wants this board to be featured in our wiki as well which is not in scope of the hardware policy. I guess that's a no-go, unfortunately, unless there is another retailer or board manufacturer who's willing to follow the process.
However, there is ample precedent for the board to have an entry in the official project documentation ("Board - FOO.md"), which can include links to vendors (as happens for a number of Banggood marketed MATEK boards), if that is the vendor's concern.
If they want additional publicity (mention on the Configurator, and / or in the wik ie.g. Supported Boards (which looks horribly outdated) then perhaps there could be a support / sponsorship arrangement, should be vendor wish to be a supporter.
If they want additional publicity (mention on the Configurator, and / or in the wik ie.g. Supported Boards (which looks horribly outdated) then perhaps there could be a support / sponsorship arrangement, should be vendor wish to be a supporter.
Yes, that's what I communicated to them. Featuring a vendor is orthogonal to adding support for a board and should be subject to a separate discussion and agreement.
If they want additional publicity (mention on the Configurator, and / or in the wik ie.g. Supported Boards (which looks horribly outdated) then perhaps there could be a support / sponsorship arrangement, should be vendor wish to be a supporter.
Yes, that's what I communicated to them. Featuring a vendor is orthogonal to adding support for a board and should be subject to a separate discussion and agreement.
Is this the end, or have there been other conversations with the vendor? I agree with your point and expected some issues regarding links to the companies product page. I hope something can be arranged that suits everyone.
There were no further email exchange. I guess the vendor is not interested in INAV supporting this board.
Hello, just saw this issue. I have worked on support for HIFIONRC F722 (AIO and Pro I hope, since both use same unified target in BF).
Hello!
I just got the new HIFIONRC F722 Pro V2 and so I tried to flash inav_2.7.0_HIFIONRCF722.hex on it. I use the INAV Configurator 2.6.1. But after a successful flashing it told me that I have to update the firmware - ... Only CLI was showing after that - and I had to go back to BF.
You need the beta of the configurator, just a Moment, i will Compile 2.6 for you, That should work with configurator 2.6
Thank you very much! I try it right now. It looks as it works, but I have to find out why the magnetometer (BN-880) is not recognized.
we came across this issue before, the "internal" i2c where Baro is connected is not the same as i2c pads afaik
you can try to solder to the i2c used by the barometer, however that requires steady hands
In BF I also had no magnetometer at first, but then I used this command in CLI: set mag_bustype = I2C set mag_i2c_device = 1 set mag_i2c_address = 0
-- but that does not work with INAV.
Sorry, but I am not that good in soldering...
okay, maybe you then have to set something in inav? like mag-type? maybe go with low-ish i2c speed
Like 100 or 400 khz I2C Speed? I have tried that - bud it does not find the magnetometer ether.
Hi to All,
I'm novice here. I bought recently the board FC HIFIONRC F7 PRO V2. Would you please tell me how to flash it? I tried to connect via rx/tx but not successfully. If i press boot button and use usb port the system stops to see it.
You have to connect the FC to your computer via a USB cable. Then open the INAV Configurator - there should a new com appear in the right upper corner. (like COM8). Go to Firmware Flasher in the menu on the left side. Use "Load Firmware [Local]" from bottom right to load inav_2.6.0_HIFIONRCF722.hex from Itwin8 (you have to unzip the file from inav_2.6.0_HIFIONRCF722.hex.zip. Then use "Flash Firmware" (It has to be in DFU-mode for flashing). I hope this helps!
You have to connect the FC to your computer via a USB cable. Then open the INAV Configurator - there should a new com appear in the right upper corner. (like COM8). Go to Firmware Flasher in the menu on the left side. Use "Load Firmware [Local]" from bottom right to load inav_2.6.0_HIFIONRCF722.hex from Itwin8 (you have to unzip the file from inav_2.6.0_HIFIONRCF722.hex.zip. Then use "Flash Firmware" (It has to be in DFU-mode for flashing). I hope this helps!
Doesn't work like that. As soon as i switch to DFU the com port is lost, and it sees as unknown device
You have to connect the FC to your computer via a USB cable. Then open the INAV Configurator - there should a new com appear in the right upper corner. (like COM8). Go to Firmware Flasher in the menu on the left side. Use "Load Firmware [Local]" from bottom right to load inav_2.6.0_HIFIONRCF722.hex from Itwin8 (you have to unzip the file from inav_2.6.0_HIFIONRCF722.hex.zip. Then use "Flash Firmware" (It has to be in DFU-mode for flashing). I hope this helps!
Doesn't work like that. As soon as i switch to DFU the com port is lost, and it sees as unknown device
try impulserc driver fixer
Thats ok. In DFU mode there are no com ports. But it does not flash?
Thats ok. In DFU mode there are no com ports. But it does not flash?
No unfortunately it doesn't flash
what happens when you dont flash - instead connect to a com? Do you see the CLI menu?
what happens when you dont flash - instead connect to a com? Do you see the CLI menu?
Yes, cli mode is available. Initial flash is betaflight 4.2.0
It connects to COM25, as soon as I try flash it having Inav or Betaflight it turns to COM11 (local port) when in boot mode and the flashing process endless
what happens when you dont flash - instead connect to a com? Do you see the CLI menu?
I even tried to connect through rx/tx using usb to TTL adapter and demostratorGUI but it says the board is read-only
What happens when you connect to USB then type dfu
in CLI - does it connect in dfu mode?
What happens when you connect to USB then type
dfu
in CLI - does it connect in dfu mode?
It says no such command
Hmmm. Also in Betaflight?
I would recommend watching some YouTube videos, painless 360, search for flashing FC firmware.On 6 Apr 2021 18:33, Lagarda @.***> wrote:
What happens when you connect to USB then type dfu in CLI - does it connect in dfu mode?
It says no such command
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.
Hmmm. Also in Betaflight?
yeap
I have installed DFU (the impulseRC) but it conflicts with win7 kernel
I tried to rich erase via gui demonstrator, it reflects smth, but anyway i cant succeed
Usually you have to flash within BF orINAV - depending on what firmware you are going to use. I don't even know if its working with the gui demostrator... What Itwin8 mentioned was this driver fixer from impulserc: https://impulserc.blob.core.windows.net/utilities/ImpulseRC_Driver_Fixer.exe
Solved I finally managed with STM 32 CUBE programmer. I have uploaded the inav 2.6.0 but i'm in cli mode only? What should i do then for normal gui?
I have flashed my FC with 2.7.0. but it works only in CLI mode, do you know how to fix it?
Добрый день с компосом еще не решили проблему ?
Unfortunately not. I'm back to Betaflight.
Betaflight есть удержания позиции ?
Добрый день с компосом еще не решили проблему ?
Нет еще. Попробовал оба компаса (магнетометра) QMC and HMC не работают.
ПОдскажите, на какой порт GPS вешать? Does anybody can tell me what port to connect GPS?
With port do you mean UART?
With port do you mean UART?
yeap UART
Current Behavior
I came across the flight controller on a recommendation by Dronemesh (youtube), it has a tremendous specification, and I expected an Inav target would soon appear. I have been unable to contact the manufacturer to request their assistance with an Inav target
Desired Behavior
An INAV target or assistance getting one
Suggested Solution
Development of an INAV target.
Who does this impact? Who is this for?
Those who have purchased this flight controller with INAV in mind.
Additional context
A Betaflight target exists as HIFIONRC F7