Conversation
| DEF_TIM(TIM9, CH2, PA3, TIM_USE_MC_MOTOR | TIM_USE_FW_SERVO, 1), // S3_OUT | ||
| DEF_TIM(TIM3, CH2, PB5, TIM_USE_MC_MOTOR | TIM_USE_FW_SERVO, 1), // S4_OUT | ||
|
|
||
| DEF_TIM(TIM4, CH1, PB6, TIM_USE_LED, 0), // LED strip |
There was a problem hiding this comment.
Is PB6 also the pin for I2C1_SCL? If so does this matter?
There was a problem hiding this comment.
To be clear, this enhancement request is for the following board, yes?
https://store.myairbot.com/flight-controller/omnibus-f3-f4/omnibusf4v6.html
Has anyone tested this for sbus? I used the fireworks target per instructions from airbot, my receiver and taranis setup are known good, board is calibrated, all icons green yet no activity in receiver tab of configurator when moving throttle, etc. I connected the Frsky X5R sbus output pin to the pad shown on the board as "sbus". I selected Uart6 as the rx input. This receiver works on a old INAV version with Naze32. I am happy to help with SBUS and GPS specific testing (Beitan 880 GPS with I2C compass). GPS disconnected while trying to get sbus working. Documentation specific to this board would be nice also. I can help with that as well if needed. I also have a 200Mhz Oscilloscope and multimeter so can probe if asked.
There was a problem hiding this comment.
Hi. This target, with the following PR, works with sbus. Fireworks will not work. I added the hex file a few months ago here, if you want to test it:
https://www.dronetrest.com/t/i2c-magnetometer-not-working-on-omnibus-f4-v6/7005/11?u=fat
I have not had time to combine the targets.
There was a problem hiding this comment.
Uart 6 is Sbus, correct?
I must have a hardware issue, I flashed this in and still seen no response in the inav configurator to my arm switch or anything else.
There was a problem hiding this comment.
Actually we might not be talking about the same board. The board I have is from Airbot and is called OMNIBUS AIO F4 V6, Not OmnibusF4V6. Its not the "Pro" board either. Since your target name does not include the string "AIO" and the resource table on dronetest that your link points to shows Uart 1 as being used for Sbus (PA10) whereas the Airbot resource table on the sheet they included with my board shows Sbus as Uart6 PC7, I think we're talking different boards.
There was a problem hiding this comment.
Hi, this is the same board. The AIO just means that the BEC is added (And I am not aware that there is another board). Please just look at my own comment at the link above, not the others, not from Unmannedtech either, as it contains incorrect mapping.. The mapping (even the mapping from airbot) is not correct! (I had to find them myself, and these are the correct ones: gps on uart3, mag i2c1, sbus uart6, sport tx1).
Regarding testing of sbus, go to the radio pane to check response from your transmitter, after you see your channels, then the modes. Let me know how it goes, regards
There was a problem hiding this comment.
atobiese,
wow what a mystery! still not working. I flashed in your patch.
https://www.dronetrest.com/t/i2c-magnetometer-not-working-on-omnibus-f4-v6/7005/11?u=fat
For your patch, must serialrx_inverted = OFF or serialrx_inverted = ON? I have tried both.
I connected an oscilloscope to the SBUS pad on the flight controller. I can see the pulse groups and when I move the throttle on taranis, I see changes in the pulses that correspond to the physical stick movement. That verifies everything up to the FC input. Uart6 Serial RX is on in the ports tab of iNav and everything else is disabled right now.
FC powers up in setup screen with all green icons (hardware health, navigation is safe, etc.).
One odd thing. The battery is 3S yet in the Setup info the Battery detected cell count is only 1. Battery is connected directly to the FC battery inputs and I'm using the internal FC BEC just fine. I've tested with battery as the power source for the receiver and with battery off and receiver being powered from FC USB 5V pin. That all works fine.
Still no activity in the Receiver tab or flight modes tab (all modes are disabled right now). I'm starting to think the FC board might be bad. Can't return it because I've soldered to it.
If you think of anything else, please let me know.
I remembered the cli status command and when I ran it, everything looks perfect except that
the battery is not "seen" even though its powering the FC and iNav does not detect the receive signal per error code RX = The RC link is not detected (RX not detected)
System Uptime: 138 seconds
Current Time: 2041-06-28T01:04:00.000+00:00
Voltage: 0.0V (1S battery - CRITICAL)
CPU Clock=168MHz, GYRO=MPU6000, ACC=MPU6000, BARO=BMP280
STM32 system clocks:
SYSCLK = 168 MHz
HCLK = 168 MHz
PCLK1 = 42 MHz
PCLK2 = 84 MHz
Sensor status: GYRO=OK, ACC=OK, MAG=NONE, BARO=OK, RANGEFINDER=NONE, OPFLOW=NONE, GPS=NONE
Stack size: 6144, Stack address: 0x10010000, Heap available: 968
I2C Errors: 0, config size: 4105, max available config: 131072
ADC channel usage:
BATTERY : configured = ADC 2, used = ADC 2
RSSI : configured = ADC 3, used = none
CURRENT : configured = ADC 1, used = none
AIRSPEED : configured = none, used = none
System load: 0, cycle time: 2001, PID rate: 499, RX rate: 49, System rate: 9
Arming disabled flags: RX CLI
| #define SENSORS_SET (SENSOR_ACC | SENSOR_BARO) | ||
|
|
||
| #define USE_LED_STRIP | ||
| #define WS2811_PIN PB6 |
There was a problem hiding this comment.
I think PB6 is used for i2c when USE_I2C_DEVICE_1 is defined. Does this matter?
There was a problem hiding this comment.
PB8 and PB9 are used for i2c1 for this board.
There was a problem hiding this comment.
OK great. I missed that STM32F4 is defined. This might help me with #4025
There was a problem hiding this comment.
Hi Alex, I'll have a look at your issue. Did you verify (with a multimeter) which pins the jst points to? note that ff its pb6/7, then uart 1 must be disabled. snakkes, Andrew
|
OMNIBUSF4 V6 is FIREWORKSV2 target |
|
Current Fireworksv2 wil not work with the omnibusf4v6 due to the different i2c pin def, ie, magnetometer will not work (as described above). UART3 is also free (not shared with i2c). Other than that its the same, and could be combined with the FW target. |
|
If the board is similar to FIREWORKSV2 then it's better to create a variant of FIREWORKSV2 rather than a completely new target |
|
Ok. I'm away for the next two weeks, but will have time when back. This board also enables two servos via rail (I have not added them yet to the target). |
|
how i can star to help on code |
|
How to install this fw? |
|
The board is very similar to FIREWORKSV2. Please change this to a variant of FIREWORKSV2 for easier maintenance. |
digitalentity
left a comment
digitalentity
left a comment
There was a problem hiding this comment.
Make this a variant of FIREWORKSV2 target
|
Just want to annote that some people really wait for the OMNIBUS F4 V6 support (incl. I2C) to come. I cannot support coding, but maybe I can help to test or measure. Scope and copter are available, so please feel free to ask for any test. |
|
Thanks Asizon. |
8 participants
This board is similar to the fireworks v2, but with changed i2c bus location (1 instead of 2). This enables uart3 for gps and magnetometer will work (and thus full features of INAV 2.0). Since sbus runs on uart6, the 6 pin JST cannot be used for gps if the sbus pin is used (RX,TX is wired to UART6, PC6 and PC7).
I have tested this board on own quad with INAV 2.0. This new board seems popular and some people at dronetrest.com have tested it there. I have noted that the omnibus boards are combined in INAV. I like separate folders but combining with fireworks v2 will save some code.