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.

Sign up for GitHub

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

Jump to bottom

LIBRARY: Implement DRV8837 Driver #296

Open
WattsUp opened this issue Apr 11, 2019 · 5 comments
Open

LIBRARY: Implement DRV8837 Driver #296

WattsUp opened this issue Apr 11, 2019 · 5 comments
Labels
Beginner A task capable of a beginner skill level Library Software Team-Attitude Tests Testing an implementation

Comments

@WattsUp
Copy link
Member

WattsUp commented Apr 11, 2019

No description provided.

@WattsUp WattsUp added ADCS Beginner A task capable of a beginner skill level Software Team-Attitude Tests Testing an implementation labels Apr 11, 2019
@WattsUp WattsUp changed the title AVIONICS: Test H-Bridge Driver LIBRARY: Implement DRV8837 Driver Sep 12, 2019
@WattsUp WattsUp added Library and removed ADCS labels Sep 12, 2019
@kevinhikaruevans
Copy link
Contributor

Do we have any DRV8837s on-hand and mounted a breakout? If so, where could somebody pick one up to borrow for testing?

@WattsUp
Copy link
Member Author

WattsUp commented Oct 2, 2019

There is a board for it in the electrical systems room. I can bring it tomorrow. Green LED is forward. Red LED is reverse. Red wire is 3.3V. Black is ground. Orange is nSleep. White is IN1. Grey is IN2.

@kevinhikaruevans
Copy link
Contributor

kevinhikaruevans commented Oct 6, 2019 •
edited
Loading

How do we want to handle non-blocking calls? As in, should I create a Timeout instance to cause an interrupt after some amount of time?

@kevinhikaruevans
Copy link
Contributor

@WattsUp nSleep is tied high on the board. Is that supposed to be constant high or is there a solder bridge somewhere? I expected it to be driven by the microcontroller.

@WattsUp
Copy link
Member Author

WattsUp commented Oct 7, 2019

Since you are just writing PWM outputs that are pretty short, there wouldn't be a difference between blocking and non-blocking. Setting up something to handle writing the outputs would probably take longer than actually setting them.

I thought I could toggle it. It is driven by the microcontroller

@kevinhikaruevans kevinhikaruevans mentioned this issue Oct 8, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Beginner A task capable of a beginner skill level Library Software Team-Attitude Tests Testing an implementation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kevinhikaruevans @WattsUp