adanlbenito Hey, super, Thanks! Took me some time to get back to this thread, so my answer comes a bit late..
I'm a Linux user - Kicad it is!! Impressive software..
dywen

- Jul 6, 2020
- Joined May 15, 2018
- 8 discussions
- 84 posts
adanlbenito So, i think my more concrete question is::: can i pretty please have your Bela Mini footprint and symbol for Kicad
- Edited
Hi adanlbenito I am interested in the Bela Mini footprint and symbol for Kicad! The only thing I have to solve if I use the mini instead of the bigger Bela, is the MicBias - but that should not be too hard..
Hi,
I want to add some sensor electronics to Bela and it would be pretty great to have a 'blank' bela Capelet on top of the Bela Cape to be able to make the design in Kicad. Is this available somewhere? I know about some capelets made for the Bela Mini ( https://github.com/BelaPlatform/embelashed-hardware/tree/master/Capelets ), but I want to have one for Bela, as I use the Mic Bias.
Thanks!Works like a charm. Soooooo nice to end my work morning (I have to take care of a lovely almost 4 year old, other parent starts working after lunch)
giuliomoro hey, yes, it is a totally neat feature, this would give the switch chip potential theremin like features, gradual because it has to reset, but perhaps workable with bit detoriation for example.
Super!
giuliomoro
I know DAC as Digital to analog conversion in sound (sample rate 44100 hz, bit depth etc)
I have to confess that DAC in this option I did not understand.
--> SO if I connect to Bela with the Bela digital out and the 10K, what does Bela, hence Pure Data send?- Edited
giuliomoro An interesting application mentioned in the datasheet is that if you need programmable trimming of the voltage into MTSA, you could use one of Bela's analog outs instead of a resistor divider.
I know, it's with PWM, I believe. I chose the voltage dividers, because I have to figure out PWM with Pure Data...
London - cool, I'm listening to the Resonance fm Mixcloud now
- Edited
Remork Perfect - confirming repetition is good
This chip has a whole boatload of spec sheets.. https://www.microchip.com/wwwproducts/en/MTCH101
Bedankt!- Edited
Hello, London (?) and Antwerp (cool!),
The reason why I'm asking is this:
5 volt makes the detection distance significantly larger. But indeed it's VDD that needs this! From one of the spec sheets (I realize now --
)
Figure 3 shows the relationship between detection distance and sensor size. Higher V DD voltage also extends the distance, because with higher V DD the sensor will generate stronger electric field for sensing.
@giuliomoro Where is
P9.07 ?
Here?
I'm trying with the potentiometer, but the sweet spot of activation is just so much further from the sensor with 5 Volt (which I now understand and did not before).
Thanks so much for thinking and reading along with me! First time I've used a smd sensor from scratchGreetings from Brussels, where at this hour 'there ain't nobody here but us pigeons',
Delving deeper into the electronics universe..Ciaooo - keep safe -
W- Edited
Hi,
I'm using a chip that needs 5 Volt to operate properly. 3.3 also works, but I lose a lot of range with only 3.3 Volt.
The Bela schematics explicitly state to not use 5V with the digital pins, but I did not find more information on this elsewhere.
This is how the Proximity sensor switch chip is connected to Bela - quick sketch:
So Pin 4 in this sketch goes to
- Digital in 2 of Bela (12 in Pure Data) (not GPIO8 as in the drawing)
- with a 4.7k resistor to 3.3 Volt (which I would like to be 5 Volt)
- to a resistor, followed by a Led to 3.3 Volt again
--> I want on this drawing all 3.3 Volt to be 5 Volt. I have been prototyping first with Arduino and the sensitivity is a lot better, also clear in the chip documents.Question ====> Can I use the Bela 5Volt pin in this set-up?
----> Or should I include a step-up from 3.3 to 5 Volt?
----> or should I just get my 5 Volt elsewhere? Does this influence the Bela digital ins?Thanks!
Greetings from a quiet Brussels,
Wendygiuliomoro
yes, that did the trick! Very bizarre then that there is audio with the older IDE as it is logical to have to activate the dsp in PD. Non capisco - No lo entiendo - Ik begrijp dit niet - I don't understand.I compared 'my render.cpp' a bit to the one for Trill (which can replace everything here.. and so it goes..).
Now the other work begins, making the interface and more complex and musical Pure Data Patches..
Thanks!
Ciaooo
w- Edited
In August 2019 this render.cpp for the mpr121 Touch sensor worked.
--> So I have reverted back to the IDE that was available at that time: v0.3.6b
And guess what, I have soundSo in the rewrite of the IDE something happened that disables sound in the render.cpp I have.
This was a lot of unnecessary misery...
Congratulations!!
- Edited
giuliomoro Which basically says sound output - could not create
interesting! you must be screwing something up pretty badly!
So, I added a |dac~| and the no sound output error disappeared
Late night forum posting
This is the Patch I'm using to test the MPR121Output is perfect, a bang each time I touch the sensors:
Bela stopped
Building project ...
Building render.cpp...
...done
Extracting dependencies of library Midi
Extracting dependencies of library Scope
Extracting dependencies of library UdpServer
Linking...
...done
Build finished
Running project ...
Running Pd 0.48-2
No MIDI device enabled
bonk version 1.5
fiddle version 1.1 TEST4
pique 0.1 for PD version 23
sigmund~ version 0.07
0: bang
1: bang
2: bang
3: bang-----> Back to post 1 in this Forum thread, still using these render.cpp and I2CMPR121 files: https://cloud.constantvzw.org/s/pNc45tZKRx2aRsQ
Which worked fine in August 2019, here's a video: http://www.wvanw.space/?p=322(yesterday I worked with someone who's really good at pd, we have turned everything outside in)
Which basically says sound output - could not create
--> What is verbose(4) and the Find menu?I do get this in the bela terminal when I run the I2CMPR121 on it's own:
1 mode switch detected on the audio thread.
Bela stopped
Building project ...
Build finished
Running project ...
Running Pd 0.48-2
No MIDI device enabled
bonk version 1.5
fiddle version 1.1 TEST4
pique 0.1 for PD version 23
sigmund~ version 0.07
output~
error: ... couldn't create
verbose(4): ... you might be able to track this down from the Find menu.
0: bang
1: banggiuliomoro Like a charm
Pretty bangs when touched- Edited
I have now reverted to my old render.cpp, and the I2CMPR121 files, adapted the library paths and now I get this error:
no matching function for call to 'sys_doio' column: 3, line: 343
/root/Bela/projects/Electret_test/render.cpp:343:3: error: no matching function for call to 'sys_doio'
sys_doio(pd_that);
~~~
/usr/local/include/libpd/s_stuff.h:168:6: note: candidate function not viable: requires 0 arguments, but 1 was provided
void sys_doio();
^
1 error generated.make: *** [/root/Bela/projects/Electret_test/build/render.o] Error 1
Line 343 gives:
#ifdef PD_THREADED_IO
void fdLoop(void arg){
t_pdinstance pd_that = (t_pdinstance)arg;
while(!gShouldStop){
sys_doio(pd_that);
usleep(3000);
}
}
#endif / PD_THREADED_IO */giuliomoro Yes, they are