Navigation

    M5Stack Community

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    1. Home
    2. Mati
    3. Posts
    • Continue chat with Mati
    • Start new chat with Mati
    • Flag Profile
    • Profile
    • Following
    • Followers
    • Blocks
    • Topics
    • Posts
    • Best
    • Groups

    Posts made by Mati

    • RE: UIFlow 1.8.8

      @arno well already 8 months since zigbee was on sale and guess what ;) still no UIFlow
      @m5stack i hope ZigBee will born nice and shine after 9 month's of development.

      About C3 - you can use pure micropyhon its already there:
      https://github.com/micropython/micropython/releases/tag/v1.17

      posted in Official Updates
      Mati
    • RE: UIFlow 1.8.6

      @ajb2k3 said in UIFlow 1.8.6:

      @mati said in UIFlow 1.8.6:

      @m5stack said in UIFlow 1.8.6:

      we will update the tutorial as soon as possible

      in my case all is working fine on core2 LCD module is connected over PortA

      Have you updated the firmware on the colour lcd?
      I get the framebuf error if I don't add the init screen block

      Nope, just out of the box and go. First try with Atom lite fail but on core2 and init in the setup all looks legit.

      posted in Official Updates
      Mati
    • RE: UIFlow 1.8.6

      @m5stack said in UIFlow 1.8.6:

      we will update the tutorial as soon as possible

      in my case all is working fine on core2 LCD module is connected over PortA

      posted in Official Updates
      Mati
    • RE: UIFlow 1.8.6

      LCD color vs Atom lite
      Traceback (most recent call last):
      File "flow/m5cloud.py", line 82, in _exec_fun
      File "<string>", line 20, in <module>
      File "units/_lcd.py", line 128, in fill
      AttributeError: 'Lcd' object has no attribute 'frame_buf'

      Traceback (most recent call last):
      File "flow/m5cloud.py", line 82, in _exec_fun
      File "<string>", line 20, in <module>
      File "units/_lcd.py", line 128, in fill
      AttributeError: 'Lcd' object has no attribute 'frame_buf'

      Traceback (most recent call last):
      File "flow/m5cloud.py", line 82, in _exec_fun
      File "<string>", line 22, in <module>
      File "units/_lcd.py", line 169, in show_on
      File "i2c_bus.py", line 101, in write_mem_list
      MemoryError: memory allocation failed, allocating 64800 bytes

      posted in Official Updates
      Mati
    • RE: Product failed. Burning, Downloading, finding where to get API get.

      ahh one more think with i just recall :D
      when my core 2 was at home by using M5Burner by mistake i just preload UIflow for Core not for Core2 and this was a same loop as you can see

      posted in Core 2
      Mati
    • RE: Product failed. Burning, Downloading, finding where to get API get.

      @edawen said in Product failed. Burning, Downloading, finding where to get API get.:

      @mati said in Product failed. Burning, Downloading, finding where to get API get.:

      a

      Putty doesnt do any good. I did find, by accident, that if i went into monitor, and pressed Reset instead of Send, it would print out this ;

      =================
      COM8
      =================
      ets Jul 29 2019 12:21:46
      
      rst:0x1 (POWERON_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
      configsip: 0, 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:1044
      load:0x40078000,len:8896
      load:0x40080400,len:5816
      entry 0x400806ac
      ets Jul 29 2019 12:21:46
      
      rst:0x1 (POWERON_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
      configsip: 0, 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:1044
      load:0x40078000,len:8896
      load:0x40080400,len:5816
      entry 0x400806ac
      M5Core2 initializing...axp: vbus limit off
      axp: gpio1 init
      axp: gpio2 init
      axp: rtc battery charging enabled
      axp: esp32 power voltage was set to 3.35v
      axp: lcd backlight voltage was set to 2.80v
      axp: lcd logic and sdcard voltage preset to 3.3v
      axp: vibrator voltage preset to 2v
      [E][sd_diskio.cpp:739] sdcard_mount(): f_mount failed 0x(3)
      OK
      [E][sd_diskio.cpp:739] sdcard_mount(): f_mount failed 0x(3)
      Addr:0x34 - Name:Axp192
      I2C Axp192 Found
      Addr:0x38 - Name:CST Touch
      I2C CST Touch Found
      Addr:0x68 - Name:IMU6886
      I2C IMU6886 Found
      Addr:0x51 - Name:BM8563
      I2C BM8563 Found
      

      I'm not sure what to Send, in monitor or Putty. This doesn't show up in Putty, as text or as garbage. There is no SD card inserted and it is at the red "SDCard Find failed" prompt on the Core2.

      This is after I shutdown the PC, removed and deleted the driver and installed CP210xVCPInstaller_x64_v6.7.0.0, the same driver installed bu UIflow. M5Burner will still not work. I have not followed the Cold Start Method yet. That will be tomorrow.

      Regards.

      this proof there is a communication, with is fine but core2 is in the boot loop.
      What about opening or to be more precision remove bottom where is a battery.
      After opening inspect both buttons maybe one stuck and this is a problem with loop.

      posted in Core 2
      Mati
    • RE: Product failed. Burning, Downloading, finding where to get API get.

      Hey @Edawen
      bit strange, what about open COM8 via putty the is any output ?
      In case on Core2 please open it and disconnect internal battery and try again.

      But more or less this could be a service tickate case.

      posted in Core 2
      Mati
    • RE: Unit V2 GUI Doesn't Have All Features

      @kylecat1 Hey,

      yes its could be old FW burned, i think i was the same with my unit,
      go to https://docs.m5stack.com/en/quick_start/unitv2/update
      and follow the guide.

      posted in PRODUCTS
      Mati
    • RE: UIFlow 1.8.4

      @m5stack said in UIFlow 1.8.4:

      We are very sorry, we are working hard to supplement the support of related modules

      thx for reply, maybe all will be happy if we can see some roadmap with HW implementation.

      posted in Official Updates
      Mati
    • RE: UIFlow 1.8.4

      @m5stack what about zigbee ? soon we gonna celebrate 5th month of waiting ;)
      0_1631533924883_338f69d2-708b-47b7-8bd1-5b6d31a8cae7-image.png

      posted in Official Updates
      Mati
    • RE: UIFlow 1.8.2

      @ajb2k3 said in UIFlow 1.8.2:

      Cant connect M5Stamp to Uiflow. firmware installed but not connecting and no wifi host

      remove Connection to pin0 and EN
      If programator is connected device is in the download mode.

      posted in Official Updates
      Mati
    • RE: UIFlow 1.8.1

      Lorawan868 - element got a wrong python lib link
      0_1627064340546_6013faa8-df07-46d3-a3ea-a7e8306aae9e-image.png
      0_1627064287131_cf05bf81-1501-4c90-9a4c-417267881754-image.png
      Its should be 868 not 915

      gif

      @m5stack when this will be fixed ? or again there is no issue ?

      posted in Official Updates
      Mati
    • RE: Unit GPS + Unit LoRaWAN 868

      Why not ?
      I am able to mix lorawan dut with env 2 and lcd =}
      Where lora is not conected yet ...

      posted in Units
      Mati
    • RE: UIFlow 1.8.0

      @m5stack said in UIFlow 1.8.0:

      @mati I think the module name is from base.DTU_LoRaWAN import DTU_LoRaWAN......a is lowercase

      This is a problem in the UiFlow, after importing lorawan init in the code we have LoRAWAN.

      And what a supprise its fixed now ;)
      0_1626445693403_ecf340f2-2500-49cc-a120-9ded8650835c-image.png

      Day ago was
      0_1626445732051_7394cf47-3223-4bba-a0d9-c88cb891e61c-image.png

      what a nice silent fix =]

      posted in Official Updates
      Mati
    • RE: UIFlow 1.8.0

      @m5stack hmm no luck one tab and still error
      0_1626370025346_36ad29ab-d056-477d-8cbf-ce803e9dd5ea-image.png

      but ... its just bug me so after listing all modules on AtomDUT its turn on you have made a typo in the from base.DTU_LoRAWAN should be base/DTU_LoRaWAN

      from base.DTU_LoRAWAN import DTU_LoRAWAN
      into
      from base.DTU_LoRaWAN import DTU_LoRaWAN

      posted in Official Updates
      Mati
    • RE: UIFlow 1.8.0

      @m5stack indeed it was two tabs !
      Let me check this, thx for a hint.

      posted in Official Updates
      Mati
    • RE: UIFlow 1.8.0

      @m5stack could we get reply about uiflow support for lorawan ?

      posted in Official Updates
      Mati
    • RE: UIFlow 1.8.0

      Hello @m5stack
      #1
      looks like new error popup in combination of Atom Lite and OLED 1.3'' module not only Env2 make error as well.
      Simple remove 'from m5stack_ui import *' fix the problem

      0_1626112386195_7412c482-2c5c-4168-90c8-5f6b899db8ae-image.png

      #2
      Plus AtomLora DUT error ..
      Traceback (most recent call last):
      File "flow/m5cloud.py", line 82, in _exec_fun
      File "<string>", line 3, in <module>
      ImportError: no module named 'base.DTU_LoRAWAN'

      #3
      LoraWan868 + Core2
      'module' object has no attribute 'LORAWAN'

      Do we have any LoraWan support in 1.8.0 ?!

      Regards
      Mati

      posted in Official Updates
      Mati
    • RE: LoRaWAN Unit 868

      Hey,
      just got own DUT Lorawan868, and also looking for some Spec ;)

      posted in General
      Mati