法规速查Regulation Navigator
先看懂要求，再查清依据。Understand the rule. Find its source.
部分资料含历史版本或来源限制。收录日期不代表现行性已复核；请先核对每项官方来源、版本和适用范围。Some records contain historical versions or source limitations. Capture dates do not establish a review of current requirements; check each official source, edition and scope before use.
法规索引Regulation index
按中文名称了解每条管什么，再展开查看解读与官方原文。Browse by subject, then expand an entry for available explanations and official text.
电子日志的提交、修改、备注与保存§ 395.30 ELD record submissions, edits, annotations, and data retention.§ 395.30 ELD record submissions, edits, annotations, and data retention.电子日志的提交、修改、备注与保存
未识别司机的驾驶记录§ 395.32 Non-authenticated driver logs.§ 395.32 Non-authenticated driver logs.未识别司机的驾驶记录
电子日志（ELD）故障与数据诊断§ 395.34 ELD malfunctions and data diagnostic events.电子日志出故障或出现诊断提示时，查看司机与承运人的处理要求。Hours & logs§ 395.34 ELD malfunctions and data diagnostic events.电子日志（ELD）故障与数据诊断
适用于联邦 ELD 规则覆盖的驾驶员和承运人。personal conveyance 和 yard move 仍须满足各自适用条件；不得为腾出工时，将真实道路驾驶改成非驾驶状态。For drivers and carriers subject to federal ELD rules. This topic does not expand personal-conveyance or yard-move allowances or authorize relabeling actual road driving to create hours.
ELD 故障须及时书面通知，并补齐记录For a malfunction, notify promptly and reconstruct accessible records
- 具体要求What the rule requires
- 发现 ELD 故障后，司机应在 24 小时内书面通知承运人。除已有或可取回的记录外，须重建当日及此前七日的记录，并按要求继续使用纸质记录，直至设备恢复。承运人通常须在发现故障或收到通知二者较早之日起八日内修复、替换或维护设备；如需延期，须在司机通知承运人后五日内向 FMCSA 提出申请，能否延期由主管机关决定。Within 24 hours of discovering an ELD malfunction, the driver must notify the carrier in writing, reconstruct the current day and preceding seven days except records already available or retrievable, and continue the required paper records until compliance resumes. The carrier generally has eight days from discovery or notification, whichever is earlier, to repair, replace or service it; an extension request must be submitted to FMCSA within five days after the driver notifies the carrier and is subject to agency approval.
- 条件与例外Conditions and exceptions
- 一般数据诊断提示，应按承运人和 ELD 提供商的建议处理。出现提示不一定属于允许使用纸质日志的设备故障，更不表示可以长期使用纸质日志。Handle data diagnostic events according to carrier and ELD-provider recommendations; not every alert permits prolonged paper logging.
(a)(1) (1) Note the malfunction of the ELD and provide written notice of the malfunction to the motor carrier within 24 hours;
(a)(2) (2) Reconstruct the record of duty status for the current 24-hour period and the previous 7 consecutive days, and record the records of duty status on graph-grid paper logs that comply with § 395.8, unless the driver already possesses the records or the records are retrievable from the ELD; and
(a)(3) (3) Continue to manually prepare a record of duty status in accordance with § 395.8 until the ELD is serviced and brought back into compliance with this subpart.
(c) (c) Driver requirements during ELD data diagnostic events. If an ELD indicates that there is a data inconsistency that generates a data diagnostic event, the driver must follow the motor carrier's and ELD provider's recommendations in resolving the data inconsistency.
(d) (d) Motor carrier requirements for repair, replacement, or service. (1) If a motor carrier receives or discovers information concerning the malfunction of an ELD, the motor carrier must take actions to correct the malfunction of the ELD within 8 days of discovery of the condition or a driver's notification to the motor carrier, whichever occurs first.
(d)(2) (2) A motor carrier seeking to extend the period of time permitted for repair, replacement, or service of one or more ELDs shall notify the FMCSA Division Administrator for the State of the motor carrier's principal place of business within 5 days after a driver notifies the motor carrier under paragraph (a)(1) of this section. Each request for an extension under this section must be signed by the motor carrier and must contain:
使用固定来源版次；适用日期与例外以原文及历史沿革为准。Uses a fixed source edition; check the original and statutory history for operative dates and exceptions.
法规原文 · 英文REGULATION TEXT · ENGLISH
电子日志（ELD）故障与数据诊断§ 395.34 ELD malfunctions and data diagnostic events.
官方来源快照；不代表已核对现行汇编及后续修订。请核对来源版本。Official-source snapshot; current consolidated law and subsequent amendments have not been verified.
展开英文原文Read the English original收起英文原文Hide the English original
49 CFR 395.34 · § 395.34 ELD malfunctions and data diagnostic events.
§ 395.34 ELD malfunctions and data diagnostic events.
(a)Recordkeeping during ELD malfunctions. In case of an ELD malfunction, a driver must do the following:
(a)(1)Note the malfunction of the ELD and provide written notice of the malfunction to the motor carrier within 24 hours;
(a)(2)Reconstruct the record of duty status for the current 24-hour period and the previous 7 consecutive days, and record the records of duty status on graph-grid paper logs that comply with § 395.8, unless the driver already possesses the records or the records are retrievable from the ELD; and
(a)(3)Continue to manually prepare a record of duty status in accordance with § 395.8 until the ELD is serviced and brought back into compliance with this subpart.
(b)Inspections during malfunctions. When a driver is inspected for hours of service compliance during an ELD malfunction, the driver must provide the authorized safety official the driver's records of duty status manually kept as specified under paragraphs (a)(2) and (3) of this section.
(c)Driver requirements during ELD data diagnostic events. If an ELD indicates that there is a data inconsistency that generates a data diagnostic event, the driver must follow the motor carrier's and ELD provider's recommendations in resolving the data inconsistency.
(d)Motor carrier requirements for repair, replacement, or service. (1) If a motor carrier receives or discovers information concerning the malfunction of an ELD, the motor carrier must take actions to correct the malfunction of the ELD within 8 days of discovery of the condition or a driver's notification to the motor carrier, whichever occurs first.
(d)(2)A motor carrier seeking to extend the period of time permitted for repair, replacement, or service of one or more ELDs shall notify the FMCSA Division Administrator for the State of the motor carrier's principal place of business within 5 days after a driver notifies the motor carrier under paragraph (a)(1) of this section. Each request for an extension under this section must be signed by the motor carrier and must contain:
(d)(2)(i)The name, address, and telephone number of the motor carrier representative who files the request;
(d)(2)(ii)The make, model, and serial number of each ELD;
(d)(2)(iii)The date and location of each ELD malfunction as reported by the driver to the carrier; and
(d)(2)(iv)A concise statement describing actions taken by the motor carrier to make a good faith effort to repair, replace, or service the ELD units, including why the carrier needs additional time beyond the 8 days provided by this section.
(d)(3)If FMCSA determines that the motor carrier is continuing to make a good faith effort to ensure repair, replacement, or service to address the malfunction of each ELD, FMCSA may allow an additional period.
(d)(4)FMCSA will provide written notice to the motor carrier of its determination. The determination may include any conditions that FMCSA considers necessary to ensure hours-of-service compliance. The determination shall constitute a final agency action.
(d)(5)A motor carrier providing a request for extension that meets the requirements of paragraph (d)(2) of this section is deemed in compliance with § 395.8(a)(1)(i) and (a)(2) until FMCSA makes an extension determination under this section, provided the motor carrier and driver continue to comply with the other requirements of this section.
依据关联的官方原文及官方项目说明起草。中文和英文解读均为 CTAC AI 辅助工作稿，未经人工审核；教学案例不是实际会员记录。采集日期不是法规生效日期。Drafted from linked official texts and agency guidance. Both language interpretations are CTAC AI-assisted drafts pending human review; examples are illustrative, not member records. Capture dates are not legal effective dates.
相关实务指南Related practical guides
中文为 CTAC 白话说明，不是官方译文，也不构成个案法律意见。请先核对适用范围、来源版本与最新官方通知。CTAC plain-language explanations are not official translations or case-specific legal advice. Check scope, source editions and current official notices.