There is something very strange going on when I'm checking Mavlink Massege Inspector. First of all when I connect PX4FLOW directly to dedicated QGC everything looks fine.
OPTICAL_FLOW.flow_x changes accordingly to the real situation:
So does OPTICAL_FLOW.flow_y
And OPTICAL_FLOW.quality
I expected to see similar values when I connected Autouad to QGC and opened Mavlink Massege Inspector. But OPTICAL_FLOW.flow_x is always, always 0. No matter what I do.
OPTICAL_FLOW.flow_y looks better but it has a tendency to not go back to 0 when quality drops down. After deeper inspection I discovered that flow_y reflects movements in x direction. So flow_y here is in fact flow_x when PX4FLOW is directly connected.
Quality is always 0 but sensor_id seems to change somehow similar to the true quality. Here is how sensor_id looks like:
This looks so strange I don't know what to think. Should I flash the PX4FLOW with this very old version of software which Bill Nesbitt posted a long time a go?
The last thing I checked was to flash the GPS led when flowSumX value was bigger then 10. That was supposed to show whether or not flow_x really is 0 as diagram shows. And diode blinked. This probably means that everything is ok and just Mavlink Massege Inspector shows incorrect values?