Hello @mehulge
yep, still broken. And my previous attempt to fix that doesn't seem to work anymore.
Thanks
Felix
Hello @mehulge
yep, still broken. And my previous attempt to fix that doesn't seem to work anymore.
Thanks
Felix
Hello @sedir
you can use the RGB blocks (in Hardware) to control the 10 RGB LEDs in the M5GO3 Bottom.
UIFlow2 Project Zone example: M5CoreS3_M5G03Bottom_RGB_UIFlow2.0.4
Thanks
Felix
Hello @taunushexe
the list blocks can be used for that. See example in UIFlow2 ProjectZone: M5Dial_Get_Values_From_Tuple_UIFlow_2.0.4
Thanks
Felix
Hello @seungmin
I wonder if the issue is only a too dark screen backlight setting? I created an UIFlow example which simply sets the screen backlight to the maximum. Does that help?
ProjectZone: M5DinMeter_BacklightSetFullBrightness_UIFlow2.0.4
Thanks
Felix
Hello @BrianR
that is not what I am seeing. With M5Dial UIFlow firmware v2.0.4--hotfix my GPS example in the Project Zone runs just fine. M5Dial_GPS_Unit_UIFlow2.0.2
Edit: Just double-checked:
Thanks
Felix
Hello @teastain
do you mean the GI (capital I for In) and GO (capital O for Out)?
That said, I think the strict one input and one output on port B is coming from ESP32 cores which would use one GPIO that actually only can be an input.
However the S3 variant doesn't seem to have this limitation anymore.
As I reported before I can set GPIO1 and GPIO2 of my M5Dial both to outputs and use them just fine.
And even if one or both of them are set as input in UIFlow firmware that should not prevent one from changing that in the user program. (Unless it is set as an input repeatedly in the UIFlow firmware.)
Note: I have not tested the same (both outputs) with an Arduino program.
Thanks
Felix
Hello @taunushexe
as @ajb2k3 mentioned only one GPIO (the second one) is used for the RGB unit. So the other GPIO can still be used as input. I created an example which uses GPIO1 as input to control the color of the three RGB LEDs in the RGB unit.
See UIFlow2 Project Zone : M5Dial_RGBUnit_GPIO1_as_input_UIFlow2.0.4
Thanks
Felix
Hello @ToughBJH
I tested with v2.0.3 and v.2.0.4--hotfix firmware and with either firmware GPIO1 and GPIO2 act independently.
BTW: v2.0.3 firmware has been built on 2024-03-21 whereas firmware v2.0.4--hotix has been built on 2024-04-16. The fact that both report 2.0.3 is probably just an oversight.
Not sure where to go from here. I'd say your M5Dial might have a hardware issue, but since your seeing it on both your M5Dials that seems a bit far fetched.
At this point in time I am out of ideas, sorry.
Thanks
Felix
Hello @ToughBJH
that is not what I am seeing. Please have a look at the UIFlow ProjectZone example M5Dial_PWM_GPIO1_GPIO2_UIFlow2.0.4.
It controls GPIO1 and GPIO2 independently. I verified it with the multi-meter and two LEDs (plus resistor).
Thanks
Felix