Difference between revisions of "ADS1115 + RFduino"
From TAMI
Jump to navigationJump to search| Line 17: | Line 17: | ||
= BLE on linux = | = BLE on linux = | ||
* Implemented GAP/GATT over L2CAP using bluez but didn't provide code: http://support.plugable.com/plugable/topics/bluetooth_low_energy_and_bluez5 | * Implemented GAP/GATT over L2CAP using bluez but didn't provide code: http://support.plugable.com/plugable/topics/bluetooth_low_energy_and_bluez5 | ||
| + | * 2011 note @bluez saying it works, no examples http://www.bluez.org/bluez-low-energy-support-status/ | ||
Revision as of 07:38, 25 January 2014
We are using the ADS1115 with an RFDuino (github)
Using Adafruit_ADS1X15 and trying to fix it's quirks here.
TODO (just a snapshot)
- do and document setup of RFDuino on fedora
- why does reading single ended results depend on order for RFduino and not for Uno?
- try with Uno
- use the RDY bit (writing special values to threshold hi and lo)
- use two with different addresses on the same I2C bus
- read the Wire library (I2C) and figure out difference between two RFduino and Uno implementations
Python serial for windows
- install python 2.7.6: 32 bit and 64
- install python serial library: 32 (no 64 on http://pyserial.sourceforge.net/)
BLE on linux
- Implemented GAP/GATT over L2CAP using bluez but didn't provide code: http://support.plugable.com/plugable/topics/bluetooth_low_energy_and_bluez5
- 2011 note @bluez saying it works, no examples http://www.bluez.org/bluez-low-energy-support-status/
