Digital Sparkle Collar, with more robust case situation
Photo by ![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
chebe
accelerationResolution itself seems to be twice the others, so half it? Not sure if this is a mistake, or I'm missing something about MPU6050_ACCEL_FS_2 vs MPU6050_RANGE_2_G.accelerationResolution and get_acce_resolution() only exist in the ElectronicCats version, they're not accessible in the i2cdevlibs version. That version seems to really want you to use the Quaternion path. But you can always use the range values from the other versions yourself on the raw values./* Source is from the InvenSense MotionApps v2 demo code. Original source is
* unavailable, unless you happen to be amazing as decompiling binary by
* hand (in which case, please contact me, and I'm totally serious).
*
* Also, I'd like to offer many, many thanks to Noah Zerkin for all of the
* DMP reverse-engineering he did to help make this bit of wizardry
* possible.
*/
MPU6050 Circuit
Made with Fritzing
DMP ready! Waiting for first interrupt...
ypr 0.01 -0.01 0.44
ypr 0.01 -0.01 0.44
ypr 0.01 -0.01 0.44
ypr 0.01 -0.01 0.43
#define OUTPUT_READABLE_YAWPITCHROLL line, and uncomment the #define OUTPUT_TEAPOT line you'll prepare the code for use with the Processing demo. Instead of nice readable yaw-pitch-roll values the info is packed into a 42-byte FIFO packet buffer; [quat w][][quat x][][quat y][][quat z][][gyro x][][gyro y][][gyro z][][accl x][][accl y][][accl z][][]. Upload to your Arduino.portName. For me that meant commenting out line 72, and uncommenting line 75, while updating line 75 to say "COM7". The demo is straight-forward, handling the drawing of the virtual plane, reading and unpacking the packets back to quaternion w,x,y,z values, and handing off the complications to the Toxi/c libraries. But when it works it's a lot of fun to manipulate the virtual plane by moving your MPU6050. And really helps you connect the board movement to what you want your project to detect/react to, in your mind.
MPUTeapot demo
Gif by chebe
write() would only sometimes work.
Servo Circuit
Made with Fritzing
#include <Servo.h>
Servo myServo;
int minPulseWidth = 750; // µs == 0.75ms
int maxPulseWidth = 2250; // µs == 2.25ms
void setup()
{
myServo.attach(9, minPulseWidth, maxPulseWidth); // digital pin (with PWM) 9
}
void loop()
{
myServo.write(90); // angle in degrees, 0-180
delay(1000); // ms
myServo.write(180); // angle in degrees, 0-180
delay(1000); // ms
myServo.write(0); // angle in degrees, 0-180
delay(1000); // ms
}
Front panel and driver attached to my glasses
Photo by chebe
#include <SPI.h>
#include <SD.h>
const int chipSelect = 10;
File root;
void setup(void) {
if (!SD.begin(chipSelect)) {
Serial.println("initialization failed!");
while (1);
}
Serial.println("initialization done.");
// List files on the SD card
root = SD.open("/");
printDirectory(root, 0);
root.close();
}printDirectory(root, 0) uses dir.openNextFile(); which sorts through your files alphabetically. bmpDraw(...) (see code below) is what what reads the bmp file and translates it into what the tft wants. Nice.setAddrWindow(...) was changed, from (start_x, start_y, end_x, end_y) to (start_x, start_y, width, height). So the change was from;tft.setAddrWindow(x, y, x+w-1, y+h-1);tft.startWrite();
tft.setAddrWindow(x, y, w, h);
tft.endWrite();pushColor(...) is deprecated. After experimentation I discovered that;tft.pushColor(tft.color565(r,g,b));tft.startWrite();
tft.writePixel(col, row, tft.color565(r,g,b));
tft.endWrite();#include <Adafruit_FreeTouch.h>Adafruit_FreeTouch qt_1 = Adafruit_FreeTouch(A2, OVERSAMPLE_4, RESISTOR_50K, FREQ_MODE_NONE);qt_1.begin(); in setup(void), and then read with qt_1.measure() as in;if (qt_1.measure() > 700) { /* do stuff */ }
Back of the badge, with SD card shield in place, and battery tucked between
Photo by chebe
Front of the badge, displaying an image with overlay, and NeoPixel backlit
Photo by chebe
Closed bumper case on PicoPlanet (design #12)
Photo by chebe
api.destroy_direct_message(direct_message.id)list_direct_messages which lists both sent and received direct messages, but only in the last 30 days. It uses cursors for paging through potentially long list of results, and can be rate limited.pip3 install tweepy --upgradepip3 install pillow
