×

SparkFun will be closing early at 3:30 Friday 5/27 and remain closed Monday for Memorial Day (5/30). Orders placed after 2pm MT on Friday (5/27) will process and ship out on Tuesday (5/31).

172pilot

Member Since: February 23, 2010

Country: United States

Profile

Bio

Geek, pilot, dad.

Role

Network engineer

  • It looks like the output is open collector.. Does that mean I would be able to power it with 5v for the longer range, and have the output pulled up on a 3.3v GPIO pin on a RPi? I figure if the reader is going to either be open or grounded, then the “high” voltage could depend on the pin it’s connected to? Or.. am I missing something?

  • Thanks for this great tutorial.. I’m having a strange problem though.. I was able to get the PHANT demo working, and then I went to solder headers on the dev board, and I came back, and it would no longer connect to my WiFi. I thought for sure I had destroyed the THING board with excessive heat during soldering, but I uploaded a standard ESP8266 “AT” command set firmware onto it, and using that firmware, I was able to connect to my wifi with no problem.. Loading the “Scan wifi” demo under Arduino works fine too, but for some reason, the PHANT demo never connects.. I keep getting a fast flashing blue light, and the wifi connect keeps returning status code 6 (not connected or connecting, I can’t remember which).. All my other WiFi devices are fine, and I have been fighting this for days now.. Is there anything strange that could explain this?! Thanks!

  • Since this is “unregulated”, is it not appropriate to use these to power the pi through the GPIO pins? I know it sounds stupid to cut off the connector and connect to the pins, when there’s a perfectly good micro USB on here, but in my application, the physical box is just wide enough for the pi, so I can’t have anything sticking out the side, so I’ve used the 2A regulated wall wart and powered through GPIO in the past, but I’ve read that it’s not a good idea with unregulated power… I guess it’s time to build a small regulator/fuse board that I can put on top of the pi for this..

  • I have a dumb question.. I can’t find anything detailing whether the 8266 chip ( or the Thing DEV board) has pull up/down resistors on the GPIOs, and if so, if they’re controllable in software.. Can anyone confirm? I’m looking to just monitor 3 switches, and sink a 5v relay to ground ( would that be a problem for the 3.3v GPIO if it’s set to output?

  • This RTC works GREAT with the raspberry pi, but it isn’t automatic by any stretch.. at least in current versions of Raspian.. There’s a great article here: http://www.sciencegizmo.com.au/?p=137

    This is the article I followed, and it got me to the point that my Pi was seeing /dev/rtc, and was working great with the hwclock executable.

    Good luck! Steve

  • SO.. Then if you’re limiting the current based on the difference between the supply and the voltage drop of the LED, if we had (as an easy fictional example) a 3v drop on an LED, and we ran it w/ 2x AA battery at exactly 3v, we would not need ANY resistor? And, extrapolating from that assumption, I could use 12v and run FOUR of these fictional 3v voltage drop LEDs in series with no problem? If that’s the case, can I estimate the battery life based on the current rating of the LED (ie: 20ma, meaning that it would run 100 hours off of the 2 AA batteries with 2000mah each in my example)?

  • Looking at the instructions / schematic, the “ground” pin is just hooked to the 3rd prong AC ground.. I should be able to ignore that pin then, right? All the low voltage DC side electronics are completely isolated from this anyway, and so this looks pointless to me..?? Am I missing something?

    Shouldn’t I just be able to hook up ground and a digital pin from an arduino and work this thing just fine?

  • You know.. I saw the close-up of this board, sitting on that table, and the white table with the holes in it kind of look like a breadboard, which made the actual circuit look REALLY tiny, compared to those “0.1 spaced” holes my brain was seeing.. :-)

  • I agree that cost isn’t a factor for GPS, but depending on the project, battery life and I/O pins might be.. I was really just curious where it got that data, and how accurate it is..

  • In the video, part of the data that came back through the email was the “Iridium” Lat/Lon Coordinates.. Nick said that was the transmitter coordinates, but when I type those into google maps, it comes up with an address that isn’t Sparkfun’s HQ… I’m wondering if those coordinates are really that of the transmitter, or if it’s the coordinates of the sattelite when it picked up the message, (ie: not directly overhead)?

    That seems unlikely, but with the address not coming up the same, and the text of the message saying “Iridium” specifically, I just wanted to clarify..

    As a follow-up, IF this device does know where it is, can it be queried for the current Lat/Lon as a GPS, without calling the satelite? Seems it would be useful to be able to exclude an additional GPS from a project if so, but I’d also think that would be a feature worthy of mention in the video..

No public wish lists :(