inavflight / inav-configurator Goto Github PK

As title says. But the values in CLI are correct.

Hi.

Add a new button that when clicked adjusts board alignment so the FC is leveled.

We need to catch up with Betaflight a little bit. Especially MSP needs to be separated into protocol and handler parts - as done here 96115be

See iNavFlight/inav#397 and iNavFlight/inav@8a73616

EDIT: Also remove ONESHOT feature for version 1.2.3+

• feature OneShot125 removed from 1.3 up
• Motor protocol and refresh rate
• Servo refresh rate
• Gyro sync and denom

Just an idea: Could it be possible to use sonar for obstacle avoidance? Maybe place it at the front (facing forward) or at the top (facing to the top). Maybe even multiple modules if possible. Then configure the position in the configurator to match the orientation. What do you think?

After flashing Naze32 with latest release of inav I don's see at all any navigation flight modes in configurator. Are there any limitations for Naze 32 or I can assign modes only via CLI? I was using Inav configurator and not a Cleanflight one.

Drop PID scaling in configurator, use CLI values where possible

With a future support of LTM the iNav-configurator could be used also as GCS. Maps, logging in real time and other tetelemetry features.

just install Inav Configurator 1.0.0 with iNav 1.1
when i try to access menu 'Calibration' it just showing 'Waiting for data'.. don't have clue why

It is not possible to set SerialRX provider with configurator. CLI works

When running INAV Configurator v1.0.2 it reports:

"You are using an old version of INAV - Configurator. There may be a more recent version with improvements and fixes."

Yet, Google extension store shows v1.0.2 as the latest. Is there a newer version or is the app incorrectly reporting that it's old when it's not?

Naze32 rev 5 Full.

When trying to configure LED it will not work.
Wiring order just will not add numbers to leds.

How to fix? :)

I found that if I have "POSHOLD" mode in the switches, "Navigation is safe" will fail. So what is the condition for "Navigation is safe" to pass?

I had all other terms pass, only "Navigation is safe" fail. I had GPS, and got 3D fix but not stable. Because the thick cloud, I could only connect to 4 satellite yesterday.

Is that the problem of too less satellites or anything else?

Thanks~

Calibration tab, makes other tabs unusable until disconnect.

Hi, having issue with using iNav after flash.
When if first got the Airbot F4 with MPU6000 I manage after a while getting to work with iNav, I tried changing some gyro sync settings and after that I cannot get it working again.

I tried flashing iNav 1.3, I tried flashing iNav 1.4 and Betaflight.

When flashing betaflight it just works, no need to install Zadig driver, its there already and I dont have multiple interfaces to install driver to. (interface 0 and interface 1) which shows up dual in device manager after I installed driver on both aswell.

With iNav I tried replacing driver, removing all driver etc etc.
iNav configurator is official from google store.

First I uninstalled all driver to start over:

After that it did not work and I tried to replace interface 1 with WINUSB

That did not work either so I tried to replace interface 0 aswell, this time I have now com ports to connect to.

Flashed betaflight revo, everything is working without doing anything

And then I tried with iNav Revo target, that did not make any difference.

When you click the "Save and Reboot" button in Ports, Failsafe and Blackbox screens, it opens the Configurator screen. Not really a bug, but it gets annoying. :)

This side of iNavFlight/inav#882

After iNavFlight/inav#708 is implemented, allow to set filters via MSP in configurator

A number of the configurator link (github, RCG, IRC) point to cleanflight resources rather than iNav resources.

A new user might find this confusing.

R/P/Y rates, TPA rate and TPA breakpoint is all messed up when using latest configurator master and latest development.

With upcoming airspeed sensor support we'll also need an airspeed sensor icon for Configurator header line. @skaman82 can you create one?

Please add UDP communication connection.

See CF Configurator

When using a mix with servos (i.e. TRI or AIRPLANE) servo bars on the Motor tab are updated only when entering the tab.

I'm able to use it with ez-gui, but Not in windows with chrome configurator

This side of iNavFlight/inav#972

Thank-you for this configurator!
I noticed that if I set failsafe_off_delay in CLI, the allowed range is 0 - 200, but the configurator accepts values up to 2000 and can write values up to 255, beyond this the value is wrapped around to zero at intervals of 256, 512, 768 etc.

Examples - a value of 300 in the configurator writes a value of 44 to the configuration.

My version info:
2017-01-08 @ 14:51:31 -- Running - OS: Windows, Chrome: 55.0.2883.87, Configurator: 1.5.2
2017-01-08 @ 14:51:35 -- Flight controller info, identifier: INAV, version: 1.5.1
2017-01-08 @ 14:51:35 -- Running firmware released on: Jan 4 2017 13:59:21
2017-01-08 @ 14:51:35 -- Board: REF3, version: 0

Multiple users have reported issues with restoring a dump in the CLI, flight modes are sometimes not restored, or only partially. Random settings are not set, and so on. See this issue:
iNavFlight/inav#229

@stronnag wrote

