Sorry for not clarifying - I mean that the program stops producing an output, while running the BBB/Bela in standalone mode.
I tested the CPU usage of the Pd patch in the IDE, but the rest of the time I'm powering the BBB/Bela from an RS power bank.
To describe the setup: The Bela receives 3 analog inputs, processes them in a Pd patch (which, when tested in the IDE, uses 48-51% of CPU) and outputs audio to an amplifier.
The BBB/Bela is housed in a ventilated plastic container, within a larger flight case; the container leaves plenty of 'breathing room' for the BBB/Bela, and the flight case in turn leaves plenty of 'breathing room' for the container.
I run the setup for around 2 hours at a time. Sometimes, the program will stop responding - that is, it just won't produce any output. This happens often after 1hr of use, and less often after a shorter period of use.
To remedy the problem, I'll usually power down the Bela (using a switch attached to GND/Pin P9-27), then restart. Usually this solves this problem, and I can continue running the program for another hour or so. Occasionally though, the program will crash 3 times or more, and I'll have to quit.
I've noticed that 'crashes' have happened more frequently on warmer days. However, ruling out the environment, is there a 'safe' maximum threshold for CPU usage that will allow me to run a program for 6+ hours a day, in normal conditions? Or am I missing something, and I should turn my attention to another potential cause of this problem?
Thanks again!