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,

I have the Atom QR Code reader and it's working nicely. I like the continuous mode (as I support disabled users who cannot touch buttons.)
ATOM QR Code Kit

Unfortunately I've tried sending the appropriate commands to turn off the sounds and nothing works. Any ideas?

See the Full Testing Example

The following binary commands are documented here.

• Startup

uint8_t wakeup_cmd       = 0x00;

 Serial2.begin(
        9600, SERIAL_8N1, 22,
        19);
 Serial2.write(wakeup_cmd);

 delay(50);

• Startup "boot" sound (still makes startup sound)

uint8_t bootSoundProhibit[]   = {0x08, 0xC6, 0x04, 0x08, 0x00, 0xF2, 0x0D, 0x00, 0xFE, 0x27};

Serial2.write(bootSoundProhibit, sizeof(bootSoundProhibit));

• Detection sound (still makes detection beep)

uint8_t prohibit_prompt_sound_decode_mode_cmd[]  = {0x07, 0xC6, 0x04, 0x08, 0x38, 0x00, 0xFE, 0xEF};

Serial2.write(prohibit_prompt_sound_decode_mode_cmd, sizeof(prohibit_prompt_sound_decode_mode_cmd));

None of these are changing the sounds in the example I posted.
Any help would be appreciated. (Beep sounds are not liked while
in a quiet museum for example).

thanks,

Unfortunately as of today, my Battery isn't working again. I can update and run will using USB power but unplugging kills the M5Core.

That's very enlightening. I've since got the battery to work but it seems to be working along the lines you mention. I actually exchanged batteries with Core 1 and it worked perfectly. But the Core 2 has some issues.

When the battery is dead, plugging in won't bring ut alive until maybe 20 minutes.

So I don't think it's totally the battery but rather how it connects and Core 2 management of the power.

Strange.
Thanks

@teastain The 4 devices I'm using are the ESP-32 board, M5ATOM, M5Core2 and M5StickC-Plus. Are all three M5's with their 1 GROVE connection all called Port B? I use the HAT as well.

Reading the code of the RF433 provided by M5Stack, it says Port B (which the M5Stack is using). So I confirm @ignoramati results of nothing.

Separate topic is needed for all the Port and I2C designs.
Thanks for the port info. I've had trouble figuring that out. I'm also trying to figure out the I2C design. I have a PbHUB to use too. I really want the many sensors to be available and dynamically turned on based on a configuration file (so all compiled into the same executable).

I'm just now trying to do the same thing, and the sample code doesn't do anything (as you pointed out). I'm using an M5Stick-C-Plus and I'm still confused on the Port A/B thing. So maybe it's not using Port B correctly?

A better example program would really go a long way!

I'm also looking at what to do with these two RF433 units. I want to send a RF signal to the TV to change the channel. I assume this is what can be achieved (after I know the correct codes).

The following example looks like going down the right direction (albeit with a different RF device).

If anyone has other examples for the M5Stack and RF433 units specifically that would be great.

I have the Core2 original and now the v1.1. But the new unit is not working
when unplugged.

Are there any special v1.1 calls to get the battery to work? Just like the
vibration needing a new call in v1.1, is there something special?

The battery voltage is working (which I've used for battery percentage).

    batVoltage = M5.Axp.GetBatVoltage();
    batPercentage = (batVoltage < 3.2) ? 0 : ( batVoltage - 3.2 ) * 100;

I've tried the following to no avail.

    M5.Axp.SetLcdVoltage(3300);
    M5.Axp.SetBusPowerMode(0);
    M5.Axp.SetCHGCurrent(AXP192::kCHG_190mA);

Is it possible the battery isn't working? It's plugged in (after opening the unit).
thanks.

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,

Thanks for the detailed replies to my wire questions. Maybe with
this more concrete example you could let me know what I need.

I have the following:

1. M5 Atom Lite (or M5 or Core2)
2. Key Unit (Button)
3. PIR Motion Unit
4. Ultrasonic Distance
   4.a Unit I/O
   4.b I2C

I can get the Key Unit working using 1 GROVE wire.
#define KEY_PIN 33

I assume to connect the other Units I use the Grove-T Connector.

But how do I talk to the PIR and other Units?

a: To connect the PIR motion sensor, do I need a HUB?
b: Adding the Distance Unit: Would the I/O (4a) or I2C (4b) be
easier to integrate?

In this example,
a. is the PbHUB required?
b. Or is the PaHUB better?

I'm using straight Arduino C as I have a complex
capability built already. I just want to add some
of these Unit sensors.

Thanks.
scott

Ok, now I'm confused. Can you explain the difference between I2C and Unit I/O? I just want to plug in the the HUB and have multiple Unit's.

I'm ordering the PbHUB but also want the Ultrasonic Distance, but it comes in 2 modes:

Ultrasonic Distance Unit I/O (RCWL-9620)
Ultrasonic Distance Unit I2C (RCWL-9620)

Or do I get the PaHUB ??

Will need to try it out (once I get one). But how would C code know which PIN is for which device? The examples all use a specific pin, so I assume there is a way to specify once they are plugged in?

My challenge in general is to extend my M5 with plug-n-play sensors - but without modifying the base code. The HAT on M5 works but some devices are too slow if they aren't plugged in (PIR is fast but LUX is slow).

So it would be great if there was a way to know what sensors are active. Worst case is a configuration message over BLE or MQTT denoting what's plugged in and which pins, etc. I'm doing that with LUX as once it gets a bad reading, it turns that code off. But a MQTT message can ask to recheck and turn it on.

Finally is PbHUB required to plug in a couple sensor units? (A) if same unit kind, (b) different unit. PIR and KEY for example.

Thanks

I've been using the HAT for the M5 successfully but there is only one at a time. I just got my first UNIT running connect to the M5 (the Key Unit touch button).

My question is how am I supposed to run multiple sensor UNIT's using all the daisy chaining of the GROVE wires? I just came upon the PbHUB concept that seems to be needed. Can someone explain the PbHUB?

My real question is how does the code work when almost all are using the same PIN numbers - and now there will be multiple UNIT's running at the same time. What PINS do they user? Is the PbHUB the way to change those PIN numbers for say 4 push button Keys?

Please help enlighten me on how one develops code for this plug-n-play variability?

Thanks.