🤖Have you ever tried Chat.M5Stack.com before asking??😎
    M5Stack Community
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    RTC serious bug - easy fix for development team

    UiFlow 2.0
    3
    7
    61
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • G
      gektron
      last edited by

      I've just purchased a Tab5 for our company evaluation for use as a time clock. We want to deploy many of these across multiple sites. So far the development using UIFlow 2.3.3 is working out okay. However I have just come across a serious bug with the hardware RTC in UIFlow as follows:

      When you add a "Set UTC time" block to the program, it generates the following python code:

      rtc.init((year, month, day, 0, hours, minutes, seconds, sub seconds))

      It should be calling rtc.datetime() with these parameters, rtc.init expects slightly different parameters (see https://docs.micropython.org/en/latest/library/machine.RTC.html). Could you fix this bug please and get the block to call the rtc.datetime() function as it is causing me a major road block. As I said seems like a simple fix.

      Additionally do you have the Tab5 camera integration with UIFlow blocks on the roadmap in the near future? Thanks.

      felmueF 1 Reply Last reply Reply Quote 0
      • felmueF
        felmue @gektron
        last edited by

        Hello @gektron

        until this gets fixed you could try to use an Execute mpy code block instead with the correct micropython code in it. This block is located under System.

        Thanks
        Felix

        GPIO translation table M5Stack / M5Core2
        Information about various M5Stack products.
        Code examples

        G 1 Reply Last reply Reply Quote 0
        • G
          gektron @felmue
          last edited by gektron

          @felmue @m5stack thanks for the quick reply Felix. As I understand this feature no longer exists in UIFlow, or at least I can’t find or enable it. Instead you have to define custom block models which seems like a very clunky method with limited scope. Are the execute mpy code blocks still available somehow?

          kurikoK 1 Reply Last reply Reply Quote 0
          • kurikoK
            kuriko @gektron
            last edited by

            @gektron
            I have reported this problem to the R&D team!
            The Tab5 camera adaptation is currently pending until Espressif adds MIPI driver support for the ESP32-P4.

            de842143-5e95-4f23-a316-15965652de32-企业微信截图_f6957739-ec4d-4770-a376-50a15ea44fa3.png

            Good morning, and welcome to the Black Mesa Transit System.

            G 1 Reply Last reply Reply Quote 0
            • G
              gektron @kuriko
              last edited by

              @kuriko Thank you for the update. I look forward to the bug fix and the forth coming camera implementation (hopefully Espressif will add MIPI support soon).

              felmueF 1 Reply Last reply Reply Quote 0
              • felmueF
                felmue @gektron
                last edited by felmue

                Hello @gektron

                I agree, the Execute mpy code block is a bit hidden in UIFlow2. But as I said before you can find it in System:

                UIFlow2_System_Execute_MPY_Code_Block_20250812.png

                Thanks
                Felix

                GPIO translation table M5Stack / M5Core2
                Information about various M5Stack products.
                Code examples

                G 1 Reply Last reply Reply Quote 0
                • G
                  gektron @felmue
                  last edited by

                  @felmue Doh! I was looking under system at the menu options. I didn't think to click on system for the block menu. Thanks for the guidance.

                  1 Reply Last reply Reply Quote 0
                  • G gektron referenced this topic
                  • First post
                    Last post