Author: QuakeLogic

Engineering knowledge hub

QuakeLogic

Curated QuakeLogic articles, application notes, and technical explainers for engineering teams.

Earthquake EngineeringStructural Health MonitoringEarthquake Early WarningSeismic SensorsInfrasound MonitoringShake TablesData Acquisition SystemsInfrastructure Monitoring
Areas of expertiseSeismic monitoring, structural health monitoring, testing systems, data acquisition, and applied engineering education.
Data center seismic monitoring system with seismic sensors protecting critical server infrastructure.
Technical Note

Data Center Seismic Monitoring

Data center seismic monitoring helps protect critical infrastructure from earthquake-related risks. Data centers depend on stable equipment, reliable power, and continuous network access. Even moderate ground movement can affect sensitive systems, especially...

Nov 6, 20267 min read

Configure and Troubleshoot NTP on OpenWrt Seismic Data Loggers

Terminal with UCI commands configuring NTP time sync on an OpenWrt seismic data logger

In short: To configure NTP on OpenWrt seismic data loggers, SSH in as root, add servers with uci add_list system.ntp.server='0.lede.pool.ntp.org' (repeat for 1 to 3), run uci commit system, restart with /etc/init.d/sysntpd restart, confirm with date, and enable at boot with /etc/init.d/sysntpd enable. For a one-off sync, stop sysntpd and run ntpd -q -p 0.lede.pool.ntp.org. If ntpd reports 'bad address', fix DNS or sync by IP.

1. SSH into Your OpenWrt Device

Open a terminal and SSH into your OpenWrt device:

ssh root@<your_openwrt_device_ip>

2. Verify NTP Configuration

Check the current NTP configuration:

uci show | grep ntp

3. Add NTP Servers to UCI Configuration

Add the NTP servers to the UCI system configuration:

uci add_list system.ntp.server='0.lede.pool.ntp.org'
uci add_list system.ntp.server='1.lede.pool.ntp.org'
uci add_list system.ntp.server='2.lede.pool.ntp.org'
uci add_list system.ntp.server='3.lede.pool.ntp.org'

4. Commit the Changes

Apply the changes to the configuration:

uci commit system

5. Restart the NTP Service

Restart the NTP service to apply the new configuration:

/etc/init.d/sysntpd restart

6. Verify Time Synchronization

Check the current date and time settings to ensure synchronization is working:

date

7. Ensure NTP Service Starts on Boot

Enable the NTP service to start on boot:

/etc/init.d/sysntpd enable

By following these steps, your OpenWrt device will be configured to use the specified NTP servers, and the system time will be synchronized correctly.

Manually Sync Time with an NTP Server

1. SSH into Your OpenWrt Device

Open a terminal and SSH into your OpenWrt device:

ssh root@<your_openwrt_device_ip>

2. Stop the NTP Service

Stop the NTP service to avoid conflicts:

/etc/init.d/sysntpd stop

3. Manually Sync Time with an NTP Server

Use the ntpd command to manually sync the time with an NTP server:

ntpd -q -p 0.lede.pool.ntp.org

The -q option tells ntpd to set the time and quit, and the -p option specifies the NTP server.

4. Start the NTP Service Again

Start the NTP service to resume automatic synchronization:

/etc/init.d/sysntpd start

5. Verify Time Synchronization

Check the current date and time to ensure it has been updated correctly:

date

By following these steps, you can manually sync the time on your OpenWrt device with a specific NTP server.

Troubleshooting “ntpd: bad address ‘0.lede.pool.ntp.org'”

1. Check DNS Configuration

Ensure your OpenWrt device can resolve domain names correctly:

ping google.com

If this fails, you might need to configure your DNS settings manually in the /etc/config/network file:

uci set network.wan.dns='8.8.8.8 8.8.4.4'
uci commit network
/etc/init.d/network restart

2. Verify NTP Package Installation

Ensure that the ntpd package is installed:

opkg update
opkg install ntpd

3. Manually Sync Time Using ntpd with IP Address

If DNS issues persist, use the IP address of the NTP server instead of the hostname:

ntpd -q -p 162.159.200.123

4. Ensure NTP Servers Are Correctly Configured in UCI

