<![CDATA[UIFlow 1.7.6]]>Ver 1.7.6 time : 2021.04.29

v1.7.6

new features

  • IoT Cloud support:
  • Azure IoT support certificate.
  • Core2
  • Display network images.
  • Play tones & network WAV audio.
  • Timing boot.
  • COM.X
  • COM.LTE HTPP(s) support.
  • Baisc&Fire
  • UNITCAM support.

Bug fix:

  • Core2 touch coordinates offset bug fix.
  • LEGO+ Module.
  • Long label text break mode.
]]>https://community.m5stack.com/topic/3244/uiflow-1-7-6RSS for NodeTue, 28 Apr 2026 19:48:26 GMTFri, 30 Apr 2021 03:01:45 GMT60<![CDATA[Reply to UIFlow 1.7.6 on Fri, 04 Jun 2021 01:33:05 GMT]]>@kmart93179 weight unit is not used the I2C protocol of course they not compatible.

]]>https://community.m5stack.com/post/13992https://community.m5stack.com/post/13992Fri, 04 Jun 2021 01:33:05 GMT<![CDATA[Reply to UIFlow 1.7.6 on Wed, 02 Jun 2021 10:49:10 GMT]]>?????????

]]>https://community.m5stack.com/post/13989https://community.m5stack.com/post/13989Wed, 02 Jun 2021 10:49:10 GMT<![CDATA[Reply to UIFlow 1.7.6 on Wed, 02 Jun 2021 10:47:50 GMT]]>I use weight unit for port A and the GOPlus2 Base at the same time. it seem like it cant work together,When i trigger the server motor ,my weight unit dont work anymore,the label keep show 0 ,i think maybe is I2C issue ,any ideas?
thx
skyler

]]>https://community.m5stack.com/post/13988https://community.m5stack.com/post/13988Wed, 02 Jun 2021 10:47:50 GMT<![CDATA[Reply to UIFlow 1.7.6 on Wed, 19 May 2021 12:22:00 GMT]]>I cannot get a QRCODE for the Cloud with the UNITCAM examples.

]]>https://community.m5stack.com/post/13819https://community.m5stack.com/post/13819Wed, 19 May 2021 12:22:00 GMT<![CDATA[Reply to UIFlow 1.7.6 on Tue, 18 May 2021 18:20:48 GMT]]>@m5stack thx, maybe some day uiflow will be able to support new HW at rls day ;)

]]>https://community.m5stack.com/post/13814https://community.m5stack.com/post/13814Tue, 18 May 2021 18:20:48 GMT<![CDATA[Reply to UIFlow 1.7.6 on Fri, 14 May 2021 11:10:10 GMT]]>@mati It is in our support plan and will be supported in future updates. so maybe after a few weeks, it will be supported.

]]>https://community.m5stack.com/post/13783https://community.m5stack.com/post/13783Fri, 14 May 2021 11:10:10 GMT<![CDATA[Reply to UIFlow 1.7.6 on Fri, 14 May 2021 11:06:58 GMT]]>@ajb2k3 could you share your code here? it would helpful for us to debug it.

]]>https://community.m5stack.com/post/13782https://community.m5stack.com/post/13782Fri, 14 May 2021 11:06:58 GMT<![CDATA[Reply to UIFlow 1.7.6 on Wed, 12 May 2021 19:45:09 GMT]]>@m5stack when we gonna see UiFlow with zigbee Init and COM ?

]]>https://community.m5stack.com/post/13771https://community.m5stack.com/post/13771Wed, 12 May 2021 19:45:09 GMT<![CDATA[Reply to UIFlow 1.7.6 on Sat, 08 May 2021 08:19:14 GMT]]>8Servos hat intermittent response with 1.7.6

]]>https://community.m5stack.com/post/13752https://community.m5stack.com/post/13752Sat, 08 May 2021 08:19:14 GMT<![CDATA[Reply to UIFlow 1.7.6 on Fri, 07 May 2021 09:53:18 GMT]]>@doswiadczalnik now it fixed. you could remove the old firmware file then download again.

]]>https://community.m5stack.com/post/13746https://community.m5stack.com/post/13746Fri, 07 May 2021 09:53:18 GMT<![CDATA[Reply to UIFlow 1.7.6 on Wed, 05 May 2021 11:10:20 GMT]]>@felmue I took it that it was for the core 2 as it has the different case shape and the longer Mbus header pins

]]>https://community.m5stack.com/post/13725https://community.m5stack.com/post/13725Wed, 05 May 2021 11:10:20 GMT<![CDATA[Reply to UIFlow 1.7.6 on Wed, 05 May 2021 08:49:49 GMT]]>Hello @ajb2k3

I don't know for sure for which core the GoPlus2 was designed for, but I think it was meant for M5Stack (Gray, Fire, etc.).

