From 8e5091703ce43c3f262b864f99aee4a903ea5682 Mon Sep 17 00:00:00 2001 From: Julian Oes Date: Thu, 21 Apr 2016 16:56:37 +0200 Subject: [PATCH] commander: no message due to LED/buzzer not found The LED init and Buzzer init messages were only annoying and not helpful on Snapdragon and SITL. Therefore they are replaced with only developer printfs. --- src/modules/commander/commander.cpp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/modules/commander/commander.cpp b/src/modules/commander/commander.cpp index f6e084bd55..964927af69 100644 --- a/src/modules/commander/commander.cpp +++ b/src/modules/commander/commander.cpp @@ -1216,11 +1216,11 @@ int commander_thread_main(int argc, char *argv[]) /* initialize */ if (led_init() != OK) { - mavlink_and_console_log_critical(&mavlink_log_pub, "ERROR: LED INIT FAIL"); + PX4_WARN("LED init failed"); } if (buzzer_init() != OK) { - mavlink_and_console_log_critical(&mavlink_log_pub, "ERROR: BUZZER INIT FAIL"); + PX4_WARN("Buzzer init failed"); } /* vehicle status topic */