Identify M5Stack Fire Revision & Issues
-
Hello,
it seems there are several revisions of the Fire Kit available, see also here:
http://forum.m5stack.com/topic/1099/m5stack-fire-oldMajor question: How to clearly identify the (latest) revision?
Possible hints on my equipment (ordered in June 2019):
a) On the backside of the Fire PCB there is a label with "2018. 2A"b) According to the shop (Amazon.de/marketplace) I ordered the one with "MPU6050+MAG3110" instead of MPU9250 as 9DOF-Sensor. The paper leaflet inside the package states the same.
The MPU9250 seems to be the current version, acc. to https://docs.m5stack.com/#/en/core/fire.c) Running the "I2C Scanner" from GitHub reveals only two I2C-adresses:
0x68 (which could be the 9250 or the MPU6050)
0x75 (which should be the IP5306)
(info from: https://docs.m5stack.com/#/en/core/fire)
==> In this case: Where has the MAG3110 gone?Fun Fact: 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 written even s.th. else. for 9DOF-Sensor
9DOF: SH200Q+BMM150I am a bit confused.
Thank you & best regards
jpk -
Can you show purchase link, MPU6050+MAG3110 has not been sold for a long time....
-
For sure. Purchase link:
https://www.amazon.de/gp/product/B07DJ3J3MZ/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1 -
@jpk
Hello,I have purchased one from the same seller.
After i have updated the firmware to v1.3.2 the gyro sensor not working.
Tried to read the values from "Hardware ->imu" i.e Acc X,Y & Gyro X,Y.Result: Error, imu not found.
Could you please let me know is it genuine or need it to be return.
Thank you.
Kind regards,
Hari. -
Hi @hari what about if you use a different revision of the firmware, you mentioned that only after you updated to 1.3.2 it stopped working. 1.3.4 is the latest firmware now and if you are programming in uiflow you need to make sure you are using flow.m5stack.com/beta . I doubt its a hardware issue, so I wonder if you can try the newer firmware and website and see if the problem persists
-
Hi @lukasmaximus thank you for your suggestion.
I will try that.Could you please check the attached image of FIRE.
Please tell me is it correct FIRE version.
 )Purchased from the below link.
link textBest regards,
Hari -
@hari said in Identify M5Stack Fire Revision & Issues:
18335520_201
Hi @hari I was unable to see your image, it looks like it did not upload successfully.
From the images on the amazon link it is impossible for me to tell which version of
the device you have. If you remove the back of the M5Stack fire on the pcb there should be a
manufacture date and revision to the left of the SD slot, please let us know what it isThanks
-
Maybe it would be easier to post a table with Manufacture Date & Revision and related HW configuration instead of everyone asking for it one by one...
Maybe you also should point out more clearly on the homepage that customers should check the HW revision before they order from amazon etc.So I ask again (see first post in this thread):
a) On the backside of the Fire PCB there is a label with "2018. 2A"
==> Which HW (especially IMU: 9250 or 6050 or SH200Q) is installed?BR
jpk -
@jpk Was there ever any response / resolution to this question regarding Fire hardware revision? I just bought a Fire from the M5Stack online store (not Amazon), and it has the same data and rev # (2018 2A). I would also like to know what model IMU is installed.
-
@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.pdfThe "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.1adc593auFAMctThere is still written "9DOF: SH200Q+BMM150", even though the latest version should be "MPU6886" acc. 1.)
Confused? :)
jpk
