I can run UIFlow 2.0 in my browser exporting my project locally but I cannot log into my UIGlow account and retrieve saved projects
Posts made by Piet
-
RE: UIFlow Down?
-
RE: UIFlow V1.12.8 Atom Lite RTC read error
@pandian-nano
Hi Felix and Pandian
I am sorry. I was using an old M5Burner.
Flashing with the M5Burner V1.12.8 and using the Web UIFlow everythings is working
Thank you for your help
kind regards piet -
RE: UIFlow V1.12.8 Atom Lite RTC read error
Hi Felix
Thank you for replying...
The following runs fine in the desktop IDE V1.9.5 and flashes the LED for the number of months so I know the rtc is set... n.b. not seconds in this example
Changing to the Web UIFlow all attemps of running the script with new read statement return an error.
I believe that the the atom and the rtc are working correctly.
The new python code in the Web UIFlow is (rtc_0.get_date_time(2)) where as in the desktop UIFlow it is (rtc_0.get_date_time())[-3] -
UIFlow V1.12.8 Atom Lite RTC read error
Using the block rtc read ["rtc_0" get rtc "seconds'] returns an error
Desktop uiFlow V1.9.5 block rtc [in list] "rtc_0" get rtc [get # from end "0"] returns ok -
UiFlow Desktop IDE RTC
Please include the Unit-RTC in the UiFlow desktop ide.
-
Schmitt Trigger Unit
Would love a schmitt trigger unit with functional uiflow programming to build frequency/pulse counters
-
RE: M5Scale / HX711 unit weight measurements inaccurate
The HX711 and loadcell don't necessarily return a linear a value. It is more likely to be a curve.. the nature of materials.
You can create a variable and factor all your read values by this amount. For example in your case 500/268 = 1.87... So assign this value to your variable and multiply you readings by this amount. This will be approximate and it will vary for different weight ranges but you can keep refining it until you are happy. You can extend this method over various weight ranges and write conditional statements to apply different corrections for different ranges. Or if you have the smarts you can write a formula for the curve and apply it to your read values. -
RTC Core2
Set time using NTP host reports an error for the 'year' and needs to be set using a constant.
Hour reports incorrectly. 1 hour needs to be added for UTC + time zone.