avatar

bTimmeh

Member Since: May 13, 2011

Country: United States

  • Product COM-10917 | about 2 years ago

    anyone find a datasheet for this part?

    or can we at least get a spec on the thickness? I have an idea for a USB powered set of speakers but i want to embed these transducers in my material.

  • News - According to Pete - July … | about 3 years ago

    I always learned it this way.
    PNP is
    Pointing
    iN
    Please
    NPN is
    Not
    Pointing
    iN
    and the arrow is always on the emitter :P saves me time when looking through other peoples schematics. thanks for the insightful video! i learned a little more about transistors.

  • Product COM-00092 | about 3 years ago

    i believe they’re talking about variability as it applies to temperature. these are rated to +- .5% over a broad temp range.

  • Product DEV-09147 | about 3 years ago

    figured out the solution to the PB3 input issue….. figured i’d share here for all who are interested (and sparkfun so they can fix the code)
    took me longer than expected because the YELLOW_LED and WHITE_LED constants refer to the other LED (YELLOW has the correct value for WHITE and visa versa).
    as expected it was the line
    DDRB &= ~(1<<4);
    that needed fixing. if you’re going to leave the rest of the code the way it is (aka not fix the constants) you change that line to look like this:
    DDRB &= ~(1<<4 | 1<<WHITE_LED);
    (note that i used white because it contains the correct offset for yellow)
    once you do that recompile and download and it works like a dream! still a nifty product to help me start working with some new sensors for a project i’m working on, but a PITA to setup right. please fix the code sparkfun!

  • Product DEV-09147 | about 3 years ago

    according to your own code (if i understand it right) PB3 never gets reconfigured as an input. (aka DDRB’s bit for PB3 is still set to 1) while you may still be using that pin for input (clearly because the ADC is still taking samples off of it) you also have it defined as an output which is in a low-state at that point in time. so anything connected to PB3 with a fresh out of the box AVR stick is bound to only read one set of analog data values with full resolution and range.
    here’s the bit of code in particular.
    DDRB &= ~(1<<4);
    that resets the PB4 bit back to zero (configuring it for input) but not PB3.
    so unfortunately all these people who have bought AVR sticks have been getting essentially half an AVR stick, because of what looks like one line of code. i’m glad i bought an ISP programmer, because i’m going to need to fix this.

  • Product DEV-09147 | about 3 years ago

    ok, i’m having the same issue. soooo frustrating. been trying to test my thumb slide joystick (which works, i tested the resistances manually) to see how easy it would be to make it a mouse for a project i’m working on….. so i was a little pissed when the third column only shows values from 5-20 because it’s still apparently turned on as an output and so is being pulled low internally? or something similar.
    anyways, i did order one of the pocket AVR programmers when i bought mine so i’m going to try what you suggest and see if i can get this bloody thing to cooperate.

No public wish lists :(