ELD (Electronic Logging Device)

ELD stands for Electronic Logging Device. It is a federally mandated technology required for most commercial motor vehicle drivers in the United States who are obligated to maintain Records of Duty Status (RODS).

The ELD mandate was established by the Federal Motor Carrier Safety Administration (FMCSA) and was fully enforced starting December 2017. The rule replaced traditional paper logbooks with automated electronic recording to improve accuracy, reduce falsification, and enhance road safety.

Key things ELDs are required to record:

• Driver hours of service (HOS) — tracking on-duty, off-duty, driving, and sleeper berth time
• Engine data — including ignition on/off and engine hours
• Vehicle movement — miles driven and location at key intervals
• Driver identification — linking records to a specific driver

ELDs must meet FMCSA technical specifications and be registered on the FMCSA's certified device list. Not all commercial drivers are required to use one — exemptions exist for drivers using paper logs fewer than 8 days within a 30-day period, driveaway-towaway operations, and vehicles older than model year 2000.

Companies like Linxup offer ELD-capable devices that combine hours-of-service compliance with GPS fleet tracking in a single solution, which is common among small-to mid-sized fleets looking to consolidate tools.

For the most current exemption rules and compliance deadlines, verify directly at fmcsa.dot.gov.

An ELD device is the physical hardware unit installed in a commercial vehicle that automatically records a driver's hours of service (HOS) and other duty status data as required by the FMCSA ELD mandate. Our blog post, "ELDs Explained: How they work, who needs one, and what they cost," explains ELDs in detail.

Unlike paper logbooks, which required manual entry and were prone to error or falsification, ELD devices connect directly to a vehicle's engine control module (ECM) to capture data automatically whenever the vehicle is in motion.

What an ELD device typically does:

• Connects to the vehicle ECM via a port (usually the OBD-II or 9-pin/6-pin diagnostic port).
• Automatically records driving time when the vehicle reaches 5 mph or more.
• Logs location data at key events such as duty status changes.
• Syncs with a driver-facing app or display for real-time HOS visibility.
• Transfers data to law enforcement or safety officials via telematics, email, or display.

ELD devices vary in form factor — some are standalone units mounted on the dash, while others are small plug-in dongles. Many fleet management providers, including Linxup, integrate ELD functionality directly into their GPS tracking hardware, allowing fleets to manage both compliance and vehicle visibility from a single platform.

When evaluating an ELD device, fleet managers typically consider FMCSA certification status, ease of driver adoption, integration with existing fleet software, and total cost per vehicle.

For verified device certification, reference the FMCSA's registered ELD list at eld.fmcsa.dot.gov.

The Federal Motor Carrier Safety Administration (FMCSA) ELD mandate is a federal regulation requiring most commercial motor vehicle (CMV) drivers who are already obligated to maintain Records of Duty Status (RODS) to use a certified Electronic Logging Device instead of paper logbooks. The mandate was established under the Moving Ahead for Progress in the 21st Century Act (MAP-21), and final rules were published in 2015, with full enforcement beginning in February 2020.

Who is required to comply:

• Commercial drivers are required to maintain RODS for more than 8 days within a 30-day period.
• Interstate truck and bus drivers are subject to HOS regulations.
• Both U.S.-based and Canadian/Mexican drivers operating in the U.S.

Who is exempt:

• Drivers who use paper RODS for 8 days or fewer within a 30-day period.
• Driveaway-towaway drivers where the vehicle being driven is the commodity.
• Drivers of vehicles manufactured before model year 2000.
• Short-haul drivers who qualify for HOS exemptions and do not need to maintain RODS.

What the mandate requires:

• Use of an FMCSA-registered and certified ELD.
• The device must automatically record driving time, engine hours, vehicle movement, and location.
• Data must be transferable to law enforcement via telematics, USB, or Bluetooth.
• Drivers must be able to view their HOS data in real time.

