Attention: Answers.ros.org is deprecated as of August the 11th, 2023. Please visit robotics.stackexchange.com to ask a new question. This site will remain online in read-only mode during the transition and into the foreseeable future. Selected questions and answers have been migrated, and redirects have been put in place to direct users to the corresponding questions on Robotics Stack Exchange. Additional details are available here.

Ros diagnostics aggregator, faster stale

asked 2020-09-25 06:59:04 -0500

Mackou

196 ●37 ●55 ●50

Hello, I have noticed that ros diagnostics aggregator report that a node is "stale" after 5s without any diagnostics messages. Is there a way to reduce it to 2 or 3 seconds ? I think this value should not be hard coded anyway !

Thanks !

edit retag flag offensive close merge delete

add a comment

1 Answer

Sort by » oldest newest most voted

answered 2020-09-25 08:08:43 -0500

Mackou

196 ●37 ●55 ●50

Answering my own question, Using the timeout parameter in the configuration of the analyzer works fine :

Example :

  sensors:
    type: AnalyzerGroup
    path: Sensors
    analyzers:
      base_hk:
        type: GenericAnalyzer
        path: Base Hokuyo
        timeout: 5.0
        find_and_remove_prefix: base_hokuyo_node
        num_items: 3
      tilt_hk:
        type: GenericAnalyzer
        path: Tilt Hokuyo
        timeout: 5.0
        find_and_remove_prefix: tilt_hokuyo_node
        num_items: 3
      imu:
        type: GenericAnalyzer
        path: IMU
        timeout: 5.0
        find_and_remove_prefix: imu_node
        num_items: 3

edit flag offensive delete link

add a comment

Question Tools

1 follower

Stats

Asked: 2020-09-25 06:59:04 -0500

Seen: 617 times

Last updated: Sep 25 '20

Ros diagnostics aggregator, faster stale edit

1 Answer

Question Tools

Stats

Related questions

Ros diagnostics aggregator, faster stale