Member Since: October 17, 2012

Country: United States

  • Yeah, I got a couple of them. But it is my first entrance into that sub-platform. However I did order 10 of the 5V Pro Micros to rebuild my stock of UNO replacements. (If I have a circuit I like based around an UNO, I integrate a Pro Mini and recover the UNO since the programming is usually a direct replacement.) I’m sure there are many like me who restock whenever the Pro Mini are on sale. ;-)

    (Edited to correct Micro to Mini. Oops…)

  • I don’t know if this is information that you want to share, but it would be interesting after the dust settles from this sale to see some charts about what sold the most during the sale. Maybe, top 10? Give number of units sold, number of customers buying that product, percentage of total customers during the sale who bought that product, and maybe average quantity of product in shopping cart. And also compare to past years.

    My money is on the Pro Mini (either version) being the top seller in pretty much all the years that you can scrounge data for.

  • true equals not 0 (typically 1 is used).

    Because true equaling not zero allows streamlining code. Lets say you want to do something with someRandomVariable only if that variable isn’t zero. Then instead of writing:

    if (someRandomVariable != 0) {}

    you can short cut it and just write:

    if (someRandomVariable) {}

    for example:

    if (someRandomVariable)
        Serial.println(5.0 / someRandomVariable);
        Serial.println(F("Sorry, I don't have an ALU that can handle calculus so I can't divide by zero. Have a good day."));

    Silly example, I know, but an example is an example.

    Even if that isn’t your personal coding style, recognizing this would help understand other people’s code.

  • The 5V supply is very well regulated so you should be able to bypass any 5V regulators on your project with this supply. (For example, use the 5V pin on an arduino instead of the DC jack.)

    The spec power efficiency of the 5V supply is 80%, much better than a linear regulator.

  • Nice. You remembered to put in the requisite coffee mug ring on your hand drawn schematic. Very classy. :-D

  • While we are being pedantic, it isn’t just MOSFETs that use the term “gate” for the controlling pin. AFAIK it’s both MOSFETs and JFETs (though I haven’t seen a JFET outside of class many solar orbits ago.) Also, don’t most thyristors use “gate”?

    Hmmm… I don’t want to spend too much time here at work researching this, but do any of the other simple solid state devices other than the BJT use “base”?

  • It isn’t well known, but the symbol(s) for switches is(are) actually quite extensive with different bits meaning different things. Kind of like letters in languages that heavily use diacritics (unlike english).

    If you take a critical look at the symbols on this page you should start to see variations of the basic symbol along with modifiers that specify things like what causes the switch to change state. If you really want to see all sorts of modifiers and how they can be applied, dig up a copy of IEEE Std 315 (also ANSI Y32.2) and look at Section 4. (I have a pdf of the 1975 version (reaffirmed in 1993), but I don’t remember where I found it other as a result of a google search. I don’t know the legality of it since I never paid for it, but as a hobbyist I really can’t justify the cost of the standards from any of the standards organizations.)

  • Right, but in the context of that table it is the Arduino platform. I’m not sure if the Arduino pre-processing stuff defines it as int8_t or if it is the gpp compiler (the actual compiler used in the Arduino environment). Shawn has already weighed in though.

    I’ll ferit away into my memory that char is truly implementation specific, especially when I eventually move to a different implementation. I keep going back and forth in my mind weather it is best to use the low level int##t and uint##t data types or the higher level byte, int, long. Especially since for me I want to write code that works on both an 8-bit AVR Arduino through to a 32-bit ARM M0 Arduino, and all the points in between, with very little changes needed. I feel I should use the higher level datatypes for portability, but I really want to conserve memory on my little UNO… Having lots of #ifdef clauses for different platforms starts making code look really ugly and hard to actually read and figure out what the intent is.

    Or do I have it completely backwards and int##t and uint##t datatypes are actually higher level?

  • I’m not sure if I spotted an error, or if I learned something wrong. I could have sworn that the ‘char’ datatype was signed. The table in the video shows it as unsigned. (Otherwise, what is the point of ‘unsigned char’ or ‘byte’, and what would be a signed 8-bit variable?)

  • Look at SparkFun’s tutorial for this display, they provide a square of foam tape to mount the display to the board (or to what ever you want, just don’t stress the flex connections). You’ll want to set the jumpers properly first before covering them with the display. This is also covered in the tutorial.

    If you are plugging this display on top of a Teensy, the pinout matches the Teensy and the tutorial has more details. If mounting it elsewhere, it looks like you could use the non-circled header holes to solder on solid bus wire that you can form loops out of to pass screws through as sort of bailing loops.

    Also, remember this is a white on black display. There is no gray, so no antialiasing. Just a warning to limit expectations. But, because it is OLED, it doesn’t have viewing angle issues that LCDs have, and is self illuminating. It is very readable under indoor lighting. I haven’t taken any of mine outside in bright sunshine so I can’t make any testimonies about that though. The natural contrast looks like it should work outside in sunshine, but reflective glare might still wash it out. YMMV.