Release Candidate #1 of iNav 2.1 was released about an hour ago and is now available at the link below for those interested.

In addition to newly added features and fixed bugs, it now supports a number of F7 boards.

https://github.com/iNavFlight/inav/releases

I've just added Pawel's announcement video for iNav 2.1 to the first post which I was unable to include earlier. Pawel is part of the iNav development team.

WTH is with the OSD Font Manager. It does not finish loading the font. SO, Tramp HV SAYS invalid font. When loading the font the progress bar ONLY GOES 1/2 and STOPS. F722SE LUX also the F722 Matek

Please advise 

Thanks

Maybe it's a bug in the iNav Configurator.

Have you tried the latest version of the configurator (2.1.1)? It was only released 5 hours ago. If not then I would try that first. Link below...

https://github.com/iNavFlight/inav-confi...r/releases

Ignore my previous post. I just saw your other thread saying that you've already tried v2.1.1 of the iNav Configurator.

Hi  All,


I am a total beginner doing my first homebuilt quad and am having trouble getting a Kakute F7 flight controller to get data from a BN-880 in iNAV.  I am running the latest iNAV configurator and have chosen a GPS model. Everything else in iNAV is working fine.  I enabled GPS on the UART 3 I am using and enabled GPS in the configuration.  I have tried two different 880s and have reflashed iNAV.  The 880 quickly get sat locks in that the 880 blue LED is flashing like data and red is slowly blinking so it has power and is working.  In iNAV the GPS icon is red, but all other icons are blue.  Given that the Kakute F7 has a built in compass maybe it is conflicting with the compass in the 880? Is there a way I can turn off the F7 compass with a CLI command? I have triple checked all the wiring, i.e TX to RX and SDA SCL to the same. In the iNAV GPS tab there is no info, no data coming in.  I also tried ublock, it connected but no data.  I really want GPS and return home to work.  I appreciate any suggestions.

Thanks

Bill

(05-Apr-2019, 08:35 PM)amacrine Wrote: Hi  All,


I am a total beginner doing my first homebuilt quad and am having trouble getting a Kakute F7 flight controller to get data from a BN-880 in iNAV.  I am running the latest iNAV configurator and have chosen a GPS model. Everything else in iNAV is working fine.  I enabled GPS on the UART 3 I am using and enabled GPS in the configuration.  I have tried two different 880s and have reflashed iNAV.  The 880 quickly get sat locks in that the 880 blue LED is flashing like data and red is slowly blinking so it has power and is working.  In iNAV the GPS icon is red, but all other icons are blue.  Given that the Kakute F7 has a built in compass maybe it is conflicting with the compass in the 880? Is there a way I can turn off the F7 compass with a CLI command? I have triple checked all the wiring, i.e TX to RX and SDA SCL to the same. In the iNAV GPS tab there is no info, no data coming in.  I also tried ublock, it connected but no data.  I really want GPS and return home to work.  I appreciate any suggestions.

Thanks

Bill

If your F7 compass and gps compass are different hardware, then i guess in INaV configurator you can choose gps compass.
If they are same, then I guess you have to physically remove the compass chip from F7 (which may not be very easy)

(06-Apr-2019, 04:20 AM)sim_tcr Wrote: If your F7 compass and gps compass are different hardware, then i guess in INaV configurator you can choose gps compass.
If they are same, then I guess you have to physically remove the compass chip from F7 (which may not be very easy)

Thanks for the reply.  Clearly this is my first build, and the software is more complex than the building.  It turns out the issue was I had the GPS hooked up to UART 3 TX and RX and TransX hooked to UART 4.  I thought the UARTs were interchangeable and were all usable, but it turns out that at least for a Kakute F7 it wants the 880 on UART 4 and the TransX on UART 6.  Then everything works perfect on the 880, with good sat detection indoors.  Quite a learning curve starting from scratch, but I love the challenge.

(06-Apr-2019, 07:54 PM)amacrine Wrote: Thanks for the reply.  Clearly this is my first build, and the software is more complex than the building.  It turns out the issue was I had the GPS hooked up to UART 3 TX and RX and TransX hooked to UART 4.  I thought the UARTs were interchangeable and were all usable, but it turns out that at least for a Kakute F7 it wants the 880 on UART 4 and the TransX on UART 6.  Then everything works perfect on the 880, with good sat detection indoors.  Quite a learning curve starting from scratch, but I love the challenge.

Amacrine,

What Kakute F7 version do you have?  The AIO or the non-AIO?  I have the non-AIO and have been unable to get iNAV to even connect to the FC after flashing.  I suspect that the firmware only works with the AIO version, but since it works for you, I wanted to see which Kakute F7 you have.

Thanks

(14-Apr-2019, 10:48 PM)fpvnov Wrote: Amacrine,

