Prolonged severe weather across the U.S. is causing delays including the ability to transport and deliver packages in certain cities. Please see here for more details. Thank you for your continued support and patience.


Please see all COVID-19 updates here as some shipments may be delayed due to CDC safety and staffing guidelines. If you have an order or shipping question please refer to our Customer Support page. For technical questions please check out our Forums. Thank you for your continued support.


Member Since: February 23, 2013

Country: United States

  • Oh, 1 other thing I just noticed too. When the packet is sent to TTN from the SparkX node, the packet data value is 0.66. When the same packet is sent from the Adafruit LoRa Feather, it correctly sends the battery voltage value of 4.29. Is the 0.66 value just a transient value? Looking at the schematic, I did change the VBATPIN from A9 to A10 as follows:

        // Prepare upstream data transmission at the next possible time.
        #define VBATPIN A10
        float measuredvbat = analogRead(VBATPIN);

    As I write this, I don't yet see the decoded value after changing the pin, but I'm guessing this change is required. Edit: The values are coming through as 0.00 now instead of 0.66, but still not reflecting the actual battery voltage.


  • Thanks Nick, that pin mapping fixed the transmit problem, packets now coming through my TTN gateway now!

    I should explain that the USB issue is one where Windows 10 complains that the USB device that was 'there', is now no longer there after an upload. When I pull the plug and re-insert the host side, it is still not found by Windows. So what I have been doing to get around it (via a Adafruit tip) is to single-tap the button during upload with Verbose output checked in preferences for Upload, then tapping it a second time so it enumerates to Win 10. This is a flaky way to do this as it seems to be hit/miss. Maybe I need to changed the port driver in Win 10 by using Zadig?

  • In the example ttn-abp sketch, there are pin mappings for the RFM95W that had to be set in order for the Adafruit Feather 32u4 RFM95 to work. Below is the array as it is in the Telkamp lmic library example:

    // Pin mapping const lmic_pinmap lmic_pins = { .nss = 6, .rxtx = LMIC_UNUSED_PIN, .rst = 5, .dio = {2, 3, 4}, };

    Looking at the schematic for the SparkX Pro RF, it appears that the nss and rst pins need to be reversed. Is this the case and are there any other changes? My Pro RF is not transmitting.

    Also, I am loosing the USB port after uploading the code; I'm using the Sparkfun Pro Micro board in the Arduino IDE, and this example sketch compiles fine. When I double tap the RST button during upload from the IDE, it usually, but not always, finds the correct USB serial port and uploads the code.

    Russ Ramirez

  • Yes, yes, and OpenWRT. Tessel 2 is very picky when it comes to what version of Node.js you run on a host dev machine, 4.2.x is the ticket currently, but any OS can be used. Support on Windows 7, 10 until recently was a little sketchy, but it's working pretty well now. Using the T2 from a Linux environment such as a RPi actually works quite well. On any OS, you are able to deploy code via USB, WiFi or LAN, which is pretty nice. I was a supporter of T2 on Kickstarter and have many hours of "fun" under my belt now, but as I said, things are pretty stable and working as intended at this point.

  • Just a heads up. Update the firmware and Yakto distribution per the instruction under the Edison "Getting Started" over on the Intel site, and do the same if you download the IoT tools, as all the code flashed on the device is too old at this point for any examples to run.

No public wish lists :(