Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove the OPFLOW_PMW3901 opflow hardware option #6678

Conversation

shellixyz
Copy link
Collaborator

The PMW3901 driver has never been implemented. Quote from @digitalentity: "It's using very weird SPI timings, won't be compatible with our scheduling"

@shellixyz shellixyz added this to the 2.7 milestone Mar 5, 2021
@shellixyz shellixyz changed the title Remove the OPFLOW_PMW3901 the opflow hardware option Remove the OPFLOW_PMW3901 opflow hardware option Mar 5, 2021
The PMW3901 driver has never been implemented. Quote from
@digitalentity: "It's using very weird SPI timings, won't be compatible
with our scheduling"
@shellixyz shellixyz force-pushed the fix/remove_PWM3901_opflow_hw_option branch from 00225a1 to 4c6f00c Compare March 5, 2021 16:39
@digitalentity digitalentity merged commit 251976f into iNavFlight:master Mar 8, 2021
@al3k87
Copy link

al3k87 commented Jun 2, 2021

is this the reason I cant get optiflow data from my Matek "OPTICAL FLOW & LIDAR SENSOR 3901-L0X"?
I only get the sonar values, if I look in the debug sensor graphs nothing is changing, I also use MSP protocol for both lidar and optiflow like it says in manual.
(I use INAV RC2 3.0 firmware with MACOS)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants