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

    Possible issue with Tab5 and UiFlow v2.3.1 - (i2c driver install error)

    General
    5
    33
    1.4k
    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.
    • robskiR
      robski
      last edited by

      for start Tube Air Pressure unit is not i2c device, it gives out analog value... something not right with unit/tube pressure lib

      K 1 Reply Last reply Reply Quote 0
      • K
        Kenzo @robski
        last edited by

        @robski Ok, so I am not going crazy... I thought the Tube Pressure sensor was analog [PortB(GPIO)] but when tried to configure the settings for Tube Pressure port in the Unit window of UiFlow, the port it came up with was Port A(G54, G53, V, G) as the default port... See attached photos...

        Is there anyone at M5Stack support team we can reach out to regarding a possible bug with the Unit/tube pressure lib?

        DefaultTubePressurePort_1.png

        1 Reply Last reply Reply Quote 0
        • robskiR
          robski
          last edited by

          ports in general are configurable, some units have just one general port which can be analog, uart, I/O, i2c.... try to build project with diff analog sensor (even without this being connected) like potentiometer unit or something...

          K 1 Reply Last reply Reply Quote 0
          • K
            Kenzo @robski
            last edited by

            @robski Thanks again for responding to the post... I tried the Mini Angle Unit Rotary Switch with Potentiometer (SKU: U005) with a very simple code and the same error occurred... Very strange... I wonder if I am the only one having this error show up when trying to use Tab5 with UiFlow v2.3.1... Is anyone else seeing this error message occur when trying to use Tab5 with a M5Stack sensor unit in UiFlow v2.3.1?

            Tab5andAngleUnitError_1.png

            Tab5andAngleUnitError_2.png

            Tab5andAngleUnitError_3.png

            Tab5andAngleUnitError_4.png

            1 Reply Last reply Reply Quote 0
            • robskiR
              robski
              last edited by robski

              try with analog value, delete get voltage block

              on your original "tube pressure" example use raw analog value for start too

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

                Hi guys

                I tested M5Tab5 (running UIFlow 2.3.1) with all the units I have available and most of them worked ok.

                Note: I also got the i2c driver install error, but it didn't cause I2C to actually fail.

                GPIO units

                • SSR - ok

                I2C units (bus speed 100k)

                • Env III - ok
                • Env IV - ok
                • ExtIO2 - ok
                • Color LCD - ok
                • OLED - ok
                • PaHUB - Env IV - ok

                I2C units (bus speed 400k)

                • PbHUB - ok
                • 4Relay - ok

                Unit Gesture and AMeter did not work for me with either bus speed 100k or 400k. M5Tab5 seemed to hang in setup and a hard reset was required.

                Thanks
                Felix

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

                robskiR K 2 Replies Last reply Reply Quote 0
                • robskiR
                  robski @felmue
                  last edited by

                  This post is deleted!
                  1 Reply Last reply Reply Quote 0
                  • K
                    Kenzo @felmue
                    last edited by

                    @felmue - Thanks felmue for tube air sensor with your Tab 5 with UIFlow 2.3.1! So your UIFlow test program with the Tube air sensor connected to Port A successfully uploaded to the Tab5 and captured air pressure readings? If so, can you post a screen shot of your simple program you used to test the sensor with?

                    I wonder what is causing i2c driver install error to be generated.

                    I will give it another try with the suggestions robski made but if you could post your testing code that ran successfully that would great!

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

                      Hello @Kenzo

                      I think you might have misread my post. I do not have a Tube Pressure unit so I cannot test this case, sorry.

                      Thanks
                      Felix

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

                      K 1 Reply Last reply Reply Quote 0
                      • K
                        Kenzo @felmue
                        last edited by

                        @felmue Yep, I read that wrong... my fault...

                        1 Reply Last reply Reply Quote 0
                        • K
                          Kenzo
                          last edited by

                          Well I started doing the process of elimination and decided to compile a default blank Tab5 project in UiFlow v2.3.1 with no unit sensors and the i2c driver install error still occurred... See screen shots... So something else is trying to load the i2c drivers in UiFlow v2.3.1 for the Tab5 device and is having a problem installing it...

                          Question: Could this be a possible bug somewhere when it comes to Tab5 and the UiFlow IDE???

                          Tab5andTest4_Error_1.png

                          Tab5andTest4_Error_2.png

                          Tab5andTest4_Error_3.png

                          1 Reply Last reply Reply Quote 0
                          • A
                            adamm5
                            last edited by

                            i'm getting the same i2c driver error on an Atom Lite, the error began following an erase but persists regardless of the UIflow2 version I attempt to refresh with.

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

                              Hello guys

                              I think that is what I wanted to tell you guys with my previous post. The i2c driver install error, which I also get, does not prevent most of my units to work properly.

                              Out of all my units only two did not work and two I2C units would only work after switching the i2c speed to 400 k.

                              In other words I do not think the i2c driver install error matters in regard with the Tube Pressure unit, which is not an I2C unit.

                              @Kenzo : do you have any other units you could try with your M5Tab5? Or any other core(s) you could try the Tube Pressure unit with?

                              Thanks
                              Felix

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

                              A 1 Reply Last reply Reply Quote 0
                              • A
                                adamm5 @felmue
                                last edited by

                                in my case i need to query an AIN unit, which is i2c...so this error is a total blocker.

                                A 1 Reply Last reply Reply Quote 0
                                • robskiR
                                  robski
                                  last edited by

                                  @Kenzo as Ive said before try below: remove "get voltage" block and try your Tube Pressure unit with analog value only
                                  kenzo0.PNG

                                  K 1 Reply Last reply Reply Quote 0
                                  • A
                                    adamm5 @adamm5
                                    last edited by

                                    @adamm5 Ive rebuilt this project from scratch and can confirm that ignoring the i2c load error is possible even when using the AIN i2c unit and PAhub unit. This seems to be a change to my earlier experience but perhaps something else was happening with the code.

                                    1 Reply Last reply Reply Quote 0
                                    • K
                                      Kenzo @robski
                                      last edited by

                                      Thanks everyone for your suggestions!

                                      @robski - I went back to my Tube example and the only one that worked was the ADC parameter to pull data. (I used 12bit)

                                      So I looked at the UiFlow1 example for the Tube Pressure and tried to duplicate it. The program now runs BUT I am not sure if I am using the correct math conversion to convert the raw data from the ADC parameter into Kpa. I have searched a couple of sources BUT can't seem to find documentation that fully explains how to correctly calculate Kpa with the ADC parameter to Kpa...

                                      Does anyone know were to get really good documentation on the tube pressure sensor that explains how to properly calculate Kpa using the sensor with ADC option?

                                      UiFlow2_WorkingCode.jpg

                                      BlockyPythonCode!.jpg

                                      UiFlow1_CalculationExample.jpg

                                      K 1 Reply Last reply Reply Quote 0
                                      • K
                                        Kenzo @Kenzo
                                        last edited by Kenzo

                                        So if I assume the ADC 12 bit option will give me 4,096 different points and the ADC 16 bit option will give me 65,536 different points maybe I can come up with a formula ( using the voltage - Pressure graph) of how to calculate Kpa when using ADC option for the Tube pressure... Everyone I am just thinking out loud so don't bash me too badly... LOL!

                                        1 Reply Last reply Reply Quote 0
                                        • robskiR
                                          robski
                                          last edited by robski

                                          what are RAW values you are getting from your sensor? pure analog read value?

                                          try below

                                          float raw = analogRead(sensorPin); // Read analog value
                                          float Vout = raw / 4095.0 * 3.6; // Convert to voltage (assuming 3.6V reference)
                                          float P = (Vout - 0.1) / 3.0 * 300.0 - 100.0; // Calculate pressure in kPa

                                          K 1 Reply Last reply Reply Quote 0
                                          • K
                                            Kenzo @robski
                                            last edited by

                                            @robski Thanks for replying! With nothing connected to the Tube pressure sensor, I am getting a RAW value of 3,287 (12 bit option selected in the ADC parameter).

                                            In regards to a 3.6V reference, where is that in the documentation?

                                            RangeSpan_1.jpg

                                            I think we are getting close to solving this problem!

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