@ollie said in Unstable program uploading to M5Stack Fire.:

Liemph, thanks for sharing your observations.

I am totally new user of M5Stack Fire. My goal is to use it for teaching and for that reason, I would like to keep it simple and use only UIFlow and not to use Arduino or external Python tools.

In your case, why did you prefer Arduino over UIFlow?

My experience was that after many hours of changing the IDE versions and M5SF firmware, I was not able to download any code. After switching to flow.m5stack.com and selecting the latest M5SF firmware I was able to download and do it without USB cable.

PS. In your case study, I believe that the explanation is in the hardware reset when you are changing the bases.

For the last few days, using the Arduino IDE I developed my codes related to IMU with my Fire and got frustrated since the Fire did not respond at all (blank LCD). I tried the same codes on M5Stack Grey and they worked perfectly. I think something was wrong with my Fire. Then I burned my Fire with the UIFlow firmware and for the time being, the Fire works well. But I have to use the Singapore server since the one provided by the server in China is not stable. Now I am learning the new graphical language.

@rashedtalukder make sure the Sensor conected the PortA. if after upload the Arduino example code. it still not working. you could contact the store. and provide video or picture. then they will help you.

@bob1996w I meet the same problem, I think I can answer your last question about RGB. I found code on M5Stack_NeoPixelTest.ino

#define M5STACK_FIRE_NEO_NUM_LEDS 10 #define M5STACK_FIRE_NEO_DATA_PIN 15 Adafruit_NeoPixel pixels = Adafruit_NeoPixel(M5STACK_FIRE_NEO_NUM_LEDS, M5STACK_FIRE_NEO_DATA_PIN, NEO_GRB + NEO_KHZ800);

NEO_GRB was the data stream order flag according to the comment. GRB & RGB orders different!

There were similar flags for FastLED, working code shows below

FastLED.addLeds<WS2812B, M5STACK_FIRE_NEO_DATA_PIN, GRB>

https://rosolinoblog.wordpress.com/2020/01/29/adesso-gioco-con-questo/

@butch said in Identify M5Stack Fire Revision & Issues:

@jpk Was there ever any response / resolution to this question regarding Fire

Hi Butch,
not really. But they put some more informations on the webpage. Which does not contribute to clarify things.

@m5stack
@lukasmaximus
In the mean time there are a lot of modules and there is more and more documentation. But the documentation is really a bit annoying and not always clear...Questions in this forum are not really answered. Initially I really was impressed by the m5stack, but this lack of quality/documentation is a bit disappointing.

Want an example? Maybe you can sort it out (b.t.w it is still the same question of the first post in this thread):

1.) Revisions (new information on the page)
See this page, scroll down to "Version-Change"
https://docs.m5stack.com/#/en/core/fire?id=version-change
But surprise, my PCB revision ("2018. 2A") is not even listed.. :-?
According the numbering scheme I own a PCB before "Initial public release" (or it is hex_2A=dec_42?)...?

2.) I2C Adresses used by the equipment
https://m5stack.oss-cn-shenzhen.aliyuncs.com/image/m5-docs_table/I2C_Address.pdf

The "Fire is not explicetly listed here, but it should be part of "M5Core" section.
Again: Revisions (see 1.)) are not taken into account here.
==> Based on this information (0x68, see first post) I should have a MPU6886 (=latest 2019 PCB revision acc 1.)) installed...?
But this does not match the fact, that I have an old and undocumented PCB revision...

3.) As the "MPU9250 Basic Example Code" is working for me, I assume I have a MPU9250 installed, which again acc. 1.) would mean I have a PCB revision "2019.7".

4.) In the "official" (?) store
https://www.aliexpress.com/store/product/M5Stack-NEW-PSRAM-2-0-FIRE-IoT-Kit-Dual-Core-ESP32-16M-FLash-4M-PSRAM-Development/3226069_32847906756.html?spm=2114.12010612.8148356.5.1adc593auFAMct

There is still written "9DOF: SH200Q+BMM150", even though the latest version should be "MPU6886" acc. 1.)

Confused? :)

jpk

I had similar problems, here you find my way for solving these

I made a hour counter using UI-Flow. When i test it using the run button of UI-Flow it works fine, but when i try downloading the program to the m5stack it also freezes.

After adding more program code, the testing also fails because the py-code where re-sorted by UI-Flow and some procedures where located at the end and are not reachable for the main loop. After manually sorting the procedures in a correct order the program runs fine again but downloading is again not possible.

The cause of this behaviour is that UI-Flow stores the complete blockly-file (.m5f-file-type) in addition to the py-code to the m5stack. Therefore i used vs-code to transfer the py-code directly to the m5stack without the blockly-file and the program runs.

My conclusions for big programs:

they will be resorted by UI-Flow in a unexpected manner they can't download with UI-Flow, i belive the cause is located in a memory limitation but they can be transferred by using vs-code, to do this see also the m5stack video: https://www.youtube.com/watch?v=Y9pOWgsNgKk

@lordinchcape if you want compiles quickly, you should use platfromIO. Not Arduino IDE

Hi @Efried are you using micropython/uiflow firmware or arduino? make sure you have installed the cp210x drivers first if you haven't already https://m5stack.com/pages/download I made a few simple tutorials on hackster.io to get started with http requests, hope they can be of use to you.
https://www.hackster.io/lukasmaximus89/m5stack-and-mit-app-inventor-47bd32
https://www.hackster.io/lukasmaximus89/m5stack-micropython-simple-web-server-20a4c4

Due to hardware flaws, sometimes when interfacing with some of the units there is an audible hiss. Unfortunately since it is a hardware flaw the only solution is to use code to reduce the volume of the hiss.

in Arduino it should be something like
dacWrite(25,0)

Python
dac0 = machine.DAC(25)
dac0.write(0)

Yes all grove ports output 5V

@ajb2k3 Amazon.it

Check your usb cable, sometimes the cables dont work.

@fonix232 said in M5Stack FIRE - should I return it?:

the bottom boards seem to be swollen as well (the bit where the battery is connected to the PCB is pushed and warped upwards, making stacking quite difficult and in some cases, impossible).

Seems odd. Can you post a picture? Maybe it’s a result of a swelling battery. There were also some battery issues earlier with their vendor/supplier. Either way, the M5Stack team provides good customer service. I’m sure they will address your problems.