Skip to content

Commit 6e4911c

Browse files
Initial commit
0 parents  commit 6e4911c

File tree

8 files changed

+40
-0
lines changed

8 files changed

+40
-0
lines changed

.gitattributes

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
# Auto detect text files and perform LF normalization
2+
* text=auto

PublishPi/desktop_subscribe.slx

38.3 KB
Binary file not shown.

PublishPi/rasberrypi_publish.slx

50.2 KB
Binary file not shown.
39.7 KB
Binary file not shown.
57.4 KB
Binary file not shown.

README.md

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
# Object Tracking using ROS and Simulink on Raspberry Pi
2+
3+
Copyright 2020 The MathWorks Inc.
4+
5+
## Introduction
6+
This repository contains resources for deploying a ROS node on Raspberry Pi hardware using Simulink showcasing an object tracking example.
7+
8+
## Folder Structure
9+
The repository has two examples which are located in two different folders:
10+
1. ***PublishPi***: Deploy a standalone ROS node with vision and control algorithms and validate it from another Simulink model for visualization.
11+
2. ***PublishSubscribePi***: Publish and Subscribe between a ROS node in Simulink and a standalone ROS node deployed onto Raspberry Pi.
12+
13+
The Raspberry Pi model has to be deployed on the hardware, whereas the Desktop model is to be run on the system.
14+
15+
## Setu
16+
1. Clone the repository.
17+
2. Open MATLAB and navigate to *PublishPi* or *PublishSubscribePi* folder.
18+
3. Open the Raspberry Pi model. Deploy the model on the hardware using Robot -> Build & Run. Installation of Raspberry Pi Support from Simulink would be necessary:
19+
https://www.mathworks.com/hardware-support/raspberry-pi-simulink.html
20+
4. Open the Desktop model and **run** the model.
21+
22+
For any queries, contact the authors at [email protected]

SECURITY.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
# Reporting Security Vulnerabilities
2+
3+
If you believe you have discovered a security vulnerability, please report it to
4+
[[email protected]](mailto:[email protected]). Please see
5+
[MathWorks Vulnerability Disclosure Policy for Security Researchers](https://www.mathworks.com/company/aboutus/policies_statements/vulnerability-disclosure-policy.html)
6+
for additional information.

license.txt

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
Copyright (c) 2019, The MathWorks, Inc.
2+
All rights reserved.
3+
4+
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
5+
6+
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
7+
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
8+
3. In all cases, the software is, and all modifications and derivatives of the software shall be, licensed to you solely for use in conjunction with MathWorks products and service offerings.
9+
10+
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

0 commit comments

Comments
 (0)