From 3835e8cd79e0698b0953e43b707bfbc8fd2b9d27 Mon Sep 17 00:00:00 2001
From: Paul Riseborough <p_riseborough@live.com.au>
Date: Tue, 22 Nov 2016 07:59:46 +1100
Subject: [PATCH] msg: improve multirotor_motor_limits reporting

---
 msg/multirotor_motor_limits.msg | 15 +++++++++++----
 1 file changed, 11 insertions(+), 4 deletions(-)

diff --git a/msg/multirotor_motor_limits.msg b/msg/multirotor_motor_limits.msg
index 2e03afc040..92b8e5a1ff 100644
--- a/msg/multirotor_motor_limits.msg
+++ b/msg/multirotor_motor_limits.msg
@@ -1,4 +1,11 @@
-uint8 lower_limit	# at least one actuator command has saturated on the lower limit
-uint8 upper_limit	# at least one actuator command has saturated on the upper limit
-uint8 yaw		# yaw limit reached
-uint8 reserved		# reserved
+uint16 saturation_status	# Integer bit mask indicating which axes in the control mixer are saturated
+# 0 - True if any motor is saturated at the upper limit
+# 1 - True if any motor is saturated at the lower limit
+# 2 - True if a positive roll increment will increase motor saturation
+# 3 - True if negative roll increment will increase motor saturation
+# 4 - True if positive pitch increment will increase motor saturation
+# 5 - True if negative pitch increment will increase motor saturation
+# 6 - True if positive yaw increment will increase motor saturation
+# 7 - True if negative yaw increment will increase motor saturation
+# 8 - True if positive thrust increment will increase motor saturation
+# 9 - True if negative thrust increment will increase motor saturation
-- 
GitLab