@rotor
This is quite simple on the Core: With the "Graphic" blocks it is easy to create graphical pages with "labels". Unfortunately, this is not so easy on the Core2 and functions are missing.

You do not use labels, but the following 3 blocks: [Lcd.clear]; [Font:...]; [Lcd.print "Label1" x: 0 y: 0 Color...]; [Lcd.print "..." x: 0 y: 20 Color...]; etc. You can first design them graphically by dragging labels onto the screen to determine the position, to then copy the screen with the graphic blocks, test whether all text appears on top of each other, and then edit the dragged labels. remove.

Use the "Functions" ("dosomething") blocks to create a page (Page1, Page2, etc). For example, by making "Setup" followed by a block "Page3", only page 3 will be visible, without using labels and you still have all the flexibility.

I hope that's how I answered your question. This is how I create multiple pages.

In this example two pages with the same layout, but in practice this is of course not necessary:

As an extra example from practice (one of my first programs in UIFlow) with two different screens:

@jobbike
Dear Job,

Welcome to this community.

That's certainly possible.
I don't think you need a Pb. hub. The I2C bus works with addresses, and as long as the addresses are different, multiple units can be connected to the same bus (read: connection). The Pb. hub is useful if you want to connect multiple weighing units set to the same address, which won't work on a single connection.

Pushbuttons can easily be connected to free pins on the controller, but there are also modules that also work with I2C.

Is this a school project or a hobby project for yourself? In the first case, you might be limited to certain components and modules. In the second case, I would recommend a different controller to start with. For example, the Basic v2.7 https://docs.m5stack.com/en/core/basic_v2.7, which has a larger display and already has three buttons.

If you have any further questions, please don't hesitate to contact us.

Translated from Dutch:

Beste Job,

Welkom in deze community.

Dat is zeker mogelijk.
Ik denk dat je geen Pb. hub nodig hebt. De I2C bus werkt met adressen en zolang de adressen verschillend zijn kunnen er meerdere units op dezelfde bus (lees aansluiting). De Pb. hub is handig als je meerdere weegunits wilt aansluiten die op hetzelfde adres zijn ingesteld - wat op één aansluiting dan niet gaat werken.

Drukknoppen kan je eenvoudig op vrije pinnen van de controller aansluiten maar er zijn ook modules die tevens met I2C werken.

Is het een school project of voor jezelf als hobby project? In het eerste geval zit je misschien vast aan bepaalde componenten en modules. In het tweede geval zou ik een andere controller adviseren om eens mee te beginnen. Bijvoorbeeld de Basic v2.7 https://docs.m5stack.com/en/core/basic_v2.7 waar een groter display op zit en ook al 3 knoppen aanwezig zijn.

Mocht je verdere vragen hebben dan horen we het graag.

I'm going to completely desolder the Pico and then test it separately. I suspect the problem persists because nothing has been changed on the PCB. I'll post an update of my findings here.

Perhaps it's an ESD-related issue. This is the second time a similar problem has occurred with the Pico, while it hasn't happened with other controllers in a enclosure.

Hi Robski,

Unfortunately, I can't show a photo due to (future) intellectual property regarding the PCB to which the module is soldered.
Thank you for your input. I'll try to explain the situation in as much detail as possible.
It was soldered manually, but professionally, and then tested for connection and short-circuiting.

When connecting the USB-TTL Downloader, external hardware was disconnected from IO pins G0, G1, and G3 by desoldering solder pads elsewhere on the PCB. EN and 3V3 are not connected.

Do you have any specific questions about the PCB?

Dear all,

After unpacking the M5STAMP PICO (D4), I immediately installed the latest firmware. I then soldered it directly to a PCB. However, the blue LED remains lit during startup.

The current meter on my lab power supply repeatedly jumps back and forth (approximately 50~100mA): apparently, it is repeatedly trying to connect. The Wi-Fi mode (yellow) is working properly: I can connect to configure the Wi-Fi key.

I unsoldered GPIO pins G0 through G3 to reinstall the firmware. This doesn't work. "A serial connection cannot be established."

This problem resembles https://forum.m5stack.com/topic/7606/m5stamp-pico-solid-blue-light
However, soldering seems to be the problem here
(of course, I checked for bad connections or short circuits to pins or to components near the pads).

What could I try to fix the problem? Where should I look?

Thank you in advance.

Under Text you will find this option, at the very bottom: Reduce ... to x decimal places. It has been tucked away a bit, but works very well.

Dear Felix,
You helped me a lot! I had already looked several times for a firmware update, but it got stuck at v1.9.8. Thanks for your tip to use M5Burner Version 3 - I used M5Burner Version 2.5.1 myself. Confusing, but now clear! With, now v1.11.0, it works well!
Thank you! Also for your very quick response.

It's very simple. The steps I do:

1. Add unit (+) in UIFlow
2. Add DIGI-CLOCK, default setting (Port A)
   2b. OK
3. Open tap 'Units (1)' (under 'Hardwares') > Digi Clock
4. Get block 'digi_clock_0 init 12c address (0x30).
5. Run

Error: File "<string>", line 8, in <module>
AttributeError: 'module' object has no attribute 'DIGI_CLOCK'

6. Add other blocks; does not matter
7. Grab another controller; makes no difference (also error).

Controlling directly with I2C is possible:
(remove unit)
Tap 'Hardwares', I2C Master:
Block 1: i2c0 Master portA freq 400000
Block 2: i2c0 Set slave addr 0x30
Block 3: i2c0 Write reg 0x4 one byte 0xFF
Display result: 8. (and no error!)

Who can help me or has an addition?

Hello,

I recently got the Core2, but run into limitations in UIFlow (current version V1.10.3). The font in the "Grapfic blocks" is limited to "Font_Default" when using the Core2. The labels can be set to other fonts. I prefer not to use labels because that limits me to using 1 screen.

Another solution is to put the generated code in an "Execute-block":

label0 = M5Label('Montserrat 10 t/m 48', x=0, y=35, color=0xffffff, font=FONT_MONT_26, parent=None)

but that is more of a temporary clumsy solution.

Can you as developers pay attention to this?

Thanks in advance!

In this example two pages with the same layout, but in practice this is of course not necessary:

As an extra example from practice (one of my first programs in UIFlow) with two different screens:

Hello,

It helps to select a different color first. Then you can still make copies. An annoying detour indeed.