All I can say (looking at the schematic) is that electrically it is not fully compatible with the M5Core2.

Also, all Arduino examples I can find are for M5Stack (Gray, Fire, etc.) and none for M5Core2.

And the GoPlus (first generation) is EOL.

BTW: I don't think the '2' is because it is meant for M5Core2. It's simply the successor of the first GoPlus module. Which, if I am correct, is an unlucky (and confusing) naming.

Thanks
Felix

]]>https://community.m5stack.com/post/13722https://community.m5stack.com/post/13722Wed, 05 May 2021 08:49:49 GMT<![CDATA[Reply to UIFlow 1.7.6 on Wed, 05 May 2021 08:22:25 GMT]]>@felmue said in UIFlow 1.7.6:

Hello @shally1986

same here. I think the reason for the green light blinking is that when M5Stack (Gray) is turned off it doesn't fully turn of the 5 V. (I measure about 2 V when turned off.)

That said, I think GoPlus2 was designed for M5Stack (Gray, Fire, etc.) and not for M5Core2 since w/o electrical modification you'll loose external I2C on M5Core2.

Thanks
Felix

Am I missing something here, the GoPlus2 was designed for the core2's (hence the 2 designation) the Goplus was designed for the core/gray/go/fire.

I haven't had time to check the Goplus2 as its connected to a robot and been busy with other projects.

]]>https://community.m5stack.com/post/13720https://community.m5stack.com/post/13720Wed, 05 May 2021 08:22:25 GMT<![CDATA[Reply to UIFlow 1.7.6 on Tue, 04 May 2021 14:31:27 GMT]]>Hello @shally1986

same here. I think the reason for the green light blinking is that when M5Stack (Gray) is turned off it doesn't fully turn of the 5 V. (I measure about 2 V when turned off.)

That said, I think GoPlus2 was designed for M5Stack (Gray, Fire, etc.) and not for M5Core2 since w/o electrical modification you'll loose external I2C on M5Core2.

Thanks
Felix

]]>https://community.m5stack.com/post/13713https://community.m5stack.com/post/13713Tue, 04 May 2021 14:31:27 GMT<![CDATA[Reply to UIFlow 1.7.6 on Tue, 04 May 2021 07:49:28 GMT]]>@felmue thank you for confirming . When I connect the goplus2 to core grey the green light keeps blinking when grey is off , but it seems okay with core2 . How does it work for you ? The light behaviour is same on both grey and core2 .

Do you recommend to use grey to stack goplus 2 ?

]]>https://community.m5stack.com/post/13711https://community.m5stack.com/post/13711Tue, 04 May 2021 07:49:28 GMT<![CDATA[Reply to UIFlow 1.7.6 on Tue, 04 May 2021 05:03:49 GMT]]>@m5stack On this version AWS block don't work with Core(v1.7.6-en) and Core2(v1.7.6-core2). But it works with M5StickC(v1.7.6). Do I missing something?

]]>https://community.m5stack.com/post/13710https://community.m5stack.com/post/13710Tue, 04 May 2021 05:03:49 GMT<![CDATA[Reply to UIFlow 1.7.6 on Mon, 03 May 2021 19:37:28 GMT]]>Hello @shally1986

works for me. Tried with an M5Stack (Gray) and M5Core2. Both motor ports A and B work in both directions just fine.

It could be a hardware issue. Each port uses a H-bridge which consists of four MOSFETs each. For one direction two of the MOSFET conduct and for the other direction the other two are in use. So if one MOSFET used for a give direction is broken, the other direction still works.

Thanks
Felix

]]>https://community.m5stack.com/post/13708https://community.m5stack.com/post/13708Mon, 03 May 2021 19:37:28 GMT<![CDATA[Reply to UIFlow 1.7.6 on Mon, 03 May 2021 12:10:27 GMT]]>goplus2 , motor A does not rotate in -127 direction but motor B does . I physically changed the motors and both run fine on motor port B .

Seems like some issue with motor port A in goplus2. Not sure if its software or hardware . Should not be hardware as motor is able to control speed from 0 to 127 on motor port A, just does not work in opposite direction .

Seems issue reported on github for goplus
https://github.com/m5stack/GoPlus/issues/1

Please help

]]>https://community.m5stack.com/post/13705https://community.m5stack.com/post/13705Mon, 03 May 2021 12:10:27 GMT<![CDATA[Reply to UIFlow 1.7.6 on Sat, 01 May 2021 20:41:04 GMT]]>After burning it to my Core device, start screen is white instead of black. I prefered black :). And my application has reversed colors. Blue title is now yellow, black background is kind of white, yellow is blue and green is pink.

]]>https://community.m5stack.com/post/13690https://community.m5stack.com/post/13690Sat, 01 May 2021 20:41:04 GMT