Paired super beacon for PX4

[zby090316]

Hi,

I am using paired super beacon to provide heading information for px4 drones. I follow the user manual https://marvelmind.com/pics/marvelmind_ ... ration.pdf. However, the drone can only get GPS information. It cannot receive the heading information. If I disable compass 0 and enable compass 1, the heading of the drone will never change no matter how I rotate the drone. Then, I connect the paired beacons to a Raspberry Pi and try to read I2C protocol using the Pi. However, the result will always be 0x00. Does anyone have the similar experience?

Best regards

[admin]

My colleague may help with the details. However, before diving deep into this, always follow the step-by-step path:

Please, follow:
- Eight essential steps from unpacking to autonomous drive/flight
- https://youtu.be/JmVjpypEc04

So, the main point: do everything in small steps:
- Get the perfect track of one beacon
- Get the perfect track of another beacon
- Get the perfect track of two beacons together, not yet paired
- Track when they are paired and installed on the drone with the drone powered as well - to make sure the telemetry doesn't interfere, etc.
- Only after that is it time to integrate with PixHawk - not before

It will save you a lot of time.

[zby090316]

Thank you for your reply. I think I did not make the usual mistakes because I have integrated super beacons with both px4 and Arducopter drones. They all can receive localization information from the super beacon. However, the problem is that the px4 drone cannot receive heading information from the paired super beacon while the localization is fine. The heading information is shown on the dashboard. And when I use a raspberry pi to read beacon information through USB, it can get non-zero angle value. But if I connect raspberry pi to the super beacon using SCL and SDA pins, it always reads zero using the I2C protocol.

[smoker77]

Hello,

Thank you for the feedback.
We have found some software issue with compass emulation by the beacon.
The fix was included to the latest software update (v7.306).
Please try update the software:
https://marvelmind.com/pics/marvelmind_SW.zip