Hello guys

the M5Cardputer doesn't have that hold button until green LED lights up mechanism. To put M5Cardputer into download mode use the method described here.

If you want to enter download mode, press and hold the G0 button on StampS3 before turning it on, then release it after powering it on.

Thanks
Felix

Hi guys

Here is an explanation as to why it may take some time to fix: M5CoreS3 uses the SPI bus in a special way to control the LCD: MISO (normally an input) is reconfigured to be an output and is used as DC line (instead of a dedicated GPIO for DC). Unfortunately to access the SD card (which shares the SPI bus with the LCD) MISO needs to be an input.

In case you might be interested. I found a way to do this switching back and forth between input and output for Arduino.

Thanks
Felix

Hello @jamstooks

@ajb2k3 is correct, the PbHub is for analog devices only and cannot be used for UART.

Unlike UART, I2C is a bus and can handle multiple units (as long as the units use different I2C addresses). So if you want to connect multiple I2C units to you M5Core2 you can use a Groove-T.
However as soon as some units you wish to connect share the same I2C address you need a different solution. You have two options:

• the units in question allow for the I2C address to be modified
• use a PaHub (like @ajb2k3 suggested)

As for connecting the UnitV2 to your M5Core2 via UART: I would suggest the Battery Bottom 2, which has been designed for M5Core2 and it gives you the UART port needed.

