@ajb2k3 So m5stack sold a useless product? @m5stack Why are you ripping your customers off? First the M5UV2 issue, now this? I’m really starting to be disgusted by how m5stack treat its customers with garbage half baked products. I purchased their products with the idea that development would be easier, but it’s not easy, They’ve given us the idea that their products are easier to use but the bugs and product issues are far more annoying than any other company that sells embedded devices.

@kombistack said in Heart Rate Unit: @ajb2k3 Thanks for the advice but I am hardly going to buy a shop brought SPO2 meter to check the M5 Heart Rate unit against. Calibrating the unit?? No instructions were provided with the unit to do this. I persisted testing it on myself many times and there is no way my heart rate fluctuates between 60 and 210. Anyway M5Stack guys were helpful in trying to assist me too so that was also appreciated. Nope but if you read the data sheet for the SPo2 then it says it needs calibrating.

Hi, could you please post the Micropython code that I could tru the same on mine please ?

Hello @HWTaro9 you can try to send the required AT command yourself. Try something like below: [image: 1662126772210-uiflowsetapn_20220902.png] Replace YOUR.APN with your APN. Note: If you are not using M5Stack Base or Go, then please adjust tx and rx GPIOs accordingly. Thanks Felix

@teastain Nice work.

Hello @meirmark good to know. Thanks for sharing and sorry I missed that in my previous answer. Thanks Felix

@felmue plugging it into a 12VDC 3A power supply makes it work fine on all of my devices, so it was just power draw issue.

@felmue Thank you very much!

@felmue said in ACSSR I2c control: Hello @ajb2k3 first of all make sure when the ACSSR powers on the internal RGB LED blinks red (=I2C mode). If not, follow the instructions here to change mode. (Section Usage/Communication protocol) Then use something like below to first scan the I2C bus, set the proper slave address, read the version and then toggle the ACSSR every second. Note: I used an M5Atom for this example. [image: 1658576213239-m5atomunitacssrtest_20220723.png] or from the Micropython tab: from m5stack import * from m5ui import * from uiflow import * import i2c_bus import time myToggle = None i2c0 = i2c_bus.easyI2C(i2c_bus.PORTA, 0x00, freq=400000) print(i2c0.scan()) wait(1) i2c0.addr=(0x50) print(i2c0.read_u8(0xFE)) myToggle = False while True: if myToggle == False: myToggle = True i2c0.write_u8(0x00, 0x01) else: myToggle = False i2c0.write_u8(0x00, 0x00) wait(1) wait_ms(2) Thanks Felix Thanks mate, I didn't know you had to set the slave address, that explains why noting is working.

Hello @learly6 maybe the issue is the I2C clock speed. Looking at each example it seems that the MLX 90640 is setup with 450 kHz (interestingly the comment says 400 kHz) whereas the Ultrasonic Range Sensor is setup with 200 kHz. The MLX datasheet indicates I2C clock speeds of 400 kHz and up. I cannot find a datasheet for the Ultrasonic Range Sensor. I'd double check the I2C frequency and whether both sensors can deal with either 200 kHz or 400 kHz. Another thing to keep in mind are the pull-up resistors. Most (if not all) I2C sensors have built-in pull-up resistors. With each additional sensor the resulting resistance gets smaller as they are all in parallel. Thanks Felix

@felmue Thanks for responding Felix! I am looking to hack the library, or my bad habit of dismantling one and putting the needed components "in-line" with the other code of the Main Loop in the Arduino IDE, but I admit that I am "Underwhelmed" by M5Stack's firmware and GitHub examples!!! I would LOVE to access the STM controller directly and make the ext IO2 be a sta nd alone processor, but whoa! I'll keep in touch...Terry

I fixed the problem with the cam2core on the core2. So the UnitCam will work with Arduino IDE code and the core2. It is a very simple fix: Replace the first line #include <M5Stack.h> with #include <M5Core2.h> Initialising the core code on a Core2 is not the best idea! Now it works on my Core2 showing the video stream from a UnitCam connected to PortB (pins 26, 36).

The Neohex has 37 RGB LEDS and the headband has 118 RGB LEDs. the range should be set to 155 as there are now 155 LEDs connected together. They should also be connected as below [image: 1655653784137-hex_cat-resized.png] However, this many LED's will cause power issues and you will need to build a power booster cable as shown in this guide. https://youtu.be/7MP_eG3U2So

@wsanders i think so, but i have trouble lighting LEDs with m5stick

Hi ajb2k3, thanks a lot. This is a quit full of money for this type of display. Seemes to be manufactured only for M5Stack. Due to the fact, that shipping costs and VAT to Germany will be applied, to by a new one for around 45 bucks (€) would be my way to go. The unit is working. I just use then the M5-unit without display (like an ESP32) and put this in setup(): #include <M5Stack.h> // put this at the beginning M5.begin(); // Initialize the M5Stack object M5.Lcd.writecommand(ILI9341_DISPOFF); M5.Lcd.setBrightness(0); Thanks, Axel