Microcontroller projects can get accurate time from several different sources. Three common options are longwave atomic clock receivers, NTP over the internet and GPS/GNSS time from satellite receiver modules. Each method can be accurate, but each one has different requirements and limitations.
This article compares AM atomic clock receivers, NTP and GPS/GNSS time modules such as the ATGM336H. The goal is to help choose the best time source for clocks, data loggers, automation systems and embedded projects.
Three Ways to Get Accurate Time
All three methods can synchronize a project to an external time reference, but they depend on different infrastructure.
- Atomic clock receiver: receives longwave radio time signals such as WWVB, DCF77, MSF or JJY
- NTP: gets time from internet time servers through WiFi or Ethernet
- GPS/GNSS: gets time from navigation satellites using a GPS/GNSS receiver module
The best choice depends on whether the project has internet access, whether it can receive radio signals, whether it can see the sky, and how much accuracy is needed.
Atomic Clock Receiver: Radio Time Without Internet
A longwave atomic clock receiver uses a tuned antenna to receive a low-frequency time signal. Examples include WWVB in North America, DCF77 in Germany, MSF in the United Kingdom and JJY in Japan.
- Works without internet access
- Works without satellites
- Requires suitable longwave signal coverage
- Requires a tuned ferrite antenna
- Reception can be affected by building structure and electrical noise
- Often works better at night
Atomic clock receivers are elegant for clocks because they can synchronize from official radio time signals without WiFi, Ethernet or GPS. The tradeoff is that reception can be unreliable in noisy indoor environments.
NTP: Internet Time Over WiFi or Ethernet
NTP, or Network Time Protocol, is a common way for internet-connected devices to get accurate time. Many ESP8266 and ESP32 projects use NTP because WiFi is already available.
- Requires internet access
- Works well with WiFi and Ethernet projects
- No special antenna required beyond normal network hardware
- Usually easy to implement on ESP8266, ESP32 and Linux-based systems
- Depends on network availability
- Not ideal for fully offline clocks
NTP is often the easiest solution when a project already connects to WiFi. It is less useful for standalone devices that should work without internet access.
GPS/GNSS Time: Satellite-Based Time Reference
GPS and other GNSS receiver modules can provide very accurate time. Modules such as the ATGM336H receive satellite signals and output time and position data, usually through a UART serial interface.
- Does not require internet access
- Provides very accurate time when satellite reception is available
- Can also provide position, speed and date information
- Requires antenna access to satellite signals
- Works best outdoors or near a window
- Startup time depends on receiver state and signal conditions
GPS/GNSS time is excellent when the project can receive satellite signals. It is less convenient for devices installed deep indoors, inside metal enclosures or in locations without a clear enough signal path to the sky.
Main Comparison Table
| Feature | Atomic Clock Receiver | NTP | GPS / GNSS |
|---|---|---|---|
| Time source | Longwave radio time signal | Internet time server | Navigation satellites |
| Internet required | No | Yes | No |
| Antenna required | Yes, tuned ferrite antenna | No special time antenna; uses network connection | Yes, GPS/GNSS antenna |
| Indoor reliability | Varies strongly with noise and building structure | Good if WiFi or Ethernet is reliable | Often poor unless near a window or using an external antenna |
| Outdoor reliability | Depends on signal coverage and noise | Depends on network access | Usually very good with sky visibility |
| Typical accuracy direction | Good for clocks, limited by reception and decoding | Good for most connected projects | Very accurate when locked to satellites |
| Startup time | Can take minutes or longer depending on signal decoding | Usually fast after network connection is available | Can take seconds to minutes depending on satellite lock |
| Best for | Standalone clocks without internet or GPS | WiFi or Ethernet-connected devices | Outdoor, mobile or precision time projects |
| Main limitation | Sensitive to electrical noise and signal coverage | Requires network and internet access | Needs satellite reception |
Atomic Clock Receiver Strengths
Atomic clock receivers are useful when a device should synchronize time without using the internet. They are especially attractive for traditional clock projects.
- No WiFi credentials needed
- No internet dependency
- No satellite visibility required
- Low data rate is not a problem for time synchronization
- Good fit for wall clocks, desk clocks and standalone time displays
A radio-controlled clock can sit in one location and occasionally synchronize itself from the time signal. It does not need to be connected to a network.
Atomic Clock Receiver Limitations
The main challenge is reception. Longwave time signals are weak by the time they reach the receiver, and indoor electrical noise can easily interfere with them.
- Reception may be poor during the day in some locations
- Switching power supplies can cause interference
- LED lights and computer equipment can create noise
- Antenna orientation matters
- Different regions require different receiver frequencies
- Signal decoding can take time
Atomic clock receivers are excellent when reception is good, but they can be frustrating in noisy indoor environments.
NTP Strengths
NTP is usually the easiest choice for internet-connected microcontroller projects. If the project already uses an ESP8266, ESP32 or Ethernet module, getting time from NTP is often only a software task.
- No longwave antenna required
- No GPS antenna required
- Works well indoors if WiFi is available
- Easy to use with ESP8266 and ESP32 projects
- Good enough accuracy for most clocks and logs
- Can update time regularly in the background
For a WiFi weather station, web-connected display or smart-home controller, NTP is usually the most convenient time source.
NTP Limitations
NTP depends on network access. If the device cannot connect to WiFi or the internet, it cannot synchronize from NTP.
- Requires WiFi or Ethernet
- Requires valid network settings
- May fail if the router or internet connection is down
- Not ideal for offline clocks
- Requires handling time zones and daylight saving rules in software
NTP gives the time in a standard reference form. The project still needs to apply the correct local time zone and daylight saving logic if local clock time is displayed.
GPS/GNSS Strengths
GPS/GNSS modules are excellent when satellite reception is available. They can provide highly accurate time and usually also provide position information.
- No internet required
- Very accurate time when locked
- Useful for mobile projects
- Useful for outdoor data loggers
- Provides location as well as time
- Often outputs serial NMEA data and sometimes a precise 1PPS signal
A module such as the ATGM336H can be useful for projects where time and location are both valuable, such as trackers, outdoor loggers, mobile devices or precision timing experiments.
GPS/GNSS Limitations
The main limitation of GPS/GNSS time is reception. Satellite signals are weak and work best with a clear view of the sky.
- May not work well indoors
- Metal enclosures can block signals
- Startup lock can take time
- Requires suitable antenna placement
- Uses more power than many RTC-only solutions
- May be unnecessary if the project only needs ordinary clock time indoors
GPS/GNSS is powerful, but it is not always the easiest solution for a wall clock in the middle of a building.
Accuracy and Practical Timekeeping
All three methods can provide accurate time for normal clocks. The practical question is not only accuracy, but how reliably the project can get a valid synchronization in its real location.
| Accuracy Need | Good Choice | Reason |
|---|---|---|
| Wall clock accuracy | Atomic receiver, NTP or GPS | All three can be accurate enough if synchronization works reliably |
| WiFi-connected display clock | NTP | Network is already available |
| Outdoor data logger | GPS/GNSS | Satellite reception and position data are useful outdoors |
| Standalone indoor clock without internet | Atomic receiver plus RTC backup | No internet or satellite access needed if radio reception works |
| Precision pulse timing | GPS/GNSS with 1PPS output | Many GNSS modules can provide a precise one-pulse-per-second reference |
Startup and Synchronization Time
Different time sources become available at different speeds.
- NTP can be fast after WiFi is connected
- GPS/GNSS may need time to acquire satellites
- Atomic clock receivers may need one or more complete time-code frames
- Bad signal conditions can delay synchronization for all radio-based methods
For a clock display, this is usually not a problem if an RTC keeps time between updates. For a device that must know the exact time immediately after power-up, startup behavior matters more.
Use an RTC for Backup
In many projects, the best solution is not only one time source. A real-time clock module can keep time between synchronizations.
- Use NTP, GPS or atomic radio to set the clock
- Use an RTC such as DS3231 to keep time when synchronization is unavailable
- Update the RTC after successful synchronization
- Use the RTC immediately at startup while waiting for external time
This approach gives the project a usable time immediately after power-up, while still allowing periodic correction from an external reference.
Time Zone and Daylight Saving Time
External time sources often provide a reference time or encoded local rules depending on the system. The project still needs to display the correct local time.
- NTP normally provides UTC-based time
- GPS/GNSS time must be converted properly for local display
- Atomic clock signals may include region-specific time information
- Daylight saving rules must be handled correctly for the target region
- Moving a clock between regions can require firmware or configuration changes
For products sold in different regions, time zone and daylight saving behavior should be planned carefully.
Indoor vs Outdoor Use
The installation location can decide the best time source.
| Installation Location | Best Direction | Why |
|---|---|---|
| Indoor, good WiFi | NTP | Internet time is easy and reliable when WiFi is already available |
| Indoor, no internet | Atomic receiver plus RTC | Works without internet if longwave reception is possible |
| Outdoor or near window | GPS/GNSS | Satellite reception is usually better outdoors |
| Inside metal enclosure | NTP or external antenna solution | Metal can block radio and satellite signals |
| Remote field installation | GPS/GNSS plus RTC | No internet needed and sky visibility may be available |
Power Consumption
Power use depends on the complete design, not only the time source. Still, the general direction is useful.
- Atomic clock receivers can be low-power but may need time to receive a valid signal
- NTP requires a network-capable controller such as ESP8266 or ESP32, and WiFi can draw significant current
- GPS/GNSS modules can draw noticeable current while acquiring and tracking satellites
- RTC modules are usually very low power and good for backup timekeeping
For battery-powered projects, it may be better to wake up occasionally, synchronize, update the RTC and then return to sleep.
Hardware Complexity
Each method adds a different kind of hardware complexity.
- Atomic receiver: tuned antenna, quiet placement and decoding input
- NTP: WiFi or Ethernet hardware and network configuration
- GPS/GNSS: satellite antenna, UART connection and possibly 1PPS input
- RTC backup: I2C RTC module and backup battery or supercapacitor
The easiest method depends on what the project already has. A WiFi project can use NTP with almost no extra hardware. A non-network clock may prefer atomic radio or GPS.
When to Use an Atomic Clock Receiver
- You want time synchronization without internet
- The device is a clock or time display
- The location has usable WWVB, DCF77, MSF or JJY reception
- You can place and orient a tuned antenna properly
- You want a traditional radio-controlled clock approach
An atomic clock receiver is a good choice when independence from internet and satellites is important and longwave reception is practical.
When to Use NTP
- The project already has WiFi or Ethernet
- Internet access is normally available
- You want simple software-based synchronization
- The device is indoors where radio or GPS reception is difficult
- The project is an ESP8266, ESP32 or network-connected controller
NTP is usually the easiest choice for internet-connected projects.
When to Use GPS/GNSS Time
- The project is outdoors or mobile
- You need both time and position
- You need a precise 1PPS timing reference
- Internet access is not available
- You can provide suitable antenna placement
GPS/GNSS time is excellent for outdoor loggers, mobile devices, trackers and precision timing projects.
Which Time Source Should You Choose?
| Project Need | Best Choice | Reason |
|---|---|---|
| WiFi-connected clock | NTP | No extra receiver hardware is needed |
| Traditional standalone wall clock | Atomic clock receiver plus RTC | Works without internet if reception is good |
| Outdoor data logger | GPS/GNSS plus RTC | Provides accurate time and location without internet |
| Indoor device with no WiFi and poor radio reception | RTC, manually set or periodically synchronized elsewhere | No external time source may be reliable in that location |
| Precision timing pulse | GPS/GNSS with 1PPS output | GNSS modules can provide precise timing pulses |
| Clock that must work during internet outage | Atomic receiver or GPS/GNSS plus RTC | External time can be received without internet, while RTC maintains time between updates |
Common Mistakes
- Choosing NTP for a device that should work without internet
- Choosing GPS for a device that will be installed deep indoors
- Choosing an atomic clock receiver without checking regional signal coverage
- Using the wrong atomic receiver frequency for the target signal
- Forgetting that GPS and NTP still require time-zone conversion for local display
- Not using an RTC backup when synchronization may be unavailable at startup
Conclusion
Atomic clock receivers, NTP and GPS/GNSS modules can all provide accurate time, but they are best suited for different projects.
- Choose an atomic clock receiver for standalone radio-controlled clocks that should work without internet or satellites.
- Choose NTP for WiFi or Ethernet-connected projects where internet access is normally available.
- Choose GPS/GNSS for outdoor, mobile or precision timing projects where satellite reception is available.
For many reliable clock designs, the best solution is to combine one external time source with an RTC module. The external source corrects the time when available, while the RTC keeps the clock running between synchronization events.