Hello all -- I'll jump into this icebreaker discussion. I teach media arts and musical instrument design at Brown University, in Providence, Rhode Island, USA. I've used many different platforms in my own work and teaching, from Microchip PICs to different flavors of Arduino (chipKIT and Fubarino). I'm impressed overall by the M5Stack platform, but am a bit frustrated by the lack of clarity with regard to the hardware architecture -- which unit has which IMU, for example. There are several posts that ask questions about this, with no clear answers. As a teacher, I need to be certain there won't be any unwelcome surprises when I have my class order their units. Also, I'm getting very unusable results from the magnetometer on my Fire (using the demo Arduino sketch), but I hope that is solvable (I have an unanswered post on that). As far as coding goes, I think the UI Flow environment looks promising for teaching, but I'm not sure yet if it's full-featured enough to replace coding in the Arduino IDE. I need to look into it more. Overall, I have to admit I'm a bit worried about the response rate from the M5Stack team on this forum -- there are many unanswered posts. M5Stack seems to be a great concept, but I wonder about the customer support.
Posts made by butch
RE: Members Introductions aka The Icebreaker discussion.
RE: Identify M5Stack Fire Revision & Issues
@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.
Constantly increasing magnetometer reading
This is my first post, having recently received an M5Stack Fire. I've successfully programmed it from the Arduino IDE, and am receiving good data from the accel and gyro. However, the magnetometer reading constantly escalates (and eventually rolls over), even when the unit is sitting flat, unmoving on the table. It steadily escalates about 3 degrees per second. Is this an issue of calibration? (It seems that if it were a calibration issue it would be off by some consistent amount.) Any suggestions?