SparkFun will be closed Nov 26th and 27th for the Thanksgiving holiday. Orders placed after 2:00pm MT on the 25th will ship out Monday the 30th.


Member Since: November 19, 2012

Country: United States

  • Shawndra is hott Shawndra Ablaze

  • Hymel-face Hymel-face

  • Being Shawn Hymel

  • If your phone can act as a hotspot, you can configure the ESP8266 to connect to your phone’s SSID. If not, you can set up the ESP8266 as an AP and connect your phone to it. In either case, there is a wealth of knowledge in the ESP8266 Community Forum at www.esp8266.com.

  • Is there any reason this would have issues on a Pro Mini @ 8MHz? I was thinking about using this as a primary input device in a wearables project, but I’m having issues getting reliable repeatability. Too often, the gestures aren’t registered within a reasonable timeframe. Trying the sample sketch, sometimes I get a response ~5-10 seconds after a gesture, but more often it’s not registered at all. Thoughts?

  • For those who’ve used this, exactly how precise are the measurements? Are we talking fractions of a millimeter? I see a lot of talk about accuracy in the comments, and I’m not sure if people are referring to accuracy or precision. Accuracy isn’t so important for me, as my needs are specifically measuring relative distance changes. So is there an actual spec for the precision/resolution, or can someone definitively post just how precise they’re able to get with their own tests?

  • Is the “peak” current synonymous with “inrush”? I have an actuator that has approximately 300 ms startup draw of ~10A, but under load is only pulling ~1.2A @ 12.6V. I don’t know what kind of tolerance or suppression this package has, but those are the parameters I’m trying to accommodate.

  • “Check out the new Zero Point Energy Field Manipulator app I just downloaded. How does it work? Here… Let me show you!”

  • Absolutely. I definitely don’t want to discredit having a thorough understanding of the schema, or XML in general. Pairing those abilities, like you said, reduces the hair-pulling moments substantially: knowing both would almost certainly bump up productivity.

  • This is a great explanation of the inner-workings of Eagle lbrs! I’ve run into this very problem myself. It turns out, if you run a built-in ULP, you can extract all the components from your schematic or board directly into their original respective libraries (or merge them into one unified library).

    That would be: from your board or schematic view File -> Run (ULP) -> Open exp-lbrs.ulp -> Select export path -> Select whether to merge libraries -> Hit OK

    Then, you can import the resultant libraries, pick them apart, reorganize them, etc. Note: older versions of eagle may have “exp-project-lbr.ulp” instead.

    I think it’s important to understand the nuances of the xml involved in storing library data and the open possibilities for creating those custom scripts or programs to modify components. So Byron’s tutorial is still a great resource, kudos!

No public wish lists :(