Optical Flow for APM 2.5 - Oh Where Did You Go?

I've been reading various posts on the Google Code wiki site for Arduino and noted many folk's discussion for the last couple of years the Optical Flow sensor and updates to the firmware code.  Everything discussion wise stop in May of this year.

Is the Optical Flow from 3D Robotics discontinued for the APM units?  If so will the PX4Flow work with only the PX4 boards or can it be used on APM's.  Seems to be a bit unclear to me where 3D is going with respect to the APM's.

I'm looking to install this type of sensor and need support in the best way to tackle this.

 

Thanks,

Doug W.

 

You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –

Replies

  • Developer

    I think the PX4Flow will make a come back for the px4 anyway and, as Charles says, it'll be mainly useful for indoors or for those rare situations where you lose GPS lock.

    I'd expect us to get it working for the px4 flow in a few months (6 months max) including incorporating the velocities into the inertial navigation which is currently just accelerometers + gps.  I imagine we will try and get the old optical flow sensor also working in this way for the APM2.  I don't expect that anyone but jDrones will be providing the sensors though.

    The real problem with the old optical flow sensor was that it's output was never integrated into the position estimate because we hadn't developed the inertial nav complementary filter.

  • What are your expectations in using the optical flow sensor?

    I was looking into this before also, and did'nt find much info on it, except the original description in the manual page

    I also noticed recently that more & more multirotors showing better acuracy in position hold and loiter seem to not include sonar or optical flow sensors

    From what I undestand, unless you are using the multirotor indoors or a non gps aquirable area they have no real function that works well, unless the craft in a low altitude state

This reply was deleted.