@Nooblearns not a good start if M5Burner doesnt play game before you even connect your M5Stick

@williamsmaith just let me know. I have over 700 clients using the system with a remote dog feeding application. I even have a client using eye-tracking to send messages to feed his dog (as the feeder is mounted to his wheel chair). - cheers.

Hi guys

I tested M5Tab5 (running UIFlow 2.3.1) with all the units I have available and most of them worked ok.

Note: I also got the i2c driver install error, but it didn't cause I2C to actually fail.

GPIO units

SSR - ok

I2C units (bus speed 100k)

Env III - ok Env IV - ok ExtIO2 - ok Color LCD - ok OLED - ok PaHUB - Env IV - ok

I2C units (bus speed 400k)

PbHUB - ok 4Relay - ok

Unit Gesture and AMeter did not work for me with either bus speed 100k or 400k. M5Tab5 seemed to hang in setup and a hard reset was required.

Thanks
Felix

@VVong_san_
glad to hear 'bout that

@PavelNDC Public (red) means that's it's not connected. normally this is an issue with the M5Stack server.

Found a little more time to troubleshoot this with the actual hardware today as well as squint at the datasheets again.

I was at least able to determine a couple more things:

I believe I've finally understood the schematics well enough to confirm that the M5 PPS operates on 3V3 I2C. I had previously gotten mixed up while trying to sort out M5's various conventions for labeling the different I2C lines (e.g. prefixes like SYS/ISO/INT/PA) as well as the fact that the M5 PPS schematic is split across two pages and I hadn't understood the precise relationship there.

TL;DR: The pins I'm using are the ISO_SCL/ISO_SCL pins as shown in the schematic below, and they are tied to the VDDB pin on the U1 isolator component, which in turn is powered via ISO_3V3 from the header.

M5 PPS I2C Pullups to 3V3 on ISO plane.png

(I also finally understand the "ISO" prefix as meaning "isolated plane", which, OK, I'll admit to a little facepalm that this wasn't obvious to me earlier.)

My wiring to the STM32 Nucleo ties ISO_SCL/ISO_SDA directly to corresponding pins on the Nucleo, while sourcing ISO_3V3 from the STM32's IOREF pin (and FWIW, I've also tried the STM32's dedicated 3V3 pin as well as probed those pins to confirm 3.3V that looks stable).

Just because it was easy to test, I tried adjusting the I2C speed parameter wayyyyy down to the comically-slow 1 kHz -- with no apparent change in behavior... but then the moment I wrote that, I realized I should check whether the Adruino TwoWire implementation I'm using actually supports arbitrary speed. Sure enough, it coerces ALL speed parameter values to one of the de facto standard values of [100 kHz, 400 kHz, 1 Mhz]. So... apparently I proved nothing via that test and doing otherwise would require hacks I'd rather not get into unless that's a pretty strong hypothesis. Sigh.

@Slarck Thank you.
Just check and add delay before and after pbhub.begin(), the program with only this library is very stable. However, the program with complete library set was not working.
I tried to remove it ne by one. Finally, I found somthing :

Every time have M5StamPLC.update(); the program cannot read data from Pbhub I tried to add delay before and after every M5StamPLC.update(), pbhub.begin() Pbhub.analogRead(0), the situation is not solved. I guess there is some trick while using pbhub together with SD card, StamPLC display , Digital Input scan. However, at this moment I still cannot make everything working at the same time.

@smily77 Did you manage to get the SD card reader to work?

@Handcannon Well the Core and Core2 will no longer compile in Arduino IDE with the latest board def, 3.12 and M5Stack says it is a 'me' problem and recommend I use an earlier revision.

@hacxx Dear hacxx, Thanks for your help.

@hacxx Obviously I am missing something because UIFLOW 2.3.1 lists neither Neopixel nor Addressable LED in the unit list for me.
92997380-2da1-450c-a3aa-320539564dc8-image.png
db000a27-58a2-4945-a1ed-76af3fb29328-image.png

@hacxx I was able to work out the problem. I implemented changes to the m5stack board_m5cores3 component which makes it enable the correct AXP2101 power management for I2C for the Port A Grove port when using USB-C power.

