When using the timestamp function with the ntp flow module the timestamp is incorrect. Timezone is set correctly and all other time functions work properly.

So I finally figured it out. Turns out the stepmotor driver module is NOT compatible with Core2. Upsetting because on the page on the M5Stack store it says: "StepMotor Driver is adapted to M5 core series..." That's core SERIES, not just Core Basic. Fortunately I had a Core Basic and could test it. Works just fine.

Please let me know if I'm wrong about the Core2 compatibility. If it is let me know what I need to do to get it to work with Core2. Thanks.

So different but similar behavior with a third Core2. Still looking for help on this.

Also I should mention I have two of these modules and two core2's and all exhibit the same behavior.

Hi!

I have a core2 stacked with a Stepmotor driver module 13.2 and a m5go bottom2.
I am using the stepmotor driver UI flow elements to program it:

No matter what I try I always get this error message when loading the code, as if the module isn't connected:

I know power is getting to the base because I can drive the LEDs, and the 12v power supply is a full 5a and does power the unit from the stepmotor base, so I can't figure out the error. Any help would be greatly appreciated!

Thanks everyone for the suggestions!

I'm trying to migrate an application to the Core2 from Core and I made extensive use of the triangle/rectangle UI things but those don't appear to be supported in Core2. Any idea why or am I missing something?

@vsthose Use "Beta" for the version when you launch M5Flow and it'll be there. The version you get is 1.6.6 (at least when I do it with the windows desktop version).

@felmue Interesting. I had not tried that. Good workaround until this gets fixed for realz.

Thanks!

I'm trying to make a robust wifi connection flow for unattended use. To do this I need to put the wifi connect commands inside a conditional so that I can test/handle/etc.

Here's a simple example to demonstrate the issue

A simple flow with the wifi connect widget in the correct place (inside a conditional):

...and here is the resulting python code. Note WiFi.doConnect has moved to the top of the python code block instead of inside the else statement:

If I move the doConnect to the correct place the code works as I expect and there are no errors.

I have tried this with doConnect and AutoConnect with the same result.