indraneel's profile - activity

Following instructions on https://catkin-tools.readthedocs.io/en/latest/installing.html fixed the problem for me $ sudo

@kllysin Hello! did you manage to figure this out? A few things that came to my mind after reading this, let me know if

@kllysin Hello! did you manage to figure this out? A few things that came to my mind after reading this, let me know if

@kllysin Hello! did you manage to figure this out? A few things that came to my mind after reading this, let me know if

Thanks brilliant suggestion!

Attempting to answer the questions for whoever that might find them useful : * line 161,what does “ *float *potarr ” me

@2ROS0 It is called Wavefront expansion algorithm https://en.wikipedia.org/wiki/Wavefront_expansion_algorithm but it ess

It is called Wavefront expansion algorithm https://en.wikipedia.org/wiki/Wavefront_expansion_algorithm but it essentiall

For anyone that could be interested in this in the future, attaching a project of mine I did earlier which visualises De

For anyone that could be interested in this in the future, attaching a project of mine I did earlier which visualises De

For anyone that could be interested in this in the future, attaching a project of mine I did earlier which visualises De

For anyone else who had this problem, reinstalling everything is not necessary, this should solve your problem : Ensur

@isauma How did you solve this problem?

@hitesh Thanks for this code!

Cartographer insists that the tracking frame be co-located at the same place as the IMU frame and gives an error if it d

Hey, just pitching my two cents here, hope this helps. Really wanted to write an answer but a really good answer to

Hello! I am sorry I am really late to this thread but heres how I would do it, I would also love to hear how you ended u

Hello! I am sorry I am really late to this thread but heres how I would do it, I would also love to hear how you ended u

Hello! I am sorry I am really late to this thread but heres how I would do it, I would also love to hear how you ended u

Hello! I am sorry I am really late to this thread but heres how I would do it, I would also love to hear how you ended u

Dear ROS community,

I am using the epos_hardware ROS package as a hardware interface between an effort controller and a EPOS2 motor controller coupled with a Maxon EC90 motor. The set up is working properly and I am able to control the motor using ROS control by sending torque commands to the controller manager. I am trying to interface Simulink with ros_control by sending torque commands directly from the controller in Simulink to ros_control and hence I need real time feedback of the motor's anglular position.

The Problem: This angular position is published by the epos_hardware node on the /diagnostics topic in the diagnostics_msgs/DiagnosticArray message form with the frequency of one message per second. I need atleast 100 or 1000 messages per second and hence I want to increase frequency of the /diagnostics topic.

Solution Attempt: I went through the epos_hardware package and found the snippet of code inside the epos_hardware_node.cpp file which according to me is setting the frequency of the diagnostics topic. :

ros::Rate controller_rate(50);
  ros::Time last = ros::Time::now();
  while (ros::ok()) {
    robot.read();
    ros::Time now = ros::Time::now();
    cm.update(now, now-last);
    robot.write();
    last = now;
    robot.update_diagnostics();
controller_rate.sleep();

I have tried changing the controller_rate but that does not seem to affect the frequency of the topic at all. Am I thinking in the right direction or is there something else I should be looking at? I would like to request anyone who can guide me how to increase frequency of the /diagnostics topic.

P.S. : I have already tried using the Simulink Pacer block to try and reduce the speed of its execution but any further decrease in sampling will affect the controller performance.

Any help would be greatly appreciated! Thanks in advance!

A two step planning approach of global planning and local planning (also called as Hierarchical Planning) is explained w

Alright, then I am afraid this is not a ROS related problem, you could use other forums like stack exchange to get bette

So, out of the top of my head, have you tried using picamera (https://picamera.readthedocs.io/en/release-1.13/) on th

So, out of the top of my head, have you tried using picamera (https://picamera.readthedocs.io/en/release-1.13/) on th

I had a similar issue, px4.launch was executing properly but no heartbeat inspite of the UART serial communication worki

I had a similar issue, px4.launch was executing properly but no heartbeat inspite of the UART serial communication worki

@RayROS I have edited my answer. Hope it helps.

A more appropriate answer to this issue is that, there is a mismatch in timestamps between when the ekf_localization is

A more appropriate answer to this issue is that, there is a mismatch in timestamps between when the ekf_localization is

A more appropriate answer to this issue is that, there is a mismatch in timestamps between when the ek_localization is m

A more appropriate answer to this issue is that, there is a mismatch in timestamps between when the ek_localization is m

@emilyfy I have this exact same problem, where I want the robot_localization to calculate map->odom but it also sho

I have this exact same problem, where I want the robot_localization to calculate map->odom but it also shows me that

I have this exact same problem, where I want the robot_localization to calculate map->odom but it also shows me that

Yes thank you! I have edited my response from Joint State Publisher to Joint State Controller. You are right, second po

Just answering this one, to hopefully help someone in the future. So as far as I remember, the diagnostics topic is not

Just answering this one, to hopefully help someone in the future. So as far as I remember, the diagnostics topic is not

Just answering this one, to hopefully help someone in the future. So as far as I remember, the diagnostics topic is not

Still a great read 7 years later!