Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SystemCommandSrv.srv missing #2

Open
ymollard opened this issue May 27, 2019 · 6 comments
Open

SystemCommandSrv.srv missing #2

ymollard opened this issue May 27, 2019 · 6 comments

Comments

@ymollard
Copy link

The problem commented there is still unsolved: 25a5054

Why has SystemCommand.srv been renamed into SystemCommandSrv.srv while this file does not exist?

@dbersan
Copy link

dbersan commented Aug 13, 2020

Yep, and many other errors

@dbersan
Copy link

dbersan commented Aug 13, 2020

I won't make a PR for this because this seems to be a dead project, but if anyone has issues, here is the correct CMakeLists.txt:

cmake_minimum_required(VERSION 2.8.3)
project(edo_core_msgs)

## Compile as C++11, supported in ROS Kinetic and newer
# add_compile_options(-std=c++11)

## Find catkin macros and libraries
## if COMPONENTS list like find_package(catkin REQUIRED COMPONENTS xyz)
## is used, also find other catkin packages
find_package(catkin REQUIRED COMPONENTS
  geometry_msgs
  message_generation
  roscpp
  std_msgs
)

## Generate messages in the 'msg' folder
 add_message_files(
   FILES
   JointState.msg
   JointStateArray.msg
   JointControl.msg
   JointControlArray.msg
   MovementCommand.msg
   MovementFeedback.msg
   JointConfiguration.msg
   JointInit.msg
   JointConfigurationArray.msg
   JointCalibration.msg
   JointReset.msg
   CartesianPose.msg
   JointsPositions.msg
   JointMonitoring.msg
   MachineState.msg
   NodeSwVersion.msg
   NodeSwVersionArray.msg
   JointFwVersion.msg
   JointFwVersionArray.msg
   Point.msg
   Frame.msg
   SystemCommand.msg
 )

## Generate services in the 'srv' folder

 add_service_files(
   FILES
   JointsNumber.srv
   DirectKinematics.srv
   InverseKinematics.srv
   SoftwareVersion.srv
   ControlSwitch.srv
   LoadConfigurationFile.srv ## 180305 GC&IL
 )


## Generate added messages and services with any dependencies listed here
 generate_messages(
   DEPENDENCIES
   geometry_msgs
   std_msgs
 )

catkin_package(
#  INCLUDE_DIRS include
#  LIBRARIES edo_core_msgs
  CATKIN_DEPENDS geometry_msgs message_generation roscpp std_msgs
#  DEPENDS system_lib
)

## Specify additional locations of header files
## Your package locations should be listed before other locations
include_directories(
# include
  ${catkin_INCLUDE_DIRS}
)

@ymollard
Copy link
Author

ymollard commented Aug 13, 2020

@dhiegomaga I've transferred all my eDo-related repositories to a dedicated Github organization eDO Community. Feel free to make PR or request write access, on my side I don't have eDOs anymore so I can't test anything with actual robots, I think it's good if several people can handle these repos.
@Bracewind @ianathompson @lucarinelli @ludusrusso you might also be interested in contributing there: eDO Community.

@Bracewind
Copy link

Bracewind commented Aug 21, 2020

Seems to me that I cannot add my repositories to the organization.

Moreover, if you directly retrieve the package edo_core_msg from the edo robot, you don't have to manually add msg files. I don't recommend adding the message files, since you will be using msg structure that eDO v3 won't probably use, and so it will probably break (or do nothing).

@ymollard
Copy link
Author

What does that mean to "retrieve the package edo_core_msg from the edo robot"?
Your workstation needs msg files in some ROS package in your workspace. Do you mean make a copy from the robot?

@Bracewind
Copy link

Yes, it is exactly what I mean. When you connect using ssh, you have access to all files contained in the robot, and especially to the catkin directory of the robot, that contains all the ros packages (such as edo_core_msg). I do not work anymore on edo so I don't remember the path. If someone find it, it would be great to push it on a fork of this repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants