You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Fixing issue with Demo.cs not working with new URDF Importer co-routine
* remove unused import (#163)
* update package import urls for tcp connector and urdf importer (#166)
* Update urdf_tutorial.md (#168)
* Added M prefixes to docs (#167)
* Adding Editor version to Ros Integration Readme
* Updating package dependencies to proper versions
Pick and place tutorial was failing to compile its scripts because
the package manifest was pointing to an older version of
ROS-TCP-Connector. Updated the manifest and also pulled latest changes
for ros_tcp_endpoint.
Tested by running DemoScene
* Updating Contribution Content (#186)
* Contributing content
* PR feedback
* Adding PR template (#191)
* fixing typo in ros-unity service tutorial (#198)
* Unity service example (#199)
* added example of implementing a UnityService
* adding tutorial for unity service
* added a couple comments to the example code
* typos and code standard fixes
* consistency: changing the service name for position_service to pos_srv
* updating the tutorial to match the corresponding script
* Update the list of new physics features (#204)
* add new sections for the released new physics features
Co-authored-by: Amanda <[email protected]>
* Update to 0.3.0 (#207)
* Removing old version tags from git URLs in quick_setup
Addressing user issue #209. Our quick_setup guide was still recommending users check out v.0.2.0 of our packages. Removed the reference to a specific package version and instead included a note that users can explicitly declare a package version if desired.
Tested by making the change locally in the package manifest.
* Adding network troubleshooting doc. (#195)
* Adding network troubleshooting doc.
* Updating tutorials to the glorious new world (#211)
* add changelog (#218)
add changelog
* Forum links to README, config.yml (#219)
* Add linter (#227)
* Add linter and pre-commit hooks
* Formatting
* Remove setting up ruby
* Resolve conflicts 2 (#233)
* Merging dev branch into main (#78)
* Reverting params.yaml and updating code in server_endpoint.md
* TcpServer class was renamed
* convert all files with dos2unix (#76)
* Minor tutorial tweaks, update version numbers
Co-authored-by: Devin Miller <[email protected]>
Co-authored-by: Peifeng Jing <[email protected]>
* Updating instructions for URDF repository (#71)
* 1. Adding images for URDF tutorial 2. Adding instructions highlighting Disable Collison tag
* Adding link to example of disable collision tag in the niryo_one URDF file
* Sarah/readme update (#112)
* Adding physics roadmap and minor formatting changes
* formatting nits
* Calling out feature requests
* Update for ROS-TCP-Connector namespace changes
* Mpinol/simrealrebased (#107)
* Adding sim and real pnp files.
* Update with new instructions (#147)
* Update tutorial text (#148)
* AIRO-405 Adding Yamato boilerplate to Robotics Hub (#144)
* Adding testing boilerplate
* Adding tests to run after message generation
* Tweaks to ensure run works in Bokken image
* Enabling audio by default, but disabling it in yamato config
* Hotfix: Remove DemoScripts asmdef
The DemoScripts.asmdef was a bit of experimental cruft that snuck in via
my Yamato changes. This causes Demo.cs to compile as an Editor script,
which means it can no longer be instantiated in the scene hierarchy
(this breaks the demo). Removing the asmdef puts things back to normal.
Tested by running the demo.
* Use latest main
* Fixing issue with Demo.cs not working with new URDF Importer co-routine
* remove unused import (#163)
* update package import urls for tcp connector and urdf importer (#166)
* Update urdf_tutorial.md (#168)
* Added M prefixes to docs (#167)
* Adding Editor version to Ros Integration Readme
* Updating package dependencies to proper versions
Pick and place tutorial was failing to compile its scripts because
the package manifest was pointing to an older version of
ROS-TCP-Connector. Updated the manifest and also pulled latest changes
for ros_tcp_endpoint.
Tested by running DemoScene
* Updating Contribution Content (#186)
* Contributing content
* PR feedback
* Adding PR template (#191)
* Unity service example (#199)
* added example of implementing a UnityService
* adding tutorial for unity service
* added a couple comments to the example code
* typos and code standard fixes
* consistency: changing the service name for position_service to pos_srv
* updating the tutorial to match the corresponding script
* Update the list of new physics features (#204)
* add new sections for the released new physics features
Co-authored-by: Amanda <[email protected]>
* Update to 0.3.0 (#207)
* Removing old version tags from git URLs in quick_setup
Addressing user issue #209. Our quick_setup guide was still recommending users check out v.0.2.0 of our packages. Removed the reference to a specific package version and instead included a note that users can explicitly declare a package version if desired.
Tested by making the change locally in the package manifest.
* Updating tutorials to the glorious new world (#211)
* add changelog (#218)
add changelog
* Forum links to README, config.yml (#219)
* Add linter (#227)
* Add linter and pre-commit hooks
* Formatting
* Remove setting up ruby
* Fixing issue with Demo.cs not working with new URDF Importer co-routine (#162)
Co-authored-by: Devin Miller <[email protected]>
* Readme: New Link (#172)
* Fixing issue with Demo.cs not working with new URDF Importer co-routine
* remove unused import (#163)
* README update
* PR feedback
* Blog post link update
Co-authored-by: Devin Miller <[email protected]>
Co-authored-by: peifeng-unity <[email protected]>
* Added newsletter link (#175)
* remove stale merge
* Minor formmating
* Fix README and git sub module
* Revert unintentional change in urdf_appendix.md
* Add back tutorials/pick_and_place/ROS/src/ros_tcp_endpoint
Co-authored-by: LaurieCheers-unity <[email protected]>
Co-authored-by: Devin Miller <[email protected]>
Co-authored-by: Peifeng Jing <[email protected]>
Co-authored-by: vidurvij-Unity <[email protected]>
Co-authored-by: sarah-gibson <[email protected]>
Co-authored-by: Devin Miller (Unity) <[email protected]>
Co-authored-by: peifeng-unity <[email protected]>
Co-authored-by: Amanda <[email protected]>
Co-authored-by: Hamid Younesy <[email protected]>
* Update Demo (#235)
* Update Demo
* Minor fix
* Update tutorial manifest to use v0.4.0
* Update ros_tcp_endpoint module
* Update quick_setup version
* Update tutorial manifest
* added chmod to make sure the python scripts are executable (#239)
* Minor update in README.md
* minor fix
Co-authored-by: Devin Miller <[email protected]>
Co-authored-by: peifeng-unity <[email protected]>
Co-authored-by: vidurvij-Unity <[email protected]>
Co-authored-by: LaurieCheers-unity <[email protected]>
Co-authored-by: Devin Miller (Unity) <[email protected]>
Co-authored-by: Amanda <[email protected]>
Co-authored-by: Hamid Younesy <[email protected]>
Co-authored-by: Peifeng Jing <[email protected]>
Co-authored-by: sarah-gibson <[email protected]>
Copy file name to clipboardexpand all lines: .github/PULL_REQUEST_TEMPLATE.md
+4-3
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ Provide any relevant links here.
16
16
17
17
## Testing and Verification
18
18
19
-
Please describe the tests that you ran to verify your changes. Please also provide instructions, ROS packages, and Unity project files as appropriate so we can reproduce the test environment.
19
+
Please describe the tests that you ran to verify your changes. Please also provide instructions, ROS packages, and Unity project files as appropriate so we can reproduce the test environment.
20
20
21
21
### Test Configuration:
22
22
- Unity Version: [e.g. Unity 2020.2.0f1]
@@ -27,8 +27,9 @@ Please describe the tests that you ran to verify your changes. Please also provi
27
27
## Checklist
28
28
-[ ] Ensured this PR is up-to-date with the `dev` branch
29
29
-[ ] Created this PR to target the `dev` branch
30
-
-[ ] Followed the style guidelines as described in the [Contribution Guidelines](../CONTRIBUTING.md)
30
+
-[ ] Followed the style guidelines as described in the [Contribution Guidelines](https://github.com/Unity-Technologies/Unity-Robotics-Hub/blob/main/CONTRIBUTING.md)
31
31
-[ ] Added tests that prove my fix is effective or that my feature works
32
+
-[ ] Updated the [Changelog](https://github.com/Unity-Technologies/Unity-Robotics-Hub/blob/dev/CHANGELOG.md) and described changes in the [Unreleased section](https://github.com/Unity-Technologies/Unity-Robotics-Hub/blob/dev/CHANGELOG.md#unreleased)
All notable changes to this repository will be documented in this file.
4
+
5
+
The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/) and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html).
Copy file name to clipboardexpand all lines: CONTRIBUTING.md
+7-7
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
# Contribution Guidelines
2
2
3
-
Thank you for your interest in contributing to Unity Robotics! To facilitate your
4
-
contributions, we've outlined a brief set of guidelines to ensure that your extensions
3
+
Thank you for your interest in contributing to Unity Robotics! To facilitate your
4
+
contributions, we've outlined a brief set of guidelines to ensure that your extensions
5
5
can be easily integrated.
6
6
7
7
## Communication
@@ -40,10 +40,10 @@ We run continuous integration on all PRs; all tests must be passing before the P
40
40
41
41
All Python code should follow the [PEP 8 style guidelines](https://pep8.org/).
42
42
43
-
All C# code should follow the [Microsoft C# Coding Conventions](https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/inside-a-program/coding-conventions).
44
-
Additionally, the [Unity Coding package](https://docs.unity3d.com/Packages/[email protected]/manual/index.html)
45
-
can be used to format, encode, and lint your code according to the standard Unity
46
-
development conventions. Be aware that these Unity conventions will supersede the
43
+
All C# code should follow the [Microsoft C# Coding Conventions](https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/inside-a-program/coding-conventions).
44
+
Additionally, the [Unity Coding package](https://docs.unity3d.com/Packages/[email protected]/manual/index.html)
45
+
can be used to format, encode, and lint your code according to the standard Unity
46
+
development conventions. Be aware that these Unity conventions will supersede the
47
47
Microsoft C# Coding Conventions where applicable.
48
48
49
49
Please note that even if the code you are changing does not adhere to these guidelines,
Copy file name to clipboardexpand all lines: README.md
+10-10
Original file line number
Diff line number
Diff line change
@@ -33,8 +33,7 @@ A robot simulation demonstrating Unity's new physics solver (no ROS dependency).
33
33
| Tutorial | Description |
34
34
|---|---|
35
35
|[ROS–Unity Integration](tutorials/ros_unity_integration/README.md)| A set of component-level tutorials showing how to set up communication between ROS and Unity |
36
-
|[URDF Importer](tutorials/urdf_importer/urdf_tutorial.md)| Steps on using the Unity package for loading [URDF](http://wiki.ros.org/urdf) files |
37
-
36
+
|[URDF Importer](tutorials/urdf_importer/urdf_tutorial.md)| Steps on using the Unity package for loading [URDF](http://wiki.ros.org/urdf) files |
38
37
39
38
## Component Repos
40
39
@@ -57,7 +56,7 @@ Unite Now 2020: Simulating Robots with ROS and Unity [video](https://resources.u
Use articulation bodies to easily prototype industrial designs with realistic motion and behavior [blog post](https://blogs.unity3d.com/2020/05/20/use-articulation-bodies-to-easily-prototype-industrial-designs-with-realistic-motion-and-behavior/)
59
+
Use articulation bodies to easily prototype industrial designs with realistic motion and behavior [blog post](https://blogs.unity3d.com/2020/05/20/use-articulation-bodies-to-easily-prototype-industrial-designs-with-realistic-motion-and-behavior/)
61
60
62
61
### More from Unity
63
62
@@ -85,19 +84,20 @@ Interested in early access to ROS 2 integration? Email [[email protected]
85
84
86
85
## Community and Feedback
87
86
88
-
The Unity Robotics projects are open-source and we encourage and welcome contributions.
89
-
If you wish to contribute, be sure to review our [contribution guidelines](CONTRIBUTING.md)
87
+
The Unity Robotics projects are open-source and we encourage and welcome contributions.
88
+
If you wish to contribute, be sure to review our [contribution guidelines](CONTRIBUTING.md)
90
89
and [code of conduct](CODE_OF_CONDUCT.md).
91
90
92
91
## Support
93
-
For general questions, feedback, or feature requests, connect directly with the
For bugs or other issues, please file a GitHub issue and the Robotics team will
97
-
investigate the issue as soon as possible.
93
+
For questions or discussions about Unity Robotics package installations or how to best set up and integrate your robotics projects, please create a new thread on the [Unity Robotics forum](https://forum.unity.com/forums/robotics.623/) and make sure to include as much detail as possible.
98
94
99
-
## Newsletter
95
+
For feature requests, bugs, or other issues, please file a [GitHub issue](https://github.com/Unity-Technologies/Unity-Robotics-Hub/issues) using the provided templates and the Robotics team will investigate as soon as possible.
100
96
97
+
For any other questions or feedback, connect directly with the
Copy file name to clipboardexpand all lines: faq.md
+2-11
Original file line number
Diff line number
Diff line change
@@ -7,9 +7,7 @@
7
7
- [How can I install the Unity Packages without starting from a template project?](#how-can-i-install-the-unity-packages-without-starting-from-a-template-project)
- [How does the TCP Endpoint compare to Rosbridge Server?](#how-does-the-tcp-endpoint-compare-to-rosbridge-server)
10
-
- [I receive a `Starting server on ...` message in my ROS terminal, but see a `SocketException: A connection attempt failed because the connected party did not respond after a period of time, or established connection failed because connected host has failed to respond.` in my Unity console.](#i-receive-a-starting-server-on--message-in-my-ros-terminal-but-see-a-socketexception-a-connection-attempt-failed-because-the-connected-party-did-not-respond-after-a-period-of-time-or-established-connection-failed-because-connected-host-has-failed-to-respond-in-my-unity-console)
11
10
- [I'm getting the error: `...failed because unknown error handler name 'rosmsg'`.](#im-getting-the-error-failed-because-unknown-error-handler-name-rosmsg)
12
-
- [Unity can't connect to ROS!](#unity-cant-connect-to-ros)
13
11
-[URDF-Importer](#urdf-importer)
14
12
- [I don't see an option to Import Robot from URDF, or I have compile errors upon importing the URDF-Importer.](#i-dont-see-an-option-to-import-robot-from-urdf-or-i-have-compile-errors-upon-importing-the-urdf-importer)
15
13
-[Can't find what you're looking for?](#cant-find-what-youre-looking-for)
@@ -23,7 +21,7 @@ How does your Unity integration compare to ROS#?
23
21
---
24
22
Two of the Unity Robotics repos (URDF Importer and TCP Connector) have been forked from the [Siemens ROS# repo](https://github.com/siemens/ros-sharp).
25
23
26
-
In the URDF Importer we have added the functionality to instantiate a robot from URDF into a Unity scene with [Articulation Body](https://docs.unity3d.com/2020.2/Documentation/Manual/class-ArticulationBody.html) components on their corresponding joints.
24
+
In the URDF Importer we have added the functionality to instantiate a robot from URDF into a Unity scene with [Articulation Body](https://docs.unity3d.com/2020.2/Documentation/Manual/class-ArticulationBody.html) components on their corresponding joints.
27
25
28
26
Aside from facilitating communication with the TCP Endpoint, the TCP Connector contains the `MessageGeneration` code from ROS#. We added the extra functionality that when generating a C# class from a ROS message, functions are also generated that will serialize and deserialize the messages as ROS would internally.
29
27
@@ -58,23 +56,16 @@ The time was logged when the message was sent from Unity before being serialized
58
56
- ROS# with ROS Bridge Suite took ~2 seconds
59
57
- TCP Connector with TCP Endpoint took ~0.17 seconds
60
58
61
-
I receive a `Starting server on ...` message in my ROS terminal, but see a `SocketException: A connection attempt failed because the connected party did not respond after a period of time, or established connection failed because connected host has failed to respond.` in my Unity console.
62
-
---
63
-
This is likely an issue with how your network adapters are set up if you are using a virtual machine. You may need to do some troubleshooting to ensure that your guest OS can talk to your host OS and vice versa. One simple way to do this is to set up a "Host-Only" style network, but this varies based on what virtualization software you're using. Try to ensure that you can `ping` your host OS's IP from inside the guest, and can `ping` the guest from the host, then try this last step again.
64
-
65
59
I'm getting the error: `...failed because unknown error handler name 'rosmsg'`.
66
60
---
67
61
This is due to a bug in an outdated package version. Try running `sudo apt-get update && sudo apt-get upgrade` to upgrade.
68
62
69
-
Unity can't connect to ROS!
70
-
---
71
-
Ensure that the ROS IP address is entered correctly as the `Host Name` in the RosConnect component in Unity, and if you are using a `params.yaml` file, that the appropriate IP addresses are filled in.
72
-
73
63
# URDF-Importer
74
64
75
65
I don't see an option to Import Robot from URDF, or I have compile errors upon importing the URDF-Importer.
76
66
---
77
67
The [ArticulationBody](https://docs.unity3d.com/2020.2/Documentation/Manual/class-ArticulationBody.html) has dependencies on Unity Editor versions [2020.2.0](https://unity3d.com/unity/whats-new/2020.2.0)+. Try updating your project to the latest 2020.2 release.
0 commit comments