Thanks, that helps a lot. This is my first use of the Unit devices. I've use the HAT on the M5
which obviously is only 1 at a time.

I'll get the PbHUB and the I2C version of the Ultrasonic Distance Unit.

I'm working on many sensors to help disabled users. These sensors help those in
wheelchairs where they might not be able to even touch buttons. So providing a multitude
of options (motion, tilt, distance, LUX, buttons) - even the touch of the Core2 is very sensitive
which is good.

Thanks,

I was able to get my M5Stack code base to work on the M5AtomS3 with M5Unified (my first time using both).

As I'm now trying to get various sensors to work, the first is the external LED.

But I get the following compiler error:

clockless_rmt_esp32.h:358:46: error: static assertion failed: Invalid pin specified

fastled_esp32.h:12

Full file path shown:

In file included from /Users/scott/Documents/Arduino/libraries/FastLED/src/platforms/esp/32/fastled_esp32.h:12,
                 from /Users/scott/Documents/Arduino/libraries/FastLED/src/platforms.h:36,
                 from /Users/scott/Documents/Arduino/libraries/FastLED/src/FastLED.h:54,
                 from /Users/scott/Documents/Arduino/libraries/M5AtomS3/src/./utility/LedDisplay.h:4,
                 from /Users/scott/Documents/Arduino/libraries/M5AtomS3/src/M5AtomS3.h:6,
                 from /Users/scott/Documents/GitHub/M5Unified-ESP_IOT_Nov24/ESP32_M5Unified/ESP_IOT/Defines.h:467,
                 from /Users/scott/Documents/GitHub/M5Unified-ESP_IOT_Nov24/ESP32_M5Unified/ESP_IOT/src/SensorClass/KeyUnitSensorClass.h:3,
                 from /Users/scott/Documents/GitHub/M5Unified-ESP_IOT_Nov24/ESP32_M5Unified/ESP_IOT/src/SensorClass/KeyUnitSensorClass.cpp:2:
/Users/scott/Documents/Arduino/libraries/FastLED/src/platforms/esp/32/clockless_rmt_esp32.h: In instantiation of 'class ClocklessController<23, 72, 72, 144, (EOrder)66, 0, false, 5>':
/Users/scott/Documents/Arduino/libraries/FastLED/src/chipsets.h:605:7:   required from 'class SK6812Controller<23, (EOrder)66>'
/Users/scott/Documents/Arduino/libraries/FastLED/src/FastLED.h:109:52:   required from 'class SK6812<23, (EOrder)66>'
/Users/scott/Documents/Arduino/libraries/FastLED/src/FastLED.h:304:39:   required from 'static CLEDController& CFastLED::addLeds(CRGB*, int, int) [with CHIPSET = SK6812; unsigned char DATA_PIN = 23; EOrder RGB_ORDER = (EOrder)66]'
/Users/scott/Documents/GitHub/M5Unified-ESP_IOT_Nov24/ESP32_M5Unified/ESP_IOT/src/SensorClass/KeyUnitSensorClass.cpp:124:54:   required from here
/Users/scott/Documents/Arduino/libraries/FastLED/src/platforms/esp/32/clockless_rmt_esp32.h:358:46: error: static assertion failed: Invalid pin specified
     static_assert(FastPin<DATA_PIN>::validpin(), "Invalid pin specified");
                   ~~~~~~~~~~~~~~~~~~~~~~~~~~~^~

Any ideas?
Should these errors be added to the GitHub?

thanks,
scott

@brrainz

I just got my M5AtomS3 running with M5Unified (with very little changes from my M5Stick display code - other than fonts.) The buttons changed, and I'm not sure what a double click is yet..

Anyway, your reference to the "static pin value" is where I'm stuck as the M5AtomS3 references the FastLED.h and doesn't compile. I actually want to use FastLED.

