-
Notifications
You must be signed in to change notification settings - Fork 54
Add industrial profile #49
Conversation
|
Oops... Turned out this PR depends on ros/meta-ros#457 and one more new commit in meta-openembedded (http://cgit.openembedded.org/meta-openembedded/commit/?id=e8d5a1bb6a022172246f095aca0979ab5a6bd2ed). |
|
@rojkov looks like svn is needed in |
|
test this please |
|
test this please |
|
test this please |
|
test this please |
|
test this please. I dont know why some requests fail to trigger build |
|
test this please |
0aded9c to
0fbfdf6
Compare
|
|
Can one of the admins verify this patch? |
5601ac0 to
0abd6f8
Compare
|
doc/industrial-profile.rst
Outdated
| #. Pick and place. | ||
|
|
||
| However combined with the computer vision profile they can be extended to | ||
| other applications like drons, self-driving cars, agricultural robots etc. |
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.
s/drons/drones
doc/industrial-profile.rst
Outdated
| joints movement planning, | ||
| - core ROS-I components used for interfacing with real robot hardware. | ||
|
|
||
| Due to the embedded nature of Refkit no GUI components have been included |
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.
Should we use 'IoT RefKit' instead of 'Refkit'?
doc/industrial-profile.rst
Outdated
|
|
||
| For detailed usage instructions please refer `ROS Industrial tutorials`_ | ||
|
|
||
| How to use |
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.
Does this section apply to the platform running the IoT RefKit?
|
|
||
| G205 <base_angle> <left_angle> <right_angle> <hand_angle> | ||
| Set position for all four servos. The code accepts four parameters which | ||
| are PWM signal widths for the respective servos in miliseconds. |
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.
s/miliseconds/milliseconds
| Setting up | ||
| ========== | ||
|
|
||
| 1. Make sure you have installed the packages `uarmmeta--moveit-config`, |
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.
How can one check if they are installed and install them if they are not?
|
| Date: Thu, 26 Jan 2017 14:42:31 +0200 | ||
| Subject: [PATCH] Switch from TinyXML to TinyXML2 | ||
|
|
||
| Upstream-Status: Inappropriate [ROS won't move to TinyXML2 until kinetic] |
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 is kinetic?
| Date: Wed, 25 Jan 2017 11:06:58 +0200 | ||
| Subject: [PATCH 2/2] moveit_ros/planning: Use TinyXML2 instead of TinyXML | ||
|
|
||
| Upstream-Status: Inappropriate [TinyXML2 is WONTFIX in indigo-devel] |
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.
Add a link here to the issue. At least I'm interested if we can ever upstream this... I don't even know what is indigo-devel.
| Date: Thu, 26 Jan 2017 14:30:04 +0200 | ||
| Subject: [PATCH] controller_manager: drop unused inclusion of tinyxml.h | ||
|
|
||
| Upstream-Status: Submitted [https://github.com/ros-controls/ros_control/pull/261] |
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.
Merged also.
| iftop@networking-layer | ||
| image-transport@ros-layer | ||
| industrial-msgs@ros-layer | ||
| industrial-robot-client@ros-layer |
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.
It might make sense to merge this patch with the previous one that was changing the same file.
| inherit packagegroup | ||
|
|
||
| SUMMARY_${PN} = "IoT Reference OS Kit Industrial Robotics profile" | ||
| RDEPENDS_${PN} = "\ |
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.
Do you need a separate packagegroup for development images? Or are the packages the same in both?
| @@ -0,0 +1,3 @@ | |||
| # TODO: This way cv_bridge doesn't require libboost_python, but this tweak | |||
| # should be dropped after ROS is compatible with python3-only distro. | |||
| EXTRA_OECMAKE += "-DANDROID=ON" | |||
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.
Hmm, the next patch says: switch ROS to python3 . Is it python3-compatible or not?
|
I think the PR should be amended with the changes in patch |
|
On Tue, Jun 13, 2017 at 5:12 PM, Ismo Puustinen wrote:
I think the PR should be amended with the changes in patch meta-refkit-industrial:
make the layer Yocto 2.0 compatible, and then the patch should be
dropped. The patches shouldn't fix previous patches in the same PR.
+1
btw, it'd be easy to add meta-refkit-industrial for compatibility checking
too (see the automatically generated tests in refkit-poky.py)
|
|
Initially I thought that the layer might have packages unrelated to
robotics, e.g. LinuxCNC or MachineKit. I wouldn't like to narrow the scope
still.
…On Tue, Jun 13, 2017 at 2:58 PM, Ismo Puustinen ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In doc/profiles.rst
<#49 (comment)>:
> @@ -61,3 +61,4 @@ Profile Summary
#. refkit-image-common: A configuration with interactive tools but without any special software in it. Recommended target if you are not interested in any given profile.
#. refkit-image-computervision: A profile with tools and configuration for computer vision use cases.
#. refkit-image-gateway: A profile with tools and configuration for acting as an IoT sensor.
+#. refkit-image-industrial: A profile with core ROS Industrial packages intended to be used as a base for industrial robotics use cases.
This is just a thought, but should the image (and profile) rather be
called industrial-robotics?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#49 (review)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AACCYQH2GFUXRLG6PAYoM6Cw_VIKOsY6ks5sDnlSgaJpZM4MM2Pt>
.
|
|
Yes. @Mynti asked to include them explicitly to built targets in the scope
of this PR.
…On Tue, Jun 13, 2017 at 3:03 PM, Ismo Puustinen ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In meta-refkit/conf/distro/include/refkit-ci.inc
<#49 (comment)>:
> @@ -59,9 +59,15 @@ REFKIT_CI_POSTBUILD_SELFTESTS="secureboot refkit-poky refkit-license-check image
# Any other symbols would be skipped in parser.
#
# Following targets would be used to perform default build task.
-# When adding new profile images, add them to refkit-installer-image.bb
-# and they will get pulled into the build indirectly.
-REFKIT_CI_BUILD_TARGETS="refkit-image-minimal refkit-installer-image swtpm-wrappers-native ovmf"
+REFKIT_CI_BUILD_TARGETS=" \
+ refkit-image-minimal \
+ refkit-image-computervision \
+ refkit-image-gateway \
Are refkit-image-computervision and refkit-image-gateway added on purpose?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#49 (review)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AACCYamK9otIv7YJkZDW616dPg0NFR4tks5sDnqvgaJpZM4MM2Pt>
.
|
|
I must confess I don't fully understand what you imply here. I just tried
to follow the way how packages are included in other profiles' images.
Mindlessly though.
…On Tue, Jun 13, 2017 at 5:08 PM, Ismo Puustinen ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In meta-refkit/recipes-core/packagegroups/packagegroup-industrial.bb
<#49 (comment)>:
> @@ -0,0 +1,14 @@
+SUMMARY = "IoT Reference OS Kit Industrial Robotics profile package groups"
+LICENSE = "MIT"
+PR = "r1"
+
+inherit packagegroup
+
+SUMMARY_${PN} = "IoT Reference OS Kit Industrial Robotics profile"
+RDEPENDS_${PN} = "\
Do you need a separate packagegroup for development images? Or are the
packages the same in both?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#49 (review)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AACCYRcFnciUxYJj8UwZDy2LMm26v1XYks5sDpfCgaJpZM4MM2Pt>
.
|
|
Thanks @ipuustin for the review!
|
|
There was a problem in CI, where one of the boards froze at test phase. Should be fixed now. |
|
@rojkov looks nice! please rebase and I'll create a combined PR |
Signed-off-by: Dmitry Rozhkov <dmitry.rozhkov@linux.intel.com>
Signed-off-by: Dmitry Rozhkov <dmitry.rozhkov@linux.intel.com>
The override is going to be used for conditional reconfigurations of packages added by the industrial profile. Signed-off-by: Dmitry Rozhkov <dmitry.rozhkov@linux.intel.com>
Signed-off-by: Dmitry Rozhkov <dmitry.rozhkov@linux.intel.com>
Signed-off-by: Dmitry Rozhkov <dmitry.rozhkov@linux.intel.com>
Signed-off-by: Dmitry Rozhkov <dmitry.rozhkov@linux.intel.com>
Signed-off-by: Dmitry Rozhkov <dmitry.rozhkov@linux.intel.com>
since it's maintained better than deprecated TinyXML. The patch set is not going to be merged to the upstream ROS layer because only ROS Indigo release is maintained in the layer currently. In ros/rospack#62 it was suggested that the packages in the ROS Indigo release are not going to switch to TinyXML2, but it may happen in future releases. Also a comment in ros/urdfdom_headers#35 suggests that the switch is precluded by the fact TinyXML types are widely used in urdfdom's public API thus requires fixing all downstream packages which can be difficult if possible at all. Signed-off-by: Dmitry Rozhkov <dmitry.rozhkov@linux.intel.com>
Signed-off-by: Dmitry Rozhkov <dmitry.rozhkov@linux.intel.com>
…itly Profile images get built in CI only because they export tests. This change makes them build targets explicitly. Signed-off-by: Dmitry Rozhkov <dmitry.rozhkov@linux.intel.com>
Signed-off-by: Dmitry Rozhkov <dmitry.rozhkov@linux.intel.com>
Signed-off-by: Dmitry Rozhkov <dmitry.rozhkov@linux.intel.com>
Also include a HOWTO doc on how to set up the demo. Signed-off-by: Dmitry Rozhkov <dmitry.rozhkov@linux.intel.com>
No description provided.