Inav: JHEMCU F7 - support !

[yo8aiv]

Hi . i don't know if this is the right way to ask for new FC to be supported.

its called JHEMCU F7 target in BF is JHEF7DUAL.
this board could be of better use in iNav than BF since it has so many uart's.
more info
https://github.com/betaflight/betaflight/issues/8605
https://github.com/betaflight/betaflight/pull/7398

Thanks.

[issue-label-bot[bot]]

Issue-Label Bot is automatically applying the label Feature request to this issue, with a confidence of 0.91. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

[digitalentity]

@yo8aiv see https://github.com/iNavFlight/inav/blob/master/docs/policies/NEW_HARDWARE_POLICY.md

[marianomd]

Hello @atgfpeyv could you kindly provide this FC to inav developers?

[marianomd]

Hi, are there guidelines to port fc support from betaflight to inav? Is it too different? I'm considering buying it and maybe I can help. Some guides to get up and running a development environment/sdk/ide? Thanks

[teckel12]

@marianomd Best to start with a similar F7 dual FC target in INAV then use the Betaflight taeget for the FC to add to make the appropriate changes. Then testing each UART, I2C, buzzer, LED, etc. (which is why having the FC in-hand is really required).

Anyway look in Betaflight for a similar FC and start there.

[marianomd]

Thank you Tim, great advise!

El jue., 29 de ago. de 2019 22:46, Tim Eckel [e-mail]
escribió:

@marianomd https://github.com/marianomd Best to start with a similar F7
dual FC target in INAV then use the Betaflight taeget for the FC to add to
make the appropriate changes. Then testing each UART, I2C, buzzer, LED,
etc. (which is why having the FC in-hand is really required).

Anyway look in Betaflight for a similar FC and start there.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/iNavFlight/inav/issues/5002?email_source=notifications&email_token=AACDELKXRTXNFSUSMF5WHKTQHB3YTA5CNFSM4IK2E5NKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5QJHHA#issuecomment-526422940,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACDELKOOAJ6GRIXKP2IVS3QHB3YTANCNFSM4IK2E5NA
.

[waynoedm]

`dump

version

Betaflight / JHEF7DUAL (JH7D) 4.0.6 Sep 1 2019 / 00:43:08 (2a64051a2) MSP API: 1.41

start the command batch

batch start

board_name JHEF7DUAL
manufacturer_id

name

name -

resources

resource BEEPER 1 C15
resource MOTOR 1 B00
resource MOTOR 2 B01
resource MOTOR 3 B04
resource MOTOR 4 B03
resource MOTOR 5 C09
resource MOTOR 6 C08
resource MOTOR 7 NONE
resource MOTOR 8 NONE
resource SERVO 1 NONE
resource SERVO 2 NONE
resource SERVO 3 NONE
resource SERVO 4 NONE
resource SERVO 5 NONE
resource SERVO 6 NONE
resource SERVO 7 NONE
resource SERVO 8 NONE
resource PPM 1 A03
resource PWM 1 NONE
resource PWM 2 NONE
resource PWM 3 NONE
resource PWM 4 NONE
resource PWM 5 NONE
resource PWM 6 NONE
resource PWM 7 NONE
resource PWM 8 NONE
resource LED_STRIP 1 A08
resource SERIAL_TX 1 A09
resource SERIAL_TX 2 A02
resource SERIAL_TX 3 B10
resource SERIAL_TX 4 A00
resource SERIAL_TX 5 C12
resource SERIAL_TX 6 C06
resource SERIAL_TX 7 NONE
resource SERIAL_TX 8 NONE
resource SERIAL_TX 9 NONE
resource SERIAL_TX 10 NONE
resource SERIAL_RX 1 A10
resource SERIAL_RX 2 A03
resource SERIAL_RX 3 B11
resource SERIAL_RX 4 A01
resource SERIAL_RX 5 D02
resource SERIAL_RX 6 C07
resource SERIAL_RX 7 NONE
resource SERIAL_RX 8 NONE
resource SERIAL_RX 9 NONE
resource SERIAL_RX 10 NONE
resource I2C_SCL 1 B06
resource I2C_SCL 2 NONE
resource I2C_SCL 3 NONE
resource I2C_SCL 4 NONE
resource I2C_SDA 1 B07
resource I2C_SDA 2 NONE
resource I2C_SDA 3 NONE
resource I2C_SDA 4 NONE
resource LED 1 A15
resource LED 2 NONE
resource LED 3 NONE
resource RX_BIND 1 NONE
resource RX_BIND_PLUG 1 NONE
resource SPI_SCK 1 A05
resource SPI_SCK 2 B13
resource SPI_SCK 3 C10
resource SPI_SCK 4 NONE
resource SPI_MISO 1 A06
resource SPI_MISO 2 B14
resource SPI_MISO 3 C11
resource SPI_MISO 4 NONE
resource SPI_MOSI 1 A07
resource SPI_MOSI 2 B15
resource SPI_MOSI 3 B05
resource SPI_MOSI 4 NONE
resource CAMERA_CONTROL 1 B08
resource ADC_BATT 1 C02
resource ADC_RSSI 1 C00
resource ADC_CURR 1 C01
resource ADC_EXT 1 NONE
resource BARO_CS 1 NONE
resource PINIO 1 C14
resource PINIO 2 B09
resource PINIO 3 NONE
resource PINIO 4 NONE
resource USB_MSC_PIN 1 NONE
resource FLASH_CS 1 C13
resource OSD_CS 1 B12
resource GYRO_EXTI 1 C04
resource GYRO_EXTI 2 C03
resource GYRO_CS 1 B02
resource GYRO_CS 2 A04

timer

timer A03 AF3

pin A03: TIM9 CH2 (AF3)

timer B00 AF2

pin B00: TIM3 CH3 (AF2)

timer B01 AF2

pin B01: TIM3 CH4 (AF2)

timer B04 AF2

pin B04: TIM3 CH1 (AF2)

timer B03 AF1

pin B03: TIM2 CH2 (AF1)

timer C09 AF3

pin C09: TIM8 CH4 (AF3)

timer C08 AF3

pin C08: TIM8 CH3 (AF3)

timer A08 AF1

pin A08: TIM1 CH1 (AF1)

timer B08 AF2

pin B08: TIM4 CH3 (AF2)

dma

dma SPI_TX 1 NONE
dma SPI_TX 2 NONE
dma SPI_TX 3 NONE
dma SPI_TX 4 NONE
dma SPI_RX 1 NONE
dma SPI_RX 2 NONE
dma SPI_RX 3 NONE
dma SPI_RX 4 NONE
dma ADC 1 NONE
dma ADC 2 NONE
dma ADC 3 0

ADC 3: DMA2 Stream 0 Channel 2

dma UART_TX 1 NONE
dma UART_TX 2 NONE
dma UART_TX 3 NONE
dma UART_TX 4 NONE
dma UART_TX 5 NONE
dma UART_TX 6 NONE
dma UART_TX 7 NONE
dma UART_TX 8 NONE
dma UART_RX 1 NONE
dma UART_RX 2 NONE
dma UART_RX 3 NONE
dma UART_RX 4 NONE
dma UART_RX 5 NONE
dma UART_RX 6 NONE
dma UART_RX 7 NONE
dma UART_RX 8 NONE
dma pin A03 NONE
dma pin B00 0

pin B00: DMA1 Stream 7 Channel 5

dma pin B01 0

pin B01: DMA1 Stream 2 Channel 5

dma pin B04 0

pin B04: DMA1 Stream 4 Channel 5

dma pin B03 0

pin B03: DMA1 Stream 6 Channel 3

dma pin C09 0

pin C09: DMA2 Stream 7 Channel 7

dma pin C08 0

pin C08: DMA2 Stream 2 Channel 0

dma pin A08 0

pin A08: DMA2 Stream 6 Channel 0

dma pin B08 0

pin B08: DMA1 Stream 7 Channel 2

`

