ros2 / rosidl_typesupport_opensplice Goto Github PK
View Code? Open in Web Editor NEWrosidl typesupport for PrismTech's OpenSplice DDS.
License: Apache License 2.0
rosidl typesupport for PrismTech's OpenSplice DDS.
License: Apache License 2.0
The warning implemented here (https://github.com/ros2/rosidl_typesupport_opensplice/blob/master/opensplice_cmake_module/env_hook/opensplice.sh.in#L71) is a little overwhelming, it appears during every environment load (e.g. new bash shell) when using a custom OSPL_URI.
Would you take a PR to remove it? I would think if the user is setting OSPL_URI, they are doing so intentionally.
Hello, I am new to ros2.
Service requests are sent (by client node) but never Received after the number of nodes reach around 98.
I searched this resp for whatever is related to 98,99,100,
and discovered a hard coded "99" here:
Is this the problem?
If it is the problem, how do I modify and make it apply?
I found that you get the gid from the instance handle, but set the seril to ZERO.
when i using opensplice's get_matched_subscription_data/get_matched_publication_data/get_discovered_participant_data or read_instance function, it will retrieve the xxxBuiltinTopicData, and we can get the gid from the BuiltinTopicKey_t key field(in fact, it is a typedef int[3]). it seems that the serial is not ZERO.
how can I match it. or what does the serial
actual mean. can I just ignore it and only using the first two field of int[3].
Hi,
I was using ros2 eloquent in conjunction with vcpkg. When configuring a simple project, the following line introduced an error somewhere down the find_package
call:
The fix for this is as follows:
file(TO_CMAKE_PATH $ENV{AMENT_PREFIX_PATH} AMENT_PREFIX_PATH)
find_package(opensplice ${quiet} NO_MODULE COMPONENTS CXX
PATHS ${AMENT_PREFIX_PATH} /usr /usr/local)
This will correctly escape the path which, due to Windows, contains backslashes.
Best,
René
Support for long double
types as defined in IDL.
Related to ros2/rosidl#383.
control_msgs contains a GripperCommand
action, which uses the GripperCommand
msg.
For ROS2 dashing, this package (released version, 0.7.0, and master) generates C header files with duplicated guard names, e.g.
$ grep -r _GRIPPERCOMMAND__H_ .
./build/control_msgs/rosidl_typesupport_opensplice_cpp/control_msgs/msg/dds_opensplice/GripperCommand_.h:#ifndef _GRIPPERCOMMAND__H_
./build/control_msgs/rosidl_typesupport_opensplice_cpp/control_msgs/msg/dds_opensplice/GripperCommand_.h:#define _GRIPPERCOMMAND__H_
./build/control_msgs/rosidl_typesupport_opensplice_cpp/control_msgs/action/dds_opensplice/GripperCommand_.h:#ifndef _GRIPPERCOMMAND__H_
./build/control_msgs/rosidl_typesupport_opensplice_cpp/control_msgs/action/dds_opensplice/GripperCommand_.h:#define _GRIPPERCOMMAND__H_
For this reason the build fails with:
In file included from /root/target_ws/build/control_msgs/rosidl_typesupport_opensplice_cpp/control_msgs/action/dds_opensplice/ccpp_GripperCommand_.h:4:0,
from /root/target_ws/build/control_msgs/rosidl_typesupport_opensplice_cpp/control_msgs/action/gripper_command__rosidl_typesupport_opensplice_cpp.hpp:10,
from /root/target_ws/build/control_msgs/rosidl_typesupport_opensplice_cpp/control_msgs/action/dds_opensplice/gripper_command__type_support.cpp:17:
/root/target_ws/build/control_msgs/rosidl_typesupport_opensplice_cpp/control_msgs/action/dds_opensplice/GripperCommand_.h:41:37: error: ‘dds_’ in namespace ‘control_msgs::msg’ does not name a type
::control_msgs::msg::dds_::GripperCommand_ command_;
^~~~
/root/target_ws/build/control_msgs/rosidl_typesupport_opensplice_cpp/control_msgs/action/dds_opensplice/gripper_command__type_support.cpp: In function ‘void control_msgs::action::typesupport_opensplice_cpp::convert_ros_message_to_dds(const __ros_msg_type_GripperCommand_Goal&, control_msgs::action::typesupport_opensplice_cpp::__dds_msg_type_GripperCommand_Goal&)’:
/root/target_ws/build/control_msgs/rosidl_typesupport_opensplice_cpp/control_msgs/action/dds_opensplice/gripper_command__type_support.cpp:108:38: error: ‘using __dds_msg_type_GripperCommand_Goal = struct control_msgs::action::dds_::GripperCommand_Goal_ {aka struct control_msgs::action::dds_::GripperCommand_Goal_}’ has no member named ‘command_’
ros_message.command, dds_message.command_);
^~~~~~~~
/root/target_ws/build/control_msgs/rosidl_typesupport_opensplice_cpp/control_msgs/action/dds_opensplice/gripper_command__type_support.cpp: In function ‘void control_msgs::action::typesupport_opensplice_cpp::convert_dds_message_to_ros(const __dds_msg_type_GripperCommand_Goal&, control_msgs::action::typesupport_opensplice_cpp::__ros_msg_type_GripperCommand_Goal&)’:
/root/target_ws/build/control_msgs/rosidl_typesupport_opensplice_cpp/control_msgs/action/dds_opensplice/gripper_command__type_support.cpp:164:17: error: ‘const __dds_msg_type_GripperCommand_Goal {aka const struct control_msgs::action::dds_::GripperCommand_Goal_}’ has no member named ‘command_’
dds_message.command_, ros_message.command);
Furthermore, JointTrajectory.action
(control_msgs) collides with JointTrajectory.msg
(trajectory_msgs), both use _JOINTTRAJECTORY__H_
.
For ROS2 crystal the generated header guards are less likely to collide, because goal, feedback and result are generated separately. (before #11?)
To avoid this problem the guards should contain the package name and the type to make them unique.
The files in dds_opensplice
get generated by idlpp
though.
Required Info:
ros-eloquent-opensplice-cmake-module/bionic,bionic,now 0.8.1-1bionic.20191024.044026 amd64 [installed,automatic]
ros-eloquent-rmw-opensplice-cpp/bionic,bionic,now 0.8.1-1bionic.20191024.062945 amd64 [installed]
ros-eloquent-rosidl-typesupport-opensplice-c/bionic,bionic,now 0.8.1-1bionic.20191024.062611 amd64 [installed,automatic]
ros-eloquent-rosidl-typesupport-opensplice-cpp/bionic,bionic,now 0.8.1-1bionic.20191024.062531 amd64 [installed,automatic]
Follow https://index.ros.org/doc/ros2/Tutorials/Actions/Creating-an-Action/
I attached an archive of the package.
action_tutorials.opspl.bug.tar.gz
Successful build
many compile errors
rosidl_typesupport_opensplice_c
and rosidl_typesupport_opensplice_cpp
need to allow generating messages and services in an action
folder and namespace
The service templates would need to change to allow service definitions to live in the .actions folder
connects to ros2/rosidl#301
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.