What Kakute F7 version do you have?  The AIO or the non-AIO?  I have the non-AIO and have been unable to get iNAV to even connect to the FC after flashing.  I suspect that the firmware only works with the AIO version, but since it works for you, I wanted to see which Kakute F7 you have.

Thanks

Hi

I have the non-AOI as I wanted to their simple cable connection to their 4 way ESC which makes a clean build.  I am running iNAV to use GPS return home, but it connected fine in betaflight as well.  I was able flash the latest versions of both betaflight and iNAV with no problem, you have to make sure you are flashing the correct Kakute F7 of both.  I am now having a problem updating the software on a X-XSR receiver by passthru.  Always a challenge.

Good luck

I was not able to update my RX with pass-thru under Inav. I have an R9-Slim+ on my 7", so it was easy enough to plug in my flashing cable to it. Not sure what the issue is. I have not really used any of the GPS features like navigation or RTH, but watching vids...they seem solid and I am looking forward to it!

Oh, the 7" has a Matek F722SE so maybe it is an issue with pass-thru on the F7 boards? Have you experimented with the GPS functions yet?

(14-Apr-2019, 11:55 PM)amacrine Wrote: Hi

I have the non-AOI as I wanted to their simple cable connection to their 4 way ESC which makes a clean build.  I am running iNAV to use GPS return home, but it connected fine in betaflight as well.  I was able flash the latest versions of both betaflight and iNAV with no problem, you have to make sure you are flashing the correct Kakute F7 of both.  I am now having a problem updating the software on a X-XSR receiver by passthru.  Always a challenge.

Good luck

Humm, that is odd.  There is only one iNav firmware file for the Kakute F7 (inav_2.1.0_KAKUTEF7.hex).  I have no problems with Betaflight on my Kakute F7, but while I can flash iNav on the same FC, it won't connect afterwards.  Since your non-AIO works, mine should too.  I will have to work on it some more.

Thanks

(15-Apr-2019, 02:43 AM)fpvnov Wrote: Humm, that is odd.  There is only one iNav firmware file for the Kakute F7 (inav_2.1.0_KAKUTEF7.hex).  I have no problems with Betaflight on my Kakute F7, but while I can flash iNav on the same FC, it won't connect afterwards.  Since your non-AIO works, mine should too.  I will have to work on it some more.

Thanks

For anyone that might see this thread, my issue looks like it was a driver problem.  I went back and re-flashed iNav and now iNav connected just fine after the flash.  I spent hours yesterday and iNav would not connect.  Now it did.  What changed was in between, I had given up on iNav and flashed Arducopter and had downloaded Mission Planner.  When Mission Planner installed, I noticed that it installed/re-installed some drivers and one of them was a STM driver.  What ever drivers I had previously worked just fine for Betaflight, but not iNav.  I suspect that at least one of the drivers installed by Mission Planner was also what iNav needed.  So now it works.

Thanks to amacrine for taking the time to reply.  The confirmation that iNav was working on his Kakute F7 non-AIO got me to try again.

I think the recent Windows 10 update screwed up my iNAV connectivity in that it removed the USB driver that was working perfectly with iNAV.  Moreover when I try to reinstall the drivers using CP210 or STM they both say installed, but neither shows up in USB device manager and I can't connect.   When I ran Zadig it failed and said it was unable to access version data.  I also tried Impulse RC which worked well in the past but now it either doesn't find the Kakute or it fails and says that it found an unexpected number of devices.  So right now I can't connect at all and can't even try reflashing iNAV.  I am at a loss and frustrated. Any suggestions would be greatly appreciated.

(16-Apr-2019, 04:14 PM)amacrine Wrote: I think the recent Windows 10 update screwed up my iNAV connectivity in that it removed the USB driver that was working perfectly with iNAV.  Moreover when I try to reinstall the drivers using CP210 or STM they both say installed, but neither shows up in USB device manager and I can't connect.   When I ran Zadig it failed and said it was unable to access version data.  I also tried Impulse RC which worked well in the past but now it either doesn't find the Kakute or it fails and says that it found an unexpected number of devices.  So right now I can't connect at all and can't even try reflashing iNAV.  I am at a loss and frustrated. Any suggestions would be greatly appreciated.

There are a number of things you can do.  You may need to uninstall the drivers before you install again.  Do CP210, STM, Zadig, or Impulse RC have the option to uninstall drivers?  I would try to clean things up and then install again using as few installers as possible.  It is possible you have too many different versions of the same driver and things are getting confused.

If that does not work, you can consider manually uninstalling from Control Panel, Programs, Programs and Features.  Your drivers will be listed as Windows Driver Package - xxx.

As far as I know you only need two drivers.  DFU (for flashing) which I used Impulse RC to install, and the STM driver (to connect normally).  There are multiple ways to installe the STM driver, and I don't know which way is best.  In my case the Ardupilot Mission Planner software installed the correct driver that worked with iNav.