The inspection file contains identifying information for the inspection such as the U. The violation file contains details on each violation that was used in SMS calculations. This includes an identifier linking the violation to the inspection in which it was cited, the violation code, violation description, and information related to the SMS methodology.
The file contains a record for each commercial motor vehicle involved in a crash including the U. It also includes information about the severity of the crash tow-away, injury, fatal and the associated severity and time weights used in the SMS. Line expected to exist was not found in the file. Only the ELD File Header Segment and End of File sections require specific line mapping and this error will always refer to a line from one of those sections.
Duplicate File Section. Missing Required Field. Context Dependent. A field defined by the rule as required has not been supplied. When analyzing the file, fields with only whitespace will be considered. Invalid Field Length. A field with a restricted length does not match a specific length, or it is outside the valid range of length.
Field Value is Outside Valid Range. For numeric fields with a specific range of possible values, the value supplied is a number but it falls outside the range of values defined in the Final Rule. Invalid Field Format. For fields which define a specific structure, the value supplied does not match the format specified in the rule, when this error is. Invalid Value. For fields which are restricted to a specific list of values, the supplied value was not found in the list.
When this error is encountered the list of potential values for the field will be supplied in the detailed error response. Invalid Decimal. The supplied value could not be parsed as a decimal number. Invalid Integer. The field value cannot be parsed as an integer. Invalid Date. The field value could not be parsed as a date. Invalid Time. The field value could not be parsed as a time.
Invalid VIN. The VIN does not have a valid check-digit. See 49 C. Invalid Hex Value. The field could not be parsed as a hex value containing only , A- F and a-f. Unexpected Empty Line. Invalid Line Delimiter. Unexpected Quote Delimiters.
Individual field values in this ELD file have been wrapped with double quote characters. No Lines. The submitted ELD file does not contain any line delimiters. Please review the submitted file to ensure the correct delimiter has been used. Empty File. The submitted ELD file is blank and does not contain any usable. Please check to make sure you have submitted the correct file.
Invalid Coordinate Value. The value supplied is not valid for a coordinate component longitude or latitude. Invalid ELD. Registration Information. This will be a warning if the issue is an expired or inactive certificate. ELD Revoked. Certificate Expired. Parameter Mismatch. This will be a Warning severity when submitted using the test flag, but will be an Error when submitted without this flag set.
Test Information. When the test. Either the email was not signed or it was signed using a certificate not associated with the ELD. Unable to Decrypt the. Invalid Message Subject. When using email transfer, the subject line of the email did not conform to any of the three formats described in. Multiple Attachments. After decrypting the email message, more than one attachment was found.
No Attachment. Each of the three 3 data check values use a mapping formula to translate the text contained in the file into a numeric value. For a single character to derive the numeric encoding:. See below. Encoded Character Sequence Example. See section 4. The event data check should be calculated at the time the event is created and stored along with the event. To calculate the event data check:. Event Data Check Calculation Example.
Numeric Mapping. Event Type. Event Code. Event Date. Event Time. Vehicle Miles. Engine Hours. Event Latitude. Event Longitude. ELD Username. XOR The line data check value is calculated on each line of the ELD output file, with the exception of the section headers and the File Data Check line.
The value is appended as a final field in the line when the data file is created. To calculate the line data check:. No space, tab, or other whitespace characters need to be inserted to signify that the intention is for the field to be empty. Field Fields are the individual values contained in an ELD file line. Section Header The section header consists of a line and the value contained in that line which define the various sections of the ELD file.
Section header lines do not contain line data check values and do not contribute to the file data check value. Table of Contents. List of Figures Figure This document provides developers with the interface functions and output file parameters required for ELDs to be fully functional and compliant.
The File Validator is not a mandatory step to self-certify; however, the tool is provided to assist providers in verifying that their ELD files meet with the technical specifications specified in the ELD rule.
Rules of Behavior Self-Certifying your ELD Device constitutes an electronic signature conveying acceptance of the following rules of behavior: I will not knowingly interfere with, disable, circumvent, or compromise any and all security controls, auditing, or monitoring enabled on FMCSA networks supporting ELDs.
I will not knowingly introduce any malicious code into the system or the DOT network. I will not share security-related information about the FMCSA information systems, software, or networks with entities outside the FMCSA unless otherwise authorized and approved in writing. I will not share any ELD-specific data, such as authentication values or private key information.
I understand that violations of the above principles and practices may lead to reprimand and or civil or criminal prosecution. I understand that the system is an official U. Federal Government web-based system and that my acceptance expressly gives assurance that I will comply with all U. Federal Government and Department of Transportation DOT regulations, policies, and procedures governing the protection, handling, processing, transmission, distribution, and destruction of sensitive unclassified information utilized by the system.
An Output File Comment, as provided by safety enforcement. FMCSA validates the client certificate with certificate submitted by the provider during self- certification of ELD, and verifies that the client certificate has not expired or been removed by the provider and that the ELD has not been removed from the self-certified list. ELD data file is validated and response is sent back to the caller.
Based on the validation status the file will: If no errors are found, it will be passed on to the inspector. If errors are found, they will be indicated in the SOAP response and the inspector will be informed of the validation failure.
Certificate validation will be enforced when using the test flag. Testing device certificate containing both public and private keys. Sample ELD Identifier. Has been self-certified and approved via the ELD registration website. Is capable of establishing a secure communication channel with the SOAP web service endpoint. When using the test flag defined below, the provider may utilize the sample ELD Identifier, sample ELD Registration ID, and testing device certificate, which will be provided to registered providers through the ELD registration website.
Interface The following sections provided implementation details for the ELD submission web service functions. ELD Submission Elements Element Name Description Data Type Constraints OutputFileComment Required: A textual field that may be populated with information pertaining to the created ELD output file; An authorized safety official may provide a key phrase or code to be included in the output file comment, which may be used to link the requested data to an inspection, inquiry, or other enforcement action; if provided to the driver by an authorized safety official, it must be entered into the ELD and included in the exchanged dataset as specified.
String characters in length. String 6 characters. String 4 characters. String 25 characters in length, plus an optional file extension ex. String String of variable length. Currently there is only a single valid version of the file as defined by the Final Rule published December 16, Version Enum Currently only the value V1 1 is available.
When the service is run in test mode the ELD output file will not be made available to any inspectors through internal mechanisms.
Boolean True or false, If no value is provided, false is assumed. ErrorCount Required: Number of validation messages identified. Integer Integer of 0 or greater. Errors Optional: If ErrorCount is greater than 0, an array of ValidationError objects describing the individual validation issues found with the file. ValidationError[] Array of 0 or more items. Broadcast Required: Global message from FMCSA, will be used in conjunction with email and other distribution channels to communicate major program announcements.
String Max length of characters. SubmissionId Required: Identifier used to track the submission internally, can be used to identify a specific submission when discussing validation issues with FMCSA support staff. GUID Globally unique value 3. Message Required: Short general description of the issue encountered when validating the file and ELD.
A comprehensive list of potential errors is included with this handbook. Detail Optional: If supplied, the detailed message will give additional information which will aid the provider in diagnosing the specific instance of the issue. Line Required; Number of the file line on which the error was encountered.
For errors related to missing lines or global file errors, a value of 0 will be used. Integer First line of the file will be considered 1. Start Required: Column within the line at which the error begins, for errors in which a 0 would be returned for the Line value, a 0 will also be returned for the Start value. Integer First position in the line is 1, final position in the line is the line length. End Required: Column within the line at which the error ends, for errors in which a 0 would be returned for the Line value, a 0 will also be returned for the End value.
DiagnosticResponse This section contains descriptions for the element names Status, Detail, and Broadcast as they pertain to the DiagnosticResponse. DiagnosticResponseStatus Enum Any status. Detail Optional: If supplied the detailed message will give additional information which will aid the provider in diagnosing the specific instance of the issue. String Optional, max length of characters 3. The ELD file will be validated. Signature will be validated using the ELD registration database.
Has been registered and approved via the ELD registration website. Interface The following section defines the email interface.
Provider registration checked and signature confirmed. File will be validated. File will be stored for retrieval by the inspector. Format Purpose Cont. Once received the email service will do the following: Received email will be decrypted. Wait, employers can't reach you! By checking this box and clicking the "Send me job offers" button below. I understand that my consent is not required to get job alerts. Jul 28, 2. Jul 28, 3. Ridgeline , Jul 28, Jul 28, 4.
Thanks guys. I have the green book for myself, my school gave I to me as required reading materials. He went thru a mega carrier and did not receive one and has received very little education regarding FMCSA regulations. I was trying to find him something that he could have on hand in a truck tucked away somewhere, but didn't realize how often the regulations could be changed and seemingly, without warning. I'll send him the link for the CFR. Jul 29, 5. Jul 29, 6.
0コメント