Closed yo8aiv closed 4 years ago
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.
Hello @atgfpeyv could you kindly provide this FC to inav developers?
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
@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.
Thank you Tim, great advise!
El jue., 29 de ago. de 2019 22:46, Tim Eckel notifications@github.com 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 .
`dump
batch start
board_name JHEF7DUAL manufacturer_id
name -
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 A03 AF3
timer B00 AF2
timer B01 AF2
timer B04 AF2
timer B03 AF1
timer C09 AF3
timer C08 AF3
timer A08 AF1
timer B08 AF2
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
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
dma pin B01 0
dma pin B04 0
dma pin B03 0
dma pin C09 0
dma pin C08 0
dma pin A08 0
dma pin B08 0
`
Forgive me for being late, so what should I do for inav to support this board?
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?
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
would u mind sending me the hex file u already made?
On Fri, Nov 1, 2019 at 3:02 PM +0100, "Ace Ervite" notifications@github.com 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.
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.
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" notifications@github.com 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.
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...
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
hi inav team! great job so far!
is there any progress on this FC?
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.
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,
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 notifications@github.com 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 .
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?
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
Hello! Are there any changes with this board? Someone was able to do it with INAV?
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
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
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.
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
Here's my try at the code for the JHE F7 Dual
Я начал с исходного кода контроллера двойного полета, который присутствует здесь в 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.
Я начал с исходного кода контроллера двойного полета, который присутствует здесь в 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 еще не успел протестировать, пожалуйста доложите
Вот моя попытка в коде для 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?
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 notifications@github.com wrote:
Я начал с исходного кода контроллера двойного полета, который присутствует здесь в inav, а затем я просто иду вперед и изменяю pinouts соответственно, чтобы соответствовать тем, которые используются в Jhe F7 Dual. Это уже работает, но я просто не могу заставить пользовательские режимы работать ... <#m2167389971052229994> 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 .
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
I want to know if the user modes work out for you guys
On Thu, Feb 6, 2020, 16:37 aknack notifications@github.com 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 .
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.
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 notifications@github.com 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 .
a shame, since its a good F7+baro for a very good price.
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.
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
As long as there are no conflicts with the timers, it'll fly just fine
On Sat, Feb 8, 2020, 22:45 aknack notifications@github.com 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 .
all seems fine, but i'm unable to arm. still debugging. any ideas?
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
Pre-arming checks : all green cli status :
Arming disabled flags: CLI
gps shows 6 satellites : ready to fly T16 bound via fport : okstill 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.
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.
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.
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.
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.
[..] 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.
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?
Just to let you know I've forked this repo with the JHE F7 Dual target added so I can test more on this.
@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.
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
step 1: r9 mini on t2 via fport: works.
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.