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

    UIFlow 1.7.1

    Official Updates
    10
    20
    30.6k
    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.
    • H
      houkensjtu
      last edited by

      I found the "Advanced" function group is missing in the Web version of UIFlow 1.7.1. Is it relocated to somewhere??

      sodokuS 1 Reply Last reply Reply Quote 0
      • sodokuS
        sodoku @houkensjtu
        last edited by

        @houkensjtu I can still see it

        1 Reply Last reply Reply Quote 0
        • sodokuS
          sodoku
          last edited by

          @m5stack using on 1.7.1 on the Fire makes the speaker quite noisy.

          1 Reply Last reply Reply Quote 0
          • ajb2k3A
            ajb2k3
            last edited by

            @m5stack Please remove the following from the Coreinks H.A.T list as they are not physically compatable with the core in.

            JoyC,
            RoverC,
            PuppyC,
            BugC
            BeetleC
            CardC

            UIFlow, so easy an adult can learn it!
            If I don't know it, be patient!
            I've ether not learned it or am too drunk to remember it!
            Author of the WIP UIFlow Handbook!
            M5Black, Go, Stick, Core2, and so much more it cant be fit in here!

            m5stackM 1 Reply Last reply Reply Quote 0
            • m5stackM
              m5stack @ajb2k3
              last edited by

              @ajb2k3 thank you for feedback. we will check that.

              G 1 Reply Last reply Reply Quote 0
              • T
                teiafra
                last edited by

                @m5stack said in UIFlow 1.7.1:

                COM.LTE

                Is the COM.LTE connectivity supported only in Core2 and not Core (Basic)?
                If so, when extended also to Core?

                m5stackM 1 Reply Last reply Reply Quote 0
                • L
                  luis
                  last edited by

                  Please add RGB, Speaker and IMU blocks in hardwares section for the M5fire device.

                  1 Reply Last reply Reply Quote 0
                  • m5stackM
                    m5stack @teiafra
                    last edited by

                    @teiafra core supported LTE connect UIFlow too.

                    T 1 Reply Last reply Reply Quote 0
                    • T
                      teiafra @m5stack
                      last edited by

                      @m5stack thanks but then I'm not able to follow the procedure shown here on Twitter (showing from M5Burner, right?) aimed to pass the APN to the module. Currently I'm on UIFlow 1.7.0.
                      I posted a topic also here Can you help me?

                      m5stackM 1 Reply Last reply Reply Quote 0
                      • m5stackM
                        m5stack @teiafra
                        last edited by

                        @teiafra which step you stuck?

                        T 1 Reply Last reply Reply Quote 0
                        • T
                          teiafra @m5stack
                          last edited by teiafra

                          @m5stack:

                          On the Core display I am a able to select COM.LTE as additional connectivity as shown here.
                          BUT the next picture 0_1610609391974_M5Burner2.jpg (I guess taken from M5Burner configuration, right?) is different in my case because it shows only WiFi, while the APN section is missing 0_1610608430876_M5Burner.jpg.
                          The final result is that if I select on the Core display COM.LTE and reboot it fails to connect. 0_1610608668641_COM.X attempt.jpg.
                          Please note that the modem is working fine, since I'm able to drive it with my UIFlow code (via AT commands) moving data back and forth perfectly.
                          My ultimate need is to use the UIFlow MQTT client not through the WiFi but natively through the mobile connection.
                          THANKS!

                          1 Reply Last reply Reply Quote 0
                          • G
                            Gaviota @m5stack
                            last edited by Gaviota

                            @m5stack

                            @ove said in UIFlow 1.7.1:

                            I installed UIFlow_Core2 version v1.7.1_core2 on my Core2 and now I have no power on port A.

                            If I add "power.setBusPowerMode(0)" in the Python tab before any Units are initialized the power is returned but I can not do this with blocks.
                            The power is restored until the Core2 is reset.

                            I detected a similar problem with the Core2 and UIFlow 1.7.1

                            Testing with the ENV- and the TVOC/eCO-units at port A of the Core2 drives it into the I2C-error message "I2C bus error(19)". After rolling back the Core2 to UIFlow 1.7.0 these units works with the Core2.

                            I think there must be a I2C-bug in UIFlow 1.7.1 for the Core2, at least for port A.

                            A lot of nice M5Stack stuff :) ....

                            MatiM m5stackM 2 Replies Last reply Reply Quote 0
                            • MatiM
                              Mati @Gaviota
                              last edited by

                              @gaviota said in UIFlow 1.7.1:

                              @m5stack

                              @ove said in UIFlow 1.7.1:

                              I installed UIFlow_Core2 version v1.7.1_core2 on my Core2 and now I have no power on port A.

                              If I add "power.setBusPowerMode(0)" in the Python tab before any Units are initialized the power is returned but I can not do this with blocks.
                              The power is restored until the Core2 is reset.

                              I detected a similar problem with the Core2 and UIFlow 1.7.1

                              Testing with the ENV- and the TVOC/eCO-units at port A of the Core2 drives it into the I2C-error message "I2C bus error(19)". After rolling back the Core2 to UIFlow 1.7.0 these units works with the Core2.

                              I think there must be a I2C-bug in UIFlow 1.7.1 for the Core2, at least for port A.

                              Yep check my finding
                              https://community.m5stack.com/topic/2663/core2-uiflow-bottom2-support/14

                              1 Reply Last reply Reply Quote 1
                              • m5stackM
                                m5stack @Gaviota
                                last edited by

                                @gaviota yeah... that is a bug. we will fix it in the next version

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

                                  Hi guys

                                  UIFlow 1.7.1.1 for M5Core2 is out and it seems to fix at least the no power issue on port A.

                                  @m5stack : is there anything else that has been fixed on 1.7.1.1? Just curious. Thanks.

                                  Happy Stacking!
                                  Felix

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

                                  m5stackM 1 Reply Last reply Reply Quote 1
                                  • m5stackM
                                    m5stack @felmue
                                    last edited by

                                    @felmue I mean. in the v1.7.1.1(for core2) version,we fixed the default(WIFI MODE) M-BUS 5V power don't open in the v1.7.1. but when you use the LTE Network Over COM Mode. you need to use it to extend DC power input else the M-BUS will lose power.

                                    For more information you could refer this tutorial :

                                    https://docs.m5stack.com/#/en/quick_start/comx_lte/network_over_com

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

                                      Hello @m5stack

                                      thank you for the clarification. I appreciate it.

                                      Thanks
                                      Felix

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

                                      1 Reply Last reply Reply Quote 0
                                      • First post
                                        Last post