Topics created by konacurrents

@felmue It looks like I need the binary version of getProtocolString. It seems the following is needed for sending an IRData (the mirror of what was learned from receiving.)

/** * Interprets and sends a IRData structure. * @param aIRSendData The values of protocol, address, command and repeat flag are taken for sending. * @param aNumberOfRepeats Number of repeats to send after the initial data if data is no repeat. * @return 1 if data sent, 0 if no data sent (i.e. for BANG_OLUFSEN, which is currently not supported here) */ size_t IRsend::write(IRData *aIRSendData, int_fast8_t aNumberOfRepeats)

And I need a way to get the IrReceiver to provide the IRData information. So It seems this is in the decodedIRData from the IrReceiver.decode call.

/** * Main class for receiving IR signals */ class IRrecv { public: IRData decodedIRData; // Decoded IR data for the application }

I assume I save these values with the associated functions (volume up, change channel, etc). I see that a lot of those functions are defined for various known operations, but for now I will learn from the IR receiver.

Thanks for the help.

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

Hello @konacurrents

for me both button examples (M5StickCPlus2 library / M5Unified library) work as expected.

Are you using the latest version of all the libraries used?

Thanks
Felix

The r-relay-unit looks promising. But how do I get power to the controller (M5 Atom, etc)?

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,

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

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,

@konacurrents @frameworklabs

I'm now onto getting the M5Core2 to work with my existing infrastructure. Looking at the M5United, I cannot see how that would be used (as the readme doesn't have a Core2 define).

It sure seems that the M5 code provided by M5Stack and others shouldn't reuse the M5 class name. Instead they should have say M5Core2 instead of M5, and M5Core2Display not M5Display.

Sure it works for the standalone programs, but trying to merge code would need something like
your M5United. Looking under the covers of say M5Core2's M5 class, they include their own Lcd (for example) which isn't compatible with other Lcd's.

As I mentioned in the previous post, for the ATOM pulling over the LED was relatively easy. But for the M5Core2 there is a lot of code that overlaps with the M5 base (starting with M5Display).

eg. M5Display.h is defined 3 places (and I use the M5StickCPlus in my main code base).

./libraries/M5Core2/src/M5Display.h
./libraries/M5StickCPlus/src/M5Display.h
./libraries/M5Stack/src/M5Display.h

I'll look more at M5United and if you can point to getting their M5DIsplay working that would help.
thanks

I also encountered the same problem when using M5 core 2. My macOS system version is 10.14.6