Topics created by Leo05

@ajb2k3 Thank you, I found the schematics (https://github.com/m5stack/M5-Schematic), but do you know where I can find Gerber files ?

I've never had any problems with the DS18B20 sensor powered at 5V, with an external 4.7k resistor. Never any esp32 or even Raspberry Pi burnt out.

I did a few tests:

24 m cable with 8 sensors of 1m at the end sensors powered by 3.3V

Works well with 4.7k external resistor
Also works well with internal resistor using pinMode(33, INPUT_PULLUP)
No errors (-127 or not detected) at all in all cases

I'll test soon with longer cables.

But, most important I use certified DS18B20, not bad quality copies that are good only for short distance.

That question of which sensors to use is dependent of environmental conditions.
In My case an RPI acts as an MQTT server (because I have one available), controllers capture the data from the sensors and send them Over WIFI to the MQTT on the RPI using very simple UIFLow code.

This all depends on wifi range. I do have a sim module to review but I have been struggling to understand and find suitable SIM cards for MQTT/IOT use.

Hi @felmue

No, the example server works fine. You are right, it was probably an issue with csv reading.

Thank you

It looks like PlatformIO is still uploading your filesystem as SPIFFS despite setting board_build.filesystem = littlefs. This happens because the default partition table might not reserve space for LittleFS. Try creating a custom partition table that supports LittleFS and specify it in platformio.ini with board_build.partitions. Also, ensure your LittleFS_esp32 library is compatible with M5Core2. Without proper partitioning, mounting fails with corrupted directory errors like yours. Let me know if you want help generating a suitable partition CSV file!

Hello @Leo05

hmm, not sure why GPIO27 didn't work - it's marked as GPIO on the M5 Bus - should be free to use. I assume you've set it to output first?

If you're not stacking a module which requires a serial connection GPIO13 and GPIO14 should be usable too.

If you are not using I2C on the Groove port then GPIO32 and GPIO33 should be free too.

Also GPIO35 and GPIO36 are free, afaik, but those two can only be inputs.

Thanks
Felix

Hello @Leo05

have a look at the schematics of M5Stack Core and PLC.

I do not have the PLC module but I do have the LAN module which is similar in that respect and I do have both 12V and USB connected at the same time while programming the M5Stack Core, but not permanently. Both power sources produce 5 volts but there might be a slight difference in the voltage which would mean one power source is feeding a small current into the other, but I don't think it will damage anything. Nevertheless, use at your own risk.

The full project, M5Stack Core and PLC module will work fine from USB only. Unless you add something in the PLC module which requires 12 volts.

According to the PLC module schematics the BAT pin is not connected / used. But it will show the battery voltage from the stacked M5Stack Core.

No, the battery in M5Stack Core will not charge when only 12V is applied. Only USB can charge the battery.

Thanks
Felix

https://docs.m5stack.com/#/en/base/plc_base

@Leo05 Hi there, any updates on the PT100 support?
I'm doing POC on ESP32 and got 4 PT100 sensors working (using 4 MAX31865).
Ideally, I'd like to use a module for M5Stack.

@noiseislife said in Dices example not working on M5Stick C:

To get around this I saved the Example sketch to disk, deleted the file Dices.ino and then opened Dices_MPU6886.iso. You will get a message about requiring that the directory name be changed, which it does for you.

You should now be able to successfully compile the sketch to the m5stick.

Thank you. Now it works !