Check and reconfigure the NTP servers if necessary:

uci show system.ntp
uci delete system.ntp.server
uci add_list system.ntp.server='0.lede.pool.ntp.org'
uci add_list system.ntp.server='1.lede.pool.ntp.org'
uci add_list system.ntp.server='2.lede.pool.ntp.org'
uci add_list system.ntp.server='3.lede.pool.ntp.org'
uci commit system

5. Restart the NTP Service

Restart the NTP service to apply the changes:

/etc/init.d/sysntpd restart

By following these steps, you should be able to resolve the “ntpd: bad address ‘0.lede.pool.ntp.org'” error and ensure your OpenWrt device can correctly sync time with the NTP servers.

By following these organized steps, you should be able to configure, manually sync, and troubleshoot NTP settings on your OpenWrt device effectively.

For questions, reach us at support@quakelogic.net. Our working hours are 8 AM to 5 PM Pacific Time (M-F).

Key Takeaways

  • Add servers with uci add_list system.ntp.server='0.lede.pool.ntp.org' through 3.lede.pool.ntp.org, then uci commit system.
  • Restart with /etc/init.d/sysntpd restart and enable at boot with /etc/init.d/sysntpd enable.
  • Manual sync: stop sysntpd, run ntpd -q -p <server> (set time and quit), then start sysntpd again.
  • 'ntpd: bad address' usually means DNS failure; test with ping google.com and set DNS via uci set network.wan.dns.
  • If DNS stays broken, sync against an IP address such as ntpd -q -p 162.159.200.123.

Frequently Asked Questions

How do I configure NTP servers on OpenWrt using UCI?

SSH into the device as root, check the current settings with uci show | grep ntp, then add servers with uci add_list system.ntp.server='0.lede.pool.ntp.org' and repeat for 1, 2 and 3.lede.pool.ntp.org. Save with uci commit system, restart the daemon with /etc/init.d/sysntpd restart, verify with date, and make it persistent across reboots with /etc/init.d/sysntpd enable. The logger will then keep time from the configured pool.

How do I manually sync time on OpenWrt with ntpd?

Stop the running service first to avoid conflicts with /etc/init.d/sysntpd stop, then run ntpd -q -p 0.lede.pool.ntp.org. The -q flag tells ntpd to set the clock once and quit, and -p names the server. Confirm the new time with date, then restart automatic synchronization with /etc/init.d/sysntpd start. This is useful after a long power outage when the clock is far off.

What causes the 'ntpd: bad address 0.lede.pool.ntp.org' error on OpenWrt?

The error means the device cannot resolve the NTP server hostname, almost always a DNS problem. Test with ping google.com; if that fails, set DNS manually with uci set network.wan.dns='8.8.8.8 8.8.4.4', uci commit network and /etc/init.d/network restart. Also confirm the package is installed (opkg update, opkg install ntpd) and that the server list in uci show system.ntp is correct. As a workaround, sync by IP: ntpd -q -p 162.159.200.123.

How do I check that NTP is working on an OpenWrt device?

Run date and confirm the reported time and date match a trusted clock; a wrong year or epoch time means synchronization has not happened. Inspect the configured servers with uci show system.ntp, and make sure the service is enabled at boot with /etc/init.d/sysntpd enable. If the time is stale, restart the daemon with /etc/init.d/sysntpd restart or force an immediate update with ntpd -q -p <server>.

Why does accurate NTP time matter on a seismic data logger?

Seismic analysis depends on comparing arrival times across stations: locating an event, measuring phase arrivals and aligning channels all assume every logger stamps samples with the same reference time. A logger with a drifting or unset clock produces records that cannot be correlated with the rest of the network. Keeping NTP configured, persistent across reboots and resolvable through DNS ensures a Linux-based logger stays within acceptable timing error.

Need help with a project? QuakeLogic designs and supplies seismic monitoring, earthquake early warning, structural health monitoring, infrasound, and shake table systems. Browse QuakeLogic products or contact our engineering team with your site, structure, or test requirements.

How to Prepare an Annual Seismic Hardware Compliance Report

Annual Hardware Compliance Report

