Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Rick Waldron
    @rwaldron
    At the moment I’m restoring all of Rose’s music from an old back up drive—she thought this was all gone forever.
    shouldn’t take me too long
    Sue Lockwood
    @deathbearbrown
    omg omg omg @rwaldron they sent Wilto ANOTHER MYO
    he only ordered one but now we have 2
    I feel less bad now that I took the other one home this weekend to play with
    Rick Waldron
    @rwaldron
    Nice!
    Do you think wilto would loan me one?
    Sue Lockwood
    @deathbearbrown
    @rwaldron maaaaybe. I also ordered one that is supposed to ship next year
    so after that we'll have 3
    Donovan Buck
    @dtex
    I2C Writes are working in dtex/imp-io + dtex/tyrion . Tested with the Adafruit PWM Breakout board. Trying to figure out where the recepitionist keeps the mailbox key so I can retrieve my MPU6050 and work on I2C reads
    Rick Waldron
    @rwaldron
    Nice!!
    That's super exciting
    Donovan Buck
    @dtex

    I might have to monkey with the reporting format. Right now it assumes two elements for each reporting pin on an array (in string format) with length n*2 where n is the number of reporting pins.

    With I2C we have to add in the address of the reporting device.

    I could reflect what I did on the payload side and separate reporting pins with a pipe, split on the pipe, and then split the resulting elements on commas. Those second elements with length === 3 are I2C.

    First Things first though: I’m going to play with multiple sensors on an Arduino, port that to the Imp and then try I2C sensors on an Arduino and then port that to Imp. I really haven’t played with sensors enough to feel confident architecting this just yet.

    Rick Waldron
    @rwaldron
    Sounds good
    Donovan Buck
    @dtex
    Is there any reason not to merge 5-and-tests with master?
    Rick Waldron
    @rwaldron
    I don’t know, I haven’t looked?
    Oh weird
    That was an accident I think
    Yes, please merge
    @dtex ^^
    Donovan Buck
    @dtex
    I kept working on this because I’m waiting on some new steppers. I’ll have it done this week. Tracking stuff down between my test.js, imu.js, imp.js, agent.nut and device.nut is causing my brain to rewire itself. I’m gonna go talk to my rubber duck now.
    Rick Waldron
    @rwaldron
    Haha ok
    Derek Wheelden
    @frxnz
    Hey gang
    Donovan Buck
    @dtex
    Hey Derek, long time no see. We’ve got the standard arduino style pin stuff working great so feel free to play with that and report any weirdness you might encounter. I’m still actually wrestling with the I2C read stuff so it’s not really in a testable state. Expect a message here soon with a request to try it out.
    Derek Wheelden
    @frxnz
    Ok perfect. I just got the imp/april today so I'll solder the headers this weekend and get everything set up
    Donovan Buck
    @dtex
    It’s a cool device. I’ve got three and expect to be doing lots of IoT stuff with them. I’m anxious to see how the Spark Photon stacks up but the Imp guys have set the bar pretty high.
    Derek Wheelden
    @frxnz
    I really like the form factor of the imp, and the setup seems reasonable simple
    dtex @dtex needs a second set of eyes
    Rick Waldron
    @rwaldron
    I can look tomorrow :)
    Donovan Buck
    @dtex
    I'm stuck on something that really shouldn't be that hard. My I2C reads are not getting the data I expect. It seems like I'm reading from the wrong register or parsing the response incorrectly. I need to clean up some indentation/white space stuff that's polluting the diff real quick first.
    Donovan Buck
    @dtex
    Okay, I’ve done that. dtex/tyrion and dtex/imp-io have the latest. I’m using @briangenisio ’s MPU6050 to test with. It works great on an Arduino and the I2C reads will return values like [2, 228, 251, 40, 62, 72, 242, 16, 253, 0, 1, 70, 255, 59] when the device is at rest and room temperature. With reads from the Imp under the same conditions I’m seeing values like [0, 0, 0, 0, 1, 65, 232, 1, 0, 243, 92, 245, 128, 255] and they bounce around a lot (like I’m not reading the same registers each time). I even hard coded the read command and listened to the response in Squirrel to take out any confusion along the way but I got the same incorrect results.
    Rick Waldron
    @rwaldron
    I just pinged Matt on Twitter to come see us in here. I'm about to get in the car to drive to New York, but I can dive in with you later this afternoon
    Donovan Buck
    @dtex
    Groovy. Safe trip.
    Rick Waldron
    @rwaldron
    Thanks, I'll check in later :)
    Donovan Buck
    @dtex
    @beardedinventor I’ll build a super simple device.nut (no J5/Imp-io/Tyrion) to replicate the issue and share that. If it doesn’t replicate, that’ll help me too.
    Matt Haines
    @beardedinventor
    @dtex - cool, I have a couple devices in the office with i2c things on them, so i'm going to try testing with those
    i haven't done i2c with johnny-five though, so pointing me in the direction of how to get things setup would be great :)
    Matt Haines
    @beardedinventor
    can you show me what your i2c writes look like for the mpu6050 (either in Squirrel or in johnny-five)? might be something obvious like how you're sending addresses?
    Donovan Buck
    @dtex
    @beardedinventor Sure, but it’s read I’m wrestling with
    i2c_addr = pin[0] << 1; // where pin[0] = 0x68, the 7-bit address
    register = “0x3B"; // Where 0x3B is the register address
    numbytes = pin[2].tointeger(); // pin[2] = 14
    
    local result = i2c.read(i2c_addr, register, numbytes);
    Writes are working really well already.
    Matt Haines
    @beardedinventor
    oh, sorry i read that totally wrong..
    Donovan Buck
    @dtex
    Oh wait a minute...
    register = “0x3B”; is actually register = 0x3B.tostring();
    So, all
    i2c_addr = pin[0] << 1;
    register = 0x3B.tostring();
    numbytes = pin[2].tointeger();
    
    local result = i2c.read(i2c_addr, register, numbytes);
    Matt Haines
    @beardedinventor
    oh, geeze
    this should actually be an easy fix (for your squirrel)
    Donovan Buck
    @dtex
    :+1:
    Matt Haines
    @beardedinventor
    you want to change the register address you're reading from to "\x3B"
    Donovan Buck
    @dtex
    I’ve tried that, but I get this error when I do:
    2015-01-17 11:30:50 UTC-6    [Agent]    ERROR: cannot convert the string
    2015-01-17 11:30:50 UTC-6    [Agent]    ERROR:   in unknown vimp:68
    2015-01-17 11:30:50 UTC-6    [Agent]    ERROR:   from unknown overrides:3
    2015-01-17 11:30:50 UTC-6    [Agent]    ERROR:   from unknown vimp:31
    Matt Haines
    @beardedinventor
    register = "\x3B";