The COMMU module should work as well, but as it has been designed for the M5Stack (Basic, Gray, Go, Fire) there seems to be some incompatibility issues like while the COMMU module is stacked to the M5Core2 the M5Core2 cannot be flashed.
(Note: I don't have the COMMU module, so I cannot confirm that issue.)

Thanks
Felix

Hello @m5stack

thank you for letting us know about the latest UIFlow 1.7.3 firmware. I appreciate it.

It is however very unfortunate that the M5Core2 PaHub bug has not been addressed in this update. I'd appreciate if your engineers fix that bug in the next update.

Or, as stated already many times in many places, please open source the UIFlow code so we can help you fix issues like that.

Thank you for listening.

Felix

Hi guys

an M5CoreInk with ESP32 in light or deep sleep still consumes a couple of mA (which is to be expected given the hardware architecture). However M5CoreInk allows to shutdown ESP32 completely and later wake it up from the RTC timer or alarm.

For an M5CoreInk in shutdown mode I've measured a current (at the battery) of only about 2.5 uA which is pretty good. And yes, the ink display retains the last image.

Cheers
Felix

Hello guys

my M5Cardputer takes about 7 hours for a full charge from a completely discharged battery state.

Note: I soldered two LEDs to the charger IC CHRG and STDBY outputs and it switched from charging to standby after about 7 hours.

Thanks
Felix

Hello @Surya

after long hours of searching and debugging I found the reason why I2C would fail. It starts to fail as soon as SSL is invoked. The SSL library uses an analog GPIO as input for its random seed. And in your code you used GPIO2 which is one of M5AtomS3 Groove GPIOs.

So to get rid of the I2C error try changing the GPIO used for random seed to GPIO10.

//SSLClient ethClientSSL(ethClient, TAs, (size_t)TAs_NUM, 2);
SSLClient ethClientSSL(ethClient, TAs, (size_t)TAs_NUM, GPIO_NUM_10);

Thanks
Felix

Hello @Bipman

by default Port A is meant for I2C, but it can be used for I/O (Port B) or UART (Port C) as well.

Note: But please be aware, that it can be only one type of port at any given time. Also, since its default use is Port A (I2C) there are internal pull-up resistors (10 k) in place on both lines which might have a negative effect when used in a different mode.

If you need Port A and Port B at the same time there is the PbHUB unit which can be used to connect some of the Port B units.

If you need all three types of ports (A, B and C) together then I am afraid M5Cardputer is the wrong device to use as core. There are simply no more GPIOs available for a dedicated Port B and/or Port C. Please see schematic here.

Thanks
Felix

Hi guys

even though I read the warning about not using certain types of chargers with M5PaperS3 I managed to do so anyways.

Suffice to say, M5Paper released some magic smoke and wouldn't start anymore.

I cracked it open from the back (as I think the eInk display is glued in) to get access to the board. (I do not recommend doing that as it is a destructive process.)

With the eInk display and touch disconnected I started to inspect the board.

I found the charger IC USB-C protection diode pack being dead from the look of it. I removed the charger IC (as it is not strictly needed to run) I replaced the USB-C protection diode pack and found the MosFet IC getting pretty hot. So I removed the MosFet as well and injected some voltage (4.2 V) after the MosFet which revealed that the 3.3 V regulator took some hit as well. I replaced the 3.3 V regulator with a similar one I took from an M5Atom.

With two ICs MosFet removed and the 3.3 V regulator replaced M5PaperS3 took a reasonable small amount of current. I also measured ok voltages for the eInk display so I dared to reattach the display and touch screen and yo and behold - M5PaperS3 is alive again.

Now I need to order some replacement ICs MosFet.

You can see the opened M5PaperS3 and the dead ICs here.

Thanks
Felix

Hello @ajb2k3

my apologies - I only read the comment of the M5Cardputer documentation w/o trying it myself.

Thanks
Felix

Hello @daniel-edge456

in UIFlow2 v2.2.6 using touch blocks for M5Paper and then look into the Python tab I get the following code to get touch coordinates:

if (M5.Touch.getCount()) > 0:
  x = M5.Touch.getX()
  y = M5.Touch.getY()

doing the same with power blocks I get:

Power.deepSleep(1000, True)

to put M5Paper into deep sleep.

Thanks
Felix

Hello @huanfai

looking at the soucre code for UIFlow2 device firmware I think authentication keys are fixed to default values. See here and here.

In ohter words I don't think the RFID blocks in UIFlow2 can handle anything different than default authentication keys.

Thanks
Felix

Hello @oracle_sod

ok, I see, the DFRobot version has an UART interface. M5ExtIO2 GPIOs can be set to multiple modes (input, output, ADC, servo, neopixel and PWM) but I am afraid none of these modes can be used for an UART connection.

According to the wiki page RX is used to select the mode, this could be achieved via M5ExtIO GPIO set as output.

However the TX line sends data with 9600 Baud, which I doubt M5ExtIO2 can handle.

That said, what is the reason you don't connect all three Ultrasound units directly to the M5Core? That would require 6 GPIOs.

And if you could live with the fact that all three Ultrasound units use the same mode you could get away with only 4 GPIOs, 1 GPIO to select the mode for all three units, and 1 GPIO for each unit to receive the UART data.

Thanks
Felix

Hello @oracle_sod

Note: I don't have the UltrasonicIO unit so my conclusions might be inaccurate.

Looking at the Arduino code, I see it uses a function called pulseIn() which does some sort of timing. I doubt it exists on the EXTIO2 unit so you would have to emulate this functionality yourself.

BTW: I think an easier setup would have been a PaHub unit with three Ultrasonic (I2C variant) units connected to it.

Thanks
Felix

Hello @Robertof

hmm, using variables in MQTT publish works for me.

How are you testing your code? Make sure your test software uses a different MQTT client id than your UIFlow2 code, else the first registered client gets kicked out.

BTW: my example is in the Project Zone, named M5CoreS3_MQTT_4Relay_UIFlow2.2.5

Thanks
Felix

Hello @lenswerks

afaik Unit CatM GNSS (U137) uses a SIM7080G which can not use both, a LTE and GNSS, at the same time due to some shared RF circuitry.

See this posting on Stack Overflow.

Thanks
Felix

Hello guys

some ideas for the next version of M5StamPLC:

1. switchable 5 V on Grove ports
2. switchable 5 V on extension port
3. LED indicators for the relays
4. LED indicators for the inputs

Notes for 1.: the existing ICs can be used by connecting output (P3) of (U5 PI4IOE5V6408) to the enable (EN) of (U4 LPW5209AB5F) instead of having EN tied to SYS_5V.

Notes for 2.: the existing ICs can be used by connecting output (P1_0) of (U4 AW9523B) to the enable (EN) of (U8 LPW5209AB5F) instead of having EN tied to PMU_5V.

Thanks
Felix

Hello @Krmiller

GetVBusVoltage() exists in M5Core2 library as well. See here.

Thanks
Felix

Hello @Krmiller

have you tried getType() to determine the correct AXP? See here.

For AXP2101 you could try getVBUSVoltage. See here.

Thanks
Felix

Hello @iainmac

you probably need to adjust the GPIOs used for I2C. You can find the GPIOs M5Dial uses for port A here. (Section HY2.0-4P)

Thanks
Felix