×

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).

PdS

Member Since: March 25, 2010

Country: United States

  • Help!! And/Or What is going on here??

    Had some major issues with getting ESP8266 Thing up & running on a new Mac / El Capitan. Downloaded Arduino 1.6.6 & added Board Manager from http://arduino.esp8266.com/stable/package_esp8266com_index.json. Tried to Verify previous working Thing code and got the message “max not defined in current scope.” Oddly, the compiler pointed out that there were alternatives in …/Arduino15/packages/esp8266/tools/…

    Also would not recognize other functions (i.e xxx not defined…) unless I put “classic” C headers up in front of the code. Went through a number of machinations. Finally got things working by installing Arduino 1.6.5 & using the Old SparkFun ESP8266 Thing board definitions: https://raw.githubusercontent.com/sparkfun/Arduino_Boards/master/IDE_Board_Manager/package_sparkfun_index.json, after stumbling across this comment section/forum.

    Is this some unique problem I’m having? (and if so, how would I fix this?) If this is widespread, I would have expected to see it up front on the hookup guide. I know that there are some issues with the current GitHub esp8266 and Arduino 1.6.6 (Also not stated prominently in the hookup guide) but I tried 1.6.5 and the “current” Board Manager listed in the hookup guide, but no luck. And I know El Cap has been an issue for a lot of third party developers, as it now protects portions of the system that some have traditionally “dumped” resources into. Conversely, Hookup guide should address Mac specific issues up front, as it appears there are configurations that will work.

    Update…

    So, using the above configuration got the code to compile, BUT - after downloading, the Thing just keeps going into wdt reset mode. I can disable the watchdog timer with wdt_disable(); , but then the code just seems to freeze. Still haven’t actually gotten the Thing to work under Mac/El Cap, although was programming fine under Yosemite and Arduino 1.6.4.

  • Originally posted a comment about wall wart difficulty. Have recently discovered that my unit was manufactured with the u.FL mounted “backward” - the center pin is connected to the “NC” pad instead of the signal input. Turns out that not having an antenna connected causes BAD things to happen, like processor resets when trying to access WiFi. Check the continuity if you’re planning on using the u.FL connector.

  • Quick “Hidden Gem” from the Data Sheet - Unlike many I2C devices, doing a multiple-byte read (e.g. to read all x,y,z values) does not automatically advance the register pointer, unless you set bit 7 in the register address. Reading 6 values from register 0x28 returns you the low order x-acceleration byte 6 times - reading 6 values from register 0xA8 will return the 3 axis 16 bit acceleration values.

  • Whoa!!! These aren’t only analog inputs – A4 and A5 are used as SCL and SDA in the I2C Wire Library. Does this mean that the Pro Micro has NO WAY of supporting any kind of I2C interface? If so, then this is a reasonably serious limitation that should be pointed out on the product page!

  • Whoa!!! These aren’t only analog inputs - A4 and A5 are used as SCL and SDA in the I2C Wire Library. Does this mean that the Pro Micro has NO WAY of supporting any kind of I2C interface? If so, then this is a reasonably serious limitation that should be pointed out on the product page!

  • If “Z” is followed by “AA” and “AB,” then a Saturn V first stage is an “AF”

  • Appears that Epson Toyocom is about to start production of a 6-axis MEMS Gyro/Accelerometer:
    http://www.epsontoyocom.co.jp/english/info/2010/0223.html

No public wish lists :(