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

Is there an possibility to have an higher publish rate than the fps #140

Open
LukasD97 opened this issue Apr 10, 2024 · 16 comments
Open

Is there an possibility to have an higher publish rate than the fps #140

LukasD97 opened this issue Apr 10, 2024 · 16 comments

Comments

@LukasD97
Copy link

Currently it seems like the maximum Publish rate of an Node is bound to the frame rate.
Is there an option to allow higher pub rates?

@yuokamoto
Copy link
Contributor

Currently there is no option to pub since it does not make sense update information higher than simulation update.
Are there any use case to publish higher than frame rate?

@james-yoo
Copy link
Contributor

Generally IMU sensor publish acceleration and gyro in high frequency(200hz, 400hz).

@yuokamoto
Copy link
Contributor

hmm, I see
but since it is higher than frame rate(higher than simulation world state update), it will result in publishing same contents in same frame.
By customizing publisher, it can be possible to publish multiple times in one frame but not sure it make sense or not

@LukasD97
Copy link
Author

It makes sense to me because another plugin delivers data at a much higher rate.
Is this an easy or difficult thing to achieve?

@yuokamoto
Copy link
Contributor

@LukasD97
Copy link
Author

jsbsim plugin for flight simulation.
Is this also possible in the blueprint, my project is build with blueprints?

@yuokamoto
Copy link
Contributor

@LukasD97
Copy link
Author

Hi, i didn't got it to work with an higher frequency only 60 possible altered tick and frame rate. Any other suggestions?

@yuokamoto
Copy link
Contributor

What do you mean only 60 possible? Some param's maximum is 60 or simulation run with 60 hz because of CPU/GPU limitation?

@LukasD97
Copy link
Author

60 hz publish rate, cpu and gpu arent an limitation. 60 fps is ok for me, i only want to publish at an higher rate

@yuokamoto
Copy link
Contributor

Where do you set 60hz?
you can publish as many times as you want by call Publish in your tick

@LukasD97
Copy link
Author

I've set 240 hz in the publishers. But they're only publishing with 60 hz

@yuokamoto
Copy link
Contributor

maximum Publish rate of an Node is bound to the frame rate as you mentioned.

You need to create non loop publisher and manually call Publish() from your bp to meet your requirements.
https://rclue.readthedocs.io/en/devel/examples/publisher_example.html#id1

@Zartris
Copy link

Zartris commented Feb 15, 2025

Sorry to join the conversation out of nowhere. Where do we see this limit today exactly?
Is it the publisher class that is bound by the framerate, because i cannot seem to find something pointing to this.
Is it the ROS2_LOOP_PUBLISHER_WITH_QOS that only runs doing update calls?

@LukasD97
Copy link
Author

The Non loop publisher has no limit. The Jsbsim plugin is only updating its data at 60 hz so it's the limitng factor.

@Zartris
Copy link

Zartris commented Feb 16, 2025

Ah so another plugin is the bottleneck, got it! I also thought it was weird as I did not see any problem in your code, both in the sensor and publisher side.

I guess it is time to just install it and get a feel for it myself 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants