(11-Apr-2021, 01:57 PM)lownslow Wrote: Not that this helps you but I recently installed a new HGLRC Zeus F722 stack and the manual shows the settings for the voltage and current perimeters.  The previous stack is had (Lumenier LUX7) also showed the settings in the manual.  I don’t understand why more manufacturers don’t do this as it would sure make life easier..... 

Manufacturer provided scales for voltage are usually in the right ballpark but the current scale the value might not always be correct as this will depend on the ESC you match/paired it with since the current sensor is usually on the ESC.

The HGLRC Zeus F730 stack is one example I found/tested where the current scale was completely wrong in the manual. This was because they have a generic manual for the Hglrc Zeus F722 mini that was paired with a different ESC.

Furthermore on some ESC’s the current sensor data is sent to the FC as an analog signal (current meter source set to onboard adc) and this can be calibrated via Betaflight/iNav. While other ESC’s send the current sensor data via esc telemetry (current meter source set to ESC sensor) and this has to be calibrated via BLHeli.

In general, since most recent FC’s do not have an onboard current sensor, I rather expect ESC manufacturers to provide the correct sensor scale value.

I'm facing the same issue, I cant get the proper current with INAV in the Diatone Mamba basic F405 MK2. Did you solve it?

(03-Sep-2021, 02:04 PM)PeladoMat Wrote: I'm facing the same issue, I cant get the proper current with INAV in the Diatone Mamba basic F405 MK2. Did you solve it?

Which iNav target are you using? Can you take a clear picture of the FC and a CLI dump?

Here are the diffs for both targets that I tried:
https://aricafpv.cl/es/miembros/PeladoFPV/RedGryphus


FC Photo:

Can you post a resource dump?

Based on the dump you posted, it looks like the ADC assignments for current and RSSI are swapped. Try entering this in the CLI:

Still need the resource dump to confirm pin assignments though.

$X>q@<
Entering CLI Mode, type 'exit' to return, or 'help'

# resource dump
IO:
----------------------
A00: FREE
A01: FREE
A02: MOTOR4 OUT
A03: MOTOR1 OUT
A04: MPU CS
A05: SPI1 SCK
A06: SPI1 MISO
A07: SPI1 MOSI
A08: BEEPER OUT
A09: FREE
A10: FREE
A11: USB IN
A12: USB OUT
A13: FREE
A14: FREE
A15: FREE
B00: MOTOR2 OUT
B01: MOTOR3 OUT
B02: FREE
B03: FLASH CS
B04: LED2 OUT
B05: LED1 OUT
B06: I2C1 SCL
B07: I2C1 SDA
B08: FREE
B09: FREE
B10: SERIAL3 UART TX
B11: SERIAL3 UART RX
B12: OSD CS
B13: SPI2 SCK
B14: SPI2 MISO
B15: SPI2 MOSI
C00: INVERTER OUT
C01: ADC CH1
C02: FREE
C03: ADC CH2
C04: MPU EXTI
C05: FREE
C06: SERIAL6 UART TX
C07: SERIAL6 UART RX
C08: FREE
C09: FREE
C10: SPI3 SCK
C11: SPI3 MISO
C12: SPI3 MOSI
C13: FREE
C14: FREE
C15: FREE
D02: FREE

#

Hmm, that shows your current ADC assigned to channel 2, but mapped to pin C03, which should be correct.

Are you seeing any current reading? What is your current scale set to?

(03-Sep-2021, 08:32 PM)V-22 Wrote: Hmm, that shows your current ADC assigned to channel 2, but mapped to pin C03, which should be correct.

Are you seeing any current reading? What is your current scale set to?

I did a full chip erase and tried again the INAV/MAMBAF405 target without pasting my diff and now it works:



Its confusing the the BF target and INAV target are called differently.

thanks for you help!

Great! Happy flying!