giuliomoro Never mind, I see the one I need to get rid of, the one I keep is on line 350

giuliomoro I've removedf the return true; on the 13th line of setup and now when I click run project I get this error:

alt text

right, that's because of the duplicated scope.setup() lines. Remove the scope.setup(2, 44100) from the fourth line of setup(). Also, remove these lines from the top of render():

 // Logging to the scope the pulse inputs and the distance
        scope.log(digitalRead(context, n, P8_08), distance/100);

    giuliomoro Nevermind, I had the wrong object name in Pd, getting it printed in the console now 🙂 thanks for all your help - I'll give you a buzz if I need anymore help. Is there a donate function on the Bela website?

    giuliomoro Haha, cheers 🙂 I'm going to have a crack at implementing a second sensor and Pd object for it, thanks for giving me confidence with C++

    giuliomoro Hiya, back again 😛

    I've attached two sensors now, with the second sensor attached to:

    GND: P08_01 Ground
    ECHO: P08_10
    TRIG: P08_09
    VCC: The pin next to (horizontally) P09_07

    I've duplicated the variables at the top of the C++ file:
    alt text

    and made the duplicates and changes to the setup:
    alt text

    and duplicated the render part:
    alt text

    Here is my new Pd patch:
    alt text

    but as you can see, the console is printing the same number for both sensors. 🙁 I get the feeling I've done something wrong with the render part...

    You also need two separate PulseIn objects.
    Just now you are initializing the same object twice, with the second call to init() probably overriding the first one, so you currently are only monitoring the second sensor.

      giuliomoro Got it, thanks, I overlooked that. Now its working but the console is updating every 1 second or so, instead of the constant stream of data like it was before, any way to fix that?

      giuliomoro Ah, its not actually, its just scrolling up the window and not staying at the bottom of the console window. Interesting..

      That may be due to the zoom of the browser tab containing your IDE window not being 100%.

        soravis I have a full PD solution for this if you're interested

        Brilliant! What is the purpose of the [metro] banging the [print] ?

        If @sambilbow was interested in a similar solution, be advised that this is using the analog outputs ([adc~ 3]) so you will have to change it to use the Digitals.

        Incidentally, @sambilbow: did you need an external transistor to amplify the 3.3V to 5V to trigger the HC-SR04 or did it work straight from the 3.3V ?

          giuliomoro
          The [metro] and [print] was totally unnecessary and it's just for logging out the current distance from time to time. In terms of power source, I feed HC-SR04's vcc with Bela's SYS 5V like advised in the C++ example.

          12 days later

          giuliomoro It worked straight from the digital outputs I connected it to. 🙂!

          By the way, the patch is going well now, I'm just fiddling with some Pd at the moment. I've come across a problem where if i stop the patch running in the IDE before a solenoid has received a 0 message, the solenoid will stay ON, causing it to get very hot (burnt one out yesterday) (its also connected to 12v). Is there any sort of reverse loadbang? where I can bang 0 to all solenoids upon closing the patch (stopping the IDE). I saw the bottom section of the render.cpp and it seems that would be the place to put it, but I'm not sure...