Skip navigation

Arduino

3 Posts authored by: cloudformdesign
Everything that happens on a micro-controller has to be known. This includes dealing with memory. Many people (myself included) have developed a wonderful set of code that can dynamically use and free memory through the standard malloc and free functions. Only later do we discover that our available memory is getting reduced as time goes by -- followed by undetermined and random failures.   This is because no microcontroller (the Arduino included) has the ability to garbage collect.   ...
User interfaces can take up a lot of memory. That is why, while developing the Arduino User Interface I focused on developing a way to store things in Program Memory instead. It turns out that storing -- and then using -- program memory objects can be slightly confusing. So I thought I would write a quick post about it.   Most people are familiar with the simple use of program memory for strings. Instead of writing   Serial.println("This is taking up a lot of mem"); &# ...
One of my first big micro-controller projects was called the Neonatal Closed Loop Oxygen System. When babies are born prematurely, they have to be fed very specific amounts of oxygen. Too little oxygen and they suffocate, too much oxygen and they can die from oxygen toxicity. Current methods are not advanced, essentially involving a nurse adjusting the oxygen levels manually. The goal of the project was to develop an automatic system.   We had to prevent this little guy from getting oxygen ...

Filter Blog

By date: By tag: