StickC Plus + PaHUB + 3 Ultrasonic I2C units



  • @felmue looks like the same code that return "ultrasonic not found" at start, but I will check it.



  • I have made a simple test for Arduino and it works. It show that hardware part is working correct need just fix the problem in the code for UIFlow.

    #include <M5StickCPlus.h>
    #include <Unit_Sonic.h>
    #include "ClosedCube_TCA9548A.h"
    
    #define PaHub_I2C_ADDRESS 0x70
    ClosedCube::Wired::TCA9548A tca9548a;
    
    SONIC_I2C sensor;
    
    void setup() {
        M5.begin();
        tca9548a.address(PaHub_I2C_ADDRESS);
        sensor.begin();
        M5.Lcd.setTextFont(2);
        M5.Lcd.setTextColor(YELLOW, TFT_BLACK);
        M5.Lcd.println(("PaHUB Example"));
        M5.Lcd.setTextColor(TFT_WHITE, TFT_BLACK);
    }
    
    void loop() {
      static float newvalue = 0;
      for (uint8_t channel = 0; channel < 6; channel++) {
        tca9548a.selectChannel(channel);
        M5.Lcd.print(channel);
        M5.Lcd.print(" = ");
        newvalue = sensor.getDistance();
        if ((newvalue < 4000) && (newvalue > 20)) {
          M5.Lcd.printf("%.2fmm", newvalue);
        } else {
          M5.Lcd.print("ERR");
        }
        M5.Lcd.print("\n");
      }
      delay(20);
      M5.Lcd.fillScreen(BLACK);
      M5.Lcd.setCursor(0,0);
    }
    


  • Hello guys

    @teastain : See example here.

    @gavin67890 : yes it still works when I add PaHub as unit on Port A.

    @robot_alf : have you tried something similar in UiFlow/Micropython? E.g. only adding one Ultrasontic unit and then manually select the PaHub port/channel?

    Thanks
    Felix



  • @robot_alf Have you tried Download rather than just Run from UIFlow? I had it on another project that refused to Run, but worked OK from Download.

    Other than that, perhaps just recheck all again from the top, right StickC model (original or Plus), right units for PaHUB and Ultrasonic, etc. Did you want to add some screenshots from UIFlow, Blocky, Python, etc. Maybe with a few pairs of eyes we can spot something (remember to hide your API Key).



  • @gavin67890 Download not working. I think it is the same like run app just the controller switched to the "app" mode instead of "internet" mode.



  • 0_1693946459135_4a3ee96e-095d-4cd6-b8ab-4c08594362e2-image.png
    This is crazy but this code working with 3 sensors )
    The pahub and ultrasonic was selected to PortA. And sometimes I see distance from incorrect sensor. I think again that hardware part is working, but code for StickC Plus controllers have some bugs.
    M5Stack engineers, could you please send me python libraries for pahub and ultrasonic? Maybe I can help to investigate the problem. I don't want to spend time for reverse engineering them from bin-file of UIFlow firmware )



  • This code also working but need to connect sensors to 1,2,3 ports of pahub, not to 0,1,2

    #include <M5StickCPlus.h>
    #include <Unit_Sonic.h>
    #include "ClosedCube_TCA9548A.h"
    
    #define PaHub_I2C_ADDRESS 0x70
    ClosedCube::Wired::TCA9548A tca9548a;
    
    SONIC_I2C sensor;
    
    void setup() {
        M5.begin();
        tca9548a.address(PaHub_I2C_ADDRESS);
        sensor.begin();
        M5.Lcd.setTextFont(2);
    }
    
    void loop() {
      static float newvalue = 0;
      for (uint8_t channel = 0; channel < 3; channel++) {
        tca9548a.selectChannel(channel);
        M5.Lcd.printf("%i = ", channel);
        newvalue = sensor.getDistance();
        if ((newvalue < 4000) && (newvalue > 20)) {
          M5.Lcd.printf("%.2fmm   ", newvalue);
        } else {
          M5.Lcd.print("ERR        ");
        }
        M5.Lcd.print("\n");
      }
      delay(20);
      M5.Lcd.setCursor(0,0);
    }


  • @robot_alf "need to connect sensors to 1,2,3 ports of pahub, not to 0,1,2"

    There are 2 hard problems in computer science: cache invalidation, naming things, and off-by-1 errors :D



  • @robot_alf That's encouraging.
    I take that label0 is Ultrasonic_0
    , label1 is Ultrasonic_1
    , label2 is Ultrasonic_2
    What happens if you complete the three unit ultrasonic set (by adding (Add/+) two more Ultrasonic units)?
    Have you tried increasing the Wait?



  • For reference/comparison. From drag and drop controls in UIFlow, I added the PaHUB first then 3x Ultrasonics (sub images pasted in and config as shown bottom right). The loop I know to work from my StickC and Ultrasonic unit. Drag in 3x labels and connect the dots.
    0_1693979509477_Screenshot 2023-09-06 at 06.46.52.png
    0_1693979912312_Screenshot 2023-09-06 at 06.57.32.png



  • Hmmm... I did the same several times and always not worked. Which PaHub are you used? I2C Hub 1 to 6 Expansion Unit (PCA9548APW) https://shop.m5stack.com/products/i2c-hub-1-to-6-expansion-unit-pca9548apw or [EOL] I2C Hub 1 to 6 Expansion Unit (TCA9548A) https://shop.m5stack.com/products/pahub-unit?variant=16804803412058 ?



  • Hi @robot_alf, I bit the bullet and bought some more hardware. So, now there are two of us in the same position.

    1x StickC (freshly flashed from M5Burner v1.12.4)
    1x M5Stack I2C Hub 1 to 6 Expansion Unit (PCA9548APW) SKU: U040-B
    2x M5Stack Ultrasonic Distance Unit I2C (RCWL-9620) SKU: U098-B1

    Strating from a new UIFlow, click Run, and (drumroll please)... "X Ultrasonic unit maybe not connect", FFS.

    The good news, I have a ENV III here, so I connected it and got the same error. Take out the Ultrasonic and it works fine (PaHub Added/+ or not). Excellent, so back to the blocks in UIFlow. I can see that the Ultrasonic unit from the ? link is SKU: U098, both of mine are SKU: U098-B1 – the "Sonic" rather than "Ultrasonic", no unit for that in UIFlow. Comparing the notes for U098 vs U098-B1, I came across this line: "This allows for easy I2C integration and multi-sensor operation using a single BUS, to save I/O resources.", interesting.

    Hmm, [now rummaging around for all sorts of hardware] Groove2Duponts, check, breadboard, check, off we go...

    Switched to Core2 and transferred all the rest of the hardware, inc. PaHub, same UIFlow setup, and guess what... it works as expected. Two independent readings/labels. NB Keep sensors a little bit apart to avoid cross talk.

    I tried additionally with power from I2C port of Core2 and no change “X Ultrasonic unit maybe not connect”. Very annoying.



  • @gavin67890 yes it works perfect for Core2. I have the problem only on StickC Plus.
    Okay, I tried to switch my project from PaHub to PbHub. I have such a hub too. I compared the photo of Ultrasonic I2C and IO versions (thanks a lot to M5 for this) and saw that it can be easily re-soldered I2C to IO. I made an IO out of one I2C sensor and it works fine, but not through PbHub. Actually now I'm at a dead end now ) It looks that I can't make a small mobile machine with two servos360 and three ultrasonic sensors on the StickC Plus (

    M5 engineers could you please add a function "get distance from ultrasonic" for PbHub?



  • @robot_alf, I can see the 0Ohm? resistors, interesting. Glad to hear at least the conversion worked.

    Yeah, it's a bit disappointing because it's a common use case, multiples of the same ultrasonic sensors.

    One thought, could you use the hat GPIO pins at the top of the StickC for the now IO ultrasonic sensor?



  • @gavin67890 Yes, you need to change two jumpers (0Ohm) in the IO position and also remove one resistor on the top of the board, which is labeled "IIC".
    It was easier for me to short-circuit the contacts than to solder small transistors. So, you just need to unsolder three resistors and then make two short circuits.

    I think that need just to add a simple function to the PbBoard for ultrasonic sensors like this - https://github.com/ErickSimoes/Ultrasonic/blob/master/src/Ultrasonic.cpp
    Because I can't to it through blocks or python, it's microseconds between send a receive an impulse.



  • I tried the example in the following documentation, but I think it is out of date because the blocks are not available as shown in UIFlow https://docs.m5stack.com/en/uiflow/advanced/i2c (@m5stack can this be refreshed please).

    Basically, I wanted to try and setup an I2C ultrasonic module from vanilla blocks, without Add/+ing the module and in accordance with this Arduino code https://github.com/m5stack/M5-ProductExampleCodes/blob/master/Unit/ULTRA/Arduino/ULTRA/ULTRA.ino and this https://www.sgbotic.com/products/datasheets/sensors/sr04_i2c.py for guidance/inspiration.

    If I could be confident in the sensor, then maybe move back to the hub, then back to multiple sensors following the Arduino and converting back to vanilla blocks, something like this https://dronebotworkshop.com/multiple-i2c-bus/

    I also tried the "Scan I2C device" block, which doesn't find address of Ultrasonic (0x57) at freq 400000 - fine for ENV III [0x44, 0x70] and PaHub [0x70] – ENV III on its own definitely scans as two addresses. freq reduced to 100000 it finds the ultrasonic address.

    If I try and use the "Available I2C address in list" block I get I2C bus error (19) message (StickC and Core2), any help appreciated on why.

    I'd really like to figure this out as I2C ultrasonic sensor arrays would be extremely useful for driving vehicles.

    0_1694186101089_Screenshot 2023-09-08 at 16.14.52.png



  • I'd like to get to this, which should be possible using PaHUB and the sensors (easier to assemble with M5Stack with sensors in cases, up to 6 at a 30deg angle to each other).
    0_1694186497256__5jbk6xmVZn.jpeg
    https://www.hackster.io/user04650005/ultrasound-sensor-array-with-the-hc-sr04-f7108f



  • Interesting from UIFlow2.0, is there a similar global? control for bus speed in UIFlow v1.12.4?
    0_1694287668044_Screenshot 2023-09-09 at 20.23.36.png



  • Anyone got any more thoughts? My intension is to raise it as a bug (I think we've exhausted our best ideas).



  • Continuing my tale-of-woe about the PaHub:

    I have now tried using G0 and G26 (StickC) to connect as custom I2C to PaHUB with the ENV III attached, which works on Port A.

    Via the PaHUB using the top hat pins (the pins an I2C hat uses). I get "Pahub unit maybe not connect", fine on Port A.