My issue was when using the device with the DIN base and the battery on and a sensor (CO2L) plugged into the Grove Port A (I2C), the device would be working. But if I disconnect USB-C from my computer and switch off the DIN base power, then switch the DIN base back on and plug USB-C back in (simulating a complete power outage of mains and battery) the device would boot loop with the message about SDA being held low.

The only way for me to get out of the loop is to unplug the CO2L from Port A. Then the device would boot on its next attempt and the I2C port recovery would be successful. Finally, I could plugin the CO2L, reset using the button, and everything would work again.

The issue was I needed to call M5.Power.setExtOutput during setup() of the BoardM5CoreS3 class from the https://github.com/m5stack/M5CoreS3-Esphome repo's components.

void BoardM5CoreS3::setup() { M5.begin(); ESP_LOGI(TAG, "Enabling 5V power output on the external ports"); M5.Power.setExtOutput(true); ESP_LOGI(TAG, "Turning off display panel backlight"); M5.Display.setBrightness(0); }

I implemented this in a custom component which I then add as an external_component to my ESPHome config. I added additional functionality in a separate component, to expose the AXP2101 battery level, charging status, etc. I also added an automation action to allow printing out debug state info from the AXP2101, to help with debugging the IRQ and other power management concerns.

In my ESPHome config it looks like this now and the CO2L sensor works reliably now without the controller going into boot-loops from various power loss/power source change scenarios:

esphome: name: ${hostname} friendly_name: ${friendlyname} platformio_options: board_build.flash_mode: dio board_build.mcu: esp32s3 board_build.f_cpu: 240000000L libraries: - m5stack/M5Unified external_components: - source: type: git url: https://github.com/terpasaurus-midwest/esphome-fork ref: m5cores3 path: my_components refresh: 2min components: [m5cores3_power, board_m5cores3] board_m5cores3: id: m5_board m5cores3_power: id: m5_power battery_sensor: name: "Battery Level" id: battery_level battery_present_sensor: name: "Battery Present" id: battery_present battery_charging_sensor: name: "Battery Charging" id: battery_charging

@TSSP_Projects
Thank you very much! Exactly that problem!

Top man and once again thank you!

like with firmware adds new but often stops something old to work.... you can always load old version if something doesnt work

Hello @xgonc

no, I did not try any other Ethernet library.

Thanks
Felix

@icarus121
great job!

@Salam-Rashid said in No enciende la pantalla.:

A quien pueda interesar: Problema solucionado. He desmontado el aparato le he desconectado la batería "es muy fácil, tiene un conector blanco de dos pines, con un cablecito Rojo y uno Blanco que se puede conectar y desconectar", con la batería quitada, lo he conectado al ordenador a trabes de su cable USB Tipo C y se ha encendido la pantalla. He desconectado el cable USB y lógicamente el modulo se ha apagado porque no tenia la batería puesta. He vuelto a conectar la batería he apretado el botón de encendido y ha vuelto a funcionar. así que problema resuelto. No se ni como ni porque surgió el problema, pero ya esta resuelto. La solución la he encontrado en este mismo foro en el idioma Japones, por el compañero @mongonta555. Gracias.

helpful！

@ajb2k3 Thanks for the reply. Maybe I'm misunderstanding what the Vbus is supposed to be. I thought it was the power coming in from the USB port. Even if there is a trickle of stuff draining the battery, there shouldn't be any input from USB. I suppose something is just leaking over somehow.

@jbruggem Your first post shows that

you haven't configured Arduino to configure code for the M5Stack Core2 which uses a different core and pin config to a base esp32. The example you are using is not an M5Stack demo, Arduino is missing Libraries.

All these errors point back to not have the M5Stack Core2 board type selected.

yuyun2000,

I wasn't able to get my structure to pass correctly. I ended up not only changing the double to a float, but I also changed it to another uint16_t. There was still a 1 byte difference in the sizes of the structure (Nano was 13, M5Stack was 14). I added the "uint8_t pad1" to the Nano so it was then 14 also. The comms routines that I have now shows that they both return a 0 (successful) but the data doesn't come across like it does with the Nano to Nano testing.

I've decided to give up on sending the Structure and just assemble the data into a String Array and send that. I have it working as a String, but I'm changing it over to use a null terminated Character Array.

Thanks Anyway, it was fun trying!

Sir Michael