[atgfpeyv]

Forgive me for being late, so what should I do for inav to support this board?

[craterghost]

I don't get it either. Is it possible to change the JHEF7DUAL.hex file from betaflight to one that's readable by INAV? What can we do to speed up the process of Supporting the FC?

[xD90o1]

I don't get it either. Is it possible to change the JHEF7DUAL.hex file from betaflight to one that's readable by INAV? What can we do to speed up the process of Supporting the FC?

Looking at the target.c of both betaflight and inav targets they seem to differ quite alot although I somehow managed to make a hex file for this specific fc though. I still couldn't manage to make the user modes work sadly

[craterghost]

would u mind sending me the hex file u already made?

On Fri, Nov 1, 2019 at 3:02 PM +0100, "Ace Ervite" [e-mail] wrote:

I don't get it either. Is it possible to change the JHEF7DUAL.hex file from betaflight to one that's readable by INAV? What can we do to speed up the process of Supporting the FC?

Looking at the target.c of both betaflight and inav targets they seem to differ quite alot although I somehow managed to make a hex file for this specific fc though. I still couldn't manage to make the user modes work sadly

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

[xD90o1]

Forgive me for being late, so what should I do for inav to support this board?

As per the New Hardware Policy md, New targets are accepted into INAV code if the board manufacturer itself provides the specs, schematics, and production samples to at least 2 core devs. Or, a community member, or board manufacturer provides board samples to at least 1 core dev and the target itself already exists in the official Cleanflight or Betaflight firmware.

[craterghost]

or I just write the code myself... can't be that hard tbh... not worth spending 20 bucks. The specs are pretty much the same as the matek F722 so I just try modding the code for the matek board with the parameters from the jhef7dual code from betaflight.

On Fri, Nov 1, 2019 at 3:55 PM +0100, "Ace Ervite" [e-mail] wrote:

Forgive me for being late, so what should I do for inav to support this board?

Also as per the New Hardware Policy md, New targets are accepted into INAV code if the board manufacturer itself provides the specs, schematics, and production samples to at least 2 core devs. Or, a community member, or board manufacturer provides board samples to at least 1 core dev and the target itself already exists in the official Cleanflight or Betaflight firmware.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

[redeyejoe]

Has anyone had any luck getting this f7 flight controller working with i nav??
I would like to be able to use its features with more gps control...

[xD90o1]

Has anyone had any luck getting this f7 flight controller working with i nav??
I would like to be able to use its features with more gps control...

I have quite some success except for the user modes. I just can't seem to get it working

[aknack]

hi inav team! great job so far!

is there any progress on this FC?

[JoseAntonioMG]

Hello, I also have this FC and I have configured it with Betaflight, but I would like to have the INAV firmware, since I am building a Long Range quad with GPS.

[redeyejoe]

Has anyone had any luck getting this f7 flight controller working with i nav??
I would like to be able to use its features with more gps control...

I have quite some success except for the user modes. I just can't seem to get it working

did you make you own fireware or what are you using to make it work partially? Can you share the file you are using that is partially working?
thanks,

[xD90o1]

I started with a source code of a dual flight controller that's present
here in inav and then I just go ahead and change the pinouts accordingly to
match the ones used in the JHE F7 Dual. It's already working but I just
can't make the user modes work

On Sat, Jan 11, 2020, 03:49 redeyejoe [e-mail] wrote:

Has anyone had any luck getting this f7 flight controller working with i
nav??
I would like to be able to use its features with more gps control...

I have quite some success except for the user modes. I just can't seem to
get it working

did you make you own fireware or what are you using to make it work
partially?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/iNavFlight/inav/issues/5002?email_source=notifications&email_token=AHZRTEK2OHC73A7KYTHNS5TQ5DGM7A5CNFSM4IK2E5NKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIVAUTY#issuecomment-573180495,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHZRTEOB5IGHC6FP3G25R33Q5DGM7ANCNFSM4IK2E5NA
.

[redeyejoe]

I started with a source code of a dual flight controller that's present here in inav and then I just go ahead and change the pinouts accordingly to match the ones used in the JHE F7 Dual. It's already working but I just can't make the user modes work
…
On Sat, Jan 11, 2020, 03:49 redeyejoe @.*> wrote: Has anyone had any luck getting this f7 flight controller working with i nav?? I would like to be able to use its features with more gps control... I have quite some success except for the user modes. I just can't seem to get it working did you make you own fireware or what are you using to make it work partially? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#5002?email_source=notifications&email_token=AHZRTEK2OHC73A7KYTHNS5TQ5DGM7A5CNFSM4IK2E5NKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIVAUTY#issuecomment-573180495>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHZRTEOB5IGHC6FP3G25R33Q5DGM7ANCNFSM4IK2E5NA .
Can you share you file?

[smaller09]

I started with a source code of a dual flight controller that's present here in inav and then I just go ahead and change the pinouts accordingly to match the ones used in the JHE F7 Dual. It's already working but I just can't make the user modes work
…
On Sat, Jan 11, 2020, 03:49 redeyejoe @.*> wrote: Has anyone had any luck getting this f7 flight controller working with i nav?? I would like to be able to use its features with more gps control... I have quite some success except for the user modes. I just can't seem to get it working did you make you own fireware or what are you using to make it work partially? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#5002?email_source=notifications&email_token=AHZRTEK2OHC73A7KYTHNS5TQ5DGM7A5CNFSM4IK2E5NKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIVAUTY#issuecomment-573180495>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHZRTEOB5IGHC6FP3G25R33Q5DGM7ANCNFSM4IK2E5NA .

did you add the pinio pins into target.h

define USE_PINIO

define USE_PINIOBOX

define PINIO1_PIN PC14 // VTX power switcher

define PINIO2_PIN PB09 // 2xCamera switcher

[soninua]

