The topic isn't very clear but it was hard to put in words in a small sentence.

So i have an Arduino and some analog sensors attached to it for example Flex sensors, and also some Piezos.

I'm using it in Max MSP, but i would like to create a system in the patch so when you open it, it will open some sort of initialization process, which means

That the patch asks you please touch the first piezo and if you do than a toggle/bang sents out and than it asks you to touch the next piezo and so on for other sensors. Maybe an easier example would be:

You open the patch – if you press the space bar for 5 seconds it tells you – HEY, SPACE BAR IS WORKING! And than goes to check the other key. I can change it for my sensors. but perhaps there’s a more elegant solution this.

This is because I want to let other people to use it and want to create some sort of initialization/familiarization before the patch - but i don't know how to go about doing that.

Can anyone direct me to a patch that maybe has the core idea of what I’m trying to do and I’ll apply it to my patch? Or any other good start would be a great help.

Sorry for the messy message, hope you guys get it. Thank You!

So i have an Arduino and some analog sensors attached to it for example Flex sensors, and also some Piezos.
I'm using it in Max MSP, but i would like to create a system in the patch so when you open it, it will open some sort of initialization process, which means
That the patch asks you please touch the first piezo and if you do than a toggle/bang sents out and than it asks you to touch the next piezo and so on for other sensors. Maybe an easier example would be:

You open the patch – if you press the space bar for 5 seconds it tells you – HEY, SPACE BAR IS WORKING! And than goes to check the other key. I can change it for my sensors. but perhaps there’s a more elegant solution  this.

This is because I want to let other people to use it and want to create some sort of initialization/familiarization before the patch - but i don't know how to go about doing that. 

Can anyone direct me to a patch that maybe has the core idea of what I’m trying to do and I’ll apply it to my patch? Or any other good start would be a great help. 

Sorry for the messy message, hope you guys get it. Thank You!


how-to-make-an-initilazation-procedure-in-a-patch-meaning-checking-elements

I pulled that out of my synth's pattr memory. I was going to reorganize it some, but it shows how you can tie every UI attribute to a structured set of logic. Its original purpose was to reset the values of everything nested inside poly~ when I changed the number of voices. Replace the voices pattr with a loadbang and the others with the logic you need. Use the triggers. I would recommend only using one loadbang though. It can get a little hairy debugging when you have a bunch.

I pulled that out of my synth's pattr memory.  I was going to reorganize it some, but it shows how you can tie every UI attribute to a structured set of logic.  Its original purpose was to reset the values of everything nested inside poly~ when I changed the number of voices.  Replace the voices pattr with a loadbang and the others with the logic you need.   Use the triggers.  I would recommend only using one loadbang though.  It can get a little hairy debugging when you have a bunch.


Here's an auto-learn abstraction that I use to calibrate sensors. Not sure it's exactly what you need, but it might give you some ideas. The #1 arguments allow you to name each abstraction and then use that name to store and recall settings. I use a simple coll file to store the settings. The coll file can be loaded on startup so that the initialization only needs to be run when something changes. Hope this helps.

How to make an initilazation procedure in a patch, meaning checking elements?