The Desktop Dual-arm Cobot, myBuddy 280, is designed for education and research, offering versatile functions for robotics learning and experimentation. With two coordinated arms, it can simulate real-world automation tasks, enhancing hands-on training in programming, AI, and engineering. Its compact desktop design makes it suitable for classrooms and labs, while safety features ensure a secure learning environment. Compatible with multiple programming languages, myBuddy 280 supports creative projects, collaborative tasks, and industry-relevant skill development, preparing students and researchers for advancements in robotics and automation technologies.

I managed to get the SD card reader to work.

H_SDIO_DRV error: sdio card init failed
The WiFi module (ESP32-C6) uses an independent set of dedicated pins (SDIO2_D0 to SDIO2_CK), thus avoiding any physical interface overlap and conflicts.

sd_mmc_card:
id: sd_card
clk_pin: GPIO43
cmd_pin: GPIO44
data0_pin: GPIO39
data1_pin: GPIO40
data2_pin: GPIO41
data3_pin: GPIO42
mode_1bit: false
slot: 0

esp32_hosted:
variant: esp32c6
active_high: true
clk_pin: GPIO12
cmd_pin: GPIO13
d0_pin: GPIO11
d1_pin: GPIO10
d2_pin: GPIO9
d3_pin: GPIO8
reset_pin: GPIO15
slot: 1

@onlysaadat My new StamPLC is exactly the same. Registered the device with M5Burner, It's on-line in UiFlow2, Loaded a fresh StamPLC demo - demo initially logged in and just flashed the monitor page no matter what browser is used on multiple computers. Cleared the monitoring user per M5s directions.

Now I get an invalid token no matter what I do.

Did you ever get your device to work with the demo or figure out how to fix the invalid token?

I do think it is too fragile to be of any practical use, I am trying to surface mount a TAB5 in a 3D printed bezel but as all the other connections are on the side, it isn't easy

Correction: The LED doesn't blink, it stays on continuously.

Hi guys

have you tried the RGB module in Hardware? Works fine for me.

I created an example using an M5Atom to control 10 SK6812 RGB LEDs. You can find it in the UIFlow2 Project Zone: M5Atom_RGB_Test_UiFlow2.3.3

Thanks
Felix

@adamm5

Well ChatGPT solved my problem....increasing the spreading factor to 11 has suddenly made everything work. Not sure why such a high SF would be needed between two devices on the same desktop? Will soon find out.

In the meantime, the following table gives some interesting perspective on the transmission time for a 19byte payload.

SF Symbol Duration Payload Symbols Total Symbols Airtime 7 1.024 ms 37 51.25 0.052 s 8 2.048 ms 37 51.25 0.105 s 9 4.096 ms 37 51.25 0.210 s 10 8.192 ms 37 51.25 0.420 s 11 16.384 ms 37 51.25 0.839 s 12 32.768 ms 37 51.25 1.678 s

I did a check and set scaling to 1 and the display is properly shown i.e. as 9:59 etc

To fix issues with M5Burner on Mac, ensure you’ve installed the correct USB-to-serial drivers (like CP210x or CH340). Run M5Burner using Rosetta if needed. Allow app permissions via System Settings > Privacy & Security. Always download the latest M5Burner version compatible with your mac.

@amudon
おそらくネットワーク接続できました！！！！！
ありがとうございます

For anyone still interested. I know I wil be likely banned for this but this post is old and will probably not be checked.
First of all, remove the sticker on the back. Then remove the 2 screws near the UART port. Take off the top part of the M5StickC. You should see the board and the screen now. If your goal is to remove the screen, then just rip off the side that is closer to the edge and unsolder the connections on the other side of the screen. The screen should be off now. For people who want to change the battery or do other modifications you can take 2 paths from here. 1st path includes unsoldering some connections. 2nd path is safer, but looks sketchy. Anyways be careful since if you damage a line/wire, it can result in some features not working. I accidentally beheaded my home button while disassemblying my M5StickC.
1st path:
There are multiple little soldering points on the sides of the screen. Unsolder them and pull out the motherboard. Be careful, the battery is still attached.
2nd path:
Take off the GPIO pin cover. Pull it away from the main case (parallel to the longest side of the M5StickC). You should see multiple fork-like connectors now. After that you can take the board out.
And that should be everything. Everything else is straightforward. wanna change a butto? Unsolder it, resolder a new one. I am not helping you here. Good luck!

@scroggyg Thanks for the suggestion! I didn't think of that. I will put that as an option if no one knows what type of wired connector to use... Hopefully someone knows where to find one...

Also if you are looking for a screen protector for your Tab5, I created a simple design over the weekend and laser cut it out on a sheet of screen protector.

I have exported the design out into multiple file types so hopefully one of four files will work for people who may be interested in a screen protector for their Tab5.

Just be sure to be careful and take the necessary precautions when dealing with the fumes when cutting material with a Laser Cutter...

Github Link to design files: https://github.com/KenzoWright/M5Stack_Tab5_Accessories
Screen Protector sheets: https://amzn.to/4flH2PM

More information

If I use M5Unified.h and then a begin of M5.begin(), the data is all zeros. If I take out the begin, then the data is correct. There must be something in the M5Unified that is restarting the Wire or taking over the I2C bus.

How can I correct this. It is a show stopper. If I can find a solution, then I will have to discard the M5Stack basic and go to a regular ESP32.

I'm curious—will the iOS version of EzData support the same modules and data types as the M5Stack Core devices? Also wondering if there's going to be integration with iCloud or local storage for exporting logs. I’ve been exploring some related iOS app development workflows, such as those outlined at Idea Maker, and wondering how closely EzData aligns with those practices. Looking forward to seeing how it develops.