-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
I found the ROS2 concept and design much more well established, especially for industrial. My problem on porting was more like when something available in ROS1 concept is not supported in the ROS2 concept. For example the infamous ira_laser_tools. This package basically merges all the scanning laser topics and publishes it as one so we can use it for AMCL / navigation (with the PointClouds too). The package will use ros::master api so it can manipulate the value alongside the data type format in which such concept is not supported in ROS2. In ROS1 we can take a list of topics with the data types in the format of std::string (topic name), std::string (data type). Laser topic parser in this package will process the data in a c++ way to get only the ones publishing sensor_msgs (scan data type). We can also call topics and the data type in ROS2, but in a format of std::map... I don't have sufficient c++ knowledge and reference to parse from the ROS2 api. I believe these kind of difficulties is also why nobody is working on it too.. In cases like these, how do you tackle the issue?
As for your system, you don't need to implement the serial protocol yourself as microROS does this for you! I'm guessing you are following the instructions in the README here. Let me know how it goes and thanks for describing your pain points :)
Related posts
-
Show HN: I made a ROS package for realtime semantic segmentation
-
Create VR-Controlled Roboter in Unity
-
Kalman Filter Tutorial: Kalman Filter from the Ground Up
-
Robotics Simulation - Bridging the Gap Between Virtual and Real Worlds
-
Show HN: Remote terminal via WebRTC and file-transfer – no SSH or VPN required