Posts made by flex

It is not possible on IOS (iPad) to create any UI Element through UI Editor in UIFlow 2.0, while it is working in UIFlow 1.12…
Do I am the only one concerned for doing nomad development on the go with an iPad?
Thank you, the dev team who is working on the development of the
UIFlow 2.0 webpage, to have a look on that problem and to solve it :)
Pascal

@IAMLIUB0

Hi,

do developers of UIFlow are reading M5Stack Community Forum, to take into account the bugs we can encounter, or is there any special bug report to do somewhere else?

I notified few months ago and also recently, that UIFlow 2.0 doesn't work with Apple IOS, while UIFlow 1.12 works correctly, in term of creating designing UI items...

Thank you for your feedback

Pascal

@iamliubo said in UiFlow 2.0 Alpha verison discuss(how-to, bug, feature request or sometings):

@iamliubo

Hi Liubo,

• there is problem using the webpage UIFLow 2.0 on IOS: it is not possible to create or modify an UI item (it is working on UIFlow 1)...
• more generally, what is the most efficient way to fill a bug report for UIFlow 2.0

Thanks, Pascal

Hi,

The “disable block” option, which is in UIFlow 1.12 web is very convenient, why it is not in UIFLow 2.0 web

Yes I am using Safari on IOS, but I also tried other web browser and with all, it was not possible to create any objet on the UI view of the CoreS3 through the webpage of uiflow 2.0 alpha 20 with latest IOS and Safari on iPad…

On uiflow 1 everything work well on IOS, so I think that is is some coding problem of the webpage of uiflow 2.0

Hi,

I cannot use the UI design part of uiflow 2.0 (alpha 20) on IOS, while I can do it without any problem with uiflow 1, or uiflow 2.0 on OSX:

It is impossible to create any design element/field on the screen view for the CoreS3

Does anyone has a hint, or is it a functionnality not yet implemented

@iamliubo
Hi
System uptime in seconds should return 0 when the system (m5stack ….S3) starts, nobostand epoch 1970 or 2000…

I think that Micropython use epoch 2000 by default

Hi dev Team,

I made small test on Alpha17:

• now "get UTC time" works correctly :)

• There is problem when using "Set timezone GMTx":
  using "Set timezone GMT+2" and then "get local time", it should return UTC+2/GMT+2 but it return UTC-2/GMT-2

• There is still problem with "get system uptime in seconds" which is not adjusted to epoch 2000 and returns a very big value

Thanks

Thanks, I'll give it a try to unbind, and then will try a rebind

@IAMLIUBO
yes it is solved now that MAC address was correctly registered in your server, and the binding process went through correctly, and therefore the burning or UIFLow...

That takes me to a question:

How could I unbind an S3 M5Stack device registered with an account, if I want another person with another account to take on it?

Thanks

@imaliubo

yes I tried,

it seems that UIFlow (based on 1.19.1) doesn't take epoch into account, which is year 2000 in MP 1.19.1 or 1.20.

Apart that there is confusion created on gmtime() and localtime() in UIFlow apis.

Also to mention that in MP 1.20, the returned values from gmtime() and localtime() are not all time reliable (sometimes the ntpserver requested in MP localtime() return what in fact is gmtime()...)

After investigations through terminal and esptool.py:

• what I thought as successful the Erase and Flash of the demo app and the config prior to flashing UIFlow2, wasn't in fact successful:
  log windows were confusing in those case,
  but not when step of flashing UIFlow2, as more tests are done I am getting the message "Error Invalid Chip".

It seems that the CoreS3 is DOA for flashing and can just run the demo app....

Hi,

I just thought also that I was not requested, at the flashing step of UIFlow, to bind my Core3S with my account, but just got that message "Error - invalid chip"...

Could it be related to the binding step?

which log do you have when flashing?

maybe I can try to flash through the terminal...

my port on the core, prior flashing is:
tty.usbmodem14101

I am able to flash the demo app on the CoreS3

I am able to set the config on the CoreS3
I am able to erase the CoreS3, prior to the step of flashing
but then,
I am not able to flash UIFLow on the CoreS3, and get just at beginning of process, before even getting the log window, a message "Error - Invalid Chip"

when I flash "CoreS3 Touch Panel Hot-Fix firmware", I get:
M5CoreS3 TP FW Information
regA1 Lib Version: 0x3008
regA3 ChipVendorID: 0x64
regA6 Firmware ID : 0x05
regA8 CTPMVendorID: 0x02

Yes I did!!!

And I was successful to update an AtomS3 and a StampS3.

And I can erase or flash successfully the CoreS3 with the demo program on my configuration

the only concern that I have is that my configuration seems to use esptool 3.32 when I use M5burner, while the latest available version of esptool is 4.51

but I just made update of the AtomS3 and StampS3 with UIFlow Alpha15 without problem with same configuration, and I am just unable to flash the CoreS3.

Could the CoreS3 version of UIFLow Alpha15, Alpha14 and Alpha15 compilations were done with some specific parameters different from AtomS3 and StampS3 or not on the same machine or by the same user?

Which esptool version is called through M5burner on your configuration when you flash the CoreS3?

on a new CoreS3, after 3 seconds press on restart button, and after getting green light shortly, with M5Burner 3.0, I then try to upload UIFlow 2.0 beta 14 (or beta 13) dedicated to the CoreS3, and I get a message "Error - Invalid Chip"

Does someone else also encounter that problem?

Is the CoreS3 defective (despite the demo app works good...)

I get report from CoreS3 Touch Panel Hot-Fix firmware below:

M5CoreS3 TP FW Information
regA1 Lib Version: 0x3008
regA3 ChipVendorID: 0x64
regA6 Firmware ID : 0x05
regA8 CTPMVendorID: 0x02

Thanks for feedback

Pascal