reach_ros_node
reach_ros_node copied to clipboard
ROS driver for the Reach RTK GNSS module by Emlid
A small change such that the build files have lowerdashes, and does not give errors building in ros2 Iron.
It would be nice to have a ros2 branch to exist in this repo. I forked and migrated this project, and a [pull request](https://github.com/rpng/reach_ros_node/pull/22) is pending. In case pull requests...
It is possible to interface with the hardware over UART rather than over TCP? Would it be possible to implement this as a feature of this package? Reference: https://docs.emlid.com/reach/before-you-start/hardware-integration/
When I run the code, It seems I have successfully connected to the RTK, but I can only receive the bytes data and got an error message like below **[INFO]...
I have been using this repo for my Reach RS+/Reach M+ pair and it worked well. I could get RTK 14 frames per second. However, today, I upgrade my iOS...
Hi, I am building a Robocar which is driven by Nvidia Jetson TX2 an Emlid Reach M+ which works with another Emlid Reach RS+. I connect the M+ and Nvidia...
Hi, I am using emlid M+ without a base station. I found that all data in /tcpvel message are 0. Is this normal?
Hi, I am using this repo with Emlid Reach M+. I found if I just ran the ros node with `rosrun each_ros_node nmea_tcp_driver _host:=192.168.2.15 _port:=7777` Everything seemed fine. I could...
Closes #13 Should be compatible with existing Python 2 installations and new Noetic builds
Explanation: In comparison to earlier versions, python 3 is treats every string as unicode. The unicode formatted string can be encoded and stored in bytes, or decoded back into unicode...