This is a well known feature of all CF firmware variants, the firmware cannot process mode changes fast enough, the buffer overflows, data is lost. This is why the mwptools cf-cfi (cli backup / restore tool) uses a baud rate and context aware inter-line delay. Slower than pasting into a terminal, but reliable.

He then suggested that a 25ms delay after each new line could help.
To all javascript gurus: How can this be implement so we can try it and see if that solves the problem?

Firmware 1.5.1, latest Configurator. Failsafe throttle in the GUI is shown as an arbitrary value.

hello
i am trying to increase the rate of roll and pich in angle mode
can someone give me a tip ?
i am using the latest firmware
thanks
kfir

Like in betaflight/betaflight-configurator#320

Follow up of #56
Inform user that he/she has to enable motor output after flashing the board
Display this info only if PWM_OUTPUT_ENABLE feature has not been enabled

as is iNavFlight/inav/#744

• MSP_SENSOR_CONFIG
• MSP_SET_SENSOR_CONFIG
• MSP_SENSOR_STATUS

Stage 2 images don't look so good.

c5df42c is the commit where it got broken.

Sometimes when I enter the CLI Tab I see some cryptic characters.

As requested by @skaman82

skaman82 [2:48 AM] 
@dzikuvx I would like to make some designs for the new profile tab but for that I need two things to change to style the content properly. I can’t do that myself. (edited)

[2:49]  
1. this list should be a UL > li construct instead of a select input

skaman82 [2:50 AM] 
uploaded this image: Bildschirmfoto 2017-01-13 um 02.48.57.png
Add Comment

skaman82 [2:51 AM] 
Each profile name should appear like this <li class=”profileitem”><a class="someclass">*ProfileName*</a></li> (edited)

[2:53]  
2. I would like to have an image for each configuration in the right box with the preset details. Basically a DIV and the css class changes depending on the selected preset. (edited)

[2:55]  
I have created a new branch “profile-gui” for this

[2:56]  
It would great if you could make this changes

[2:56]  
thanks

skaman82 [3:06 AM] 
If there will be more presets, we maybe should display them in categories or just select the category to show depending on selected mixer (we dont need presets for wings if QuadX is selected, right?) (edited)

skaman82 [3:22 AM] 
if you see this as a starting point for configuration, then showing different categories all together would make sense, but groups like Wings/Mini(Racing)quads/Quads would help if the list is going to be much longer (edited)

When changing the "Gyroscope LPF cutoff frequency", it resets the "Gyroscope task frequency" to 500Hz in asynchronous mode.

Works on cleanflight.

As done here betaflight/betaflight-configurator#281

I could rework the colorscheme a bit to look nicer. The dark blue color is a bit heavy on the yes :). I also think the logo could use some work – and maybe not look so much alike the CF Logo. Do you call it iNAV or iNAVFLIGHT? (first one is a bit nicer - people call you project iNAV anyway). @digitalentity what do you think?

• Rate Acceleration limiting
• MagHold rate limit and MagHold Error LPF
• Iterm ignore rate
• Yaw P limit
• Gyro soft LPF
• dterm_lpf_hz
• yaw_lpf_hz

I am not sure if it is even an option in the current code but it will be good to have RTH selectable in the stage2 settings in the failsafe tab

change line in https://github.com/iNavFlight/inav-configurator/blob/master/js/msp.js#L314
from:
GPS_DATA.alt = data.getUint16(10, 1);
to:
GPS_DATA.alt = data.getInt16(10, 1);

After poking around and running some search scripts i finally manage to find what controls the color of the progress bars in the firmware flasher

https://github.com/iNavFlight/inav-configurator/blob/master/tabs/gps.css#L122
Yes, in the gps.css, makes sense... NOT!

Not sure what fancy blue color code to use here, perhaps @skaman82 would like to do his magic touch on this one?

Support for iNavFlight/inav#706

Hello, I have some questions about the iNavFlight Configurator.

1. In iNav-Configurator, if I set Receiver Mode to RX_MSP, then the value bars will disappear in the Receiver page;
2. The control sticks don’t work when I am using RX_MSP;
3. Previously I wrote a GUI joystick to simulate control sticks and send out signals to the board via UART2 and it works for CleanFlight, but when I move to iNavFlight it doesn’t work any more, so the communication protocol changed? How?
4. If I want to use the Ground control station, how to set up the receiver modes? I am using a pair of XBees to do the wireless communication. Thanks!

I am currently using Naze 32 full rev6 with firmware 1.2.1.

Thanks~
Any reply is greatly appreciated.

I compiled the source code with customized settings and it worked. Thanks~

To make it simpler to setup INAV on various platforms, introduce "Presets" that will set different "internal" parameters depending of platforms properties.

Settings to change in Presets:

• gyro_lpf
• gyro_soft_lpf_hz
• gyro_sync_denom
• acc_soft_lpf_hz
• dterm_lpf_hz
• yaw_lpf_hz
• ROLL/PITCH/YAW PIDs
• LEVEL I (LPF)