Dangield's profile - activity

overview network karma followed questions activity

2019-10-11 05:01:36 -0500	received badge	● Famous Question (source)
2019-01-29 23:47:33 -0500	received badge	● Notable Question (source)
2018-05-15 15:55:40 -0500	received badge	● Popular Question (source)
2018-05-15 09:17:27 -0500	edited question	Unreliable wall_timer in ros2 Unreliable wall_timer in ros2 I encountered something rather alarming while using wall_timer in ros2. I created a simple
2018-05-15 08:41:11 -0500	asked a question	Unreliable wall_timer in ros2 Unreliable wall_timer in ros2 I encountered something rather alarming while using wall_timer in ros2. I created a simple
2018-05-15 06:26:31 -0500	commented answer	Unreliable communication using executors Sorry, didn't see your comment earlier. It's here. There is a for loop with sleep_for() in it, that seemed to be the pro
2018-04-24 12:54:40 -0500	received badge	● Famous Question (source)
2018-04-24 12:49:40 -0500	commented question	Unreliable communication using executors Of course. Sorry for inconvenience.
2018-04-24 12:48:24 -0500	received badge	● Scholar (source)
2018-04-24 12:47:47 -0500	marked best answer	Unreliable communication using executors Hello. I have a problem I can’t solve by myself. I have 2 nodes inheriting from the main Node class, one of them receives data from an IMU and sends it to the other. In the other one frequency of received messages is being calculated. When I run both nodes separately I get results close to expected ones, so eg for 50Hz publishing I receive messages with ~50Hz frequency, for 25Hz it’s also ~25Hz and so on. The issue starts when I try to start both nodes from an executor. In that case when publishing with 50Hz I receive messages with about 37-38 Hz, for 25Hz - ~18-19Hz and so on. Generally for every frequency above 1 Hz I receive messages with about 2/3-3/4 of the publishing frequency. I tried both single-threaded and multi-threaded executor but it doesn’t seem to change anything, nor does toggling the intra-process communication in nodes’ constructors. I’ve also tried modifying QoS options of this particular connection on both ends but with no effect. The publishing node has been confirmed to publish data with configured frequency. I'm working on BeagleBone Green Wireless board with 4.4.113-ti-r149 linux kernel. I'm using ros2 ardent latest version (I updated this month but I am not aware if the issue was present before or not). Publisher Node: https://github.com/GroupOfRobots/RysR... Subscriber Node: https://github.com/GroupOfRobots/RysR... Launching with executors: https://github.com/GroupOfRobots/RysR...
2018-04-24 12:46:28 -0500	answered a question	Unreliable communication using executors I found the solution. It seems that it was caused by a rclcpp::sleep_for() found in a different node ran from this execu
2018-04-24 12:46:18 -0500	edited question	Unreliable communication using executors Unreliable communication using executors Hello. I have a problem I can’t solve by myself. I have 2 nodes inheriting from
2018-04-24 12:46:18 -0500	received badge	● Editor (source)
2018-04-24 12:06:53 -0500	edited question	Unreliable communication using executors Unreliable communication using executors Hello. I have a problem I can’t solve by myself. I have 2 nodes inheriting from
2018-04-21 21:12:54 -0500	received badge	● Notable Question (source)
2018-04-20 08:43:21 -0500	received badge	● Popular Question (source)
2018-04-20 07:15:03 -0500	asked a question	Unreliable communication using executors Unreliable communication using executors Hello. I have a problem I can’t solve by myself. I have 2 nodes inheriting from