In short: An annual seismic monitoring hardware compliance report is prepared in 12 steps: inventory every datalogger, sensor, server and network device; review applicable regulations such as GDPR and safety standards; inspect and function-test each unit; confirm approved firmware versions; review purchase, warranty and maintenance records; run a gap analysis; assess and rank risks; write a remediation plan; compile and submit the report; review with stakeholders; implement fixes; keep monitoring.

Ensuring that all seismic monitoring hardware within an organization meets regulatory standards, safety requirements, and internal guidelines is crucial for maintaining operational integrity and compliance. At QuakeLogic, we understand the importance of systematic procedures to achieve this goal. Here’s a detailed outline on how to prepare an Annual Seismic and Early Warning Monitoring Hardware Compliance Report:

1. Inventory Assessment

  • Objective: Compile a comprehensive list of all hardware assets, including dataloggers, sensors, computers, servers, network equipment, and any other relevant hardware.

2. Regulatory and Standards Review

  • Objective: Ensure compliance with current regulations and standards applicable to your hardware, which may include industry-specific regulations, data protection standards like GDPR, and safety standards.

3. Hardware Inspection and Testing

  • Objective: Conduct physical inspections and functional tests to verify that each piece of hardware is operating safely and correctly, checking for wear and tear or other potential issues.

4. Software and Firmware Compliance

  • Objective: Check that all hardware is running the latest approved software and firmware versions to ensure optimal security and functionality.

5. Documentation Review

  • Objective: Review all relevant documentation for hardware, including purchase records, warranty information, and maintenance logs, ensuring everything is up-to-date.

6. Compliance Gap Analysis

  • Objective: Identify any discrepancies between the actual state of the hardware and compliance requirements, noting outdated or non-compliant equipment.

7. Risk Assessment

  • Objective: Assess the risks associated with identified compliance gaps, determining their potential impact and prioritizing them accordingly.

8. Remediation Plan

  • Objective: Develop strategies to address identified compliance issues, which may involve hardware upgrades, additional maintenance, or new safety protocols.

9. Reporting

  • Objective: Compile a detailed report summarizing the findings, risk assessments, and proposed remediation plans.

10. Submission and Review

  • Objective: Submit the report to relevant authorities and hold review sessions with stakeholders to discuss the findings and next steps.

11. Implementation of Recommendations

  • Objective: Execute the remediation plans to rectify compliance issues and ensure all hardware meets required standards.

12. Continuous Monitoring and Updates

  • Objective: Establish ongoing monitoring processes to continuously assess and update the compliance status of hardware.

By adhering to these steps, organizations can maintain their hardware in compliance with all pertinent regulations and standards, thus minimizing risks and bolstering operational effectiveness.

A template report can be downloaded from HERE.

For any questions regarding the process or to seek guidance on specific compliance challenges, feel free to contact us at support@quakelogic.net or call us at +1-916-899-0391. We’re here to help you ensure that your hardware systems are safe, compliant, and optimally functioning.

Key Takeaways

  • Step 1 is a complete inventory of dataloggers, sensors, computers, servers and network equipment in the seismic and early warning system.
  • Steps 2 to 5 cover regulatory review (including data protection rules like GDPR), physical inspection and testing, firmware and software version checks and documentation review.
  • Steps 6 to 8 convert findings into a gap analysis, a risk assessment that prioritizes each gap by impact, and a remediation plan.
  • Steps 9 to 12 are reporting, submission and stakeholder review, implementation of fixes, and continuous monitoring of compliance status.
  • QuakeLogic provides a downloadable template report and support at support@quakelogic.net.

Frequently Asked Questions

What should an annual seismic hardware compliance report contain?

An annual seismic hardware compliance report should contain a full asset inventory, the regulations and standards each asset is measured against, inspection and functional test results, firmware and software version status, documentation status (purchase records, warranties, maintenance logs), a gap analysis listing non-compliant or outdated equipment, a risk assessment ranking those gaps, a remediation plan with owners and dates, and a section on continuous monitoring.

Which regulations apply to seismic monitoring and early warning hardware?

Applicable requirements vary by jurisdiction and sector, but a review typically covers industry-specific regulations for the facility being monitored, electrical and equipment safety standards, and data protection rules such as GDPR where sensor or alert data involves personal information. The compliance review step identifies the current versions of these regulations and internal guidelines so every hardware item can be checked against them.

