×

SparkFun will be closing on Monday for Memorial Day (5/28). Orders placed after 2pm MT on Friday (5/25) will process and ship out on Tuesday (5/29).

TM'

Member Since: October 5, 2015

Country: United States

  • Not wishing to rain on anyone’s parade, but what does this deliver over, say, a Teensy? (Apart from the acc/gyro) If Intel want to establish their IoT credentials at the low end why do they come in with an offering below FRDM boards or the Teensy in price/performance? I do like the 5V tolerant I/O: that at least is fan service. In an alternate reality, both sets of warring Italians sign over their naming rights to Paul Stoffregen and the singularity is brought forward by “n” years. In this reality we get to choose between Hillary, Trump and Intel.

  • Edit: I was having issues with the module hanging.

    I think the root of my problem is that I’d copied some initialization code from the example “LSM9DS1_Settings.ino”. One or more of the settings was causing glitchy behaviour. After reverting to the default settings in the library’s init() function, the problems went away.

    Having a boatload of fun with this board. Thank you Sparkfun!

  • As previously posted, I had no luck using the shield plugged into Arduino UNO R3s (but was able to use the shield on a Mega 2560 with some tweaks to the library).

    Both of the UNO R3 boards I tried had DIP packaged ATmega328ps. I wonder if perhaps the shield was developed and tested with a Sparkfun Redboard (with SOIC MCU). Has anyone got the shield working plugged into a DIP package UNO? Perhaps there’s too much electrical noise/EMI from a DIP packaged microcontroller?

  • Works as a “Thing” but gets flaky when stacked on an Arduino UNO R3. I tried plugging the shield into a genuine Arduino UNO R3 and an Inland (Microcenter) clone. In both cases I had to pull the esp8266 RST pin low for a second to get any sign of life from the shield. The shield’s blue status light switches off after the first attempts to communicate with it (via sw serial pins 8 & 9).

    I had more luck with a Mega 2560 board (Inland/Microcenter clone). Rather than cutting traces like Brad10 below, I set pins 8 & 9 as inputs and connected TX1(18) to 9 and RX1(19) to 8 with patch cables.

    If you only have UNO boards, I’d suggest buying a “Thing” instead (until the next HW revision of the shield).

    Changes to library to support Mega 2560

    In SparkFunESP8266WiFi.h, add a third value

     ESP8266_HARDWARE_SERIAL1
    

    to the definition of esp8266_serial_port.

    In SparkFunESP8266WiFi.cpp, add a third clause:

    else if (serialPort == ESP8266_HARDWARE_SERIAL1)
    {
    #if defined(__AVR_ATmega2560__)
        Serial1.begin(baudRate);
        _serial = &Serial1;
    #else
        return false;
    #endif
    }
    

    to the if statement at the start of begin().

    Changes to example code

    In setup(), add

    pinMode(ESP8266_SW_TX, INPUT); 
    pinMode(ESP8266_SW_RX, INPUT);
    

    before calling Serial.begin().

    Change the esp8266.begin() call to

    esp8266.begin(9600,ESP8266_HARDWARE_SERIAL1)
    

    That’s it. You should now be able to run the library examples on a Mega 2560 with the shield installed and TX1 & RX1 connected to pins 9 & 8.

    Good luck.

    P.S. The flash memory is 512KB (same as an esp-01): this is too small for recent versions of the stock AT firmware. If you’re shopping for modules look for more. N.B. Chinese sites sometimes label module memory as “4Megabits” - this is just 512KBytes.

No public wish lists :(