Posts made by felmue

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

Hello @gadgetguy

I can confirm that enabling RFID prevents M5Dial from connecting to WiFi.

After enabling RFID in M5Dial.begin(cfg, true, true), try M5Dial.Rfid.PCD_AntennaOff() to temporarily disable RFID while using WiFi, then after disconnecting from WiFi enable RFID again with M5Dial.Rfid.PCD_AntennaOn().

Thanks
Felix

Hello @desmbr

I created an UIFlow2 light sleep example for M5CoreInk but I cannot confirm the display fading you are reporting.

You can find my example in the UIFlow2 ProjectZone called: M5CoreInk_LightSleep_Test_UIFlow2.2.3

Thanks
Felix

Hello @konacurrents

yes, that silk screen can be a bit misleading.

There is function IrReceiver.getProtocolString() which gives you the protocol (e.g. NEC, Samsun, etc.) to use when sending a learned code. Have you tried that?

Thanks
Felix

Hello @konacurrents

by Atom's port extender do you mean M5AtomABC? If yes, the middle port is using GPIO33 and GPIO23 (not GPIO32) - see here.

Thanks
Felix

Hello @ChuckInDallas

there is a POWER SWITCH at the bottom. See here. Make sure it is in the on position to charge and/or power M5Core.

Thanks
Felix

Hello @cthulu

you want to check against ESP_SLEEP_WAKEUP_EXT0 as wake-up cause since the touch interrupt line (GPIO36) is setup using esp_sleep_enable_ext0_wakeup().

BTW: ESP_SLEEP_WAKEUP_TOUCHPAD is meant for an ESP32 feature where a GPIO can act as a touch sensor. See here (Which is different from the touch screen).

Thanks
Felix

Hello @myscho151

you could use an M5StickCPlus - see stock example here.

Thanks
Felix

Hello @taunushexe

please find an M5Dial RFID example reading UID and data in the UIFlow2 Project Zone: M5Dial_RFID_ReadUID_ReadData_UIFlow2.2.2

Thanks
Felix

Hi guys

please find an M5CoreS3 example in UIFlow2 Project Zone controlling a servo. It's named: M5CoreS3_Servo_Example_UIFlow2.2.2

Thanks
Felix