ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
Thanks!
I was just trying to make it work :P, so, just in case i missunderstood the things about the header, i tested with header too.
the dump of the byte array im tryinto send to the turtle is
#[0 0 0 64 0 0 0 0] in hex '[0000004000000000]'
I tried to implement some of the subscriber logic, and use the /turtle1/pose topic
trying to understand (by hand) the shape of the stream i realized that there are a word that doesnt match with the type format:
expecting these values (in this order) 4.72179222107 #[236 24 151 64] 7.13545799255 #[172 85 228 64]. 4.0640001297 #[74 12 130 64]. 0.0 #[0 0 0 0]. 0.0 #[0 0 0 0].
i received the following bytes (as part of a longer stream)
228 64 74 12 130 64 0 0 0 0 0 0 0 0 20 0 0 0 236 24 151 64 172 85
matching with the expected values, and sorting by expected position: 236 24 151 64 172 85 228 64 74 12 130 64 0 0 0 0 0 0 0 0
[ 20 0 0 0 ] Here, this guy have nothing to do with the rest of the message, but appear in the stream splitting the messages. So, i tried using all the permutations of this word at the beginning and the end of the message with out any success.
It could be related? do i need to send a trail-word? I searched in google about ROS and trails without success too.
2 | ordering the couple of bytes |
Thanks!
I was just trying to make it work :P, so, just in case i missunderstood the things about the header, i tested with header too.
the dump of the byte array im tryinto send to the turtle is
#[0 0 0 64 0 0 0 0] in hex '[0000004000000000]'
I tried to implement some of the subscriber logic, and use the /turtle1/pose topic
trying to understand (by hand) the shape of the stream i realized that there are a word that doesnt match with the type format:
expecting these values (in this order)
4.72179222107 #[236 24 151 64]
64]
7.13545799255 #[172 85 228 64].
64].
4.0640001297 #[74 12 130 64].
64].
0.0 #[0 0 0 0].
0.0 #[0 0 0 0].
i received the following bytes (as part of a longer stream)
228 64 74 12 130 64 0 0 0 0 0 0 0 0 20 0 0 0 236 24 151 64 172 85
matching with the expected values, and sorting by expected position:
position:
236 24 151 64
64
172 85 228 64
64
74 12 130 64
0 0 0 0
64
0 0 0 0
0 0 0 0
[ 20 0 0 0 ] Here, this guy have nothing to do with the rest of the message, but appear in the stream splitting the messages. So, i tried using all the permutations of this word at the beginning and the end of the message with out any success.
It could be related? do i need to send a trail-word? I searched in google about ROS and trails without success too.
3 | edited in the main answer |
Thanks! thanks for the tip
I was just trying to make it work :P, so, just in case i missunderstood the things about the header, i tested with header too.
the dump of the byte array im tryinto send to the turtle is
#[0 0 0 64 0 0 0 0] in hex '[0000004000000000]'
I tried to implement some of the subscriber logic, and use the /turtle1/pose topic
trying to understand (by hand) the shape of the stream i realized that there are a word that doesnt match with the type format:
expecting these values (in this order) 4.72179222107 #[236 24 151 64]
7.13545799255 #[172 85 228 64].
4.0640001297 #[74 12 130 64].
0.0 #[0 0 0 0].
0.0 #[0 0 0 0].
i received the following bytes (as part of a longer stream)
228 64 74 12 130 64 0 0 0 0 0 0 0 0 20 0 0 0 236 24 151 64 172 85
matching with the expected values, and sorting by expected position:
236 24 151 64
172 85 228 64
74 12 130 64
0 0 0 0
0 0 0 0
[ 20 0 0 0 ] Here, this guy have nothing to do with the rest of the message, but appear in the stream splitting the messages. So, i tried using all the permutations of this word at the beginning and the end of the message with out any success.
It could be related? do i need to send a trail-word? I searched in google about ROS and trails without success too.