I'm running simple patch using Pi2 - I'm reading data from on button using arduino

After a while patch is stuck and data is not pass from the comport to the rest of the patch.

Any idea what can it be? I don't think patch is High in CPU usage

@whale-av Thank you very much David. I put [time-gate 2] and for the moment it all work without stucking. I'll run it for few hours and will see if it really helps. Seems good for the moment

btw - I'm getting a popup message of i/o error and I think is because the audio dialog choose a inputdevice that doesn't really exist(?)
Is it possible to untick the audio input device via thr [audio-dialog] message i'm banging when patch is first loaded, so it will not be choose?

some updates:
I came back to the pi after two hours and press the button. Patch is stacked again...
so perhaps it was not the multiple bangs from the right outlet the sf-play~ causing the problem. Any idea what can I try else?

Pressing manually after patch was stacked

some extra update: i noticed that after patch is stacked - when I un-tick and tick again the DSP message in the pd console the patch is back to work and all the messages are printed again. it might be an issue with the builtin output the is crashing??

@KMETE Alsa input error (snd_pcm_open) no such file or directory.... is normal..... as the RPI doesn't have an audio input. You should change the message at the top of the patch to.......
[audio-dialog 0 0 0 0 0 0 0 0 $1 0 0 0 2 0 0 0 44100 25 -1 64(
That will deselect audio input in the Pd audio settings.
Whether that will solve the sticking problem I don't know..... it might.

You seem to now know for sure that audio is stopping.
I will wait for you to find out whether changing the message solves the problem.
David.

@whale-av I connected small usb dongle audio card and for the moment it seems very stable. Not freezing. I get the feeling that indeed it was the built-in headphones output of the pi2B that is not so good apparently.

After many hours of pi running I can confirm the issue was caused by the built-in audio output. Adding the dongle USB audio interface indeed solved it.

@KMETE Excellent news.
David.