Well I started doing the process of elimination and decided to compile a default blank Tab5 project in UiFlow v2.3.1 with no unit sensors and the i2c driver install error still occurred... See screen shots... So something else is trying to load the i2c drivers in UiFlow v2.3.1 for the Tab5 device and is having a problem installing it...

Question: Could this be a possible bug somewhere when it comes to Tab5 and the UiFlow IDE???

Tab5andTest4_Error_1.png

Tab5andTest4_Error_2.png

Tab5andTest4_Error_3.png

If you're seeking a Data Analyst study plan, focus on essential skills like Excel, SQL, Python, statistics, and visualization tools such as Power BI or Tableau. Reputable institutions like MITSDE offer structured, flexible programs that cover both theoretical concepts and practical applications in analytics. Understanding technology basics is also crucial—especially hardware/software clarification. Hardware includes physical components (CPU, RAM), while software refers to applications and systems that run on them. Distinguishing between the two ensures better troubleshooting, compatibility decisions, and overall technical efficiency—key for any aspiring data analyst.

@yuyun2000

Traceback (most recent call last): File "<stdin>", line 25, in <module> File "<stdin>", line 16, in setup TypeError: unexpected keyword argument 'timer_id'

@killernils Your project is feasible with UIflow2 (MicroPython). Here's the breakdown:

Hardware Compatibility:

CoreS3 (SKU:K128) supports both Unit Weight-I2C and Module13.2 Stepmotor Driver v1.1 (SKU:M039-V11) via I2C
Stepper driver provides precise control with microstepping (FULL to 1/32 step) and step counting
Weight unit offers calibration, tare function, and filter settings through UIflow2 blocks

Required Functions Implementation:

Load Cell Calibration: Use WEIGHT_I2CUnit.set_calibration() with known weights
Tare Function: Implement via WEIGHT_I2CUnit.set_reset_offset()
Stepper Control: Utilize StepMotorDriverModule methods for direction, microstepping, and PWM frequency control
Position Tracking: Count steps using motor control commands and convert to displacement based on T8x4 rod (4mm per revolution)
Data Logging: Use UIflow2's file system blocks to save CSV data to internal storage
HMI Interface: Create buttons and plots using CoreS3's display blocks

Implementation Considerations:

Ensure proper power supply (9-24V) for the stepper driver
Implement step delay logic for smooth motor movement
Add error handling for load cell over-range conditions
Use filter functions on weight readings for stable measurements

https://chat.m5stack.com/

@yuyun2000 said in カードピュータ1.1をラズベリーパイのbleキーボードとして使いたいのですが、ブルートゥースでペアリングができません。:

Raspberry PiのBluetooth設定Raspbian Bullseyeでは、BlueZのバージョンによってBLE互換性が異なる場合があります。以下のコマンドでBluetoothサービスを再起動し、デバイスを再スキャンしてください：
sudo systemctl restart bluetooth
bluetoothctl scan on

当初はGUIデスクトップで接続できない状態でしたが、おかげさまでCLIコマンドで bluetoothctl を使い、scan on でアドレスをスキャンし、pair <MACアドレス> で無事に接続できました。

CLIコマンドの使い方をよく知らなかったので調べるきっかけができました。ありがとうございます。

@GeorgeR
Have a search for 'quadcopter battery' on Amazon (or your marketplace of choice) and you should find one of the right size and correct connector. I've bought a couple of batteries and charged them with the 'Timer Power Unit' for various projects.
WARNING!! BEWARE! I've found about 50% of the batteries I've bought had the wires the opposite way round to that required by the M5Stack controllers. They will instantly kill your controller! Triple check the polarity before ever plugging them into your controller.

@kuriko So you are saying it is a software issue rather than hardware which seems to be the case to me. It would be really helpful to have access to the source for the unit classes so I could add functionality through inheritance.

@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.

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

@jahaan2311 The "GET mac failed" error when burning UIFlow 2.0 firmware to your PaperS3 (SKU:C139) typically relates to communication issues during the flashing process. Here are the recommended steps to resolve this:

