-
Notifications
You must be signed in to change notification settings - Fork 54
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
Alarms, Launch, Utils #30
Conversation
<launch> | ||
<!-- This is the default pointgrey launch file with our id's and our names --> | ||
|
||
<arg name="front_camera_serial" default="15223362" /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What are the serial parameters for? Do they identify each camera?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep
Good to merge? |
Merging... If you got beef, let me know and I will attempt to correct the issues |
* UTILS: Moved sub8 utils over to remove dependency * GAZEBO: Fix build issues * LAUNCH: Add launch for lidar and cameras * TOOLS: Fix wrong name * ALARMS: Make alarm kill work, fix controller startup * LAUNCH: Seperate TF into it's own launch file * SRVS: Add navigator srv directory * Fix PR issues.
Moved utils over from sub repo to remove the dependency there (I think Jake wrote most of those utils).
The alarms should work now - not sure if they were working before but from what I saw they shouldn't have been to the full extent. There is a
kill
alarm and adocking
alarm to replacefull_kill
andhalf_kill
alarms.kill
will shutdown C3 as well as zeroing motor commands.Cameras will need to be calibrated
Closes #6