Quite sure he did 
Although I didn’t use Mission Planner. But both Qgroundcontrol and APM shows I am reading constant value
Yes ,I just cloned master , waf configure with erlebrain2 and waf copter
@LanderU thanks for the update
@JD-ETH I think I might have the answer why Px4Flow does not work with GCS
1 Like
Aha that must be it! … I didn’t clearly understand what was decided in the dev call though — Should I attempt to flash back a older version of firmware?
@JD-ETH
The Px4Flow code http://ardupilot.org/copter/docs/common-px4flow-overview.html#upgrade-the-px4flow-sensor-s-firmware4 is the only version that is compatible with APM. What @rmackay9 will do is to pull Paul’s branch into the ardupilot github area and then change the reported id from the flow sensor so the GCSs are happier.
So, until this is done and tested, the only method that works for testing and configuring the Px4Flow is using Mission Planner.
2 Likes
As long as I can use it in APM I’m happy! I will downgrade the firmware then.
If I understood correctly, the only way to fuse the px4flow data into ardupilot is using that specific firmware version? Or it is just not shown on the apm planner?
I will be happy to see the new firmware working too in the future. Great, thanks!
The specific PX4Flow firmware is for ArduPilot and I still recommend that you use Mission Planner to test , set and calibrate.
1 Like
Using the officially recommanded documentation doesn’t change anything. I am still observing spikes at the optical flow output. It seems to be generated by the erroneous body rates.
I suspect there is incompatibility between rapsberry pi 3 and the ardupilot or Erle Firmware. Has there been use cases with rapsberry pi 3 and Px4Flow? Attached is the bin file.
4 13-06-2017 19-20-04.bin (2.0 MB)
Just test with px4flow (remove lidar lite for the moment)
We tried and we were getting same results. However, we are getting some interesting results with the current beta :3.5rc7. still far from being correct but at least no spikes anymore http://forum.erlerobotics.com/t/arducopter-3-5-beta-testing/2936/10
1 Like
With the ardupilot beta (3.5.0 RC 7) we were able to read the log.
Yes it still requires calibration and set yaw, but good thing it is reading legitimate value!
2 Likes
Great !!
Keep us updated with the flight test.
One more little tweek , you can adjust the optical flow delay to get a very accurate correlation between the PX4FLOW and the FC IMU; I have good results by adding 20 Millisecs.
Thanks for the suggestion, we will test it when we fly.
After setting to the correct direction and having similar amplitude at the gyro measurement, We are finally reading data from the log.(On APM Planner it has very low stream rate somehow and one can’t really see what’s going on)
However, the EKF 2 kept switching between optical flow, even though I don’t seem to be using it.
Log here:
Parameter attached tooFatMan_15_06.param (10.5 KB)
Looking at your parameter file, there are a lot of stuff missing, are you using mission planner for setting params ?
Please save parmater file from Mission Planner and submit again.
Ok I will switch to Mission Planner. It has became super slow somehow in parameter transfer, and it takes 10 minutes to finish getting parameters…
This really not normal, you connect UDP using the appropriate port ?
If you go in command shell : and Ping the ErleBrain, = you should get a steady Ping back around few millisecs
Other test, launch manually using Ethernet
Finally finished downloading those.
ParamList0615.param (12.8 KB)
I will check the ping now:
Ping seems fine, time < 1ms for all package sent.
Ahhhh Much better 
Ok now according to instruction,
Set the EK2_GPS_TYPE parameter to 3 to make the EKF ignore GPS and use the flow sensor
http://ardupilot.org/copter/docs/parameters.html#ek2-gps-type-gps-mode-control
And this RNGFND_TYPE,-1 should be set to 15
2 Likes
The error message disappeared!
However, the update rate of the flow measurement is still extremly low, updates every 2 seconds. On the logs they seem to be update way faster.
I think there is something weird going on between the board and the GCS.
My LidarLitev3 shows a constant offset, however changing offset (V) doesn’t seem to affect anything(not analog). Is there a way to offset the measured value?
So here I can confirm PX4flow would theoretically work on Erle brain 3 in ardupilot 3.5.0 rc7. However, the ardupilot would occasionally crash for no reason, and this is stopping me from taking it out for a test fly.
Hopefully we could resolve this soon.