@ciconde I take it that you are not using the M5Stack US units?
https://m5stack-store.myshopify.com/collections/m5-unit/products/ultrasonic-distance-unit-rcwl-9600?variant=36550631424164

If you use the PaHub (i2c) you should be able to connect two US units to the same port.

@cerocca said in 1 to 3 HUB Expansion Unit:

Hi @felmue

and thanks for your reply, appreciated. I knew it was simple but I wanted confirmation :)
Regardless of this, thanks for pointing me out where to find all documentation, including schematics.

So I have another question: are the modules "possible to open"?
I mean, I saw some modules interesting for my project (heart rate sensor) and their schematic show that there is a LDO regulator from the +5V to the +3v3 of the IC.
I was wondering if it was possible to safely open the white plastic package, bypass the LDO so that I can feed the sensor directly with the +3v3 I have on the I2C VCC line.

Thanks if you (or anybody else!) can answer my doubt.

@cerocca said in 1 to 3 HUB Expansion Unit:

Hi @felmue

and thanks for your reply, appreciated. I knew it was simple but I wanted confirmation :)
Regardless of this, thanks for pointing me out where to find all documentation, including schematics.

So I have another question: are the modules "possible to open"?
I mean, I saw some modules interesting for my project (heart rate sensor) and their schematic show that there is a LDO regulator from the +5V to the +3v3 of the IC.
I was wondering if it was possible to safely open the white plastic package, bypass the LDO so that I can feed the sensor directly with the +3v3 I have on the I2C VCC line.

Thanks if you (or anybody else!) can answer my doubt.

dont bypass the ldo!
units have a supply voltage of 5v and if you bypass the ldo you will put 5v into a 3v3 device.

@IAMLIUBO can you seperate the

wifiCfg.wlan_ap.active(True)
wifiCfg.wlan_sta.active(True)

functions so that they have their own blocks for setting to true or false please.

@garfield On the main pcb you will find the date printed. this will tell you the batch and sometimes the revision.

@lumpynose the coreink default behaviour when you do a screen refresh (instead of partial refesh) is to change the whole screen to black and white several times as its basic e-ink function.
The coreink has a slow refresh rate of 15 seconds between refreshes and this is pointed out quite a few times in uiflow!

@dionw said in How to make RTC clock with NTP:

@lukasmaximus I'm keen to see this working as well. When do you think it might be possible for the NTP RTC example uiFlow block @ajb2k3 mentioned
he had uploaded to be available?

Not Sure what happened to it but the example file has been uploaded to github
https://github.com/Ajb2k3/UIFlowHandbook/blob/master/NTP_RTC.m5f

@wolli01 said in Lcd driver for M5Stack Core2:

@russ
Thank you very much for your effort.
What is this code for in the end?
Is it mandatory to use it?

finally:
    # shutdown
    spi.deinit()

The code de initialises the SPI bus so that that other functions can use the pins or the bus

@marcvl Really?

Wow thanks for discovering the m5mqtt.subscribe/mqtt.start issue.
BTW is this in micropython?

@felmue

Thanks @felmue that brings my eink documents closer to finishing.