Ensure Correct Download Mode: When connecting the PaperS3 to your Mac, make sure the device enters download mode properly. The screen should remain blank after connecting, indicating it's in programming mode.

Verify M5Burner Setup:

Confirm you have the latest M5Burner version installed for macOS
Select the correct PaperS3 firmware in M5Burner
Double-check the USB port selection matches your connected device

Check USB Connection:

Try using a different USB-C cable (preferably a data cable, not charging-only)
Connect directly to your Mac's USB port instead of using a hub
Avoid using USB-C adapters if possible

Reconfigure Burning Settings:

In M5Burner, click "Configure" before burning
Verify all Wi-Fi settings are correctly entered
Ensure the baud rate is set to the recommended value (typically 115200)

macOS Specific Considerations:

Ensure you have the necessary USB drivers installed
Check System Preferences > Security & Privacy for any blocked developer extensions
Try restarting your Mac and the PaperS3 device before retrying

If the issue persists after these steps, please try burning the factory firmware first using the PaperS3 Factory Firmware and then attempt the UIFlow 2.0 firmware again.

https://chat.m5stack.com/

@jalmalogni To debug the USB keyboard issue with your Tab5 (SKU:C145/K145), please try the following steps:

Verify USB OTG Configuration: Ensure your code correctly initializes USB OTG mode. Add these build flags to your PlatformIO configuration:
build_flags =
-DARDUINO_USB_CDC_ON_BOOT=1
-DARDUINO_USB_MODE=1

Check USB Initialization Order: Modify the initialization sequence in setup():
USB.begin(); // Initialize USB first
delay(1000); // Add delay before keyboard initialization
Keyboard.begin();

Monitor USB Enumeration: Connect via WebTerminal through UiFlow2 to check if the USB device is recognized. Navigate to the serial monitor and look for USB HID initialization messages.

Test Hardware Connection: Ensure you're using the USB-C port (labeled as USB 2.0 OTG) on Tab5, not the USB-A host port. Try different USB cables known to work with data transfer.

Simplify Test Code: Use this minimal example to isolate the issue:
#include <M5Unified.h>
#include "USB.h"
#include "USBHIDKeyboard.h"

USBHIDKeyboard Keyboard;

void setup() {
M5.begin();
USB.begin();
delay(2000);
Keyboard.begin();
M5.Lcd.print("USB HID Ready");
}

void loop() {
M5.update();
if (M5.BtnA.wasPressed()) {
Keyboard.print("Hello");
Keyboard.write(KEY_RETURN);
}
}

Check Power Management: Ensure Tab5 is sufficiently powered (use external power if battery level is low). USB HID functionality may be disabled under low power conditions.

https://chat.m5stack.com/

A digital input interrupt in UIFlow is used to respond instantly to changes in the state of a pin, such as the pressing or releasing of a button. Instead of constantly checking the pin, you set an interrupt on a chosen GPIO with rising, falling, or changing detection. The callback function is triggered by this event, making your program more efficient and responsive to real-time input without using excessive processing power.

For Core2 AWS Deep Sleep Wake:
The M5Stack Core2 AWS exposes ESP32 RTC GPIOs GPIO36 (VP), GPIO39 (VN), GPIO34, GPIO35, GPIO25, GPIO26, GPIO27, and GPIO32 for external wakeup triggers. Configure via esp_sleep_enable_ext0_wakeup() or esp_sleep_enable_ext1_wakeup(). Check the Core2 pinout to avoid conflicts with built-in peripherals.

Note: Some pins may require pull-up/down resistors. Test with low-power triggers (e.g., buttons) to verify wakeup reliability.

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.

@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

which exact firmware are you flashing in to it?

this might be a dumb question but is there any way to get a bin file for m5 launcher

That sounds frustrating! Since it's been an issue since purchase, it might be a hardware defect in the IT8951 controller. Try a 'nuclear reset'。 Disconnect the battery for 30 mins + hold power button to drain residual charge, then reflash.