Posts made by felmue

Hello @KamilB

I do not have the hardware to test this myself, but I think you might want to pull GPIO12 HIGH to make sure you're talking to BMI270 only. See here.

Thanks
Felix

Hello @obstbauer

I think you might want to call cr.begin() in setup to set stuff like the proper I2C address for the library to use. See here.

Thanks
Felix

Hello @andrew-winton

I don't have a RP4 nor do I have the AIN4-20mA module so my tests might be irrelevant for your setup.

Using an RP3 and about every M5Stack I2C unit I have (RFID, Relay4, PaHub, PbHub, EXTIO, etc.), all of them get detected just fine using i2cdetect -y 1.

That said:

• have you verified that there are proper pull-up resistors on SCL and SDA? (RP should have them by default.)
• have you tried with different wires?
• have you tried w/o supplying 12 v? I think it's redundant looking at the schematic. (External 12 V power also produces BUS_5V which might clash with the 5 V from RP.)
• have you tried to reduce the I2C speed? (default seems to be 100k)

Thanks
Felix

Hello @shiva

please have a look in Project Zone example: M5StickCPlus2_UseTimerToCountSeconds_UIFlow2.2.4

It shows how to use a timer (instead of sleep) to count. Using a timer makes sure a button press is honored all the time.

Thanks
Felix

Hello @xxx_yyy

I stand corrected. My apologies. You are absolutely correct: IMU INT in M5StickCPlus2 is not connected to anything. (I was looking at the RTC INT.)

That said - and to answer your original question - yes, it is possible to connect the IMU INT pin to an ESP32 GPIO. Please see here.

However it would only allow to wake ESP32 from deep/light sleep, but not to turn M5StickCPlus2 back on from being powered off due to the fact that IMU is powered from 3.3 V (and not like RTC from VBAT_IN).

Thanks
Felix

Hello @xxx_yyy

IMU in M5StickCPlus2 is running from the battery and IMU INT is connected to the power on logic. So it should be possible to setup WoM, then turn ESP32 off and then upon motion IMU INT turns ESP32 back on again.

Thanks
Felix

Hello @desmbr

indeed, that doesn't look good. I wonder if maybe the internal battery is defective preventing the power rails from reaching the proper voltages.

Edit: first, however I would unplug the hat and maybe try a different USB power supply.

If you still have warranty, I suggest you ask for a replacement.

If not, you might try to open it and disconnect the battery to see if that helps. These pictures I took a while ago might be helpful opening M5CoreInk.

Thanks
Felix

Hello @fkarner

well, while the website iotcreators.com is still up theirs SIM cards no longer seem to be activated. From the iotcreators.com discord server:
a user asks: "... I'm wondering if iotcreators.com is still active ..." and
[STAFF] Afzal answers: "It is not. Sorry. I tried my best to keep it alive"

Thanks
Felix

Hello @fkarner

Miotiq, in my opinion, is a good offer - I tested with one myself. And they list Italy as supported country.

However, when I tried a while ago, the Miotiq SIM did not allow the modem to connect directly to my server. The modem always has to use the Miotiq backend as a proxy. See here.

So for instance the M5Stack MQTT example will not work as the modem cannot connect directly to M5Stack MQTT server.

Thanks
Felix

Hello @fkarner

I get SimStatus: 1 when SIM card is installed and recognized. (I get SimStatus: 0 if I remove the SIM card.)

So yes, it appears that something is either wrong with the SIM card you are using or with the sim card slot in the DTU.

Thanks
Felix

Hello @ewoodier84

hmm, I am not seeing that. I get to select from all three buttons in UIFlow2 V2.2.3 with M5Core2 selected.

The same is true when I load some of my older UIFlow2 programs.

Which browser are you using? I think UIFlow2 only works properly in Chrome. Maybe try to clear the cache?

Thanks
Felix

Hello @fkarner

I get the same error, but it's not fatal. The error stems from the fact that in ATOM_DTU_NB.h a GPIO is defined, e.g.

#define ATOM_DTU_SIM7020_RESET -1

for the SIM7020 reset which isn't connected in the DTU.
If you change that to something like 13 the error goes away.

The program is probably stuck in Inititalzing modem as it tries to check for the SIM card and that it doesn't have a PIN defined.

Have you double-checked that the SIM card is placed in the correct orientation and that it doesn't use a PIN?

Thanks
Felix

Hello @s1y99

reading your other post, I think you already figured that out yourself. It's not possible to jumper LoRa V1.1 so the same GPIOs are used as it were for the older LoRa module.

Both LoRa modules use the same GPIOs for MOSI (23), MISO (19) and SCK (18). However RST and IRQ cannot be jumpered the same; CS/NSS can be jumpered the same.

LoRa (433 old): RST(26), IRQ (36), CS/NSS (5)
LoRa V1.1: RST(25/13), IRQ (35/34), CS/NSS (0, 15, 12, 5)

Note: GPIO numbers above are for an M5Core (Basic).

Please also see schematics here and here.

Just curious. What is preventing you from modifying your firmware to use the GPIOs of the newer LoRa module?

Thanks
Felix

Hello @desmbr

have you checked the boot option? In M5Burner click onto the Configure (yellow) button and then set Boot Option to Show startup menu and network setup. Then click onto Next to set the new boot option.

Thanks
Felix

Hello @fkarner

thank you for the update. So it's confirmed something's wrong with the first SIM7020G. I still suspect the baudrate got changed somehow, especially since you are writing that the LEDs behave normally.

Thanks
Felix

Hello @peolsolutions

just an FYI: M5Stack Fire doesn't have an AXP192 PMU.

I get the feeling some of your posts are AI generated, no? If I am correct I'd appreciate if you could first verify the technical facts before posting.

Thank you very much for your understanding.

Thanks
Felix

Hello @wrs642

Note:

• port A (red) is by default I2C
• port B (black) is by default IN/OUT
• port C (blue) is by default UART

M5GoPlus2 has three port B, none of which is I2C. I2C is only available on MBUS (pins 21/22). Please check schematics here.

Thanks
Felix

Hello @davekc

M5Stamp-C3: PORT-U pins and USB-C are not the same. Check schematics here.

M5Stamp-C3U: PORT-U pins and USB-C are the same. Check schematics here.

Thanks
Felix

Hello @fkarner

hmm, since you already tried changing the modem baudrate I am at a loss what might have gone wrong.

Maybe my serial pass-through example can shed some light onto this issue?

Thanks
Felix

Hello @desmbr

hmm, yes, that doesn't look good.

Have you tried without the hat connected?

Have you tried when running from battery?

Have you tried to fully power off / on M5CoreInk? E.g.

• disconnect USB-C
• press and hold RST button in the back for 5 seconds
• turn back on via side button (or by plugging in USB-C)

Also, are you running the latest UIFlow2 v2.2.3 firmware? Maybe use M5Burner to fully erase first and then reinstall UIFlow2 v2.2.3?

Thanks
Felix