Assuming this is the same error, can you document how you got it to compile? (If not I'll post my own problem).

/Users/scott/Documents/Arduino/libraries/FastLED/src/FastLED.h:304:39:   required from 'static CLEDController& CFastLED::addLeds(CRGB*, int, int) [with CHIPSET = SK6812; unsigned char DATA_PIN = 23; EOrder RGB_ORDER = (EOrder)66]'
/Users/scott/Documents/GitHub/M5Unified-ESP_IOT_Nov24/ESP32_M5Unified/ESP_IOT/src/SensorClass/KeyUnitSensorClass.cpp:124:54:   required from here
/Users/scott/Documents/Arduino/libraries/FastLED/src/platforms/esp/32/clockless_rmt_esp32.h:358:46: error: static assertion failed: Invalid pin specified
     static_assert(FastPin<DATA_PIN>::validpin(), "Invalid pin specified");
                   ~~~~~~~~~~~~~~~~~~~~~~~~~~~^~

I've been using the export binary from Arduino for a couple years. These are put on a server so an OTA can occur.

To my surprise, I made some changes, repeated my process - but the update never happened.

That's when I found out the name of the binary file was changed from:
m5stick_c_plus to m5stack_stickc_plus

I haven't found any documentation on the name of the binary, but I assume it related to the board (and mine is still: M5StickCPlus).

I had been using library 2.0.4 but then upgraded to 2.0.7
and now I see the version changed to: 0.4.3
And the web page says to use the M5Unified version. For me that's
a bridge too far right now.

Arduion is version 1.8.19

Is there any documentation on the versions and how the binary names are created? I did just see this (thanks). https://docs.m5stack.com/en/platform

I especially need to have a binary that is the same memory configuration as my 2.0.4 M5 and ESP32 since the OTA has to work for 100's of installed versions.

thanks.

@ajb2k3 Thanks for reply. My question is what happens in the example stated when the M5Atom is using the ATOMIC PortABC Extension. In this case, there are 2 I2C ports.

So if my button is plugged into the M5Atom, it uses one set of pins, but if plugged into the Extension, it's a different pin set (and plugged into the red one as you state.)

I just did some testing and with an EPROM setting I can state which of the 2 plugs (and associated pins) to use. Next time it's powered on - the buttons work in the new plugin.

Unfortunately the changes won't work unless POWER is cycled (rebooting isn't enough). Actually after changing the pins, rebooting will start looking at the different pin, and it won't work (without the POWER cycle.)

So again, I was wondering what developers do with this plug-n-play vision without hardcoding all the devices and knowing where they are plugged in. I have the PBHub but haven't played with it yet (but I think it has a naming issue as well, eg. plug1 in slot1, etc).

This dynamic configuration is where a JSON (or equivalent) configuration could be specified and stored in EPROM.

Thanks.

Re: How to use multiple Units wired via GROVE? PbHub?

Following up on my earlier post. I have a single binary code base (same .ino) that needs to be configured at runtime based on which sensors are plugged into which ports and bus kind (UART, GPIO or I2C).

Question: How do others manage this plug-n-play vision?

For example, I currently send a MQTT or BLE message to my devices with configuration values when it cannot be determined at runtime.

Example M5 Atom

The M5 Atom has the PB port out the back. This has KEY pin 32 and DATA pin 26. I can plug in a push button sensor.

But if I plug in the same push button sensor into port PB of the
ATOMIC PortABC Extension Base - it uses keys: 23 and 33.

As mentioned in the PortABC reviews:

So useful in an M5 ecosystem where some sensors still use UART or GPIO for integration. With that extension base, your Atom ends up with so many integration ports (2 x I2C, 1 UART, 1 GPIO) using YH2.0-4P connectors in a very compact form.

Sensor Mapping

I envision a JSON file that defines this kind of mapping (sensor to pins and ports).

@felmue sadly that is the button example I mentioned also doesn't work.

So at present the new M5 Stick Plus-2 won't work as a replacement (and luckily more of the red M5 was found for our customers to use).

thanks,

M5Stick-C-Plus2

M5Stick C Plus2

It seems the "incremental" improvement of the M5Stick-CPlus to the Plus2 is more than "incremental', especially as they switched to the M5United - which definitely changes things.

Anyway, after going through some changes, I can get my main M5Stick-C-Plus application working with WIFI, MQTT, and BLE. Also the Display works nicely. So I can send MQTT messages to change the display (even a long press button A message) - so I can control the device.

But I cannot get the Button A and B to work. So I cannot control via button press (long or shot pressing of A or B).

M5 Buttons do not work

I have even loaded the sample and the buttons don't work. button.ino

Easyloader demo works!

After dusting off a Windows PC, I "Download Windows Version Easyloader"
and that version works with buttons and all.

Driver?

Only thing I don't know is if I've done correctly is loading the device driver from my Mac computer: CH9102 I actually don't know how that's done, but all my other M5 devices work nicely (M5 Atom, M5 Core 1/2, and M5 Stick C Plus 1)

Any help would be appreciated.
thanks

Is there a sensor in the M5 set that lets one control the on/off of a powered wire (like a light switch)? I have the M5PowerSocket and it works nicely (MQTT and BLE), but how could a house with a lot of light (or other switches) be hooked up to many M5 controllers (like Atom)?

I assume the power to the switch could power the M5 and then a sensor could control the wire and it's power.

thanks.

It turns out that part of the solution is sending the host mode to the ATOM. My code above did not do that (thus none of the commands were working.)

Not knowing the full state machine of the ATOM QR, I somehow assumed host and continuous were opposite modes - but I was mistaken.

I'm still unclear on how to send the Setup Code Prompt that is shown in the QR code.

So I have a version that makes no sounds - but I'm unclear if it was totally from the Serial2.write calls, and not from the scanning of that Setup Code Prompt mentioned
here

thanks,

@flypeek Ok, that might be how to perform those operations via scanning the QR code itself, but how can I send the same messages as I showed in the previous post?

I have turned off the QR scanning of these code, partially because I don't want clients to goof it up. I also got into a mode that was hard to get out of (can't remember exactly).

Anyway, shouldn't I be able to send the messages with the Serial2.write?

Thanks,