Posts made by Kabron

Did anybody seen similar?
I have no idea how to repair.

I already wrote about poor documentation(
https://community.m5stack.com/topic/2482/ecg-module-code)
Now, I tested acquisition speed of the device.
Maximum data rate(DisplayECG() - OFF, delay(5) - OFF) is 66Hz.
And it could not be increased without changing onboard STM32 FW.
This uC acts as BLACK BOX. No description, no source code.
DisplayECG() - ON, delay(5) - OFF - 45Hz
Any serious ECG measurements started with data rate at least 250Hz.

Initially, I planned to use it with IR pulse sensor for Blood Pressure estimation. Obviously, with 15 mS accuracy it is impossible.

Make your own conclusions

It is very shame that the product is not accompanied with any documentation.
Where is the detailed schematic?
Where is the description of the FW?
Where is the description of RawDisplay SW?
Where is description of the passthrough serial?
Where is protocol description?

ECG Module13.2 detailed schematic mandatory
Block-diagram absolutely non informative

I post it here
https://github.com/m5stack/M5Core2/issues/40

Now Battery Coulombs are calculated correctly.

@m5stack said in AXP192 coulomb counter issues:

it seems like a bug. I will contact our engineer to solve this problem.

Any progress?

According to datasheet IP5306 charging current is 1.8A.
Battery, used in M5 Core Bottom is 300mAh.
It means that charge current is 6(!) times greater than C/10.
Only special designed batteries could work with such charge rate!
For me it is nothing surprizing that batteryes in M5 Core lives nothing.
For me is surprizing that no flammable incidents were reported yet.
What your designers were thinked about?!

Got 2 M5stack Core2 yesterday.

Spent 2 hours trying to understand M5 logic with versions mess.
Burned Core2 via M5Burner(2.1.6) with UIFlow Beta4-core2.
Download UIFlow-Desktop-IDE and choosed Beta, because there is no Core2 in v1.4.5.
CheckUpdate gives Current Version 1.0.12 on both 1.4.5 and Beta.
What is 1.0.12 for?

After connecting to Core2, IDE reccomend update Firmware to 1.6.3,
WEB IDE reccomend update Firmware to 1.6.4.
What are 1.6.3 and 1.6.4 Firmwares and where are them located?

After switching off by double click on power button
M5stack Grey Spontaneously Turns ON after several minutes.
And it continues till battery discharge.
Does anybody observed such behaviour?

This example illustrates how to get information from multiple SPAD areas from VL53L1X TOF sensor. 16 Regions Of Interest(ROI) with size of 4 * 4 SPAD elements each are defined in SPAD sensor array. Thus, a 4 * 4 measurement matrix formed. Distances measured from each of 16 ROI, interpolated to 8 * 8 image and displayed as Thermal like image.
Code here:
https://yadi.sk/d/qpxO0fMItW4Qpw
Video here:
https://youtu.be/b18ghRCWawo

Firstly I saw this amazing ST video
https://www.youtube.com/watch?v=c91Ve-g0J2U
but they did not publish source code.
So, it was the challenge. After a shot time I realized the idea and made my own.
Now, similar design with WEMOS D1 mini Lite works as room light controller with no faults allready 3 days.

This example illustrates direction recognition with the single VL53L1X TOF sensor. Two Regions Of Interest(ROI) are defined in SPAD sensor array:
ROI1 ROI2
0,15___12,15
####----####
####----####
####----####
...
####----####
####----####
_____3,0 _____15,0
Data measurements distance0 and distance1 cyclically readed from both ROIs, switching them on the fly.
Then STM32duino_Proximity_Gesture library used for event interpretation.
To suit Arduino requirement I added necessary library description to Pololu vl53l1_api.
Also, to handle handMustCoverBoth parameter support in STM32duino_Proximity_Gesture library, I had to slightly modify tof_gestures_DIRSWIPE_1.cpp and tof_gestures_DIRSWIPE_1.h. Both libraries are included in this bundle.

Data outputs to serial @115200 and to OLED. For investigations and adjustments it is suitable to use SerialPlot: https://bitbucket.org/hyOzd/serialplot.
Files here:
https://yadi.sk/d/MxBzgSyutU0f-Q
You should use exactly the libraries attached to project, as they were patched to suit classic gesture lib requirements and due to limited functionality of ESP32 Wire library. Also due this terrible Wire lib M5STACK works slower (42 Hz sample rate than to say ESP8266(72 Hz)).
Video here:
https://youtu.be/iSCgwss2vQs

@watson 在 Ideas, helping M5Stack document stuff... 中说：

Please read this doc. I updated it just now.

It is better to see once than read 100 times bla-bla-bla

I istalled release, but I guess I find another reason.
In the M5BALA stack there are three IP5306 IC on the 5V BUS.
And one of these IC is controlled by ESP32.
During reboot procedure trouble things occured at 5V bus Brownout
As (thanks to M5 team) we do not still have all fucking schematics, nobody could resolve what is going on there.
Now, the situation looks like the following: one time it could start working normally or another time it could not. Unpredictable.

@watson 在 Ideas, helping M5Stack document stuff... 中说：

I am adding schematic files

M5Fire schematic still TopSecret?

Well, on my office PC I had to reinstal ESP32 package and I found that your suggestions allready icluded in the new
release. Now, regardless of choosen board( M5-Stack-Core/Fire/ESP32-Dev) I got this stange behaviour.
It looks like very huge negative value(about 30 digits)of measured angle, which begins to rize in positive direction,
until it reach correct value. From this point, the program could or could not continue normal run.
I'll try to roll back the package install to see what happened.

@watson 在 Ideas, helping M5Stack document stuff... 中说：

Please pay more attention to github and docs.

Schematics???

Do I descripte your phenomenon correctly?

Absolutelly correct.
I have to mark socket sides of all my cables

@watson 在 Warranty question M5stack is dead 中说：

Hi, kabron @kabron Does your Type-C cables work now?

It works in only one direction(position).

Thanks, it's useful.

@rop 在 HOWTO: M5Stack Fire - use the full 16MB with the Arduino IDE (UPDATED) 中说：

@Kabron I don't have the BALA hardware so cannot test. Can you better explain what you mean by:

it gives wrong M5Bala library operation

Does it work it you use the original (smaller) partition scheme on the Fire? I.e.: do we know it is connected to the partitioning at all? Or could it be some other difference between the Core and the Fire?

Not now, maybe tomorrow.