Hello!
Are there any changes with this board? Someone was able to do it with INAV?

[redeyejoe]

I started with a source code of a dual flight controller that's present here in inav and then I just go ahead and change the pinouts accordingly to match the ones used in the JHE F7 Dual. It's already working but I just can't make the user modes work
…
On Sat, Jan 11, 2020, 03:49 redeyejoe _@_.*> wrote: Has anyone had any luck getting this f7 flight controller working with i nav?? I would like to be able to use its features with more gps control... I have quite some success except for the user modes. I just can't seem to get it working did you make you own fireware or what are you using to make it work partially? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#5002?email_source=notifications&email_token=AHZRTEK2OHC73A7KYTHNS5TQ5DGM7A5CNFSM4IK2E5NKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIVAUTY#issuecomment-573180495>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHZRTEOB5IGHC6FP3G25R33Q5DGM7ANCNFSM4IK2E5NA .

did you add the pinio pins into target.h

define USE_PINIO

define USE_PINIOBOX

define PINIO1_PIN PC14 // VTX power switcher

define PINIO2_PIN PB09 // 2xCamera switcher

Is there any way you could just post your working bin file so I can try it how it is? Thanks

[smaller09]

I started with a source code of a dual flight controller that's present here in inav and then I just go ahead and change the pinouts accordingly to match the ones used in the JHE F7 Dual. It's already working but I just can't make the user modes work
…
On Sat, Jan 11, 2020, 03:49 redeyejoe _@_.*> wrote: Has anyone had any luck getting this f7 flight controller working with i nav?? I would like to be able to use its features with more gps control... I have quite some success except for the user modes. I just can't seem to get it working did you make you own fireware or what are you using to make it work partially? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#5002?email_source=notifications&email_token=AHZRTEK2OHC73A7KYTHNS5TQ5DGM7A5CNFSM4IK2E5NKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIVAUTY#issuecomment-573180495>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHZRTEOB5IGHC6FP3G25R33Q5DGM7ANCNFSM4IK2E5NA .

did you add the pinio pins into target.h

define USE_PINIO

define USE_PINIOBOX

define PINIO1_PIN PC14 // VTX power switcher

define PINIO2_PIN PB09 // 2xCamera switcher

Is there any way you could just post your working bin file so I can try it how it is? Thanks

inav_2.4.0_JHEMCUF7DUAL.zip
not have time to test yet, please report back

[aknack]

the .hex included in the zip does not work on my FC.
after flashing and powering it makes 4 (or 5) very quick beeps, followed by 2 longer ones.
this repeats until the FC reboots on itself. and then beeps again in same manner.

after reflashing it with

# version
# Betaflight / STM32F7X2 (S7X2) 4.1.3 Jan 16 2020 / 11:35:53 (543a5e1ba) MSP API: 1.42
# manufacturer_id: JHEF   board_name: JHEF7DUAL   custom defaults: YES

all is fine again.

[xD90o1]

I started with a source code of a dual flight controller that's present here in inav and then I just go ahead and change the pinouts accordingly to match the ones used in the JHE F7 Dual. It's already working but I just can't make the user modes work
…
On Sat, Jan 11, 2020, 03:49 redeyejoe _@_.*> wrote: Has anyone had any luck getting this f7 flight controller working with i nav?? I would like to be able to use its features with more gps control... I have quite some success except for the user modes. I just can't seem to get it working did you make you own fireware or what are you using to make it work partially? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#5002?email_source=notifications&email_token=AHZRTEK2OHC73A7KYTHNS5TQ5DGM7A5CNFSM4IK2E5NKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIVAUTY#issuecomment-573180495>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHZRTEOB5IGHC6FP3G25R33Q5DGM7ANCNFSM4IK2E5NA .

did you add the pinio pins into target.h

define USE_PINIO

define USE_PINIOBOX

define PINIO1_PIN PC14 // VTX power switcher

define PINIO2_PIN PB09 // 2xCamera switcher

Is there any way you could just post your working bin file so I can try it how it is? Thanks

inav_2.4.0_JHEMCUF7DUAL.zip
not have time to test yet, please report back

JHEF7DUAL.zip

Here's my try at the code for the JHE F7 Dual

[soninua]

Я начал с исходного кода контроллера двойного полета, который присутствует здесь в inav, а затем я просто иду вперед и изменяю pinouts соответственно, чтобы соответствовать тем, которые используются в Jhe F7 Dual. Это уже работает, но я просто не могу заставить пользовательские режимы работать
...
On Sat, Jan 11, 2020, 03: 49 redeyejoe _@_.* > написал: кому-нибудь повезло получить этот контроллер полета f7, работающий с I nav?? Я хотел бы иметь возможность использовать его функции с большим контролем gps... У меня есть довольно некоторый успех, за исключением пользовательских режимов. Я просто не могу заставить его работать вы сделали себе собственное программное обеспечение или что вы используете, чтобы заставить его работать частично? — Вы получаете это, потому что вы подписаны на эту нить. Ответьте на это письмо напрямую, просмотрите его на GitHub < #5002?email_source=notifications&email_token=AHZRTEK2OHC73A7KYTHNS5TQ5DGM7A5CNFSM4IK2E5NKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIVAUTY#issuecomment-573180495>, или отписаться > https://github.com/notifications/unsubscribe-auth/AHZRTEOB5IGHC6FP3G25R33Q5DGM7ANCNFSM4IK2E5NA -да .

вы добавили булавки pinio в target?h

определите USE_PINIO

определите USE_PINIOBOX

определить PINIO1_PIN PC14 / / VTX Power switcher

определить pinio2_pin pb09 / / 2xcamera switcher

Is there any way you could just post your working bin file so I can try it how it is? Thanks

inav_2.4.0_JHEMCUF7DUAL.zip
not have time to test yet, please report back

Hello!
This version does not work, there is no communication in the configurator, the board reboots after 5-6 seconds.

[soninua]

Я начал с исходного кода контроллера двойного полета, который присутствует здесь в inav, а затем я просто иду вперед и изменяю pinouts соответственно, чтобы соответствовать тем, которые используются в Jhe F7 Dual. Это уже работает, но я просто не могу заставить пользовательские режимы работать
...
On Sat, Jan 11, 2020, 03: 49 redeyejoe _@_.* > написал: кому-нибудь повезло получить этот контроллер полета f7, работающий с I nav?? Я хотел бы иметь возможность использовать его функции с большим контролем gps... У меня есть довольно некоторый успех, за исключением пользовательских режимов. Я просто не могу заставить его работать вы сделали себе собственное программное обеспечение или что вы используете, чтобы заставить его работать частично? — Вы получаете это, потому что вы подписаны на эту нить. Ответьте на это письмо напрямую, просмотрите его на GitHub < #5002?email_source=notifications&email_token=AHZRTEK2OHC73A7KYTHNS5TQ5DGM7A5CNFSM4IK2E5NKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIVAUTY#issuecomment-573180495>, или отписаться > https://github.com/notifications/unsubscribe-auth/AHZRTEOB5IGHC6FP3G25R33Q5DGM7ANCNFSM4IK2E5NA -да .

