{"_id":"58a1eb7c76d9fb25004afc76","__v":0,"project":"56835bb57af9120d007ac339","user":"56835b733b87430d00483b77","version":{"_id":"58a1eb7b76d9fb25004afc6d","project":"56835bb57af9120d007ac339","__v":1,"createdAt":"2017-02-13T17:23:07.814Z","releaseDate":"2017-02-13T17:23:07.814Z","categories":["58a1eb7b76d9fb25004afc6e","58a1eb7b76d9fb25004afc6f","58a1eb7b76d9fb25004afc70","58a1eb7b76d9fb25004afc71"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"Artifice","version_clean":"20170213.0.0","version":"20170213"},"category":{"_id":"58a1eb7b76d9fb25004afc6e","version":"58a1eb7b76d9fb25004afc6d","project":"56835bb57af9120d007ac339","__v":0,"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2016-04-05T03:18:16.877Z","from_sync":false,"order":0,"slug":"initial-setup","title":"Initial Setup"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-10-02T21:30:09.751Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":4,"body":"# This documentation is superseded.  dRonin Documentation is now on http://dronin.org/docs/\n\nThe October 2016 (\"Quixote\") release of dRonin introduced a new \"annunciator\" subsystem used to blink LEDs and control buzzers.\n\nBy default, all alarms blink on the \"heartbeat\" LED if the hardware has one.  Everything of severity \"warning\" or worse blinks on the \"alarm\" LED as well.  Finally, alarms having to do with the radio subsystem beep through an attached buzzer on supported hardware, but only after arming has taken place (this avoids nuisance alarm beeps on powerup).\n\nThe following are the blink codes supported by the hardware:\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Sequence\",\n    \"h-1\": \"Meaning\",\n    \"1-0\": \"**•• , •• , •• **  …\",\n    \"6-0\": \"** •— , •— , •— ** ...\",\n    \"1-1\": \"Normal *(armed)*\",\n    \"0-0\": \"**— , — , — ** …\",\n    \"0-1\": \"Normal *(disarmed)*\",\n    \"2-0\": \"**•—• , •—• , •—• **  …\",\n    \"2-1\": \"No connection to radio *(failsafe)*\",\n    \"3-0\": \"**—••• , —••• , —••• ** …\",\n    \"3-1\": \"Battery status alarm\",\n    \"4-0\": \"**—•—• , —•—• , —•—• ** …\",\n    \"4-1\": \"System configuration issue-- attempting to arm in illegal mode (like AutoTune) or flight modes configured without associated module running\",\n    \"5-0\": \"** ——• , ——• , ——• **  …\",\n    \"5-1\": \"GPS alarm\",\n    \"6-1\": \"Other alarm not otherwise specified (connect GCS)\"\n  },\n  \"cols\": 2,\n  \"rows\": 7\n}\n[/block]\n\n[block:callout]\n{\n  \"type\": \"warning\",\n  \"title\": \"Adjusting alarm destinations\",\n  \"body\": \"There is not formal support in the UI, but alarm-to-annunciator routing can be altered by going into the UAVO browser on the GCS system pane and altering the values in Settings → AnnunciatorSettings .\"\n}\n[/block]\nThere are also panic codes that happen at startup.  For these, generally only the error LED will blink.  They are repeated three times and then the flight controller reboots.  These usually indicate a hardware problem:\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Sequence\",\n    \"h-1\": \"Meaning\",\n    \"0-0\": \"2 blinks ( ** •• ** )\",\n    \"0-1\": \"Failed to communicate with gyro\",\n    \"1-0\": \"3 blinks ( ** ••• ** )\",\n    \"1-1\": \"Failed to communicate with magnetometer (compass)\",\n    \"2-0\": \"4 blinks ( ** •••• ** )\",\n    \"2-1\": \"Failed to communicate with barometer (altimeter)\",\n    \"3-0\": \"5 blinks ( ** ••••• ** ) or 6 blinks ( ** •••••• ** )\",\n    \"3-1\": \"Flash chip or flash filesystem problem\",\n    \"4-0\": \"7 blinks ( ** ••••••• ** ) or 8 blinks ( ** •••••••• **)\",\n    \"4-1\": \"Problems with I2C (internal or external)\",\n    \"5-0\": \"9 blinks ( ** ••••••••• **)\",\n    \"5-1\": \"Failure to communicate via SPI\",\n    \"6-0\": \"10 blinks ( ** •••••••••• **)\",\n    \"6-1\": \"Failure to communicate via CAN\",\n    \"7-0\": \"11 blinks ( ** ••••••••••• ** )\",\n    \"7-1\": \"Failed to initialize ADC\",\n    \"8-0\": \"12 blinks ( ** •••••••••••• ** )\",\n    \"8-1\": \"Failed to initialize On-Screen Display\"\n  },\n  \"cols\": 2,\n  \"rows\": 9\n}\n[/block]","excerpt":"DiDahDit","slug":"blink-beep-codes","type":"basic","title":"Blink & Beep Codes"}

Blink & Beep Codes

DiDahDit

# This documentation is superseded. dRonin Documentation is now on http://dronin.org/docs/ The October 2016 ("Quixote") release of dRonin introduced a new "annunciator" subsystem used to blink LEDs and control buzzers. By default, all alarms blink on the "heartbeat" LED if the hardware has one. Everything of severity "warning" or worse blinks on the "alarm" LED as well. Finally, alarms having to do with the radio subsystem beep through an attached buzzer on supported hardware, but only after arming has taken place (this avoids nuisance alarm beeps on powerup). The following are the blink codes supported by the hardware: [block:parameters] { "data": { "h-0": "Sequence", "h-1": "Meaning", "1-0": "**•• , •• , •• ** …", "6-0": "** •— , •— , •— ** ...", "1-1": "Normal *(armed)*", "0-0": "**— , — , — ** …", "0-1": "Normal *(disarmed)*", "2-0": "**•—• , •—• , •—• ** …", "2-1": "No connection to radio *(failsafe)*", "3-0": "**—••• , —••• , —••• ** …", "3-1": "Battery status alarm", "4-0": "**—•—• , —•—• , —•—• ** …", "4-1": "System configuration issue-- attempting to arm in illegal mode (like AutoTune) or flight modes configured without associated module running", "5-0": "** ——• , ——• , ——• ** …", "5-1": "GPS alarm", "6-1": "Other alarm not otherwise specified (connect GCS)" }, "cols": 2, "rows": 7 } [/block] [block:callout] { "type": "warning", "title": "Adjusting alarm destinations", "body": "There is not formal support in the UI, but alarm-to-annunciator routing can be altered by going into the UAVO browser on the GCS system pane and altering the values in Settings → AnnunciatorSettings ." } [/block] There are also panic codes that happen at startup. For these, generally only the error LED will blink. They are repeated three times and then the flight controller reboots. These usually indicate a hardware problem: [block:parameters] { "data": { "h-0": "Sequence", "h-1": "Meaning", "0-0": "2 blinks ( ** •• ** )", "0-1": "Failed to communicate with gyro", "1-0": "3 blinks ( ** ••• ** )", "1-1": "Failed to communicate with magnetometer (compass)", "2-0": "4 blinks ( ** •••• ** )", "2-1": "Failed to communicate with barometer (altimeter)", "3-0": "5 blinks ( ** ••••• ** ) or 6 blinks ( ** •••••• ** )", "3-1": "Flash chip or flash filesystem problem", "4-0": "7 blinks ( ** ••••••• ** ) or 8 blinks ( ** •••••••• **)", "4-1": "Problems with I2C (internal or external)", "5-0": "9 blinks ( ** ••••••••• **)", "5-1": "Failure to communicate via SPI", "6-0": "10 blinks ( ** •••••••••• **)", "6-1": "Failure to communicate via CAN", "7-0": "11 blinks ( ** ••••••••••• ** )", "7-1": "Failed to initialize ADC", "8-0": "12 blinks ( ** •••••••••••• ** )", "8-1": "Failed to initialize On-Screen Display" }, "cols": 2, "rows": 9 } [/block]