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.

Creative Commons images are CC BY-NC-SA 3.0

$ 74.95

added to your
shopping cart

31 available 31 in stock
74.95 1+ units
71.20 10+ units
67.46 25+ units
63.71 100+ units

Description: The Copernicus II is a great GPS module from Trimble, but the SMD module prohibits immediate gratification. This DIP allows the customer to gain direct access to the pins on the SMD module. Simply provide 2.7 - 3.3VDC. The Copernicus II DIP breakout has an impedance-matched, end-launch, standard SMA connector that will mate with our SMA GPS antennas listed below.

This revision of the board fixes a few silkscreen errors and adds a jumper between the VCC and XSTBY pins.

Not sure which GPS module is right for you? Check out our GPS Buying Guide!


  • 1.1 x 1.25"
  • 0.9" between pins (bread board friendly)


Replaces: GPS-11067

Recommended Products

Customer Comments

  • Integrating this module in a new application. SparkFun makes this SUPER easy! Minor Notes: The Trimble Studio Link above is stale: new link http://www.trimble.com/embeddedsystems/copernicus2.aspx?dtID=support

    Future requests: 1. optional pad for an MCX connector instead of the SMA 2. silk screen for some of the pads on the same side as the chip (once it was mounted to the bread board it was hard to probe 3. [ALTERNATE] bring Vcc, GND, TXB, RXB to board edge opposite the antenna

    Otherwise, super pleased!

  • I’ve created an Arduino library for this module, now available here: https://github.com/trbabb/copernicus

    The module implements the powerful TSIP binary interface, and includes an example sketch. This should make getting the GPS up and running a lot simpler, especially if you need to get at some of its more advanced features.


    • Awesome! Would you mind if we added your library to our GitHub repository (it’s linked above in the Documents section)?

      • Yep, go right ahead! Actually, how about a link to the source repository? That way the two won’t get out of sync when updates are made.

        • We could do either. If you’d rather not have your code modified by other SFE users and possibly added into the repository at a later date, we can just do a link.

          • The main thing is that I’d like changes/improvements made by other users to make their way into the original branch, and vice versa, rather than dev happening in two places. In other words, I don’t want to have to keep copying back improvements from SF, or if I make improvements, I don’t want yours to fall behind. If there’s a way to arrange that, I’m happy! (Sounded like it was just going to be duplicated over, but maybe it can be branched into your repo? I’m still somewhat new to GitHub, so apologies if that’s what you meant).

            • I’ll take a look into it and see what we can do. I totally understand not wanting to let the two versions get out of sync, and that’s a good consideration for sharing the information. Thanks!

  • I’m having a hard time get a fix with this GPS. I’m configured to use TAIP, and all queries to the GPS return <RXX … 0000 … >. I’m using the following antenna: https://www.sparkfun.com/products/177 and I connected the GPS/Antenna with a separated Power Supply.

    This is my following setup: XSTBY –> Vcc OPEN –> GND VBAT –> Vcc The rest of the pins are unconnected.

    Any ideas why is not working??

    • I know it has been 8 months but I am trying to change mine over from TSIP to TAIP and can’t figure out how to structure the command. If you still have your code could you give me any pointers?

    • My first thought would be that your power supply can’t source enough current. This is a pretty common error that occurs with a weak power supply. Double check that, and if you are still having problems, contact techsupport@sparkfun and they can help you out further.

  • What antenna can I use with this?


  • I have an early copernicus II module, but cannot talk to it. I have worked through the tutorial l using a USB breakout set for 3.3v and tried Tera Term on a PC and coolterm on a MAC. In both cases I can connect TX to RX and see stuff I type on the keyboard echoed back to the terminal screen. However when I connect to either TX-B and RX-B or TX-A and RX-A nothing shows on the terminal screen. I have an active antenna connected, I am doing my test setup in side a house so reception will be a bit iffy, but I reckon I should see something. Apologies if this comment should be posted somewhere else.

    Any thoughts or suggestions welcome.


    • Try to figure out what version you have and double check the schematic of the previous version (linked above). There were pin connection changes, so you could potentially have a version which requires a different connection.

      • Thanks to the persistent Allison in Tech support I now have a working Copernicus II, my unit was a very old version and it needed to have XSTBY, BOOT, XRST & R2 all tied to VCC. Then it came to life and started sending out NMEA sentences.

        To Toni_K Thanks for your interest. It did indeed turn out to be pin connection changes that were needed.

        • Glad to hear Allison was able to help you out and you now have a working unit. Have fun playing :)

  • similar problem… Antenna connected … tx-b pin 3… rx-b pin2… vcc @3.3, gnd to pwr-gnd and pin5… xstdby to vcc. not seeing anything via hyperterm.
    swapped in null modem just in case. still nothing out.
    Oscope can see tx data burst, but Hyperterm @4800 doesn’t show anything. not even garbage. does anyone else have this module working?

    • This module works, I verified operation for both A (115200 baud) and B (4800 baud). I tested on windows with putty and mac osx with coolterm.

  • Does this revision fix the RF impedance issued mentioned by John Beans in the previous product page: https://www.sparkfun.com/products/11067

    Both layouts appear to be 50 mil. The trace length is around 140 mil for both. This gives an impedance of roughly 75 ohms. The RF Input on the Copernicus is a 50 ohm input however. The trace width needs to be wider for 0.064" thickness with 1 oz copper thickness. Am I missing something here?

    I’ve attached screenshot of existing setup: http://imgur.com/yEvXdVo

    I’ve attached screenshot of what I think is a properly sized transmission line: http://imgur.com/msl875R

    GPS L1 power on the reciever is very low, like attowatts. The signal is literally below the noise floor so decibels really matter here, so losing 50% of the power is a big deal.

    • It looks to me that the module uses a grounded coplanar wave guide and not a microstrip. If you re-run your calculation with a 50 mil trace and 10 mil clearance between signal trace and ground you should get approximately 50 ohms. http://i.imgur.com/sEpKPAK.png

      • I checked the Eagle files. This module is using a grounded co-planar wave guide but “S” (the spacing between the signal trace and the top-layer ground) is 12 mil instead of 10. This works out to an impedance of 52.8 Ohms. It would have been better if the spacing was 10 mil, but still a LOT better than 70 - 80 Ohms!

  • It still cant work. I set the pin as http://i.imgur.com/JW0EGNf.jpg, and link pin R2 to Vcc(3.3V) but it still cant work.

  • Hi, I have buy this Eval Boards GPS11858. I link the pin : pin——>input/output VCC—->power 3.3V GND—->power ground TXA—–>RS232 TXB—–>RS232

    It will return message, but without the GPS data. Anyone can help me?

  • Any idea if this has the ITAR limitations on it?

    • If you’re talking about the speed and altitude limitations that all consumer GPS receivers have built into them, than yes, this has those limits.

      • It does implement those limits as AND rather than OR, so apparently in “AIR” mode it will work up to 50,000m as long as you are going slower than 515 m/s

Customer Reviews

4 out of 5

Based on 2 ratings:

5 star
4 star
3 star
2 star
1 star

Good Performance GPS chip

This module performs exactly as per specs, it is ease to interface and very sensitive. My only remark is that the module does not allow the antenna to be fed independently. That would allow antenna current sensing, among other possibilities.