вы добавили булавки pinio в target?h

определите USE_PINIO

определите USE_PINIOBOX

определить PINIO1_PIN PC14 / / VTX Power switcher

определить pinio2_pin pb09 / / 2xcamera switcher

Есть ли какой-либо способ, которым вы можете просто опубликовать свой рабочий файл bin, чтобы я мог попробовать его, как это есть? Спасибо

inav_2. 4.0_JHEMCUF7DUAL.zip
еще не успел протестировать, пожалуйста доложите

JHEF7DUAL.застежка-молния

Вот моя попытка в коде для Jhe F7 Dual

Hello!
This version works, the configurator 2.2.1 works fine. I did not have time to test everything. There is communication with the board in the configurator program, the sensors are working. We need to test further. can this version be rebuilt under 2.4.0 INAV?

[xD90o1]

It can be. I think the target source codes for the 2.2.1 and 2.4.0 don't
differ that much.

On Wed, Feb 5, 2020 at 3:51 AM soninua [e-mail] wrote:

Я начал с исходного кода контроллера двойного полета, который присутствует
здесь в inav, а затем я просто иду вперед и изменяю pinouts соответственно,
чтобы соответствовать тем, которые используются в Jhe F7 Dual. Это уже
работает, но я просто не могу заставить пользовательские режимы работать
... <#m_2167389971052229994_>
On Sat, Jan 11, 2020, 03: 49 redeyejoe @.* > написал: кому-нибудь
повезло получить этот контроллер полета f7, работающий с I nav?? Я хотел бы
иметь возможность использовать его функции с большим контролем gps... У
меня есть довольно некоторый успех, за исключением пользовательских
режимов. Я просто не могу заставить его работать вы сделали себе
собственное программное обеспечение или что вы используете, чтобы заставить
его работать частично? — Вы получаете это, потому что вы подписаны на эту
нить. Ответьте на это письмо напрямую, просмотрите его на GitHub < #5002
https://github.com/iNavFlight/inav/issues/5002?email_source=notifications&email_token=AHZRTEK2OHC73A7KYTHNS5TQ5DGM7A5CNFSM4IK2E5NKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIVAUTY#issuecomment-573180495>,
или отписаться > https://github.com/notifications/unsubscribe-auth/AHZRTEOB5IGHC6FP3G25R33Q5DGM7ANCNFSM4IK2E5NA
-да
https://github.com/notifications/unsubscribe-auth/AHZRTEOB5IGHC6FP3G25R33Q5DGM7ANCNFSM4IK2E5NA
.

вы добавили булавки pinio в target?h

определите USE_PINIO

определите USE_PINIOBOX

определить PINIO1_PIN PC14 / / VTX Power switcher

определить pinio2_pin pb09 / / 2xcamera switcher

Есть ли какой-либо способ, которым вы можете просто опубликовать свой
рабочий файл bin, чтобы я мог попробовать его, как это есть? Спасибо

inav_2. 4.0_JHEMCUF7DUAL.zip
https://github.com/iNavFlight/inav/files/4148858/inav_2.4.0_JHEMCUF7DUAL.zip
еще не успел протестировать, пожалуйста доложите

JHEF7DUAL.застежка-молния
https://github.com/iNavFlight/inav/files/4153482/JHEF7DUAL.zip

Вот моя попытка в коде для Jhe F7 Dual

Hello!
This version works, the configurator 2.2.1 works fine. I did not have time
to test everything. There is communication with the board in the
configurator program, the sensors are working. We need to test further. can
this version be rebuilt under 2.4.0 INAV?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/iNavFlight/inav/issues/5002?email_source=notifications&email_token=AHZRTENIU5W5BZX5TBPKXHDRBHBNHA5CNFSM4IK2E5NKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKY6VAY#issuecomment-582085251,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHZRTEOFIYV67D273SW3EBLRBHBNHANCNFSM4IK2E5NA
.

[aknack]

it builds unter origin/master:

Building JHEF7DUAL succeeded.
ak@osboxes:inav$ ll obj/inav_2.3.0_JHEF7DUAL.hex
-rw-r--r-- 1 ak ak 897K Feb  6 03:22 obj/inav_2.3.0_JHEF7DUAL.hex

and also builds unter 2.4.0-RC2

Building JHEF7DUAL succeeded.
ak@osboxes:inav$ ll obj/inav_2.4.0_JHEF7DUAL.hex
-rw-r--r-- 1 ak ak 924K Feb  6 03:30 obj/inav_2.4.0_JHEF7DUAL.hex

inav_2.4.0_JHEF7DUAL.hex.zip

[xD90o1]

I want to know if the user modes work out for you guys

On Thu, Feb 6, 2020, 16:37 aknack [e-mail] wrote:

it builds unter origin/master:

Building JHEF7DUAL succeeded.
ak@osboxes:inav$ ll obj/inav_2.3.0_JHEF7DUAL.hex
-rw-r--r-- 1 ak ak 897K Feb 6 03:22 obj/inav_2.3.0_JHEF7DUAL.hex

and also builds unter 2.4.0-RC2

Building JHEF7DUAL succeeded.
ak@osboxes:inav$ ll obj/inav_2.4.0_JHEF7DUAL.hex
-rw-r--r-- 1 ak ak 924K Feb 6 03:30 obj/inav_2.4.0_JHEF7DUAL.hex

inav_2.4.0_JHEF7DUAL.hex.zip
https://github.com/iNavFlight/inav/files/4163984/inav_2.4.0_JHEF7DUAL.hex.zip

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/iNavFlight/inav/issues/5002?email_source=notifications&email_token=AHZRTEOXMJLWEXHQR7ZR7ETRBPD4LA5CNFSM4IK2E5NKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEK6LVDY#issuecomment-582793871,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHZRTENKATD5RDUPXDPXRYTRBPD4LANCNFSM4IK2E5NA
.

[aknack]

user modes are NOT morking for me.
according to https://ae01.alicdn.com/kf/HTB11y.9VMHqK1RjSZFgq6y7JXXaT.jpg
i can power the vtx with BF413 ,
but not with the compiled .hex unter INAV. anyhow this version connects with the configurator.

[xD90o1]

Unfortunately, that's the brick wall I've ran into months ago when I use
that firmware which I tried coding for that fc for inav.

On Thu, Feb 6, 2020, 17:51 aknack [e-mail] wrote:

