ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
If I understand you correctly, you could take a look at ShapeShifter to create a generic subscriber. That subscriber has access to the raw data bytes.
See also the ros_type_introspection package for some examples and convenience classes that make this sort of thing somewhat easier to do.
2 | No.2 Revision |
If I understand you correctly, you could take a look at ShapeShifter to create a generic subscriber. That subscriber has access to the raw data bytes.
See also the ros_type_introspection package for some examples (such as How to create a generic Topic Subscriber) and convenience classes that make this sort of thing somewhat easier to do.
3 | No.3 Revision |
If It's still unclear to me why you want to do this (but then again, perhaps that is not important): but if I understand you correctly, you could take a look at ShapeShifter to create a generic subscriber. That subscriber has access to the raw data bytes.
See also the ros_type_introspection package for some examples (such as How to create a generic Topic Subscriber) and convenience classes that make this sort of thing somewhat easier to do.
4 | No.4 Revision |
It's still unclear to me why you want to do this (but then again, perhaps that is not important): but if I understand you correctly, you could take a look at ShapeShifter to create a generic subscriber. That subscriber has access to the raw data bytes.
See also the ros_type_introspection package for some examples (such as How to create a generic Topic Subscriber) and convenience classes that make this sort of thing somewhat easier to do.
Edit:
If it is possible to just get the raw eth frame of the topic [..]
You're probably aware that TCP streams != ethernet frames, so what you suggest is not directly possible without some knowledge of how the network stack on the publishing side fragmented the stream.