Firmware Library for X-NUCLEO-IKS01A1 (MEMS Inertial & Environmental Sensors) Expansion Board
Dependencies: X_NUCLEO_COMMON ST_INTERFACES
Dependents: MultiTech_Dragonfly_2015_ATT_Gov_Solutions_Hackathon_Example HelloWorld_IKS01A1 LoRaWAN-test-10secs ServoMotorDemo ... more
Fork of X_NUCLEO_IKS01A1 by
X-NUCLEO-IKS01A1 MEMS Inertial & Environmental Sensor Nucleo Expansion Board Firmware Package
Introduction
This firmware package includes Components Device Drivers and Board Support Package for STMicroelectronics' X-NUCLEO-IKS01A1 MEMS Inertial & Environmental Sensors Nucleo Expansion Board.
Firmware Library
Class X_NUCLEO_IKS01A1 is intended to represent the MEMS inertial & environmental sensors expansion board with the same name.
The expansion board is basically featuring four IPs:
- a HTS221 Relative Humidity and Temperature Sensor,
- a LIS3MDL 3-Axis Magnetometer,
- a LPS25H MEMS Pressure Sensor, and
- a LSM6DS0 3D Accelerometer and 3D Gyroscope
The expansion board features also a DIL 24-pin socket which makes it possible to add further MEMS adapters and other sensors (e.g. UV index).
It is intentionally implemented as a singleton because only one X_NUCLEO_IKS01A1 at a time might be deployed in a HW component stack. In order to get the singleton instance you have to call class method `Instance()`, e.g.:
// Sensors expansion board singleton instance static X_NUCLEO_IKS01A1 *sensors_expansion_board = X_NUCLEO_IKS01A1::Instance();
Furthermore, library ST_INTERFACES
contains all abstract classes which together constitute the common API to which all existing and future ST components will adhere to.
Example Applications
Diff: x_nucleo_iks01a1.h
- Revision:
- 87:f4fa3dad9ec4
- Parent:
- 86:c5e05108d07b
--- a/x_nucleo_iks01a1.h Wed Jun 01 16:58:00 2016 +0200 +++ b/x_nucleo_iks01a1.h Mon Jun 06 10:32:14 2016 +0200 @@ -124,16 +124,6 @@ PinName ff_irq_pin = IKS01A1_PIN_FF); static X_NUCLEO_IKS01A1* Instance(PinName sda, PinName scl, PinName ff_irq_pin = NC); - /** - * @brief Destructor - */ - ~X_NUCLEO_IKS01A1(){ - //if(dev_i2c!=NULL){ delete dev_i2c; dev_i2c=0; } how to understand if dev_i2c is locally allocated (so it must be deleted) or comes from constructors args? - if(ht_sensor!=NULL){ delete ht_sensor; ht_sensor=NULL; } - if(magnetometer!=NULL){ delete magnetometer; magnetometer=NULL; } - if(pt_sensor!=NULL){ delete pt_sensor; pt_sensor=NULL; } - } - DevI2C *dev_i2c; HTS221 *ht_sensor;