user modes are NOT morking for me.
according to https://ae01.alicdn.com/kf/HTB11y.9VMHqK1RjSZFgq6y7JXXaT.jpg
i can power the vtx with BF413 ,
but not with the compiled .hex unter INAV. this version connects with the
configurator.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/iNavFlight/inav/issues/5002?email_source=notifications&email_token=AHZRTENMXO75TWLOB2CYNX3RBPMQVA5CNFSM4IK2E5NKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEK6SSFI#issuecomment-582822165,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHZRTEORO7TUPM7TMTQGLKTRBPMQVANCNFSM4IK2E5NA
.

[aknack]

a shame, since its a good F7+baro for a very good price.

[smaller09]

user modes are NOT morking for me.
according to https://ae01.alicdn.com/kf/HTB11y.9VMHqK1RjSZFgq6y7JXXaT.jpg
i can power the vtx with BF413 ,
but not with the compiled .hex unter INAV. anyhow this version connects with the configurator.

I think the problem should be in the config.c

void targetConfiguration(void)
{
pinioBoxConfigMutable()->permanentId[0] = 40;
pinioBoxConfigMutable()->permanentId[1] = 41;
}

#endif

the two ID should be the MENU ID, so it could not use the number from BF
I took that from the MATEKF765

void targetConfiguration(void)
{
pinioBoxConfigMutable()->permanentId[0] = 47;
pinioBoxConfigMutable()->permanentId[1] = 48;
}

You can try it.

[aknack]

smaller09 , you''re the man ! :)

i can confirm user-modes are working. can't confirm yet, that it will fly.
inav_2.4.0_JHEF7DUAL_smaller09_menu_patch.zip

[xD90o1]

As long as there are no conflicts with the timers, it'll fly just fine

On Sat, Feb 8, 2020, 22:45 aknack [e-mail] wrote:

smaller09 , you''re the man ! :)

i can confirm user-modes are working. can't confirm yet, that it will fly.
inav_2.4.0_JHEF7DUAL_smaller09_menu_patch.zip
https://github.com/iNavFlight/inav/files/4174416/inav_2.4.0_JHEF7DUAL_smaller09_menu_patch.zip

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/iNavFlight/inav/issues/5002?email_source=notifications&email_token=AHZRTEPP2F7KBMZWAF26LELRB3AO7A5CNFSM4IK2E5NKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELFTJII#issuecomment-583742625,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHZRTEKCH5S3N5KLFVG6QGLRB3AO7ANCNFSM4IK2E5NA
.

[aknack]

all seems fine, but i'm unable to arm. still debugging.
any ideas?

[aknack]

Pre-arming checks : all green
cli status :
Arming disabled flags: CLI
gps shows 6 satellites : ready to fly
T16 bound via fport : ok

still it won't arm if detached from computer.
JHEF7DUAL2.4.0_dump_all.zip

[xD90o1]

Pre-arming checks : all green
cli status :
Arming disabled flags: CLI
gps shows 6 satellites : ready to fly
T16 bound via fport : ok

still it won't arm if detached from computer.
JHEF7DUAL2.4.0_dump_all.zip

Do you have a beeper? Beepers really help a lot when knowing if it's ready to arm.

[aknack]

yes. i have a beeper.
opentx-inav-lua-amber-sound-pack tells me "ready to fly"
the beeper stays silent when arming, but the FC does not arm.

[michaelj0hn]

As I have the same FC and was surprised there wasn't an INAV image for it, I had to google :) Found this discussion, used the image that was posted here. I can confirm that the quad arms and flies without any problems.

[JoseAntonioMG]

Hello, I have installed the firmware that has been published here and, apparently, the quad works, it is armed and it seems to fly, the yaw does work and I can turn it, the throttle also works and I can go up and down, but when trying to use the pitch and roll, the quad does not respond and remains in the same position.

The quad uses GPS and magnetometer, I have calibrated it correctly (gyroscope, accelerometer and compass).

I have changed the firmware for the betaflight and everything works perfectly.

[xD90o1]

Hello, I have installed the firmware that has been published here and, apparently, the quad works, it is armed and it seems to fly, the yaw does work and I can turn it, the throttle also works and I can go up and down, but when trying to use the pitch and roll, the quad does not respond and remains in the same position.

The quad uses GPS and magnetometer, I have calibrated it correctly (gyroscope, accelerometer and compass).

I have changed the firmware for the betaflight and everything works perfectly.

That's odd..
I've changed some of its timers since it conflicts with existing timers when I jumped the gap to iNav but then I seem to overlook the issue and focus only on fixed wing aircrafts that I forgot to check if it works for quads as well.

[michaelj0hn]

[..] when trying to use the pitch and roll, the quad does not respond and remains in the same position.

I do not have any issues like this, quad is moving well in all directions.

The quad uses GPS and magnetometer, I have calibrated it correctly (gyroscope, accelerometer and compass).

I do not have GPS or a magnetometer connected, but assuming this should not make a difference when in flying in ANGL mode.

[michaelj0hn]

When testing ALTHOLD, it however resulted in the quad violently flipping over and crashing to the ground. This was with pure ANGL mode, no compass or GPS modes had been added. Any idea what this could have caused?

[xD90o1]

Just to let you know I've forked this repo with the JHE F7 Dual target added so I can test more on this.

[aknack]

@xD90o1
im building a new quad based on this FC [ pro version with baro ] and i will be using inav_2.4.0_JHEF7DUAL.hex from your fork.

[xD90o1]

I haven't tested this yet on the deluxe version as I only have the acro version but hopefully they would just be the same since acro lacks only a second IMU and a Flash Memory

[aknack]

step 1: r9 mini on t2 via fport: works.

[aknack]

step 2: attached https://www.banggood.com/de/Anniversary-Special-Edition-Racerstar-REV35-35A-BLheli_S-3-6S-4-In-1-ESC-Built-in-Current-Sensor-for-RC-Drone-p-1180734.html?rmmds=myorder&cur_warehouse=CN , flahed them successfully via jesc. -> passthrough works fine.

[aknack]

step 3: attached motor on M1. ESC initialisation peep suggests: all fine.

[aknack]

step 4: rc-mode: angle.
arming, and look whats happening:
https://youtu.be/MdWsASn1UHs

[aknack]

ok, that video might help you guys for debugging:

https://youtu.be/GXO2XZ3cnbc

[xD90o1]

It might be one of two problems which is

A: ESC Issue - when you arm, the motor spins for awhile and stops even when armed, yeah? That could probably mean a bad ESC or;

B: Timer Conflict - Although I've already made sure that no such conflicts would appear in config.c

[xD90o1]

I haven't really tested it yet with DShot with a Multirotor config since the ESC I had used in my plane is a generic hobbywing 30A that can only use PWM Signal.

[aknack]

i'd exclude ESC issues. since i had problems with at least 3 different ones that all worked fine with BF.
i can support you with hardware if you whish.

[xD90o1]

That's the deluxe board you're using, right? Mine is the acrk versuon with a blue color on the solder mask of its board

[aknack]

jepp.

there is the barometer:

[xD90o1]

From what I've read however in the website, the difference between acro and
deluxe is that the deluxe has dual gyro and a flash memory while the acro
doesn't have those

