See what safety officials see when they open your ELD output file

FMCSA logo
Electronic Logging Device

Now Available: Enforcement View of ELD Output Files

It is now possible for ELD providers to see the same view as safety officials for select ELD output files that have been successfully submitted to FMCSA.

Updates to ELD Provider Portal

The ELD Provider Portal has the information you need to develop and test ELDs. We have now made it even easier for you to find this information on our site. Upon logging in, you’ll see an updated landing page and new links in the side navigation.

Develop and Test Your Device

One added feature is a new landing page that puts all the downloadable materials and information provided by FMCSA in one place. This includes the ELD Interface Control Document and Web Services Development Handbook, ELD public key, and more.

File Validator Archive and ELD Test Output Files

If you have successfully submitted ELD Output files to FMCSA, you may now be able to see how safety officials will view these files. This is an optional step you can take to ensure the accuracy and completeness of your ELD output files.

How can I see the enforcement view of my ELD output files?

Files successfully submitted to FMCSA in one of the following ways can be seen in the enforcement view:

  1. Files submitted to the FMCSA File Validator that received a success message. Access the enforcement view of these files in your File Validator Archive.
  2. Files that have been successfully submitted to the FMCSA Web Services test environment. To access the enforcement view, these test files must be tagged with the ELD Identifier and ELD Registration ID your company has on file with FMCSA. Access enforcement view of these files in your ELD Test Output Files.
The ELD Provider Portal has the information you need to be ready for December 18.
Login to your Account

Q&A: FMCSA addresses your technical questions

As announced on October 20, 2017, ELD providers are able to verify successful submission of your ELD data files via Web Services. Below are some frequently asked questions on this process to assist you in conducting a successful test.

Q: What does the response “InvalidRegistrationData” mean when I submit a Ping request using the “test” information provided by FMCSA?

A: There is no test mode provided for the Ping request. Any Ping requests sent with the test value provided by FMCSA will return this invalid registration data message.

Q: When submitting a request to the ELD submission service, I am receiving the response below. How can I resolve this?

An error occurred while making the HTTP request to This could be due to the fact that the server certificate is not configured properly with HTTP.SYS in the HTTPS case. This could also be caused by a mismatch of the security binding between the client and the server.

A: This is an error which comes from the .Net framework choosing to use a security protocol other than TLS 1.2. You can resolve this by applying the following setting prior to making the call to the ELD Service:

ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;

Q: I am receiving a response with code 403 from the ELD submission service. How do I resolve this?

A: You will receive a 403 response if you have not correctly associated your client certificate with your request. The methods for making this connection will vary by device. This message indicates that the issue is with how the certificate is being sent, rather than with the certificate itself.

Q: When submitting the request I am getting no response back at all. How can I resolve this?

A: If you are using Java, check your default settings. By default, Java does not send the Action header defining the SOAP function to be called in the SOAP header. Try adjusting this setting and re-submitting.

More questions are answered in the updated ELD Technical Specification Frequently Asked Questions. These questions and answers are intended to assist ELD providers in creating ELDs that comply with the ELD rule.

Have additional questions? Let us know.