Dear Espruino folks,
I've been bitten by the Espruino bug (particularly the NRF52 portion!) and while playing around with the software and hardware some questions arose concerning the interesting design decisions.
First, what was the reason for switching to the MMC5603NJ magnetometer in rev 2.1? The LIS3MDLTR seems to have a much lower power consumption and an interrupt pin...is it the annoying component shortage?
The second question is somewhat related: since the 2.1 schematic is not publically available, what is the pin configuration of the MMC5603NJ? Is the reset pin of the NRF52 free again and the SDA and SCL the same as on the LIS3MDLTR in 2.0?
Third question: as the red LED is the light sensor, what is the "infrared in" pin used for? Does it actually work as a receiver or a sensor?
Have you considered using a BME280 or so as the temperature sensor? You'd have additional interesting parameters for context awareness with a similar amount of hassle and power consumption...
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Dear Espruino folks,
I've been bitten by the Espruino bug (particularly the NRF52 portion!) and while playing around with the software and hardware some questions arose concerning the interesting design decisions.
First, what was the reason for switching to the MMC5603NJ magnetometer in rev 2.1? The LIS3MDLTR seems to have a much lower power consumption and an interrupt pin...is it the annoying component shortage?
The second question is somewhat related: since the 2.1 schematic is not publically available, what is the pin configuration of the MMC5603NJ? Is the reset pin of the NRF52 free again and the SDA and SCL the same as on the LIS3MDLTR in 2.0?
Third question: as the red LED is the light sensor, what is the "infrared in" pin used for? Does it actually work as a receiver or a sensor?
Have you considered using a BME280 or so as the temperature sensor? You'd have additional interesting parameters for context awareness with a similar amount of hassle and power consumption...