├── .readthedocs.yaml
├── LICENSE
├── README.md
├── axis_by_axis
├── CMakeLists.txt
├── package.xml
└── src
│ └── trajectory.cpp
├── docs
├── Install.md
├── application.md
├── architechture.md
├── examples.md
├── experiments.md
├── extra.css
├── extra.js
├── huro.html
├── images
│ ├── architecture.png
│ ├── circularGMAT.jpg
│ ├── circularOnOrbitROS.png
│ ├── circularResults.jpeg
│ ├── cranfield.png
│ ├── drag.png
│ ├── elipticOnOrbitROS.png
│ ├── ellipticGMAT.jpg
│ ├── ellipticResults.jpeg
│ ├── etsvii.jpg
│ ├── frames.png
│ ├── gravGrad.png
│ ├── hurospace.jpg
│ ├── linkedin.png
│ ├── logo.png
│ ├── logo_huro_fondo_blanco.png
│ ├── logo_huro_large.svg
│ ├── orbit_publisher.png
│ ├── ros_pub.png
│ └── ua.png
├── index.md
├── launch.md
├── requirements.txt
└── troubleshooting.md
├── docs_inOnorbitros_june.zip
├── ets_vii
├── CMakeLists.txt
├── config
│ ├── effort_controllers.yaml
│ ├── gazebo_controllers.yaml
│ └── ros_controllers.yaml
├── launch
│ ├── axis_by_axis.launch
│ ├── effort_controllers.launch
│ ├── effort_controllers_indivudual.launch
│ ├── effort_controllers_wgg.launch
│ ├── ets_vii.launch
│ ├── only_the_model.launch
│ └── trajectory.launch
├── log
│ └── note.txt
├── package.xml
├── rviz
│ └── config.rviz
├── urdf
│ ├── ets_vii.xacro
│ ├── ets_vii_gazebo.xacro
│ └── ets_vii_gazebo_wgg.xacro
└── worlds
│ ├── no_gravity.world
│ └── no_gravity_dart.world
├── logo.png
├── logo_w.png
├── mkdocs.yml
├── orbit_publisher_pkg
├── CMakeLists.txt
├── config
│ ├── dynamic_orbit.yaml
│ └── fixed_orbit.yaml
├── include
│ └── orbit_publisher_pkg
│ │ └── Orbit.h
├── launch
│ ├── basic.launch
│ └── basic_fix.launch
├── package.xml
└── src
│ ├── Orbit.cpp
│ ├── fix_orbit_publisher_pkg_node.cpp
│ └── orbit_publisher_pkg_node.cpp
├── orbit_robot_pkg
├── CMakeLists.txt
├── include
│ └── orbit_robot_pkg
│ │ └── OrbitLink.h
├── package.xml
└── src
│ ├── OrbitLink.cpp
│ └── Orbit_robot_pkg_plugin.cpp
├── package_template
├── CMakeLists.txt
├── launch
│ └── default.launch
├── package.xml
├── urdf
│ └── cubesat_template.xacro
└── worlds
│ ├── no_gravity.world
│ └── no_gravity.world.xacro
├── requirements.txt
└── site
├── 404.html
├── Install
└── index.html
├── arquitechture
└── index.html
├── assets
├── images
│ └── favicon.png
├── javascripts
│ ├── bundle.c8d2eff1.min.js
│ ├── bundle.c8d2eff1.min.js.map
│ ├── lunr
│ │ ├── min
│ │ │ ├── lunr.ar.min.js
│ │ │ ├── lunr.da.min.js
│ │ │ ├── lunr.de.min.js
│ │ │ ├── lunr.du.min.js
│ │ │ ├── lunr.el.min.js
│ │ │ ├── lunr.es.min.js
│ │ │ ├── lunr.fi.min.js
│ │ │ ├── lunr.fr.min.js
│ │ │ ├── lunr.he.min.js
│ │ │ ├── lunr.hi.min.js
│ │ │ ├── lunr.hu.min.js
│ │ │ ├── lunr.hy.min.js
│ │ │ ├── lunr.it.min.js
│ │ │ ├── lunr.ja.min.js
│ │ │ ├── lunr.jp.min.js
│ │ │ ├── lunr.kn.min.js
│ │ │ ├── lunr.ko.min.js
│ │ │ ├── lunr.multi.min.js
│ │ │ ├── lunr.nl.min.js
│ │ │ ├── lunr.no.min.js
│ │ │ ├── lunr.pt.min.js
│ │ │ ├── lunr.ro.min.js
│ │ │ ├── lunr.ru.min.js
│ │ │ ├── lunr.sa.min.js
│ │ │ ├── lunr.stemmer.support.min.js
│ │ │ ├── lunr.sv.min.js
│ │ │ ├── lunr.ta.min.js
│ │ │ ├── lunr.te.min.js
│ │ │ ├── lunr.th.min.js
│ │ │ ├── lunr.tr.min.js
│ │ │ ├── lunr.vi.min.js
│ │ │ └── lunr.zh.min.js
│ │ ├── tinyseg.js
│ │ └── wordcut.js
│ └── workers
│ │ ├── search.b8dbb3d2.min.js
│ │ └── search.b8dbb3d2.min.js.map
└── stylesheets
│ ├── main.7e359304.min.css
│ ├── main.7e359304.min.css.map
│ ├── palette.06af60db.min.css
│ └── palette.06af60db.min.css.map
├── examples
└── index.html
├── images
├── architecture.png
├── logo.png
├── logo_huro_fondo_blanco.png
└── logo_huro_large.svg
├── index.html
├── search
└── search_index.json
├── sitemap.xml
└── sitemap.xml.gz
/.readthedocs.yaml:
--------------------------------------------------------------------------------
1 | # .readthedocs.yaml
2 | # Read the Docs configuration file
3 | # See https://docs.readthedocs.io/en/stable/config-file/v2.html for details
4 |
5 | # Required
6 | version: 2
7 |
8 | # Set the OS, Python version and other tools you might need
9 | build:
10 | os: ubuntu-22.04
11 | tools:
12 | python: "3.12"
13 | # You can also specify other tool versions:
14 | # nodejs: "19"
15 | # rust: "1.64"
16 | # golang: "1.19"
17 |
18 | # Build documentation in the "docs/" directory with Sphinx
19 | # sphinx:
20 | # configuration: docs/conf.py
21 |
22 | # Build documentation with Mkdocs
23 | mkdocs:
24 | configuration: mkdocs.yml
25 |
26 | # Dependencies required to build your docs
27 | python:
28 | install:
29 | - requirements: requirements.txt
30 |
31 | # Optionally build your docs in additional formats such as PDF and ePub
32 | # formats:
33 | # - pdf
34 | # - epub
35 |
36 | # Optional but recommended, declare the Python requirements required
37 | # to build your documentation
38 | # See https://docs.readthedocs.io/en/stable/guides/reproducible-builds.html
39 | # python:
40 | # install:
41 | # - requirements: docs/requirements.txt
42 |
--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
1 | MIT License
2 |
3 | Copyright (c) 2022 OnOrbitROS Jose Luis Ramon Carretero
4 |
5 | Permission is hereby granted, free of charge, to any person obtaining a copy
6 | of this software and associated documentation files (the "Software"), to deal
7 | in the Software without restriction, including without limitation the rights
8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9 | copies of the Software, and to permit persons to whom the Software is
10 | furnished to do so, subject to the following conditions:
11 |
12 | The above copyright notice and this permission notice shall be included in all
13 | copies or substantial portions of the Software.
14 |
15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21 | SOFTWARE.
22 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | # Simulation
2 | ROS Framework for on orbiting space robots
3 | 
4 |
5 | Documentation found here: https://simulation.readthedocs.io/
6 |
--------------------------------------------------------------------------------
/axis_by_axis/CMakeLists.txt:
--------------------------------------------------------------------------------
1 | cmake_minimum_required(VERSION 3.0.2)
2 | project(axis_by_axis)
3 |
4 | ## Compile as C++11, supported in ROS Kinetic and newer
5 | # add_compile_options(-std=c++11)
6 |
7 | ## Find catkin macros and libraries
8 | ## if COMPONENTS list like find_package(catkin REQUIRED COMPONENTS xyz)
9 | ## is used, also find other catkin packages
10 | find_package(catkin REQUIRED COMPONENTS
11 | roscpp
12 | rospy
13 | std_msgs
14 | )
15 |
16 | ## System dependencies are found with CMake's conventions
17 | # find_package(Boost REQUIRED COMPONENTS system)
18 |
19 |
20 | ## Uncomment this if the package has a setup.py. This macro ensures
21 | ## modules and global scripts declared therein get installed
22 | ## See http://ros.org/doc/api/catkin/html/user_guide/setup_dot_py.html
23 | # catkin_python_setup()
24 |
25 | ################################################
26 | ## Declare ROS messages, services and actions ##
27 | ################################################
28 |
29 | ## To declare and build messages, services or actions from within this
30 | ## package, follow these steps:
31 | ## * Let MSG_DEP_SET be the set of packages whose message types you use in
32 | ## your messages/services/actions (e.g. std_msgs, actionlib_msgs, ...).
33 | ## * In the file package.xml:
34 | ## * add a build_depend tag for "message_generation"
35 | ## * add a build_depend and a exec_depend tag for each package in MSG_DEP_SET
36 | ## * If MSG_DEP_SET isn't empty the following dependency has been pulled in
37 | ## but can be declared for certainty nonetheless:
38 | ## * add a exec_depend tag for "message_runtime"
39 | ## * In this file (CMakeLists.txt):
40 | ## * add "message_generation" and every package in MSG_DEP_SET to
41 | ## find_package(catkin REQUIRED COMPONENTS ...)
42 | ## * add "message_runtime" and every package in MSG_DEP_SET to
43 | ## catkin_package(CATKIN_DEPENDS ...)
44 | ## * uncomment the add_*_files sections below as needed
45 | ## and list every .msg/.srv/.action file to be processed
46 | ## * uncomment the generate_messages entry below
47 | ## * add every package in MSG_DEP_SET to generate_messages(DEPENDENCIES ...)
48 |
49 | ## Generate messages in the 'msg' folder
50 | # add_message_files(
51 | # FILES
52 | # Message1.msg
53 | # Message2.msg
54 | # )
55 |
56 | ## Generate services in the 'srv' folder
57 | # add_service_files(
58 | # FILES
59 | # Service1.srv
60 | # Service2.srv
61 | # )
62 |
63 | ## Generate actions in the 'action' folder
64 | # add_action_files(
65 | # FILES
66 | # Action1.action
67 | # Action2.action
68 | # )
69 |
70 | ## Generate added messages and services with any dependencies listed here
71 | # generate_messages(
72 | # DEPENDENCIES
73 | # std_msgs
74 | # )
75 |
76 | ################################################
77 | ## Declare ROS dynamic reconfigure parameters ##
78 | ################################################
79 |
80 | ## To declare and build dynamic reconfigure parameters within this
81 | ## package, follow these steps:
82 | ## * In the file package.xml:
83 | ## * add a build_depend and a exec_depend tag for "dynamic_reconfigure"
84 | ## * In this file (CMakeLists.txt):
85 | ## * add "dynamic_reconfigure" to
86 | ## find_package(catkin REQUIRED COMPONENTS ...)
87 | ## * uncomment the "generate_dynamic_reconfigure_options" section below
88 | ## and list every .cfg file to be processed
89 |
90 | ## Generate dynamic reconfigure parameters in the 'cfg' folder
91 | # generate_dynamic_reconfigure_options(
92 | # cfg/DynReconf1.cfg
93 | # cfg/DynReconf2.cfg
94 | # )
95 |
96 | ###################################
97 | ## catkin specific configuration ##
98 | ###################################
99 | ## The catkin_package macro generates cmake config files for your package
100 | ## Declare things to be passed to dependent projects
101 | ## INCLUDE_DIRS: uncomment this if your package contains header files
102 | ## LIBRARIES: libraries you create in this project that dependent projects also need
103 | ## CATKIN_DEPENDS: catkin_packages dependent projects also need
104 | ## DEPENDS: system dependencies of this project that dependent projects also need
105 | catkin_package(
106 | # INCLUDE_DIRS include
107 | # LIBRARIES axis_by_axis
108 | # CATKIN_DEPENDS roscpp rospy std_msgs
109 | # DEPENDS system_lib
110 | )
111 |
112 | ###########
113 | ## Build ##
114 | ###########
115 |
116 | ## Specify additional locations of header files
117 | ## Your package locations should be listed before other locations
118 | include_directories(
119 | # include
120 | ${catkin_INCLUDE_DIRS}
121 | )
122 |
123 | ## Declare a C++ library
124 | # add_library(${PROJECT_NAME}
125 | # src/${PROJECT_NAME}/axis_by_axis.cpp
126 | # )
127 |
128 | ## Add cmake target dependencies of the library
129 | ## as an example, code may need to be generated before libraries
130 | ## either from message generation or dynamic reconfigure
131 | # add_dependencies(${PROJECT_NAME} ${${PROJECT_NAME}_EXPORTED_TARGETS} ${catkin_EXPORTED_TARGETS})
132 |
133 | ## Declare a C++ executable
134 | ## With catkin_make all packages are built within a single CMake context
135 | ## The recommended prefix ensures that target names across packages don't collide
136 | add_executable(${PROJECT_NAME}_node src/trajectory.cpp)
137 |
138 |
139 | ## Rename C++ executable without prefix
140 | ## The above recommended prefix causes long target names, the following renames the
141 | ## target back to the shorter version for ease of user use
142 | ## e.g. "rosrun someones_pkg node" instead of "rosrun someones_pkg someones_pkg_node"
143 | # set_target_properties(${PROJECT_NAME}_node PROPERTIES OUTPUT_NAME node PREFIX "")
144 |
145 | ## Add cmake target dependencies of the executable
146 | ## same as for the library above
147 | add_dependencies(${PROJECT_NAME}_node ${${PROJECT_NAME}_EXPORTED_TARGETS} ${catkin_EXPORTED_TARGETS})
148 |
149 | ## Specify libraries to link a library or executable target against
150 | target_link_libraries(${PROJECT_NAME}_node
151 | ${catkin_LIBRARIES}
152 | )
153 |
154 | #############
155 | ## Install ##
156 | #############
157 |
158 | # all install targets should use catkin DESTINATION variables
159 | # See http://ros.org/doc/api/catkin/html/adv_user_guide/variables.html
160 |
161 | ## Mark executable scripts (Python etc.) for installation
162 | ## in contrast to setup.py, you can choose the destination
163 | # catkin_install_python(PROGRAMS
164 | # scripts/my_python_script
165 | # DESTINATION ${CATKIN_PACKAGE_BIN_DESTINATION}
166 | # )
167 |
168 | ## Mark executables for installation
169 | ## See http://docs.ros.org/melodic/api/catkin/html/howto/format1/building_executables.html
170 | # install(TARGETS ${PROJECT_NAME}_node
171 | # RUNTIME DESTINATION ${CATKIN_PACKAGE_BIN_DESTINATION}
172 | # )
173 |
174 | ## Mark libraries for installation
175 | ## See http://docs.ros.org/melodic/api/catkin/html/howto/format1/building_libraries.html
176 | # install(TARGETS ${PROJECT_NAME}
177 | # ARCHIVE DESTINATION ${CATKIN_PACKAGE_LIB_DESTINATION}
178 | # LIBRARY DESTINATION ${CATKIN_PACKAGE_LIB_DESTINATION}
179 | # RUNTIME DESTINATION ${CATKIN_GLOBAL_BIN_DESTINATION}
180 | # )
181 |
182 | ## Mark cpp header files for installation
183 | # install(DIRECTORY include/${PROJECT_NAME}/
184 | # DESTINATION ${CATKIN_PACKAGE_INCLUDE_DESTINATION}
185 | # FILES_MATCHING PATTERN "*.h"
186 | # PATTERN ".svn" EXCLUDE
187 | # )
188 |
189 | ## Mark other files for installation (e.g. launch and bag files, etc.)
190 | # install(FILES
191 | # # myfile1
192 | # # myfile2
193 | # DESTINATION ${CATKIN_PACKAGE_SHARE_DESTINATION}
194 | # )
195 |
196 | #############
197 | ## Testing ##
198 | #############
199 |
200 | ## Add gtest based cpp test target and link libraries
201 | # catkin_add_gtest(${PROJECT_NAME}-test test/test_axis_by_axis.cpp)
202 | # if(TARGET ${PROJECT_NAME}-test)
203 | # target_link_libraries(${PROJECT_NAME}-test ${PROJECT_NAME})
204 | # endif()
205 |
206 | ## Add folders to be run by python nosetests
207 | # catkin_add_nosetests(test)
208 |
--------------------------------------------------------------------------------
/axis_by_axis/package.xml:
--------------------------------------------------------------------------------
1 |
2 |
30 |
31 |
--------------------------------------------------------------------------------
/docs/experiments.md:
--------------------------------------------------------------------------------
1 | # Experiments to validate OnOrbitROS
2 |
3 | Some experiments have been conducted to validate the framework.
4 |
5 | ---
6 |
7 | ## OnOrbitROS Dynamics: ETS VII simulation
8 |
9 | The dynamics of the ETS VII robotic experiments are simulated and compared to the actual flight data obtained from the mission.
10 |
11 | The results obtained are presented in:
12 |
13 | Ramón, J. L., Pomares, J., & Felicetti, L. (2023). Task space control for on-orbit space robotics using a new ROS-based framework. Simulation Modelling Practice and Theory, 127(102790), 102790. [https://doi.org/10.1016/j.simpat.2023.102790](https://doi.org/10.1016/j.simpat.2023.102790)
14 |
15 |
16 | And compared to the real mission from:
17 |
18 | S. Abiko, K. Yoshida, Post flight analysis of ETS-VII space robotic experiments, in: Proceedings of the 6th International Symposium on Artificial Intelligence and Robotics & Automation in Space: I-SAIRAS, St-Hubert, Quebec, Canada, 2001.
19 |
20 | and
21 |
22 | K. Yoshida, Engineering test satellite VII flight experiments for space robot dynamics and control: theories on laboratory test beds ten years ago, now in orbit, Int. J. Rob. Res. 22 (2003) 321–335, https://doi.org/10.1177/0278364903022005003.
23 |
24 |
25 | ---
26 |
27 | ## OnOrbitROS propagator
28 |
29 | Two orbits, a circular an elliptic, have been simulated and compared to GMAT's RungeKutta89 propagator.
30 | The satellite used is a sphere with 1m of diameter orbiting around Earth in LEO.
31 |
32 | The selected orbit has been taken from the Cubesat XI-V orbit on 17th April 2024:
33 |
34 | ```yaml
35 | 1 28895U 05042F 24108.35401664 .00006071 00000-0 10830-2 0 9996
36 | 2 28895 98.1916 244.1444 0015992 185.6352 174.4674 14.67269849985536
37 | ```
38 |
39 | >> ### Circular Orbit
40 |
41 | The orbit has been taken from the previous TLE set (in km and º) and the eccentricity set to 0:
42 |
43 | eccentricity: 0.0
44 | semi_major_axis: 7047.5
45 | inclination: 98.1916
46 | rate_of_right_ascension: 244.1444
47 | right_ascension_ini: 244.1444
48 | argument_of_perigee_ini: 185.6352
49 | rate_argument_Of_perigee: 185.6352
50 | mean_anomaly_ini: 174.4674
51 |
52 | time_pass_perigee:
53 | sec : 0
54 | min: 0
55 | hour: 0
56 | mday: 1
57 | mon: 1
58 | year: 2000
59 |
60 | time_start:
61 | sec : 0
62 | min: 0
63 | hour: 0
64 | mday: 1
65 | mon: 1
66 | year: 2000
67 |
68 |
69 |
70 | In the graphs below, the orbital position relative to the ECI (Earth MJ2000) frame is shown for the first 15,000 seconds of the propagated orbit. The left panels display results from OnOrbitROS, while the right one show results from GMAT. The `x`, `y`, and `z` axes are represented in red, green, and blue respectively. The satellite's altitude is depicted in orange.
71 |
72 | The table following the graphs presents the numerical data for the maximum values of the orbital position and the mean altitude. The orbital shapes and maximum values obtained using OnOrbitROS are consistent with those from GMAT, with relative errors under 1%, using GMAT as the reference standard.
73 |
74 |
75 |
76 |
77 |
78 |
79 | >> ### Elliptic Orbit
80 |
81 | The same orbit has been evaluated in this case with an eccentricity value of 0.01.
82 |
83 | eccentricity: 0.01
84 |
85 | The following graphs show the results for the elliptic orbit, following the same format as used for the circular orbit. The shapes of the orbits in both cases are consistent, with a maximum relative error of 1.64%.
86 |
87 |
88 |
89 |
90 |
91 |
92 | ---
93 |
94 | ## Other validations
95 |
96 |
97 | !!! Warning
98 | More validations on orbital mechanics and perturbation modelling to come.
99 |
--------------------------------------------------------------------------------
/docs/extra.css:
--------------------------------------------------------------------------------
1 | h1 {
2 | color: darkblue;
3 | }
4 |
--------------------------------------------------------------------------------
/docs/extra.js:
--------------------------------------------------------------------------------
1 |
2 | document.addEventListener('DOMContentLoaded', function() {
3 | var codeBlocks = document.querySelectorAll('pre');
4 | codeBlocks.forEach(function(codeBlock) {
5 | var copyButton = document.createElement('button');
6 | copyButton.className = 'copy-button';
7 | copyButton.innerHTML = '';
8 | copyButton.addEventListener('click', function() {
9 | var codeText = codeBlock.querySelector('code').innerText;
10 | navigator.clipboard.writeText(codeText).then(function() {
11 | console.log('Code copied to clipboard');
12 | }, function(err) {
13 | console.error('Failed to copy code: ', err);
14 | });
15 | });
16 | codeBlock.parentNode.insertBefore(copyButton, codeBlock);
17 | positionCopyButton(copyButton, codeBlock); // Call the function to position the copy button
18 | });
19 | });
20 |
21 | // Function to position the copy button
22 | function positionCopyButton(copyButton, codeBlock) {
23 | // Set the copy button's position to the top right corner of the code block
24 | var codeBlockRect = codeBlock.getBoundingClientRect();
25 | copyButton.style.position = 'absolute';
26 | copyButton.style.top = (codeBlockRect.top-30) + 'px';
27 | copyButton.style.right = (codeBlockRect.left+105) + 'px';
28 | }
--------------------------------------------------------------------------------
/docs/huro.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
If you are not redirected automatically, click here.
13 | 14 | -------------------------------------------------------------------------------- /docs/images/architecture.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/OnOrbitROS/Simulation/c2edc7414cc90a6f0421c16702ef44c5895fd151/docs/images/architecture.png -------------------------------------------------------------------------------- /docs/images/circularGMAT.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/OnOrbitROS/Simulation/c2edc7414cc90a6f0421c16702ef44c5895fd151/docs/images/circularGMAT.jpg -------------------------------------------------------------------------------- /docs/images/circularOnOrbitROS.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/OnOrbitROS/Simulation/c2edc7414cc90a6f0421c16702ef44c5895fd151/docs/images/circularOnOrbitROS.png -------------------------------------------------------------------------------- /docs/images/circularResults.jpeg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/OnOrbitROS/Simulation/c2edc7414cc90a6f0421c16702ef44c5895fd151/docs/images/circularResults.jpeg -------------------------------------------------------------------------------- /docs/images/cranfield.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/OnOrbitROS/Simulation/c2edc7414cc90a6f0421c16702ef44c5895fd151/docs/images/cranfield.png -------------------------------------------------------------------------------- /docs/images/drag.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/OnOrbitROS/Simulation/c2edc7414cc90a6f0421c16702ef44c5895fd151/docs/images/drag.png -------------------------------------------------------------------------------- /docs/images/elipticOnOrbitROS.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/OnOrbitROS/Simulation/c2edc7414cc90a6f0421c16702ef44c5895fd151/docs/images/elipticOnOrbitROS.png -------------------------------------------------------------------------------- /docs/images/ellipticGMAT.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/OnOrbitROS/Simulation/c2edc7414cc90a6f0421c16702ef44c5895fd151/docs/images/ellipticGMAT.jpg -------------------------------------------------------------------------------- /docs/images/ellipticResults.jpeg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/OnOrbitROS/Simulation/c2edc7414cc90a6f0421c16702ef44c5895fd151/docs/images/ellipticResults.jpeg -------------------------------------------------------------------------------- /docs/images/etsvii.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/OnOrbitROS/Simulation/c2edc7414cc90a6f0421c16702ef44c5895fd151/docs/images/etsvii.jpg -------------------------------------------------------------------------------- /docs/images/frames.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/OnOrbitROS/Simulation/c2edc7414cc90a6f0421c16702ef44c5895fd151/docs/images/frames.png -------------------------------------------------------------------------------- /docs/images/gravGrad.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/OnOrbitROS/Simulation/c2edc7414cc90a6f0421c16702ef44c5895fd151/docs/images/gravGrad.png -------------------------------------------------------------------------------- /docs/images/hurospace.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/OnOrbitROS/Simulation/c2edc7414cc90a6f0421c16702ef44c5895fd151/docs/images/hurospace.jpg -------------------------------------------------------------------------------- /docs/images/linkedin.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/OnOrbitROS/Simulation/c2edc7414cc90a6f0421c16702ef44c5895fd151/docs/images/linkedin.png -------------------------------------------------------------------------------- /docs/images/logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/OnOrbitROS/Simulation/c2edc7414cc90a6f0421c16702ef44c5895fd151/docs/images/logo.png -------------------------------------------------------------------------------- /docs/images/logo_huro_fondo_blanco.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/OnOrbitROS/Simulation/c2edc7414cc90a6f0421c16702ef44c5895fd151/docs/images/logo_huro_fondo_blanco.png -------------------------------------------------------------------------------- /docs/images/logo_huro_large.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 73 | -------------------------------------------------------------------------------- /docs/images/orbit_publisher.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/OnOrbitROS/Simulation/c2edc7414cc90a6f0421c16702ef44c5895fd151/docs/images/orbit_publisher.png -------------------------------------------------------------------------------- /docs/images/ros_pub.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/OnOrbitROS/Simulation/c2edc7414cc90a6f0421c16702ef44c5895fd151/docs/images/ros_pub.png -------------------------------------------------------------------------------- /docs/images/ua.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/OnOrbitROS/Simulation/c2edc7414cc90a6f0421c16702ef44c5895fd151/docs/images/ua.png -------------------------------------------------------------------------------- /docs/index.md: -------------------------------------------------------------------------------- 1 | # Welcome to OnOrbitROS 2 |  3 | 4 | OnOrbitROS is a unified open-source framework for space-robotics 5 | simulations. It is based on Robot Operating System (ROS) and includes and reproduces the principal environmental conditions that eventual space robots and manipulators could experience in an on-orbit servicing scenario. 6 | 7 | 8 | ## About Us 9 |OnOrbitROS is a unified open-source framework for space-robotics simulations. It is based on Robot Operating System (ROS) and includes and reproduces the principal environmental conditions that eventual space robots and manipulators could experience in an on-orbit servicing scenario.
"},{"location":"#about-us","title":"About Us","text":"Developed by Human Robotics (HURO) group, University of Alicante, Spain.
Space robotics broadly encompasses the application of robots and autonomous systems for operations in the space environment. HURO Space Robotics section investigates the development of robotic systems and their control for performing tasks in space.
You can find more information about this project and other works in our website: HURO Space Robotics
"},{"location":"Install/","title":"Installation Guide","text":"OnOrbitROS framework can be found on this GitHub. There you will find the packages to install in your ROS environment as well as different guided examples to discover the functionalities OnOrbitROS offers. With this framework it is also possible to create new projects from the existing ones or from scrath.
"},{"location":"Install/#ros-distribution","title":"ROS Distribution","text":"The project has been developed in ROS Noetic (Ubuntu 20.04). The intallation guidelines can be found here. ROS offers many tutorials and guides to help you set up and work with your environments and projects, that can be accessed through ROS Wiki.
"},{"location":"Install/#gazebo-simulator","title":"Gazebo Simulator","text":"Gazebo is an open-source and free simulation tool specifically designed for fast and efficient test development. It has been selected as it can simulate complex 3D environments where each element possesses properties such as mass, velocity, and friction, and can accurately represent the dynamics and interations of space robots in complex 3D settings, so it is possible to create a realistic simulation of on-orbit conditions. Install here.
There is high interation of Gazebo within ROS: simulations are generated from an XML file based on the SDF description language (extension of URDF that ROS uses for robot description) for quick and easy creations and configurations; and it is possible to include additional plugins to extend its functionalities.
OnOrbitROS includes different plugins to simulate the on-orbit-specific conditions (using existing standard and available ROS/Gazebo packages to develop complex tasks). Also, Gazebo integrates interfaces to use multiple physics engines such as Open Dynamics Engine, Bullet, Simbody, Dynamic Animation and Robotics Toolkit (DART).
"},{"location":"Install/#onorbitros-framework","title":"OnOrbitROS Framework","text":"Import the ROS framework from the GitHub (found here).
git clone
or manually into your desired ROS environment.catkin_make
or catkin_make_isolated
.You can now start working with the framework.
"},{"location":"Install/#examples-of-applications","title":"Examples of Applications","text":"In case you would like to install the example cases:
git clone
or manually into the folder orbit_ws/src
.catkin_make
or catkin_make_isolated
..launch
corresponding to that example. See the specific example documentation for that (found in Examples of Applications)In addition to the Ubuntu installation with its packages, it might be necessary to manually install this other packages. This is because OnOrbitROS takes advantages of the number of packages already developed in ROS to improve its functionalities.
Packages for the controllers:
$ sudo apt-get install ros-noetic-controller-manager
$ sudo apt-get install ros-noetic-joint-state-controller
$ sudo apt-get install ros-noetic-effort-controller
$ sudo apt-get install ros-noetic-position-controllers
OnOrbitROS serves as a foundational platform for the study and development of on-orbit applications, leveraging the powerful combination of ROS and Gazebo for hyper-realistic simulations.
For extended information about this framework, its architecture and some applications go to doi.
Jos\u00e9 L. Ram\u00f3n, Jorge Pomares, Leonard Felicetti,\nTask space control for on-orbit space robotics using a new ROS-based framework,\nSimulation Modelling Practice and Theory,\nVolume 127,\n2023,\n102790,\nISSN 1569-190X,\nhttps://doi.org/10.1016/j.simpat.2023.102790\n(https://www.sciencedirect.com/science/article/pii/S1569190X23000679)\n
Here you can find the architecture of the framework. In the OnOrbitROS workspace installed (see Installation Guide for more info) you will find many pacakges, which are shown in this image.
"},{"location":"examples/","title":"Examples of Applications using OnOrbitROS","text":"In this section you can find different examples that exploit OnOrbitROS functionalities. They can serve as a guide to develop your own application, based on this or from scratch.
"}]} -------------------------------------------------------------------------------- /site/sitemap.xml: -------------------------------------------------------------------------------- 1 | 2 |