Posts made by felmue

Hello @nefasto

have you tried the RGB blocks in UIFlow2? You can find them under Hardware.

An example can be found in the UIFlow2 Project Zone: M5CoreS3_RGBUnit_PortA_UIFlow2.1.8

Thanks
Felix

Hello @mukul_100_

No.

I think you are still on the library I incorrectly linked to in my example before.

Incorrect library: https://github.com/arduino-libraries/ArduinoRS485

Library I used: https://github.com/m5stack/ArduinoRS485

Thanks
Felix

Hello @mukul_100_

yes.

Thanks
Felix

Hello @bsmorgan

well, M5CoreInk cannot shutdown in the first place when running from USB - see schematic here.

A modified USB-C cable (with 5 V line cut) might help with debug statements in this case.

Thanks
Felix

Hello @mukul_100_

I linked the incorrect variants for RS485 and Modbus libraries. Sorry about that. I fixed the example. The libraries I used are the ones from M5Stack.

https://github.com/m5stack/ArduinoModbus
https://github.com/m5stack/ArduinoRS485

Thanks
Felix

Hello @HappyUser

the code works for me using M5Core2v1.1 and the following modifications:

//#include <M5Core2.h>   <-- replace this with below lines
#include <M5Unified.h>
#include <Wire.h>

    M5.begin();
    Wire.begin();  <--- add this after above line

Thanks
Felix

Hi guys

I don't think you can use pre-compiled Meshtastic firmware as some GPIOs used in pre-compiled firmware cannot be selected in LoRa868 V1.1 module.

From the M5Stack Meshtastic variant.h file and the previous LoRa module I understand the following GPIOs are used:

SCK   : GPIO18
MISO  : GPIO19
MOSI  : GPIO23
CS/NSS: GPIO5
IRQ   : GPIO36
RST   : GPIO26

However the newer LoRa868 V1.1 module doesn't allow to select GPIO36 as IRQ nor GPIO26 as RST.

So I think you either need to compile Meshtastic firmware (with the correct GPIOs) yourself, get the older LoRa868 module or modify the V1.1 hardware.

Note: I do not have the necessary hardware to test this myself - so my above conclusions could be incorrect.

Thanks
Felix

Hello @SB12345

ok, I see, hmm.

Have you tried to connect one TOF4m to port A and the other to port C and then setup two I2C busses?

Thanks
Felix

Hi guys

BTW: TOF4m allows to change its I2C address (using set I2C address block in UIFlow2) so you could change the I2C address of one TOF4m, then connect both using a passive hub. This would take PaHub out of the equation.

Thanks
Felix

Hello @ScheduleDisplay

unfortunately that is not possible; all GPIOs (Port A, B and C) and the GPIO used for the side button go directly to ESP32 which is powered off in shutdown mode.

The only two options (I know of) to wakeup M5Paper from shutdown mode are:

• long press of side button
• RTC alarm

Thanks
Felix

Hello @Krmiller

I am not able to reproduce the issue you are describing. Tested with Linux and MacOS client. That said I recommend not using delay() in the loop as it blocks the WiFi background process.

Try replacing loop with below code. (You should see a much quicker response too.)

void loop() {
  static uint32_t t = millis();

  if(millis() > t + 5000)
  {
    t = millis();
    int clientCount = WiFi.softAPgetStationNum();
    Serial.print("Connected clients: ");
    Serial.println(clientCount);
  }
}

Thanks
Felix

Hello @Pajdzian

I measure about 62 mA charging current (at the battery) when using M5Launcher and the same amount when running Cardputer UIFlow2 or Demo firmware (the one preloaded).

So I am curious: what other firmware did give you a slower charging rate?

Thanks
Felix

Hello @sqbaczek

unfortunately I don't have the proper hardware, e.g. TOF4m unit, so I cannot test this myself. Sorry.

BTW: are you aware that in UIFlow1 you use PaHUB channel 0 and 2 and in UIFlow2 you setup PaHUB channel 0 and 1.

Thanks
Felix

Hello @sqbaczek

assuming the programming is correct my best guess would be that the two ToF4m influence each other due to the signal they both send out. Maybe the signal of one gets reflected from the walls and then is picked up by both (and vice versa)?

BTW: have you tried the UIFlow2 instead? Do you get the same results?

Thanks
Felix

Hello @cryptospok

please find an example in the UIFlow2 Project Zone: M5ToughTouchTest_UIFlow2.1.7 showing how to get rid of old / duplicate touch events.

Thanks
Felix

Hello @mtrehy

have you tried to connect only one of the two (M5Scale or Led Bar) to your M5Atom and see if you can make one work at the time?

Thanks
Felix

Hello @r0kh0rd

I think it has been fixed by M5Stack. Check out this example - works for me.

BTW: my example does not work anymore as M5.Lcd.getSPIinstance() no longer exists in M5CoreS3 library.

Thanks
Felix

Hello @r0kh0rd

I am not sure it is still valid, but last year I encountered a similar issue when trying to use the LCD and the SD card together with an M5CoreS3.

Maybe the solution I found at the time might be helpful for your situation as well.

Note: I cannot test this myself as I lack the necessary hardware, e.g. I do not have a LoRa868 v1.1.

Thanks
Felix

Hello @soujiro0725

please find an example here.

Thanks
Felix

Hello @reptilepvp

just try something like below:

label2.setText(str(((ncir2_0.get_temperature_value) * 9) / 5 + 32))

Note: untested as I do not have the necessary hardware to verify.
Thanks
Felix