On Fri, Feb 28, 2020, 20:54 aknack [e-mail] wrote:

jepp.

there is the barometer:

[image: WhatsApp Image 2020-02-28 at 13 52 11]
https://user-images.githubusercontent.com/6792254/75550223-c39d8880-5a31-11ea-8eaa-3ba5a81886c0.jpeg

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/iNavFlight/inav/issues/5002?email_source=notifications&email_token=AHZRTEL3YGK25CFWUHDCDSDRFECORA5CNFSM4IK2E5NKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENINMBI#issuecomment-592500229,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHZRTEMFBUI3SH5Q4ZQKXVTRFECORANCNFSM4IK2E5NA
.

[aknack]

i tried to switch the gyro from gyro 0 shown as MPU600

set gyro_to_use=1
set acc_hardware = ICM20689
save

the FC now seems to reboot over and over.
i'm not able to connect to the FC with inav

as far as i remember gyro #0 in betaflight is the ICM and #1 is MPU,

[michaelj0hn]

@aknack @xD90o1 I did not have any problems with getting the motors running and was actually flying a few batteries. I am attaching a dump of my config (that is pretty much standard). I believe the default gyro for INAV is MPU6000.

INAV_cli_20200229_130143.txt

[aknack]

works on the bench:

https://youtu.be/0KSczXa5M3A

[aknack]

works.

https://www.youtube.com/watch?v=u5nG86WBjk4

[aknack]

even better :D

https://www.youtube.com/watch?v=CNavxiyPzrM

[joebloe0]

could you please port the config (diff all)
i have the flight controller working but when i try to drive the motors there is a big dead zone about 15% of the throttle doesn't work.

if anyone knows how to set the minimum throttle value please tell me.

[aknack]

only on the bench that 15% . you won't notice if you arm and fly.
anyway, here's the diff.

INAV.JHEF7DUAL 2.4.0.diff.all.txt

please note: props direction is reversed!
set yaw_motor_direction = -1

[joebloe0]

thank you.
the config the you attached works better than mine.
only 5% is a deadzone not 15%
i think that is an acceptable range thank you so much for your help.

[aknack]

i got managed to fiddle the filters/advanced settings until quad wasnt able to fly (escs/motors did shut down like 300ms after thrusting, did not change BL_S firmware):
fucked up.txt
after reverting to
INAV.JHEF7DUAL 2.4.0.diff.all.txt

all was fine again. flys like a dream.

[soninua]

Hello! Please, help. In the PID TUNING tab, the gyro rpm filters menu is not active. I installed this firmware with these controls on the omnibus f4 pro board, everything is fine, this menu is active. Can someone explain this. Thanks.https://drive.google.com/open?id=16DU3ja_0KjXPSg9LjCAOwzo97oiGmigo

[soninua]

even better :D

https://www.youtube.com/watch?v=CNavxiyPzrM

Hello! Please, help. In the PID TUNING tab, the gyro rpm filters menu is not active. I installed this firmware with these controls on the omnibus f4 pro board, everything is fine, this menu is active. Can someone explain this. Thanks.https://drive.google.com/open?id=16DU3ja_0KjXPSg9LjCAOwzo97oiGmigo

[soninua]

smaller09 , you''re the man ! :)

i can confirm user-modes are working. can't confirm yet, that it will fly.
inav_2.4.0_JHEF7DUAL_smaller09_menu_patch.zip
Hello! Please, help. I have motor controllers with feedback. On the omnibus f4 controller, a gyroscopic rpm filter worked. In this firmware, activation of this filter is not available. What can you do about this?
In the PID TUNING tab, the gyro rpm filters menu is not active. I installed this firmware with these controls on the omnibus f4 pro board, everything is fine, this menu is active. Can someone explain this. Thanks.https://drive.google.com/open?id=16DU3ja_0KjXPSg9LjCAOwzo97oiGmigo

define USE_SERIALSHOT

is this parameter active?

betaflight target JHEF7DUA

define USE_ESCSERIAL

I completely assembled the copter, ready to test.

[Dropsleutel]

Hi guys what is the procedure on this Flight controller ? I have the full baro version, how to get it flashed properly with Inav? Does it work?

[xD90o1]

As of now, since I've only tested it om my plane, it works. I dunno yet on
multirotors though but I'm getting mixed results form other people

On Sat, Apr 18, 2020, 20:39 Dropsleutel [e-mail] wrote:

Hi guys what is the procedure on this Flight controller ? I have the full
baro version, how to get it flashed properly with Inav? Does it work?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/iNavFlight/inav/issues/5002#issuecomment-615861424,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHZRTEL5CJSLYFIWSKNEFA3RNGNO5ANCNFSM4IK2E5NA
.

[Dropsleutel]

Can you post the target here, so I'll flash it, can do some testing.

[xD90o1]

Check the linked pull request in this issue

On Sat, Apr 18, 2020, 20:47 Dropsleutel [e-mail] wrote:

Can you post the target here, so I'll flash it, can do some testing.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/iNavFlight/inav/issues/5002#issuecomment-615863164,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHZRTEOTIK4N3XD4YMFN37DRNGOODANCNFSM4IK2E5NA
.

[soninua]

Hello! I put one of the options on my quadrocopter, it did not behave correctly, it flew away, I could not return it. RPM filtering did not work, the sound of the motors was interrupted, the copter was gaining altitude and did not respond to control. I had to make a disarmament and the copter fell from a height of 100 meters. Fortunately, everything remained intact. After that, I changed the controller to the Matec f7se and everything was fine. With default settings, Matek works well. Very sorry. Why the RPM filtering item is not active in the firmware. Maybe publish again that firmware that can work? thanks

[xD90o1]

I haven't done some experimentation on the RPM Filtering yet since I only used this on a wing and I can't test some of the stuff you were suggesting yet either since the lockdown here prevents me from going out

[xD90o1]

Hello! I put one of the options on my quadrocopter, it did not behave correctly, it flew away, I could not return it. RPM filtering did not work, the sound of the motors was interrupted, the copter was gaining altitude and did not respond to control. I had to make a disarmament and the copter fell from a height of 100 meters. Fortunately, everything remained intact. After that, I changed the controller to the Matec f7se and everything was fine. With default settings, Matek works well. Very sorry. Why the RPM filtering item is not active in the firmware. Maybe publish again that firmware that can work? thanks

Have you got a blackbox log of that particular flight? I or someone might have a look at it to see why it happened

[Narnasqueneth]

Hi all,
Still no sign of support for this in Inav 2.5 RC2. Is this something that is actively being looked at as it is one of the cheapest f7 boards out there- likely people will have noticed and want to buy if Inav supports. I'm fine using betaflight on it for now but would be nice....

[digitalentity]

Closing this, as there seem to be little interesting from the manufacturer to follow the INAV hardware policy.

