search

afry-south / dragonfly-fcb

ÅF Dragonfly Quadrotor UAV Project
Other
7 stars 3 forks source link

error handling strategy #47

Open adam-at-epsilon opened 9 years ago

adam-at-epsilon commented 9 years ago

We need an error handling strategy.

For instance, upon errors, we could call an error handler which switches on every red LED among the circular ones, for instance.

stenbergd commented 9 years ago

I think this is done? @adam-at-epsilon

At the very least we indicate error. Probably as the system progresses we would like to handle different errors in different ways.

adam-at-epsilon commented 9 years ago

@DanielStenis you are of course right in that different errors need different handling. Some should be logged to USB, others need corrective action (land immediately) and so forth.

I'd like to keep this issue open as a reminder.

stenbergd commented 9 years ago

You are right. And right now we sometimes seem to end up in the error handler. Perhaps we should print some information. For this, we should use the CDC_Transmit function and somehow bypass the mutex so we can output error data even if the RTOS/system state has failed.

adam-at-epsilon commented 9 years ago

just an idea: in an error condition, we should repeatedly try to print every 5 seconds or so to USB so that when (or if) we attach the USB cable, FCB will immediately print a status report.