How to set up the Vibration Graph via defining an Acceleration Port 1, 2, or 3

Jason_S · February 23, 2023, 1:58am

Screenshot 2023-02-22 174821
I would like to see the vibration graph working, however, It does not display any data.
Only stating:
“Clip count”
“Accel 1: undefined.”
“Accel 2: undefined.”
“Accel 3: undefined.”

This menu is located in the Analyze Tools tab in the QGroundControl software. I am using a Px4 6c with the HolyBro 2015 edition, S500 Drone kit.

JulianOes · February 23, 2023, 10:33pm

What PX4 version are you using? Have you updated to latest stable v1.13.2?

Jason_S · February 23, 2023, 11:37pm

If you are talking about firmware, it is recent enough.

JulianOes · March 5, 2023, 10:53pm

Well that sounds good then. (I’m giving a vague answer to your vague answer )

bayetan · March 14, 2023, 2:11pm

I’m runngin qGroundControl v4.2.4 and FC 1.13.2 and I have the same problem. I do have good data in MAVLink Inspector (VIBRATION) at 2-3 Hz though.

Jason_S · March 14, 2023, 3:08pm

Sorry for my vague answers. I wasn’t sure what exactly was being updated. For the firmware update I just clicked update, thinking it would automatically retrieve the newest stable version to install.

JulianOes · March 14, 2023, 8:47pm

In QGC? Ok, so that’s presumably v1.13.2 or v.13.3, so fine.

I wonder if some messages containing the clip count are meant to be sent but are not actually sent by default, presumably the VIBRATION message.

According to the source the message should be sent every 10 seconds on a normal (e.g. SiK radio) link:

github.com

PX4/PX4-Autopilot/blob/release/1.13/src/modules/mavlink/mavlink_main.cpp#L1526


      
          		configure_stream_local("ORBIT_EXECUTION_STATUS", 2.0f);
          		configure_stream_local("PING", 0.1f);
          		configure_stream_local("POSITION_TARGET_GLOBAL_INT", 1.0f);
          		configure_stream_local("POSITION_TARGET_LOCAL_NED", 1.5f);
          		configure_stream_local("RAW_RPM", 2.0f);
          		configure_stream_local("RC_CHANNELS", 5.0f);
          		configure_stream_local("SERVO_OUTPUT_RAW_0", 1.0f);
          		configure_stream_local("SYS_STATUS", 1.0f);
          		configure_stream_local("UTM_GLOBAL_POSITION", 0.5f);
          		configure_stream_local("VFR_HUD", 4.0f);
          		configure_stream_local("VIBRATION", 0.1f);
          		configure_stream_local("WIND_COV", 0.5f);
          
          
#if !defined(CONSTRAINED_FLASH)
          		configure_stream_local("DEBUG", 1.0f);
          		configure_stream_local("DEBUG_FLOAT_ARRAY", 1.0f);
          		configure_stream_local("DEBUG_VECT", 1.0f);
          		configure_stream_local("NAMED_VALUE_FLOAT", 1.0f);
          		configure_stream_local("LINK_NODE_STATUS", 1.0f);
          #endif // !CONSTRAINED_FLASH

So then the question is whether it is not published at all? I need to debug this in-depth.

Another way to check clipping is to check the clipping output in the ulg file, just FYI.

JulianOes · March 30, 2023, 7:50pm

I had a closer look and this looks like a QGC issue to me.

The VIBRATION message is being sent with clipping_0, clipping_1, and clipping_2 populated, however, the vibration tab just shows “undefined”.

I created a QGC issue: Clipping count not shown in Vibration tab · Issue #10650 · mavlink/qgroundcontrol · GitHub

Jason_S · March 30, 2023, 10:20pm

Thank you! Please keep me updated when a QGC stable version with vibration statistics is released. I also have questions about programming a servo motor and what cameras you would recommend. Please let me know when you’re available to message.
Thank you for your time and sorry for the late replies.

JulianOes · March 31, 2023, 7:59pm

No worries, you’re welcome

I’m not available for one to one help at this point, sorry. However, I always suggest to just ask questions in public here in the forum, and who ever has an answer, can post it.