@teastain Yes! Binding it to my finger makes it work properly! Thank you!
Seeing the module code M5Stack is using would certainly help, but I don't know how to do this of if it is even possible.
@teastain Yes! Binding it to my finger makes it work properly! Thank you!
Seeing the module code M5Stack is using would certainly help, but I don't know how to do this of if it is even possible.
@ajb2k3 Yes - I am making progress - working on the calibration against a medical grade device. Thank you!
Connecting TXD to RXD & supplying 5V to the Grove connector works great! I never thought about studying the schematic right on the device. Thanks for your assistance!
Very helpful. Thank you so much!
This unit works great using UiFlow and the Grove UART connection. I have been unable to get the synth to respond to MIDI input from an Arturia MINILAB 3 via either the MIDI IN or TRS IN connector. The MIDI signals coming from the MINILAB and going in to either of these two connectors are correct and verified with a logic analyzer.
I am new to MIDI - am I making a beginners mistake or is it not possible to send a MIDI note in to this device from a keyboard?
Is there a method to log a few seconds of sensor data directly to ESP32 memory using either version of UiFlow? Specifically, I am trying to use one of the lightweight controllers such as the Atom or Nano to capture some model rocket accelerometer or barometer data for some young students. These students have been able to make exceptional progress with UiFlow.
@cerietke I didn’t try your code yet, but the first thing I would do is get your core2 updated to 1.13.5 via M5 Burner.
Update - just tested your UiFlow code and it works fine on my Core2. I usually load my WiFi credentials when I burn the firmware via M5 Burner. I’m not sure how you are connecting to WiFi using your code without using the SSID and PASSWORD block
@teastain Thank you! Good information.
Does anyone have any experience using the EXT-ENCODER (U161) to read rotary encoders? When I connect a Type LPD3806-360BM Rotary Encoder, I can accurately count the pulses if the RPM is very slow. When I look at the A and B inputs with an oscilloscope the EXT-ENCODER is adding capacitance causing the leading edge of the pulse to be rounded off. If the RPM is increased, the pulses never reach enough voltage to be counted. Disconnecting the A & B leads removes the capacitance and restores the encoder pulses to a perfect square wave even at high RPM. The EXT-ENCODER schematic shows pull up resistors which are required and they appear to be correct.
This is the first time I have worked with reading encoders & I need to learn more.
This sensor is surprisingly difficult to use but I still learned a lot. As suggested, I took a look at the raw data from the sensor using an M5Stack Arduino program. Although you can see the pulse data, it is very unstable, noisy and has a varying offset. Here is a very good description of what it takes to make the MAX30100 work.
https://morf.lv/implementing-pulse-oximeter-using-max30100 In addition to what the article says, the two Heart sensors I have behave differently and would require individual calibrations.
@basgoossen Thank you for this excellent information.
@ajb2k3 Yes - I am making progress - working on the calibration against a medical grade device. Thank you!