How often should seismic monitoring hardware be inspected and tested?

At minimum, seismic monitoring and early warning hardware should receive a physical inspection and functional test once a year as part of the annual compliance report, with findings recorded in maintenance logs. Hardware in harsh environments or supporting automated protective actions warrants more frequent checks. The annual cycle also verifies that firmware and software are on the latest approved versions.

What is a compliance gap analysis for monitoring hardware?

A compliance gap analysis compares the actual state of each datalogger, sensor, server and network device against the applicable regulations, standards and internal guidelines, and records every discrepancy, such as outdated firmware, expired calibration, missing documentation or equipment that no longer meets safety requirements. Each gap then feeds a risk assessment that rates its potential impact so remediation can be prioritized.

Is there a template for a seismic hardware compliance report?

Yes. QuakeLogic provides a downloadable template report that follows the 12-step structure: inventory, regulatory review, inspection and testing, software and firmware, documentation, gap analysis, risk assessment, remediation plan, reporting, submission and review, implementation, and continuous monitoring. The template is linked from the article, and questions about specific compliance challenges can be sent to support@quakelogic.net.

Need help with a project? QuakeLogic designs and supplies seismic monitoring, earthquake early warning, structural health monitoring, infrasound, and shake table systems. Browse QuakeLogic products or contact our engineering team with your site, structure, or test requirements.

ACEBOX Accelerograph for Building Seismic Monitoring and EEW

SARA ACEBOX triaxial accelerograph in aluminum IP68 enclosure for building seismic monitoring

In short: The ACEBOX is an all-in-one accelerograph for building seismic monitoring that combines three SA10-series force balance accelerometers, an SL06 recorder, GPS timing and Ethernet in one IP68 corrosion-resistant aluminum case. Units are installed at roof, mid-level and ground level, stream SeedLink data at up to 10 packets per second for earthquake early warning, and run on-board P-wave alerting, frequency peak-picking and UNI9916 measurements.

QuakeLogic proudly presents the ACEBOX accelerographs, the ultimate solution for comprehensive building seismic monitoring. Our high-fidelity accelerographs feature triaxial force balance accelerometers, an integrated datalogger, GPS, and Ethernet capabilities.

These sophisticated instruments are strategically placed at the roof, mid-level, and ground level of buildings to ensure accurate and reliable seismic data collection, as shown in the schematic below.

SARA SL x 3 bundle for for SF for "ACEBOX: Ultimate High-Fidelity Solution for Comprehensive Building Seismic Monitoring"

The ACEBOX is a compact all-in-one high-resolution accelerograph based on the reliable and field-proven SL06 recorder. It embeds three force balance accelerometers of the SA10 series, allowing for efficient and fast deployment. Within seconds of activation, the system is operational. Encased in robust, corrosion-resistant aluminum, the ACEBOX can be deployed in the field indefinitely with minimal environmental protection. Its weight and durability guarantee excellent ground coupling, and flexible data connectivity allows direct linkage to your central observatory. The ultra-fast SeedLink server accelerates data streaming up to 10 packets per second, making the ACEBOX the best option for Earthquake Early Warning Systems (EEWS).

acebox 1 for "ACEBOX: Ultimate High-Fidelity Solution for Comprehensive Building Seismic Monitoring"

Key features of the SARA ACEBOX include:

  • Ultra-low noise design with an embedded FBA sensor featuring ultra-low noise and cross-axis sensitivity
  • GPS synchronization with options for PPS or NTP when GPS is unavailable
  • Wide power supply voltage range and internal NiMh battery for safe shutdown on power failure
  • Edge computing capabilities, including alerting algorithms like P-wave analysis
  • Ultra-fast SeedLink streaming protocol or custom protocols with substreaming capability
  • Networking options including TCP, SSH, FTP, HTTP, ModBus, MQTT, Telnet, Telegram, and SMS
  • VPN readiness for operation behind firewalls and NAT filters
  • High-capacity local data storage and real-time measurements according to the UNI9916 norm
  • Automatic frequency peak-picking with frequency shifting alarm reports
  • Easy web browser configuration and management
  • IP68 protection grade for harsh environments

