{"action":"created","issue":{"url":"https://api.github.com/repos/betaflight/betaflight/issues/3088","repository_url":"https://api.github.com/repos/betaflight/betaflight","labels_url":"https://api.github.com/repos/betaflight/betaflight/issues/3088/labels{/name}","comments_url":"https://api.github.com/repos/betaflight/betaflight/issues/3088/comments","events_url":"https://api.github.com/repos/betaflight/betaflight/issues/3088/events","html_url":"https://github.com/betaflight/betaflight/issues/3088","id":228553732,"number":3088,"title":"Full SD Card causing loss of control: Omnibus F4 V3","user":{"login":"MiddleMan5","id":12738069,"avatar_url":"https://avatars0.githubusercontent.com/u/12738069?v=3","gravatar_id":"","url":"https://api.github.com/users/MiddleMan5","html_url":"https://github.com/MiddleMan5","followers_url":"https://api.github.com/users/MiddleMan5/followers","following_url":"https://api.github.com/users/MiddleMan5/following{/other_user}","gists_url":"https://api.github.com/users/MiddleMan5/gists{/gist_id}","starred_url":"https://api.github.com/users/MiddleMan5/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/MiddleMan5/subscriptions","organizations_url":"https://api.github.com/users/MiddleMan5/orgs","repos_url":"https://api.github.com/users/MiddleMan5/repos","events_url":"https://api.github.com/users/MiddleMan5/events{/privacy}","received_events_url":"https://api.github.com/users/MiddleMan5/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2017-05-14T16:54:03Z","updated_at":"2017-05-14T21:11:12Z","closed_at":null,"body":"_Pertinent info:\r\nBoard: [Omnibus F4 V3 ](http://www.readytoflyquads.com/flip-32---f4---omnibus-v3)\r\nBetaflight 3.1.6\r\n2GB SD Card formatted FAT with 32KB allocation units\r\nESC comm: DSHOT 600\r\nFRsky SBUS receiver_\r\n\r\nOkay, so this is a strange one, I think I've been having these issues for awhile now, but never chalked it up to be the SD Card.\r\n It doesn't help that every time I had one of these lockups my craft would smash into something hard and break something, leading me away from the real issue. \r\n\r\nWhen the SD card in my quad is full, I get sporadic operation.\r\n\r\nTroubleshooting:\r\n- RSSI values stay green the entire flight, current draw and voltage levels all within nominal range.\r\n- Cleared SD card, flies fine\r\n\r\nSymptoms: \r\n\r\n- Craft will periodically boot up but not initialize ESCs (no startup beacon) \r\n- Craft will fly for a short amount of time (30 sec) then lock up (air-mode still engaged, motors still running) and fall out of the sky\r\n- Black-box logs will show multiple empty files (can we please fix the time-stamps on these!!)\r\n\r\nReplication:\r\nThis is the fricking tricky part, I have no real way to reproduce these consistently, nor is there functionality (that I know of) to diagnose these issues. \r\n\r\n- Place a full sdcard in omnibus\r\n- plug battery in\r\n- fly and hope\r\n\r\nBut to say clearing the card is a fix isn't the whole truth, sure it fixes the symptoms of an overloaded card, but betaflight should never prioritize SD card communication over actual operation, there's a bug in the code here somewhere."},"comment":{"url":"https://api.github.com/repos/betaflight/betaflight/issues/comments/301340249","html_url":"https://github.com/betaflight/betaflight/issues/3088#issuecomment-301340249","issue_url":"https://api.github.com/repos/betaflight/betaflight/issues/3088","id":301340249,"user":{"login":"MiddleMan5","id":12738069,"avatar_url":"https://avatars0.githubusercontent.com/u/12738069?v=3","gravatar_id":"","url":"https://api.github.com/users/MiddleMan5","html_url":"https://github.com/MiddleMan5","followers_url":"https://api.github.com/users/MiddleMan5/followers","following_url":"https://api.github.com/users/MiddleMan5/following{/other_user}","gists_url":"https://api.github.com/users/MiddleMan5/gists{/gist_id}","starred_url":"https://api.github.com/users/MiddleMan5/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/MiddleMan5/subscriptions","organizations_url":"https://api.github.com/users/MiddleMan5/orgs","repos_url":"https://api.github.com/users/MiddleMan5/repos","events_url":"https://api.github.com/users/MiddleMan5/events{/privacy}","received_events_url":"https://api.github.com/users/MiddleMan5/received_events","type":"User","site_admin":false},"created_at":"2017-05-14T21:11:12Z","updated_at":"2017-05-14T21:11:12Z","body":"Maybe a feature switch, because personally I'd rather it start overwriting earlier logs and give me feedback on my latest flight. An OSD value might be handy to warn the user of an overflow.\r\nIf FREESPAC.E is used to allocate write memory, can't you check FREESPAC.E is not below some critical value, if it is check user options for halt/overwrite, choose lowest value log file (assuming it wasn't edited by the user) and add it's memory map to the FREESPAC.E file?"}}
{"actor":{"display_login":"MiddleMan5"}}