ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
I found a temporary solution for my problem! I tested different versions/tags (whichever is the right terminology) of the Rosserial git and I found out that the error was introduced in version/tag 0.5.6. So for now I guess I will use 0.5.5, which works nicely with the xbee.
In order to use 0.5.5 of rosserial I had to enter a command inside of the git directory: git checkout ba83ced96c
(this is the last commit of 0.5.5). Then it could install that with catkin_make
and catking_make install
2 | No.2 Revision |
I found a temporary solution solution for my problem! I tested different versions/tags (whichever is the right terminology) of the Rosserial git and I found out that the error was introduced in version/tag 0.5.6.
So for now I guess I will use 0.5.5, which works nicely with the xbee.
In order to use 0.5.5 of rosserial I had to enter a command inside of the git directory: git checkout ba83ced96c
(this is the last commit of 0.5.5). Then it could install that with catkin_make
and catking_make install
3 | No.3 Revision |
I found a temporary solution for my problem! I tested different versions/tags (whichever is the right terminology) of the Rosserial git and I found out that the error was introduced in version/tag 0.5.6. So for now I guess I will use 0.5.5, which works nicely with the xbee.
In order to use 0.5.5 of rosserial I had to enter a command inside of the git directory: git checkout ba83ced96c
(this is the last commit of 0.5.5). Then it could install that with catkin_make
and catking_make install
Hope this issue gets fixed soon!
4 | No.4 Revision |
I found a temporary solution for my problem! I tested different versions/tags (whichever is the right terminology) of the Rosserial git and I found out that the error was introduced in version/tag 0.5.6. So for now I guess I will use 0.5.5, which works nicely with the xbee.
In order to use 0.5.5 of rosserial I had to enter a command inside of the git directory: git checkout ba83ced96c
(this is the last commit of 0.5.5). Then it I could install that with catkin_make
and catking_make install
Hope this issue gets fixed soon!
5 | No.5 Revision |
I found a temporary solution for my problem! I tested different versions/tags (whichever is the right terminology) of the Rosserial git and I found out that the error was introduced in version/tag 0.5.6. So for now I guess I will use 0.5.5, which works nicely with the xbee.
In order to use 0.5.5 of rosserial I had to enter a command inside of the git directory: git checkout ba83ced96c
(this is the last commit of 0.5.5). Then I could install that with catkin_make
and catking_make install
Hope this issue gets fixed soon!
EDIT: It turns out I came across a lucky bug, because when I tried to do the same again on my other ROS copy, it did not work =(
6 | No.6 Revision |
I found a temporary solution for my problem! I tested different versions/tags (whichever is the right terminology) of the Rosserial git and I found out that the error was introduced in version/tag 0.5.6. So for now I guess I will use 0.5.5, which works nicely with the xbee.
In order to use 0.5.5 of rosserial I had to enter a command inside of the git directory: git checkout ba83ced96c
(this is the last commit of 0.5.5). Then I could install that with catkin_make
and catking_make install
Hope this issue gets fixed soon!
EDIT: It turns out I came across a lucky bug, because when I tried to do the same again on my other ROS copy, it did not work =(work.
7 | No.7 Revision |
I found a temporary solution solution for my problem! I tested different versions/tags (whichever is the right terminology) of the Rosserial git and I found out that the error problem was introduced in version/tag 0.5.6.
So for now I guess I will use 0.5.5, which works nicely with the xbee.
Hope this issue gets fixed soon!
EDIT: It turns out I came across a lucky bug, because when I tried to do the same again on my other ROS copy, it did not work.. Really hope this issue gets fixed soon!