[cgaxtreme10]

Does anyone have contact with the manufacturer to reach a hardware support agreement with INav?

[xD90o1]

I think JHE swung by this thread a few posts earlier

On Mon, May 25, 2020, 02:19 cgaxtreme10 [e-mail] wrote:

Does anyone have contact with the manufacturer to reach a hardware support
agreement with INav?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/iNavFlight/inav/issues/5002#issuecomment-633271151,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHZRTEPKJ4KEKZWNWLAUQR3RTFQK7ANCNFSM4IK2E5NA
.

[cgaxtreme10]

Dear @atgfpeyv
This card has great potential for its construction and low cost of sale. It is a pity that due to lack of cooperation you cannot get the most out of it with INav. In the last year I have followed this product closely, including the latest version of the JHEMCU F7 BT Dual, however, the lack of support for it ends up making it unattractive.
Best regards

[yo8aiv]

Hi guys. i see there has been quite some activity here. Great.
Wich is the latest tested or not FW i could try on this FC .. i have deluxe version.
Thanks. Great job.

[xD90o1]

Check my fork. Hopefully the target source code would work on the latest
version of iNav

On Sun, Aug 9, 2020, 08:15 yo8aiv [e-mail] wrote:

Hi guys. i see there has been quite some activity here. Great.
Wich is the latest tested or not FW i could try on this FC . Thanks. Great
job.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/iNavFlight/inav/issues/5002#issuecomment-670987640,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHZRTELYBAR5NL24E4DSTX3R7XTCHANCNFSM4IK2E5NA
.

[yo8aiv]

Check my fork. Hopefully the target source code would work on the latest version of iNav
…
On Sun, Aug 9, 2020, 08:15 yo8aiv @.*> wrote: Hi guys. i see there has been quite some activity here. Great. Wich is the latest tested or not FW i could try on this FC . Thanks. Great job. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#5002 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHZRTELYBAR5NL24E4DSTX3R7XTCHANCNFSM4IK2E5NA .

link ?! thx.

[Narnasqueneth]

yeah, sorry, noob here- where can we get the target for manual flashing or is this now part of official INAV targets? Would love a link if poss...

[xD90o1]

link ?! thx.

http://github.com/xD90o1/iNav
Also I had a pull request made a few months ago
http://github.com/iNavflight/iNav/pull/5502

[yo8aiv]

can you guys please post a hex file that was tested to be working !! thx

[xD90o1]

can you guys please post a hex file that was tested to be working !! thx

JHEF7DUAL.zip

Here's my try at the code for the JHE F7 Dual

2.2.1 but I've been hearing success from some people trying to make it work on 2.4

[yo8aiv]

that's good news. thanks for sharing.
will report back.

[redeyejoe]

can you guys please post a hex file that was tested to be working !! thx

JHEF7DUAL.zip
Here's my try at the code for the JHE F7 Dual

2.2.1 but I've been hearing success from some people trying to make it work on 2.4

What all have you got working on this or what is not working, just the user modes?
thanks

[lavachemist]

I'm also interested in this. I just ordered this FC and I'm very interested in using iNav with it.

[xD90o1]

What all have you got working on this or what is not working, just the user modes?

I've seen someone here modify it a bit to make the user mode work

[ivanplkolev]

I tried both hex files for 2.2.1 and 2.5.2
For the both user switch 2 does not work - can not provide 8V to VTX - any fixes for that ?
(in betaflight t works, here the vtx might be soldered directly to the battery)

[xD90o1]

I assume it's the wrong menu id for the piniobox

On Mon, Oct 12, 2020, 19:20 Ivan Kolev [e-mail] wrote:

I tried both hex files for 2.2.1 and 2.5.2
For the both user switch 2 does not work - can not provide 8V to VTX - any
fixes for that ?
(in betaflight t works, here the vtx might be soldered directly to the
battery)

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/iNavFlight/inav/issues/5002#issuecomment-707058455,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHZRTEMRPWB5NOWJVB47UKDSKLQ7NANCNFSM4IK2E5NA
.

[redeyejoe]

In JHEMCU F7 is no user switch.
There is pin PC14, which switches cameras and pin PB9, which turns on/off the 8 V power supply for cameras.
Pins PC14, PB9 are assigned to CAMERA CONTROL 2 and CAMERA CONTROL 3.
Try using modes CAMERA CONTROL 2 and CAMERA CONTROL 3.

On betaflight the camera 8v is controled by user 1 and camera change is controled by user 2. They dont use the camera 2 and 3 tabs.

[terminat25]

inav_2.5.2_JHEF7DUAL (USER1,2).zip

[redeyejoe]

I tried the user1,2 firmware and it seems to be working in configurator, but when I arm and try to test fly it, my right stick (pitch,roll)on my transmitter acts like it is not connected to flight controller, I can move it all around when armed and props spinning and I get no response. throttle seems to be working but not yaw as far as I can tell. The motors spin up correctly in inav configurator motors tab, and my transmitter is working fine in the receiver tab. Must be something else not matching up?

[lavachemist]

inav_2.5.2_JHEF7DUAL (USER1,2).zip

So far this seems to be working. Only thing that seems slightly off is that data is set for UART1. I believe this was supposed to be for Bluetooth, which is on UART 4. Easy enough to change, but worth noting.

[lavachemist]

inav_2.5.2_JHEF7DUAL (USER1,2).zip

@terminat25 can you share the uncompiled target files? I'd like to be able to remap some stuff, which we can't do via hex file.

[UnchartedBull]

Feel free to checkout this branch of my fork: https://github.com/UnchartedBull/inav/tree/jhemcu-f722. Builds just fine and the I/O pins are working for me as well.

Edit: I disabled the MPU6000 Gyro, since my board (the one with the PDB) doesn't have one. You're probably best of forking it again to your repo and then adjusting everything :)

[terminat25]

For INAV 2.5.2 only.

target.h file:

define TARGET_BOARD_IDENTIFIER "JH7D"

define USBD_PRODUCT_STRING "JHEF722DUAL"

/ Indicators /

define LED0 PA15

define BEEPER PC15

define BEEPER_INVERTED

/ IMU sensors /

define USE_EXTI

define USE_TARGET_IMU_HARDWARE_DESCRIPTORS

define USE_MPU_DATA_READY_SIGNAL

define USE_DUAL_GYRO

define USE_IMU_MPU6000

define MPU6000_SPI_BUS BUS_SPI1

define MPU6000_CS_PIN PA4

define MPU6000_EXTI_PIN PC3

define MPU6000_ALIGN CW90_DEG

define USE_IMU_ICM20689

define ICM20689_SPI_BUS BUS_SPI1

define ICM20689_CS_PIN PB2

define ICM20689_EXTI_PIN PC4

define ICM20689_ALIGN CW90_DEG

/ SPI bus /

define USE_SPI

define USE_SPI_DEVICE_1 // Gyro 1/2

