Thanks for the info and the schematic Gordon.
This component shortage really sucks. As you said in another thread, a simplified puck.js totally makes sense, something similar to the "custom beacon kit". Some time ago I actually started creating my own version, because they are so hard to get.
How does the current Puck.js firmware adapt to the different puck versions that are around or handle the situation if sensors are missing? For example if you had a "purpose-specific puck" with only the IMU mounted, would the firmware start up nevertheless, despite the missing magnetometer or PCT2075? Or does it make way more sense to compile a custom firmware?
Greetings,
Arthur
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.
Thanks for the info and the schematic Gordon.
This component shortage really sucks. As you said in another thread, a simplified puck.js totally makes sense, something similar to the "custom beacon kit". Some time ago I actually started creating my own version, because they are so hard to get.
How does the current Puck.js firmware adapt to the different puck versions that are around or handle the situation if sensors are missing? For example if you had a "purpose-specific puck" with only the IMU mounted, would the firmware start up nevertheless, despite the missing magnetometer or PCT2075? Or does it make way more sense to compile a custom firmware?
Greetings,
Arthur