Fleet operators should verify their specific compliance obligations directly at fmcsa.dot.gov, as exemptions and enforcement guidance can change. Some fleet management providers, including Linxup, offer FMCSA-registered ELD solutions designed to simplify compliance for small and mid-sized fleets.

Whether you are required to use an Electronic Logging Device (ELD) depends on the type of vehicle you operate, how you use it, and whether you are already required to maintain Records of Duty Status (RODS) under FMCSA Hours of Service rules.

You are generally required to have an ELD if you:

• Operate a commercial motor vehicle in interstate commerce.
• Are required to maintain RODS for more than 8 days within a 30-day period.
• Drive a vehicle with a gross vehicle weight rating (GVWR) over 10,001 lbs, carry more than 8 passengers for compensation, or transport hazardous materials requiring a placard.

You may be exempt if you:

• Use paper RODS for 8 days or fewer within a 30-day period.
• Drive a vehicle manufactured before model year 2000.
• Operate in a driveaway-towaway capacity where the driven vehicle is itself the cargo.
• Qualify for a short-haul exemption that eliminates your RODS requirement.

Intrastate drivers — those operating only within a single state — may face different requirements depending on state-level regulations, which vary. You should verify your state's specific rules with your state's Department of Transportation.

For small and mid-sized fleets trying to determine compliance obligations, some fleet management providers like Linxup offer guidance alongside their ELD solutions to help operators understand what's required for their specific operation.

Always verify your specific obligation at fmcsa.dot.gov or consult a transportation compliance specialist before making a compliance determination.

Yes. Linxup provides the Apollo ELD, a device that is self-certified by the manufacturer and registered on the FMCSA's official ELD list, as required by federal law. You can verify Apollo's registration status directly on the FMCSA ELD registry at eld.fmcsa.dot.gov.

What "self-certified and registered" means:

• ELD manufacturers are required to test their own devices against FMCSA technical specifications.
• Once self-certification is complete, the device is registered on the FMCSA's publicly searchable ELD list.
• The FMCSA does not independently test or endorse any ELD device — self-certification and registration are the standard compliance process for all ELDs on the market.
• Using a registered ELD is what constitutes legal compliance under the federal mandate.

What this means for your fleet:

• Linxup's Apollo ELD meets the technical and legal requirements of the FMCSA ELD mandate.
• The device is eligible for use by drivers required to maintain electronic Records of Duty Status (RODS).
• Fleet operators can confirm compliance by referencing the Apollo listing on the official FMCSA registry.

For fleets evaluating ELD options, choosing a device from the FMCSA-registered list is the baseline requirement. Linxup combines Apollo ELD functionality with GPS fleet tracking, giving small and mid-sized fleets a single solution for both compliance and vehicle visibility.

Q: What Is Required to Meet the FMCSA ELD Mandate?

Drivers and motor carriers subject to the FMCSA ELD mandate must meet several requirements beyond simply having a device installed. The mandate, codified under 49 CFR Part 395 Subpart B, covers the device itself, required documentation drivers must carry, and carrier recordkeeping obligations.

The device:

• Must be self-certified by the manufacturer and registered on the FMCSA's official ELD list at eld.fmcsa.dot.gov.
• Must connect to the vehicle's engine control module (ECM) and automatically record driving time and hours of service data.
• Must be capable of transferring HOS records to authorized safety officials.

Documentation drivers must carry at all times:

• A user's manual describing how to operate the ELD.
• An instruction sheet describing supported data transfer methods and how to produce and transfer HOS records to an authorized safety official.
• An instruction sheet describing malfunction reporting requirements and recordkeeping procedures during a malfunction.
• A supply of blank paper RODS graph-grids sufficient to record duty status for a minimum of 8 days, in the event of a device malfunction.

Why the paper backup matters:
If an ELD malfunctions, drivers are required to reconstruct their logs on paper RODS for the current 24-hour period and the previous 7 days. Carriers must repair or replace a malfunctioning ELD within 8 days.

Fleet management providers like Linxup, which offer the Apollo ELD — self-certified and registered on the FMCSA ELD list — can help small and mid-sized fleets meet these requirements with a combined ELD and GPS tracking solution.

For the complete regulatory text, refer to 49 CFR Part 395 Subpart B on the eCFR website.

ELD log review requirements differ depending on the context — a roadside inspection has different rules than a carrier audit. Understanding both helps drivers and fleet managers stay prepared.

At a roadside inspection:
ELDs are required to be able to send records for the current 24-hour period and the previous consecutive 7 days for review during a roadside inspection. This means a driver must be able to display or transfer 8 days of logs — today plus the prior 7 days — to an authorized safety official on demand. FMCSA ELD

For carrier recordkeeping and audits:
A motor carrier must retain ELD RODS data and supporting documents for six months, per 49 CFR 395.8(k)(1). Additionally, a backup copy of ELD records must be maintained on a separate device from where the original data was stored, also for six months. During a compliance audit or DOT investigation, safety officials can request records going back to the full six-month retention window. FMCSA ELD

Key timeframes at a glance:

• 8 days (current day + previous 7) — required to be accessible at the roadside.
• 30 days — ELD devices must be capable of producing a data file covering this period when specified by a safety official.
• 6 months — full carrier retention requirement under federal regulation.

What this means for fleet operators:
Drivers should never assume that only recent logs matter. A safety official conducting a compliance review has the authority to request records up to six months back. Fleets using an integrated ELD and GPS tracking solution — such as Linxup with the Apollo ELD — can access and export historical logs quickly, reducing exposure during audits.

For the authoritative source, refer to 49 CFR Part 395 Subpart B, Appendix A, Section 4.9.1 and eld.fmcsa.dot.gov.

AOBRDs and ELDs both connect to a commercial vehicle's engine to record driver hours of service, but they operate under different regulatory standards — and as of December 16, 2019, AOBRDs are no longer considered Records of Duty Status (RODS) compliant. The ELD mandate requires all non-exempt drivers to use FMCSA-registered ELDs. Motive

What is an AOBRD?

An AOBRD is an older style of electronic logging device that complied with 49 CFR 395.15. It connected to a vehicle's engine to record a driver's hours of service. AOBRDs were commonly used before the ELD mandate took effect and were permitted on a grandfathered basis through December 2019. EROAD

Key differences between AOBRDs and ELDs:

• Automation: ELDs make log entries automatically, but AOBRDs allow drivers to decide whether to have the machine automatically track duty status or track it manually instead. FTSGPS
• Data recorded: The main difference is that AOBRDs do not record or display as much data as ELDs. ELDs must capture GPS location, engine hours, vehicle movement, miles driven, and driver identification with greater precision and automation. EROAD
• Tamper resistance: The ELD rule goes further in its anti-tampering requirements — only limited edits can be made to ELD records by either the driver or the carrier; drivers must approve any changes made by the carrier; and an original copy of the ELD record is preserved when edits are made. FTSGPS
• Location tracking: AOBRDs were required to record a vehicle's location at each change of duty status, but it did not have to be automatically logged by GPS — drivers were permitted to manually log their location. ELDs must record GPS location automatically. FTSGPS
• Graph grid display: AOBRDs were not required to display daily duty status changes in graph grid format. ELDs must present this on a printout or display screen.
• Registration requirement: ELDs must be self-certified and registered on the FMCSA's official ELD list. AOBRDs had no equivalent registration requirement.

Bottom line:

In general, ELDs are more restrictive but much more robust than AOBRDs. If your fleet is still operating with AOBRD-era hardware, it is not compliant with the current federal mandate. Fleet management providers like Linxup offer the Apollo ELD — self-certified and registered on the FMCSA ELD list — as a compliant replacement. Motive

For the full regulatory comparison, refer to 49 CFR 395.15 vs. 49 CFR Part 395 Subpart B on the eCFR website.

For most fleets, ELD installation is straightforward and does not require a professional technician. The Linxup Apollo ELD is designed to be set up quickly by a fleet manager or owner-operator, with the full process typically completed in just a few minutes per vehicle.

What the setup process involves:

• Portal configuration — Log into the Apollo ELD portal using admin credentials and verify your carrier information, including DOT number, time zone, and carrier name pulled automatically from the FMCSA.
• Home terminal setup — Enter your home base location(s) and assign drivers accordingly.
• Driver profiles — Create a profile for each driver, including license number, ruleset, HOS start time, and app login credentials.
• Asset entry — Add each vehicle or trailer with its VIN, license plate, and registration state.
• Physical installation — Connect the J-Bus device to the truck's diagnostic port using the appropriate adapter cable (Linxup offers 6-pin, 9-pin, and RP1226 options), turn on the ignition, open the Apollo ELD app, and scan for the device to pair it.

No special tools or technical expertise are required. The device connects directly to the vehicle's diagnostic port, and the app guides drivers through pairing by scanning for nearby devices and matching the serial number.

Linxup provides driver-facing reference materials to distribute to your team, including a cab card and driver manuals for both iOS and Android, making it easy to get drivers up and running with minimal training.

For a step-by-step walkthrough including a video tutorial, visit the Linxup ELD Onboarding page.

Q: How Can I Be Sure My ELD Solution Is Tamper-Resistant?

ELD tamper resistance is not just a product feature — it is a federal requirement. The FMCSA mandate builds specific data integrity protections directly into the technical specifications that every registered ELD must meet under 49 CFR Part 395 Subpart B.

What the federal mandate requires:

No driver or motor carrier may disable, deactivate, disengage, jam, or otherwise block or degrade a signal transmission or reception, or reengineer, reprogram, or otherwise tamper with an ELD so that the device does not accurately record and retain required data. This prohibition applies to carriers and drivers alike and extends to anyone they permit or require to interfere with the device. eCFR

How ELD data integrity is protected by design:

• Driving time cannot be reduced or deleted. Edits that reduce the total amount of driving time automatically recorded by the ELD are not allowed. Driving time may not otherwise be reassigned and may never be cumulatively changed. dot
• Original records are always preserved. While edits or corrections are allowed to ensure an accurate record of the driver's duty status, the electronic record must retain what was originally recorded, as well as the date, time, and identity of the individual entering the corrections or edits. dot
• Certain event types cannot be edited at all. Events of type 2 (intermediate log), 5 (login/logout), 6 (CMV power-up/shut-down), or 7 (malfunction/diagnostic) may not be edited in any way. dot
• Driver approval is required for carrier edits. Carriers may suggest edits to a driver's logs, but drivers must review and confirm any changes — carriers cannot unilaterally alter a driver's records.
• Tamper resistance is a technical specification. Under §395.26, an ELD must be tamper-resistant for original driving data. FleetCollect

What this means in practice:

Any ELD that is self-certified and registered on the FMCSA's ELD list — including the Apollo ELD provided by Linxup — must meet these data integrity requirements as a condition of registration. The combination of automatic engine-synced recording, immutable original records, and full edit audit trails means that HOS data cannot be quietly altered without a traceable record.

For the complete technical specifications, refer to 49 CFR Part 395 Subpart B, Appendix A on the eCFR website.

The Linxup tablet (if ordered) does not come with mounting gear but does include all necessary cables to connect to the JBus or OBD ports of the vehicle. You also have the option to use your own tablet.

Yes. You can use your own tablet, or we can provide you with one. If you use your own tablet, you can download the software from Google Play or Apple's App Store. Instructions are found in our Help Center at https://www.linxup.com/eldhelp..., select the appropriate link under "Bring Your Own Device - App Install Guides."

The Apollo ELD records data continuously and automatically whenever the vehicle is in operation, with specific recording intervals determined by the FMCSA technical specifications that all registered ELDs must meet under 49 CFR Part 395 Subpart B.

How and when data is recorded:

• Driving time is recorded automatically the moment the vehicle reaches 5 mph or more, without any driver input required.
• Engine events are recorded at every engine power-up and shutdown.
• Duty status changes are recorded at every change, whether that is transitioning from off duty to on duty, to driving, or to sleeper berth.
• GPS location is recorded automatically at every duty status change and at 60-minute intervals during driving, per FMCSA specification.
• Intermediate logs are recorded at regular intervals during active driving to ensure continuous, unbroken data.
• Diagnostic and malfunction events are recorded automatically whenever the system detects a compliance issue.

What this means in practice:

Data capture is event-driven and interval-based, not dependent on a driver remembering to log anything. The Apollo ELD connects directly to the vehicle's Engine Control Module (ECM) via the diagnostic port, pulling engine data in real time. If the vehicle moves without a driver logged in, the system automatically records those miles under an unidentified driver profile, which must then be reviewed and assigned.

Because recording is tied to the engine and GPS rather than manual entry, there is no gap in data coverage during active vehicle operation. Fleet managers can review logs through the Apollo ELD portal, and drivers can view their real-time hours-of-service status directly on the app.

For complete technical recording specifications, refer to 49 CFR Part 395 Subpart B, Appendix A, and the Linxup ELD help center.

Yes. The Apollo ELD provided by Linxup includes built-in alerts that notify drivers as they approach their Hours of Service limits, giving them time to plan stops and avoid violations before they occur.

How the alerts work:

• Visual indicators — the Apollo home screen displays three real-time "donut" gauges showing time spent in each duty status: driving, on-shift on-duty, and on-cycle on-duty. Each gauge turns yellow as the driver approaches the limit and red when the limit is near.
• Violation warnings — the app displays the driver's closest possible upcoming violation directly on the main screen.
• Advance notifications — the ELD triggers a pop-up alert one hour before a potential violation and again thirty minutes before the limit is reached, giving drivers two advance warnings per limit.

Additional planning tools built into the app:

• Recap summary — drivers can tap their on-cycle gauge to see exactly how much on-duty time will be returned when their 7th or 14th day resets, helping with weekly route and rest planning.
• Deferral option — where regulations permit, drivers can split off-duty time across two consecutive days using the in-app deferral feature.
• Adverse conditions — an optional setting activates when a driver is nearing shift limits under qualifying adverse driving conditions, per FMCSA guidelines.

These features are built directly into the Apollo ELD app and function automatically once the driver is logged in and connected to the ECM device. No manual configuration is required by the driver.

For more details, visit the Linxup ELD FAQ or contact Linxup ELD support at 877-732-4980.

The FMCSA maintains a publicly searchable list of ELD devices that have been revoked or removed from compliance. Using a revoked device does not satisfy the ELD mandate, even if the device was previously registered — and a motor carrier operating with a revoked ELD can be cited during a roadside inspection.

Why devices get revoked:

Revoked devices were found by FMCSA to not meet the Electronic Logging Device technical specifications. Revocations fall into two categories: dot

• Revoked — the FMCSA determined the device does not meet the required technical specifications.
• Self-Revoked — the manufacturer voluntarily withdrew the device from the registered list, which may indicate the product was discontinued, updated, or no longer supported.

Notable examples from the current revoked list include: CyntrX ELD Pro, ELD Fleet (GPS Trackit), InTouch ELD, TST 1 ELD, AirELD, All Truckers ELD, Blue Star ELD, and others. This list changes over time as devices are added or removed.

What this means for fleet operators:

• A device appearing on the revoked list is no longer compliant for HOS recordkeeping, regardless of when it was purchased or installed.
• Carriers should periodically verify that their ELD is still on the registered list, as revocations can occur without direct notice to the fleet.
• Operating with a revoked ELD during a roadside inspection can result in violations and potential out-of-service orders.

How to verify your device's status:

Always check the current registered and revoked lists directly at eld.fmcsa.dot.gov/List. The Apollo ELD provided by Linxup remains on the FMCSA-registered list as of the date of this writing — you can confirm the current status by searching "Apollo" on the FMCSA ELD list.

For fleet managers, verifying ELD registration status periodically is a straightforward compliance safeguard that takes only minutes.