AI hardware

GNSS Antenna Placement in Small Trackers

An opened graphite tracker reveals a ceramic GNSS patch antenna, board and battery.Concept render

Vendor guidance for patch GNSS antennas is a ground plane of about 50 x 50 to 70 x 70 mm, 4 to 10 mm of clearance, and a 5 mm keep-out for chip antennas. No vendor we reviewed publishes a battery keep-out, so log C/N0 in the enclosure, with the battery, and with the modem transmitting.

A tracker can show good satellite signal on the bench and weaker signal once the PCB is in its housing next to a battery and a cellular antenna. Rules of thumb on forums conflict with each other. This guide collects what antenna vendors publish, shows how to compare it with your own layout, and lists the measurements you need to take on your sample. It contains no Duobay price and no test result of ours.

What do the antenna vendors publish?

Each row comes from a vendor document, read on October 31, 2026. These are vendor-specific guidelines for the parts they describe. They are not universal rules.

TopicWhat the vendor saysCaveatSource
Receiver performance lineAverage C/N0 of the strongest satellites at least 44 dBHz. A well-designed system averages 44 to about 50 dBHz on high-elevation satellites.Use as a reference line for your logs. The vendor defines it for the receiver to reach its specified performance.u-blox GNSS antennas application note, as of October 31, 2026
Patch ground planeAbout 50 x 50 to 70 x 70 mm is a compromise between gain and polarization (axial ratio) loss. This is largely independent of the size of a ceramic patch.A small plane gives a back lobe and more multipath susceptibility.u-blox GNSS antennas application note, as of October 31, 2026
Patch datasheet exampleThe 25 mm SMD patch is optimized for a 70 x 70 mm ground plane. Smaller planes can be used.The datasheet also asks for a square, symmetric ground plane and a symmetric environment. This article quotes no performance values from it.Taoglas 25 mm patch datasheet, as of October 31, 2026
Patch clearanceClearance of 4 to 10 mm in all directions from the board or housing, on a non-conductive area, for maximum efficiency.Ground plane size also shifts the patch center frequency, so the patch must be tuned in the real device.Taoglas patch integration application note, as of October 31, 2026
Chip antenna keep-outIsolation distance (keep-out area) typically 5 mm.An inadequate ground plane makes a chip antenna insufficient for GNSS, per the vendor.u-blox GNSS antennas application note, as of October 31, 2026
Cellular transmitter in the same deviceMaximize the distance between the GNSS antenna and the transmitter antenna.The paper gives the principle. It does not give a distance for your enclosure.u-blox GNSS interference white paper, as of October 31, 2026

How do you compare your board with the guidance?

Start with ground area. For a rectangular ground plane, the area in square millimeters is length times width, with both in millimeters.

A_board   = L × W                       (mm², your ground plane)
A_low     = 50 × 50 = 2,500 mm²        (lower end of u-blox range)
A_high    = 70 × 70 = 4,900 mm²        (upper end of u-blox range)
A_opt     = 70 × 70 = 4,900 mm²        (plane the Taoglas 25 mm patch is optimized for)

ratio_low = A_board / A_low

Worked example with a hypothetical board. Suppose L = 40 mm and W = 25 mm, which are invented dimensions for illustration only. Then A_board = 1,000 mm², and ratio_low = 1,000 / 2,500 = 0.4. That board has 40 percent of the area at the lower end of the guidance and is far below the 4,900 mm² plane the Taoglas 25 mm patch is optimized for. Replace L and W with your own measured values. The guidance describes a compromise for ceramic patches, so a ratio below 1 means: read your antenna datasheet and measure the board.

Then check clearances with a ruler on your assembly: 4 to 10 mm from board or housing for a patch, 5 mm keep-out for a chip antenna. The Taoglas datasheet also asks for a square, symmetric ground plane and a symmetric environment around the antenna, with the antenna centered. Write each measured distance next to the vendor number.

What about the battery and the enclosure?

This is where the public vendor documents say the least. We found no official source that quantifies a battery to antenna keep-out distance, a dB penalty from battery proximity, or a detuning effect from the plastic enclosure. Vendor figure: not published, measure it on your board. We have not measured these effects either, so this article states none.

What the vendors do say is about the surrounding environment. Taoglas recommends clearance from the housing and asks for a symmetric environment. u-blox calls out the keep-out area as having an important impact on chip antenna efficiency. A large metal-cased cell is part of the environment. Treat its position as a variable to test.

What are the common pitfalls?

These follow from the vendor statements above. They are engineering reasoning from those statements. No company incident is described.

  • Following one rule of thumb for every antenna. The ledger sources give different numbers for different parts: 50 x 50 to 70 x 70 mm for patches in the u-blox note, a 70 x 70 mm optimization point in one Taoglas datasheet, and a typical 5 mm keep-out for chip antennas. Vendor figures belong to the part they describe. Use the datasheet of your antenna first.
  • Assuming a bigger ground plane always helps. Taoglas says gain generally rises with ground plane size, while u-blox calls 50 x 50 to 70 x 70 mm a compromise between gain and polarization loss. Check both effects in your antenna datasheet.
  • Tuning the patch on a bench plane and shipping it on a smaller board. Taoglas states that ground plane size shifts the patch center frequency. A patch tuned on a large test plane may sit at a different frequency on your small PCB, so the tuning must be checked in the real device. This is engineering reasoning from that statement.
  • Putting a chip antenna on a board with a thin ground plane. u-blox says an inadequate ground plane makes a chip antenna insufficient for GNSS. A tiny board that cannot give the chip antenna its footprint and keep-out will not meet the line you hoped for.
  • Placing the GNSS and LTE antennas as close as the enclosure allows. The u-blox white paper advises maximizing the antenna distance when a cellular transmitter is in the same device. Short spacing in a compact housing works against that advice.
  • Testing only the bare board. Taoglas asks for clearance from the housing and says the patch must be tuned in the real device. A pass on the open PCB therefore says little about the closed product. Test in the enclosure as built.
  • Trusting a battery rule you cannot find a source for. No official vendor source in our research quantifies a battery to antenna keep-out distance or a dB penalty. A number found in a forum or a repost has no basis here. Vendor figure: not published. Measure it on your board.

