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 #260763

Member Since: October 22, 2011

Country: United States

  • Well, the uSD worked for about a minute. I could read an image off of it and display it. Then it went flaky and I have exactly that same issue as this guy:


    Works fine without a uSD inserted. As soon as you insert one (and I’ve tried 4) the screen goes black.

    Great unit, but I wouldn’t depend on the SD card.

  • BTW, I measured the output with a multimeter; 5v. The boards I received are mislabeled.

  • The picture shows the 5v version and the output on the header is marked “5v”. I bought 2 5v and 2 3.3v. The 5v units are labe “5v” next to the USB socket, but the output is marked 3.3v.

    Color me confused.

  • I’ve ruined a few of these with my poor soldering skills. What i wouldn’t give for an identical board with through holes to change voltage and ULVO. Based on the comments, it’s possible that more people are modifying these than using them out of the box.

  • i built a circuit using the same chips as Mintyboost but for 3.3v (you just have to change the signal on one pin). It worked great, but i couldn’t drive analog sensors with it because the output oscillated a bit to much. I easily drive analog sensors with this part.

  • Haven’t seen this posted, but for those having connection problems, check the MAC address that you are assigning in software. I wish that W5100 had it’s own HW generated MAC address, but it doesn’t.

    It goes wihtout saying that the MAC address must be unique on your network, but another detail to watch out for is that the first octet (leftmost) must be an even number (LSB of least significant octet is 0). Even numbers are used for unicast and odd for multicast. I had an issue that drove me crazy for a while because if I was direct connected to the PC or a switch, it worked fine. But over a wireless bridge or a powerline bridge I couldn’t get any connection at all. The culprit? I forgot to set the first octet even.

  • Well, I started a Windows VM, and used X-CTU and got it to work. I really didn’t want to change the FTDI drivers on my Linux box since they work for everything else.

  • Just received my XBee Explorer and 2 XBee Pro 900 modules. I run Linux, so I figured the first order of business is just to establish a connection. I plugged one of the modules into the Explorer, plugged in the USB, the power LED is lit, and I see /dev/ttyUSB0. Great.

    But after trying minicom, screen, etc, I get absolutely no response.

    Anyone have any clues? The XBee Explorer description says that it works with the Pro.

No public wish lists :(