Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The sensor data updates really slow #137

Closed
yhan33 opened this issue Nov 13, 2020 · 7 comments
Closed

The sensor data updates really slow #137

yhan33 opened this issue Nov 13, 2020 · 7 comments
Labels

Comments

@yhan33
Copy link

yhan33 commented Nov 13, 2020

Hi, I successfully connected my Nao H25 V5 using naoqi_driver. However, as I rostopic echo /joint states, the data updated very slow for some reason. Can I get some help here?

Thanks

@mbusy
Copy link
Member

mbusy commented Nov 13, 2020

Hi @yhan33, could you specify what you mean by "really slow" in terms of frequency? Also, I assume that naoqi_driver is running on your computer, how are your computer and your robot connected to the network (WiFi or Ethernet) ?

@mbusy mbusy added the question label Nov 13, 2020
@yhan33
Copy link
Author

yhan33 commented Nov 13, 2020

Thanks for the reply.

I am using NAO H25 V5. The robot connects to the PC via Ethernet.

I have a couple problems and one of them are mentioned in the previous issues.

  1. There is always an error when I launch the node, as shown in the following picture
    image

2)After roslaunch, I did "rostopic echo/joint_states". It seems the hand joint angle measurements are not included since the hand joint angles are "nan", as shown in the following picture
image

  1. "Really slow" means the scanning frequency of the topic joint_state is very low. I looked into the naoqi_driver.cpp file and it shows that the joint_states frequency is 20 Hz (as shown in the follow picture). I think I only get less than 5 Hz.
    image

Thanks again for your help.

@mbusy
Copy link
Member

mbusy commented Nov 16, 2020

So if I understand correctly, the robot is directly connected to the computer through Ethernet then ?

Regarding the first two issue:

  1. That's indeed a known bug (check here), but it shouldn't prevent you from doing what you're trying to achieve
  2. That is actually normal, as the "hand joints" are different from the other revolute joints of the robot. The hand joints position will be a value between 0 and 1 (corresponding to a percentage of hand opening/closing). The velocity of that "joint" and its effort are not computed, hence resulting in a nan in the joint_states message

Regarding your third point, that's strange, it should be faster. First, make sure that you also have 20Hz in the share/boot_config.json file. Then, are you running things in parallel on your computer / on the robot ?

@yhan33
Copy link
Author

yhan33 commented Feb 9, 2021

So if I understand correctly, the robot is directly connected to the computer through Ethernet then ?

Regarding the first two issue:

  1. That's indeed a known bug (check here), but it shouldn't prevent you from doing what you're trying to achieve
  2. That is actually normal, as the "hand joints" are different from the other revolute joints of the robot. The hand joints position will be a value between 0 and 1 (corresponding to a percentage of hand opening/closing). The velocity of that "joint" and its effort are not computed, hence resulting in a nan in the joint_states message

Regarding your third point, that's strange, it should be faster. First, make sure that you also have 20Hz in the share/boot_config.json file.

Thanks for your reply.
I have changed the joint_state rate in boot_config.json file (see attached the snapshot)
Screenshot from 2021-02-08 20-19-11

It seems the maximum frequency is always 13.3Hz (see the snapshot)
Screenshot from 2021-02-08 20-21-16

Then, are you running things in parallel on your computer / on the robot ?

No, I am only running the naoqi_driver to read the sensor data from the robot

Can you please point out if I can change anywhere else to get around 50 Hz sensor frequency?

Thanks

@mbusy
Copy link
Member

mbusy commented Feb 11, 2021

Unfortunately, you won't be able to get a better frequency than what you already have... Less than 5Hz seemed really low, but that frequency seems correct

@yhan33
Copy link
Author

yhan33 commented Feb 11, 2021

Anyway. Thanks for your kind help!

@mbusy
Copy link
Member

mbusy commented Feb 11, 2021

@yhan33 You're welcome!

@mbusy mbusy closed this as completed Feb 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants