Longtime lurker, first time poster My name is Tenkai, and I run Zetaohm. I released a sequencer last year named FLXS1, and I referenced mutable designs for so many things during the design process. So, thank you Olivier for your contributions! I was at Superbooth 2017, and hoped to meet you, but thats when you were sick and unable to attend.
Anywho, I wanted to ask about something I saw in the Plaits ADC input design. You have a “Normalization Probe” and I just wanted to verify with you what I assume is going on, and also have a question…
It appears that this circuit is designed to allow you to actively sense the connection of a cable into any of the ports by pinging the normalization input of all ADCs simultaneously (between ADC reads, I assume) with a 3v3 signal.
My question is:
With the 1n caps on some of the ADC inputs, and a .2ms settling time for a 3v3 ping, how are you able to achieve a 2khz DC input, and also check for normalization? I would assume that checking for normalization would require that a ping be sent, and one ADC sample would be lost.
Sorry to bump an old thread. I see you’re using RCC_AHBPeriphClockCmd in the implementation of the normalization probe driver. But I’m unable to determine how that factors into Ui::DetectNormalization().
I understand that it’s an STM specific peripheral. But is there a direction I could start looking in, to figure out how to implement a similar bus on my teensy based device? Furthermore, what would I even be looking for to understand how this may work outside of STM32?
This is such a clever design and I’m itching to understand more about it.
Thank you so much for all of the knowledge you’ve helped spread Émilie
OH HOLY CRAP I GET IT NOW. THANK YOU. I had to re-re-read your first comment. TLDR is if the ADC mismatches the noise on the probe for a given sample, you track that in normalization_detection_mismatches_. This works because if the jack is plugged in… the connection breaks and the noise obviously won’t match the ADC input -_-