NodeStatus extended with a 32-bit vendor-specific status code

dsdl/uavcan/protocol/550.NodeStatus.uavcan

@@ -1,6 +1,9 @@
 #
 # Abstract node status information.
 # Any UAVCAN node is required to publish this message periodically.
+# It is NOT recommended to change its publication rate at run time.
+#
+# See http://uavcan.org/Standard_data_types_and_application_level_functions
 #
 
 uint16 MAX_PUBLICATION_PERIOD_MS = 1000
@@ -13,9 +16,6 @@ uint16 OFFLINE_TIMEOUT_MS = 3000
 uint28 uptime_sec
 
 # Status code should be used to reflect the node status in the most abstract way.
-# Use cases: top-level onboard computer should not allow the UAV to begin normal operation
-# unless all nodes report OK. If a mission critical node reports CRITICAL status, current
-# mission should be immediately yet safely aborted (e.g. RTL).
 # OFFLINE status can be actually reported by the node to explicitly inform other network
 # participants that the sending node is about to shutdown. In this case other nodes will not
 # have to wait OFFLINE_TIMEOUT_MS before they detect that the node is no longer available.
@@ -25,3 +25,6 @@ uint4 STATUS_WARNING      = 2
 uint4 STATUS_CRITICAL     = 3
 uint4 STATUS_OFFLINE      = 15
 uint4 status_code
+
+# Optional, vendor-specific node status code, e.g. a fault code or a status bitmask.
+uint32 vendor_specific_status_code