Strange local_position_ned and need for a "forced" reboot to work

[edwinpha]

Hi there,

I am having problems using my PX4FLOW.

First of all, when I use only the PX4FLOW (without Pixhawk), the local_position_ned that I can see is really accurate (even if using sonar). So, when I attach it to a pixhawk with a TFMINI, I was expecting a similar performance. But I see a much bigger drift in the local_position_ned (the one that you can see from pixhawk).

Then, I realized that there are some problems with the versions. For example, 1.11. needed for the specific "start px4flow" even if enabling sens_en_px4flow. Currently, I am using 1.10., but still there are some issues. For instance, when I reboot the Pixhawk (both from mavlink terminal or unplugging the wire) the PX4FLOW does not give any value in the integrated_*, it only gives temperature, distance, time_delta_... and time_usec. To make it give again some values, or at least for me to read them from pixhawk, I have to unplug and plug the i2c cable.

Not sure, if someone can guide me through these problems or tell me the last really stable version.

I have seen in the PX4-Autopilot repository some saying that it work with 1.9 or 1.10, because they were fixed issues, but for me they are still generating some problem. Maybe I am doing something wrong?