Applications for the ACEBOX include EEWS, aftershock studies, reservoir microseismic monitoring, operational modal analysis (OMA), and structural health monitoring (SHM).

The GUI of ACEBOX is extremely easy to use and navigate.

Our accelerographs are designed to meet and exceed industry code regulations and standards, ensuring the highest level of safety and performance. The ACEBOX provides precise data essential for structural health monitoring and safety assessments, making it an invaluable tool for engineers and building managers.

For more information and sales inquiries, please contact us at sales@quakelogic.net or visit our product website at SARA ACEBOX Accelerographs.

Seismic monitoring instrumentation for "ACEBOX: Ultimate High-Fidelity Solution for Comprehensive Building Seismic Monitoring"
Screenshot

About QuakeLogic

QuakeLogic is a leading provider of advanced seismic monitoring solutions, offering a range of products and services designed to enhance the accuracy and efficiency of seismic data acquisition and analysis. Our innovative technologies and expert support help organizations worldwide to better understand and mitigate the impacts of seismic events.

Contact Information
Emailto:sales@quakelogic.net
Phone: +1-916-899-0391
WhatsApp: +1-650-353-8627
Website: www.quakelogic.net

For more information about our products and services, please visit our website or contact our sales team. We are here to help you with all your seismic monitoring needs.

Thank you for choosing QuakeLogic. We look forward to assisting you with your seismic monitoring projects.

Key Takeaways

  • ACEBOX embeds three SA10-series force balance accelerometers and the field-proven SL06 recorder in one IP68 aluminum enclosure.
  • Typical building deployment places units at roof, mid-level and ground level.
  • Ultra-fast SeedLink streaming at up to 10 packets per second suits earthquake early warning systems.
  • Timing via GPS, with PPS or NTP fallback; an internal NiMH battery allows safe shutdown on power failure.
  • Edge computing includes P-wave alerting, automatic frequency peak-picking with frequency-shift alarms and UNI9916 real-time measurements.

Frequently Asked Questions

What is the ACEBOX accelerograph?

The SARA ACEBOX is a compact, high-resolution accelerograph built on the SL06 recorder with three embedded SA10-series force balance accelerometers, GPS synchronization and Ethernet connectivity. It is housed in corrosion-resistant aluminum with IP68 protection, so it can be left in the field indefinitely with minimal shelter, and it becomes operational within seconds of power-up.

Where should accelerographs be placed for building seismic monitoring?

For building seismic monitoring, ACEBOX units are strategically placed at the roof, at a mid-level floor and at ground level. The ground unit records the input motion, while the mid-level and roof units capture how the structure amplifies and filters that motion, which is what engineers need for structural health monitoring, operational modal analysis and post-earthquake safety assessment.

Why is the ACEBOX suitable for earthquake early warning systems?

The ACEBOX streams data through an ultra-fast SeedLink server at up to 10 packets per second, so a central observatory receives ground motion with very low latency. Its edge computing runs alerting algorithms such as P-wave analysis on the device itself, and it supports MQTT, ModBus, Telegram, SMS and other protocols for pushing alerts directly, which together make it a strong fit for EEWS.

How does the ACEBOX keep time when GPS is unavailable?

The ACEBOX normally synchronizes its clock to GPS. When no GPS signal is available, such as inside a building, it can take a PPS (pulse per second) input or synchronize over the network with NTP, so timestamps remain consistent across all units in a structure. Accurate common timing is essential for comparing roof, mid-level and ground records.

What applications does the ACEBOX support beyond building monitoring?

Beyond structural health monitoring, the ACEBOX is used for earthquake early warning systems, aftershock studies after large events, reservoir microseismic monitoring and operational modal analysis (OMA). Its automatic frequency peak-picking with frequency-shift alarm reports lets operators detect changes in a structure's natural frequencies that may indicate damage, and real-time measurements follow the UNI9916 norm.

Need help with a project? QuakeLogic designs and supplies seismic monitoring, earthquake early warning, structural health monitoring, infrasound, and shake table systems. Browse QuakeLogic products or contact our engineering team with your site, structure, or test requirements.