Member Since: August 14, 2006
Country: United States
Nathan Seidle grew up in Tulsa, Oklahoma and transplanted himself to Colorado during college.
Hand in every cookie jar. I run SparkX (and eat cookies).
SparkFun Electronics
English and Datasheet
C, VB, and evil Makefiles
Oklahoma School of Science and Mathematics - class of 2000 (Oklahoma City, OK), University of Colorado - class of 2004 (Boulder, CO).
Crew, hiking, boxing, and the occasional snowboard jump.
www.sparkfun.com
We've written hundreds of libraries and made lots of mistakes. Learn the basics of how to write a good library.
The costs and time required to get the world's first open source BLE module certified with the FCC.
Any FCC certified module needs a tin can to protect and prevent RF emissions. Check out how we did it for Artemis!
Checkout how we drilled through the back of a PCB in order to solder to the hidden pads under a cellular module.
Learn how we created our own SMD module using PCB tips and tricks for blind and buried vias.
SparkFun is pleased to announce a new line of development tools to help implement edge computing, including voice and image recognition.
If we've learned one thing at SparkFun it's that geeks love to talk about their projects! We can't wait to share what we've been cooking. Check out the pile of new products, sensors and breakout boards!
It's not pretty but we've come up with a way to make I2C based libraries even more flexible. Now you can pass a software I2C port into a library!
We've got the magnetic tile back in stock and the first boards made with Buzzard are in!
Watch out, we’ve been translating technical English… How to install and edit the SparkFun English file for the Charm High software.
To celebrate our "crystal anniversary," here's a collection of the stories, blog posts, products and adventures from 15 years of making crazy things.
Wherein I felt the urge to respond to a recent WIRED article that hits close to home.
What's in the box?! Opening a safe with a little intelligence and a little brute force.
We use 0603 SMD packages but the electronics world uses much smaller sized components.
When writing a library, pass in I2C ports to make the library more useful on different platforms.
Looking for information in the noise: a contest to crowdsource a better algorithm for accelerometer data.
Sorry we don't have better dimensional drawings of the connectors themselves, we never imagined a user would want to spin their own enclosure! Here is a rough drawing showing the connector spacing but you'll need to model the connectors themselves. You can get the EAGLE files here to get the board outline. Hope this helps a little!
A 12 month warranty is included.
The LoRa radio is specifically tuned to 902-928MHz and will not be compatible at 868MHz.
At this time we don't plan on a EU version for LoRa support.
Yes, the Torch supports Galileo HAS. Please see our Torch test results here (summary, ~80mm was achieved in under 10 minutes). We have not tested with Esri. You can see the current tested software here. We have not tested performance when BeiDou is turned off but constellation control is supported.
While we sell LTE options, it's not trivial to hook one to the RTK mosaic. Alternatively, the RTK mosaic can easily be put into WiFi mode and connect to the hotspot on your choice. If you don't want to use your cell phone for the connection, a mobile hot spot can be used as well.
The Torch is compatible with Field Genius but we haven't yet tested the tilt sensor. We believe it will be since the RTK Torch modifies the NMEA before transmission to the GIS software (so it shouldn't know or care that tilt compensation is happening) but we all know what happens when you assume... We'll try to get it tested this follow week.
Unfortunately the RTK mosaic does not support ESP-Now and we do not plan to add it at this time. This station is primarily designed for ethernet casting (either over WiFi or a wired connection).
The Torch has an L1 antenna phase center of 115mm, and a L2/L5 phase center of 118mm. These are distances from the antenna reference point (basically the bottom of the unit). We're checking on this, but if the GIS app only has room for one ARP (or more technically 'ARP to APC'), the consensus seems to be to average the APCs: 115+118 / 2 = 116.5mm. So if you have a 1.8m long pole, you need to enter 1.8+0.1165 = 1.9165m into SW Maps. If the data entry is limited to three decimals then it's deal's choice of what to do with the 500 microns. At that point the thermal expansion of your surveying pole needs to be accounted for...
Yes.
Yup. Fixed. Thanks!