ATOM DTU NB MQTT Example dosn't work
-
Hello Community,
i have an ATOM DTU NB iot device and i try the example flow in UIFlow Base - DTU - NB-iot - Load Example. I changed the mqtt-Server and credentials but i get an error.
Serial Output:
"rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 188777542, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0018,len:4
load:0x3fff001c,len:5228
load:0x40078000,len:12908
ho 0 tail 12 room 4
load:0x40080400,len:3512
entry 0x4008063c_ __ _
_ ()/ | | _____ __
| | | | | || |/ _ \ \ /\ / /
| || | | | | () \ V V /
_,||| ||___/ _/_/APIKEY: XXXXXXXX
Traceback (most recent call last):
File "main.py", line 36, in <module>
File "base/DTU_NB.py", line 50, in mqtt_to_connect
File "base/DTU_NB.py", line 75, in mqtt_ischeck_connect
IndexError: list index out of range
MicroPython f78d1e78a-dirty on 2022-11-24; M5Stack with ESP32
Type "help()" for more information.
"SIM is inserted. What i'm doing wrong? Can somebody help?
-
Hello @BennoB
have you tried to run the example without modification, e.g. connecting to
mqtt.m5stack.com
as a test? Does that work?Thanks
Felix -
The same. Nothing changed. Load example, Download to device, open Terminal and reset device with button B.
rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 188777542, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0018,len:4
load:0x3fff001c,len:5228
load:0x40078000,len:12908
ho 0 tail 12 room 4
load:0x40080400,len:3512
entry 0x4008063c_ __ _
_ ()/ | | _____ __
| | | | | || |/ _ \ \ /\ / /
| || | | | | () \ V V /
_,||| ||___/ _/_/APIKEY: XXXXXXXX
Traceback (most recent call last):
File "main.py", line 36, in <module>
File "base/DTU_NB.py", line 50, in mqtt_to_connect
File "base/DTU_NB.py", line 75, in mqtt_ischeck_connect
IndexError: list index out of range
MicroPython f78d1e78a-dirty on 2022-11-24; M5Stack with ESP32
Type "help()" for more information. -
Same issue with downgraded V1.9.9
-