dan
/
EM7180_STM32
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
Browse Source

Update README.md

master
Kris Winer 10 years ago
parent
0a26b85838
commit
84371815af
1 changed files with 9 additions and 3 deletions
Whitespace
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Split View
Diff Options
Show Stats Download Patch File Download Diff File
  1. 12
      README.md

12
README.md
Unescape View File

@ -1,10 +1,16 @@ @@ -1,10 +1,16 @@
EM7180_SENtral_sensor_hub
=========================
There are two files in this repository.
There are two kinds of files in this repository.
The FirmwareUpload.ino file is a sketch that takes the firmware file xxx.fw (~22 kbyte) generated by the EM7180 [SENtral Tool Kit Configuration](http://www.emdeveloper.com/?page_id=105) tool and writes it to an ST Microelectronics M24512DFM EEPROM from an SD card. Both the SD card and the [SENtral breakout board](https://www.tindie.com/products/onehorse/em7180-sentral-sensor-hub-with-bmx055-motion-sensor/) need to be connected to a microcontroller; I use the Teensy 3.1. The SENtral breakout board is connected to the Teensy 3.1 I2C port on pins 16 and 17 and the SD card reader is connected to the SPI port on pins 10-13. Once the firmware is loaded onto the EEPROM it doesn't have to be done again unless the firmware changes or is updated; the SENtral reads the firmware upon power on and gets the information it needs about the particular sensors on the board.
The FirmwareUpload.ino file is a sketch that takes the firmware file xxx.fw (~22 kbyte) generated by the EM7180 [SENtral Tool Kit Configuration](http://www.emdeveloper.com/?page_id=105) tool and writes it to an ST Microelectronics M24512DFM/C EEPROM from an SD card. Both the SD card and the [SENtral breakout board](https://www.tindie.com/products/onehorse/em7180-sentral-sensor-hub-with-bmx055-motion-sensor/) need to be connected to a microcontroller; I use the Teensy 3.1. The SENtral breakout board is connected to the Teensy 3.1 I2C port on pins 16 and 17 and the SD card reader is connected to the SPI port on pins 10-13. Once the firmware is loaded onto the EEPROM it doesn't have to be done again unless the firmware changes or is updated; the SENtral reads the firmware upon power on and gets the information it needs about the particular sensors on the board.
The other file is a sketch that further configures the SENtral for either normal mode, where it manages the BMX055 or LSM9DS0 sensors as slaves providing scaled sensor output and quaternions,or pass-through mode, where the Teensy microcontroller can directly communicate with the BMX055 or LSM9DS0 motion sensors and the MS5637 pressure sensor.
The other files are sketches that further configure the SENtral for either normal mode, where it manages the BMX055 or LSM9DS0 or MPU6500+AK8963C sensors as slaves providing scaled sensor output and quaternions,or pass-through mode, where the Teensy microcontroller can directly communicate with the BMX055 or LSM9DS0 or MPU6500+AK8963C motion sensors and the MS5637/BMP280 pressure sensor.
These are the three major motion sensor inputs I am planning to implement in the short term. These will allow ne to test the dependence of the quality of the motion sensor input data on the resulting sensor fusion solution using the same fusion algorithms and fusion engine.
The SENtral is configurable and the firmware, inclusing the sensor fusion algorithms, can be programmed by the (sophisticated) user. It's just not easy.
Later, I will add altimetry to the sensor fusion algorithm as well as some other refinements. This is a great platform for testing sensor fusion algorithms and new motion sensors.
This project is a work in progress...

Write Preview
Loading…
Cancel
Save