What should you measure on your own board?

The measurement is average C/N0 of the high-elevation satellites, logged from the module's NMEA GSV sentences or UBX-NAV-SAT messages, in each state of the product. Change one thing between runs. The pass line is set by you from the product requirement, and you should record the basis for it. The 44 dBHz line from u-blox is one reference point. Your product requirement still sets the pass line. This is an engineering summary of public vendor guidance and does not replace your antenna vendor's support.

What to measureHow to probe or collectRaw data to record
Baseline signal quality of the bare modulePlace the PCB with its antenna in open sky view, powered from a bench supply. Log C/N0 per satellite from NMEA GSV or UBX-NAV-SAT, along with satellite elevation, for a fixed log window you choose.Raw per-satellite C/N0 and elevation, the log window, location, date, and the module and antenna part numbers. Keep the raw log file.
Same board in the closed enclosureRepeat the baseline with the final housing, label, gasket and any potting or foam in place, at the same location and orientation.Raw C/N0 and elevation logs, photos of the orientation, housing material and finish, and the date. Compare with the baseline log.
Battery connected and in its final positionRepeat with the real cell mounted as it will ship. Then change only the battery position or orientation, one change per run.Raw logs for each position, a sketch or photo with distances measured, battery model, and which run changed which variable.
LTE modem transmittingRepeat while the modem registers and sends data in the real network conditions you expect. Log modem state with timestamps next to the GNSS log.Raw C/N0 logs with time-aligned modem activity, band in use, and the antenna layout used. Vendors list in-band risk, so record the band.
Time to first fix and fix availabilityCold start the receiver in each state above and record when the first valid fix appears and whether fixes continue.Start time, first-fix time, fix flags from the NMEA or UBX output, and the number of satellites used.
Layout against the vendor guidanceMeasure your ground plane length and width, the antenna to board edge distance, and the clearance to metal, battery and the cellular antenna on the real assembly.A dimensioned drawing or photo set. Compare each value with the guidance table in this article and your antenna datasheet.

Fix the pass line before you look at the logs. A line chosen after you see the result tends to land just under it.

What should you ask before you freeze the layout?

Take this list to your RF designer and to any supplier who proposes an antenna placement.

  • Is our antenna a patch or a chip, and does our board offer the ground plane that the datasheet for that exact part expects?
  • What are our ground plane length and width, and how do they compare with the 50 x 50 to 70 x 70 mm guidance and the 70 x 70 mm plane the Taoglas datasheet is optimized for?
  • Does the antenna sit centered on its ground plane with a symmetric environment around it, as the Taoglas datasheet asks?
  • What is the measured clearance from the antenna to the housing, the battery and any metal, and where did we write it down?
  • Is the patch tuned in the real assembly, or only on the vendor evaluation plane?
  • How far is the GNSS antenna from the cellular antenna in the final enclosure, and which LTE bands will the product use?
  • What state does the product spend most of its time in, and have we logged C/N0 in that state?
  • Where is our pass line written down, and what product requirement does it come from?
  • Who repeats this test when the battery supplier, housing material or modem changes?

Questions about GNSS antenna placement

What C/N0 should my tracker reach?

u-blox states that a receiver reaches its specified performance only if the average C/N0 of the strongest satellites is at least 44 dBHz, and that a well-designed system averages 44 to about 50 dBHz on high-elevation satellites (u-blox application note, as of October 31, 2026). Set your own pass line from your product requirement and write down why.

How big does the ground plane need to be for a patch antenna?

u-blox gives about 50 x 50 to 70 x 70 mm as a compromise between gain and polarization loss. One Taoglas 25 mm patch datasheet is optimized for 70 x 70 mm and says smaller planes can be used. Your part's datasheet has the final word, and the patch must be tuned in your real device.

How far should the battery be from the GNSS antenna?

The vendor documents we reviewed give no battery keep-out distance and no dB penalty. Vendor figure: not published, measure it on your board. The test table above shows how to log C/N0 with the battery in different positions.

Can I put the GNSS and LTE antennas next to each other?

The u-blox interference white paper advises maximizing the distance between the GNSS antenna and the wireless transmitter antenna. It does not give a distance for your enclosure, so measure with the modem transmitting.

Is this a design service or an RF certification guide?

This is an engineering summary of public vendor guidance. It is not legal or regulatory advice. For LTE tracker development, read our tracker page or tell us about your device.

If you want help laying out and testing a tracker, tell us about your device. You can also read how LTE and GNSS tracker development is organized.

Sources

All pages accessed October 31, 2026. Vendor guidance is specific to the parts described, so re-read your own datasheet before you decide.

Planning a tracker? Tell us what it needs to do. A Duobay engineer replies within 1 business day. Send a project brief →

Related reading

More engineering guides

Have a dev kit and a deadline?

Tell us what the device must do. An engineer replies within 1 business day with questions, not a sales deck.

Talk to an engineer