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

Pneumatic Arduino Code #234

Open
irwineffect opened this issue Apr 7, 2017 · 3 comments
Open

Pneumatic Arduino Code #234

irwineffect opened this issue Apr 7, 2017 · 3 comments
Milestone

Comments

@irwineffect
Copy link
Member

irwineffect commented Apr 7, 2017

Introduction

This is going to be an arduino-based node that actuates our pneumatics to fire torpedoes and drop markers. It should use the ROS services API. Need to talk to the mechanical engineers to ask them how to actuate the pneumatics to move the mechanisms.

Service Names

fire_torpedo/left - std_srvs/Trigger
fire_torpedo/right - std_srvs/Trigger
fire_torpedo_status - robosub/pneumatic_status
drop_marker/left - std_srvs/Trigger
drop_marker/right - std_srvs/Trigger
drop_marker_status - robosub/pneumatic_status

Parameters

Exact parameter naming is tbd, but they will be describing which of the pnematics perform which action. For example pn1 might be used to open the marker dropper, and pn5 might be used to reset the marker dropper mechanism.

@skallaher
Copy link
Member

Since there are two marker dropper mechanisms, shouldn't there be two services? One for left and one for right?

It also might be a good idea to have a way to determine the status of each so that the AI doesn't have to guess if it has already fired a torpedo. This could be a service call as well.

@irwineffect
Copy link
Member Author

Agreed, updated the description!

@bkallaher
Copy link
Member

see #236 for the addition of the tbd service.

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

No branches or pull requests

3 participants