It is not showing any error when the set frequency is not satisfied

[danielrr7]

Hi there!

First of all, I just wanted to say that this tool looks really promising. I’ve been testing it a bit and it looks really nice.

While trying it out, I ran into something that I think might be an issue (or maybe I’m just missing something 😅).
It doesn’t seem to show any error when the set frequency isn’t being met:

(using commit 0f35afb)

Side note / small suggestion:

It could be nice to have some kind of configuration file for the ncurses dashboard, so it can start already tracking the desired topics.
It might also be useful to support namespaces, so the same config file can be reused across different robots or instances.

For example, in another node I’m using a similar setup via a ROS2 YAML file:

Where:

• If the topic starts with /, it ignores the node namespace.
• If it doesn’t, it takes the node namespace (same as ROS2 subscriptions by default).

Just an idea that might make it even more flexible 🙂

This is just a brainstorming. Anyways, it’s really cool to see tools like this being developed.

[sgillen]

Thank you for the report. There is a bug where the expected frequency will not work for topics that don't have headers, I'll work on a fix when I'm free.

The config is a good idea, if you want you can today integrate greenwave into your launch files with topics and expected frequencies configured. And even better you can use messaage_diagnostics.hpp to compute and publish diagnostics directly in your node, then they will show up in the frontend without the monitor node.

[sgillen]

@danielrr7 I moved your configuration suggestion into it's own issue: #19