define SPI1_SCK_PIN PA5

define SPI1_MISO_PIN PA6

define SPI1_MOSI_PIN PA7

define USE_SPI_DEVICE_2 // OSD (MAX7456)

define SPI2_SCK_PIN PB13

define SPI2_MISO_PIN PB14

define SPI2_MOSI_PIN PB15

define USE_SPI_DEVICE_3 // FLASH

define SPI3_SCK_PIN PC10

define SPI3_MISO_PIN PC11

define SPI3_MOSI_PIN PB5

/ I2C bus /

define USE_I2C

define USE_I2C_DEVICE_1 // I2C pads

define I2C1_SCL PB6

define I2C1_SDA PB7

/ OSD /

define USE_OSD

define USE_MAX7456

define MAX7456_CS_PIN PB12

define MAX7456_SPI_BUS BUS_SPI2

/ Onboard flash /

define USE_FLASHFS

define USE_FLASH_M25P16

define M25P16_CS_PIN PC13

define M25P16_SPI_BUS BUS_SPI3

/ Serial ports /

define USE_VCP

define USE_UART1

define UART1_TX_PIN PA9

define UART1_RX_PIN PB10

define USE_UART2

define UART2_TX_PIN PA2

define UART2_RX_PIN PA3

define USE_UART3

define UART3_TX_PIN PB10

define UART3_RX_PIN PB11

define USE_UART4

define UART4_TX_PIN PA0

define UART4_RX_PIN PA1

define USE_UART5

define UART5_TX_PIN PC12

define UART5_RX_PIN PD2

define USE_UART6

define UART6_TX_PIN PC6

define UART6_RX_PIN PC7

define SERIAL_PORT_COUNT 7

/ BARO & MAG /

define USE_BARO

define BARO_I2C_BUS BUS_I2C1

define USE_BARO_BMP280

define USE_MAG

define MAG_I2C_BUS BUS_I2C1

define USE_MAG_HMC5883

define USE_MAG_QMC5883

/ ADC /

define USE_ADC

define ADC_CHANNEL_1_PIN PC2

define ADC_CHANNEL_2_PIN PC1

define ADC_CHANNEL_3_PIN PC0

define VBAT_ADC_CHANNEL ADC_CHN_1

define CURRENT_METER_ADC_CHANNEL ADC_CHN_2

define RSSI_ADC_CHANNEL ADC_CHN_3

/ PINIO /

define USE_PINIO

define USE_PINIOBOX

define PINIO1_PIN PC14

define PINIO2_PIN PB9

/ LED STRIP /

define USE_LED_STRIP

define WS2811_PIN PA8

/ Default settings /

define ENABLE_BLACKBOX_LOGGING_ON_SPIFLASH_BY_DEFAULT

define CURRENT_METER_SCALE_DEFAULT 170

define SERIALRX_UART SERIAL_PORT_USART2

define DEFAULT_RX_TYPE RX_TYPE_SERIAL

define SERIALRX_PROVIDER SERIALRX_SBUS

define DEFAULT_FEATURES (FEATURE_TELEMETRY | FEATURE_OSD | FEATURE_VBAT | FEATURE_CURRENT_METER | FEATURE_BLACKBOX)

/ Timer/PWM output /

define USE_SERIAL_4WAY_BLHELI_INTERFACE

define MAX_PWM_OUTPUT_PORTS 6

define USE_DSHOT

define USE_ESC_SENSOR

/ Used pins /

define TARGET_IO_PORTA 0xffff

define TARGET_IO_PORTB 0xffff

define TARGET_IO_PORTC 0xffff

define TARGET_IO_PORTD (BIT(2)) // ???

[terminat25]

For INAV 2.5.2 only.

target.c file:

include

include

include

include "drivers/io.h"

include "drivers/bus.h"

include "drivers/timer.h"

include "drivers/sensor.h"

include "drivers/pwm_mapping.h"

include "io/piniobox.h"

// IMU 1/2
BUSDEV_REGISTER_SPI_TAG(busdev_mpu6000, DEVHW_MPU6000, MPU6000_SPI_BUS, MPU6000_CS_PIN, MPU6000_EXTI_PIN, 0, DEVFLAGS_NONE, MPU6000_ALIGN);
BUSDEV_REGISTER_SPI_TAG(busdev_icm20689, DEVHW_ICM20689, ICM20689_SPI_BUS, ICM20689_CS_PIN, ICM20689_EXTI_PIN, 1, DEVFLAGS_NONE, ICM20689_ALIGN);

const timerHardware_t timerHardware[] = {
DEF_TIM(TIM9, CH2, PA3, TIM_USE_PPM, 0, 0), // PPM&SBUS

DEF_TIM(TIM3,  CH3, PB0,  TIM_USE_MC_MOTOR, 0, 0),      // S1 - D(1,2)          
DEF_TIM(TIM3,  CH4, PB1,  TIM_USE_MC_MOTOR, 0, 0),      // S2 - D(1,4)          
DEF_TIM(TIM3,  CH1, PB4,  TIM_USE_MC_MOTOR, 0, 0),      // S3 - D(1,6)          
DEF_TIM(TIM2,  CH2, PB3,  TIM_USE_MC_MOTOR, 0, 0),      // S4 - D(1,5)          
DEF_TIM(TIM8,  CH4, PC9,  TIM_USE_MC_MOTOR, 0, 0),      // S5 - D(2,4)          
DEF_TIM(TIM8,  CH3, PC8,  TIM_USE_MC_MOTOR, 0, 0),      // S6 - D(2,1)          

DEF_TIM(TIM1,  CH1, PA8,  TIM_USE_LED,      0, 0),     // LED STRIP(1,5)

// DEF_TIM(TIM4, CH3, PB8, TIM_USE_ANY, 0, 0), // ???
};

const int timerHardwareCount = sizeof(timerHardware) / sizeof(timerHardware[0]);

void targetConfiguration(void)
{
pinioBoxConfigMutable()->permanentId[0] = 39; // CAMERA CONTROL 1
pinioBoxConfigMutable()->permanentId[1] = 40; // CAMERA CONTROL 2
}

[terminat25]

For INAV 2.5.2 only.

JHEF7DUAL.zip

[lavachemist]

Attached is my version of the JHEMCU F7 DUAL target (hex file and also target files in the zip file).

This will allow you to run INAV on the JHEMCU F7 DUAL in 2.5.2 as both a multicopter (up to hexacopter or quadcopter with two servos) and wing (up to 4 servos and two motors) without running into issues with incorrect timer settings.

All I did was rearrange the variables for S1 - S6. Now, if you are building a single motor flying wing, for example, it will map the motor to S4, and map the two servos to S1 and S2. The other versions above do not have FW motors and servos mapped, so it would have tried to put the servos and motors on S1-S3, which did not work since those outputs are all on the same timer.

JHEF7DUAL_LC.zip