MPR121 capacitive touch and Pure Data

Ok, back to Pure Data and knowing how that works :-)
Two questions::

---> I'm trying to find out what pure Data gets from the MPR121 via render.cpp
I managed to print this

 rt_printf("%d ", sensorValue[i]); 

:-D
--> so the MPR121 gives values from 0 (state of not touched) to 110 approximately
I need an object in pd that does not send bangs (like [route] does) but a construction that works with a threshold (when the value is higher than 30, button is pressed, play sound)
Any ideas? - I think I know about an object, but I don't know how it deals with the array of 12 numbers..

---> Render.cpp does not want to print rt_printf("%d ", sensorIndex); (commented out in the following code snippet)
Is this because sensorIndex is just a very local variable?
is it ignored?
Is it a problem (seems not to be the case..)

// Auxiliary task to read the I2C board
void readMPR121(void*)
{
	for(int i = 0; i < NUM_TOUCH_PINS; i++) {
		sensorValue[i] = -(mpr121.filteredData(i) - mpr121.baselineData(i));
		sensorValue[i] -= threshold;
		if(sensorValue[i] < 0)
			sensorValue[i] = 0;
		libpd_float("sensorIndex", (float)i);
		//rt_printf("%d ", sensorIndex[i]); //error: use of undeclared identifier 'sensorIndex'
		libpd_float("sensorValue", (float)sensorValue[i]);
#ifdef DEBUG_MPR121
		rt_printf("%d ", sensorValue[i]); //prints the values of the sensor when DEBUG_MPR121 is define at beginning of programme
#endif
	}
#ifdef DEBUG_MPR121
	rt_printf("\n");
#endif
	
// You can use this to read binary on/off touch state more easily
//rt_printf("Touched: %x\n", mpr121.touched());
}

Full render.cpp file is here:
https://framabin.org/p/?6facff6f6e1a593b#XZ1pyi4ED24QQQ+dUT9aEfZh+IzhXY58XUYzLIHQw8E=

And, thanks - you made my day!
greetz,
dywen

Of course!
But Pure data still sees them as one

They bang together
When I touch the 0 of MPR121 both values get printed - when I touch the 1 of MPR121 it's the same.
I should be able to pour sensorValue into an array (but a pd array is not the same as an array in C..)

dywen

> [r sensorValue]
> |
> [print]

---> Did not give a list

what is your C++ code at this point?
Are you sending this?

	        libpd_start_message(8);
                for(int n = 0; n < 8; ++n)
                    libpd_add_float(sensorValue[n]);
		libpd_finish_list("sensorValue");

IMPORTANT: are you sending something else?

yep, it was in setup, not render.
(I had a - bad - reason for that)

Looking better!

Now it needs serious debouncing - I think
Touching once, briefly, gives 100 bangs (or more - who knows)

----> Too many messages have been printed to the console too quickly. Reduce your printing frequency

ok, better - except that sensor 0 - co-bangs with all sensors
(When I touch 1, 3 or 6 - 0 prints bang as well)

There must be another sensorValue disrupting the flow - I tried to make this render.cpp "cleaner" but I got tons of error messages (and bela stopping)

If someone feels like taking out the midi stuff of this render.cpp and finding two renderings of sensorValue - I would appreciate that
https://framabin.org/p/?5d16d77f039d8958#QYF2tXlzMwCrGdw0525a0wGyhfVgd5f2zpvurT7Hr3E=

pfewww
I'm an autodidact - thanks for your patience Guilormo - it was truly great - I have learnt a lot!

hey,

I have a friend who's a crack at C and he had a look at the code of the render.cpp I had
Here's an outline what he proposed:
in the original code, libpd start message is at the beginning of render:

void render(BelaContext *context, void *userData)
{
	int num;
libpd_start_message(8); //get data from all 8 MPR121 pins
	for(int n = 0; n < 8; ++n)
    	libpd_add_float(sensorValue[n]);
    	
libpd_finish_list("sensorValue");
libpd_finish_message("pd", "dsp");

His proposal:
"Try to combine the 'float' and add_float from with the code in render, and put it at the VERY END of render() but inside render, remove the for loop from readMPR121."

    libpd_start_message(8); //get data from all 8 MPR121 pins
    for(int n = 0; n < 8; ++n){
        libpd_add_float(sensorValue[n]);
    }
    libpd_finish_list("sensorValue");
    libpd_finish_message("pd", "dsp");

   libpd_start_message(8); //get data from all 8 MPR121 pins
    for(int n = 0; n < 8; ++n){
        libpd_add_float((float)n);
    }
    libpd_finish_list("sensorIndex");
    libpd_finish_message("pd", "dsp");

OLD read at the end of render.cpp:

void readMPR121(void*)
{
	for(int i = 0; i < NUM_TOUCH_PINS; i++) {
		sensorValue[i] = -(mpr121.filteredData(i) - mpr121.baselineData(i));
		sensorValue[i] -= threshold;
		if(sensorValue[i] < 0)
			sensorValue[i] = 0;
		libpd_float("sensorIndex", (float)i);
		//rt_printf("%d ", sensorIndex[i]); //error: use of undeclared identifier 'sensorIndex'
		libpd_float("sensorValue", (float)sensorValue[i]);
#ifdef DEBUG_MPR121
		rt_printf("%d ", sensorValue[i]); //prints the values of the sensor when DEBUG_MPR121 is define at beginning of programme
#endif
	}
#ifdef DEBUG_MPR121
	rt_printf("\n");
#endif
	
// You can use this to read binary on/off touch state more easily
//rt_printf("Touched: %x\n", mpr121.touched());

-----> NEW read:

void readMPR121(void*){
    for(int i = 0; i < NUM_TOUCH_PINS; i++) {
        sensorValue[i] = -(mpr121.filteredData(i) - mpr121.baselineData(i));
        sensorValue[i] -= threshold;
        if(sensorValue[i] < 0)
            sensorValue[i] = 0;
#ifdef DEBUG_MPR121
        rt_printf("%d ", sensorValue[i]); //prints the values of the sensor when DEBUG_MPR121 is define at beginning of programme
#endif
    }
#ifdef DEBUG_MPR121
    rt_printf("\n");
#endif
   

// You can use this to read binary on/off touch state more easily
//rt_printf("Touched: %x\n", mpr121.touched());
}

It WORKS!

Also with the little piece of handwoven e-textile (80% polyester, 20%stainless steel)

(image is green because of curtains - heatwave)

Latest render.cpp is here - it desperately needs a clean-up.
https://framabin.org/p/?79ecd118364dce6a#PgFmcFomCItZkIJRkx5azj8hnZuxZs4f76OEgMIOefk=
(you need javascript to decrypt)

End of August - beginning of September I will write about this in full detail and post the project.