Baro:
dang I thought that was just an orientation mark…cool thanks.
Hey Andy how does one go about getting that hardware thingy updated for this other baro. I am not in any real hurry just curious.
Someone has to write a new hwdef
I thought as much.
I guess I won’t worry about it. There are other AIO’s out there.
Not sure what to do with this one but I will find a place for it.
Thanks for your help.
Writing one to support the different IMU is pretty trivial. What takes the time is working out the other pinout changes (if any). Ideally I need to know if this is a v1 pinout or a v2 pinout. If you feel like pouring over the manuals for the 3 different versions that would probably help.
Hey Andy glad to help.
If your talking about the pin out of the board itself this is what I can tell you.
These are the main differences tech wise.
V1.2-V2: Updated some circuit improvements implemented.
V2-V2.2: Gyro updated to BMI270.
However pinout.
On the V2 and V2.2 board there are different pinouts between the V2-V2.2 and the v1.0 - V1.2 versions
On the V2-V2.2 the bottom corner has this pinout
Where as the V1 - V1.2 has this
Also the Buzzer location changes
on the V1.0 - V1.2 versions it’s here
On the V2 and V2.2 versions its on the corner
I have found no other differences.
The other thing I notice is there is no I2C so GPS and external compass…ah not so much.
This is everything I have learned so far
So it looks like it’s the same as the v2.2, except it has a different IMU and still has a baro. On the v2.2 USART3 can also be used as I2C
Cool
Um how do you tell it that the UART should be I2C. Is there a config setting of some sort.
If so then I won’t go shopping for another AIO. I will just wait and fingers crossed that HWDEF gets updated sooner then later.
Lol
Well in theory you set BRD_ALT_CONFIG=1
Try this - see if it gets you any further
arducopter_with_bl.zip (1013.6 KB)
This give me a config error fix problem then reboot. Then it mentions that it is unable to initialize the baro.
I did set BRD_ALT_CONFIG=1 and rebooted it but no joy.
Basically the same experience.
has there been any progress with this board.
If not…not the end of the world. just curious.
Can you send me pictures of your board?
This I had posted earlier.
The baro on your board is not a BMI270 as far as I can tell. Looks like a DPS310 - maybe you can see the lettering?
Try this. You should be able to unzip and load with mission planner if you have the BeastF7v2 bootloader loaded
arducopter.apj.zip (589.9 KB)
I think this is the same firmware you gave me earlier in the posts. I just tried it but no joy.
Same issue Config error. Something about the baro and driver.
I also noticed this comment in the product description.
