ELD List
The listed devices are self-certified by the manufacturer. The Federal Motor Carrier Safety Administration does not endorse any electronic logging devices.
| Device Name | Model Number | Software Version | ELD Identifier | Image | User Manual | Company | Phone | Company Website | Address | Supported Data Transfer Methods | Supported Data Transfer Description | ELD Malfunctions | Certifying Statement | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| "Compliance Now" Hours of Service | Android & CalAmp 4230 | 1.0.1905.190710 | GEO001 | Download | Download | Geosavi Inc. https://geosavi.com | 1-800-261-4361 | support@geosavi.com | https://geosavi.com | 8230 E Broadway Blvd. Ste. E9B, Tucson, AZ 85750 | Data Transfer The Compliance Now provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. Selecting the Data Transfer button from the Main HOS Main Screen will display the list of supported data transfer options which are via Bluetooth, Email and USB. A Select Vehicle option is also available for selecting a vehicle upon performing the data transfer, this option enables the Compliance Now to produce a data file or a series of data files of ELD records for a subset of its vehicles used by the driver. * Transfer via Bluetooth - this option enables the user to transfer files through Bluetooth. The ELD prompts for an output file comment which the driver may enter (optional). After the input, if Bluetooth is not yet turned on, a prompt will appear asking you to turn it on. You will then be asked to select the device name to which the data will be transmitted via Bluetooth. * Transfer via Email - this option enables the user to transfer files through email. The ELD output file transferred is encrypted using AES-256 in FIPS Publication 197. Before sending, the ELD prompts for an output file comment which the driver may enter (optional). The device's default email application will then be opened before sending the email to which the data will be transferred. * Transfer via USB - this option enables the user to transfer files through USB (external devices). However, prior to saving the driver’s ELD file to an external storage/device, the ELD re-authenticates the driver account by asking for its password. | Malfunctions The Compliance Now ELD is capable of monitoring its compliance for various detectable malfunctions. At each instance when an ELD malfunction event is detected or cleared by the Compliance Now ELD, the ELD records the event. The recorded malfunction events are inconsistencies found while monitoring the ELD against FMCSA compliance requirements. Malfunction occurrences are indicated in the application header and in the Android notification toolbar with the letter ‘M’, respectively. The following shows the list of detectable malfunctions: ? Power Malfunction ? Engine Synchronization Malfunction ? Timing Malfunction ? Position Malfunction ? Data Recording Malfunction ? Data Transfer Malfunction Once the Malfunctions indicator ‘M’ is tapped, a dialog will be displayed with a list of the detected malfunction events alongside a ‘Clear’ button for each event. Tapping the Clear button will clear out the detected malfunction event. | Certifying Statement of FMCSA Regulation Testing The Compliance Now ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The Compliance Now ELD was installed on various types and sizes of Android phones and tablets. Testing was performed through the use of a J1939 simulator and actual vehicles while having been connected to the VBUS with Geometris & Calamp4230 connected devices. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the Hours of Service web application (portal) that can be accessed through a web browser. | |
| "All-In-One" ELD by HOS247 | FLT4 | 4.1 and up | 247HOS | Download | Download | HOS247 LLC | 415-839-9977 | hello@hos247.com | www.hos247.com | 203 Flamingo Rd Unit 507, Mill Valley, CA 94941 | "All-In-One" ELD by HOS247 is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item and then press “Send Logs” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, press “Email Logs”, enter an email provided by an authorized safety official and press “Send“ button. | "All-In-One" ELD by HOS247 monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The "All-In-One" ELD by HOS247 Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on the "All-In-One" ELD by HOS247 during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | "All-In-One" ELD by HOS247 meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. HOS247 ELD was tested to comply with FMCSA regulations by completing steps and testing procedures described in Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| "Prime8" ELD by Gorilla Safety | GS0001 | 3.3.5 And Above | GS0001 | Download | Download | Gorilla Fleet Safety, LLC | 844-636-1360 | info@gorillasafety.com | http://www.gorillasafety.com | 22327 Gosling Rd, Spring, TX 77379 | Data transfer is easily done from the mobile device by clicking on the "Email Logs and DVIR" button in the inspection screen. Steps: 1. Tap the Inspection icon. 2. Tap the "BEGIN NEW INSPECTION" icon 3. Tap the "Email Logs and DVIR" button 4. Enter email address and send | There are no known malfunctions. If a malfunction, as outlined in the ruling, occurs while using the ELD, a message appears to the driver and that malfunction will be recorded. | The product has been thoroughly tested by both internal and external, third party, testers. Each requirement of the ELD has been either met or exceeded. The process of review and testing included the full review of the ruling, testing procedures and debugging of any blocker found in the software package. It further included the retesting by additional quality assurance professionals. Ultimately, the programing and hardware operate as intended and are in compliance. | |
| TST 1 ELD | TRS | 2.23.11 and later | TRS220 | Download | Download | TST GROUP INC. | +13314012336 | tstgroupinc@gmail.com | www.tsteld.com | 258 PATRICIA LANE , EAST DUNDEE /IL/60118 | Telematic (Web Service, Email) | The data transfer method utilized by TST 1 ELD is telematics, which includes web services and email. To access DOT Inspection Mode, the driver can select "Start Inspection" to display logs for the safety officer, or choose "Email logs" to send them via email or "Send logs" to transfer them through web services. | TST 1 ELD records any engine synchronization diagnostics or other malfunctions as per 49 CFR part 395, subpart B, Appendix A, section 4.6.1.2. The malfunction procedures are outlined in a document provided to users. | TST 1 ELD certifies that the ELD has been tested and found to adhere to FMCSA's testing procedures, demonstrating compliance with federal legislation. Therefore, it meets the requirements of the ELD mandate. |
| TT ELD 30 (ios) | ARN752 | 4.4.7 | CZGS10 | Download | Download | TT ELD Inc | 8339070707 | support@tteld.com | https://tteld.com | 799 N Court Street Suite 7, Medina OH 44256 | Telematic (Web Service) | TT ELD platform build for recording, storing and transferring the ELD data via telematics method of transferring. In order to transfer data, user should use Web services and Email. Transferring data to authorized safety official with web service takes two steps, first go to “INSPECTION” from menu bar and then press “SEND ELD OUTPUT FILE TO DOT”. In order, send the ELD data with Email, Driver should go to “INSPECTION” from menu bar and press “EMAIL LOGS”, enter email address provided by authorized safety official then press “SEND LOGS”. | The TT ELD hardware capable of monitoring its compliance with technical requirement and detects malfunctions and keeps records of its malfunction. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. All TT ELD malfunctions are stored and can withdraw when data needed for further analysis. If any malfunction occurs - driver will be notified with a popup describing information about the malfunction. | TT ELD platform is tested in various types of iPad devices and the team of TT ELD goes through all processes and steps of the ELD Test Plan and Procedures provided by FMCSA. We certify the ELD has been tested and fully passed with all the FMCSA ELD Mandate Compliance. |
| Verizon Connect WorkPlan & HOS ELD (Android & iOS) - Formerly Telogis WorkPlan & HOS | Calamp LMU 3640 Series | Workplan 4/HOS 3 | TC3640 | Download | Download | Verizon Connect | +1 (949) 389 5500 | support@verizonconnect.com | https://www.verizonconnect.com | 20 Enterprise, Ste 100, Aliso Viejo, CA 92656 | Verizon Connect ELD uses an electronic data transfer method to deliver driver logs. The driver can send the logs via email or web services to FMCSA from the application. Below are the step by step instructions: o Click Actions from main HOS screen o Select Inspector Mode o Select the transfer icon at the top of the screen o Select either Email to FMCSA or Upload to FMCSA o Note: Driver will have to enter their password to leave Inspector Mode | Verizon Connect ELD supports the following malfunctions: ▪ Power Compliance Malfunction – There has been a hardware issue or possible tampering with the installed unit. The recorded engine on and off events do not match between the mobile device and the vehicle unit. ▪ Engine Synchronization Compliance Malfunction – The mobile device has lost connectivity to the vehicle ECM for more than 30 minutes in a 24 hour period. During this time, the data on engine power status, vehicle motion status, miles driven and engine hours were not accessible. ▪ Timing Compliance Malfunction – There was a discrepancy of more than 5 minutes between the vehicle hardware and the mobile device, or between the mobile device and a network sourced timestamp. ▪ Positioning Compliance Malfunction – The GPS signal has been lost and the mobile device has not been able to retrieve a valid location for more than 60 minutes in a 24 hour period. ▪ Data Recording Compliance Malfunction – The mobile device is unable to properly record required data due to not enough storage space on the device. The mobile device can no longer record new events and events that have not been uploaded might be lost. ▪ Data Transfer Compliance Malfunction – The automatic data transfer check (that is performed once every 24 hours) has failed more than 3 times consecutively. | This statement is to certify that the Verizon Connect ELD application and the hardware unit (TC3640) combined offering is in compliance with the U.S. Department of Transportation (“DOT”) Federal Motor Carrier Safety Administration (“FMCSA”) Electronic Logging Device (“ELD”) for Hours-Of-Service (“HOS”) Requirements (“FMCSA ELD Requirements”), 49 CFR Part 395 Subpart B. The Verizon Telogis ELD offering has gone through extensive testing using the distributed testing procedures as outlined by the FMCSA , along with additional field/drive testing. Using this offering, customers are able to to record, transmit and store all hours of service information according to the functional requirements as detailed in the FMCSA regulations noted above. | |
| !A1 - Ez-smart ELD by Ezlogz | Ezlogz DApp 1 | IOS2.4.17/GP2.1.57up | EZSGEO | Download | Download | Ezlogz Inc | (800)670-7807 | support@ezlogz.com | https://ezlogz.com | 201 NE Park Plaza dr, suite 148, Vancouver, WA 98684 | The Ezlogz !A1 ELD on Blockchain Device offers the fallowing data transfer options: Email, Officer inspection mode, Bluetooth, and Web Services (Output file). | On Logbook screen of ELD driver always see's the eld icon, if any mulfunction occurs - driver will be notified with a popup describing information about the mulfunction and recomendations how driver should try to resolve/fix it and eld icon will become red. Same time information about malfunction save into user history and will be displayed in inspection display/print data, eld data file. If any mulfunctions currently active - eld icon will be red and clicking on it will show current mulfunctions infromation. Also each eld client will recieve a printout, describing possible mulfunctions, how to detect them and steps to resolve them. If need any additional information - please provide more specific question, as nowhere in eld mandate/ELD Test Plan and Procedures specified what exactly should be pointed in this field(explanation, examples) Currently implemented malfunctions: -Power data diagnostic events - if ELD is not powered and fully functional within one minute of the vehicle’s engine receiving power -Power compliance malfunctions - if ELD is not powered for an aggregated in-motion driving time of 30 minutes or more over a 24-hour period across all driver profiles -Engine synchronization data diagnostic events - if no data comes from vehicle ecu's within five seconds of the need -Engine synchronization compliance malfunctions - if no data comes from vehicle ecu's for more than 30 minutes during a 24-hour period aggregated across all driver profiles. -Timing compliance malfunction - if ELD can no longer meet the underlying compliance requirement to record Coordinated Universal Time (UTC) -Positioning compliance malfunction - if ELD fails to acquire a valid position measurement within 5 miles of the commercial motor vehicle moving and 60 minutes has passed(gps failure) -Data recording compliance malfunction - occurs when an ELD can no longer record or retain required events or retrieve recorded logs that are not kept remotely by the motor carrier(memory limit, save failure) -Missing required data elements data diagnostic event - if any required data field is missing at the time of its recording(validation failure) -Data transfer data diagnostic event - if when the operation of the data transfer mechanism(s) is not confirmed(file generation failure, transfer failure) -Data transfer compliance malfunction - if ELD stays in the unconfirmed data transfer mode following the next three consecutive monitoring checks(file generation failure, transfer failure) -Unidentified driving records data diagnostic event - If ELD record driving event with no driver logged in for more than 30 minutes of driving time for an unidentified driver is recorded within a 24-hour period | The Ezlogz techs fallowed all the FMCSA step by step procedures and came back with a positive (P) pass result. IOSIX techs fallowed all the FMCSA step by step procedures and came back with a positive (P) pass result. | |
| !A1 ELD by HOS247 | A1 | 2.2 and up | 1A1ELD | Download | Download | HOS247 LLC | 415-839-9977 | hello@hos247.com | www.hos247.com | 203 Flamingo Rd Unit 507, Mill Valley, CA 94941 | !A1 ELD by HOS247 is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item and then press “Send Logs” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, press “Email Logs”, enter an email provided by an authorized safety official and press “Send“ button. | !A1 ELD by HOS247 monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The !A1 ELD by HOS247 Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on !A1 ELD by HOS247 during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | !A1 ELD by HOS247 meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. !A1 ELD by HOS247 was tested to comply with FMCSA regulations by completing steps and testing procedures described in Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| " DataTrack247 ELD" | DT247-BT-ELD | 3.0.6 | WLI001 | Download | Download | Tamir Alima | 7183952239 | sales@datatrack247.com | http://datatrack247.com | 138-48 Jewel Ave, Flushing/NY/11367 | There is a one page document describing how the officer can enter “officer mode” by clicking on the icon on the top right “officer icon” present on all screens. Once in “officer mode” the Daily Header and Full Day ELD Record defined by the FMCSA are displayed. On the bottom of the page there is a button marked “send report.” Clicking this button brings up the window to email the report to any email address entered. It also features an option to submit the data to the FMCSA web services endpoint. This will utilize the SOAP protocol, per the FMCSA documentation, to transmit the ELD data file and the output file comment entered by the inspecting officer. | Each malfunction has been coded following the "Standard Coding for Required Compliance Malfunction and Data Diagnostic Event Detection" definitions regarding "Malfunction/Diagnostic Code", "Malfunction Description" and "Data Diagnostic Event." Power Compliance monitoring assures that the ELD will become fully functional within one minute of the engine on event and remain on as long as the vehicle's engine stays powered. Engine Synchronization monitoring determines our connection to the ECM. This alerts the driver if there is a loss of connectivity to the ECM. For Timing Compliance Monitoring, we periodically check UTC time via the internet. For Positioning Compliance the ELD records the location, and uses the last valid position measurement and includes the latitude and longitude coordinates and distance traveled in miles, since the last valid position measurement. We also measure the elapsed time during periods when the ELD does not require a valid position measurement within 5 miles. If the time exceeds 60 minutes in a 24 hour period, it is marked as a positioning compliance malfunction. An ELD monitors its storage capacity and integrity and detects data recording compliance malfunction if it can no longer record or retain required events or retrieve recorded logs that are not otherwise catalogued remotely by the motor carrier. The ELD monitors the completeness of the ELD event record information in relation to the required data elements for each event type and records a missing data elements data diagnostics event for the driver if any required field is missing at the time of recording. We check to make sure that our data transfer mechanism works properly at least once every 7 days. All Data Diagnostic events are handled similarly according to the mandate. | I certify that the product meet the FMCSA specifications | |
| "All in one" Ez-Simple ELD by Ezlogz | EZ101 | iOS.2.4.4/GP2.1.45UP | EZLELD | Download | Download | Ezlogz Inc | (800)670-7807 | support@ezlogz.com | https://ezlogz.com | 201 NE Park Plaza dr, suite 148, Vancouver, WA 98684 | The Ezlogz Device uses email, officer inspection mode, Bluetooth, and web services (Output file). | On Logbook screen of ELD driver always see's the eld icon, if any mulfunction occurs - driver will be notified with a popup describing information about the mulfunction and recomendations how driver should try to resolve/fix it and eld icon will become red. Same time information about malfunction save into user history and will be displayed in inspection display/print data, eld data file. If any mulfunctions currently active - eld icon will be red and clicking on it will show current mulfunctions infromation. Also each eld client will recieve a printout, describing possible mulfunctions, how to detect them and steps to resolve them. If need any additional information - please provide more specific question, as nowhere in eld mandate/ELD Test Plan and Procedures specified what exactly should be pointed in this field(explanation, examples) Currently implemented malfunctions: -Power data diagnostic events - if ELD is not powered and fully functional within one minute of the vehicle’s engine receiving power -Power compliance malfunctions - if ELD is not powered for an aggregated in-motion driving time of 30 minutes or more over a 24-hour period across all driver profiles -Engine synchronization data diagnostic events - if no data comes from vehicle ecu's within five seconds of the need -Engine synchronization compliance malfunctions - if no data comes from vehicle ecu's for more than 30 minutes during a 24-hour period aggregated across all driver profiles. -Timing compliance malfunction - if ELD can no longer meet the underlying compliance requirement to record Coordinated Universal Time (UTC) -Positioning compliance malfunction - if ELD fails to acquire a valid position measurement within 5 miles of the commercial motor vehicle moving and 60 minutes has passed(gps failure) -Data recording compliance malfunction - occurs when an ELD can no longer record or retain required events or retrieve recorded logs that are not kept remotely by the motor carrier(memory limit, save failure) -Missing required data elements data diagnostic event - if any required data field is missing at the time of its recording(validation failure) -Data transfer data diagnostic event - if when the operation of the data transfer mechanism(s) is not confirmed(file generation failure, transfer failure) -Data transfer compliance malfunction - if ELD stays in the unconfirmed data transfer mode following the next three consecutive monitoring checks(file generation failure, transfer failure) -Unidentified driving records data diagnostic event - If ELD record driving event with no driver logged in for more than 30 minutes of driving time for an unidentified driver is recorded within a 24-hour period | The Ezlogz techs fallowed all the FMCSA step by step procedures and came back with a positive (P) pass result. | |
| "Gorilla Fleet Intelligence" by Gorilla Safety | Gorilla Fleet Intelligence ELD | 3.3.5 And Above | GS0002 | Download | Download | Gorilla Fleet Safety, LLC | 844-636-1360 | info@gorillasafety.com | http://www.gorillasafety.com | 22327 Gosling Rd, Spring, TX 77379 | We use the web services and email method of transfer. | The malfunctions supported are: Power Compliance Malfunction Engine Synchronization Malfunction Timing Compliance Malfunction Positioning Compliance Malfunction Data Recording Malfunction Data Transfer Malfunction Each of these malfunctions appears prominently for the user to understand the issue. When the user is presented with this, he is able to rectify the situation, contact the manufacturer or use paper logs, as provided as part of the instruction guide, to remain compliant. The malfunctions and malfunction codes can be found in the instruction guide with the required details in order for the driver to understand what he needs to do next. | The product has been thoroughly tested by both internal and external, third party, testers. Each requirement of the ELD has been either met or exceeded. The process of review and testing included the full review of the ruling, testing procedures and debugging of any blocker found in the software package. It further included the retesting by additional quality assurance professionals. Ultimately, the programing and hardware operate as intended and are in compliance. | |
| "Gorilla Fleet Intelligence" by Gorilla Safety ioSIX and Android | Gorilla Fleet Intelligence ELD IA | 3.3.5 And Above | GS0006 | Download | Download | Gorilla Fleet Safety, LLC | 844-636-1360 | info@gorillasafety.com | http://www.gorillasafety.com | 22327 Gosling Rd, Spring, TX 77379 | This ELD uses the web services and email method of transmission. Driver, from the "Dashboard" page of their ELD, will tap on "Roadside Inspection," then "Send Logs." Once they tap send logs, any annotation or note requested by the inspecting officer can be entered by the driver prior to sending. | The malfunctions supported are: Power Compliance Malfunction Engine Synchronization Malfunction Timing Compliance Malfunction Positioning Compliance Malfunction Data Recording Malfunction Data Transfer Malfunction Each of these malfunctions appears prominently for the user to understand the issue. When the user is presented with this, he is able to rectify the situation, contact the manufacturer or use paper logs, as provided as part of the instruction guide, to remain compliant. The malfunctions and malfunction codes can be found in the instruction guide with the required details in order for the driver to understand what he needs to do next. | The product has been thoroughly tested by both internal and external, third party, testers. Each requirement of the ELD has been either met or exceeded. The process of review and testing included the full review of the ruling, testing procedures and debugging of any blocker found in the software package. It further included the retesting by additional quality assurance professionals. Ultimately, the programing and hardware operate as intended and are in compliance. | |
| "Gorilla Fleet Intelligence" by Gorilla Safety ioSIX and iOS | Gorilla Fleet Intelligence ELD II | 3.4.2 And Above | GS0005 | Download | Download | Gorilla Fleet Safety, LLC | 844-636-1360 | info@gorillasafety.com | http://www.gorillasafety.com | 22327 Gosling Rd, Spring, TX 77379 | This ELD uses the web services and email method of transmission. Driver, from the "Dashboard" page of their ELD, will tap on "Roadside Inspection," then "Send Logs." Once they tap send logs, any annotation or note requested by the inspecting officer can be entered by the driver prior to sending. | The malfunctions supported are: Power Compliance Malfunction Engine Synchronization Malfunction Timing Compliance Malfunction Positioning Compliance Malfunction Data Recording Malfunction Data Transfer Malfunction Each of these malfunctions appears prominently for the user to understand the issue. When the user is presented with this, he is able to rectify the situation, contact the manufacturer or use paper logs, as provided as part of the instruction guide, to remain compliant. The malfunctions and malfunction codes can be found in the instruction guide with the required details in order for the driver to understand what he needs to do next. | The product has been thoroughly tested by both internal and external, third party, testers. Each requirement of the ELD has been either met or exceeded. The process of review and testing included the full review of the ruling, testing procedures and debugging of any blocker found in the software package. It further included the retesting by additional quality assurance professionals. Ultimately, the programing and hardware operate as intended and are in compliance. | |
| "Gorilla Fleet Intelligence" by Gorilla Safety Pacific Track and Android | Gorilla Fleet Intelligence ELD PA | 3.3.5 And Above | GS0003 | Download | Download | Gorilla Fleet Safety, LLC | 844-636-1360 | info@gorillasafety.com | http://www.gorillasafety.com | 22327 Gosling Rd, Spring, TX 77379 | This ELD uses the web services and email method of transmission. Driver, from the "Dashboard" page of their ELD, will tap on "Roadside Inspection," then "Send Logs." Once they tap send logs, any annotation or note requested by the inspecting officer can be entered by the driver prior to sending. | The malfunctions supported are: Power Compliance Malfunction Engine Synchronization Malfunction Timing Compliance Malfunction Positioning Compliance Malfunction Data Recording Malfunction Data Transfer Malfunction Each of these malfunctions appears prominently for the user to understand the issue. When the user is presented with this, he is able to rectify the situation, contact the manufacturer or use paper logs, as provided as part of the instruction guide, to remain compliant. The malfunctions and malfunction codes can be found in the instruction guide with the required details in order for the driver to understand what he needs to do next. | The product has been thoroughly tested by both internal and external, third party, testers. Each requirement of the ELD has been either met or exceeded. The process of review and testing included the full review of the ruling, testing procedures and debugging of any blocker found in the software package. It further included the retesting by additional quality assurance professionals. Ultimately, the programing and hardware operate as intended and are in compliance. | |
| "Gorilla Fleet Intelligence" by Gorilla Safety Pacific Track and iOS | Gorilla Fleet Intelligence ELD PI | 3.3.5 And Above | GS0004 | Download | Download | Gorilla Fleet Safety, LLC | 844-636-1360 | info@gorillasafety.com | http://www.gorillasafety.com | 22327 Gosling Rd, Spring, TX 77379 | This ELD uses the web services and email method of transmission. Driver, from the "Dashboard" page of their ELD, will tap on "Roadside Inspection," then "Send Logs." Once they tap send logs, any annotation or note requested by the inspecting officer can be entered by the driver prior to sending. | The malfunctions supported are: Power Compliance Malfunction Engine Synchronization Malfunction Timing Compliance Malfunction Positioning Compliance Malfunction Data Recording Malfunction Data Transfer Malfunction Each of these malfunctions appears prominently for the user to understand the issue. When the user is presented with this, he is able to rectify the situation, contact the manufacturer or use paper logs, as provided as part of the instruction guide, to remain compliant. The malfunctions and malfunction codes can be found in the instruction guide with the required details in order for the driver to understand what he needs to do next. | The product has been thoroughly tested by both internal and external, third party, testers. Each requirement of the ELD has been either met or exceeded. The process of review and testing included the full review of the ruling, testing procedures and debugging of any blocker found in the software package. It further included the retesting by additional quality assurance professionals. Ultimately, the programing and hardware operate as intended and are in compliance. | |
| "HOS Reporter PLUS" | XEL-003 | 215 or Higher | XEL003 | Download | Download | HOS-Reporter | 844-567-3191 | sales@hos-reporter.com | http://www.hos-reporter.com | 4740 Von Karman Ste #120, Newport Beach, CA 92660 | Local (USB, Bluetooth) , Telematic (Web Service, Email) | To submit the Output File to an authorized safety official, the driver selects the “Export ELD Data File” from the Logbook screen. The driver, then, will select one of the following methods: - FMCSA web service: This option securely communicates to FMCSA's end-point ad obtains submission ID. - ELD Email Interface: This option transfer an encrypted email to FMCSA email address | Low battery, network disconnection, low internal memory space, ECM data transfer failure, location sensor failure. In addition, the following malfunctions are detected (and appropriate records created) by the XEL003: - Power data diagnostic (diagnostic - 1) - Engine synchronization data diagnostic (diagnostic - 2) - Missing required data elements (diagnostic - 3) - Data transfer (diagnostic - 4) - Unidentified driving records data diagnostic (diagnostic - 5) - Other ELD diagnostics (diagnostic - 6 - Power compliance (malfunction - P) - Engine synchronization compliance (malfunction - E) - Timing compliance (malfunction - T) - Positioning compliance (malfunction - L) - Data recording compliance (malfunction - R) - Data transfer compliance (malfunction - S) - Other ELD malfunctions (malfunction - O) | The "HOS Reporter PLUS" (XEL003) was tested on a diverse range of CMVs from different manufacturers and models as well drivers with different experience and backgrounds. Tests were also performed on different environments (indoor, outdoor, inside and outside CMVs). Procedures and areas of examinations were followed according to the “ELD Test Plan and Procedures” version 1.0 document released by FMCSA on April 25th 2016. The Requirement Traceability Matrix (RTM) was used and fully verified to ensure ELD compliance. Corrective actions and regression tests were made on all Failed test results. |
| "Journey 8" and "Journey 8R" | iGBL J8R | 7.1.76.409 | IGBW61 | Download | Download | iGlobal LLC | 734-585-7878 | info@igloballlc.com | www.igloballlc.com | 315 NE 14th Street, Ocala FL 34470 | Telematic (Web Service, Email) | The Journey 8 R supports Wireless Web Service and Email transmission of the ELD Output file for Data Transmission. To create an output file for Transmission, the user will need to press the ELD Transmission button that is located on the Menu Bar on the Top of all screens on the ELD. When this button is pressed, the user will be have the ability to enter an output file comment and chose Wireless Web Transmission or Email Transmission. Once the Transmission type is pressed a request is generated on the ELD to generate an output file and then to send to the selected transfer mechanism. The user will also have the ability to display their Daily Header and Event list to an authorized safety office by accessing the Elog tile, selecting review logs and then choosing Daily header or Event List. From the review logs screen the user and authorized safety official will also be able to view the drivers daily log graph. | The summary of malfunctions is as follows: Power Compliance Malfunction - Created when there is a aggregated In-Motion Driving time understatement of 30 minutes or more Engine Synchronization Compliance Malfunction - Created when connectivity to the ECM data sources is lost for more than 30 minutes in a 24 hour period. Timing Compliance Malfunction - Created when ELD time exceeded a 10 minute deviation from the Coordinated Universal Time Positioning Compliance Malfunction - Created when ELD fails to acquire a valid position measurement within 5 miles of the trucks movement and has elapsed a cumulative 60 minutes in a 24-hour period Data Recording Compliance Malfunction – Created when ELD is no longer able to record/retain events or retrieve recorded logs. Data Transfer Compliance Malfunction - Created when ELD has stayed in an unconfirmed data transfer mode for three consecutive monitoring checks. Other ELD Malfunction - Created when ELD has failed to Synch logs | The software used in the Journey 8 tablet is the same software we already put through rigorous testing before we registered the EDGE MDT, but the hardware is different. I certify that both the hardware and software have been sufficiently tested and meet all known requirements of the ELD Mandate. New testing was completed with the tablet to ensure every test case passed. |
| #1 ELD by HOS247 | FLT3 | 2.5 and up | 247ELD | Download | Download | HOS247 LLC | 415-839-9977 | hello@hos247.com | www.hos247.com | 203 Flamingo Rd Unit 507, Mill Valley, CA 94941 | #1 ELD is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item and then press “Send Logs” button. In order to send the ELD records via Email a driver must press “DOT Inspection” menu item, press “Email Logs”, enter an email provided by an authorized safety official and press “Send“ button. | #1 ELD monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The #1 ELD Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on #1 ELD during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | #1 ELD meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. #1 ELD was tested to comply with FMCSA regulations by completing steps and testing procedures described in Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| .ELD-Discounts | LMU4230K | 2.2 | VB0G12 | Download | Download | iConnect Inc. | 844-539-8255 | sales@eldsmartphone.com | www.iConnectamc.com | 4455 Lyndon B Johnson Fwy, Dallas, Texas 75244 | 1. To your logs, select "Send/Print Logs" then choose the desired option and follow the prompts to perform the desired task. 2. Transfer options include email, bluetooth, & usb. 3. Select the method for sharing the logs 4. Select to Send/Transfer Logs | Power compliance malfunction There has been a hardware issue or possible tampering with the unit that is installed in your vehicle. The recorded engine on and off events do not match between the mobile device and the vehicle unit. Possibly the CMV has been operated with the hardware unit unplugged. Engine synchronization compliance malfunction The mobile device has lost connectivity to the vehicle unit for more than 30 minutes during a 24-hour period. During this time the data on engine power status, vehicle motion status, miles driven, and engine hours could no longer be accessed. Timing compliance malfunction There was a discrepancy of more than 5 minutes, either between the mobile device's time and the hardware unit’s time, or, between the ECM’s time and the hardware unit’s time. Positioning compliance malfunction The GPS connection has been lost and the mobile device has not been able to retrieve a valid location for more than 60 minutes within a 24-hour period. Check your GPS aerial. Data recording compliance malfunction The mobile device is unable to properly record required data, because there is not enough storage space available on the device. The mobile device can no longer record new events and you might lose events that have not been uploaded yet. Data transfer compliance malfunction The automatic data transfer check that is done once within each 24-hour period has failed more than 3 times. This means that you might have issues if you try to transfer your data. | I certify the ELD has been tested to fully compile with FMCSA ELD Mandate Compliance. | |
| .ELDSmartPhone | LMU4230J | 2.2 | VB0G11 | Download | Download | iConnect Inc. | 844-539-8255 | sales@eldsmartphone.com | www.iConnectamc.com | 4455 Lyndon B Johnson Fwy, Dallas, Texas 75244 | 1. To your logs, select "Send/Print Logs" then choose the desired option and follow the prompts to perform the desired task. 2. Transfer options include email, bluetooth, & usb. 3. Select the method for sharing the logs 4. Select to Send/Transfer Logs | Power compliance malfunction There has been a hardware issue or possible tampering with the unit that is installed in your vehicle. The recorded engine on and off events do not match between the mobile device and the vehicle unit. Possibly the CMV has been operated with the hardware unit unplugged. Engine synchronization compliance malfunction The mobile device has lost connectivity to the vehicle unit for more than 30 minutes during a 24-hour period. During this time the data on engine power status, vehicle motion status, miles driven, and engine hours could no longer be accessed. Timing compliance malfunction There was a discrepancy of more than 5 minutes, either between the mobile device's time and the hardware unit’s time, or, between the ECM’s time and the hardware unit’s time. Positioning compliance malfunction The GPS connection has been lost and the mobile device has not been able to retrieve a valid location for more than 60 minutes within a 24-hour period. Check your GPS aerial. Data recording compliance malfunction The mobile device is unable to properly record required data, because there is not enough storage space available on the device. The mobile device can no longer record new events and you might lose events that have not been uploaded yet. Data transfer compliance malfunction The automatic data transfer check that is done once within each 24-hour period has failed more than 3 times. This means that you might have issues if you try to transfer your data. | I certify the ELD has been tested to fully compile with FMCSA ELD Mandate Compliance. | |
| .eTracELD | LMU4230H | 2.2 | VB0G10 | Download | Download | iConnect Inc. | 844-539-8255 | sales@eldsmartphone.com | www.iConnectamc.com | 4455 Lyndon B Johnson Fwy, Dallas, Texas 75244 | 1. To your logs, select "Send/Print Logs" then choose the desired option and follow the prompts to perform the desired task. 2. Transfer options include email, bluetooth, & usb. 3. Select the method for sharing the logs 4. Select to Send/Transfer Logs | Power compliance malfunction There has been a hardware issue or possible tampering with the unit that is installed in your vehicle. The recorded engine on and off events do not match between the mobile device and the vehicle unit. Possibly the CMV has been operated with the hardware unit unplugged. Engine synchronization compliance malfunction The mobile device has lost connectivity to the vehicle unit for more than 30 minutes during a 24-hour period. During this time the data on engine power status, vehicle motion status, miles driven, and engine hours could no longer be accessed. Timing compliance malfunction There was a discrepancy of more than 5 minutes, either between the mobile device's time and the hardware unit’s time, or, between the ECM’s time and the hardware unit’s time. Positioning compliance malfunction The GPS connection has been lost and the mobile device has not been able to retrieve a valid location for more than 60 minutes within a 24-hour period. Check your GPS aerial. Data recording compliance malfunction The mobile device is unable to properly record required data, because there is not enough storage space available on the device. The mobile device can no longer record new events and you might lose events that have not been uploaded yet. Data transfer compliance malfunction The automatic data transfer check that is done once within each 24-hour period has failed more than 3 times. This means that you might have issues if you try to transfer your data. | I certify the ELD has been tested to fully compile with FMCSA ELD Mandate Compliance. | |
| .NoFeeELD | LMU4230L | 2.2 | VB0G13 | Download | Download | iConnect Inc. | 844-539-8255 | sales@eldsmartphone.com | www.iConnectamc.com | 4455 Lyndon B Johnson Fwy, Dallas, Texas 75244 | 1. To your logs, select "Send/Print Logs" then choose the desired option and follow the prompts to perform the desired task. 2. Transfer options include email, bluetooth, & usb. 3. Select the method for sharing the logs 4. Select to Send/Transfer Logs | Power compliance malfunction There has been a hardware issue or possible tampering with the unit that is installed in your vehicle. The recorded engine on and off events do not match between the mobile device and the vehicle unit. Possibly the CMV has been operated with the hardware unit unplugged. Engine synchronization compliance malfunction The mobile device has lost connectivity to the vehicle unit for more than 30 minutes during a 24-hour period. During this time the data on engine power status, vehicle motion status, miles driven, and engine hours could no longer be accessed. Timing compliance malfunction There was a discrepancy of more than 5 minutes, either between the mobile device's time and the hardware unit’s time, or, between the ECM’s time and the hardware unit’s time. Positioning compliance malfunction The GPS connection has been lost and the mobile device has not been able to retrieve a valid location for more than 60 minutes within a 24-hour period. Check your GPS aerial. Data recording compliance malfunction The mobile device is unable to properly record required data, because there is not enough storage space available on the device. The mobile device can no longer record new events and you might lose events that have not been uploaded yet. Data transfer compliance malfunction The automatic data transfer check that is done once within each 24-hour period has failed more than 3 times. This means that you might have issues if you try to transfer your data. | I certify the ELD has been tested to fully compile with FMCSA ELD Mandate Compliance. | |
| 1701 NCX ELD | NCX1701 | 2.3.1 | RFS6T7 | Download | Download | National Carrier Exchange | 213 232 8687 | support@NationalCarrierExchange.com | https://www.NationalCarrierExchange.com | 5757 W Century Blvd, Suite 700-1, Los Angeles, CA 90045 | 1. In the "My Log" page of the mobile application, select the "Transfer Logs" button. 2. Select the dates for the Logs you wish to transfer by tapping the date boxes. 3. To transfer by Email, tap the "Email" section. The Email will be automatically entered in the email field and your logs will be ready to be emailed. Tap the green transfer button to complete the transfer. 4. If the inspector asks to use Web Services, they will provide a routing code. After you enter the routing code, the last 8 days of your logs will be transferred to the FMCSA, where the inspector can review them. | Hardware Function Displays: Connection (Green Status Light) Cellular Network (Yellow Status Light) Bluetooth Connection (Blue Status Light) GNSS Position Fix (Red Status Light) Unauthorized Movement (Audio Alert) Each status indicator will show a live display of the monitored state of that portion of the ELD. The Software Application running on the Driver's Mobile Device will provide additional data in the event of any malfunctions, such as Compliance Malfunctions and Data Diagnostic Event Detections. Specifically, these are the errors described in TABLE 4 (Page 89), using the provided coding system for Malfunctions and Diagnostic Events: P: Power Compliance malfunction E: Engine Synchronization Compliance malfunction T: Timing Compliance malfunction L: Positioning Compliance malfunction R: Data Recording Compliance malfunction S: Data Transfer Compliance malfunction O: Other ELD-Detected malfunction 1: Power Data Diagnostic event 2: Engine Synchronization Data Diagnostic event 3: Missing Required Data Elements Data Diagnostic event 4: Data Transfer Data Diagnostic event 5: Unidentified Driving Records Data Diagnostic event 6: Other ELD-Identified Diagnostic event | Throughout the development process, we have tested this model of device in a different makes and models of trucks, under a wide variety of use conditions and have corrected all bugs and errors that such testing has revealed through a continuous, iterative development process. At this point, we consider the device's hardware and software ready to release for use by the Trucking Industry. We hereby certify that this device is compliant to meet the requirements imposed by the Federal Motor Carrier Safety Administration's Electronic Logging Device Mandate of December 2015, and any subsequent updates and amendments that have been released to date. | |
| 1ELD | CTG4 | 2.H | CTG4BT | Download | Download | Cartrack USA | 4245008601 | aziz.asad@cartrack.us | https://www.cartrack.us/ | 12100 Wilshire Blvd, 1550, Los Angeles | Following are available OPTIONS Currently Available Data Transfer During Roadside Safety Inspections Driver can enter roadside inspection mode on the tablet and either Email or display the data to the officer during the inspection. Driver can show current 24 hours and past 7 days to the inspecting officer. This will be in a traditional log based view as per current paper based log book inspections. Email Driver can email RODS in a PDF format or data file in a CSV format to the Inspection officer. The CSV file has: (1) a header segment, which specifies current or non-varying elements of an ELD file; and (2) variable length comma-delimited segments for the drivers, vehicles, ELD events, ELD malfunction and data diagnostics records, ELD login and logout activity, and unidentified driver records. Future state, Web Service and Bluetooth data transfer protocols to be defined these will both be available. The 1ELD application has the ability to send RODS via Web services and SOAP based on configurations. | ELD Malfunction events are logged based on Accelerometer and GPS movement and comparison to actual data received from ECM. Connectivity issues are logged in real time based on communication between ECM and ELD. GPS and ELD. Server and ELD. Driver ELD app and ELD. Database Required fields and ELD. The following Malfunctions are all logged by the ELD Power Compliance Malfunctions Engine Synchronization Malfunctions Timing Compliance Malfunctions Position Compliance Malfunctions Data Recording Malfunctions Missing Required Data Malfunctions | The company certifies based on the following testing procedure that the 1ELD device is compliant and passed the FMCSA Test plan and Procedures Requirements. We used a third party Quality assurance and Testing Team. Devices were beta tested in customers for field testing. Detailed user testing and regression testing procedures. For Hardware and Application: Test Case Preparation Automated Script Identification and Modification Manual and Automated Testing Usability Testing Performance Testing Security and Compliance Testing Device Testing QA and testing of all modules excluding ELD-FUNC-4.3.2.5-2 ELD-FUNC-4.9.1-2 ELD-FUNC-4.9.2-5 ELD-FUNC-4.10.1.1-2 ELD-FUNC-4.10.1.1-3 ELD-FUNC-4.10.1.1-4 ELD-FUNC-4.10.1.2-2 ELD-FUNC-4.10.1.2-3 ELD-FUNC-4.10.2-1 | |
| 24HOS ELD / Android | PT30 | 1.0.01 | 024HOS | Download | Download | 24HOS ELD | 13853424411 | safety24hos@gmail.com | http://24hoseld.com | 3957 1000 East, Millcreek, UT, 84124 | Telematic (Web Service, Email) | To transfer your ELD records to authorized Safety Officials, you need to open the "DOT Inspect" menu (Click on the "DOT Inspect" button it the Additional Menu on your device). The DOT Inspection menu provides summaries of all the collected data about the driver, truck, and trip. You may also use this menu to transfer the data to FMCSA during the DOT inspection, certify your logs, or view unidentified records. Click on the “Start Inspection” button and check if your logs are ready to be transferred to the Safety Officials. If everything is OK, click the “Transfer Data” to Roadside Inspector button and choose the method of sending your logs: - Send it to the Personal Email (provided by the inspector); - Send it to the FMCSA Email; - Send it to Web Services (FMCSA). If you select “Personal Email”, you need to enter the recipient's address and add a comment. If you select “Web Services (FMCSA)” or “Email to FMCSA” you need to add a comment. The reporting period will vary depending on the rules of the country in which you operate. | If there are any malfunctions or data diagnostic issues detected, the M/D icon at the top of the app screen will change its color from green to red. In case of a malfunction, the red "M" letter will indicate a Malfunction, and if there is a Data Diagnostic, the red "D" letter will indicate data error. Malfunctions and Data Diagnostic can also be displayed in the Logs menu as Malfunction event or Data Diagnostic event. As of the Malfunctions you can notice such types of issues: -Engine Synchronization -Positioning compliance -Data recording compliance -Unregistered odometer change -Timing compliance -Power compliance As of the Data Diagnostics problem you can notice such types of issue: -Engine synchronization -Missing data elements -Unidentified driving records -Data transfer -Power data diagnostic To learn more about the problem you are facing, tap the M/D icon at the top of the app screen and check the details. | The 24HOS ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The application was installed on various models of Android and iOS operated mobile devices. The testing was performed using a simulator as well as actual motor vehicles. |
| 24HOS ELD / iOS | PT30 | 1.01.01 | 024HOS | Download | Download | 24HOS ELD | 13853424411 | safety24hos@gmail.com | http://24hoseld.com | 3957 1000 East, Millcreek, UT, 84124 | Telematic (Web Service, Email) | To transfer your ELD records to authorized Safety Officials, you need to open the "DOT Inspect" menu (Click on the "DOT Inspect" Button on your device). Click on the “Start Inspection” button and check if your logs are ready to be transferred to the Safety Officials. If everything is OK, click the “Transfer Data” to Roadside Inspector button and choose the method of sending your logs: - Send it to the Personal Email (provided by the inspector); - Send it to the FMCSA Email; - Send it to Web Services (FMCSA). If you select “Personal Email”, you need to enter the recipient's address and add a comment. If you select “Web Services (FMCSA)” or “Email to FMCSA” you need to add a comment. The reporting period will vary depending on the rules of the country in which you operate. | If there are any malfunctions or data diagnostic issues detected, the M/D icon at the top of the app screen will change its color from green to red. In case of a malfunction, the red "M" letter will indicate a Malfunction, and if there is a Data Diagnostic, the red "D" letter will indicate data error. Malfunctions and Data Diagnostic can also be displayed in the Logs menu as Malfunction event or Data Diagnostic event. As of the Malfunctions you can notice such types of issues: -Engine Synchronization -Positioning compliance -Data recording compliance -Unregistered odometer change -Timing compliance -Power compliance As of the Data Diagnostics problem you can notice such types of issue: -Engine synchronization -Missing data elements -Unidentified driving records -Data transfer -Power data diagnostic To learn more about the problem you are facing, tap the M/D icon at the top of the app screen and check the details. | The 24HOS ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The application was installed on various models of Android and iOS operated mobile devices. The testing was performed using a simulator as well as actual motor vehicles. |
| 24RALLY ELD | 2RS | 2.0 or higher | 2RS188 | Download | Download | 24Rally LLC | 224-306-8022 | info@24Rally.com | http://www.24Rally.com | 2591 Dallas Pkwy, Ste 300, Frisco, TX 75034 | 24RALLY ELD is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | 24RALLY ELD monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The 24RALLY ELD Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on 24RALLY ELD during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | 24RALLY ELD meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. 24RALLY ELD was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| 3MD ELD | 3MD 100 Pacific Track iOS | 2120.211122.1 | 3MD100 | Download | Download | 3MD Solutions, LLC | 708-698-1000 | info@3mdinc.com | http://www.3mdinc.com | 6475 Joliet Road, Countryside, IL 60525 | Telematic (Web Service, Email) | The 3MD ELD provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. This can be done by selecting the Roadside Inspection button from the main HOS dashboard and selecting the option for Data Transfer. A list of supported data transfer options is then displayed which include Bluetooth, Email and USB. A Select Vehicle option is also available for selecting a vehicle upon performing the data transfer, this option enables the 3MD ELD to produce a data file or a series of data files of ELD records for a subset of its vehicles used by the driver. Transfer via Bluetooth - this option enables the user to transfer files through Bluetooth. The ELD prompts for an output file comment which the driver may enter (optional). After the input, if Bluetooth is not yet turned on, a prompt will appear asking you to turn it on. You will then be asked to select the device name to which the data will be transmitted via Bluetooth. Transfer via Email - this option enables the user to transfer files through email. The ELD output file transferred is encrypted using AES-256 in FIPS Publication 197. Before sending, the ELD prompts for an output file comment which the driver may enter (optional). The device's default email application will then be opened before sending the email to which the data will be transferred. Transfer via USB - this option enables the user to transfer files through USB (external devices). However, prior to saving the driver’s ELD file to an external storage/device, the ELD re-authenticates the driver account by asking for its password. | The 3MD ELD is capable of monitoring its compliance for various detectable malfunctions. At each instance when an ELD malfunction event is detected or cleared by the 3MD ELD, the ELD records the event. The recorded malfunction events are inconsistencies found while monitoring the ELD against FMCSA compliance requirements. Malfunction occurrences are indicated in the application header and in the iOS notification toolbar with the letter ‘M’, respectively. The following shows the list of detectable malfunctions: Power Malfunction Engine Synchronization Malfunction Timing Malfunction Position Malfunction Data Recording Malfunction Data Transfer Malfunction Once the Malfunctions indicator ‘M’ is tapped, a dialog will be displayed with a list of the detected malfunction events alongside a ‘Clear’ button for each event. Tapping the Clear button will clear out the detected malfunction event. | The 3MD ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The 3MD ELD was installed on various types and sizes of iOS phones and iPad tablets. Testing was performed through the use of a J1939 simulator and actual vehicles while having been connected to the Geometris, Digi WVA, CalAmp 4230, Pacific Track and IOSiX engine connected devices. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the Hours of Service web application (portal) that can be accessed through a web browser. |
| 3MD ELD | 3MD 100 Pacific Track Android | 3.0.2212.220905 | 3MD100 | Download | Download | 3MD Solutions, LLC | 708-698-1000 | info@3mdinc.com | http://www.3mdinc.com | 6475 Joliet Road, Countryside, IL 60525 | Telematic (Web Service, Email) | The 3MD ELD provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. This can be done by selecting the Roadside Inspection button from the main HOS dashboard and selecting the option for Data Transfer. A list of supported data transfer options is then displayed which include Bluetooth, Email and USB. A Select Vehicle option is also available for selecting a vehicle upon performing the data transfer, this option enables the 3MD ELD to produce a data file or a series of data files of ELD records for a subset of its vehicles used by the driver. Transfer via Bluetooth - this option enables the user to transfer files through Bluetooth. The ELD prompts for an output file comment which the driver may enter (optional). After the input, if Bluetooth is not yet turned on, a prompt will appear asking you to turn it on. You will then be asked to select the device name to which the data will be transmitted via Bluetooth. Transfer via Email - this option enables the user to transfer files through email. The ELD output file transferred is encrypted using AES-256 in FIPS Publication 197. Before sending, the ELD prompts for an output file comment which the driver may enter (optional). The device's default email application will then be opened before sending the email to which the data will be transferred. Transfer via USB - this option enables the user to transfer files through USB (external devices). However, prior to saving the driver’s ELD file to an external storage/device, the ELD re-authenticates the driver account by asking for its password. | The 3MD ELD is capable of monitoring its compliance for various detectable malfunctions. At each instance when an ELD malfunction event is detected or cleared by the 3MD ELD, the ELD records the event. The recorded malfunction events are inconsistencies found while monitoring the ELD against FMCSA compliance requirements. Malfunction occurrences are indicated in the application header and in the Android notification toolbar with the letter ‘M’, respectively. The following shows the list of detectable malfunctions: Power Malfunction Engine Synchronization Malfunction Timing Malfunction Position Malfunction Data Recording Malfunction Data Transfer Malfunction Once the Malfunctions indicator ‘M’ is tapped, a dialog will be displayed with a list of the detected malfunction events alongside a ‘Clear’ button for each event. Tapping the Clear button will clear out the detected malfunction event. | The 3MD ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The 3MD ELD was installed on various types and sizes of Android phones and tablets. Testing was performed through the use of a J1939 simulator and actual vehicles while having been connected to the Geometris, Digi WVA, CalAmp 4230, Pacific Track and IOSiX engine connected devices. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the Hours of Service web application (portal) that can be accessed through a web browser. |
| 3MD ELD | 3MD 100 Geometris iOS | 2120.211122.1 | 3MD100 | Download | Download | 3MD Solutions, LLC | 708-698-1000 | info@3mdinc.com | http://www.3mdinc.com | 6475 Joliet Road, Countryside, IL 60525 | Telematic (Web Service, Email) | The 3MD ELD provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. This can be done by selecting the Roadside Inspection button from the main HOS dashboard and selecting the option for Data Transfer. A list of supported data transfer options is then displayed which include Bluetooth, Email and USB. A Select Vehicle option is also available for selecting a vehicle upon performing the data transfer, this option enables the 3MD ELD to produce a data file or a series of data files of ELD records for a subset of its vehicles used by the driver. Transfer via Bluetooth - this option enables the user to transfer files through Bluetooth. The ELD prompts for an output file comment which the driver may enter (optional). After the input, if Bluetooth is not yet turned on, a prompt will appear asking you to turn it on. You will then be asked to select the device name to which the data will be transmitted via Bluetooth. Transfer via Email - this option enables the user to transfer files through email. The ELD output file transferred is encrypted using AES-256 in FIPS Publication 197. Before sending, the ELD prompts for an output file comment which the driver may enter (optional). The device's default email application will then be opened before sending the email to which the data will be transferred. Transfer via USB - this option enables the user to transfer files through USB (external devices). However, prior to saving the driver’s ELD file to an external storage/device, the ELD re-authenticates the driver account by asking for it. | The 3MD ELD is capable of monitoring its compliance for various detectable malfunctions. At each instance when an ELD malfunction event is detected or cleared by the 3MD ELD, the ELD records the event. The recorded malfunction events are inconsistencies found while monitoring the ELD against FMCSA compliance requirements. Malfunction occurrences are indicated in the application header and in the iOS notification toolbar with the letter ‘M’, respectively. The following shows the list of detectable malfunctions: Power Malfunction Engine Synchronization Malfunction Timing Malfunction Position Malfunction Data Recording Malfunction Data Transfer Malfunction Once the Malfunctions indicator ‘M’ is tapped, a dialog will be displayed with a list of the detected malfunction events alongside a ‘Clear’ button for each event. Tapping the Clear button will clear out the detected malfunction event. | The 3MD ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The 3MD ELD was installed on various types and sizes of iOS phones and tablets. Testing was performed through the use of a J1939 simulator and actual vehicles while having been connected to the Geometris, Digi WVA, CalAmp 4230, Pacific Track and IOSiX engine connected devices. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the Hours of Service web application (portal) that can be accessed through a web browser. |
| 3MD ELD | 3MD 100 Geometris Android | 3.0.2212.220905 | 3MD100 | Download | Download | 3MD Solutions, LLC | 708-698-1000 | info@3mdinc.com | http://www.3mdinc.com | 6475 Joliet Road, Countryside, IL 60525 | Telematic (Web Service, Email) | The 3MD ELD provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. This can be done by selecting the Roadside Inspection button from the main HOS dashboard and selecting the option for Data Transfer. A list of supported data transfer options is then displayed which include Bluetooth, Email and USB. A Select Vehicle option is also available for selecting a vehicle upon performing the data transfer, this option enables the 3MD ELD to produce a data file or a series of data files of ELD records for a subset of its vehicles used by the driver. Transfer via Bluetooth - this option enables the user to transfer files through Bluetooth. The ELD prompts for an output file comment which the driver may enter (optional). After the input, if Bluetooth is not yet turned on, a prompt will appear asking you to turn it on. You will then be asked to select the device name to which the data will be transmitted via Bluetooth. Transfer via Email - this option enables the user to transfer files through email. The ELD output file transferred is encrypted using AES-256 in FIPS Publication 197. Before sending, the ELD prompts for an output file comment which the driver may enter (optional). The device's default email application will then be opened before sending the email to which the data will be transferred. Transfer via USB - this option enables the user to transfer files through USB (external devices). However, prior to saving the driver’s ELD file to an external storage/device, the ELD re-authenticates the driver account by asking for it | The 3MD ELD is capable of monitoring its compliance for various detectable malfunctions. At each instance when an ELD malfunction event is detected or cleared by the 3MD ELD, the ELD records the event. The recorded malfunction events are inconsistencies found while monitoring the ELD against FMCSA compliance requirements. Malfunction occurrences are indicated in the application header and in the Android notification toolbar with the letter ‘M’, respectively. The following shows the list of detectable malfunctions: Power Malfunction Engine Synchronization Malfunction Timing Malfunction Position Malfunction Data Recording Malfunction Data Transfer Malfunction Once the Malfunctions indicator ‘M’ is tapped, a dialog will be displayed with a list of the detected malfunction events alongside a ‘Clear’ button for each event. Tapping the Clear button will clear out the detected malfunction event. | The 3MD ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The 3MD ELD was installed on various types and sizes of Android phones and tablets. Testing was performed through the use of a J1939 simulator and actual vehicles while having been connected to the Geometris, Digi WVA, CalAmp 4230, Pacific Track and IOSiX engine connected devices. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the Hours of Service web application (portal) that can be accessed through a web browser. |
| 3MD ELD | Android & Pacific Track PT40 | 3.0.2212.220905 | 3MD100 | Download | Download | 3MD Solutions, LLC | 708-698-1000 | info@3mdinc.com | http://www.3mdinc.com | 6475 Joliet Road, Countryside, IL 60525 | Telematic (Web Service, Email) | The 3MD ELD provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. This can be done by selecting the Roadside Inspection button from the main HOS dashboard and selecting the option for Data Transfer. A list of supported data transfer options is then displayed which include Bluetooth, Email and USB. A Select Vehicle option is also available for selecting a vehicle upon performing the data transfer, this option enables the 3MD ELD to produce a data file or a series of data files of ELD records for a subset of its vehicles used by the driver. Transfer via Bluetooth - this option enables the user to transfer files through Bluetooth. The ELD prompts for an output file comment which the driver may enter (optional). After the input, if Bluetooth is not yet turned on, a prompt will appear asking you to turn it on. You will then be asked to select the device name to which the data will be transmitted via Bluetooth. Transfer via Email - this option enables the user to transfer files through email. The ELD output file transferred is encrypted using AES-256 in FIPS Publication 197. Before sending, the ELD prompts for an output file comment which the driver may enter (optional). The device's default email application will then be opened before sending the email to which the data will be transferred. Transfer via USB - this option enables the user to transfer files through USB (external devices). However, prior to saving the driver’s ELD file to an external storage/device, the ELD re-authenticates the driver account by asking for its password. | The 3MD ELD is capable of monitoring its compliance for various detectable malfunctions. At each instance when an ELD malfunction event is detected or cleared by the 3MD ELD, the ELD records the event. The recorded malfunction events are inconsistencies found while monitoring the ELD against FMCSA compliance requirements. Malfunction occurrences are indicated in the application header and in the Android notification toolbar with the letter ‘M’, respectively. The following shows the list of detectable malfunctions: Power Malfunction Engine Synchronization Malfunction Timing Malfunction Position Malfunction Data Recording Malfunction Data Transfer Malfunction Once the Malfunctions indicator ‘M’ is tapped, a dialog will be displayed with a list of the detected malfunction events alongside a ‘Clear’ button for each event. Tapping the Clear button will clear out the detected malfunction event. | The 3MD ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The 3MD ELD was installed on various types and sizes of Android phones and tablets. Testing was performed through the use of a J1939 simulator and actual vehicles while having been connected to the Geometris, Digi WVA, CalAmp 4230, Pacific Track and IOSiX engine connected devices. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the Hours of Service web application (portal) that can be accessed through a web browser. |
| 3PL TEK ELD | 3RS | 2.0 or higher | 3RS266 | Download | Download | 3PL TEK INC | 415-481-0418 | support@3pltek.com | http://www.3pltek.com | 1200 FRANKLIN MALL SUITE 581, SANTA CLARA, CA 95052 | 3PL TEK ELD is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | 3PL TEK ELD monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The 3PL TEK ELD Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on 3PL TEK ELD during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | 3PL TEK ELD meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. 3PL TEK ELD was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| 48 ELD | 4RS | 2.0 or higher | 4RS123 | Download | Download | 48 ELD | 3127688014 | admin@48eld.com | http://www.48eld.com | 34737 Pyle Center Rd , Frankford/DE/19945 | 48 ELD is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | 48 ELD monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The 48 ELD Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on 48 ELD during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | 48 ELD meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations.48 ELD was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| 5001 MW ELD | MW-ELD-JOJ | 3.15 or higher | MW5001 | Download | Download | Mobile Warrior LLC | 888-474-9284 | customercare@mobilewarrior.com | http://www.mobilewarrior.com/corporate/ | 226 Marmalade Trail, Dawsonville, GA 30534 | From the Report Tab choose the ELD DOT Telemetry Report option and then choose to either send the Data Transfer File via the Wireless Web directly to the FMCSA Web Service account or to transfer the the file into an Email. Once the Email is displayed with the attached file, input the send to email required by the DOT and send it. | Power compliance P : If recorded event sequence find a possibility of in motion time then this ELD record will have a P set. A period of time of more then 30 minutes in the last 24 hours when a power on might have occurred. Field is set true. Time compliance T : If the data incoming from box indicates that the time is not consistent with the mobile device adjusted to the time zone of the driver. This field is set true if these are out of sync by 10 minutes. Engine sync compliance E : monitoring the data set of the last 24 hour of a period of time of more then 30 when the ELD was active and no j bus data is provided. This field is set true Position Location compliance L : must record a failure to track the current location for 60 minutes within 5 miles of the last known location. This will show last know location and time of recording it. Data Recording compliance R :This field is set true if the application is currently unable to create records or sync those records to the server. Monitoring record of unidentified drivers: If the vehicle has a 30 minute period in the last 7 days with unidentified driver time. This alert can be cleared if that time drops to 15 minutes. This field is true. | We modeled our testing using the FMCSA testing requirements along with our own internal testing and quality control procedures. | |
| 7 DAYS LOGS ELD | 7RS | 2.24.15 and higher | 7RS223 | Download | Download | 7 DAYS LOGS | 5179404499 | info@7dayslogs.com | https://www.7dayslogs.com | 11775 KINGS COLONY RD, GRAND BLANC, MI 48439 | Telematic (Web Service, Email) | The data transfer method supported by 7 DAYS LOGS ELD is telematics. RODS can be sent via wireless web services or email during roadside inspections using the mobile app's DOT Inspection Mode. Drivers can also display RODS to the officer directly on their mobile devices. | Pursuant to section 4.6, Appendix A, 7 DAYS LOGS ELD software continually self-monitors for diagnostic events and malfunctions. Any issues the software detects are logged and visually indicated to the driver per 4.6.2.1. | 7 DAYS LOGS ELD system has undergone all the necessary tests to prove compliance with FMCSA regulations. The product met every item listed in the FMCSA's Requirements Traceability Matrix and has proven efficient and compliant on the road. |
| 888 ELD | EIG8T | 2.16-2 or higher | 8RS262 | Download | Download | MAUMAU LLC | +19293206290 | 888eld@gmail.com | http://www.888eld.com | 166 FAIRFIELD DR, ROMEOVILLE, IL 60446 | Telematic (Web Service, Email) | 888 ELD, or Electronic Logging Device, is a tool that offers a comprehensive overview of a driver's records during a roadside inspection. Not only does it provide this information within the app, but it also facilitates the transfer of telematics data through email or web services. The DOT Inspection mode allows the driver to choose the method that works best for them. To transfer ELD records through Web services, the driver needs to access the "DOT Inspection" menu and select the "Send Logs" option. Then, they should choose Web Service as the Data Transfer Type and click the "SEND" button. Similarly, to transfer ELD records via Email, the driver should follow the same steps but select Email as the Data Transfer Type before clicking the "SEND" button. | The 888 ELD system ensures compliance with technical requirements, identifies malfunctions and data inconsistencies, and maintains records of such occurrences. Compliance malfunctions and diagnostic events are classified with specific codes, including P for "Power compliance" malfunction, E for "Engine synchronization compliance" malfunction, T for "Timing compliance" malfunction, L for "Positioning compliance" malfunction, R for "Data recording compliance" malfunction, S for "Data transfer compliance" malfunction, O for "Other" ELD-detected malfunctions, 1 for "Power data diagnostic" event, 2 for "Engine synchronization data diagnostic" event, 3 for "Missing required data elements data diagnostic" event, 4 for "Data transfer data diagnostic" event, 5 for "Unidentified driving records data diagnostic" event, and 6 for "Other" ELD-identified diagnostic events. The 888 ELD Malfunction and Diagnostic Event Records document all malfunctions that occurred during the relevant time period. Active malfunctions are communicated to all drivers who may use the ELD. | 888 ELD has been thoroughly tested to ensure compliance with all the functional requirements outlined in Title 49, Part 395 of Section 4.9.1, Appendix A, Subpart B. 888 ELD can confidently certify that our ELD product adheres to all the necessary ELD regulations. |
| AAT HOS | 1810 | v1.0.0 | AXHOS2 | Download | Download | Air Automotive Tracking Inc. | 18556924756 | info@aatracking.com | http://www.aatracking.com | Suite #1092 - 1820 Avenue M, Brooklyn/NY/11230 | As of now, there are only 2 options for ELD data transfer. 1. The driver can disclose data through an FMCSA's recommended ELD web service(https://eldws.fmcsa.dot.gov) using the public key-private key certificate to the FMCSA's safety official. 2. The driver can transfer the CSV ELD file through the FMSCA's recommended AES-256 encrypted email transfer to the fmcsaeldsub@dot.gov | Power/ Initialization Malfunction - On power-up Device make established connections with network and in-vehicle hardware and run through start-up procedure to make sure all services are running. If one aspect fails to initialize then this is logged and alerted to the driver and system administrator. Position Recording Malfunction - If Void GPS information is being received excessively then this event is logged and alerted to Driver and System administrator. Communication with Vehicle Malfunction - If vehicle data is not being obtained the driver is alerted along with the system administrator. Communication with Network Malfunction - If there is no network communication available or established, then malfunction is logged and data is stored. The driver is notified. Data Transfer Malfunction - With each message sent a confirmation must be returned that it was received in its entirety with Checksum calculation. At that point, the message can be cleared from the buffer. If data is not able to transfer properly this malfunction is alerted to the driver and system Administrator. | Testing of the AAT ELD was certified through successful testing and verification of the FMCSA ELD Test Procedures. The AAT HOS solution complies with FMCSA regulations. The AAT ELD solution was installed on various types and sizes of Android phones and tablets. Testing was performed through the use of a CAN-BUS simulator ( J1939) and actual vehicles with AAT AXON hardware. The test procedures were verified through the use of the Hours of Service web application. | |
| AccuGPS | OBD-Smart-19 | 1.1 | ACCU19 | Download | Download | AccuGPS | 3153080068 | info@accugps.com | https://accugps.com | 5727 E Seneca Turnpike, Jamesville/NY/13078 | Open the accuGPS ELD app, go to “Logs” from the bottom navigation bar. Tap on the share icon on the top right of the screen will bring up a pop-up window. Choose to use “Email” or “Web Service” to submit the report. | accuGPS ELD is capable of monitoring ELD functionalities and detecting malfunctions. Malfunction occurrences are displayed on the top of the screen in the notification area of the mobile apps. The following shows the list of detectable malfunctions: ● Power Malfunction ● Engine Synchronization Malfunction ● Timing Malfunction ● Position Malfunction ● Data Recording Malfunction ● Data Transfer Malfunction Tapping the malfunction notifications will bring up the detailed window, and malfunctions can be reviewed or cleared. | I here certify that accuGPS ELD software and hardware have been tested according to FMCSA ELD regulations and have met the requirements defined by FMCSA. accuGPS ELD was tested following the FMCSA ELD Test procedure and guidelines. accuGPS apps were installed on iOS and Android phones, and accuGPS OBD-Smart hardware was installed on multiple testing vehicles, including passenger cars from the US and foreign countries, as well as heavy-duty vehicles running J1939 protocols. Data collections were verified from accuGPS cloud-based platform and accuGPS ELD mobile apps. | |
| ACTION ELD | ACT | 2.17.4 and higher | ACT282 | Download | Download | ACTION ELD | (224)998-3789 | info@actioneld.com | http://www.actioneld.com | 4000 Hollywood Boulevard Hills, Hollywood/FL/33021 | Telematic (Web Service, Email) | ACTION ELD choice of data transfer method is telematics, web services and email. The application provides a DOT inspection function for drivers to transfer logs to officers or produce an in-app report for the officer to review on their mobile device's screen. | ACTION ELD software monitors the system for any malfunctions and diagnostic events listed in section 4.6.1: power malfunctions, engine synchronization malfunctions, timing malfunctions, position malfunctions, data recording malfunctions, and data transfer malfunctions. All malfunction and diagnostic events are adequately recorded and visually cued for the operator. | Test Plan and Procedures provided by the FMCSA have been applied to ACTION ELD to ensure the ELD functionality necessary for compliance. ACTION ELD certifies the compliance with the ELD mandate. |
| ADVANTAGE KNIGHTS ELD | ARS | 2.0 or higher | ARS128 | Download | Download | Advantage Knights Inc | 847 201 6100 | info@advantageknights.com | https://advantageknights.com/home/ | 847 S Randall Rd #137, Elgin IL 60123 | ADVANTAGE KNIGHTS ELD is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | ADVANTAGE KNIGHTS ELD monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The ADVANTAGE KNIGHTS ELD Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on ADVANTAGE KNIGHTS ELD during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | ADVANTAGE KNIGHTS ELD meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. ADVANTAGE KNIGHTS ELD was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| ADX FLEET ELD | ARS | 2.0 or higher | ARS243 | Download | Download | ADX FLEET ELD INC | 3475066317 | adxfleeteld@gmail.com | http:// | 441 TOMILSON RD APT H6, PHILADELPHIA PA 19116 | ADX FLEET ELD is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | ADX FLEET ELD monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The ADX FLEET ELD Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on ADX FLEET ELD during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | ADX FLEET ELD meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. ADX FLEET ELD was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| AFS WORLD ELD | AFSWD | 2.26.0 or above | ARS251 | Download | Download | AFS WORLD ELD | 2672506414 | info@afsworldeld.com | http://afsworldeld.com | 2820 Welsh rd Unit B, Philadelphia, PA 19152 | Telematic (Web Service, Email) | Through the AFS WORLD ELD system, telematics data transfer is facilitated using either email or web services. The driver can perform the transfer by accessing the DOT Inspection Mode menu and clicking the "Send" button. Furthermore, a separate DOT Inspection Mode button is available for the driver to display the logs report to a DOT officer on their mobile device. | With the goal of maintaining compliance, detecting malfunctions and data inconsistencies, and documenting such occurrences, the AFS WORLD ELD system employs specific codes to classify compliance malfunctions and diagnostic events, such as: ■ P for "Power compliance" malfunction, ■ E "Engine synchronization compliance" malfunction, ■ T for "Timing compliance" malfunction, ■ L for "Positioning compliance" malfunction, ■ R for "Data recording compliance" malfunction, ■ S for "Data transfer compliance" malfunction, ■ O for "Other" ELD-detected malfunctions, ■ 1 for "Power data diagnostic" event, ■ 2 for "Engine synchronization data diagnostic" event, ■ 3 for "Missing required data elements data diagnostic" event, ■ 4 for "Data transfer data diagnostic" event, ■ 5 for "Unidentified driving records data diagnostic" event, ■ 6 for "Other" ELD-identified diagnostic events. The AFS WORLD ELD Malfunction and Diagnostic Event Records record all malfunctions that occurred during the relevant time period and relay active malfunctions to all ELD users. | The FMCSA´s testing procedures require thorough testing of AFS WORLD ELD to verify compliance as an electronic logging system, which has been completed. The system is able to confirm that it meets the requirements of 49 CFR Part 395 Subpart B, including the accurate logging and transmission of hours of service data. |
| AIKS ELOG BL | BLE 4.1 | 3.9.6 or Higher | WLI001 | Download | Download | AikSphere Technologies Inc | (905) 495-9559 | info@aiks.ca | https://aiks.ca | 7015 Tranmere Dr Unit#7, MISSISSAUGA, ON | When entering an inspection scenario, the driver follows the instructions provided on his printed one page manual which instructs the driver to press the "Officer Button" located on the top right of the DriverLog apps' home screen display. This will launch the Officer View. The officer view features a "Send" button and an Add comment button, which allows the officer to enter his identifier and send out the ELD data file through web services or email (both options are available). Following the guidance of the ELD section of the Federal Register...section "4.10.1. Data Transfer Mechanisms," we allow the officer to use both e-mail or Web Services to transfer the driver's data to the official FMCSA ELD e-mail address or the the FMCSA's Web Service repository. Currently the e-mail is formatted exactly to section "4.10.1.2. Wireless Data Transfer Through Email" specifications stated in the Federal Register. Web Services will utilize the SOAP protocol, per the FMCSA documentation, to transmit the ELD data file and the output file comment entered by the inspecting officer. | Each malfunction has been coded following the "Standard Coding for Required Compliance Malfunction and Data Diagnostic Event Detection" definitions regarding "Malfunction/Diagnostic Code", "Malfunction Description" and "Data Diagnostic Event." Power Compliance monitoring assures that the ELD will become fully functional within one minute of the engine on event and remain on as long as the vehicle's engine stays powered. Engine Synchronization monitoring determines our connection to the ECM. This alerts the driver if there is a loss of connectivity to the ECM. For Timing Compliance Monitoring, we periodically check UTC time via the internet. For Positioning Compliance the ELD records the location, and uses the last valid position measurement and includes the latitude and longitude coordinates and distance traveled in miles, since the last valid position measurement. We also measure the elapsed time during periods when the ELD does not require a valid position measurement within 5 miles. If the time exceeds 60 minutes in a 24 hour period, it is marked as a positioning compliance malfunction. An ELD monitors its storage capacity and integrity and detects data recording compliance malfunction if it can no longer record or retain required events or retrieve recorded logs that are not otherwise catalogued remotely by the motor carrier. The ELD monitors the completeness of the ELD event record information in relation to the required data elements for each event type and records a missing data elements data diagnostics event for the driver if any required field is missing at the time of recording. We check to make sure that our data transfer mechanism works properly at least once every 7 days. All Data Diagnostic events are handled similarly according to the mandate. | We certify that our ELD application and related hardware have been tested to meet the FMCSA's test procedures. | |
| AIKS ELOG PICPLUS | PCP4G | 3.9.6 or Higher | WLI001 | Download | Download | AikSphere Technologies Inc | (905) 495-9559 | info@aiks.ca | https://aiks.ca | 7015 Tranmere Dr Unit#7, MISSISSAUGA, ON | When entering an inspection scenario, the driver follows the instructions provided on his printed one page manual which instructs the driver to press the "Officer Button" located on the top right of the DriverLog apps' home screen display. This will launch the Officer View. The officer view features a "Send" button and an Add comment button, which allows the officer to enter his identifier and send out the ELD data file through web services or email (both options are available). Following the guidance of the ELD section of the Federal Register...section "4.10.1. Data Transfer Mechanisms," we allow the officer to use both e-mail or Web Services to transfer the driver's data to the official FMCSA ELD e-mail address or the the FMCSA's Web Service repository. Currently the e-mail is formatted exactly to section "4.10.1.2. Wireless Data Transfer Through Email" specifications stated in the Federal Register. Web Services will utilize the SOAP protocol, per the FMCSA documentation, to transmit the ELD data file and the output file comment entered by the inspecting officer. | Each malfunction has been coded following the "Standard Coding for Required Compliance Malfunction and Data Diagnostic Event Detection" definitions regarding "Malfunction/Diagnostic Code", "Malfunction Description" and "Data Diagnostic Event." Power Compliance monitoring assures that the ELD will become fully functional within one minute of the engine on event and remain on as long as the vehicle's engine stays powered. Engine Synchronization monitoring determines our connection to the ECM. This alerts the driver if there is a loss of connectivity to the ECM. For Timing Compliance Monitoring, we periodically check UTC time via the internet. For Positioning Compliance the ELD records the location, and uses the last valid position measurement and includes the latitude and longitude coordinates and distance traveled in miles, since the last valid position measurement. We also measure the elapsed time during periods when the ELD does not require a valid position measurement within 5 miles. If the time exceeds 60 minutes in a 24 hour period, it is marked as a positioning compliance malfunction. An ELD monitors its storage capacity and integrity and detects data recording compliance malfunction if it can no longer record or retain required events or retrieve recorded logs that are not otherwise catalogued remotely by the motor carrier. The ELD monitors the completeness of the ELD event record information in relation to the required data elements for each event type and records a missing data elements data diagnostics event for the driver if any required field is missing at the time of recording. We check to make sure that our data transfer mechanism works properly at least once every 7 days. All Data Diagnostic events are handled similarly according to the mandate. | We certify that our ELD application and related hardware have been tested to meet the FMCSA's test procedures. | |
| AKAL ELD | AKAL100 | v 5.5.0.0 And Higher | FF66EE | Download | Download | RoadReady Solutions (formerly GeoSpace Labs) | 877.4.GEOWIZ | david@geowiz.biz | https://www.geospacelabs.com | 5302 South Florida Ave #207, Lakeland, FL 33813 | AKAL ELD supports wireless Web services and email (Option 1) for its compliant data transfer mechanism. For a driver to transmit this information to an authorized safety official they will: 1. Tap the tools button in the upper right corner of the mobile ELD device. 2. Tap the send logs button in the lower right of the popup. 3. NOTE: Driver may check the 'copy me on this email' option to also receive a copy of the log transfer | 1. Check that Bluetooth is enabled on the phone and that the modem device is available for pairing 2. Inspect the physical model for its error state. There are 2 primary states 3. A rapidly blinking light indicates that the modem was unable to pair with the mobile device 4. A steady dull light means the modem was entered an error state and is not attempting to pair with any device 5. In either scenario hold the small button on the bottom left of the modem device front panel for 5 seconds to reset the device and to clear its error state ERROR CODES The primary default code is the inability of the mobile device to connect to the engine modem. This is indicated by the red bar along the top of the device. For troubleshooting instructions see above section “Setting Up The AKAL Plug In” FMCSA Error Codes Malfunction/Diagnostic Code Description P “Power compliance” malfunction E “Engine synchronization compliance” malfunction T “Timing compliance” malfunction L “Positioning compliance” malfunction R “Data recording compliance” malfunction S “Data transfer compliance” malfunction O “Other” ELD detected malfunction AKAL Equivalent Codes Code Description Shown on Mobile Device P “The plug in device is not powered on.” E “The plug in device is not able to synchronize” T “The plug in timing is not working correctly” L “System is not able to determine positioning” R “System is not able to record data” S “System is not able to transfer data” O “An unidentified error has occurred” Malfunction/Diagnostic Code Data Diagnostic Event 1 “Power data diagnostic” event 2 “Engine synchronization data diagnostic” event 3 “Missing required data elements data diagnostic” event 4 “Data transfer data diagnostic” event 5 “Unidentified driving records data diagnostic” event 6 “Other” ELD identified diagnostic event AKAL Equivalent Codes Code Process Run, Description 1 “AKAL will attempt to reset the plug in” 2 “AKAL will attempt to reset the plug in” 3 “You are missing data xxx from the ELD logs” 4 “Attempting to reconnect..” 5 “Unidentified driving records found” 6 “A general system diagnostic is in process..” | The FMCSA ELD Requirements document and usage case scenario document were followed step by step to validate each function in the requirements with our ELD device. Several updates to the software were made and the testing procedure was repeated until all scenarios passed. Software version 2.0 contains the code base tested against the FMCA requirements. | |
| Alert Gps Inc. ELD | Alert ELD | 1.0.28 and above | ALERT1 | Download | Download | Alert Gps Inc | 312-722-6661 | info@alertgpsinc.com | https://alertgpsinc.com/ | 2720 W.Chicago Ave, Chicago | To submit the Output File to an authorized safety official, the driver selects the “Export ELD Data File” from the Logbook screen. The driver, then, will select one of the following methods: - Email Transfer: An email will be preformatted with the .AES file attached to it. The destination email address will the one provided during this registration process - USB Transfer: The ELD will wait for the driver or safety official to connect the external storage device and will automatically enter Mass Storage mode. After the external storage device is detected, the driver will be prompted to re-authenticate before the transfer of the output data file is started - Bluetooth Transfer: After selecting this option, the authorized safety official will pair and verify PIN with the driver. Once the Bluetooth devices are paired, the safety official’s technology equipment will transfer the output file to the FMCSA website using Web services. | Low battery, network disconnection, low internal memory space, ECM data transfer failure, location sensor failure. | The Apollo ELD was tested on a diverse range of CMVs from different manufacturers and models as well drivers with different experience and backgrounds. Tests were also performed on different environments (indoor, outdoor, inside and outside CMVs). Procedures and areas of examinations were followed according to the “ELD Test Plan and Procedures” version 1.0 document released by FMCSA on April 25th 2016. The Requirement Traceability Matrix (RTM) was used and fully verified to ensure ELD compliance. Corrective actions and regression tests were made on all Failed test results. | |
| Alfa ELD (Android) | PT30 | 1.0.01 or higher | ALFA01 | Download | Download | Alfa ELD | +14694452757 | Alfaelog@gmail.com | https://alfaeld.com/ | 5832 Prospect Avenue , Dallas, TX 75206 | Telematic (Web Service, Email) | The DOT inspect tab has a summary of all your collected data, it will also show you the graph and the full data regarding truck readings: engine hours, odometer, etc. You may also use this tab to transfer your data to FMCSA during the DOT inspection. Click Start Inspection; Transfer Data to Safety Official Select one of the 3 options (Web Services, Email to FMCSA or Personal email) Enter comment and click Send * If you have selected the Personal email - you would need to enter the recipient's email account, select the file type (PDF or CSV) and (if pdf) - country. | We have the MD icon on the application upper left corner, which is normally painted green. Once the malfunction issue is detected, the color of “M” on the MD icon will be changed to Red. When a data diagnostic event happens, the color of “D” would be Red. Malfunctions also appear in logs as malfunction events. A driver can click on the red icon or such event in logs to see which exact error has been detected. We have a guide published for our users for further steps. The following shows the list of detectable malfunctions: Power Malfunction, Engine Synchronization Malfunction, Timing Malfunction, GPS signal Malfunction, Data Recording Malfunction, and Data Transfer Malfunction | I confirm that the testing of our Android application in conjunction with the PT30 has been performed and the application has passed all the tests and proved to be working as required. |
| Alfa ELD (iOS) | PT30 | 1.01.01 or higher | ALFA01 | Download | Download | Alfa ELD | +14694452757 | Alfaelog@gmail.com | https://alfaeld.com/ | 5832 Prospect Avenue , Dallas, TX 75206 | Telematic (Web Service, Email) | The DOT inspect tab has a summary of all your collected data, it will also show you the graph and the full data regarding truck readings: engine hours, odometer, etc. You may also use this tab to transfer your data to FMCSA during the DOT inspection. Click Start Inspection; Transfer Data to Safety Official Select one of the 3 options (Web Services, Email to FMCSA, or Personal email) Enter a comment and click Send * If you have selected the Personal email - you would need to enter the recipient's email account, select the file type (PDF or CSV), and (if pdf) - country. | We have the MD icon on the application upper left corner, which is normally painted green. Once the malfunction issue is detected, the color of “M” on the MD icon will be changed to Red. When a data diagnostic event happens, the color of “D” would be Red. Malfunctions also appear in logs as malfunction events. A driver can click on the red icon or such event in logs to see which exact error has been detected. We have a guide published for our users for further steps. The following shows the list of detectable malfunctions: Power Malfunction, Engine Synchronization Malfunction, Timing Malfunction, GPS signal Malfunction, Data Recording Malfunction, and Data Transfer Malfunction | I confirm that the testing of our iOS application in conjunction with the PT30 has been performed and the application has passed all the tests and proved to be working as required. |
| ALL THE WAY ELD | ARS | 2.3.15 or higher | ARS136 | Download | Download | All The Way Transport | 916 560-9906 | allthewayt175@gmail.com | http://www.allthewayeld.com | 5244 New Britton Cir, Antelope/CA/95843 | Local (Bluetooth) , Telematic (Web Service, Email) | ALL THE WAY ELD is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | ALL THE WAY ELD monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The ALL THE WAY ELD Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on ALL THE WAY ELD during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | ALL THE WAY ELD meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. ALL THE WAY ELD was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. |
| ALL TRUCKERS ELD | ARS | 2.0 or higher | ARS194 | Download | Download | All Truckers ELD | 445-888-1818 | admin@alltruckerseld.com | http:// | 10900 Bustleton ave apt#B23 Philadelphia PA 19116, Philadelphia PA 19116 | ALL TRUCKERS ELD is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | ALL TRUCKERS ELD monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The ALL TRUCKERS ELD Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on ALL TRUCKERS ELD during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | ALL TRUCKERS ELD meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. ALL TRUCKERS ELD was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| AllwaysTrack | AT001 | 1.0 and Above | ATN001 | Download | Download | Gorilla Fleet Safety, LLC | 844-636-1360 | info@gorillasafety.com | http://www.gorillasafety.com | 22327 Gosling Rd, Spring, TX 77379 | Telematic (Web Service, Email) | This ELD uses the web services and email method of transmission. Driver, from the "Dashboard" page of their ELD, will tap on "Roadside Inspection," then "Send Logs." Once they tap send logs, any annotation or note requested by the inspecting officer can be entered by the driver prior to sending. | The malfunctions supported are: Power Compliance Malfunction Engine Synchronization Malfunction Timing Compliance Malfunction Positioning Compliance Malfunction Data Recording Malfunction Data Transfer Malfunction Each of these malfunctions appears prominently for the user to understand the issue. When the user is presented with this, he is able to rectify the situation, contact the manufacturer or use paper logs, as provided as part of the instruction guide, to remain compliant. The malfunctions and malfunction codes can be found in the instruction guide with the required details in order for the driver to understand what he needs to do next. | The product has been thoroughly tested by both internal and external, third party, testers. Each requirement of the ELD has been either met or exceeded. The process of review and testing included the full review of the ruling, testing procedures and debugging of any blocker found in the software package. It further included the retesting by additional quality assurance professionals. Ultimately, the programing and hardware operate as intended and are in compliance. |
| AllyELD | ARS | 2.0 or higher | ARS226 | Download | Download | AllyELD | 770-359-9966 | ally@allyeld.com | http://allyeld.com | 330 Fox Meadow DR, Covington/GA/30016 | AllyEld is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | AllyEld monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The AllyEld Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on AllyEld during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | AllyEld meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. AllyEld was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| ALS-ELD | ALS-E100 | 3.6.40 or higher | ALS100 | Download | Download | Arethos | 7789294567 | mail@arethos.com | http://www.arethos.com | 5331 Chetwynd Ave, Richmond , BC, Richmond/BC/V6Y1X9 | Telematic (Web Service, Email) | ELD data transfer to FMCSA is carried out using two methods which are Telematics (Web Services and Email). Web service is our primary method of transferring data to FMCSA. The data transmitted to FMCSA will have ELD’s certificate, ELD Identifier, and Registration ID. Both request will be submitted using the Mobile App running on any mobile devices supported by Android and iOS platform. Once the request is submitting to our server than the web service and email will be triggered to transfer the required files to FMSCA. | Malfunctions events related to power, data synchronization, missing data, timing, positioning, data recording, data transfer, and unidentified driver records. The ELD output file will identify these data malfunction events and their status with predefined standard codes for compliance as mention in table 4 of Federal Register/ Vol. 80, no 241. Most recorded malfunction is “data transfer compliance”, where no signal is detected from SIM. Truck data recorded as offline in device memory and transferred later, when signal is available. | We have tested and verified all cases, which are mentioned in document Electronic Logging Device (ELD) Test Plan and Procedures with date 10/17/2016 and Version 2.0 from FMCSA web site. We have certified our ELD product/software complying with FMCSA rules and regulations. |
| ALS-ELD | ALS-E100 | 3.12.10 or higher | ALS100 | Download | Download | Arethos | 7789294567 | mail@arethos.com | http://www.arethos.com | 5331 Chetwynd Ave, Richmond , BC, Richmond/BC/V6Y1X9 | Telematic (Web Service, Email) | ELD data transfer to FMCSA is carried out using two methods which are Telematics (Web Services and Email). Web service is our primary method of transferring data to FMCSA. The data transmitted to FMCSA will have ELD’s certificate, ELD Identifier, and Registration ID. Both request will be submitted using the Mobile App running on any mobile devices supported by Android and iOS platform. Once the request is submitting to our server than the web service and email will be triggered to transfer the required files to FMSCA. | Malfunctions events related to power, data synchronization, missing data, timing, positioning, data recording, data transfer, and unidentified driver records. The ELD output file will identify these data malfunction events and their status with predefined standard codes for compliance as mention in table 4 of Federal Register/ Vol. 80, no 241. Most recorded malfunction is “data transfer compliance”, where no signal is detected from SIM. Truck data recorded as offline in device memory and transferred later, when signal is available. | We have tested and verified all cases, which are mentioned in document Electronic Logging Device (ELD) Test Plan and Procedures with date 10/17/2016 and Version 2.0 from FMCSA web site. We have certified our ELD product/software complying with FMCSA rules and regulations. |
| ALZ TRACKING ELD | ARS | 2.0 or higher | ARS197 | Download | Download | ALZ TRACKING ELD | 330 391-6879 | allianzeld@gmail.com | www.allianzeld.com | 1100 North Glebe Rd Suite 1010, Arlington, VA 22201 | ALZ TRACKING ELD is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | ALZ TRACKING ELD monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The ALZ TRACKING ELD Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on ALZ TRACKING ELD during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | ALZ TRACKING ELD meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. ALZ TRACKING ELD was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| AM LOGS ELD | ARS | 2.0 or higher | ARS106 | Download | Download | Am logs INC | 2604437153 | AMlogsINC@gmail.com | https://www.amlogsinc.com/ | 2056 Louisiana St, Gary, IN, 46407, 2056 Louisiana St, Gary, IN, 46407 | AM LOGS ELD is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select WebService as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | AM LOGS ELD monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The AM LOGS ELD Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on AM LOGS ELD during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | AM LOGS ELD meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. AM LOGS ELD was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| Amazon Relay ELD | PT-1 | 1.33.2 or higher | AMZN01 | Download | Download | Amazon | 1-888-280-4331 | relay-eld@amazon.com | http:// | 207 Boren Avenue North, Seattle, WA 98108 | Amazon Relay ELD supports transferring of driver RODS data via Web Services and Email. To transfer driver data to FMCSA 1) scroll to the bottom of the main Relay ELD screen and tap “Roadside inspection”, 2) on the Roadside Inspection screen tap ”Send logs”, 3) tap ”Web Services” or “Email” and add a comment as directed by the law enforcement officer and tap “Submit”. You will receive a success or error message within 30 seconds. Relay ELD is used to support certain Amazon services and is not available for public distribution. | Amazon Relay ELD monitors and alerts drivers to ELD malfunctions. An ELD malfunction is indicated by a visual indicator “M” in the header of ELD screens with a magenta-colored background. When a malfunction is indicated, a driver must reconstruct paper records of duty status (RODS) for the current 24-hour period and the previous 7 days and continue to use paper RODS until the ELD malfunction has cleared. A driver must notify the carrier within 24 hours of the malfunction. These malfunctions are automatically captured in the ELD database. Amazon Relay ELD monitors and alerts for the following six types of malfunction codes/descriptions. 1) P/Power compliance, 2) E/Engine synchronization compliance, 3) T/Timing compliance, 4) L/Positioning compliance, 5) R/Data recording compliance, and 6) S/Data transfer compliance. Relay ELD is used to support certain Amazon services and is not available for public distribution. | The Amazon Relay ELD product and engineering teams developed and used compliance test plans incorporating the FMCSA provided Electronic Logging Device (ELD) Test Plan and Procedures and ELD mandated requirements defined in part 395 Subpart B. We incorporated FMCSA test processes from the recommended test document, validated functional compliance through pilot testing the ELD with drivers operating over the road, and had a 3rd party evaluate the product for compliance with ELD regulations. This testing has demonstrated that the Amazon Relay ELD product is compliant with applicable regulations. We have instituted product development and technical support processes to ensure continued and on-going compliance with ELD regulations. Relay ELD is used to support certain Amazon services and is not available for public distribution. | |
| Amber ELD (Android) | PT30 | 1.0.01 | AMBER1 | Download | Download | Amber ELD | +15058195676 | safety.ambereld@gmail.com | http://ambereld.com | 5 Bisbee Ct, Santa Fe / NM / 87508 | Telematic (Web Service, Email) | To transfer your ELD records to authorized Safety Officials, you need to open the "DOT Inspect" menu (Click on the "DOT Inspect" button it the Additional Menu of the Application on your device). The DOT Inspection menu provides summaries of all the collected data about the driver, truck, and trip. You may also use this menu to transfer the data to FMCSA during the DOT inspection, certify your logs, or view unidentified records. Click on the “Start Inspection” button and check if your logs are ready to be transferred to the Safety Officials. If everything is OK, click the “Transfer Data” to Roadside Inspector button and choose the method of sending your logs: - Send it to the Personal Email (provided by the inspector); - Send it to the FMCSA Email; - Send it to Web Services (FMCSA). If you select “Personal Email”, you need to enter the recipient's address and add a comment. If you select “Web Services (FMCSA)” or “Email to FMCSA” you need to add a comment. The reporting period will vary depending on the rules of the country in which you operate. | If there are any malfunctions or data diagnostic issues detected, the M/D icon at the top of the app screen will change its color from green to red. In case of a malfunction, the red "M" letter will indicate a Malfunction, and if there is a Data Diagnostic, the red "D" letter will indicate data error. Malfunctions and Data Diagnostic can also be displayed in the Logs menu as Malfunction event or Data Diagnostic event. As of the Malfunctions you can notice such types of issues: -Engine Synchronization -Positioning compliance -Data recording compliance -Unregistered odometer change -Timing compliance -Power compliance As of the Data Diagnostics problem you can notice such types of issue: -Engine synchronization -Missing data elements -Unidentified driving records -Data transfer -Power data diagnostic To learn more about the problem you are facing, tap the M/D icon at the top of the app screen and check the details. | We can confirm that the application operates in accordance with the FMCSA guidelines as a consequence of the extensive testing that has been conducted by the team of QA engineers of the Android application. |
| Amber ELD (iOS) | PT30 | 1.01.01 | AMBER1 | Download | Download | Amber ELD | +15058195676 | safety.ambereld@gmail.com | http://ambereld.com | 5 Bisbee Ct, Santa Fe / NM / 87508 | Telematic (Web Service, Email) | To transfer your ELD records to authorized Safety Officials, you need to open the "DOT Inspect" menu (Click on the "DOT Inspect" Button on your device). Click on the “Start Inspection” button and check if your logs are ready to be transferred to the Safety Officials. If everything is OK, click the “Transfer Data” to Roadside Inspector button and choose the method of sending your logs: - Send it to the Personal Email (provided by the inspector); - Send it to the FMCSA Email; - Send it to Web Services (FMCSA). If you select “Personal Email”, you need to enter the recipient's address and add a comment. If you select “Web Services (FMCSA)” or “Email to FMCSA” you need to add a comment. The reporting period will vary depending on the rules of the country in which you operate. | If there are any malfunctions or data diagnostic issues detected, the M/D icon at the top of the app screen will change its color from green to red. In case of a malfunction, the red "M" letter will indicate a Malfunction, and if there is a Data Diagnostic, the red "D" letter will indicate data error. Malfunctions and Data Diagnostic can also be displayed in the Logs menu as Malfunction event or Data Diagnostic event. As of the Malfunctions you can notice such types of issues: -Engine Synchronization -Positioning compliance -Data recording compliance -Unregistered odometer change -Timing compliance -Power compliance As of the Data Diagnostics problem you can notice such types of issue: -Engine synchronization -Missing data elements -Unidentified driving records -Data transfer -Power data diagnostic To learn more about the problem you are facing, tap the M/D icon at the top of the app screen and check the details. | We can confirm that the application operates in accordance with the FMCSA guidelines as a consequence of the extensive testing that has been conducted by the team of QA engineers of the iOS application. |
| AMERICAN SOIL ELD | ARS | 2.0 or higher | ARS191 | Download | Download | AMERICAN SOIL ELD | 9735124265 | americaneld1@gmail.com | www.amercianeld.com | 1012 Lighthouse Ct, Cedar Hill/TX/75104 | AMERICAN SOIL ELD is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | AMERICAN SOIL ELD monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The AMERICAN SOIL ELD Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on AMERICAN SOIL ELD during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | AMERICAN SOIL ELD meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. AMERICAN SOIL ELD was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| ANYTIME DRIVE | ARS | 2.0 or higher | ARS157 | Download | Download | Viktor Bright | 7739643462 | anytimedrive2020@gmail.com | http://anytimedrive.net | 14544 Club Circle Dr, Oak Forest/IL/60452 | ANYTIME DRIVE is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | ANYTIME DRIVE monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The ANYTIME DRIVE Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on ANYTIME DRIVE during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | ANYTIME DRIVE meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. ANYTIME DRIVE was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| Apollo ELD (at.eDash) | Apollo | 215-Android 198-iOS | APOLLO | Download | Download | Apollo ELD | 305-971-6777 | eldinfo@apolloeld.com | http://www.apolloeld.com | 8230 Coral Way, Miami FL 33155 | Local (USB, Bluetooth) , Telematic (Web Service, Email) | To submit the Output File to an authorized safety official, the driver selects the “Export ELD Data File” from the Logbook screen. The driver, then, will select one of the following methods: - Email Transfer: An email will be preformatted with the .AES file attached to it. The destination email address will the one provided during this registration process - USB Transfer: The ELD will wait for the driver or safety official to connect the external storage device and will automatically enter Mass Storage mode. After the external storage device is detected, the driver will be prompted to re-authenticate before the transfer of the output data file is started - Bluetooth Transfer: After selecting this option, the authorized safety official will pair and verify PIN with the driver. Once the Bluetooth devices are paired, the safety official’s technology equipment will transfer the output file to the FMCSA website using Web services. | Low battery, network disconnection, low internal memory space, ECM data transfer failure, location sensor failure. | The Apollo ELD was tested on a diverse range of CMVs from different manufacturers and models as well drivers with different experience and backgrounds. Tests were also performed on different environments (indoor, outdoor, inside and outside CMVs). Procedures and areas of examinations were followed according to the “ELD Test Plan and Procedures” version 1.0 document released by FMCSA on April 25th 2016. The Requirement Traceability Matrix (RTM) was used and fully verified to ensure ELD compliance. Corrective actions and regression tests were made on all Failed test results. |
| ARROW ELD | ARS | 2.0 or higher | ARS184 | Download | Download | ARROW ELD | 7089860003 | info@arrowhos.com | http:// | 904 S ROSELLE RD UNIT 172, SCHAUMBURG IL 60193 | ARROW ELD is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | ARROW ELD monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The ARROW ELD Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on ARROW ELD during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | ARROW ELD meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. ARROW ELD was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| Ashavi Global | ASHT01 | 1.0 | ASHAV1 | Download | Download | Ashavi Global | 18006761244 | cs@ashaviglobal.com | http://www.ashaviglobal.com | 139 Devon Road Unit 3, Brampton/ Ontario/ L6T 5L8 | 1. Transfer via email to FMCSA’s ELD email address. NOTE: Email transfers will only be used to transfer ELD data via FMCSA’s ELD email address, not directly to a roadside inspector. 2. Using the S/MIME standard, the email will be encrypted using at a minimum the AES-256 algorithm and FMCSA ELD public key. The message will be signed using the manufacturer’s private key. 3. Once transmitted to FMCSA: o Email will be decrypted. o Signature will be validated using the manufacturer’s public key. o ELD file will be validated. 4. A reply is sent to “From” address indicating success or providing a list of errors. Step-by-step instructions for a driver 1. Driver need to click on request log on Home Screen 2. Driver will entre Fax number or Email address provided by roadside inspector. 3. Once driver click on send logs, the logs will be sent to fax or email provided within 5 minutes. Transferring data via Bluetooth The driver’s/motor carrier’s ELD will have to use the safety official’s internet connection to transfer data. The internet connection between the ELD and the safety official will be limited and can only be used for the purpose of transferring the ELD data via the web service. During Bluetooth data transfer, the driver/motor carrier will make the ELD discoverable. Once the ELD detects the safety official’s laptop, the safety official will provide the driver/motor carrier with a Bluetooth code to enter into the ELD and confirm Bluetooth connectivity between the safety official’s laptop and the ELD. Once the connection between the safety official’s laptop and the ELD has been confirmed, the safety official will provide the driver/motor carrier with the safety official’s unique code, and the driver/motor carrier will transfer the ELD data to web services for the safety official to retrieve. Transferring data via web service The authorized safety official will give the driver a routing code to assist the official in locating the data once transmitted, and the driver will initiate a web transfer to an FMCSA server to be retrieved by the safety official’s software. Transferring data via usb 2.0 An authorized safety official will have to provide a secure USB device to allow the driver to electronically transfer data from the ELD to the official. The driver will return the USB device to the safety official, who will transfer the data to a computing device. | • Power compliance malfunction: In this instance an ELD is not powered for “an aggregated in-motion driving time of 30 minutes or more” during a 24-hour period across all drivers. • Engine synchronization compliance malfunction: This failure occurs when ECM connectivity to any required data source such as engine power status, miles driven, engine hour, etc., is lost for more than 30 minutes during a 24-hour period aggregated across all drivers. • Time compliance malfunction: An ELD that is unable to meet the “underlying compliance requirement to record Coordinated Universal Time (UTC), where ELD time must be synchronized with UTC, not to exceed an absolute deviation of 10 minutes at any time.” • Positioning compliance malfunction: This occurs when the ELD is unable to obtain a valid position measurement within five miles of the truck moving and during a 60 minute period. • Data recording compliance malfunction: This happens when the ELD can’t record or retain events or can’t retrieve recorded logs that aren’t kept remotely. • Data transfer compliance malfunction: This failure occurs if the operation of the data transfer mechanism is in the unconfirmed data transfer mode during three consecutive monitoring checks If the driver notices a malfunction, he or she must provide written notice of the malfunction to the carrier within 24 hours. They also must reconstruct the record of duty status (RODS) for the current 24-hour period and the previous 7 consecutive days, and record the data on graph-grid paper logs. The driver must continue to prepare RODS until the ELD is back in compliance. | This is to certify that the design of the Ashavi Global Hours of Service driver logs application has been sufficiently tested to meet the requirement stated in section 49 CFR 395.15 of the Federal Motor Carrier Safety Regulations as prescribed by the United States Department of Transportation Federal Motor Carrier Safety Act. The sevice may be used to record, transmit, and store all hours of service information required by the Department of Transportation insection 49 CFR 395.15. | |
| ASMebook | AGE001 | 1.12 | ASMGPS | Download | Download | Auto Security & Monitoring Inc | 626-454-3278 | info@asmgps.com | www.asmgps.com | 9322 Klingerman Street,Suite A, South El Monte, CA 91733 | ASM ELD can transfer ELD record data by Email. When an ELD user is ready to require a record, an identical user name and password are needed to log-in by APP, after authorized by ASM control server, ELD user can email driving log record day by day with driver’s info, vehicle ID and motor carrier info etc. in RFC 5322 internet message format. We retain 3-year vehicle ELD record data on ASM data center server, driver need download iPhone ASMBook APP, login with username and password, select transfer data date, click email button in the APP, input Receiver email address and ELD registration ID +”:”+ASMGPS in Subject field, and input some comment in Email, ELD record data file will be attached automatically. ASM ELD can transfer data via ASM Soap encoded Web Service in WSDL1.1 file too. ASM ELD web service reference address is: http://www.asmgps.com/eldwebservice, there is a method LOGRECORDLIST that will transfer compliant CSV format file data after authorization. | Power Compliance Malfunction Engine Status Compliance Malfunction Positioning Compliance Malfunction Timing Compliance Malfunction Data Recording Compliance Malfunction Data Transfer Compliance Malfunction | Auto Security & Monitoring Inc. certifies based on ELD Compliance Test Procedure: For on-vehicle device, we assign more than 10 users, after 30-day, we compare driving route synthesized from data base with drivers’ records, including location, date time, vehicle speed,engine status etc. info to ensure all geographic data, timing are correct. For monitoring software, it must display necessary info and chart, test all features including read, save, restore, test user will finish both handwriting and electrical log records, after 30 days, we compare paper log records and electrical chart, and ensure all display info are correct.. | |
| AssetWorks ELD | MDT7 | v2.2 or higher | ELD001 | Download | Download | AssetWorks | 403.705.3880 | eld.support@assetworks.com | https://www.assetworks.com/fss/ | 10, 2175 - 29th St NE, Calgary, Alberta | Driver or Official will use the Options button on the driver overview screen Driver or Official will use the Roadside Inspection button on the drop down This button will navigate the user to a Logs Grid page The Logs Grid page will contain a button labeled "Data File Transfer” The Officer will tap on the button and be instructed to choose email or wireless webservices and enter the instructions or code to send the data file to the FMCSA | Power P Device lost power during driving events for a total of 30 min or more over a 24-hour period Engine synchronization E Device lost connection to the ECM (or other data source) for a total of more than 30 min during a 24-hour period Timing T Device is not able to synchronize to UTC Positioning L Device is not able to acquire a valid position measurement within 5 mi of vehicle movement for a total of more than 60 min over a 24 hour period. Data recording R Device is no longer able to record or retain required event data or retrieve locally-stored recorded logs Data transfer S Device continues to fail checks of the roadside transfer mechanism for three days following a Data Transfer Diagnostic Event Other ELD detected O The eFleetSuite application has stopped working or is not responding as expected | AssetWorks ELD certifies based on our completion of the testing procedures provided by the FMCSA in the Electronic Logging Device Test Plan and Procedures document version 2.0 dated 10/17/2016 that ME4230 and MDT7 complies with all Federal Motor Carrier Safety Administration (FMCSA) specifications as found in 49 CFR Part 395 for Electronic Logging Devices, Subpart B.Devices, Subpart B. | |
| AssetWorks Ranger ELD | Ranger4 | 3.24 or higher | ELD002 | Download | Download | AssetWorks | 403.705.3880 | eld.support@assetworks.com | https://www.assetworks.com/fss/ | 10, 2175 - 29th St NE, Calgary, Alberta | Driver or Official will use the Driver Options button on the Other screen Driver or Official will use the Roadside Inspection button on the the next screen This button will navigate the user to a Logs Grid page The Logs Grid page will contain a button labeled "Data File Transfer” The Officer will tap on the button and be instructed to choose email or wireless webservices and enter the instructions or code to send the data file to the FMCSA | Power P Device lost power during driving events for a total of 30 min or more over a 24-hour period Engine synchronization E Device lost connection to the ECM (or other data source) for a total of more than 30 min during a 24-hour period Timing T Device is not able to synchronize to UTC Positioning L Device is not able to acquire a valid position measurement within 5 mi of vehicle movement for a total of more than 60 min over a 24 hour period. Data recording R Device is no longer able to record or retain required event data or retrieve locally-stored recorded logs Data transfer S Device continues to fail checks of the roadside transfer mechanism for three days following a Data Transfer Diagnostic Event Other ELD detected O The ELD application has stopped working or is not responding as expected | AssetWorks Ranger ELD certifies based on our completion of the testing procedures provided by the FMCSA in the Electronic Logging Device Test Plan and Procedures document version 2.0 dated 10/17/2016 that Ranger complies with all Federal Motor Carrier Safety Administration (FMCSA) specifications as found in 49 CFR Part 395 for Electronic Logging Devices, Subpart B.Devices, Subpart B. | |
| ASSIATRAK ELD | ARS | 2.0 or higher | ARS143 | Download | Download | Assia Trak HOS | 1-833-353-7767 | Info@assiatrakhos.com | http://assiatrakhos.com | PO Box 2156, Sun City, CA 92336 | ASSIATRAK ELD is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | ASSIATRAK ELD monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The ASSIATRAK ELD Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on ASSIATRAK ELD during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | ASSIATRAK ELD meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. ASSIATRAK ELD was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| Astus ELD | Astus & iOS | 1.0.2106.210505.1 | AELD01 | Download | Download | Astus/ETL Electronique | 1-866-702-7887 | support@astus.com | https://astus.com | 2396 de la province, Longueuil, Qc, J4G1G1 | Astus ELD provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. This can be done by selecting the Roadside Inspection button from the main HOS dashboard and selecting the option for Data Transfer. A list of supported data transfer options is then displayed which include Bluetooth, Email, and web service. A Select Vehicle option is also available for selecting a vehicle upon performing the data transfer, this option enables Astus ELD to produce a data file or a series of data files of ELD records for a subset of its vehicles used by the driver. • Transfer via Bluetooth - this option enables the user to transfer files through Bluetooth. The ELD prompts for an output file comment which the driver may enter (optional). After the input, if Bluetooth is not yet turned on, a prompt will appear asking you to turn it on. You will then be asked to select the device name to which the data will be transmitted via Bluetooth. • Transfer via Email - this option enables the user to transfer files through email. The ELD output file is encrypted using AES-256 in FIPS Publication 197. Before sending, the ELD prompts for an output file comment which the driver may enter (optional). The email is then automatically sent to the FMCSA email address specified in the ELD Provider Registration website: fmcsaeldsub@dot.gov • Transfer via Web Service - this option enables the user to transfer files to FMCSA via Web Services. The Web Service data transfer follows the following standards: WSDL, SOAP, XML. | Astus ELD is capable of monitoring its compliance for various detectable malfunctions. At each instance when an ELD malfunction event is detected or cleared by Astus ELD, the ELD records the event. The recorded malfunction events are inconsistencies found while monitoring the ELD against FMCSA compliance requirements. Malfunction occurrences are indicated in the application header and in the Android & iOS notification toolbar with the letter ‘M’, respectively. The following shows the list of detectable malfunctions: • Power Malfunction • Engine Synchronization Malfunction • Timing Malfunction • Position Malfunction • Data Recording Malfunction • Data Transfer Malfunction Once the Malfunctions indicator ‘M’ is tapped, a dialog will be displayed with a list of the detected malfunction events alongside a ‘Clear’ button for each event. Tapping the Clear button will clear out the detected malfunction event. | Astus ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. Astus ELD was installed on various types and sizes of Android & iOS phones and tablets. Testing was performed through the use of a J1939 simulator and actual vehicles while having been connected to the Astus TAG engine connected device. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the Hours of Service web application (portal) that can be accessed through a web browser. | |
| Astus ELD | Astus & Android | 1.0.2106.210505.1 | AELD01 | Download | Download | Astus/ETL Electronique | 1-866-702-7887 | support@astus.com | https://astus.com | 2396 de la province, Longueuil, Qc, J4G1G1 | Astus ELD provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. This can be done by selecting the Roadside Inspection button from the main HOS dashboard and selecting the option for Data Transfer. A list of supported data transfer options is then displayed which include Bluetooth, Email, USB, and web service. A Select Vehicle option is also available for selecting a vehicle upon performing the data transfer, this option enables Astus ELD to produce a data file or a series of data files of ELD records for a subset of its vehicles used by the driver. • Transfer via Bluetooth - this option enables the user to transfer files through Bluetooth. The ELD prompts for an output file comment which the driver may enter (optional). After the input, if Bluetooth is not yet turned on, a prompt will appear asking you to turn it on. You will then be asked to select the device name to which the data will be transmitted via Bluetooth. • Transfer via Email - this option enables the user to transfer files through email. The ELD output file is encrypted using AES-256 in FIPS Publication 197. Before sending, the ELD prompts for an output file comment which the driver may enter (optional). The email is then automatically sent to the FMCSA email address specified in the ELD Provider Registration website: fmcsaeldsub@dot.gov • Transfer via USB - this option enables the user to transfer files through USB (external devices). However, prior to saving the driver’s ELD file to an external storage/device, the ELD re-authenticates the driver account by asking for its password. • Transfer via Web Service - this option enables the user to transfer files to FMCSA via Web Services. The Web Service data transfer follows the following standards: WSDL, SOAP, XML. | Astus ELD is capable of monitoring its compliance for various detectable malfunctions. At each instance when an ELD malfunction event is detected or cleared by Astus ELD, the ELD records the event. The recorded malfunction events are inconsistencies found while monitoring the ELD against FMCSA compliance requirements. Malfunction occurrences are indicated in the application header and in the Android & iOS notification toolbar with the letter ‘M’, respectively. The following shows the list of detectable malfunctions: • Power Malfunction • Engine Synchronization Malfunction • Timing Malfunction • Position Malfunction • Data Recording Malfunction • Data Transfer Malfunction Once the Malfunctions indicator ‘M’ is tapped, a dialog will be displayed with a list of the detected malfunction events alongside a ‘Clear’ button for each event. Tapping the Clear button will clear out the detected malfunction event. | Astus ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. Astus ELD was installed on various types and sizes of Android & iOS phones and tablets. Testing was performed through the use of a J1939 simulator and actual vehicles while having been connected to the Astus TAG engine connected device. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the Hours of Service web application (portal) that can be accessed through a web browser. | |
| Astus ELD | iOS & Astus | 1.0.2106.210505.1 | AELD01 | Download | Download | Astus/ETL Electronique | 1-866-702-7887 | support@astus.com | https://astus.com | 2396 de la province, Longueuil, Qc, J4G1G1 | Astus ELD provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. This can be done by selecting the Roadside Inspection button from the main HOS dashboard and selecting the option for Data Transfer. A list of supported data transfer options is then displayed which include Bluetooth, Email, and web service. A Select Vehicle option is also available for selecting a vehicle upon performing the data transfer, this option enables Astus ELD to produce a data file or a series of data files of ELD records for a subset of its vehicles used by the driver. • Transfer via Bluetooth - this option enables the user to transfer files through Bluetooth. The ELD prompts for an output file comment which the driver may enter (optional). After the input, if Bluetooth is not yet turned on, a prompt will appear asking you to turn it on. You will then be asked to select the device name to which the data will be transmitted via Bluetooth. • Transfer via Email - this option enables the user to transfer files through email. The ELD output file is encrypted using AES-256 in FIPS Publication 197. Before sending, the ELD prompts for an output file comment which the driver may enter (optional). The email is then automatically sent to the FMCSA email address specified in the ELD Provider Registration website: fmcsaeldsub@dot.gov • Transfer via Web Service - this option enables the user to transfer files to FMCSA via Web Services. The Web Service data transfer follows the following standards: WSDL, SOAP, XML. | Astus ELD is capable of monitoring its compliance for various detectable malfunctions. At each instance when an ELD malfunction event is detected or cleared by Astus ELD, the ELD records the event. The recorded malfunction events are inconsistencies found while monitoring the ELD against FMCSA compliance requirements. Malfunction occurrences are indicated in the application header and in the Android & iOS notification toolbar with the letter ‘M’, respectively. The following shows the list of detectable malfunctions: • Power Malfunction • Engine Synchronization Malfunction • Timing Malfunction • Position Malfunction • Data Recording Malfunction • Data Transfer Malfunction Once the Malfunctions indicator ‘M’ is tapped, a dialog will be displayed with a list of the detected malfunction events alongside a ‘Clear’ button for each event. Tapping the Clear button will clear out the detected malfunction event. | Astus ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. Astus ELD was installed on various types and sizes of Android & iOS phones and tablets. Testing was performed through the use of a J1939 simulator and actual vehicles while having been connected to the Astus TAG engine connected device. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the Hours of Service web application (portal) that can be accessed through a web browser. | |
| AT&T Fleet Complete ELD | MGS700 (GNX6) / MGS800 | 33.1 or higher | FCBR20 | Download | Download | BigRoad Inc | 1-888-305-8777 | support@bigroad.com | www.bigroad.com | 180 Columbia St. W., Waterloo, Ontario, N2L 3L3 | Telematic (Web Service, Email) | Data transfer is supported via telematics types, specifically web services and email. Step by step instructions: 1) Tap Inspect Logs 2) Select 7 days (US) 3) Tap Send to FMCSA 4) Select either "Via web services" or "Via email" 5) Tap Send 6) Fill in the provided output file comment 7) Tap Send | Supported Malfunctions include: Engine Synchronization Malfunction - indicated when the ELD is unable to sense required engine and vehicle information such as odometer, hours, VIN, road speed, engine on/off Timing Compliance Malfunction - indicated when the ELDs clock diverges by more than 10 minutes from the external, reliable source (GPS Time) Positioning Compliance Malfunction - indicated when the ELD is continually unable to determine an accurate location and >5 miles of driving have elapsed Data Recording Malfunction - indicated when the ELD is unable to store data Power Compliance Malfunction - indicated when the ELD is unable to power on with sufficient time during vehicle use Data Transfer Malfunction - indicated when the ELD has been unable to transfer required information to FMCSA servers for an extended period of time | The AT&T Fleet Complete ELD has been tested in accordance with BigRoad testing procedures to be compliant with FMSCA regulation 49 CFR part 395, subpart B, appendix A; describing the functional requirements for ELD solutions. |
| AT&T Fleet Complete ELD | FT1 / FT2 / FT3 | 33.1 or higher | FCBR20 | Download | Download | BigRoad Inc | 1-888-305-8777 | support@bigroad.com | www.bigroad.com | 180 Columbia St. W., Waterloo, Ontario, N2L 3L3 | Telematic (Web Service, Email) | Data transfer is supported via telematics types, specifically web services and email. Step by step instructions: 1) Tap Inspect Logs 2) Select 7 days (US) 3) Tap Send to FMCSA 4) Select either "Via web services" or "Via email" 5) Tap Send 6) Fill in the provided output file comment 7) Tap Send | Supported Malfunctions include: Engine Synchronization Malfunction - indicated when the ELD is unable to sense required engine and vehicle information such as odometer, hours, VIN, road speed, engine on/off Timing Compliance Malfunction - indicated when the ELDs clock diverges by more than 10 minutes from the external, reliable source (GPS Time) Positioning Compliance Malfunction - indicated when the ELD is continually unable to determine an accurate location and >5 miles of driving have elapsed Data Recording Malfunction - indicated when the ELD is unable to store data Power Compliance Malfunction - indicated when the ELD is unable to power on with sufficient time during vehicle use Data Transfer Malfunction - indicated when the ELD has been unable to transfer required information to FMCSA servers for an extended period of time | The AT&T Fleet Complete ELD has been tested in accordance with BigRoad testing procedures to be compliant with FMSCA regulation 49 CFR part 395, subpart B, appendix A; describing the functional requirements for ELD solutions. |
| AUTOGRI ELD | ATGRI | 2.15 and above | AGR529 | Download | Download | AutogriELD | +1 (331) 345-49-99 | autogrield@gmail.com | http://autogri.online | 2840 Gypsum Cir, Naperville IL 60564, Naperville/IL/60564 | Telematic (Web Service, Email) | AUTOGRI ELD, or Electronic Logging Device, is a tool that offers a comprehensive overview of a driver's records during a roadside inspection. Not only does it provide this information within the app, but it also facilitates the transfer of telematics data through email or web services. The DOT Inspection mode allows the driver to choose the method that works best for them. To transfer ELD records through Web services, the driver needs to access the "DOT Inspection" menu and select the "Send Logs" option. Then, they should choose Web Service as the Data Transfer Type and click the "SEND" button. Similarly, to transfer ELD records via Email, the driver should follow the same steps but select Email as the Data Transfer Type before clicking the "SEND" button. | The AUTOGRI ELD system ensures compliance with technical requirements, identifies malfunctions and data inconsistencies, and maintains records of such occurrences. Compliance malfunctions and diagnostic events are classified with specific codes, including P for "Power compliance" malfunction, E for "Engine synchronization compliance" malfunction, T for "Timing compliance" malfunction, L for "Positioning compliance" malfunction, R for "Data recording compliance" malfunction, S for "Data transfer compliance" malfunction, O for "Other" ELD-detected malfunctions, 1 for "Power data diagnostic" event, 2 for "Engine synchronization data diagnostic" event, 3 for "Missing required data elements data diagnostic" event, 4 for "Data transfer data diagnostic" event, 5 for "Unidentified driving records data diagnostic" event, and 6 for "Other" ELD-identified diagnostic events. The AUTOGRI ELD Malfunction and Diagnostic Event Records document all malfunctions that occurred during the relevant time period. Active malfunctions are communicated to all drivers who may use the ELD. | AUTOGRI ELD has been thoroughly tested to ensure compliance with all the functional requirements outlined in Title 49, Part 395 of Section 4.9.1, Appendix A, Subpart B. AUTOGRI ELD can confidently certify that our ELD product adheres to all the necessary ELD regulations. |
| Automile | AUTOMILE BOX 2 | 2.6.7 or higher | AUTELD | Download | Download | AUTOMILE | 415-749-9270 | marketing@automile.com | https://automile.com/ | 291 Alma Street, 291, Alma Street, Palo Alto, CA - 94301 | Data transfer is supported by means of a document exported in pdf format, and then e-mailed to any required email addresses. Here are the step by step instruction for email data transfer that needs to be followed from the Automile App: STEP 1: Tap on 'HOS' from left navigation menu in the app and tap on top right 3-dot icon STEP 2: Select the day to show log STEP 3: Tap on 'Export HOS log' or 'Show logs to Officer' STEP 4: Enter appropriate email address to send the log data or show the HOS log from the app itself STEP 5: You can either show an individual day HOS log or historic log HOS logs can also be accessed in json format through a RESTful API from our Web Services. Here are step-by-step instruction for wireless web services capabilities: STEP 1: Driver enters the routing code provided by safety official into the app STEP 2: Driver initiates a web transfer via the app STEP 3: Automile will upload the data to an FMCSA server to be retrieved by the safety official | Guidelines set forth in §395.22 – Motor carrier responsibilities – In general. (h) A motor carrier must ensure that its drivers possess onboard a commercial motor vehicle on ELD information packet containing the following items: (3) An instruction sheet for the driver describing ELD malfunction reporting requirements and recordkeeping procedures during ELD malfunctions How does the driver know if the ELD is malfunctioning? The lights are turned on when the device is plugged showing that it is powered. • The ELD device malfunctions if the device is unplugged or incorrectly plugged-in to the vehicle OBD-II port. • In the event of the device being unplugged from the vehicle OBD-II port, a ‘device-disconnect’ notification or alert will be sent to the motor carrier via the Automile app. What does the driver need to do if the ELD is malfunctioning? • Keep a paper log for that day until ELD is repaired or replaced. In the event of an inspection, display the logs of previous 15 days from the Automile app. • Note the malfunction and provide written notice to your motor carrier within 24 hours. What does the fleet need to do if the ELD is malfunctioning? • The motor carrier will be notified of the malfunction via the Automile app. Immediately contact Automile support at +1-(415)-749-9270 or support@automile.com to troubleshoot the issue. • The motor carrier must take actions to correct the malfunctions within 8 days of discovery of the condition (whether it was reported by the driver or identified on their own) • Automile will send a new device in the event of a malfunction where the device is the issue and cannot be corrected immediately • If a motor carrier needs a time extension, they must notify the FMCSA Division Administrator for the state of motor carrier’s principal place of business within5 days after a driver notifies the motor carrier according to the guidelines set forth in §395.34(2) Malfunction Summary Table below (The PDF of malfunction summary that includes table has also been sent via email) Power compliance Cause - When the ELD has more than 30 minutes of driving time lost in a 24-hour period. Resolution - Use paper logs and please contact your motor carrier immediately Engine Synchronization Cause - When the ELD has more than 30 minutes of engine sync time lost in a 24-hour period. Resolution - Use paper logs and please contact your motor carrier immediately Timing compliance Cause - When there is time deviation and not synchronized with the server. Resolution - This should be auto-resolved however if not, please contact your motor carrier immediately Positioning compliance Cause - Occurs when the vehicle is in any area without GPS / the GPS is disconnected or not properly fitted to the ELD. Resolution - This should be auto-resolved however if not, please contact your motor carrier immediately | Automile, Inc. certifies that our model AUTOMILE BOX 2, used in conjunction with the Automile iOS or Android app on a smartphone conforms to the ELD specifications. | |
| AVLTRACK ELD | ELD-A100 | 1.1.0 and above | AVLT01 | Download | Download | Gestion Econoplus Inc | 514-953-4864 | Jean.b@avltrack.com | www.avltrack.com | 1384 Avenue de la Gare , Mascouche J7K 2Z2 | Our supported transfer methods are the telematic type: wireless Web services and email. The user must press the DOT Inspection icon, chose the transfer method and press the send button. If requested by the inspector, a comment could be entered before pressing the send button. | AVLTRACK ELD system supports and monitors following malfunction events: a) P - “Power compliance” malfunction b) E - “Engine synchronization compliance” malfunction c) T - “Timing compliance” malfunction d) L - “Positioning compliance” malfunction e) R - “Data recording compliance” malfunction f) S - “Data transfer compliance” malfunction g) O - “Other” ELD detected malfunction | We certify that our ELD solution meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. We certify that our eld solution has been sufficiently tested to comply with FMCSA regulations by completing steps and testing procedures described in Electronic Logging Device (ELD) Test Plan and Procedures (Version 2.1). | |
| AWA247 ELD | ARS | 2.4.9 and higher. | ARS110 | Download | Download | AWA247 | 7085163020 | eldawa247@gmail.com | http://awa247.com | 6600 S. Melvina Ave, Chicago IL 60638 | Telematic (Web Service) | AWA247 ELD is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | AWA247 ELD monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The AWA247 ELD Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on AWA247 ELD during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | AWA247 ELD meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. AWA247 ELD was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. |
| AwareGPS- ELD | AGAW01 | 1.4.72 or higher | AGAW01 | Download | Download | AwareGPS | 855-894-8729 | sales@awaregps.com | http://www.awaregps.com/ | 16305 Swingley Ridge Rd. Suite 100, Chesterfield/ MO/ 63017 | We have chosen to use wireless web services and email as our choice for the ELD output file. - Driver or Official will tap on "Logs" from the Driver Overview screen. - Tap on Events/Grid button to toggle between the grid view and a line-by line detail view. -Driver or Official will use the Options button on the driver overview screen -Driver or Official will use the Roadside Inspection button on the drop down -This button will navigate the user to a Logs Grid page -The Logs Grid Page will contain a button labeled “Transmit ELD Data File” -This button will be disabled until the FMCSA has released the URL to send the data file | The AwareGPS ELD system continuously monitors for all appropriate malfunctions as specified in Appendix A section 4.6. It supports detection of all malfunctions and diagnostic events specified by the ELD mandate, including: power, engine synchronization, timing, positioning, data recording, data transfer, required data elements, and unidentified driving. When a malfunction is detected, it is reported as required in ELD data file(s) and visually indicated on the ELD system as required by 4.6.2.1. | AwareGPS (Agilis Systems) certifies that AwareGPS-ELD based on our completion of the testing procedures provided by the FMCSA in the Electronic Logging Device Test Plan and Procedures document version 2.0 dated 10/17/2016 that AGAW01 and complies with all Federal Motor Carrier Safety Administration (FMCSA) specifications as found in 49 CFR Part 395 for Electronic Logging Devices, Subpart B. Devices, SubpartB. | |
| Axis TMS Logbook | AX ONE | 1.0.1905.190614 | AXIS01 | Download | Download | Axis TMS Corp | 8553396599 | hello@axistms.com | https://www.axistms.com | 780 W. Maple Rd Ste A, Troy, MI 48084 | The Axis TMS Logbook provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. This can be done by selecting the Roadside Inspection button from the main HOS dashboard and selecting the option for Data Transfer. A list of supported data transfer options is then displayed which include Bluetooth, Email, USB, and web service. A Select Vehicle option is also available for selecting a vehicle upon performing the data transfer, this option enables the Axis TMS Logbook to produce a data file or a series of data files of ELD records for a subset of its vehicles used by the driver. • Transfer via Bluetooth - this option enables the user to transfer files through Bluetooth. The ELD prompts for an output file comment which the driver may enter (optional). After the input, if Bluetooth is not yet turned on, a prompt will appear asking you to turn it on. You will then be asked to select the device name to which the data will be transmitted via Bluetooth. • Transfer via Email - this option enables the user to transfer files through email. The ELD output file is encrypted using AES-256 in FIPS Publication 197. Before sending, the ELD prompts for an output file comment which the driver may enter (optional). The email is then automatically sent to the FMCSA email address specified in the ELD Provider Registration website: fmcsaeldsub@dot.gov • Transfer via USB - this option enables the user to transfer files through USB (external devices). However, prior to saving the driver’s ELD file to an external storage/device, the ELD re-authenticates the driver account by asking for its password. • Transfer via Web Service - this option enables the user to transfer files to FMCSA via Web Services. The Web Service data transfer follows the following standards: WSDL, SOAP, XML. | The Axis TMS Logbook ELD is capable of monitoring its compliance for various detectable malfunctions. At each instance when an ELD malfunction event is detected or cleared by the Axis TMS Logbook ELD, the ELD records the event. The recorded malfunction events are inconsistencies found while monitoring the ELD against FMCSA compliance requirements. Malfunction occurrences are indicated in the application header and in the Android/iOS notification toolbar with the letter ‘M’, respectively. The following shows the list of detectable malfunctions: - Power Malfunction - Engine Synchronization Malfunction - Timing Malfunction - Position Malfunction - Data Recording Malfunction - Data Transfer Malfunction Once the Malfunctions indicator ‘M’ is tapped, a dialog will be displayed with a list of the detected malfunction events alongside a ‘Clear’ button for each event. Tapping the Clear button will clear out the detected malfunction event. | The Axis TMS Logbook was certified by the Axis TMS Corp testing team through successful execution and verification of the FMCSA ELD Test Procedures. The Axis TMS Logbook was installed on various types and sizes of Android & iOS phones and tablets. Testing was performed through the use of a J1939 simulator and actual vehicles while having been connected to the AX ONE engine connected device. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the HOS web application (portal) that can be accessed through a web browser. | |
| AZ ELD | ARS | 2.5.4 or higher | ARS105 | Download | Download | AZELDS Inc. | 3067373990 | info@azelds.com | http://azelds.com | 4110 Alton Cres, REGINA/Saskachewan/ S4w0h6 | Telematic (Web Service, Email) | According to 49 CFR 395.4.9.1, drivers using the AZ ELD system can transfer log data through telematics. If an officer needs to review a driver's logs, the driver can produce a report on their mobile device or transfer log data through web services or email. | The AZ ELD system has the capability to self-detect any malfunctions as per the guidelines given in Appendix A, section 4.6. Drivers using the system will be alerted with a visual signal in case of any malfunction or diagnostic event that includes data recording, data transfer, missing data elements, power failure, engine synchronization, timing, positioning and unidentified driving. | The AZ ELD has been put through a thorough testing process as per the standards set by the FMCSA. The AZ ELD confirms that the combination of hardware and mobile application conforms to the standards of a compliant electronic logging system and all the functional requirements specified under 49 CFR Part 395 Subpart B are fully satisfied. |
| Azuga E-Logs | AZ-TAB-E8-ELD | 2.1.25 or higher | AZELD1 | Download | Download | Azuga | 4084305777 | products@azuga.com | https://www.azuga.com | 2570 N. First Street, #200 San Jose, CA, 95131, California | We have chosen to use wireless web services and email as our choice for the ELD output file - Driver or Official will use the Options button on the driver overview screen - Driver or Official will use the Roadside Inspection button on the drop down - This button will navigate the user to a Logs Grid page - The Logs Grid page will contain a button labeled "Transmit ELD Data File” - The Officer will tap on the button and be instructed to choose email or wireless web-services and enter the instructions or code to send the data file to the FMCSA | Power - P Device lost power during driving events for a total of 30 min or more over a 24-hour period Engine synchronization - E Device lost connection to the ECM (or other data source) for a total of more than 30 min during a 24-hour period Timing - T Device is not able to synchronize to UTC Positioning - L Device is not able to acquire a valid position measurement within 5 mi of vehicle movement for a total of more than 60 min over a 24 hour period. Data recording - R Device is no longer able to record or retain required event data or retrieve locally-stored recorded logs Data transfer - S Device continues to fail checks of the roadside transfer mechanism for three days following a Data Transfer Diagnostic Event Other ELD detected - O The eFleetSuite application has stopped working or is not responding as expected | Azuga ELD certifies based on our completion of the testing procedures provided by the FMCSA in the Electronic Logging Device Test Plan and Procedures document version 2.0 dated 10/17/2016 that AZ-TAB-E-ELD complies with all Federal Motor Carrier Safety Administration (FMCSA) specifications as found in 49 CFR Part 395 for Electronic Logging Devices, Subpart B.Devices, Subpart B. | |
| Azuga E-Logs BYOD | AZ-BYOD-ELD | 2.1.25 or higher | AZELD2 | Download | Download | Azuga | 4084305777 | products@azuga.com | https://www.azuga.com | 2570 N. First Street, #200 San Jose, CA, 95131, California | We have chosen to use wireless web services and email as our choice for the ELD output file - Driver or Official will use the Options button on the driver overview screen - Driver or Official will use the Roadside Inspection button on the drop down - This button will navigate the user to a Logs Grid page - The Logs Grid page will contain a button labeled "Transmit ELD Data File” - The Officer will tap on the button and be instructed to choose email or wireless web-services and enter the instructions or code to send the data file to the FMCSA | Power - P Device lost power during driving events for a total of 30 min or more over a 24-hour period Engine synchronization - E Device lost connection to the ECM (or other data source) for a total of more than 30 min during a 24-hour period Timing - T Device is not able to synchronize to UTC Positioning - L Device is not able to acquire a valid position measurement within 5 mi of vehicle movement for a total of more than 60 min over a 24 hour period. Data recording - R Device is no longer able to record or retain required event data or retrieve locally-stored recorded logs Data transfer - S Device continues to fail checks of the roadside transfer mechanism for three days following a Data Transfer Diagnostic Event Other ELD detected - O The eFleetSuite application has stopped working or is not responding as expected | Azuga ELD certifies based on our completion of the testing procedures provided by the FMCSA in the Electronic Logging Device Test Plan and Procedures document version 2.0 dated 10/17/2016 that AZ-TAB-E-ELD complies with all Federal Motor Carrier Safety Administration (FMCSA) specifications as found in 49 CFR Part 395 for Electronic Logging Devices, Subpart B.Devices, Subpart B. | |
| BELLFAM ELD | BRS | 2.7.13 or higher | BRS114 | Download | Download | Bellfam | 5852002004 | bellfamsp@gmail.com | http://none.com | 52 Forestglen Drive, Buffalo, NY 14221, NORTH PALM BEACH, FL 33408 | Telematic (Web Service, Email) | According to 49 CFR 395.4.9.1, drivers using the BELLFAM ELD system can transfer log data through telematics. If an officer needs to review a driver's logs, the driver can produce a report on their mobile device or transfer log data through web services or email. | The BELLFAM ELD system has the capability to self-detect any malfunctions as per the guidelines given in Appendix A, section 4.6. Drivers using the system will be alerted with a visual signal in case of any malfunction or diagnostic event that includes data recording, data transfer, missing data elements, power failure, engine synchronization, timing, positioning and unidentified driving. | The BELLFAM ELD has been put through a thorough testing process as per the standards set by the FMCSA. The BELLFAM ELD confirms that the combination of hardware and mobile application conforms to the standards of a compliant electronic logging system and all the functional requirements specified under 49 CFR Part 395 Subpart B are fully satisfied. |
| BEST SOURCE ELD | BRS | 2.0 or higher | BRS218 | Download | Download | Best Source ELD | (331) 261-4010 | support@bestsourceeld.com | http://BestSourceEld.com | PO BOX 87133, CAROL STREAM, IL,60188-7133, Glendale Hts,IL 60139 | BEST SOURCE ELD is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | BEST SOURCE ELD monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The BEST SOURCE ELD Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on BEST SOURCE ELD during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | BEST SOURCE ELD meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. BEST SOURCE ELD was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| BEST-ELD | BRS | 2.0 or higher | BRS131 | Download | Download | BEST-ELD | 9088005555 | admin@best-eld.xyz | http://best-eld.xyz | 1301 Lamar, Dayton, OH 45404, Dayton, OH, 45069 | BEST-ELD is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | BEST-ELD monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The BEST-ELD Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on BEST-ELD during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | BEST-ELD meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. BEST-ELD was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| BIT ELD Dashcam | BIT18000 | 6.0.5 or higher | B1TCAM | Download | Download | Blue Ink Tech | (304) 381-1512 | support@blueinktech.com | https://blueinktech.com | 1102 3rd Ave; Suite 401, Huntington, WV 25701 | Telematic (Web Service, Email) | Supported and certified data transfer mechanisms: Web Services per 4.10.1.1 & Email per 4.10.1.2. The web services data exchange has been tested with the FMCSA endpoint. Log in to the ELD with a valid username and password. Select the "Main Menu" at the top-left of the screen. The "Main Menu" icon looks like 3 horizontal lines stacked on top of each other. Select "Roadside Inspection" The ELD records will be presented on the screen. To transfer data, click the green gear at the bottom-right of the screen. Click "Email Records to DOT" to send the logs via email. Click "Send Records to DOT Web Server" to send the logs via Web Services. | Power Compliance malfunction per 4.6.1.1 Engine Synchronization malfunction per 4.6.1.2 Timing Compliance malfunction per 4.6.1.3 Positioning Compliance malfunction per 4.6.1.4 Data Recording Compliance malfunction per 4.6.1.5 Data Transfer Compliance malfunction per 4.6.1.7 | Blue Ink Technology, Inc. certifies that this ELD device was tested and meets the requirements stated in the ELD Final Rule. |
| BIT ELD for Android | BIT17001 | 6.0.5 or higher | BITELD | Download | Download | Blue Ink Tech | (304) 381-1512 | support@blueinktech.com | https://blueinktech.com | 1102 3rd Ave; Suite 401, Huntington, WV 25701 | Telematic (Web Service, Email) | Supported and certified data transfer mechanisms: Web Services per 4.10.1.1 & Email per 4.10.1.2. The web services data exchange has been tested with the FMCSA endpoint. Log in to the ELD with a valid username and password. Select the "Main Menu" at the top-left of the screen. The "Main Menu" icon looks like 3 horizontal lines stacked on top of each other. Select "Roadside Inspection" The ELD records will be presented on the screen. To transfer data, click the green gear at the bottom-right of the screen. Click "Email Records to DOT" to send the logs via email. Click "Send Records to DOT Web Server" to send the logs via Web Services. | Power Compliance malfunction per 4.6.1.1 Engine Synchronization malfunction per 4.6.1.2 Timing Compliance malfunction per 4.6.1.3 Positioning Compliance malfunction per 4.6.1.4 Data Recording Compliance malfunction per 4.6.1.5 Data Transfer Compliance malfunction per 4.6.1.7 | An all-hands meeting was held with all of the employees of our company in attendance. We went through the ELD Final Rule as a group. Each requirement was read aloud. We created a document that specifies how we satisfy each of the requirements and any interpretations we made. Our team was in unanimous agreement that our system complies with the ELD Final Rule. |
| BIT ELD for Apple | BIT17001 | 6.0.5 or higher | BITELD | Download | Download | Blue Ink Tech | (304) 381-1512 | support@blueinktech.com | https://blueinktech.com | 1102 3rd Ave; Suite 401, Huntington, WV 25701 | Telematic (Web Service, Email) | Supported and certified data transfer mechanisms: Web Services per 4.10.1.1 & Email per 4.10.1.2. The web services data exchange has been tested with the FMCSA endpoint. Log in to the ELD with a valid username and password. Select the "Main Menu" at the top-left of the screen. The "Main Menu" icon looks like 3 horizontal lines stacked on top of each other. Select "Roadside Inspection" The ELD records will be presented on the screen. To transfer data, click the green gear at the bottom-right of the screen. Click "Email Records to DOT" to send the logs via email. Click "Send Records to DOT Web Server" to send the logs via Web Services. | Power Compliance malfunction per 4.6.1.1 Engine Synchronization malfunction per 4.6.1.2 Timing Compliance malfunction per 4.6.1.3 Positioning Compliance malfunction per 4.6.1.4 Data Recording Compliance malfunction per 4.6.1.5 Data Transfer Compliance malfunction per 4.6.1.7 | An all-hands meeting was held with all of the employees of our company in attendance. We went through the ELD Final Rule as a group. Each requirement was read aloud. We created a document that specifies how we satisfy each of the requirements and any interpretations we made. Our team was in unanimous agreement that our system complies with the ELD Final Rule. |
| BIT ELD Gen2 | BIT17003 | 6.0.5 or higher | BITEG2 | Download | Download | Blue Ink Tech | (304) 381-1512 | support@blueinktech.com | https://blueinktech.com | 1102 3rd Ave; Suite 401, Huntington, WV 25701 | Telematic (Web Service, Email) | Supported and certified data transfer mechanisms: Web Services per 4.10.1.1 & Email per 4.10.1.2. The web services data exchange has been tested with the FMCSA endpoint. Log in to the ELD with a valid username and password. Select the "Main Menu" at the top-left of the screen. The "Main Menu" icon looks like 3 horizontal lines stacked on top of each other. Select "Roadside Inspection" The ELD records will be presented on the screen. To transfer data, click the green gear at the bottom-right of the screen. Click "Email Records to DOT" to send the logs via email. Click "Send Records to DOT Web Server" to send the logs via Web Services. | Power Compliance malfunction per 4.6.1.1 Engine Synchronization malfunction per 4.6.1.2 Timing Compliance malfunction per 4.6.1.3 Positioning Compliance malfunction per 4.6.1.4 Data Recording Compliance malfunction per 4.6.1.5 Data Transfer Compliance malfunction per 4.6.1.7 | Blue Ink Technology, Inc. certifies that this ELD device was tested and meets the requirements stated in the ELD Final Rule. |
| BIT OBD ELD for Android | BIT17002 | 6.0.5 or higher | BITELD | Download | Download | Blue Ink Tech | (304) 381-1512 | support@blueinktech.com | https://blueinktech.com | 1102 3rd Ave; Suite 401, Huntington, WV 25701 | Telematic (Web Service, Email) | Supported and certified data transfer mechanisms: Web Services per 4.10.1.1 & Email per 4.10.1.2. The web services data exchange has been tested with the FMCSA endpoint. Log in to the ELD with a valid username and password. Select the "Main Menu" at the top-left of the screen. The "Main Menu" icon looks like 3 horizontal lines stacked on top of each other. Select "Roadside Inspection" The ELD records will be presented on the screen. To transfer data, click the green gear at the bottom-right of the screen. Click "Email Records to DOT" to send the logs via email. Click "Send Records to DOT Web Server" to send the logs via Web Services. | Power Compliance malfunction per 4.6.1.1 Engine Synchronization malfunction per 4.6.1.2 Timing Compliance malfunction per 4.6.1.3 Positioning Compliance malfunction per 4.6.1.4 Data Recording Compliance malfunction per 4.6.1.5 Data Transfer Compliance malfunction per 4.6.1.7 | An all-hands meeting was held with all of the employees of our company in attendance. We went through the ELD Final Rule as a group. Each requirement was read aloud. We created a document that specifies how we satisfy each of the requirements and any interpretations we made. Our team was in unanimous agreement that our system complies with the ELD Final Rule. Our OBD-II ELD was tested on multiple medium duty vehicles from Dodge, Ford, and Chevrolet, however it does not work in all medium duty vehicles because there is not a standard way of acquiring the odometer reading in ODB-II enabled vehicles. Our OBD-II ELD only works with certain vehicles that have a Controller Area Network (CAN) diagnostics port. Our ELD was not tested in all possible combinations for make, model, trim, year, ECU, and instrument cluster configurations so it is possible our OBD-II will not read the odometer from all Dodge, Ford, or Chevrolet vehicles. |
| BIT OBD ELD for Apple | BIT17002 | 6.0.5 or higher | BITELD | Download | Download | Blue Ink Tech | (304) 381-1512 | support@blueinktech.com | https://blueinktech.com | 1102 3rd Ave; Suite 401, Huntington, WV 25701 | Telematic (Web Service, Email) | Supported and certified data transfer mechanisms: Web Services per 4.10.1.1 & Email per 4.10.1.2. The web services data exchange has been tested with the FMCSA endpoint. Log in to the ELD with a valid username and password. Select the "Main Menu" at the top-left of the screen. The "Main Menu" icon looks like 3 horizontal lines stacked on top of each other. Select "Roadside Inspection" The ELD records will be presented on the screen. To transfer data, click the green gear at the bottom-right of the screen. Click "Email Records to DOT" to send the logs via email. Click "Send Records to DOT Web Server" to send the logs via Web Services. | Power Compliance malfunction per 4.6.1.1 Engine Synchronization malfunction per 4.6.1.2 Timing Compliance malfunction per 4.6.1.3 Positioning Compliance malfunction per 4.6.1.4 Data Recording Compliance malfunction per 4.6.1.5 Data Transfer Compliance malfunction per 4.6.1.7 | An all-hands meeting was held with all of the employees of our company in attendance. We went through the ELD Final Rule as a group. Each requirement was read aloud. We created a document that specifies how we satisfy each of the requirements and any interpretations we made. Our team was in unanimous agreement that our system complies with the ELD Final Rule. Our OBD-II ELD was tested on multiple medium duty vehicles from Dodge, Ford, and Chevrolet, however it does not work in all medium duty vehicles because there is not a standard way of acquiring the odometer reading in ODB-II enabled vehicles. Our OBD-II ELD only works with certain vehicles that have a Controller Area Network (CAN) diagnostics port. Our ELD was not tested in all possible combinations for make, model, trim, year, ECU, and instrument cluster configurations so it is possible our OBD-II will not read the odometer from all Dodge, Ford, or Chevrolet vehicles. |
| BIT OBD-II ELD Gen2 | BIT17004 | 6.0.5 or higher | BITOG2 | Download | Download | Blue Ink Tech | (304) 381-1512 | support@blueinktech.com | https://blueinktech.com | 1102 3rd Ave; Suite 401, Huntington, WV 25701 | Telematic (Web Service, Email) | Supported and certified data transfer mechanisms: Web Services per 4.10.1.1 & Email per 4.10.1.2. The web services data exchange has been tested with the FMCSA endpoint. Log in to the ELD with a valid username and password. Select the "Main Menu" at the top-left of the screen. The "Main Menu" icon looks like 3 horizontal lines stacked on top of each other. Select "Roadside Inspection" The ELD records will be presented on the screen. To transfer data, click the green gear at the bottom-right of the screen. Click "Email Records to DOT" to send the logs via email. Click "Send Records to DOT Web Server" to send the logs via Web Services. | Power Compliance malfunction per 4.6.1.1 Engine Synchronization malfunction per 4.6.1.2 Timing Compliance malfunction per 4.6.1.3 Positioning Compliance malfunction per 4.6.1.4 Data Recording Compliance malfunction per 4.6.1.5 Data Transfer Compliance malfunction per 4.6.1.7 | Blue Ink Technology, Inc. certifies that this ELD device was tested and meets the requirements stated in the ELD Final Rule. Our OBD-II ELD was tested on multiple medium duty vehicles from Dodge, Ford, and Chevrolet, however it does not work in all medium duty vehicles because there is not a standard way of acquiring the odometer reading in ODB-II enabled vehicles. Our OBD-II ELD only works with certain vehicles that have a Controller Area Network (CAN) diagnostics port. Our ELD was not tested in all possible combinations for make, model, trim, year, ECU, and instrument cluster configurations so it is possible our OBD-II will not read the odometer from all Dodge, Ford, or Chevrolet vehicles. |
| BITEC ELD | BRS | 2.0 or higher | BRS253 | Download | Download | BITEC CORP | 9735360165 | info@eldbitec.com | http://eldbitec.com | 200 Vesey Street, 24th Floor, New York/New York/10281 | BITEC ELD is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | BITEC ELD monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The BITEC ELD Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on BITEC ELD during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | BITEC ELD meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. BITEC ELD was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| Black Bear ELD | BRS | 2.0 or Higher | BRS254 | Download | Download | Black Bear ELD | 1-800-394-8081 | blackbeareld@gmail.com | http://www.blackbeareld.com | 10614 Avenida Fresca Dr, Bakersfield, CA 93311 | BLACK BEAR ELD is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | BLACK BEAR ELD monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The BLACK BEAR ELD Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on BLACK BEAR ELD during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | BLACK BEAR ELD meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. BLACK BEAR ELD was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| BLOG ELD | BRS | 2.4.13 or higher | BRS135 | Download | Download | Blog ELD | 8133255219 | bllblogeld@gmail.com | http://www.blogeld.com | 2319 W Aileen St, Tampa FL 33607 | Local (Bluetooth) , Telematic (Web Service, Email) | BLOG ELD is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | BLOG ELD monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The BLOG ELD Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on BLOG ELD during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | BLOG ELD meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. BLOG ELD was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. |
| BluAgent ELD | iOS & CALAMP 4230 | 1803.0226 | BA0001 | Download | Download | BLUAGENT TECHNOLOGIES, INC | (619)-878-5852 | david@bluagent.com | http://bluagent.com/ | 9765 Marconi Drive Suite 200M, 9765 MARCONI DRIVE SUITE 200M, SAN DIEGO, CA 92154 | The BluAgent Electronic Logbook provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. This can be done by selecting the Roadside Inspection button from the main HOS dashboard and selecting the option for Data Transfer. A list of supported data transfer options is then displayed which include Bluetooth, Email, USB, and web service. A Select Vehicle option is also available for selecting a vehicle upon performing the data transfer, this option enables the BluAgent Electronic Logbook to produce a data file or a series of data files of ELD records for a subset of its vehicles used by the driver. • Transfer via Bluetooth - this option enables the user to transfer files through Bluetooth. The ELD prompts for an output file comment which the driver may enter (optional). After the input, if Bluetooth is not yet turned on, a prompt will appear asking you to turn it on. You will then be asked to select the device name to which the data will be transmitted via Bluetooth. • Transfer via Email - this option enables the user to transfer files through email. The ELD output file is encrypted using AES-256 in FIPS Publication 197. Before sending, the ELD prompts for an output file comment which the driver may enter (optional). The email is then automatically sent to the FMCSA email address specified in the ELD Provider Registration website: fmcsaeldsub@dot.gov • Transfer via USB - this option enables the user to transfer files through USB (external devices). However, prior to saving the driver’s ELD file to an external storage/device, the ELD re-authenticates the driver account by asking for its password. • Transfer via Web Service - this option enables the user to transfer files to FMCSA via Web Services. The Web Service data transfer follows the following standards: WSDL, SOAP, XML. | The BluAgent Electronic Logbook ELD is capable of monitoring its compliance for various detectable malfunctions. At each instance when an ELD malfunction event is detected or cleared by the BluAgent Electronic Logbook ELD, the ELD records the event. The recorded malfunction events are inconsistencies found while monitoring the ELD against FMCSA compliance requirements. Malfunction occurrences are indicated in the application header and in the Android & iOS notification toolbar with the letter ‘M’, respectively. The following shows the list of detectable malfunctions: ● Power Malfunction ● Engine Synchronization Malfunction ● Timing Malfunction ● Position Malfunction ● Data Recording Malfunction ● Data Transfer Malfunction Once the Malfunctions indicator ‘M’ is tapped, a dialog will be displayed with a list of the detected malfunction events alongside a ‘Clear’ button for each event. Tapping the Clear button will clear out the detected malfunction event. | The BluAgent Electronic Logbook ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The BluAgent Electronic Logbook ELD was installed on various types and sizes of Android & iOS phones and tablets. Testing was performed through the use of a J1939 simulator and actual vehicles while having been connected to the <VBUS Device Name (ex: Geometris, Digi WVA, CalAmp 4230, Pacific Track)> engine connected device. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the Hours of Service web application (portal) that can be accessed through a web browser. | |
| BluAgent ELD | Pacifik Track PT30 | 3.0.2118.211028 | BA0001 | Download | Download | BLUAGENT TECHNOLOGIES, INC | (619)-878-5852 | david@bluagent.com | http://bluagent.com/ | 9765 Marconi Drive Suite 200M, 9765 MARCONI DRIVE SUITE 200M, SAN DIEGO, CA 92154 | The < BluAgent Electronic Logbook > provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. This can be done by selecting the Roadside Inspection button from the main HOS dashboard and selecting the option for Data Transfer. A list of supported data transfer options is then displayed which include Bluetooth, Email, USB, and web service. A Select Vehicle option is also available for selecting a vehicle upon performing the data transfer, this option enables the <BluAgent Electronic Logbook> to produce a data file or a series of data files of ELD records for a subset of its vehicles used by the driver. • Transfer via Bluetooth - this option enables the user to transfer files through Bluetooth. The ELD prompts for an output file comment which the driver may enter (optional). After the input, if Bluetooth is not yet turned on, a prompt will appear asking you to turn it on. You will then be asked to select the device name to which the data will be transmitted via Bluetooth. • Transfer via Email - this option enables the user to transfer files through email. The ELD output file is encrypted using AES-256 in FIPS Publication 197. Before sending, the ELD prompts for an output file comment which the driver may enter (optional). The email is then automatically sent to the FMCSA email address specified in the ELD Provider Registration website: fmcsaeldsub@dot.gov • Transfer via USB - this option enables the user to transfer files through USB (external devices). However, prior to saving the driver’s ELD file to an external storage/device, the ELD re-authenticates the driver account by asking for its password. • Transfer via Web Service - this option enables the user to transfer files to FMCSA via Web Services. The Web Service data transfer follows the following standards: WSDL, SOAP, XML. | The <BluAgent Electronic Logbook> ELD is capable of monitoring its compliance for various detectable malfunctions. At each instance when an ELD malfunction event is detected or cleared by the < BluAgent Electronic Logbook > ELD, the ELD records the event. The recorded malfunction events are inconsistencies found while monitoring the ELD against FMCSA compliance requirements. Malfunction occurrences are indicated in the application header and in the Android/iOS notification toolbar with the letter ‘M’, respectively. The following shows the list of detectable malfunctions: • Power Malfunction • Engine Synchronization Malfunction • Timing Malfunction • Position Malfunction • Data Recording Malfunction • Data Transfer Malfunction Once the Malfunctions indicator ‘M’ is tapped, a dialog will be displayed with a list of the detected malfunction events alongside a ‘Clear’ button for each event. Tapping the Clear button will clear out the detected malfunction event. | The <BluAgent Electronic Logbook> was certified by the <Vistrack> testing team through successful execution and verification of the FMCSA ELD Test Procedures. The <BluAgent Electronic Logbook> was installed on various types and sizes of Android & iOS phones and tablets. Testing was performed through the use of a J1939 simulator and actual vehicles while having been connected to the < Pacific Track)> engine connected device. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the HOS web application (portal) that can be accessed through a web browser | |
| BluAgent ELD | Android & IOSix | 1.0.1805.14123 | BA0001 | Download | Download | BLUAGENT TECHNOLOGIES, INC | (619)-878-5852 | david@bluagent.com | http://bluagent.com/ | 9765 Marconi Drive Suite 200M, 9765 MARCONI DRIVE SUITE 200M, SAN DIEGO, CA 92154 | The BluAgent Electronic Logbook provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. This can be done by selecting the Roadside Inspection button from the main HOS dashboard and selecting the option for Data Transfer. A list of supported data transfer options is then displayed which include Bluetooth, Email, and web service. A Select Vehicle option is also available for selecting a vehicle upon performing the data transfer, this option enables the BluAgent Electronic Logbook to produce a data file or a series of data files of ELD records for a subset of its vehicles used by the driver. • Transfer via Bluetooth - this option enables the user to transfer files through Bluetooth. The ELD prompts for an output file comment which the driver may enter (optional). After the input, if Bluetooth is not yet turned on, a prompt will appear asking you to turn it on. You will then be asked to select the device name to which the data will be transmitted via Bluetooth. • Transfer via Email - this option enables the user to transfer files through email. The ELD output file is encrypted using AES-256 in FIPS Publication 197. Before sending, the ELD prompts for an output file comment which the driver may enter (optional). The email is then automatically sent to the FMCSA email address specified in the ELD Provider Registration website: fmcsaeldsub@dot.gov • Transfer via Web Service - this option enables the user to transfer files to FMCSA via Web Services. The Web Service data transfer follows the following standards: WSDL, SOAP, XML. | The BluAgent Electronic Logbook ELD is capable of monitoring its compliance for various detectable malfunctions. At each instance when an ELD malfunction event is detected or cleared by the BluAgent Electronic Logbook ELD, the ELD records the event. The recorded malfunction events are inconsistencies found while monitoring the ELD against FMCSA compliance requirements. Malfunction occurrences are indicated in the application header and in the Android & iOS notification toolbar with the letter ‘M’, respectively. The following shows the list of detectable malfunctions: ● Power Malfunction ● Engine Synchronization Malfunction ● Timing Malfunction ● Position Malfunction ● Data Recording Malfunction ● Data Transfer Malfunction Once the Malfunctions indicator ‘M’ is tapped, a dialog will be displayed with a list of the detected malfunction events alongside a ‘Clear’ button for each event. Tapping the Clear button will clear out the detected malfunction event. | The BluAgent Electronic Logbook ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The BluAgent Electronic Logbook ELD was installed on various types and sizes of Android & iOS phones and tablets. Testing was performed through the use of a J1939 simulator and actual vehicles while having been connected to the <VBUS Device Name (ex: Geometris, Digi WVA, CalAmp 4230, Pacific Track)> engine connected device. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the Hours of Service web application (portal) that can be accessed through a web browser. | |
| BluAgent ELD | iOS & IOSix | 1.0.1805.14123 | BA0001 | Download | Download | BLUAGENT TECHNOLOGIES, INC | (619)-878-5852 | david@bluagent.com | http://bluagent.com/ | 9765 Marconi Drive Suite 200M, 9765 MARCONI DRIVE SUITE 200M, SAN DIEGO, CA 92154 | The BluAgent Electronic Logbook provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. This can be done by selecting the Roadside Inspection button from the main HOS dashboard and selecting the option for Data Transfer. A list of supported data transfer options is then displayed which include Bluetooth, Email, and web service. A Select Vehicle option is also available for selecting a vehicle upon performing the data transfer, this option enables the BluAgent Electronic Logbook to produce a data file or a series of data files of ELD records for a subset of its vehicles used by the driver. • Transfer via Bluetooth - this option enables the user to transfer files through Bluetooth. The ELD prompts for an output file comment which the driver may enter (optional). After the input, if Bluetooth is not yet turned on, a prompt will appear asking you to turn it on. You will then be asked to select the device name to which the data will be transmitted via Bluetooth. • Transfer via Email - this option enables the user to transfer files through email. The ELD output file is encrypted using AES-256 in FIPS Publication 197. Before sending, the ELD prompts for an output file comment which the driver may enter (optional). The email is then automatically sent to the FMCSA email address specified in the ELD Provider Registration website: fmcsaeldsub@dot.gov • Transfer via Web Service - this option enables the user to transfer files to FMCSA via Web Services. The Web Service data transfer follows the following standards: WSDL, SOAP, XML. | The BluAgent Electronic Logbook ELD is capable of monitoring its compliance for various detectable malfunctions. At each instance when an ELD malfunction event is detected or cleared by the BluAgent Electronic Logbook ELD, the ELD records the event. The recorded malfunction events are inconsistencies found while monitoring the ELD against FMCSA compliance requirements. Malfunction occurrences are indicated in the application header and in the Android & iOS notification toolbar with the letter ‘M’, respectively. The following shows the list of detectable malfunctions: ● Power Malfunction ● Engine Synchronization Malfunction ● Timing Malfunction ● Position Malfunction ● Data Recording Malfunction ● Data Transfer Malfunction Once the Malfunctions indicator ‘M’ is tapped, a dialog will be displayed with a list of the detected malfunction events alongside a ‘Clear’ button for each event. Tapping the Clear button will clear out the detected malfunction event. | The BluAgent Electronic Logbook ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The BluAgent Electronic Logbook ELD was installed on various types and sizes of Android & iOS phones and tablets. Testing was performed through the use of a J1939 simulator and actual vehicles while having been connected to the <VBUS Device Name (ex: Geometris, Digi WVA, CalAmp 4230, Pacific Track)> engine connected device. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the Hours of Service web application (portal) that can be accessed through a web browser. | |
| BluAgent ELD | Android & CALAMP 4230 | 1.0 | BA0001 | Download | Download | BLUAGENT TECHNOLOGIES, INC | (619)-878-5852 | david@bluagent.com | http://bluagent.com/ | 9765 Marconi Drive Suite 200M, 9765 MARCONI DRIVE SUITE 200M, SAN DIEGO, CA 92154 | The BluAgent Electronic Logbook provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. This can be done by selecting the Roadside Inspection button from the main HOS dashboard and selecting the option for Data Transfer. A list of supported data transfer options is then displayed which include Bluetooth, Email, USB, and web service. A Select Vehicle option is also available for selecting a vehicle upon performing the data transfer, this option enables the BluAgent Electronic Logbook to produce a data file or a series of data files of ELD records for a subset of its vehicles used by the driver. • Transfer via Bluetooth - this option enables the user to transfer files through Bluetooth. The ELD prompts for an output file comment which the driver may enter (optional). After the input, if Bluetooth is not yet turned on, a prompt will appear asking you to turn it on. You will then be asked to select the device name to which the data will be transmitted via Bluetooth. • Transfer via Email - this option enables the user to transfer files through email. The ELD output file is encrypted using AES-256 in FIPS Publication 197. Before sending, the ELD prompts for an output file comment which the driver may enter (optional). The email is then automatically sent to the FMCSA email address specified in the ELD Provider Registration website: fmcsaeldsub@dot.gov • Transfer via USB - this option enables the user to transfer files through USB (external devices). However, prior to saving the driver’s ELD file to an external storage/device, the ELD re-authenticates the driver account by asking for its password. • Transfer via Web Service - this option enables the user to transfer files to FMCSA via Web Services. The Web Service data transfer follows the following standards: WSDL, SOAP, XML. | The BluAgent Electronic Logbook ELD is capable of monitoring its compliance for various detectable malfunctions. At each instance when an ELD malfunction event is detected or cleared by the BluAgent Electronic Logbook ELD, the ELD records the event. The recorded malfunction events are inconsistencies found while monitoring the ELD against FMCSA compliance requirements. Malfunction occurrences are indicated in the application header and in the Android & iOS notification toolbar with the letter ‘M’, respectively. The following shows the list of detectable malfunctions: ● Power Malfunction ● Engine Synchronization Malfunction ● Timing Malfunction ● Position Malfunction ● Data Recording Malfunction ● Data Transfer Malfunction Once the Malfunctions indicator ‘M’ is tapped, a dialog will be displayed with a list of the detected malfunction events alongside a ‘Clear’ button for each event. Tapping the Clear button will clear out the detected malfunction event. | The BluAgent Electronic Logbook ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The BluAgent Electronic Logbook ELD was installed on various types and sizes of Android & iOS phones and tablets. Testing was performed through the use of a J1939 simulator and actual vehicles while having been connected to the <VBUS Device Name (ex: Geometris, Digi WVA, CalAmp 4230, Pacific Track)> engine connected device. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the Hours of Service web application (portal) that can be accessed through a web browser. | |
| BluAgent ELD | Android & BAFX/ELM327 | 1.0 | BA0001 | Download | Download | BLUAGENT TECHNOLOGIES, INC | (619)-878-5852 | david@bluagent.com | http://bluagent.com/ | 9765 Marconi Drive Suite 200M, 9765 MARCONI DRIVE SUITE 200M, SAN DIEGO, CA 92154 | The BluAgent Electronic Logbook provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. This can be done by selecting the Roadside Inspection button from the main HOS dashboard and selecting the option for Data Transfer. A list of supported data transfer options is then displayed which include Bluetooth, Email, USB, and web service. A Select Vehicle option is also available for selecting a vehicle upon performing the data transfer, this option enables the BluAgent Electronic Logbook to produce a data file or a series of data files of ELD records for a subset of its vehicles used by the driver. • Transfer via Bluetooth - this option enables the user to transfer files through Bluetooth. The ELD prompts for an output file comment which the driver may enter (optional). After the input, if Bluetooth is not yet turned on, a prompt will appear asking you to turn it on. You will then be asked to select the device name to which the data will be transmitted via Bluetooth. • Transfer via Email - this option enables the user to transfer files through email. The ELD output file is encrypted using AES-256 in FIPS Publication 197. Before sending, the ELD prompts for an output file comment which the driver may enter (optional). The email is then automatically sent to the FMCSA email address specified in the ELD Provider Registration website: fmcsaeldsub@dot.gov • Transfer via USB - this option enables the user to transfer files through USB (external devices). However, prior to saving the driver’s ELD file to an external storage/device, the ELD re-authenticates the driver account by asking for its password. • Transfer via Web Service - this option enables the user to transfer files to FMCSA via Web Services. The Web Service data transfer follows the following standards: WSDL, SOAP, XML. | The BluAgent Electronic Logbook ELD is capable of monitoring its compliance for various detectable malfunctions. At each instance when an ELD malfunction event is detected or cleared by the BluAgent Electronic Logbook ELD, the ELD records the event. The recorded malfunction events are inconsistencies found while monitoring the ELD against FMCSA compliance requirements. Malfunction occurrences are indicated in the application header and in the Android & iOS notification toolbar with the letter ‘M’, respectively. The following shows the list of detectable malfunctions: ● Power Malfunction ● Engine Synchronization Malfunction ● Timing Malfunction ● Position Malfunction ● Data Recording Malfunction ● Data Transfer Malfunction Once the Malfunctions indicator ‘M’ is tapped, a dialog will be displayed with a list of the detected malfunction events alongside a ‘Clear’ button for each event. Tapping the Clear button will clear out the detected malfunction event. | The BluAgent Electronic Logbook ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The BluAgent Electronic Logbook ELD was installed on various types and sizes of Android & iOS phones and tablets. Testing was performed through the use of a J1939 simulator and actual vehicles while having been connected to the <VBUS Device Name (ex: Geometris, Digi WVA, CalAmp 4230, Pacific Track)> engine connected device. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the Hours of Service web application (portal) that can be accessed through a web browser. | |
| Blue Link GPS | BlueLink | 3.0.6 | WLI001 | Download | Download | Eddy Stevens | 9056699677 | eddy@securitystores.com | http://www.itrackgps.com | 201 Millway ave Unit 12, Concord/Ontario/L4K5K8 | There is a one page document describing how the officer can enter “officer mode” by clicking on the icon on the top right “officer icon” present on all screens. Once in “officer mode” the Daily Header and Full Day ELD Record defined by the FMCSA are displayed. On the bottom of the page there is a button marked “send report.” Clicking this button brings up the window to email the report to any email address entered. It also features an option to submit the data to the FMCSA web services endpoint. This will utilize the SOAP protocol, per the FMCSA documentation, to transmit the ELD data file and the output file comment entered by the inspecting officer. | Each malfunction has been coded following the "Standard Coding for Required Compliance Malfunction and Data Diagnostic Event Detection" definitions regarding "Malfunction/Diagnostic Code", "Malfunction Description" and "Data Diagnostic Event." Power Compliance monitoring assures that the ELD will become fully functional within one minute of the engine on event and remain on as long as the vehicle's engine stays powered. Engine Synchronization monitoring determines our connection to the ECM. This alerts the driver if there is a loss of connectivity to the ECM. For Timing Compliance Monitoring, we periodically check UTC time via the internet. For Positioning Compliance the ELD records the location, and uses the last valid position measurement and includes the latitude and longitude coordinates and distance traveled in miles, since the last valid position measurement. We also measure the elapsed time during periods when the ELD does not require a valid position measurement within 5 miles. If the time exceeds 60 minutes in a 24 hour period, it is marked as a positioning compliance malfunction. An ELD monitors its storage capacity and integrity and detects data recording compliance malfunction if it can no longer record or retain required events or retrieve recorded logs that are not otherwise catalogued remotely by the motor carrier. The ELD monitors the completeness of the ELD event record information in relation to the required data elements for each event type and records a missing data elements data diagnostics event for the driver if any required field is missing at the time of recording. We check to make sure that our data transfer mechanism works properly at least once every 7 days. All Data Diagnostic events are handled similarly according to the mandate. | By using the Blue Link Wireless device we have stress tested it under strict conditions. From this unique type of testing we have noticed it is safe, fully functional, and reliable. At all times of operation it is able to communicate with the FMCSA servers and be compliant with the FMCSA policy. In addition, it meets and goes beyond the expectations of the FMCSA by being error-free and responsive to problems by giving signals when there is a malfunction within the system. Furthermore, after repeated testings we have come to the conclusion that it meets our standards and is safe, reliable, and successfully meets the criteria of the FMCSA regulation. | |
| BLUE STAR ELD | BSE | 1.0.0 or higher | BSE777 | Download | Download | BLUE STAR ELD INC | (267) 551-4401 | sales@bluestareld.com | https://www.bluestareld.com | 501 Cambria Ave Suite 311, BENSALEM, PA 19020 | Telematic (Web Service, Email) | Blue Star ELD is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press the “DOT Inspection” menu item, then press the “Transfer Logs” button, select Web Service as the Data Transfer Type, and press the “Transfer Logs” button. In order to send the ELD records via Email, a driver must press the “DOT Inspection” menu item, then press the “Transfer Logs” button, select Email as the Data Transfer Type, and press the “Transfer Data” button. | Blue Star ELD monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The Blue Star ELD Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on Blue Star ELD during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | Blue Star ELD meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of Title 49, Code of Federal Regulations. Blue Star ELD was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. |
| BLUE STAR ELD | BRS | 2.4-34 or above. | BRS153 | Download | Download | BLUE STAR ELD INC | (267) 551-4401 | sales@bluestareld.com | https://www.bluestareld.com | 501 Cambria Ave Suite 311, BENSALEM, PA 19020 | Telematic (Web Service, Email) | The supported data transfer method by BLUE STAR ELD is telematics, namely web services and email. The driver can enter the DOT Inspection Mode and tap "Start Inspection" to display logs for the safety officer, or tap "Email logs" to email their logs or "Send logs" to transfer them via web services. | As required by section 4.6.1.2 of 49 CFR part 395, subpart B, Appendix A, BLUE STAR ELD visually alerts the drivers of any malfunction or diagnostic event, including data recording, data transfer, required data elements, power, engine synchronization, timing, positioning, and unidentified driving. | BLUE STAR ELD was tested according to FMCSA's testing procedures, proving its adherence to federal legislation. Thus, BLUE STAR ELD hereby certifies that the product is compliant with the requirements of the ELD mandate. |
| Blue Tree ELD | BT500 / BT504 | 4.0 and higher | ELD001 | Download | Download | ORBCOMM | 1-800-ORBCOMM | FMSupport@orbcomm.com | https://www.orbcomm.com/ | 2700 N Military Trail, Boca Raton, FL 33431 USA | Telematic (Web Service, Email) | As a telematics provider we support both email & web service transfer. Instructions below & in user guide with images. Transferring Logs The Blue Tree Systems ELD allows transferring of your RODS to the DOT via email or web services. Email Transfer ¿ Tap the 'Email Logs' button. The email screen displays the destination email address as specified by the FMCSA. The roadside officer can enter a different email address ¿ If provided, enter the roadside inspector's comment ¿ Tap the 'Send' button to send your logs via email. Web Services Transfer ¿ Tap the 'Upload Logs' button ¿ If provided, enter the roadside inspector's comment ¿ Tap the 'Upload Logs' button to send your logs via webservices. | Code Malfunction Cause Resolution P Power Compliance The ELD has accumulated more than 30 minutes of driving time lost in a 24-hour period. There may be a fault in the ECM link or an issue with the ELD installation. Please contact your motor carrier. You should revert to paper logs. E Engine Synchronization The ELD has accumulated more than 30 minutes without ECM engine synchronization over a 24-hour period. There may be a fault in the ECM link or an issue with the ELD installation. Please contact your motor carrier. You should revert to paper logs. T Timing Compliance The ELD's internal clock in the vehicle has not yet synchronized with the server that resulted in a time deviation of 10+ minutes. This can occur when the vehicle the ELD is in has not been in service for a period of time? This should auto-resolve once the internal clock has synchronized with the Blue Tree server. If this malfunction does not auto-resolve or persists, please contact your motor carrier. L Positioning Compliance The ELD has accumulated more than 60 minutes without a GPS lock within a 24-hour period. This can occur when the vehicle is in any area without GPS / the GPS is disconnected or not properly fitted to the ELD. This should auto-resolve once the ELD gets a valid GPS lock. If this malfunction does not auto-resolve or persists, please contact your motor carrier. R Data Recording The ELD does not have sufficient storage capacity to record ELD events. Please contact your motor carrier. You should revert to paper logs. S Data Transfer Compliance The ELD has failed to transfer the driver's logs to the DOT as requested during a roadside inspection. Occurs if a Data Transfer Data Diagnostic event has not auto-resolved after 3 days from the when it was detected. Verify the ELD has network connectivity. You may be operating in a location with poor cellular coverage. If this malfunction does not auto-resolve within a 24-hour period, please contact your motor carrier. | Using the FMCSA provided test suite / document we added all cases to our manual test case repository and manually tested and logged results for each case. |
| BRANIX ELD | BRAIX | 2.16.5 or higher | BRS279 | Download | Download | Control y Monitoreo Avanzado S de RL de CV | +5216865678895 | eld.admin@branix.com | http://www.branix.com | Calzada CETYS 2901 3C, Mexicali, Baja California, 21259 | Telematic (Web Service, Email) | BRANIX ELD, or Electronic Logging Device, is a tool that offers a comprehensive overview of a driver's records during a roadside inspection. Not only does it provide this information within the app, but it also facilitates the transfer of telematics data through email or web services. The DOT Inspection mode allows the driver to choose the method that works best for them. To transfer ELD records through Web services, the driver needs to access the "DOT Inspection" menu and select the "Send Logs" option. Then, they should choose Web Service as the Data Transfer Type and click the "SEND" button. Similarly, to transfer ELD records via Email, the driver should follow the same steps but select Email as the Data Transfer Type before clicking the "SEND" button. | The BRANIX ELD system ensures compliance with technical requirements, identifies malfunctions and data inconsistencies, and maintains records of such occurrences. Compliance malfunctions and diagnostic events are classified with specific codes, including P for "Power compliance" malfunction, E for "Engine synchronization compliance" malfunction, T for "Timing compliance" malfunction, L for "Positioning compliance" malfunction, R for "Data recording compliance" malfunction, S for "Data transfer compliance" malfunction, O for "Other" ELD-detected malfunctions, 1 for "Power data diagnostic" event, 2 for "Engine synchronization data diagnostic" event, 3 for "Missing required data elements data diagnostic" event, 4 for "Data transfer data diagnostic" event, 5 for "Unidentified driving records data diagnostic" event, and 6 for "Other" ELD-identified diagnostic events. The BRANIX ELD Malfunction and Diagnostic Event Records document all malfunctions that occurred during the relevant time period. Active malfunctions are communicated to all drivers who may use the ELD. | BRANIX ELD has been thoroughly tested to ensure compliance with all the functional requirements outlined in Title 49, Part 395 of Section 4.9.1, Appendix A, Subpart B. BRANIX ELD can confidently certify that our ELD product adheres to all the necessary ELD regulations. |
| BreakerLog ELD | BLELD-5 and higher | 5.0 and higher | ELDMCB | Download | Download | Carrus Mobile, Inc. | +1 (855) 772-2778 | sales@breakerlog.com | http://www.breakerlog.com | 54 W 40 St, New York, NY 10018 | According to ELD Final Rule requirement, BreakerLog ELD supports and certifies a data transfer mechanism based on Telematic option using Email and Web-Services. In order for conduct a data transfer, the Driver must complete following steps: Select menu item “DOT Reports” Select “Create Data Transfer” Select from following data transfer methods: 1. Email – if selected, driver must complete following actions: 1.1. Enter optional “Output File Comment” in menu field 1.2. Enter the address provided by the inquiring party in appropriate field in mailing application 1.3. Complete action by selecting “Send” – email containing an encrypted ELD output file will be sent to specified address 2. Web Service – if selected Driver must complete following actions 2.1. Enter optional “Output File Comment” in menu field 2.2. Select “Complete Transfer”, after which report will be uploaded into FMCSA specified web service endpoint. | Breakerlog ELD system supports and monitors following malfunction events: a) P - “Power compliance” malfunction b) E - “Engine synchronization compliance” malfunction c) T - “Timing compliance” malfunction d) L - “Positioning compliance” malfunction e) R - “Data recording compliance” malfunction f) S - “Data transfer compliance” malfunction g) O - “Other” ELD detected malfunction | Carrus Mobile, Inc. certifies that BreakerLog ELD system for model BLELD-5 and higher and version 5.0 and higher has been sufficiently tested to meet the functional requirements included in the technical specifications in the Appendix to subpart B of part 395, title 49 of the Code of Federal Regulations based on the Compliance Test Procedures provided on FMCSA website available at the following link https://www.fmcsa.dot.gov/hours-service/elds/eld-test-procedures | |
| BridgeHaul ELD | Bluelink | 3.0.0 | BRHL01 | Download | Download | BridgeHaul Inc | 8007856438 | support@bridgehaul.com | https://bridgehaul.com | 177 E Colorado Blvd STE 200, Pasadena, CA 91105 | BridgeHaul's ELD supports telemetatics webservices data transfer and email. To transfer data as a driver, the driver clicks on “Send eRODs” in the settings menu. A modal will pop up in the center of the screen with an optional input field for a comment. The driver will indicate the transfer method by checking the “webservices” box or the “email” box. Once the driver adds the optional comment, he/she clicks “SEND” which will initiate the file transfer to the FMCSA via webservices. The ELD communicates to BridgeHaul’s internal servers via APIs over cellular service and BridgeHaul connects to an FMCSA SOAP service and submits a client certificate, the ELD data file with output file comment input by the driver. For email file transfers, BridgeHaul uses the secure/multipurpose internet mail exchange (S/MIME) standard which is encrypted using AES-256 (AES cipher with a 256-bit key length). BridgeHaul attaches the FMCSA’s ELD public key and is signed using BridgeHaul’s ELD private key that corresponds with the ELD public key submitted to the FMCSA by BridgeHaul during the self-certifying process. | Malfunctions and diagnostic events are flagged with a red icon on the ELD homescreen. Each malfunction or diagnostic event (the event) attributes a 1 digit code that further specifies the underlying malfunction or data diagnostic event as defined in Table 4 of the technical appendix to the ELD Final Rule. Attached to this event are additional required fields such as date, time, CMV, vehicle miles, and engine hours and driver profile. The ELD is has the ability to record all malfunction and data diagnostic events as defined in Table 4 of the technical appendix to the ELD Final Rule including power compliance, engine synchronization compliance, timing compliance, positioning compliance, data recording compliance, data transfer compliance, and other various malfunctions. For data diagnostic events, the ELD can detect and record power data diagnostic, engine synchronization diagnostic, missing required data element diagnostic , data transfer diagnostic, and unidentified driving record diagnostic events. Once the required elapsed time or value drops below the malfunction or diagnostic threshold the ELD records when the malfunction/diagnostic is cleared. In addition to the displayed icon, the ELD will flag and prompt a driver to accept or reject unidentified driving events that have not been claimed upon connecting to the device if any are present. | BridgeHaul Inc certifies that this ELD model and version has been sufficiently tested to meet the functional requirements included in the technical specifications in the Appendix to subpart B of part 395, title 49 of the Code of Federal Regulations, under the conditions in which the ELD would be used. | |
| BST ELD | BRS | 2.0 or higher | brs125 | Download | Download | Lhb Trucking inc | 7738758268 | info@lhbtrucking.net | http://lhbtrucking.net | 8821 W 84Th St, Justice, IL 60458 | BST ELD is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button | BST ELD monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The BST ELD Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on BST ELD during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | BST ELD meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. BST ELD was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| Budget Trucker | G3000 | 1824.190131.1 | HOS001 | Download | Download | Budget Trucker | 855-368-7233 | info@budgettrucker.com | http://budgettrucker.com | 6101 Long Prairie Road, Ste. 744-281, Flower Mound, TX | Data Transfer Description – Apple iOS Registrations Budget Trucker provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. This can be done by selecting the Roadside Inspection button from the main HOS dashboard and selecting the option for Data Transfer. A list of supported data transfer options is then displayed which include Bluetooth, Email, USB, and web service. A Select Vehicle option is also available for selecting a vehicle upon performing the data transfer, this option enables Budget Trucker to produce a data file or a series of data files of ELD records for a subset of its vehicles used by the driver. • Transfer via Bluetooth - this option enables the user to transfer files through Bluetooth. The ELD prompts for an output file comment which the driver may enter (optional). After the input, if Bluetooth is not yet turned on, a prompt will appear asking you to turn it on. You will then be asked to select the device name to which the data will be transmitted via Bluetooth. • Transfer via Email - this option enables the user to transfer files through email. The ELD output file is encrypted using AES-256 in FIPS Publication 197. Before sending, the ELD prompts for an output file comment which the driver may enter (optional). The email is then automatically sent to the FMCSA email address specified in the ELD Provider Registration website: fmcsaeldsub@dot.gov • Transfer via USB - this option enables the user to transfer files through USB (external devices). However, prior to saving the driver’s ELD file to an external storage/device, the ELD re-authenticates the driver account by asking for its password. • Transfer via Web Service - this option enables the user to transfer files to FMCSA via Web Services. The Web Service data transfer follows the following standards: WSDL, SOAP, XML. Data Transfer Description – iOS Registrations Budget Trucker provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. This can be done by selecting the Roadside Inspection button from the main HOS dashboard and selecting the option for Data Transfer. A list of supported data transfer options is then displayed which include Bluetooth, Email, and web service. A Select Vehicle option is also available for selecting a vehicle upon performing the data transfer, this option enables Budget Trucker to produce a data file or a series of data files of ELD records for a subset of its vehicles used by the driver. • Transfer via Bluetooth - this option enables the user to transfer files through Bluetooth. The ELD prompts for an output file comment which the driver may enter (optional). After the input, if Bluetooth is not yet turned on, a prompt will appear asking you to turn it on. You will then be asked to select the device name to which the data will be transmitted via Bluetooth. • Transfer via Email - this option enables the user to transfer files through email. The ELD output file is encrypted using AES-256 in FIPS Publication 197. Before sending, the ELD prompts for an output file comment which the driver may enter (optional). The email is then automatically sent to the FMCSA email address specified in the ELD Provider Registration website: fmcsaeldsub@dot.gov • Transfer via Web Service - this option enables the user to transfer files to FMCSA via Web Services. The Web Service data transfer follows the following standards: WSDL, SOAP, XML. | Summary of Malfunctions Budget Trucker ELD is capable of monitoring its compliance for various detectable malfunctions. At each instance when an ELD malfunction event is detected or cleared by Budget Trucker ELD, the ELD records the event. The recorded malfunction events are inconsistencies found while monitoring the ELD against FMCSA compliance requirements. Malfunction occurrences are indicated in the application header and in the Android & iOS notification toolbar with the letter ‘M’, respectively. The following shows the list of detectable malfunctions: Power Malfunction Engine Synchronization Malfunction Timing Malfunction Position Malfunction Data Recording Malfunction Data Transfer Malfunction Once the Malfunctions indicator ‘M’ is tapped, a dialog will be displayed with a list of the detected malfunction events alongside a ‘Clear’ button for each event. Tapping the Clear button will clear out the detected malfunction event. | Certifying Statement of FMCSA Regulation Testing Budget Trucker was certified by the Budget Trucker testing team through successful execution and verification of the FMCSA ELD Test Procedures. Budget Trucker was installed on various types and sizes of Android & iOS phones and tablets. Testing was performed through the use of a J1939 simulator and actual vehicles while having been connected to the Geometris engine connected device. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the HOS web application (portal) that can be accessed through a web browser. | |
| Budget Trucker | G3000 | 1.0.1625.6584 | HOS001 | Download | Download | Budget Trucker | 855-368-7233 | info@budgettrucker.com | http://budgettrucker.com | 6101 Long Prairie Road, Ste. 744-281, Flower Mound, TX | Data Transfer Description – Android Registrations Budget Trucker provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. This can be done by selecting the Roadside Inspection button from the main HOS dashboard and selecting the option for Data Transfer. A list of supported data transfer options is then displayed which include Bluetooth, Email, USB, and web service. A Select Vehicle option is also available for selecting a vehicle upon performing the data transfer, this option enables Budget Trucker to produce a data file or a series of data files of ELD records for a subset of its vehicles used by the driver. • Transfer via Bluetooth - this option enables the user to transfer files through Bluetooth. The ELD prompts for an output file comment which the driver may enter (optional). After the input, if Bluetooth is not yet turned on, a prompt will appear asking you to turn it on. You will then be asked to select the device name to which the data will be transmitted via Bluetooth. • Transfer via Email - this option enables the user to transfer files through email. The ELD output file is encrypted using AES-256 in FIPS Publication 197. Before sending, the ELD prompts for an output file comment which the driver may enter (optional). The email is then automatically sent to the FMCSA email address specified in the ELD Provider Registration website: fmcsaeldsub@dot.gov • Transfer via USB - this option enables the user to transfer files through USB (external devices). However, prior to saving the driver’s ELD file to an external storage/device, the ELD re-authenticates the driver account by asking for its password. • Transfer via Web Service - this option enables the user to transfer files to FMCSA via Web Services. The Web Service data transfer follows the following standards: WSDL, SOAP, XML. Data Transfer Description – iOS Registrations Budget Trucker provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. This can be done by selecting the Roadside Inspection button from the main HOS dashboard and selecting the option for Data Transfer. A list of supported data transfer options is then displayed which include Bluetooth, Email, and web service. A Select Vehicle option is also available for selecting a vehicle upon performing the data transfer, this option enables Budget Trucker to produce a data file or a series of data files of ELD records for a subset of its vehicles used by the driver. • Transfer via Bluetooth - this option enables the user to transfer files through Bluetooth. The ELD prompts for an output file comment which the driver may enter (optional). After the input, if Bluetooth is not yet turned on, a prompt will appear asking you to turn it on. You will then be asked to select the device name to which the data will be transmitted via Bluetooth. • Transfer via Email - this option enables the user to transfer files through email. The ELD output file is encrypted using AES-256 in FIPS Publication 197. Before sending, the ELD prompts for an output file comment which the driver may enter (optional). The email is then automatically sent to the FMCSA email address specified in the ELD Provider Registration website: fmcsaeldsub@dot.gov • Transfer via Web Service - this option enables the user to transfer files to FMCSA via Web Services. The Web Service data transfer follows the following standards: WSDL, SOAP, XML. | Summary of Malfunctions Budget Trucker ELD is capable of monitoring its compliance for various detectable malfunctions. At each instance when an ELD malfunction event is detected or cleared by Budget Trucker ELD, the ELD records the event. The recorded malfunction events are inconsistencies found while monitoring the ELD against FMCSA compliance requirements. Malfunction occurrences are indicated in the application header and in the Android & iOS notification toolbar with the letter ‘M’, respectively. The following shows the list of detectable malfunctions: Power Malfunction Engine Synchronization Malfunction Timing Malfunction Position Malfunction Data Recording Malfunction Data Transfer Malfunction Once the Malfunctions indicator ‘M’ is tapped, a dialog will be displayed with a list of the detected malfunction events alongside a ‘Clear’ button for each event. Tapping the Clear button will clear out the detected malfunction event. | Certifying Statement of FMCSA Regulation Testing Budget Trucker was certified by the Budget Trucker testing team through successful execution and verification of the FMCSA ELD Test Procedures. Budget Trucker was installed on various types and sizes of Android & iOS phones and tablets. Testing was performed through the use of a J1939 simulator and actual vehicles while having been connected to the Geometris engine connected device. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the HOS web application (portal) that can be accessed through a web browser. | |
| Canada & US by Gorilla Safety | CUSGEOAN | 1.0 and Above | CAUS01 | Download | Download | Gorilla Fleet Safety, LLC | 844-636-1360 | info@gorillasafety.com | http://www.gorillasafety.com | 22327 Gosling Rd, Spring, TX 77379 | This ELD uses the web services and email method of transmission. Driver, from the "Dashboard" page of their ELD, will tap on "Roadside Inspection," then "Send Logs." Once they tap send logs, any annotation or note requested by the inspecting officer can be entered by the driver prior to sending. | The malfunctions supported are: Power Compliance Malfunction Engine Synchronization Malfunction Timing Compliance Malfunction Positioning Compliance Malfunction Data Recording Malfunction Data Transfer Malfunction Each of these malfunctions appears prominently for the user to understand the issue. When the user is presented with this, he is able to rectify the situation, contact the manufacturer or use paper logs, as provided as part of the instruction guide, to remain compliant. The malfunctions and malfunction codes can be found in the instruction guide with the required details in order for the driver to understand what he needs to do next. | The product has been thoroughly tested by both internal and external, third party, testers. Each requirement of the ELD has been either met or exceeded. The process of review and testing included the full review of the ruling, testing procedures and debugging of any blocker found in the software package. It further included the retesting by additional quality assurance professionals. Ultimately, the programing and hardware operate as intended and are in compliance. | |
| Canada & US by Gorilla Safety | CUSGEOAP | 1.0 and Above | CAUS02 | Download | Download | Gorilla Fleet Safety, LLC | 844-636-1360 | info@gorillasafety.com | http://www.gorillasafety.com | 22327 Gosling Rd, Spring, TX 77379 | This ELD uses the web services and email method of transmission. Driver, from the "Dashboard" page of their ELD, will tap on "Roadside Inspection," then "Send Logs." Once they tap send logs, any annotation or note requested by the inspecting officer can be entered by the driver prior to sending. | The malfunctions supported are: Power Compliance Malfunction Engine Synchronization Malfunction Timing Compliance Malfunction Positioning Compliance Malfunction Data Recording Malfunction Data Transfer Malfunction Each of these malfunctions appears prominently for the user to understand the issue. When the user is presented with this, he is able to rectify the situation, contact the manufacturer or use paper logs, as provided as part of the instruction guide, to remain compliant. The malfunctions and malfunction codes can be found in the instruction guide with the required details in order for the driver to understand what he needs to do next. | The product has been thoroughly tested by both internal and external, third party, testers. Each requirement of the ELD has been either met or exceeded. The process of review and testing included the full review of the ruling, testing procedures and debugging of any blocker found in the software package. It further included the retesting by additional quality assurance professionals. Ultimately, the programing and hardware operate as intended and are in compliance. | |
| CAPTAIN ELD | CPI | 2.14.31 or above | CPI682 | Download | Download | TRANS ATLANTIC GSV, INC. | (618) 556-3555 | info@captaineld.com | http://captaineld.com | 10011 NE 120th St. Kirkland, WA, 98034, Seatle / Washington / 98034 | Telematic (Web Service, Email) | CAPTAIN ELD is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | CAPTAIN ELD monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The CAPTAIN ELD Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on CAPTAIN ELD during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | CAPTAIN ELD meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. CAPTAIN ELD was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.14.31. |
| CarJack ELD | Blue Link | 3.0.6 | WLI001 | Download | Download | CarJack GPS | +5216643855155 | oficina@carjackgps.com | http://www.carjackgps.com | Calle Mision San Javier 10661-A Zona Rio Tijuana BC Mexico, Tijuana Baja California Mexico 22010 | When entering an inspection scenario, the driver follows the instructions provided on his printed one page manual which instructs the driver to press the "Officer Button" located on the top right of the DriverLog apps' home screen display. This will launch the Officer View. The officer view features a "Send" button and an Add comment button, which allows the officer to enter his identifier and send out the ELD data file through web services or email (both options are available). Following the guidance of the ELD section of the Federal Register...section "4.10.1. Data Transfer Mechanisms," we allow the officer to use both e-mail or Web Services to transfer the driver's data to the official FMCSA ELD e-mail address or the the FMCSA's Web Service repository. Currently the e-mail is formatted exactly to section "4.10.1.2. Wireless Data Transfer Through Email" specifications stated in the Federal Register. Web Services will utilize the SOAP protocol, per the FMCSA documentation, to transmit the ELD data file and the output file comment entered by the inspecting officer. | Each malfunction has been coded following the "Standard Coding for Required Compliance Malfunction and Data Diagnostic Event Detection" definitions regarding "Malfunction/Diagnostic Code", "Malfunction Description" and "Data Diagnostic Event." Power Compliance monitoring assures that the ELD will become fully functional within one minute of the engine on event and remain on as long as the vehicle's engine stays powered. Engine Synchronization monitoring determines our connection to the ECM. This alerts the driver if there is a loss of connectivity to the ECM. For Timing Compliance Monitoring, we periodically check UTC time via the internet. For Positioning Compliance the ELD records the location, and uses the last valid position measurement and includes the latitude and longitude coordinates and distance traveled in miles, since the last valid position measurement. We also measure the elapsed time during periods when the ELD does not require a valid position measurement within 5 miles. If the time exceeds 60 minutes in a 24 hour period, it is marked as a positioning compliance malfunction. An ELD monitors its storage capacity and integrity and detects data recording compliance malfunction if it can no longer record or retain required events or retrieve recorded logs that are not otherwise catalogued remotely by the motor carrier. The ELD monitors the completeness of the ELD event record information in relation to the required data elements for each event type and records a missing data elements data diagnostics event for the driver if any required field is missing at the time of recording. We check to make sure that our data transfer mechanism works properly at least once every 7 days. All Data Diagnostic events are handled similarly according to the mandate. | We certify that our ELD application and related hardware have been tested to meet the FMCSA's test procedures. | |
| CDL4LIFE ELD | CRS | 2.0 or higher | CRS216 | Download | Download | CDL 4 LIFE LLC | 833-235-5433 | cjeffers@cdl4life.com | http://cdl4life.com | 15502 Enid Dr, Austin, TX 78734 | CDL4LIFE ELD is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | CDL4LIFE ELD monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The CDL4LIFE ELD Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on CDL4LIFE ELD during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | CDL4LIFE ELD meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. CDL4LIFE ELD was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. 3. Let us know when the ELD Device Certification registration is submitted. 4. Provide us with “ELD Registration ID” when the ELD Device Certification registration is approved (may take several weeks) and we will add it to your ELD app. (To find the ELD Registration ID, go to your FMCSA account, click on “Manage Your Devices” and click on your registered ELD. | |
| CDSUS ELD | CRS | 2.0 or higher | CRS167 | Download | Download | CDSUS | 888-740-9070 | info@useld.com | http://www.useld.com | 7495 Tahoe Lake Ct Apt 101, Mason OH 45040 | CDSUS ELD is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | CDSUS ELD monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The CDSUS ELD Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on CDSUS ELD during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD | CDSUS ELD meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. CDSUS ELD was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| CellutrakELD | GEO81 | 1.0.1625.6584 | ELDTRK | Download | Download | Cellutrak Inc. | 888-901-8725 x 353 | eldsupport@cellutrak.ca | www.cellutrak.ca | 55 Louvain St. Suite 402, Montreal Quebec H2N 1A4 | https://drive.google.com/open?id=1EkA7-ARsFoNl7oDSRIzyq5ScttyWRYm4P0ZNgAm8u6g | https://drive.google.com/open?id=1ia0SFytgn22xOT0Agypes843JaRpM1aG1kNAk6XJ97Y | https://drive.google.com/open?id=10dKDN7MbJE_ccwNMdgPvHebBHh9f7X-knAmVyp0MRHQ | |
| Chamelogs | G01 | 1.0.95+ | CELD01 | Download | Download | Chameleon Innovation Technology | 18558888353 | support@chamelogs.com | http://chamelogs.com | 900 Turnbull Canyon Road Suite 102, City of Industry/CA/91745 | Telematic (Web Service, Email) | Step 1: Driver sign in to the ELD device. Step 2: Select Data transfer in the Menu. Step 3: Select method of transfer(could be Web Services or Email) in the drop down input box. Step 4: Enter Comment in the text box. Step 5: Press Transfer RODS button. Data Transfer Completed. | We followed the requirement that listing on section 4.6 ELD_Test_Plan_and_Procedures_All_Chapters_11_2_2016.pdf. Therefore we include the following error detection function in our product: “Power compliance” malfunction “Engine synchronization compliance” malfunction “Timing compliance” malfunction “Positioning compliance” malfunction “Data recording compliance” malfunction “Data transfer compliance” malfunction “Other” ELD detected malfunction and “Power data diagnostic” event “Engine synchronization data diagnostic” event “Missing required data elements data diagnostic” event “Data transfer data diagnostic” event “Unidentified driving records data diagnostic” event “Other” ELD identified diagnostic event | Chameleon Innovation Technology go thru all the test procedure listed in ELD_Test_Plan_and_Procedures_All_Chapters_11_2_2016.pdf. and passing all of them. |
| CI ELD LOGS | CILGS | 2.14.8 or higher | CRS270 | Download | Download | CV Options LLC | 4013883234 | info@connectedineld.com | http://connectedineld.com | 8 The Green, Suite #13879, Dover, DE, 19901 | Telematic (Web Service, Email) | CI ELD LOGS, or Electronic Logging Device, is a tool that offers a comprehensive overview of a driver's records during a roadside inspection. Not only does it provide this information within the app, but it also facilitates the transfer of telematics data through email or web services. The DOT Inspection mode allows the driver to choose the method that works best for them. To transfer ELD records through Web services, the driver needs to access the "DOT Inspection" menu and select the "Send Logs" option. Then, they should choose Web Service as the Data Transfer Type and click the "SEND" button. Similarly, to transfer ELD records via Email, the driver should follow the same steps but select Email as the Data Transfer Type before clicking the "SEND" button. | The CI ELD LOGS system ensures compliance with technical requirements, identifies malfunctions and data inconsistencies, and maintains records of such occurrences. Compliance malfunctions and diagnostic events are classified with specific codes, including P for "Power compliance" malfunction, E for "Engine synchronization compliance" malfunction, T for "Timing compliance" malfunction, L for "Positioning compliance" malfunction, R for "Data recording compliance" malfunction, S for "Data transfer compliance" malfunction, O for "Other" ELD-detected malfunctions, 1 for "Power data diagnostic" event, 2 for "Engine synchronization data diagnostic" event, 3 for "Missing required data elements data diagnostic" event, 4 for "Data transfer data diagnostic" event, 5 for "Unidentified driving records data diagnostic" event, and 6 for "Other" ELD-identified diagnostic events. The CI ELD LOGS Malfunction and Diagnostic Event Records document all malfunctions that occurred during the relevant time period. Active malfunctions are communicated to all drivers who may use the ELD. | CI ELD LOGS has been thoroughly tested to ensure compliance with all the functional requirements outlined in Title 49, Part 395 of Section 4.9.1, Appendix A, Subpart B. CI ELD LOGS can confidently certify that our ELD product adheres to all the necessary ELD regulations. |
| CLD | 0.1 | 0.0.62 | eldcld | Download | Download | Consolidated Bulk Carriers Corp | 631.232.7171 | info@consolidatedbulk.com | https://www.consolidatedbulk.com | 43 Windsor Place, Central Islip, New York 11722 | Telematic (Web Service, Email) | Our ELD system is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. Below are the steps for the both methods. Step 1: Click on "Data Transfer" button in the top bar (when you are on Dashboard page) Step 2: You are on "Data Transfer" page now. Authorized safety official may fill a key phrase or code in "Comment" input field during an inspection as specified in accordance with the section "4.3.2.5. Driver's Entry of an Output File Comment". Step 3: a) Click on "Send Email" button to initiate ELD data records output file generation and sending to a specific FMCSA email address. ELD data records output file generation for the current 24-hour period and the previous 7 consecutive days will take place on the supporting server. After generation this file will be automatically sent to the FMCSA email address. b) Or click on "Send Via Web Service" button to initiate ELD data records output file generation and sending to FMCSA via Web Services. ELD data records output file generation for the current 24-hour period and the previous 7 consecutive days will take place on the supporting server. After generation this file will be automatically sent to the FMCSA via Web Services. Step 4: After clicking any of the above mentioned buttons you will see a message indicating successful process initiation: "ELD Data Records output file generating has been initiated. It will be sent soon." | At Each instance when an ELD malfunction or data diagnostic event is detected or cleared by the ELD, the ELD records the event. The recorded malfunctions and data diagnostic events are inconsistencies found while monitoring the app/ELD against FMCSA compliance requirements. These instances are indicated in the application header with 2 icon indicators (Diagnostic and Malfunction). If an Diagnostic or Malfunction Event occurred appropriate indicator will become red and Record will be created and saved in ELD. To know more info about the event occured, click on the red indicator and it will show popup with the event message. If event has been cleared by the ELD indicator it will then go back to a normal state. Here is the list of messages and codes for Diagnostic and Malfunction Events: Malfunction Events (Code - Description) P - “Power compliance” malfunction E - “Engine synchronization compliance” malfunction T - “Timing compliance” malfunction L - “Positioning compliance” malfunction R - “Data recording compliance” malfunction S - “Data transfer compliance” malfunction O - “Other” ELD detected malfunction Diagnostiс Events (Code - Description) 1 - “Power data diagnostic” event 2 - “Engine synchronization data diagnostic” event 3 - “Missing required data elements data diagnostic” event 4 - “Data transfer data diagnostic” event 5 - “Unidentified driving records data diagnostic” event 6 - “Other” ELD identified diagnostic event | Malfunctions during our first round of testing included the automation of Driving and On Duty status not working. We also experienced a few issues where drivers were not presented with on screen notifications. These malfunctions were fixed during our testing and certification process. |
| CloudELD | SmartTab | 1.0.00 | ETSELD | Download | Download | LiRCTek Inc | (916) 945-2894 | support@cloudeld.com | http://www.cloudeld.com | 2150 HANNAH WAY, ROCKLIN CA 95765 | Our product supports wireless transfer through web services and email. Instructions: 1. Click on top left menu. 2. Tap on DOT Inspection mode 3. Click on Data Transfer icon on top right corner 4. Click on Email or Web services tab. 5. Enter the comment 6. Click on Send button. | The ELD System support to monitor all the compliance of FMCSA for various detectable malfunctions and data diagnostic events. Power (P) - Device lost power during driving events for a total of 30 min or more, over a 24-hour period. Engine Synchronization (E) - Device lost connection to the ECM for a total of more than 30 min during a 24-hour period. Timing (T) - Device is not able to synchronize to UTC. Positioning (L) - Device is not able to acquire a valid position measurement within 5 miles of vehicle movement for a total of more than 60 min over a 24 hour period. Data recording (R) - Device is no longer able to record or retain required event data or retrieve locally-stored recorded logs. Data transfer (S) - Device continues to fail checks of the roadside transfer mechanism for three days following a Data Transfer Diagnostic Event. Other ELD detected (O) - If application has stopped working or is not responding as expected. On Home Screen top right corner if any malfunction occurs in the device icon with circle M appears and similar way if any data diagnostic events occurs icon with circle D appears. | LiRCTek certifies that tested all the Test Plans and Procedures provided by FMCSA and compliant with FMCSA safety regulations 49 CFR part 395, subpart B, appendix A. We have done testing our devices in-house and also on few fleets on the road. | |
| CloudELD | Tab7 | 9.0.03 | ESTAB7 | Download | Download | LiRCTek Inc | (916) 945-2894 | support@cloudeld.com | http://www.cloudeld.com | 2150 HANNAH WAY, ROCKLIN CA 95765 | Telematic (Web Service, Email) | Our product supports wireless transfer through web services and email. Instructions: 1. Click on top left menu. 2. Tap on DOT Inspection mode 3. Click on Data Transfer icon on top right corner 4. Click on Email or Web services tab. 5. Enter the comment 6. Click on Send button. | The ELD System support to monitor all the compliance of FMCSA for various detectable malfunctions and data diagnostic events. Power (P) - Device lost power during driving events for a total of 30 min or more, over a 24-hour period. Engine Synchronization (E) - Device lost connection to the ECM for a total of more than 30 min during a 24-hour period. Timing (T) - Device is not able to synchronize to UTC. Positioning (L) - Device is not able to acquire a valid position measurement within 5 miles of vehicle movement for a total of more than 60 min over a 24 hour period. Data recording (R) - Device is no longer able to record or retain required event data or retrieve locally-stored recorded logs. Data transfer (S) - Device continues to fail checks of the roadside transfer mechanism for three days following a Data Transfer Diagnostic Event. Other ELD detected (O) - If application has stopped working or is not responding as expected. On Home Screen top right corner if any malfunction occurs in the device icon with circle M appears and similar way if any data diagnostic events occurs icon with circle D appears. | LiRCTek certifies that tested all the Test Plans and Procedures provided by FMCSA and compliant with FMCSA safety regulations 49 CFR part 395, subpart B, appendix A. We have done testing our devices in-house and also on few fleets on the road. |
| CloudELD | BLE1 | 1.4 | ESBLE1 | Download | Download | LiRCTek Inc | (916) 945-2894 | support@cloudeld.com | http://www.cloudeld.com | 2150 HANNAH WAY, ROCKLIN CA 95765 | Telematic (Web Service, Email) | Our product supports wireless transfer through web services and email. Instructions: 1. Click on top left menu. 2. Tap on DOT Inspection mode 3. Click on Data Transfer icon on top right corner 4. Click on Email or Web services tab. 5. Enter the comment 6. Click on Send button. | The ELD System support to monitor all the compliance of FMCSA for various detectable malfunctions and data diagnostic events. Power (P) - Device lost power during driving events for a total of 30 min or more, over a 24-hour period. Engine Synchronization (E) - Device lost connection to the ECM for a total of more than 30 min during a 24-hour period. Timing (T) - Device is not able to synchronize to UTC. Positioning (L) - Device is not able to acquire a valid position measurement within 5 miles of vehicle movement for a total of more than 60 min over a 24 hour period. Data recording (R) - Device is no longer able to record or retain required event data or retrieve locally-stored recorded logs. Data transfer (S) - Device continues to fail checks of the roadside transfer mechanism for three days following a Data Transfer Diagnostic Event. Other ELD detected (O) - If application has stopped working or is not responding as expected. On Home Screen top right corner if any malfunction occurs in the device icon with circle M appears and similar way if any data diagnostic events occurs icon with circle D appears. | LiRCTek certifies that tested all the Test Plans and Procedures provided by FMCSA and compliant with FMCSA safety regulations 49 CFR part 395, subpart B, appendix A. We have done testing our devices in-house and also on few fleets on the road. |
| CloudHawk ELD | CELD01 | 3.0.2116.210920 | CELD01 | Download | Download | Spark Technology Labs Inc. | 1-888-472-3255 | info@cloudhawk.com | www.cloudhawk.com | 680-D Davenport Rd., Waterloo, ON N2V 2C3 | The CloudHawk ELD provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. This can be done by selecting the Roadside Inspection button from the main HOS dashboard and selecting the option for Data Transfer. A list of supported data transfer options is then displayed which include Bluetooth, Email and USB. A Select Vehicle option is also available for selecting a vehicle upon performing the data transfer, this option enables the CloudHawk ELD to produce a data file or a series of data files of ELD records for a subset of its vehicles used by the driver. - Transfer via Bluetooth - this option enables the user to transfer files through Bluetooth. The ELD prompts for an output file comment which the driver may enter (optional). After the input, if Bluetooth is not yet turned on, a prompt will appear asking you to turn it on. You will then be asked to select the device name to which the data will be transmitted via Bluetooth. - Transfer via Email - this option enables the user to transfer files through email. The ELD output file transferred is encrypted using AES-256 in FIPS Publication 197. Before sending, the ELD prompts for an output file comment which the driver may enter (optional). The device's default email application will then be opened before sending the email to which the data will be transferred. - Transfer via USB - this option enables the user to transfer files through USB (external devices). However, prior to saving the driver’s ELD file to an external storage/device, the ELD re-authenticates the driver account by asking for its password. | The CloudHawk ELD is capable of monitoring its compliance for various detectable malfunctions. At each instance when an ELD malfunction event is detected or cleared by the CloudHawk ELD, the ELD records the event. The recorded malfunction events are inconsistencies found while monitoring the ELD against FMCSA compliance requirements. Malfunction occurrences are indicated in the application header and in the Android notification toolbar with the letter ‘M’, respectively. The following shows the list of detectable malfunctions: - Power Malfunction - Engine Synchronization Malfunction - Timing Malfunction - Position Malfunction - Data Recording Malfunction - Data Transfer Malfunction Once the Malfunctions indicator ‘M’ is tapped, a dialog will be displayed with a list of the detected malfunction events alongside a ‘Clear’ button for each event. Tapping the Clear button will clear out the detected malfunction event. | The CloudHawk ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The CloudHawkELD was installed on various types and sizes of Android phones and tablets. Testing was performed through the use of a J1939 simulator and actual vehicles while having been connected to the Geometris whereQube engine connected devices. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the Hours of Service web application (portal) that can be accessed through a web browser. | |
| Club ELD / Android | PT30 | 1.0.01 | 01CLUB | Download | Download | Club ELD | 16159005551 | clubeldprovider@gmail.com | http://clubeld.com | 899 Easthagan Dr , Nashville, TN 37217 USA | Telematic (Web Service, Email) | When you need to transfer your ELD records to authorized Safety Officials, you need to open an additional menu (Click on the button with three horizontal lines in the left top corner of the app's screen) and choose the "DOT Inspect" menu. The DOT Inspection menu provides summaries of all the collected data regarding a driver, truck, and trip. You may also use this menu to transfer the data to FMCSA during the DOT inspection, certify your logs, or view unidentified records. Tap the Start Inspection button and check if your logs are ready to be transferred to the safety officials. If everything is OK, tap the Transfer Data to the Roadside Inspector button and choose the method of sending your logs: send it to the Web Services (FMCSA); send it to the FMCSA email; send it to the personal email (provided by the inspector). If you select “personal email”, you need to enter the recipient's address and add a comment. If you select “Web Services (FMCSA)” or “Email to FMCSA” you need to add a comment. The reporting period will vary depending on the rules of the country in which you operate. | If there are any malfunctions or data diagnostic issues detected, the M/D icon at the top of the app screen will change its color from green to red. The red M letter will signal a malfunction, and the red D letter will indicate a data inconsistency. Malfunctions and Data Diagnostic can also be displayed in the Logs menu as Malfunction event or Data Diagnostic event. As for the Malfunctions you can notice such types of issues: Engine Synchronization Positioning compliance Data recording compliance Unregistered odometer change Timing compliance Power compliance As for the Data Diagnostics problem you can notice such types of issues: Engine synchronization Missing data elements Unidentified driving records Data transfer Power data diagnostic To learn more about the problem you are facing, tap the M/D icon at the top of the app screen and check the details. | The Club ELD Android Application was certified through successful execution and verification of the FMCSA ELD Test Procedures. The application was installed on various models of Android mobile devices. The testing was performed using a simulator as well as actual motor vehicles. |
| Club ELD / iOS | PT30 | 1.01.01 | 01CLUB | Download | Download | Club ELD | 16159005551 | clubeldprovider@gmail.com | http://clubeld.com | 899 Easthagan Dr , Nashville, TN 37217 USA | Telematic (Web Service, Email) | When you need to transfer your ELD records to authorized Safety Officials, you need to open an additional menu (Click on the button with three horizontal lines in the left top corner of the app's screen) and choose the "DOT Inspect" menu. The DOT Inspection menu provides summaries of all the collected data regarding a driver, truck, and trip. You may also use this menu to transfer the data to FMCSA during the DOT inspection, certify your logs, or view unidentified records. Tap the Start Inspection button and check if your logs are ready to be transferred to the safety officials. If everything is OK, tap the Transfer Data to the Roadside Inspector button and choose the method of sending your logs: send it to the Web Services (FMCSA); send it to the FMCSA email; send it to the personal email (provided by the inspector). If you select “personal email”, you need to enter the recipient's address and add a comment. If you select “Web Services (FMCSA)” or “Email to FMCSA” you need to add a comment. The reporting period will vary depending on the rules of the country in which you operate. | If there are any malfunctions or data diagnostic issues detected, the M/D icon at the top of the app screen will change its color from green to red. The red M letter will signal a malfunction, and the red D letter will indicate a data inconsistency. Malfunctions and Data Diagnostic can also be displayed in the Logs menu as Malfunction event or Data Diagnostic event. As for the Malfunctions you can notice such types of issues: Engine Synchronization Positioning compliance Data recording compliance Unregistered odometer change Timing compliance Power compliance As for the Data Diagnostics problem you can notice such types of issues: Engine synchronization Missing data elements Unidentified driving records Data transfer Power data diagnostic To learn more about the problem you are facing, tap the M/D icon at the top of the app screen and check the details. | The Club ELD iOS Application was certified through successful execution and verification of the FMCSA ELD Test Procedures. The application was installed on various models of iOS-operated mobile devices. The testing was performed using a simulator as well as actual motor vehicles. |
| ClutchELD | Android and ioSIX | 1.0 and Above | CELD03 | Download | Download | ClutchELD | 800-402-58824 | info@clutcheld.com | http://clutcheld.com | 22325 Gosling RD, Spring/TX/77373 | To send logs at roadside a driver must: 1. Start on the main dashboard. 2. Select "Roadside Inspection" from about the middle of the screen. 3. Select "Send Logs to DOT." 4. Type in the notation requested by the inspecting officer. 5. Select "Send." This will send logs using both Wireless Web Services and Email (option 1 as stated in the ELD mandate regarding roadside data transfer). | The malfunctions supported are: Power Compliance Malfunction Engine Synchronization Malfunction Timing Compliance Malfunction Positioning Compliance Malfunction Data Recording Malfunction Data Transfer Malfunction Each of these malfunctions appears prominently for the user to understand the issue. When the user is presented with this, he is able to rectify the situation, contact the manufacturer or use paper logs, as provided as part of the instruction guide, to remain compliant. The malfunctions and malfunction codes can be found in the instruction guide with the required details in order for the driver to understand what he needs to do next. | The product has been thoroughly tested by both internal and external, third party, testers. Each requirement of the ELD has been either met or exceeded. The process of review and testing included the full review of the ruling, testing procedures and debugging of any blocker found in the software package. It further included the retesting by additional quality assurance professionals. Ultimately, the programing and hardware operate as intended and are in compliance. | |
| ClutchELD | iOS and ioSIX | 1.0 and Above | CELD04 | Download | Download | ClutchELD | 800-402-58824 | info@clutcheld.com | http://clutcheld.com | 22325 Gosling RD, Spring/TX/77373 | To send logs at roadside a driver must: 1. Start on the main dashboard. 2. Select "Roadside Inspection" from about the middle of the screen. 3. Select "Send Logs to DOT." 4. Type in the notation requested by the inspecting officer. 5. Select "Send." This will send logs using both Wireless Web Services and Email (option 1 as stated in the ELD mandate regarding roadside data transfer). | The malfunctions supported are: Power Compliance Malfunction Engine Synchronization Malfunction Timing Compliance Malfunction Positioning Compliance Malfunction Data Recording Malfunction Data Transfer Malfunction Each of these malfunctions appears prominently for the user to understand the issue. When the user is presented with this, he is able to rectify the situation, contact the manufacturer or use paper logs, as provided as part of the instruction guide, to remain compliant. The malfunctions and malfunction codes can be found in the instruction guide with the required details in order for the driver to understand what he needs to do next. | The product has been thoroughly tested by both internal and external, third party, testers. Each requirement of the ELD has been either met or exceeded. The process of review and testing included the full review of the ruling, testing procedures and debugging of any blocker found in the software package. It further included the retesting by additional quality assurance professionals. Ultimately, the programing and hardware operate as intended and are in compliance. | |
| ClutchELD | Android and Pacific Track | 1.0 and Above | CELD01 | Download | Download | ClutchELD | 800-402-58824 | info@clutcheld.com | http://clutcheld.com | 22325 Gosling RD, Spring/TX/77373 | To send logs at roadside a driver must: 1. Start on the main dashboard. 2. Select "Roadside Inspection" from about the middle of the screen. 3. Select "Send Logs to DOT." 4. Type in the notation requested by the inspecting officer. 5. Select "Send." This will send logs using both Wireless Web Services and Email (option 1 as stated in the ELD mandate regarding roadside data transfer). | The malfunctions supported are: Power Compliance Malfunction Engine Synchronization Malfunction Timing Compliance Malfunction Positioning Compliance Malfunction Data Recording Malfunction Data Transfer Malfunction Each of these malfunctions appears prominently for the user to understand the issue. When the user is presented with this, he is able to rectify the situation, contact the manufacturer or use paper logs, as provided as part of the instruction guide, to remain compliant. The malfunctions and malfunction codes can be found in the instruction guide with the required details in order for the driver to understand what he needs to do next. | The product has been thoroughly tested by both internal and external, third party, testers. Each requirement of the ELD has been either met or exceeded. The process of review and testing included the full review of the ruling, testing procedures and debugging of any blocker found in the software package. It further included the retesting by additional quality assurance professionals. Ultimately, the programing and hardware operate as intended and are in compliance. | |
| ClutchELD | iOS and Pacific Track | 1.0 and Above | CELD02 | Download | Download | ClutchELD | 800-402-58824 | info@clutcheld.com | http://clutcheld.com | 22325 Gosling RD, Spring/TX/77373 | To send logs at roadside a driver must: 1. Start on the main dashboard. 2. Select "Roadside Inspection" from about the middle of the screen. 3. Select "Send Logs to DOT." 4. Type in the notation requested by the inspecting officer. 5. Select "Send." This will send logs using both Wireless Web Services and Email (option 1 as stated in the ELD mandate regarding roadside data transfer). | The malfunctions supported are: Power Compliance Malfunction Engine Synchronization Malfunction Timing Compliance Malfunction Positioning Compliance Malfunction Data Recording Malfunction Data Transfer Malfunction Each of these malfunctions appears prominently for the user to understand the issue. When the user is presented with this, he is able to rectify the situation, contact the manufacturer or use paper logs, as provided as part of the instruction guide, to remain compliant. The malfunctions and malfunction codes can be found in the instruction guide with the required details in order for the driver to understand what he needs to do next. | The product has been thoroughly tested by both internal and external, third party, testers. Each requirement of the ELD has been either met or exceeded. The process of review and testing included the full review of the ruling, testing procedures and debugging of any blocker found in the software package. It further included the retesting by additional quality assurance professionals. Ultimately, the programing and hardware operate as intended and are in compliance. | |
| CMG ELD | CRS | 2.0 or higher | CRS204 | Download | Download | Cargo Management Group Inc | 916-666-7647 | eldcmg@gmail.com | http://cmgeld.com | 2007 Opportunity Dr STE 6, Roseville, CA 95678, Roseville, CA 95678 | CMG ELD is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | CMG ELD monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The CMG ELD Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on CMG ELD during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | CMG ELD meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. CMG ELD was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| CN ELD | CNCTNOW | 2.23-18 and above | CRS235 | Download | Download | ELD CONNECTION | (323)986-6668 | info@eldconnection.com | 2000 Center Dr, Hoffman Estates/IL/60192 | Telematic (Web Service, Email) | As per Title 49, Part 395 of Section 4.9.1, Appendix A, Subpart B of the CFR, drivers using the CN ELD system can transfer log data via telematics methods. Drivers can also produce a report on their mobile display or send log data via web services or email if an officer requests to review them. | As per Appendix A, section 4.6, the CN ELD system continuously checks for any malfunctions or diagnostic events, including issues with data recording, data transfer, required data elements, power, engine synchronization, timing, positioning, and unidentified driving. Drivers will be alerted of any malfunction through a visual alert. | CN ELD product has undergone testing in accordance with the FMCSA's testing procedures. CN ELD certifies that the hardware unit and mobile application together form a compliant electronic logging system. Testing results confirm that hours of service data is accurately logged and transmitted and that it meets the functional requirements of 49 CFR Part 395 Subpart B. | |
| COLIBRI ELD | CLBR | 2.22.06 and later | CLB892 | Download | Download | COLIBRI ELD LLC | 331-255-1894 | info@colibrield.com | http://colibrield.com | 3030 WARRENVILLE ROAD, STE 450-10, Lisle, IL 60532 | Telematic (Web Service, Email) | COLIBRI ELD system allows drivers to transfer log data through telematics methods in compliance with the regulations outlined in Title 49, Part 395, Section 4.9.1, Appendix A, Subpart B of the CFR. Drivers can also produce a report on their mobile display or transfer log data through web services or email if requested by an officer. To transfer ELD records through Web services, the driver needs to access the "DOT Inspection" menu and select the "Send Logs" option. Then, they should choose Web Service as the Data Transfer Type and click the "SEND" button. Similarly, to transfer ELD records via Email, the driver should follow the same steps but select Email as the Data Transfer Type before clicking the "SEND" button. | As per the regulations outlined in Appendix A, section 4.6, the COLIBRI ELD system continuously monitors itself for malfunctions. If a malfunction or diagnostic event occurs, such as issues with data recording, data transfer, or power, COLIBRI ELD system will display a visual alert to the driver. This includes alerts for any issues with engine synchronization, timing, positioning, or unidentified driving. Compliance malfunctions and diagnostic events are classified with specific codes, including P for "Power compliance" malfunction, E for "Engine synchronization compliance" malfunction, T for "Timing compliance" malfunction, L for "Positioning compliance" malfunction, R for "Data recording compliance" malfunction, S for "Data transfer compliance" malfunction, O for "Other" ELD-detected malfunctions, 1 for "Power data diagnostic" event, 2 for "Engine synchronization data diagnostic" event, 3 for "Missing required data elements data diagnostic" event, 4 for "Data transfer data diagnostic" event, 5 for "Unidentified driving records data diagnostic" event, and 6 for "Other" ELD-identified diagnostic events. | As per the FMCSA's testing procedures, COLIBRI ELD has undergone thorough testing to ensure compliance as an electronic logging system. COLIBRI ELD can confirm that the system meets the requirements of 49 CFR Part 395 Subpart B, including the correct logging and transmission of hours of service data. |
| COMFORT ELD | CRS | 2.0 or higher | CRS144 | Download | Download | Comfort ELD | 7737629892 | comforteld2020@gmail.com | http://www.comforteld.online | 6400 W Berteaue ave , Chicago IL 60634 | COMFORT ELD is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | COMFORT ELD monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The COMFORT ELD Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on COMFORT ELD during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | COMFORT ELD meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. COMFORT ELD was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| Command Alkon TFleet TFVG850 | TFVG850 | v6.0.1A | TFM001 | Download | Download | Command Alkon Inc. | 205-879-3282 | 5csalesteamall@commandalkon.com | http://www.commandalkon.com/ | 1800 international Park Drive, Suite 400, Birmingham, AL 35243 | The system will transfer the data using either email or web services, the officer may select either option. Detailed Steps: • The Driver or Official will select the Options dropdown button on the driver overview screen and select the Roadside Inspection option from that drop down. • This will navigate the user to a Logs Grid page that contains a button labeled Transmit ELD Data File. • The Officer taps on the Transmit Data File button. • A dialog will appear allowing the officer to choose between Wireless Web Service or Email and a space will be made available for the officer’s code. • The system will use the pre-defined email or webservice address to send the file to the FMCSA site. | P (Power) - Device lost power during driving events for a total of 30 min or more over a 24-hour period. E (Engine synchronization) - Device lost connection to the ECM (or other data source) for a total of more than 30 min during a 24-hour period. T (Timing) - Device is not able to synchronize to UTC. L (Positioning) - Device is not able to acquire a valid position measurement within 5 mi of vehicle movement for a total of more than 60 min over a 24-hour period. R (Data recording) - Device is no longer able to record or retain required event data or retrieve locally stored recorded logs. S (Data transfer) - Device continues to fail checks of the roadside transfer mechanism for three days following a Data Transfer Diagnostic Event. O (Other ELD detected) - The Command Alkon Incorporated’s TFleet HoS application has stopped working or is not responding as expected. | Command Alkon Incorporated certifies, based on our completion of the testing procedures provided by the FMCSA in the Electronic Logging Device Test Plan and Procedures document version 2.0 dated 10/17/2016, that Command Alkon Incorporated’s TFleet HoS complies with all Federal Motor Carrier Safety Administration (FMCSA) specifications as found in 49 CFR Part 395 for Electronic Logging Devices, Subpart B.Devices, Subpart B. | |
| Command Alkon TFleet TFVG950 | TFVG950 | v6.0.1A | TFM002 | Download | Download | Command Alkon Inc. | 205-879-3282 | 5csalesteamall@commandalkon.com | http://www.commandalkon.com/ | 1800 international Park Drive, Suite 400, Birmingham, AL 35243 | The system will transfer the data using either email or web services, the officer may select either option. Detailed Steps: • The Driver or Official will select the Options dropdown button on the driver overview screen and select the Roadside Inspection option from that drop down. • This will navigate the user to a Logs Grid page that contains a button labeled Transmit ELD Data File. • The Officer taps on the Transmit Data File button. • A dialog will appear allowing the officer to choose between Wireless Web Service or Email and a space will be made available for the officer’s code. • The system will use the pre-defined email or webservice address to send the file to the FMCSA site. | P (Power) - Device lost power during driving events for a total of 30 min or more over a 24-hour period. E (Engine synchronization) - Device lost connection to the ECM (or other data source) for a total of more than 30 min during a 24-hour period. T (Timing) - Device is not able to synchronize to UTC. L (Positioning) - Device is not able to acquire a valid position measurement within 5 mi of vehicle movement for a total of more than 60 min over a 24-hour period. R (Data recording) - Device is no longer able to record or retain required event data or retrieve locally stored recorded logs. S (Data transfer) - Device continues to fail checks of the roadside transfer mechanism for three days following a Data Transfer Diagnostic Event. O (Other ELD detected) - The Command Alkon Incorporated’s TFleet HoS application has stopped working or is not responding as expected. | Command Alkon Incorporated certifies, based on our completion of the testing procedures provided by the FMCSA in the Electronic Logging Device Test Plan and Procedures document version 2.0 dated 10/17/2016, that Command Alkon Incorporated’s TFleet HoS complies with all Federal Motor Carrier Safety Administration (FMCSA) specifications as found in 49 CFR Part 395 for Electronic Logging Devices, Subpart B.Devices, Subpart B. | |
| Command Alkon Trackit | CATT01 | 1.0 and Above | CATT01 | Download | Download | Gorilla Fleet Safety, LLC | 844-636-1360 | info@gorillasafety.com | http://www.gorillasafety.com | 22327 Gosling Rd, Spring, TX 77379 | Telematic (Web Service, Email) | This ELD uses the web services and email method of transmission. Driver, from the "Dashboard" page of their ELD, will tap on "Roadside Inspection," then "Send Logs." Once they tap send logs, any annotation or note requested by the inspecting officer can be entered by the driver prior to sending. | The malfunctions supported are: Power Compliance Malfunction Engine Synchronization Malfunction Timing Compliance Malfunction Positioning Compliance Malfunction Data Recording Malfunction Data Transfer Malfunction Each of these malfunctions appears prominently for the user to understand the issue. When the user is presented with this, he is able to rectify the situation, contact the manufacturer or use paper logs, as provided as part of the instruction guide, to remain compliant. The malfunctions and malfunction codes can be found in the instruction guide with the required details in order for the driver to understand what he needs to do next. | The product has been thoroughly tested by both internal and external, third party, testers. Each requirement of the ELD has been either met or exceeded. The process of review and testing included the full review of the ruling, testing procedures and debugging of any blocker found in the software package. It further included the retesting by additional quality assurance professionals. Ultimately, the programing and hardware operate as intended and are in compliance. |
| CommandGPS ELD | AGCM01 | 1.4.72 or higher | AGCM01 | Download | Download | Linxup | 314 732 4925 Option 1 for Sales | sales@agilissystems.com | http://www.agilissystems.com/ | 424 S Woods Mill Rd STE 210, Chesterfield/ MO/ 63017 | We have chosen to use wireless web services and email as our choice for the ELD output file. - Driver or Official will tap on "Logs" from the Driver Overview screen. - Tap on Events/Grid button to toggle between the grid view and a line-by line detail view. -Driver or Official will use the Options button on the driver overview screen -Driver or Official will use the Roadside Inspection button on the drop down -This button will navigate the user to a Logs Grid page -The Logs Grid Page will contain a button labeled “Transmit ELD Data File” -This button will be disabled until the FMCSA has released the URL to send the data file | The CommandGPS ELD system continuously monitors for all appropriate malfunctions as specified in Appendix A section 4.6. It supports detection of all malfunctions and diagnostic events specified by the ELD mandate, including: power, engine synchronization, timing, positioning, data recording, data transfer, required data elements, and unidentified driving. When a malfunction is detected, it is reported as required in ELD data file(s) and visually indicated on the ELD system as required by 4.6.2.1. | Agilis Systems certifies that CommandGPS-ELD based on our completion of the testing procedures provided by the FMCSA in the Electronic Logging Device Test Plan and Procedures document version 2.0 dated 10/17/2016 that AGCM01 and complies with all Federal Motor Carrier Safety Administration (FMCSA) specifications as found in 49 CFR Part 395 for Electronic Logging Devices, Subpart B. Devices, SubpartB. | |
| Companion | TD4230 | 1.1 | TD0001 | Download | Download | Trip Data & Safety Management Inc. | 506-853-7522 | sales@tdsm.com | http://www.tdsm.com/aspx_docs/electronic_logs.aspx | 383 Baig Blvd, Moncton | Screen View - Our devices are detachable and can be passed out of the truck. eMail - Transfer data via email to officials. The user will be prompted to enter officials email address. 4.9.1 (1)(ii) USB - Transfer data via USB device. 4.9.1 (2)(i) Bluetooth – Transfer data via Bluetooth to officials. The user will be prompted to enter a code given to them by the officer. 4.9.1 (2)(ii) | Engine synchronization Timing compliance Positioning compliance Data recording compliance Data transfer compliance Cellular Radio validation GPS Radio validation | 4 testers processing chapters 1-3 of FMCSA testing documents. All test elements in a chapter must pass before moving onto the next chapter. There are currently 2 failures within the test documents, but we are working with FMCSA to resolve these issues. 1. We can not test our exports. The FMCSA test for exported data currently crashes. 2. In the test documents for exempt drivers a. Section 4.3.3.1.2-1(c) states that data should not be saved for exempt drivers. b. Section 4.3.3.1.2-3(c) states that data should be saved for exempt drivers. | |
| Compliance Now | Android & Geometris | 1.0.1905.190710 | GEO001 | Download | Download | Geosavi Inc. https://geosavi.com | 1-800-261-4361 | support@geosavi.com | https://geosavi.com | 8230 E Broadway Blvd. Ste. E9B, Tucson, AZ 85750 | Data Transfer The Compliance Now provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. Selecting the Data Transfer button from the Main HOS Main Screen will display the list of supported data transfer options which are via Bluetooth, Email and USB. A Select Vehicle option is also available for selecting a vehicle upon performing the data transfer, this option enables the Compliance Now to produce a data file or a series of data files of ELD records for a subset of its vehicles used by the driver. * Transfer via Bluetooth - this option enables the user to transfer files through Bluetooth. The ELD prompts for an output file comment which the driver may enter (optional). After the input, if Bluetooth is not yet turned on, a prompt will appear asking you to turn it on. You will then be asked to select the device name to which the data will be transmitted via Bluetooth. * Transfer via Email - this option enables the user to transfer files through email. The ELD output file transferred is encrypted using AES-256 in FIPS Publication 197. Before sending, the ELD prompts for an output file comment which the driver may enter (optional). The device's default email application will then be opened before sending the email to which the data will be transferred. * Transfer via USB - this option enables the user to transfer files through USB (external devices). However, prior to saving the driver’s ELD file to an external storage/device, the ELD re-authenticates the driver account by asking for its password. | Malfunctions The Compliance Now ELD is capable of monitoring its compliance for various detectable malfunctions. At each instance when an ELD malfunction event is detected or cleared by the Compliance Now ELD, the ELD records the event. The recorded malfunction events are inconsistencies found while monitoring the ELD against FMCSA compliance requirements. Malfunction occurrences are indicated in the application header and in the Android notification toolbar with the letter ‘M’, respectively. The following shows the list of detectable malfunctions: ? Power Malfunction ? Engine Synchronization Malfunction ? Timing Malfunction ? Position Malfunction ? Data Recording Malfunction ? Data Transfer Malfunction Once the Malfunctions indicator ‘M’ is tapped, a dialog will be displayed with a list of the detected malfunction events alongside a ‘Clear’ button for each event. Tapping the Clear button will clear out the detected malfunction event. | Certifying Statement of FMCSA Regulation Testing The Compliance Now ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The Compliance Now ELD was installed on various types and sizes of Android phones and tablets. Testing was performed through the use of a J1939 simulator and actual vehicles while having been connected to the VBUS with Geometris & Calamp4230 connected devices. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the Hours of Service web application (portal) that can be accessed through a web browser. | |
| Compliance Now | Android & Pacific Tracks | 1.0.1905.190710 | GEO001 | Download | Download | Geosavi Inc. https://geosavi.com | 1-800-261-4361 | support@geosavi.com | https://geosavi.com | 8230 E Broadway Blvd. Ste. E9B, Tucson, AZ 85750 | Data Transfer The Compliance Now provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. Selecting the Data Transfer button from the Main HOS Main Screen will display the list of supported data transfer options which are via Bluetooth, Email and USB. A Select Vehicle option is also available for selecting a vehicle upon performing the data transfer, this option enables the Compliance Now to produce a data file or a series of data files of ELD records for a subset of its vehicles used by the driver. * Transfer via Bluetooth - this option enables the user to transfer files through Bluetooth. The ELD prompts for an output file comment which the driver may enter (optional). After the input, if Bluetooth is not yet turned on, a prompt will appear asking you to turn it on. You will then be asked to select the device name to which the data will be transmitted via Bluetooth. * Transfer via Email - this option enables the user to transfer files through email. The ELD output file transferred is encrypted using AES-256 in FIPS Publication 197. Before sending, the ELD prompts for an output file comment which the driver may enter (optional). The device's default email application will then be opened before sending the email to which the data will be transferred. * Transfer via USB - this option enables the user to transfer files through USB (external devices). However, prior to saving the driver’s ELD file to an external storage/device, the ELD re-authenticates the driver account by asking for its password. | Malfunctions The Compliance Now ELD is capable of monitoring its compliance for various detectable malfunctions. At each instance when an ELD malfunction event is detected or cleared by the Compliance Now ELD, the ELD records the event. The recorded malfunction events are inconsistencies found while monitoring the ELD against FMCSA compliance requirements. Malfunction occurrences are indicated in the application header and in the Android notification toolbar with the letter ‘M’, respectively. The following shows the list of detectable malfunctions: ¿ Power Malfunction ¿ Engine Synchronization Malfunction ¿ Timing Malfunction ¿ Position Malfunction ¿ Data Recording Malfunction ¿ Data Transfer Malfunction Once the Malfunctions indicator ‘M’ is tapped, a dialog will be displayed with a list of the detected malfunction events alongside a ‘Clear’ button for each event. Tapping the Clear button will clear out the detected malfunction event. | Certifying Statement of FMCSA Regulation Testing The Compliance Now ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The Compliance Now ELD was installed on various types and sizes of Android phones and tablets. Testing was performed through the use of a J1939 simulator and actual vehicles while having been connected to the VBUS with Geometris , Calamp4230 & Pacific Tracks connected devices. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the Hours of Service web application (portal) that can be accessed through a web browser. | |
| Compliance Now | iOS & Pacific Tracks | 1905.190710 | GEO001 | Download | Download | Geosavi Inc. https://geosavi.com | 1-800-261-4361 | support@geosavi.com | https://geosavi.com | 8230 E Broadway Blvd. Ste. E9B, Tucson, AZ 85750 | Data Transfer The Compliance Now provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. Selecting the Data Transfer button from the Main HOS Main Screen will display the list of supported data transfer options which are via Bluetooth, Email and USB. A Select Vehicle option is also available for selecting a vehicle upon performing the data transfer, this option enables the Compliance Now to produce a data file or a series of data files of ELD records for a subset of its vehicles used by the driver. * Transfer via Bluetooth - this option enables the user to transfer files through Bluetooth. The ELD prompts for an output file comment which the driver may enter (optional). After the input, if Bluetooth is not yet turned on, a prompt will appear asking you to turn it on. You will then be asked to select the device name to which the data will be transmitted via Bluetooth. * Transfer via Email - this option enables the user to transfer files through email. The ELD output file transferred is encrypted using AES-256 in FIPS Publication 197. Before sending, the ELD prompts for an output file comment which the driver may enter (optional). The device's default email application will then be opened before sending the email to which the data will be transferred. * Transfer via USB - this option enables the user to transfer files through USB (external devices). However, prior to saving the driver’s ELD file to an external storage/device, the ELD re-authenticates the driver account by asking for its password. | Malfunctions The Compliance Now ELD is capable of monitoring its compliance for various detectable malfunctions. At each instance when an ELD malfunction event is detected or cleared by the Compliance Now ELD, the ELD records the event. The recorded malfunction events are inconsistencies found while monitoring the ELD against FMCSA compliance requirements. Malfunction occurrences are indicated in the application header and in the Android notification toolbar with the letter ‘M’, respectively. The following shows the list of detectable malfunctions: ¿ Power Malfunction ¿ Engine Synchronization Malfunction ¿ Timing Malfunction ¿ Position Malfunction ¿ Data Recording Malfunction ¿ Data Transfer Malfunction Once the Malfunctions indicator ‘M’ is tapped, a dialog will be displayed with a list of the detected malfunction events alongside a ‘Clear’ button for each event. Tapping the Clear button will clear out the detected malfunction event. | Certifying Statement of FMCSA Regulation Testing The Compliance Now ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The Compliance Now ELD was installed on various types and sizes of Android phones and tablets. Testing was performed through the use of a J1939 simulator and actual vehicles while having been connected to the VBUS with Geometris , Calamp4230, Calamp Veosphere & Pacific Tracks connected devices. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the Hours of Service web application (portal) that can be accessed through a web browser. | |
| Compliance Now | Android & CalAmp Veosphere | 1.0.1905.190710 | GEO001 | Download | Download | Geosavi Inc. https://geosavi.com | 1-800-261-4361 | support@geosavi.com | https://geosavi.com | 8230 E Broadway Blvd. Ste. E9B, Tucson, AZ 85750 | Data Transfer The Compliance Now provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. Selecting the Data Transfer button from the Main HOS Main Screen will display the list of supported data transfer options which are via Bluetooth, Email and USB. A Select Vehicle option is also available for selecting a vehicle upon performing the data transfer, this option enables the Compliance Now to produce a data file or a series of data files of ELD records for a subset of its vehicles used by the driver. * Transfer via Bluetooth - this option enables the user to transfer files through Bluetooth. The ELD prompts for an output file comment which the driver may enter (optional). After the input, if Bluetooth is not yet turned on, a prompt will appear asking you to turn it on. You will then be asked to select the device name to which the data will be transmitted via Bluetooth. * Transfer via Email - this option enables the user to transfer files through email. The ELD output file transferred is encrypted using AES-256 in FIPS Publication 197. Before sending, the ELD prompts for an output file comment which the driver may enter (optional). The device's default email application will then be opened before sending the email to which the data will be transferred. * Transfer via USB - this option enables the user to transfer files through USB (external devices). However, prior to saving the driver’s ELD file to an external storage/device, the ELD re-authenticates the driver account by asking for its password. | Malfunctions The Compliance Now ELD is capable of monitoring its compliance for various detectable malfunctions. At each instance when an ELD malfunction event is detected or cleared by the Compliance Now ELD, the ELD records the event. The recorded malfunction events are inconsistencies found while monitoring the ELD against FMCSA compliance requirements. Malfunction occurrences are indicated in the application header and in the Android notification toolbar with the letter ‘M’, respectively. The following shows the list of detectable malfunctions: ? Power Malfunction ? Engine Synchronization Malfunction ? Timing Malfunction ? Position Malfunction ? Data Recording Malfunction ? Data Transfer Malfunction Once the Malfunctions indicator ‘M’ is tapped, a dialog will be displayed with a list of the detected malfunction events alongside a ‘Clear’ button for each event. Tapping the Clear button will clear out the detected malfunction event. | Certifying Statement of FMCSA Regulation Testing The Compliance Now ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The Compliance Now ELD was installed on various types and sizes of Android phones and tablets. Testing was performed through the use of a J1939 simulator and actual vehicles while having been connected to the VBUS with Geometris, Calamp4230, CAlAmp Veosphere & Pacific Tracks connected devices. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the Hours of Service web application (portal) that can be accessed through a web browser. | |
| CONNECTED TO THE ROAD ELD | CRS | 2.0 or higher | CRS129 | Download | Download | Connected to the road | 4694004780 | Eldfh3@connectedtotheroad.com | http://www.connectedtotheroad.com | 16416 s ave B, Somerton AZ 85350 | CONNECTED TO THE ROAD ELD is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | CONNECTED TO THE ROAD ELD monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The CONNECTED TO THE ROAD ELD Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on CONNECTED TO THE ROAD ELD during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | CONNECTED TO THE ROAD ELD meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations.CONNECTED TO THE ROAD ELD was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| Constitution Risk Management | RT0001 | 1.0 and Above | RTELD1 | Download | Download | Gorilla Fleet Safety, LLC | 844-636-1360 | info@gorillasafety.com | http://www.gorillasafety.com | 22327 Gosling Rd, Spring, TX 77379 | This ELD uses the web services and email transmission method. | The malfunctions supported are: Power Compliance Malfunction Engine Synchronization Malfunction Timing Compliance Malfunction Positioning Compliance Malfunction Data Recording Malfunction Data Transfer Malfunction Each of these malfunctions appears prominently for the user to understand the issue. When the user is presented with this, he is able to rectify the situation, contact the manufacturer or use paper logs, as provided as part of the instruction guide, to remain compliant. The malfunctions and malfunction codes can be found in the instruction guide with the required details in order for the driver to understand what he needs to do next. | The product has been thoroughly tested by both internal and external, third party, testers. Each requirement of the ELD has been either met or exceeded. The process of review and testing included the full review of the ruling, testing procedures and debugging of any blocker found in the software package. It further included the retesting by additional quality assurance professionals. Ultimately, the programing and hardware operate as intended and are in compliance. | |
| Conti-GO Plug & Play ELD | CONTIGO1 | 4.3.3 | CTAI01 | Download | Download | Conti-GO Transportation Technologies, LLC | 2103485716 | info@conti-gotech.com | http://www.conti-gotech.com | 9703 N I-35, San Antonio/TX/78233 | Telematic (Web Service, Email) | There is a section in the uploaded manual that describes and highlights the data transfer mechanism with colors and visual cues. 1. Tap the hamburger menu icon on the top left corner, or swipe from the left side of your device to the right side and select “Inspection Module” 2. Tap “Begin Inspection” and hand your device to the officer or tap “Send Output File” to send the report via email or web services. | There is a section in uploaded manual that describes and showcases Malfunctions with colors and visual cues. How does the driver know if Conti-GO ELD is malfunctioning? The Conti-GO ELD device has LED lights to simply indicate its status to the driver. DURING INSTALLATION NO LIGHTS Device Not Plugged into the truck's diagnostic port. BLUE SOLID (WORKING PROPERLY) The application is Connected and the Adapter is Receiving ECM data. BLUE BLINKING (MALFUNCTIONING) The Adapter is waiting for the application to connect. GREEN BLINKING (MALFUNCTIONING) The application is connected but the Adapter is waiting for the ECMs. Most likely this is because the key is off. DURING ELD OPERATION BLUE SOLID WITH MAGENTA FLASHES (WORKING PROPERLY) The application is Connected and the Adapter is Recording ELD data. The LEDs will flash Magenta each time record is recorded. GREEN SOLID WITH MAGENTA FLASHES (MALFUNCTIONING) The application is not connected and the Adapter is recording ELD data. The LEDs will flash Magenta each time a record is recorded. GREEN BLINKING (MALFUNCTIONING) The application is not connected and the Adapter is recording ELD data but waiting for ECM data. Most likely the key is off. WHAT DOES THE DRIVER NEED TO DO IF THE ELD IS MALFUNCTIONING? 1. Contact Conti-GO ELD support immediately after discovering a malfunction at 888-228-4460 or support@help24.us to troubleshoot the issue. 2. Provide written notice to your fleet management within 24 hours of malfunction discovery. 3. Keep a paper log for that day and until ELD is repaired or replaced. WHAT DOES THE FLEET NEED TO DO IF THE ELD IS MALFUNCTIONING? 1. A motor carrier must take action to correct the malfunction of the ELD within 8 days of discovery of the malfunction or a driver’s notification to the motor carrier, whichever occurs first. 2. Upon notification by fleet manager, Conti-GO Tech will send a new device. 3. If a motor carrier needs a time extension, they must notify the FMCSA Division Administrator for the State of the motor carrier’s principal place of business within five days after a driver notifies the motor carrier according to the guidelines set forth in § 395.34 (2). Conti-GO ELD will monitor and report malfunction data based on section 4.6 ELD’s Self-Monitoring of Required Functions table 4: P - “Power compliance” malfunction E - “Engine synchronization compliance” malfunction T - “Timing compliance” malfunction L - “Positioning compliance” malfunction R - “Data recording compliance” malfunction S - “Data transfer compliance” malfunction O - “Other” ELD detected malfunction | We have used the suggested Electronic Logging Device (ELD) Test Plan and Procedures document, version 2.0 dated 10/17/2016 provided by FMCSA to conduct testing of Conti-GO ELD. Upon completion of necessary tests outlined in the above named document we certify that Conti-GO ELD meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. Tests under the following categories have been conducted and passed (P): Accounts Inputs Vehicle Interface Processing Monitoring Recording Outputs Data Transfer |
| Contractors E Logs - 3030 | LMU-3030 | 4.3.13 | LMU030 | Download | Download | EquipmentShare | (573) 310-7902 | t3support@equipmentshare.com | https://www.equipmentshare.com/t3 | 5710 Bull Run Dr, Columbia, MO 65201 | Telematic (Web Service, Email) | The certified method of transferring data is via email and wireless web services. A driver will select “Inspection Mode” from the menu. There will be a button that says “Send Logs”. Select “Send Logs” and enter the email that the data will be transferred to. A driver may also send data directly to the FMCSA by tapping the button that reads "Send ELD Output File". If an internet connection cannot be established the driver can select “Begin Inspection” and pass the tablet to the safety official who can then view the current and last 7 days logs. Supported Data Transfer Methods: Email and Web Service | 1. POWER: There is a power issue with the hardware. Its possible the device is not connected. 2. ENGINE SYNCHRONIZATION: The mobile device has lost connectivity to the 3030 vehicle device for over 30 minutes. 3. TIMING: There is a discrepancy in timing between the devices and the vehicle. 4. POSITIONING: The GPS connection has been lost for 60 minutes or more. 5. DATA RECORDING: The device can no longer record or retain required events or retrieve recorded logs that are not kept remotely by the motor carrier. 6. DATA TRANSFER: The operation of the data transfer mechanism(s) is not confirmed. The device has remained in an unconfirmed data transfer mode for three consecutive monitoring checks. | I, William J Schlacks , hereby certify on behalf of EquipmentShare that ELD model LMU-3030 and version 4.3.13 has been sufficiently tested to meet the functional requirements included in the technical specifications in the Appendix to subpart B of part 395, title 49 of the Code of Federal Regulations, under the conditions in which the ELD would be used. |
| Contractors E Logs - MC3 | MC3 | 4.3.13 | MC3ELD | Download | Download | EquipmentShare | (573) 310-7902 | t3support@equipmentshare.com | https://www.equipmentshare.com/t3 | 5710 Bull Run Dr, Columbia, MO 65201 | Telematic (Web Service, Email) | The certified method of transferring data is via email and wireless web services. A driver will select “Inspection Mode” from the menu. There will be a button that says “Send Logs”. Select “Send Logs” and enter the email that the data will be transferred to. A driver may also send data directly to the FMCSA by tapping the button that reads "Send ELD Output File". If an internet connection cannot be established the driver can select “Begin Inspection” and pass the tablet to the safety official who can then view the current and last 7 days logs. Supported Data Transfer Methods: Email and Web Service | 1. POWER: There is a power issue with the hardware. Its possible the device is not connected. 2. ENGINE SYNCHRONIZATION: The mobile device has lost connectivity to the MC4 vehicle device for over 30 minutes. 3. TIMING: There is a discrepancy in timing between the devices and the vehicle. 4. POSITIONING: The GPS connection has been lost for 60 minutes or more. 5. DATA RECORDING: The device cannot retrieve recorded logs | I, William J Schlacks , hereby certify on behalf of EquipmentShare that ELD model MC3 and version 4.3.13 has been sufficiently tested to meet the functional requirements included in the technical specifications in the Appendix to subpart B of part 395, title 49 of the Code of Federal Regulations, under the conditions in which the ELD would be used. |
| Contractors E Logs - MC4 | MC-4 | 4.3.13 | MC4ELD | Download | Download | EquipmentShare | (573) 310-7902 | t3support@equipmentshare.com | https://www.equipmentshare.com/t3 | 5710 Bull Run Dr, Columbia, MO 65201 | Telematic (Web Service, Email) | The certified method of transferring data is via email and wireless web services. A driver will select “Inspection Mode” from the menu. There will be a button that says “Send Logs”. Select “Send Logs” and enter the email that the data will be transferred to. A driver may also send data directly to the FMCSA by tapping the button that reads "Send ELD Output File". If an internet connection cannot be established the driver can select “Begin Inspection” and pass the tablet to the safety official who can then view the current and last 7 days logs. Supported Data Transfer Methods: Email and Web Service | 1. POWER: There is a power issue with the hardware. Its possible the device is not connected. 2. ENGINE SYNCHRONIZATION: The mobile device has lost connectivity to the 3030 vehicle device for over 30 minutes. 3. TIMING: There is a discrepancy in timing between the devices and the vehicle. 4. POSITIONING: The GPS connection has been lost for 60 minutes or more. 5. DATA RECORDING: The device can no longer record or retain required events or retrieve recorded logs that are not kept remotely by the motor carrier. 6. DATA TRANSFER: The operation of the data transfer mechanism(s) is not confirmed. The device has remained in an unconfirmed data transfer mode for three consecutive monitoring checks. | I, William J Schlacks , hereby certify on behalf of EquipmentShare that ELD model MC-4 and version 4.3.13 has been sufficiently tested to meet the functional requirements included in the technical specifications in the Appendix to subpart B of part 395, title 49 of the Code of Federal Regulations, under the conditions in which the ELD would be used. |
| Contractors E Logs - MC4+ | MC-4+ | 4.3.13 | MC4PEL | Download | Download | EquipmentShare | (573) 310-7902 | t3support@equipmentshare.com | https://www.equipmentshare.com/t3 | 5710 Bull Run Dr, Columbia, MO 65201 | Telematic (Web Service, Email) | The certified method of transferring data is via email and wireless web services. A driver will select “Inspection Mode” from the menu. There will be a button that says “Send Logs”. Select “Send Logs” and enter the email that the data will be transferred to. A driver may also send data directly to the FMCSA by tapping the button that reads "Send ELD Output File". If an internet connection cannot be established the driver can select “Begin Inspection” and pass the tablet to the safety official who can then view the current and last 7 days logs. Supported Data Transfer Methods: Email and Web Service | 1. POWER: There is a power issue with the hardware. Its possible the device is not connected. 2. ENGINE SYNCHRONIZATION: The mobile device has lost connectivity to the MC4PEL vehicle device for over 30 minutes. 3. TIMING: There is a discrepancy in timing between the devices and the vehicle. 4. POSITIONING: The GPS connection has been lost for 60 minutes or more. 5. DATA RECORDING: The device can no longer record or retain required events or retrieve recorded logs that are not kept remotely by the motor carrier. 6. DATA TRANSFER: The operation of the data transfer mechanism(s) is not confirmed. The device has remained in an unconfirmed data transfer mode for three consecutive monitoring checks. | I, William J Schlacks , hereby certify on behalf of EquipmentShare that ELD model MC-4+ and version 4.3.13 has been sufficiently tested to meet the functional requirements included in the technical specifications in the Appendix to subpart B of part 395, title 49 of the Code of Federal Regulations, under the conditions in which the ELD would be used. |
| Contractors E Logs - MCX101 | MCX101-A | 4.3.13 | MCX101 | Download | Download | EquipmentShare | (573) 310-7902 | t3support@equipmentshare.com | https://www.equipmentshare.com/t3 | 5710 Bull Run Dr, Columbia, MO 65201 | Telematic (Web Service, Email) | The certified method of transferring data is via email and wireless web services. A driver will select “Inspection Mode” from the menu. There will be a button that says “Send Logs”. Select “Send Logs” and enter the email that the data will be transferred to. A driver may also send data directly to the FMCSA by tapping the button that reads "Send ELD Output File". If an internet connection cannot be established the driver can select “Begin Inspection” and pass the tablet to the safety official who can then view the current and last 7 days logs. Supported Data Transfer Methods: Email and Web Service | 1. POWER: There is a power issue with the hardware. It is possible the device is not connected. 2. ENGINE SYNCHRONIZATION: The mobile device has lost connectivity to the MCX101 vehicle device for over 30 minutes. 3. TIMING: There is a discrepancy in timing between the devices and the vehicle. 4. POSITIONING: The GPS connection has been lost for 60 minutes or more. 5. DATA RECORDING: The device can no longer record or retain required events or retrieve recorded logs that are not kept remotely by the motor carrier. 6. DATA TRANSFER: The operation of the data transfer mechanism(s) is not confirmed. The device has remained in an unconfirmed data transfer mode for three consecutive monitoring checks. | I, William J Schlacks , hereby certify on behalf of EquipmentShare that ELD model MCX101 and version 4.3.13 has been sufficiently tested to meet the functional requirements included in the technical specifications in the Appendix to subpart B of part 395, title 49 of the Code of Federal Regulations, under the conditions in which the ELD would be used. |
| CoreHub | HTHUB-NA | 1.11.11 | HUBDR1 | Download | Download | Coretex | 888-887-0935 | sales@coretex.com | www.coretex.com | One Bridge Plaza, Suite 100, Fort Lee, NJ 07024 | Telematic (Web Service, Email) | Coretex has designed a 'vizor card' for carriage within each vehicle. It shows graphically and with words what the driver, law enforcement officer is required to do to perform a roadside inspection. As there is no option to paste images into this registration request, the words alone have been extracted from this document. Coretex is happy to provide a copy of this document if requested to. Coretex has implemented the following data transfer mechanisms: Web Services Email Roadside Inspection If an FMCSA agent asks you to present your driver logs, be prepared to allow the inspector to examine and, or transfer the logs to the FMCSA. The inspector is required only to see log data as displayed via the Roadside Inspection screen. Logs cannot be edited during this process. This Quick Guide will show you how to access the Roadside Inspection from Coretex Drive. 1. Access your driver logs - In normal operation, tap the Home key to return to the dashboard. - Tap MENU to present the dashboard menu - Tap View Logs to present your driver Logs screen. 2 From the Driver Logs screen A graph of your status through the current day is presented by status, hour on the default graph. Log data is available for today’s date and the prior seven days. 3. Proceed to Roadside Inspection Tap ROADSIDE INSPECTION to present your Roadside Inspection screen. Hand the tablet to the inspector. The inspector can examine all the required statistics for the current driver and their available logs covering today’s date and the previous seven days. The inspector can navigate to the log date/s they want to inspect using the Previous Day or Next Day buttons. 4. Unidentified driving events Tap UNIDENTIFIED to view the Unidentified Driving Events screen, proceed to step 5. 5. Option to Data Transfer From the Roadside Inspection screen the inspector has the option to have all available driver logs sent to FMCSA. Tap DATA TRANSFER to present the EXPORT DATA FILE dialog Here you can easily transfer a copy of the driver logs, and have them sent directly to FMCSA. To export and transfer the data Tap either Web Service or Email as the preferred delivery protocol. The inspector can enter an optional comment to be lodged with the entry. Tap SEND to export and transfer the file. The export and transfer is completed and you are returned to the Roadside Inspection screen. | Coretex has designed a quick guide that explains the function of data diagnostics and malfunctions. It shows graphically and with words what each of them are and an explanation as to what to take note of and any actions required. As there is no option to paste images into this registration request, the words alone have been extracted from this document. Coretex is happy to provide a copy of this document if requested to. Data Diagnostics and Malfunctions Dealing with Data Diagnostic, Malfunction events ELD functionality in Coretex DRIVE caters for a number of error conditions that are flagged as data diagnostic or malfunction events. These are detailed here describing the codes, their descriptions, likely causes and response or resolution. Data Diagnostic events These events are when your ELD detects a data inconsistency such that you are triggered to follow the recommendations of the ELD provider to resolve the inconsistency. Note: Refer to Section 49 CFR 395.34c of the FMCSA regulations. In this section: 1 Power data diagnostic 2 Engine synchronization data diagnostic 3 Missing required data elements data diagnostic 4 Data transfer data diagnostic 5 Unidentified driving records data diagnostic Data Diagnostic codes Note: Refer to the ELD mandate on what you must do when there is a diagnostic event. Code Event Description 1 Power data diagnostic An ELD must monitor the data it receives, from the engine ECM or alternative sources, and data record history, or record a power data diagnostic event, to identify instances when it may not. Resolve driver can resolve Cause ELD not full functional within one minute of turning the engine on wiring or power source fault Code Event Description 2 Engine synchronization data diagnostic An ELD is required to establish a link to the engine ECM, and must record an engine synchronization diagnostic event, when it loses that link for more than five seconds. Resolve driver can resolve Cause wiring or power source fault Code Event Description 3 Missing required data elements data diagnostic An ELD must monitor the completeness of the ELD event record information in relation to the required data elements for each event type. It must record a missing required data element data diagnostic event for you, if any required fields are missing at the time of recording. Resolve driver can resolve Cause temporary or permanent loss of GPS signal intermittent or disconnected link to the vehicle ECM Code Event Description 4 Data transfer data diagnostic The ELD will automatically test the data transfer mechanism every seven days. A Data transfer data diagnostic event is triggered when the automatic test fail. Resolve might auto resolve Cause the scheduled automatic data transfer failed connectivity with the ELD host service is required for a successful test. Code Event Description 5 Unidentified driving records data diagnostic If more than 30 mins. of driving in a 24 hour period shows as ‘unidentified driver’ on the ELD, it must detect and record an unidentified driving record data diagnostic event. The data diagnostic indicator must be turned on for all drivers logged into that ELD for the current 24 hour period and the following seven days. Resolve driver can resolve Cause more than 30 mins combined vehicle use without a logged-in user Resolving Data Diagnostic events You must attend to data diagnostic events from your Coretex DRIVE dashboard. Codes Description 1 tap on the information card as an acknowledgement that you have been alerted to it 2 the card will clear when the condition ends 3 information cards appear on your dashboard with the title Data Diagnostics, and then the title of the particular data diagnostic tap on each in turn from the Driver Log View screen the log entry with a data diagnostic will highlight in a different color tap on the entry to edit the log to resolve the issue 4 tap on the information card as an acknowledgement that you have been alerted to it 5 tap the information card for the Unidentified Driver Records data diagnostic that appears on your dashboard the Unidentified Driving Records screen appears with entries in a list tap each in turn and assign to your log if these events belong to you Malfunction events Malfunction events are when the ELD detects technical compliance issues. You must: notify the motor carrier within 24 hours reconstruct the record of duty status for the current 24 hours and the last seven days on graph paper logs keep paper logs until the ELD is serviced and brought back into compliance Note: Refer to Section 49 CFR 395.34c of the FMCSA regulations. In this section: P Power compliance E Engine synchronization compliance T Timing compliance L Positioning compliance R Data recording compliance S Data transfer compliance Malfunction codes Code Event Description P Power compliance An ELD must monitor the data it receives from the engine ECM and set a power compliance malfunction event to identify instances when it may not have complied with the power requirements Resolve driver can resolve Cause more than 30 mins of driving time lost in a 24 hour period Code Event Description E Engine synchronization compliance An ELD must set an engine synchronization compliance malfunction, if connectivity to any of the required data sources is lost for more than 30 mins during a 24 hour period, aggregated across all driver profiles. Resolve driver can resolve Cause more than 30 mins without ECM engine synchronization over a 24 hour period Code Event Description T Timing compliance The ELD must periodically cross-check its time with an external UTC source, and must record a timing compliance malfunction when it can no longer meet the underlying timing requirement of less than 10 mins of time deviation. Resolve driver can resolve Cause vehicle has been out of service for sufficient time that the internal clock is no longer accurate, and the ELD has not yet synchronized its time you are recommended to ensure that the tablet’s Settings is set to using automatic time synchronization Code Event Description L Positioning compliance An ELD must monitor elapsed time during periods when the ELD fails to acquire a valid position measurement within five miles of the vehicle’s movement, when such elapsed time exceeds a cumulative 60 mins over a 24 hour period, the ELD must set and record a Positioning compliance malfunction. Resolve might auto resolve Cause more than 60 mins without a valid GPS reading in a 24 hour period Code Event Description R Data recording compliance An ELD must monitor its storage capacity and integrity, and must detect a data recording compliance malfunction, if it can no longer: record or retain required events retrieve recorded logs that are not otherwise cataloged remotely by the motor carrier Resolve driver can not resolve Cause hardware fault Code Event Description S Data transfer compliance After an ELD records a data transfer data diagnostic event, the ELD must increase the frequency of the monitoring function to check at least once every 24 hour period. If the ELD stays in the unconfirmed data transfer mode following the next three consecutive monitoring checks, the ELD must detect and record a data transfer compliance malfunction. This fault auto-resolves when the device begins to communicate successfully. Resolve might auto resolve Cause failure to communicate for three days following a data transfer data diagnostic event | Certifying Statement of FMCSA Regulation Testing Coretex has tested and compared its ELD functionality in full against the Electronic Logging Device Test Plan and Procedures, dated 7.18.2017, Version 2.1 as published by the Federal Motor Carrier Safety Administration. Coretex appointed two independent persons, separated operationally and from outside the Coretex company to impartially test Coretex's compliance with the above mentioned Test Plan and Procedures. Three hundred and thirty seven individuals tests, from the documentation, have been tested and checked against the requirements. All tests have passed and are compliant. Coretex also understands that the process is self-certification and if any discrepancies are found then Coretex is required to resolve any issues within the time required by the ELD Mandate. Coretex’s ELD solution exceeds the functionality requirements of the Test Plan and Procedures and these items have been tested in unison with the mandated requirements. External tests have also been completed against the recently released web services from the FMCSA for checking the Roadside Inspection File output format. Coretex also understands that future releases of its ELD solution will require to be compliant against the Test Plan and Procedures from the FMCSA as and when either changes. Rav Brar, Product Manager, Coretex Auckland, New Zealand |
| Coretex DRIVE | ELD01 | 1.11.11 | TMUDRI | Download | Download | Coretex | 888-887-0935 | sales@coretex.com | www.coretex.com | One Bridge Plaza, Suite 100, Fort Lee, NJ 07024 | Telematic (Web Service, Email) | Coretex has designed a 'vizor card' for carriage within each vehicle. It shows graphically and with words what the driver,law enforcement officer is required to do to perform a roadside inspection. As there is no option to paste images into this registration request, the words alone have been extracted from this document. Coretex is happy to provide a copy of this document if requested to. Coretex has implemented the following data transfer mechanisms: Web Services Email Roadside Inspection If an FMCSA agent asks you to present your driver logs, be prepared to allow the inspector to examine and,or transfer the logs to the FMCSA. The inspector is required only to see log data as displayed via the Roadside Inspecton screen. Logs cannot be edited during this process. This Quick Guide will show you how to access the Roadside Inspecton from Coretex Drive. 1. Access your driver logs - In normal operaton, tap the Home key to return to the dashboard. - Tap MENU to present the dashboard menu - Tap View Logs to present your driver Logs screen. 2 From the Driver Logs screen A graph of your status through the current day is presented by status, hour on the default graph. Log data is available for today’s date and the prior seven days. 3. Proceed to Roadside Inspection Tap ROADSIDE INSPECTION to present your Roadside Inspecton screen. Hand the tablet to the inspector. The inspector can examine all the required statistics for the current driver and their available logs covering today’s date and the previous seven days. The inspector can navigate to the log date/s they want to inspect using the Previous Day or Next Day butons. 4. Unidentifed driving events Tap UNIDENTIFIED to view the Unidentifed Driving Events screen, proceed to step 5. 5. Option to Data Transfer From the Roadside Inspection screen the inspector has the opton to have all available driver logs sent to FMCSA. Tap DATA TRANSFER to present the EXPORT DATA FILE dialog Here you can easily transfer a copy of the driver logs, and have them sent directly to FMCSA. To export and transfer the data Tap either Web Service or Email as the preferred delivery protocol. The inspector can enter an optional comment to be lodged with the entry. Tap SEND to export and transfer the file. The export and transfer is completed and you are returned to the Roadside Inspection screen. | Coretex has designed a quick guide that explains the function of data diagnostics and malfunctions. It shows graphically and with words what each of them are and an explanation as to what to take note of and any actions required. As there is no option to paste images into this registration request, the words alone have been extracted from this document. Coretex is happy to provide a copy of this document if requested to. Data Diagnostics and Malfunctions Dealing with Data Diagnostic, Malfunction events ELD functionality in Coretex DRIVE caters for a number of error conditions that are flagged as data diagnostic or malfunction events. These are detailed here describing the codes, their descriptions, likely causes and response or resolution. Data Diagnostic events These events are when your ELD detects a data inconsistency such that you are triggered to follow the recommendations of the ELD provider to resolve the inconsistency. Note: Refer to Section 49 CFR 395.34c of the FMCSA regulations. In this section: 1 Power data diagnostic 2 Engine synchronization data diagnostic 3 Missing required data elements data diagnostic 4 Data transfer data diagnostic 5 Unidentified driving records data diagnostic Data Diagnostic codes Note: Refer to the ELD mandate on what you must do when there is a diagnostic event. Code Event Description 1 Power data diagnostic An ELD must monitor the data it receives, from the engine ECM or alternative sources, and data record history, or record a power data diagnostic event, to identify instances when it may not. Resolve driver can resolve Cause ELD not full functional within one minute of turning the engine on wiring or power source fault Code Event Description 2 Engine synchronization data diagnostic An ELD is required to establish a link to the engine ECM, and must record an engine synchronization diagnostic event, when it loses that link for more than five seconds. Resolve driver can resolve Cause wiring or power source fault Code Event Description 3 Missing required data elements data diagnostic An ELD must monitor the completeness of the ELD event record information in relation to the required data elements for each event type. It must record a missing required data element data diagnostic event for you, if any required fields are missing at the time of recording. Resolve driver can resolve Cause temporary or permanent loss of GPS signal intermittent or disconnected link to the vehicle ECM Code Event Description 4 Data transfer data diagnostic The ELD will automatically test the data transfer mechanism every seven days. A Data transfer data diagnostic event is triggered when the automatic test fail. Resolve might auto resolve Cause the scheduled automatic data transfer failed connectivity with the ELD host service is required for a successful test. Code Event Description 5 Unidentified driving records data diagnostic If more than 30 mins. of driving in a 24 hour period shows as ‘unidentified driver’ on the ELD, it must detect and record an unidentified driving record data diagnostic event. The data diagnostic indicator must be turned on for all drivers logged into that ELD for the current 24 hour period and the following seven days. Resolve driver can resolve Cause more than 30 mins combined vehicle use without a logged-in user Resolving Data Diagnostic events You must attend to data diagnostic events from your Coretex DRIVE dashboard. Codes Description 1 tap on the information card as an acknowledgement that you have been alerted to it 2 the card will clear when the condition ends 3 information cards appear on your dashboard with the title Data Diagnostics, and then the title of the particular data diagnostic tap on each in turn from the Driver Log View screen the log entry with a data diagnostic will highlight in a different color tap on the entry to edit the log to resolve the issue 4 tap on the information card as an acknowledgement that you have been alerted to it 5 tap the information card for the Unidentified Driver Records data diagnostic that appears on your dashboard the Unidentified Driving Records screen appears with entries in a list tap each in turn and assign to your log if these events belong to you Malfunction events Malfunction events are when the ELD detects technical compliance issues. You must: notify the motor carrier within 24 hours reconstruct the record of duty status for the current 24 hours and the last seven days on graph paper logs keep paper logs until the ELD is serviced and brought back into compliance Note: Refer to Section 49 CFR 395.34c of the FMCSA regulations. In this section: P Power compliance E Engine synchronization compliance T Timing compliance L Positioning compliance R Data recording compliance S Data transfer compliance Malfunction codes Code Event Description P Power compliance An ELD must monitor the data it receives from the engine ECM and set a power compliance malfunction event to identify instances when it may not have complied with the power requirements Resolve driver can resolve Cause more than 30 mins of driving time lost in a 24 hour period Code Event Description E Engine synchronization compliance An ELD must set an engine synchronization compliance malfunction, if connectivity to any of the required data sources is lost for more than 30 mins during a 24 hour period, aggregated across all driver profiles. Resolve driver can resolve Cause more than 30 mins without ECM engine synchronization over a 24 hour period Code Event Description T Timing compliance The ELD must periodically cross-check its time with an external UTC source, and must record a timing compliance malfunction when it can no longer meet the underlying timing requirement of less than 10 mins of time deviation. Resolve driver can resolve Cause vehicle has been out of service for sufficient time that the internal clock is no longer accurate, and the ELD has not yet synchronized its time you are recommended to ensure that the tablet’s Settings is set to using automatic time synchronization Code Event Description L Positioning compliance An ELD must monitor elapsed time during periods when the ELD fails to acquire a valid position measurement within five miles of the vehicle’s movement, when such elapsed time exceeds a cumulative 60 mins over a 24 hour period, the ELD must set and record a Positioning compliance malfunction. Resolve might auto resolve Cause more than 60 mins without a valid GPS reading in a 24 hour period Code Event Description R Data recording compliance An ELD must monitor its storage capacity and integrity, and must detect a data recording compliance malfunction, if it can no longer: record or retain required events retrieve recorded logs that are not otherwise cataloged remotely by the motor carrier Resolve driver can not resolve Cause hardware fault Code Event Description S Data transfer compliance After an ELD records a data transfer data diagnostic event, the ELD must increase the frequency of the monitoring function to check at least once every 24 hour period. If the ELD stays in the unconfirmed data transfer mode following the next three consecutive monitoring checks, the ELD must detect and record a data transfer compliance malfunction. This fault auto-resolves when the device begins to communicate successfully. Resolve might auto resolve Cause failure to communicate for three days following a data transfer data diagnostic event | Certifying Statement of FMCSA Regulation Testing Coretex has tested and compared its ELD functionality in full against the Electronic Logging Device Test Plan and Procedures, dated 10.17.2016, Version 2.0 as published by the Federal Motor Carrier Safety Administration. Coretex appointed two independent persons, separated operationally and from outside the Coretex company to impartially test Coretex's compliance with the above mentioned Test Plan and Procedures. Three hundred and fifteen individuals tests, from the documentation, have been tested and checked against the requirements. All tests have passed and are compliant. Coretex also understands that the process is self-certification and if any discrepancies are found then Coretex is required to resolve any issues within sixty days. Coretex's ELD solution exceeds the functionality requirements of the Test Plan and Procedures and these items have been tested in unison with the mandated requirements. External tests have also been completed against the recently released web services from the FMCSA for checking the Roadside Inspection File output format. Coretex also understands that future releases of its ELD solution will require to be compliant against the Test Plan and Procedures from the FMCSA as and when either changes. Ben Martel Chief Science Officer Coretex Auckland, New Zealand |
| Coretex DRIVE | ELD02 | 1.11.11 | GENDRI | Download | Download | Coretex | 888-887-0935 | sales@coretex.com | www.coretex.com | One Bridge Plaza, Suite 100, Fort Lee, NJ 07024 | Telematic (Web Service, Email) | Coretex has designed a 'vizor card' for carriage within each vehicle. It shows graphically and with words what the driver,law enforcement officer is required to do to perform a roadside inspection. As there is no option to paste images into this registration request, the words alone have been extracted from this document. Coretex is happy to provide a copy of this document if requested to. Coretex has implemented the following data transfer mechanisms: Web Services Email Roadside Inspection If an FMCSA agent asks you to present your driver logs, be prepared to allow the inspector to examine and,or transfer the logs to the FMCSA. The inspector is required only to see log data as displayed via the Roadside Inspecton screen. Logs cannot be edited during this process. This Quick Guide will show you how to access the Roadside Inspecton from Coretex Drive. 1. Access your driver logs - In normal operaton, tap the Home key to return to the dashboard. - Tap MENU to present the dashboard menu - Tap View Logs to present your driver Logs screen. 2 From the Driver Logs screen a graph of your status through the current day is presented by status, hour on the default graph. Log data is available for today’s date and the prior seven days. 3. Proceed to Roadside Inspection Tap ROADSIDE INSPECTION to present your Roadside Inspecton screen. Hand the tablet to the inspector. The inspector can examine all the required statistics for the current driver and their available logs covering today’s date and the previous seven days. The inspector can navigate to the log date/s they want to inspect using the Previous Day or Next Day butons. 4. Unidentifed driving events Tap UNIDENTIFIED to view the Unidentifed Driving Events screen, proceed to step 5. 5. Option to Data Transfer From the Roadside Inspection screen the inspector has the opton to have all available driver logs sent to FMCSA. Tap DATA TRANSFER to present the EXPORT DATA FILE dialog Here you can easily transfer a copy of the driver logs, and have them sent directly to FMCSA. To export and transfer the data Tap either Web Service or Email as the preferred delivery protocol. The inspector can enter an optional comment to be lodged with the entry. Tap SEND to export and transfer the file. The export and transfer is completed and you are returned to the Roadside Inspection screen. Description of the supported and certified data transfer mechanisms and step-by-step instructions for a driver to produce and transfer the ELD records to an authorized safety official | Coretex has designed a quick guide that explains the function of data diagnostics and malfunctions. It shows graphically and with words what each of them are and an explanation as to what to take note of and any actions required. As there is no option to paste images into this registration request, the words alone have been extracted from this document. Coretex is happy to provide a copy of this document if requested to. Data Diagnostics and Malfunctions Dealing with Data Diagnostic, Malfunction events ELD functionality in Coretex DRIVE caters for a number of error conditions that are flagged as data diagnostic or malfunction events. These are detailed here describing the codes, their descriptions, likely causes and response or resolution. Data Diagnostic events These events are when your ELD detects a data inconsistency such that you are triggered to follow the recommendations of the ELD provider to resolve the inconsistency. Note: Refer to Section 49 CFR 395.34c of the FMCSA regulations. In this section: 1 Power data diagnostic 2 Engine synchronization data diagnostic 3 Missing required data elements data diagnostic 4 Data transfer data diagnostic 5 Unidentified driving records data diagnostic Data Diagnostic codes Note: Refer to the ELD mandate on what you must do when there is a diagnostic event. Code Event Description 1 Power data diagnostic An ELD must monitor the data it receives, from the engine ECM or alternative sources, and data record history, or record a power data diagnostic event, to identify instances when it may not. Resolve driver can resolve Cause ELD not full functional within one minute of turning the engine on wiring or power source fault Code Event Description 2 Engine synchronization data diagnostic An ELD is required to establish a link to the engine ECM, and must record an engine synchronization diagnostic event, when it loses that link for more than five seconds. Resolve driver can resolve Cause wiring or power source fault Code Event Description 3 Missing required data elements data diagnostic An ELD must monitor the completeness of the ELD event record information in relation to the required data elements for each event type. It must record a missing required data element data diagnostic event for you, if any required fields are missing at the time of recording. Resolve driver can resolve Cause temporary or permanent loss of GPS signal intermittent or disconnected link to the vehicle ECM Code Event Description 4 Data transfer data diagnostic The ELD will automatically test the data transfer mechanism every seven days. A Data transfer data diagnostic event is triggered when the automatic test fail. Resolve might auto resolve Cause the scheduled automatic data transfer failed connectivity with the ELD host service is required for a successful test. Code Event Description 5 Unidentified driving records data diagnostic If more than 30 mins. of driving in a 24 hour period shows as ‘unidentified driver’ on the ELD, it must detect and record an unidentified driving record data diagnostic event. The data diagnostic indicator must be turned on for all drivers logged into that ELD for the current 24 hour period and the following seven days. Resolve driver can resolve Cause more than 30 mins combined vehicle use without a logged-in user Resolving Data Diagnostic events You must attend to data diagnostic events from your Coretex DRIVE dashboard. Codes Description 1 tap on the information card as an acknowledgement that you have been alerted to it 2 the card will clear when the condition ends 3 information cards appear on your dashboard with the title Data Diagnostics, and then the title of the particular data diagnostic tap on each in turn from the Driver Log View screen the log entry with a data diagnostic will highlight in a different color tap on the entry to edit the log to resolve the issue 4 tap on the information card as an acknowledgement that you have been alerted to it 5 tap the information card for the Unidentified Driver Records data diagnostic that appears on your dashboard the Unidentified Driving Records screen appears with entries in a list tap each in turn and assign to your log if these events belong to you Malfunction events Malfunction events are when the ELD detects technical compliance issues. You must: notify the motor carrier within 24 hours reconstruct the record of duty status for the current 24 hours and the last seven days on graph paper logs keep paper logs until the ELD is serviced and brought back into compliance Note: Refer to Section 49 CFR 395.34c of the FMCSA regulations. In this section: P Power compliance E Engine synchronization compliance T Timing compliance L Positioning compliance R Data recording compliance S Data transfer compliance Malfunction codes Code Event Description P Power compliance An ELD must monitor the data it receives from the engine ECM and set a power compliance malfunction event to identify instances when it may not have complied with the power requirements Resolve driver can resolve Cause more than 30 mins of driving time lost in a 24 hour period Code Event Description E Engine synchronization compliance An ELD must set an engine synchronization compliance malfunction, if connectivity to any of the required data sources is lost for more than 30 mins during a 24 hour period, aggregated across all driver profiles. Resolve driver can resolve Cause more than 30 mins without ECM engine synchronization over a 24 hour period Code Event Description T Timing compliance The ELD must periodically cross-check its time with an external UTC source, and must record a timing compliance malfunction when it can no longer meet the underlying timing requirement of less than 10 mins of time deviation. Resolve driver can resolve Cause vehicle has been out of service for sufficient time that the internal clock is no longer accurate, and the ELD has not yet synchronized its time you are recommended to ensure that the tablet’s Settings is set to using automatic time synchronization Code Event Description L Positioning compliance An ELD must monitor elapsed time during periods when the ELD fails to acquire a valid position measurement within five miles of the vehicle’s movement, when such elapsed time exceeds a cumulative 60 mins over a 24 hour period, the ELD must set and record a Positioning compliance malfunction. Resolve might auto resolve Cause more than 60 mins without a valid GPS reading in a 24 hour period Code Event Description R Data recording compliance An ELD must monitor its storage capacity and integrity, and must detect a data recording compliance malfunction, if it can no longer: record or retain required events retrieve recorded logs that are not otherwise cataloged remotely by the motor carrier Resolve driver can not resolve Cause hardware fault Code Event Description S Data transfer compliance After an ELD records a data transfer data diagnostic event, the ELD must increase the frequency of the monitoring function to check at least once every 24 hour period. If the ELD stays in the unconfirmed data transfer mode following the next three consecutive monitoring checks, the ELD must detect and record a data transfer compliance malfunction. This fault auto-resolves when the device begins to communicate successfully. Resolve might auto resolve Cause failure to communicate for three days following a data transfer data diagnostic event | Certifying Statement of FMCSA Regulation Testing Coretex has tested and compared its ELD functionality in full against the Electronic Logging Device Test Plan and Procedures, dated 10.17.2016, Version 2.0 as published by the Federal Motor Carrier Safety Administration. Coretex appointed two independent persons, separated operationally and from outside the Coretex company to impartially test Coretex's compliance with the above mentioned Test Plan and Procedures. Three hundred and fifteen individuals tests, from the documentation, have been tested and checked against the requirements. All tests have passed and are compliant. Coretex also understands that the process is self-certification and if any discrepancies are found then Coretex is required to resolve any issues within sixty days. Coretex's ELD solution exceeds the functionality requirements of the Test Plan and Procedures and these items have been tested in unison with the mandated requirements. External tests have also been completed against the recently released web services from the FMCSA for checking the Roadside Inspection File output format. Coretex also understands that future releases of its ELD solution will require to be compliant against the Test Plan and Procedures from the FMCSA as and when either changes. Ben Martel Chief Science Officer Coretex Auckland, New Zealand |
| CTAndroidELD | CTAndroidAppELD | 1.6.11 or higher | CTAA19 | Download | Download | Data System Services LLC | 586-939-7000 ext 3606 opt 2 | tac@datasystemservicesllc.com | http://datasystemservicesllc.com | 34200 Mound Rd, Sterling Heights MI 48310 | Telematic (Web Service, Email) | Generate the ELD Compliance Report when requested for ELD records sent to an “authorized safety official” utilizing Telematics using Web services and Email. Simply going to the Options portion in the HOS Application. Driver will click “Generate”, enter in number of days the officer wants, any comments the Officer would like to add to Email, then click “Generate Report”.If all info is correct, report will be sent. If all data is not automatically captured, driver will be given a manual field to enter in correct Odometer reading. Once Odometer is entered, the ELD will send report. | Positioning Compliance Malfunction Power Compliance Malfunction Engine Synchronization Malfunction Timing Compliance Malfunction Low battery Data Transfer Malfunction Other malfunction Data Recording Compliance Malfunction | Data System services LLC has tested and certify that the ELD device complies with FMCSA regulations (ELD Rule). |
| CTE-LOG ELD | CRS | 2.11.12 or up. | CRS102 | Download | Download | CTE LOG ELD LLC | (347) 664-0077 | ctelogbook@gmail.com | www.ctelogs.com | 5808 WILLOW VIEW DR, Mason/OH/45040 | Telematic (Web Service, Email) | CTE-LOG ELD solution offers an easily accessible inspection mode that compiles ELD records and enables logs data transfer to safety officials during roadside inspections. The DOT Inspection Mode can be accessed from the main menu and supports email and web service data transfer. | CTE-LOG ELD detects malfunctions and diagnostic events through a continuous self-monitoring system. Following section 4.6 of the ELD mandate, all issues related to unidentified driving, data transfer, required data elements, data recording, power, engine synchronization, timing, and positioning are identified, recorded, and notified to the driver by visual cues. | CTE-LOG ELD has been tested in accordance with the FMCSA's Test Plan and Procedures. CTE-LOG ELD certifies that our product fulfills all requirements as specified in the Functional Specifications for the ELD product. |
| CTWinmobileELD | CTMC9500ELD | 3.46 or higher | CT9500 | Download | Download | Data System Services LLC | 586-939-7000 ext 3606 opt 2 | tac@datasystemservicesllc.com | http://datasystemservicesllc.com | 34200 Mound Rd, Sterling Heights MI 48310 | Telematic (Web Service, Email) | Generate the ELD Compliance Report when requested for ELD records sent to an “authorized safety official” utilizing Telematics using Web services and Email. Simply going to the Options portion in the HOS Application. Driver will click “Generate”, enter in number of days the officer wants, any comments the Officer would like to add to Email, then click “Generate Report”.If all info is correct, report will be sent. If all data is not automatically captured, driver will be given a manual field to enter in correct Odometer reading. Once Odometer is entered, the ELD will send report. | Positioning Compliance Malfunction Power Compliance Malfunction Engine Synchronization Malfunction Timing Compliance Malfunction Low battery Data Transfer Malfunction Other malfunction Data Recording Compliance Malfunction | Data System services LLC has tested and certify that the ELD device complies with FMCSA regulations (ELD Rule). |
| CyntrX ELD Plus | iOS and Geometris | 1.0 | CXEPO1 | Download | Download | CyntrX | 9203380479 | compliance@cyntrx.com | http://www.cyntrx.com | 1302 South Broadway, De Pere, WI, 54115 | To send logs at roadside a driver must: 1. Start on the main dashboard. 2. Select "Roadside Inspection" from about the middle of the screen. 3. Select "Send Logs to DOT." 4. Type in the notation requested by the inspecting officer. 5. Select "Send." This will send logs using both Wireless Web Services and Email (option 1 as stated in the ELD mandate regarding roadside data transfer). | The malfunctions supported are: Power Compliance Malfunction Engine Synchronization Malfunction Timing Compliance Malfunction Positioning Compliance Malfunction Data Recording Malfunction Data Transfer Malfunction Each of these malfunctions appears prominently for the user to understand the issue. When the user is presented with this, he is able to rectify the situation, contact the manufacturer or use paper logs, as provided as part of the instruction guide, to remain compliant. The malfunctions and malfunction codes can be found in the instruction guide with the required details in order for the driver to understand what he needs to do next. | The product has been thoroughly tested by both internal and external, third party, testers. Each requirement of the ELD has been either met or exceeded. The process of review and testing included the full review of the ruling, testing procedures and debugging of any blocker found in the software package. It further included the retesting by additional quality assurance professionals. Ultimately, the programing and hardware operate as intended and are in compliance. | |
| CyntrX ELD Plus | Android and Geometris | 1.0 | CXEPO2 | Download | Download | CyntrX | 9203380479 | compliance@cyntrx.com | http://www.cyntrx.com | 1302 South Broadway, De Pere, WI, 54115 | To send logs at roadside a driver must: 1. Start on the main dashboard. 2. Select "Roadside Inspection" from about the middle of the screen. 3. Select "Send Logs to DOT." 4. Type in the notation requested by the inspecting officer. 5. Select "Send." This will send logs using both Wireless Web Services and Email (option 1 as stated in the ELD mandate regarding roadside data transfer). | The malfunctions supported are: Power Compliance Malfunction Engine Synchronization Malfunction Timing Compliance Malfunction Positioning Compliance Malfunction Data Recording Malfunction Data Transfer Malfunction Each of these malfunctions appears prominently for the user to understand the issue. When the user is presented with this, he is able to rectify the situation, contact the manufacturer or use paper logs, as provided as part of the instruction guide, to remain compliant. The malfunctions and malfunction codes can be found in the instruction guide with the required details in order for the driver to understand what he needs to do next. | The product has been thoroughly tested by both internal and external, third party, testers. Each requirement of the ELD has been either met or exceeded. The process of review and testing included the full review of the ruling, testing procedures and debugging of any blocker found in the software package. It further included the retesting by additional quality assurance professionals. Ultimately, the programing and hardware operate as intended and are in compliance. | |
| DAILY ELD | DRS | 2.22.22 or up | DRS231 | Download | Download | DAILY ELD LLC | 2248288476 | info@dailyeld.com | www.dailyeld.com | 2136 Colonial St, Aurora, IL 60503 | Telematic (Web Service) | DAILY ELD system allows drivers to transfer log data through telematics methods in compliance with the regulations outlined in Title 49, Part 395, Section 4.9.1, Appendix A, Subpart B of the CFR. Drivers can also produce a report on their mobile display or transfer log data through web services or email if requested by an officer. | As per the regulations outlined in Appendix A, section 4.6, the DAILY ELD system continuously monitors itself for malfunctions. If a malfunction or diagnostic event occurs, such as issues with data recording, data transfer, or power, DAILY ELD system will display a visual alert to the driver. This includes alerts for any issues with engine synchronization, timing, positioning, or unidentified driving. | As per the FMCSA's testing procedures, DAILY ELD has undergone thorough testing to ensure compliance as an electronic logging system. DAILY ELD can confirm that the system meets the requirements of 49 CFR Part 395 Subpart B, including the correct logging and transmission of hours of service data. |
| Datasmart ELD | DSTTG-1710 | 3.0.2116.210920 | DSE001 | Download | Download | Datasmart ELD | (951) 331-4522 | general@datasmart4trucks.com | http://datasmart4trucks.co/ | 31915 rancho california road suite 200-336, temecula, CA 92591 | Data Transfer The datasmart ELD HOS provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. Selecting the Data Transfer button from the Main HOS Main Screen will display the list of supported data transfer options which are via Bluetooth, Email and USB. A Select Vehicle option is also available for selecting a vehicle upon performing the data transfer, this option enables the datasmart ELD HOS to produce a data file or a series of data files of ELD records for a subset of its vehicles used by the driver. Transfer via Bluetooth - this option enables the user to transfer files through Bluetooth. The ELD prompts for an output file comment which the driver may enter (optional). After the input, if Bluetooth is not yet turned on, a prompt will appear asking you to turn it on. You will then be asked to select the device name to which the data will be transmitted via Bluetooth. Transfer via Email - this option enables the user to transfer files through email. The ELD output file transferred is encrypted using AES-256 in FIPS Publication 197. Before sending, the ELD prompts for an output file comment which the driver may enter (optional). The device's default email application will then be opened before sending the email to which the data will be transferred. Transfer via USB - this option enables the user to transfer files through USB (external devices). However, prior to saving the driver’s ELD file to an external storage/device, the ELD re-authenticates the driver account by asking for its password. | Malfunctions The datasmart ELD HOS is capable of monitoring its compliance for various detectable malfunctions. At each instance when an ELD malfunction event is detected or cleared by the datasmart ELD HOS, the ELD records the event. The recorded malfunction events are inconsistencies found while monitoring the ELD against FMCSA compliance requirements. Malfunction occurrences are indicated in the application header and in the Android notification toolbar with the letter ‘M’, respectively. The following shows the list of detectable malfunctions: Power Malfunction Engine Synchronization Malfunction Timing Malfunction Position Malfunction Data Recording Malfunction Data Transfer Malfunction Once the Malfunctions indicator ‘M’ is tapped, a dialog will be displayed with a list of the detected malfunction events alongside a ‘Clear’ button for each event. Tapping the Clear button will clear out the detected malfunction event. | Certifying Statement of FMCSA Regulation Testing The datasmart ELD HOS was certified through successful execution and verification of the FMCSA ELD Test Procedures. The datasmart ELD HOS was installed on various types and sizes of Android phones and tablets. Testing was performed through the use of a J1939 simulator and actual vehicles while having been connected to the datasmart ELD EBM engine connected devices. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the Hours of Service web application (portal) that can be accessed through a web browser. | |
| DELTA SOLUTIONS ELD | DELS | 2.21.28 or above | DRS258 | Download | Download | Delta Solutions Inc. | 9703559339 | info@deltasolutionseld.com | http://www.deltasolutionseld.com | 4837 S Picadilly Ct, Aurora/CO/80015 | Telematic (Web Service, Email) | Through the DELTA SOLUTIONS ELD system, telematics data transfer is facilitated using either email or web services. The driver can perform the transfer by accessing the DOT Inspection Mode menu and clicking the "Send" button. Furthermore, a separate DOT Inspection Mode button is available for the driver to display the logs report to a DOT officer on their mobile device. | With the goal of maintaining compliance, detecting malfunctions and data inconsistencies, and documenting such occurrences, the DELTA SOLUTIONS ELD system employs specific codes to classify compliance malfunctions and diagnostic events, such as: ■ P for "Power compliance" malfunction, ■ E "Engine synchronization compliance" malfunction, ■ T for "Timing compliance" malfunction, ■ L for "Positioning compliance" malfunction, ■ R for "Data recording compliance" malfunction, ■ S for "Data transfer compliance" malfunction, ■ O for "Other" ELD-detected malfunctions, ■ 1 for "Power data diagnostic" event, ■ 2 for "Engine synchronization data diagnostic" event, ■ 3 for "Missing required data elements data diagnostic" event, ■ 4 for "Data transfer data diagnostic" event, ■ 5 for "Unidentified driving records data diagnostic" event, ■ 6 for "Other" ELD-identified diagnostic events. The DELTA SOLUTIONS ELD Malfunction and Diagnostic Event Records record all malfunctions that occurred during the relevant time period and relay active malfunctions to all ELD users. | The FMCSA´s testing procedures require thorough testing of DELTA SOLUTIONS ELD to verify compliance as an electronic logging system, which has been completed. The system is able to confirm that it meets the requirements of 49 CFR Part 395 Subpart B, including the accurate logging and transmission of hours of service data. |
| DFL ELD | DRS | 2.0 or higher | DRS240 | Download | Download | DFL ELD | 800-613-3570 | admin@dfleld.com | www.dfleld.com | 197 JOHNSON ST , TULARE CA 93274 | DFL ELD is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | DFL ELD monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The DFL ELD Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on DFL ELD during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | DFL ELD meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. DFL ELD was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| DIALOG ELD | DELD01 | DELDA1.0 | DWLA01 | Download | Download | Trucksoft Solutions | 847-773-5560 | info@dialogeld.com | http://dialogeld.com | 2600 S 25th Ave, Suite J, Broadview, IL, 60155, Broadview, IL, 60155 | DIALOG ELD provides an easy way for a driver to produce and transfer the ELD records to an authorized safety official. TELEMATICS EMAIL: 1. Tap “Send Logs” from “Inspection Module” screen. 2. Select the checkbox next to each log you want to send. 3. Choose the transfer method by clicking on Email tab. 4. Enter the email address of the authorized safety official. 5. Tap “Send” to email your logs. TELEMATICS WIRELESS TRANSFER: 1. Tap “Send Output File” from “Inspection Module” screen. 2. Enter the Investigation Code of the authorized safety official. 3. Tap “Send” to transfer your logs. *Federal Motor Carrier Safety regulation 49 CFR § 395.15 does not require a driver to provide a hard copy printout of their logs for an authorized safety official. However, you can email your logs from the ELD ONE App if you choose to provide the authorized safety official a copy. ELD ONE is made to transfer data wirelessly via Web Services and follows the below standards put forward by FMCSA in article 4.10.1.1. (a) Transfer of ELD data to FMCSA via Web Services must follow the following standards: (1)Web Services Description Language (WSDL) 1.1 (2)Simple Object Access Protocol (SOAP) 1.2 (incorporated by reference, see § 395.38) (3)Extensible Markup Language (XML) 1.0 5th Edition (b) If an ELD provider plans to use Web Services, upon ELD provider registration as described in section 5.1 of this appendix, (1) FMCSA will provide formatting files necessary to convert the ELD file into an XML format and upload the data to the FMCSA servers. These files include FMCSA’s Rules of Behavior, XML Schema, WSDL file, Interface Control Document (ICD), and the ELD Web Services Development Handbook, and (2)ELD Providers must obtain a Public/Private Key pair compliant with the NIST SP 800-32, Introduction to Public Key Technology and the Federal PKI Infrastructure, (incorporated by reference, see § 395.38), and submit the public key with their registration. (3)ELD Providers will be required to complete a test procedure to ensure their data is properly formatted before they can begin submitting driver’s ELD data to the FMCSA server. (c)ELD data transmission must be accomplished in a way that protects the privacy of the driver(s). (d)At roadside, if both the vehicle operator and law enforcement have an available data connection, the vehicle operator will initiate the transfer of ELD data to an authorized safety official. In some cases, an ELD may be capable of converting the ELD file to an XML format using an FMCSA-provided schema and upload it using information provided in the WSDL file using SOAP via RFC 7230, RFC 7231, and RFC 5246, Transport Layer Security (TLS) Protocol Version 1.2 (incorporated by reference, see § 395.38). Wireless Data Transfer tests will be conducted and detailed instructions will be provided upon FMCSA publishing specific test cases | DIALOG ELD will monitor and report malfunction data based on section 4.6 ELD’s Self-Monitoring of Required Functions table 4: P - “Power compliance” malfunction E - “Engine synchronization compliance” malfunction T - “Timing compliance” malfunction L - “Positioning compliance” malfunction R - “Data recording compliance” malfunction S - “Data transfer compliance” malfunction O - “Other” ELD detected malfunction WHAT DOES THE DRIVER NEED TO DO IF THE ELD IS MALFUNCTIONING? 1. Provide written notice to fleet management within 24 hours of malfunction discovery. 2. Keep paper logs for that day and until ELD is repaired or replaced. WHAT DOES THE FLEET NEED TO DO IF THE ELD IS MALFUNCTIONING? 1. A motor carrier must take action to correct the malfunction of the ELD within 8 days of discovery of the malfunction or a driver’s notification to the motor carrier, whichever occurs first. 2. Upon notification by fleet manager, DIALOG ELD will send a new device. 3. If a motor carrier needs a time extension, they must notify the FMCSA Division Administrator for the State of the motor carrier’s principal place of business within five days after a driver notifies the motor carrier according to the guidelines set forth in § 395.34 (2). | We have used the suggested Electronic Logging Device (ELD) Test Plan and Procedures document, version 2.0 dated 10/17/2016 provided by FMCSA to conduct testing of DIALOG ELD. Upon completion of necessary tests outlined in the above named document we certify that DIALOG ELD meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. Tests under the following categories have been conducted and passed (P): Accounts, Inputs, Vehicle, Interface, Processing, Monitoring, Recording, Outputs, Data Transfer. | |
| Digilog | DGLG111 | 215 or Higher | DGLG23 | Download | Download | DIGILOG | 8484335225 | digilogllc@gmail.com | https://digilogllc.com/ | 11 LOCKLIN CT , SAYREVILLE/ NJ/ 08872 | Local (USB, Bluetooth) , Telematic (Web Service, Email) | To submit the Output File to an authorized safety official, the driver selects the “Export ELD Data File” from the Logbook screen. The driver, then, will select one of the following methods: - FMCSA web service: This option securely communicates to FMCSA's end-point ad obtains submission ID. - ELD Email Interface: This option transfer an encrypted email to FMCSA email address | Low battery, network disconnection, low internal memory space, ECM data transfer failure, location sensor failure. In addition, the following malfunctions are detected (and appropriate records created) by the DGLG23: - Power data diagnostic (diagnostic - 1) - Engine synchronization data diagnostic (diagnostic - 2) - Missing required data elements (diagnostic - 3) - Data transfer (diagnostic - 4) - Unidentified driving records data diagnostic (diagnostic - 5) - Other ELD diagnostics (diagnostic - 6 - Power compliance (malfunction - P) - Engine synchronization compliance (malfunction - E) - Timing compliance (malfunction - T) - Positioning compliance (malfunction - L) - Data recording compliance (malfunction - R) - Data transfer compliance (malfunction - S) - Other ELD malfunctions (malfunction - O) | The Digilog (DGLG23) was tested on a diverse range of CMVs from different manufacturers and models as well drivers with different experience and backgrounds. Tests were also performed on different environments (indoor, outdoor, inside and outside CMVs). Procedures and areas of examinations were followed according to the “ELD Test Plan and Procedures” version 1.0 document released by FMCSA on April 25th 2016. The Requirement Traceability Matrix (RTM) was used and fully verified to ensure ELD compliance. Corrective actions and regression tests were made on all Failed test results. |
| DIGITAL ELD | DTL | 2.13.17 | DTL792 | Download | Download | Digital ELD LLC | 5594160153 | contact@digitaleld.com | http://www.DigitalELD.com | 3356 Rivermont Street , West Sacramento, CA, 95691 | Telematic (Web Service, Email) | DIGITAL ELD, or Electronic Logging Device, is a tool that offers a comprehensive overview of a driver's records during a roadside inspection. Not only does it provide this information within the app, but it also facilitates the transfer of telematics data through email or web services. The DOT Inspection mode allows the driver to choose the method that works best for them. To transfer ELD records through Web services, the driver needs to access the "DOT Inspection" menu and select the "Send Logs" option. Then, they should choose Web Service as the Data Transfer Type and click the "SEND" button. Similarly, to transfer ELD records via Email, the driver should follow the same steps but select Email as the Data Transfer Type before clicking the "SEND" button. | The DIGITAL ELD system ensures compliance with technical requirements, identifies malfunctions and data inconsistencies, and maintains records of such occurrences. Compliance malfunctions and diagnostic events are classified with specific codes, including P for "Power compliance" malfunction, E for "Engine synchronization compliance" malfunction, T for "Timing compliance" malfunction, L for "Positioning compliance" malfunction, R for "Data recording compliance" malfunction, S for "Data transfer compliance" malfunction, O for "Other" ELD-detected malfunctions, 1 for "Power data diagnostic" event, 2 for "Engine synchronization data diagnostic" event, 3 for "Missing required data elements data diagnostic" event, 4 for "Data transfer data diagnostic" event, 5 for "Unidentified driving records data diagnostic" event, and 6 for "Other" ELD-identified diagnostic events. The DIGITAL ELD Malfunction and Diagnostic Event Records document all malfunctions that occurred during the relevant time period. Active malfunctions are communicated to all drivers who may use the ELD. | DIGITAL ELD has been thoroughly tested to ensure compliance with all the functional requirements outlined in Title 49, Part 395 of Section 4.9.1, Appendix A, Subpart B. DIGITAL ELD can confidently certify that our ELD product adheres to all the necessary ELD regulations. |
| Digital Fleet | DF-ELD | 8.5.0 and newer | DIGI05 | Download | Download | Digital Fleet, LLC | (630) 518-4606 | info@digitalfleet.com | https://www.digitalfleet.com/ | 350 N Orleans St #9000N, Chicago, IL 60654 | Our ELD supports data transfer by email or web services. Step 1: Select the "Transfer ELD Records" button in the ELD Screen to initiate a data transfer. Step 2: Under the "Transfer Records to the FMCSA" section, enter the Output File Comment as required. Step 3: Select desired data transfer mechanism. Step 4: Select "Transfer Records" to collect and transmit records. | Power compliance malfunction - Triggered if power compliance incidents result in a driving time understatement of 30 minutes or more on the ELD over a 24 hour period across all driver profiles. Engine synchronization compliance malfunction - Triggered when we are unable to receive required engine data for a combined total of 30 or more minutes over a 24 hour period. Timing compliance malfunction - Triggered when it is determined that the system time is more than 10 minutes off from UTC time. Positioning compliance malfunction - Triggered when we are unable to receive valid GPS data for a combined total of 60 or more minutes over a 24 hour period. Data recording compliance malfunction - Triggered when the ELD system is unable to record new data. Data transfer compliance malfunction - Triggered when the ELD system is unable to perform a data transfer to the FMCSA for more than 7 consecutive days. | Digital Fleet has tested the Electronic Logging Device functionality pursuant to FMCSA Electronic Logging Device (ELD) Test Plans and Procedures version 2.1 and verified the product meets the requirements outlined in FMCSA Section 49 CFR 395.8 Subpart B. In accordance with section 1.5.1 Record Retention of the Test Plans and Procedures document, records of testing will be maintained for a period of two (2) years. | |
| Digital Fleet | DF-ELD | 5.3.0 and newer | DIGI05 | Download | Download | Digital Fleet, LLC | (630) 518-4606 | info@digitalfleet.com | https://www.digitalfleet.com/ | 350 N Orleans St #9000N, Chicago, IL 60654 | Our ELD supports data transfer by email or web services. Step 1: Select the "Transfer ELD Records" button in the ELD Screen to initiate a data transfer. Step 2: Enter Output File Comment as required. Step 3: Select desired data transfer mechanism. Step 4: Select "Transfer Records to FMCSA" to collect and transmit records. | Power compliance malfunction - Triggered if power compliance incidents result in a driving time understatement of 30 minutes or more on the ELD over a 24 hour period across all driver profiles. Engine synchronization compliance malfunction - Triggered when we are unable to receive required engine data for a combined total of 30 or more minutes over a 24 hour period. Timing compliance malfunction - Triggered when it is determined that the system time is more than 10 minutes off from UTC time. Positioning compliance malfunction - Triggered when we are unable to receive valid GPS data for a combined total of 60 or more minutes over a 24 hour period. Data recording compliance malfunction - Triggered when the ELD system is unable to record new data. Data transfer compliance malfunction - Triggered when the ELD system is unable to perform a data transfer to the FMCSA for more than 7 consecutive days. | Digital Fleet has tested the Electronic Logging Device functionality pursuant to FMCSA Electronic Logging Device (ELD) Test Plans and Procedures version 2.1 and verified the product meets the requirements outlined in FMCSA Section 49 CFR 395.8 Subpart B. In accordance with section 1.5.1 Record Retention of the Test Plans and Procedures document, records of testing will be maintained for a period of two (2) years. | |
| Direct Logs | DET | 2.21 and up | DET972 | Download | Download | Direct Logs Inc | 513 305 3639 | info@directlogs.org | http://directlogs.com | 6377 Ashdale ct, Liberty Township OH 45044 | Telematic (Web Service, Email) | DIRECT LOGS is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | DIRECT LOGS monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The DIRECT LOGS Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on DIRECT LOGS during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD | DIRECT LOGS meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. DIRECT LOGS was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. |
| DispatchCrude.com | DCT-317 | 4.7.54.1 | DCT317 | Download | Download | Capital Technology Solutions | 8123034357 | Support@dccloud.net | http://dispatchcrude.com/ | 1112 South Villa Drive, Evansville/IN/47714 | Using Web Services and/or Email, DC submits CSV file data to FMCSA as required in the mandate. This has already been tested working with the FMCSA ELD Team. | Code Description 1 "Power data diagnostic" event 2 "Engine synchronization data diagnostic" event 3 "Missing required data elements data diagnostic" event 4 "Data transfer data diagnostic" event 5 "Unidentified driving record data diagnostic" event 6 "Other" ELD identified diagnostic event P "Power compliance" malfunction E "Engine synchronization compliance" malfunction T "Timing compliance" malfunction L "Positioning compliance" malfunction R "Data recording compliance" malfunction S "Data transfer compliance" malfunction O "Other" ELD detected malfunction | We have worked through the details of the mandate throughout the year 2017, and along with final testing and certification with the FMCSA, are happy to offer our fully integrated ELD solution. DC Enterprise integrates compliance documentation, HOS, ELD, driver scheduling, and order hueristics, for a totally integrated and intelligent solution. | |
| DRAGON ELD | DRA | 2.13.15 and later | DRA782 | Download | Download | Dragon ELD | (708) 778-3616 | info@dragoneld.com | http://dragoneld.com | 18 West 140 Butterfield Rd, Oakbrook Terrace/IL/60181 | Telematic (Web Service, Email) | DRAGON ELD system uses electronic data transfer to send driver logs. Drivers can also use the mobile app to send logs via email or web services as needed. In order to send the logs to DOT, the driver must go to “DOT Inspection Mode”, click “Send”, choose the appropriate transfer method (Email or Web Service), enter the personal officer code and click “Send Logs”. | DRAGON ELD (Electronic Logging Device) system is designed to ensure compliance with regulations and improve safety on the road. It continuously monitors for malfunctions and records any detected issues. As per the guidelines outlined in Appendix A, section 4.6, it also has the capability to self-diagnose and troubleshoot. The driver will be alerted visually in case of any malfunctions detected. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. | DRAGON ELD system complies with the technical specifications outlined in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. It has undergone extensive testing to ensure compliance with FMCSA regulations, following the steps and testing procedures outlined in the Electronic Logging Device Test Plan and Procedures Version 2.0. |
| DREAM ELD | DRAM | 2.24.9 | DRS126 | Download | Download | DREAM ELD | (800) 782-9079 | support@dreameld.com | http://dreameld.com | 371 E Street Road, Feasterville PA 19053 | Telematic (Web Service, Email) | DREAM ELD system allows for wireless web services and email as ways to transfer telematics data, by pressing "Send" button in the dedicated DOT Inspection Mode. If a driver doesn't have internet, they can view logs on the mobile app. As per section 4.10 of the ELD mandate, the DOT Inspection Mode shows RODS for the current 24 hours and the driver's logs for the past 7 days. | As per Appendix A, section 4.6, DREAM ELD electronic logging device is programmed to self-monitor and detect malfunctions. An example of this would be the ELD system displaying visual alerts to the driver for issues with engine synchronization, timing, positioning, or unidentified driving. | DREAM ELD has undergone rigorous testing in accordance with the FMCSA's Test Plan and Procedures. DREAM ELD certifies that the test results confirm that the ELD conforms to the Functional Specifications for the ELD product. |
| DREAM ELD PRO | IOS2050 | 1.1.1 | DREM30 | Download | Download | DREAM ELD | (800) 782-9079 | support@dreameld.com | http://dreameld.com | 371 E Street Road, Feasterville PA 19053 | Telematic (Web Service, Email) | DREAM ELD PRO is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | DREAM ELD PRO monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The DREAM ELD PRO Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on DREAM ELD PRO during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | DREAM ELD PRO meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. DREAM ELD PRO was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. |
| Drive ELD | driveeld_2017_1.0 | 4.5+ | 100DE1 | Download | Download | Drive ELD LLC | 866-623-7483 | contact@drive-eld.com | https://www.drive-eld.com/ | 201 East Washington Street, Suite 1302, Iowa City, Iowa, 42240 | To transfer data using the DriveELD application. A user must log into the smartphone app on their phone or mobile device. Immediately upon logging in, a user can access the menu by pressing the button in the upper left corner. The menu icon is labeled, “menu” and is represented by a standard hamburger menu icon (i.e. three horizontal lines). A drawer will open, DOT Inspection is one of the options available in the menu. The user clicks DOT Inspection. The user has two options “View Logs on Phone” or “Transfer to FMCSA”. The user should select “Transfer to FMCSA” and click the “confirm” button in the upper right hand corner of the screen. On the next screen, the user selects either web services or email as their certified transfer method. Below these options is a text box where users can type in comments from the enforcement official, this is the Output File Comment. The user then selects “Send”. The user’s device communicates with the DriveELD server and the server sends the output file using the mechanism selected on the mobile device. | 4.6.1.1. (P / power compliance malfunction): An ELD must set a power compliance malfunction if the power data diagnostics event described in paragraph 4.6.1.1(a) of this appendix indicates an aggregated in-motion driving time understatement of 30 minutes or more on the ELD over a 24-hour period across all driver profiles, including the unidentified driver profile. 4.6.1.2 (E / Engine Synchronization Compliance Malfunction): An ELD must set an engine synchronization compliance malfunction if connectivity to any of the required data sources specified in section 4.3.1 of this appendix is lost for more than 30 minutes during a 24-hour period aggregated across all driver profiles, including the unidentified driver profile. 4.6.1.3 (T / Timing Compliance Malfunction): The ELD must periodically cross-check its compliance with the requirement specified in section 4.3.1.5 of this appendix with respect to an accurate external UTC source and must record a timing compliance malfunction when it can no longer meet the underlying compliance requirement. 4.6.1.4 (L / Position Compliance Malfunction): ELD records requiring location information must use the last valid position measurement and include the latitude/longitude coordinates and distance traveled, in miles, since the last valid position measurement. An ELD must monitor elapsed time during periods when the ELD fails to acquire a valid position measurement within 5 miles of the CMV’s movement. When such elapsed time exceeds a cumulative 60 minutes over a 24 hour period, the ELD must set and record a positioning compliance malfunction. 4.6.1.5 (R / Data Recording Compliance Malfunction): An ELD must monitor its storage capacity and integrity and must detect a data recording compliance malfunction if it can no longer record or retain required events or retrieve recorded logs that are not otherwise catalogued remotely by the motor carrier. 4.6.1.7 (S / Data Transfer Compliance Malfunction): (a) An ELD must implement in-service monitoring functions to verify that the data transfer mechanism(s) described in section 4.9.1 of this appendix are continuing to function properly. An ELD must verify this functionality at least once every 7 days. These monitoring functions may be automatic or may involve manual steps for a driver. (b) If the monitoring mechanism fails to confirm proper in-service operation of the data transfer mechanism(s), an ELD must record a data transfer data diagnostic event and enter an unconfirmed data transfer mode. (c) After an ELD records a data transfer data diagnostic event, the ELD must increase the frequency of the monitoring function to check at least once every 24- hour period. If the ELD stays in the unconfirmed data transfer mode following the next three consecutive monitoring checks, the ELD must detect a data transfer compliance malfunction | The product was tested using the FMCSA’s eldtestplanandprocedures07-18-201721-all-chapters.pdf as a template. Tests were performed using the app, Pacific Track hardware, a CMV simulator, and vehicles with OBDII and j1939 protocols. | |
| Driver•i | D430 | 3.5.21.rc.7 and up | DRI430 | Download | Download | Netradyne | 1-833-476-9663 | driveri@netradyne.com | https://netradyne.com | 9171 Towne Centre Drive, Suite 110, San Diego, CA 92122 | Geotab Drive supports the telematics (electronic) data transfer method via wireless Web services and email. To enable this during a roadside inspection, the following steps will apply: 1) Upon launching the Geotab Drive, select HOS from the Dashboard. 2) From the top bar, select the Options tab and scroll to the bottom of the page. 3) Select the Transfer button next to Transfer logs, then choose between email or Web services. 4) Drivers may need to enter an output file comment provided by the inspector into the textbox when prompted. This is also outlined in this document: https://goo.gl/8x2PgF | ELD Malfunctions Malfunction Code P: Power data malfunction: An ELD must monitor the data it receives from the engine ECM or alternative sources, and data record history to identify instances when it might not have complied with the power requirements. Driver’s actions for when a power data malfunction occurs: This may be caused by an intermittent or disconnected connection to the vehicle ECM. This is likely due to an install issue.Contact your carrier to get the install inspected if you’re unable to check yourself. Once investigated and the problem is found you may clear this event. Malfunction Code E: Engine synchronization compliance malfunction: An ELD must set an engine synchronization compliance malfunction, if connectivity to any of the required data sources is lost for more than 30 minutes during a 24-hour period aggregated across all driver profiles. Driver’s actions for when a engine synchronization compliance malfunction occurs: This may be caused by an intermittent or disconnected connection to the vehicle ECM. This is likely due to an install issue. Contact your carrier to get the install inspected if you’re unable to check yourself. Once investigated and the problem is found you may clear this event. Malfunction Code T: Timing compliance malfunction: The ELD must periodically cross-check its time with an external UTC source, and must record a timing compliance malfunction when it can no longer meet the underlying timing requirement of less than 10 minutes’ time deviation. Driver’s actions for when a timing compliance malfunction occurs: Check your mobile device’s phone time. Ensure it is set to acquire time automatically. Once investigated and the problem is found you may clear this event. Malfunction Code L: Positioning Compliance malfunction: An ELD must monitor elapsed time during periods when the ELD fails to acquire a valid position measurement within five miles of the CMV’s movement. When such elapsed time exceeds a cumulative 60 minutes over a 24-hour period, the ELD must set and record a positioning compliance malfunction. Driver’s actions for when a positioning Compliance malfunction occurs: This can be caused by temporary or permanent loss of GPS by the Driver•i device. Contact your carrier to get the install inspected. If problem still persists, replace the Driver•i device.Once investigated and the problem is found you may clear this event. Malfunction Code R: Data recording compliance malfunction: An ELD must monitor its storage capacity and integrity and must detect a data recording compliance malfunction if it can no longer record or retain required events, or retrieve recorded logs that are not otherwise cataloged remotely by the motor carrier. Driver’s actions for when a data recording compliance malfunction occurs: Contact your carrier to get in touch with Support as soon as possible.Once investigated and the problem is found you may clear this event. Malfunction Code S: Data transfer compliance malfunction: After an ELD records a data transfer data diagnostic event, the ELD must increase the frequency of the monitoring function to check at least once every 24-hour period. If the ELD stays in the unconfirmed data transfer mode following the next three consecutive monitoring checks, the ELD must detect a data transfer compliance malfunction. Driver’s actions for when a data transfer compliance malfunction occurs: Check your internet connection. If problem persists, contact your carrier. Once investigated and the problem is found you may clear this event. Malfunction Code O: “Other” ELD identified malfunction: The other ELD identified malfunction is not supported. Diagnostic Code: 1 Power data diagnostic: An ELD must monitor the data it receives from the engine ECM and data record history to identify instances when it may not have complied with the power requirements. Driver’s actions for when a power data diagnostic occurs: This may be caused by an intermittent or disconnected connection to the vehicle ECM. This is likely due to an install issue. Once investigated and the problem is resolved, the system will auto clear the event. Diagnostic Code: 2 Engine synchronization diagnostic: An ELD is required to establish a link to the engine ECM,and must record an engine synchronization data diagnostics event, when it no longer can acquire values for the ELD parameters required for records within five seconds. Driver’s actions for when a engine synchronization diagnostic occurs: This may be caused by an intermittent or disconnected connection to the vehicle ECM. This is likely due to an install issue. This may also be caused if the ELD is unable to pick up the required engine data from the vehicle ECM.Contact your carrier if the problem persists. Once investigated, and the problem is resolved, the system will auto clear the event. Diagnostic Code: 3 Missing required data elements data diagnostic: An ELD must monitor the completeness of the ELD event record information in relation to the required data elements for each event type, and must record a missing data element and data diagnostics event for the driver, if any required field is missing at the time of recording. Driver’s actions for when a missing required data elements data diagnostic occurs:This can be caused by the creation of a manual log by the driver when there is temporary loss of GPS by the Driver•i device. If the driver does not enter an address manually when prompted by the “Where was this?” message, this diagnostic will be created. It can be resolved by selecting the “Where was this?” associated with the record and manually entering the missing data. Once investigated, and the problem is resolved, the system will auto clear the event. Diagnostic Code: 4 Data transfer data diagnostic: An ELD must implement in-service monitoring functions to verify that the data transfer mechanism(s) are continuing to function properly. An ELD must verify this functionality at least once every seven days. Driver’s actions for when a data transfer data diagnostic occurs: Check your internet connection. If problem persists, contact your carrier. Once investigated, and the problem is resolved, the system will auto clear the event. Diagnostic Code: 5 Unidentified driving records data diagnostic: If more than 30 minutes of driving in a 24-hour period shows unidentified driver on the ELD, the ELD must detect and record an unidentified driving record data diagnostic event, and the data diagnostic indicator must be turned on for all drivers logged in to that ELD for the current 24-hour period and the following seven days. Driver’s actions for when an unidentified driving records data occurs: Review all unassigned logs when logging in or logging out of the vehicle and ensure you have claimed any logs that may be applicable to yourself. If the unassigned logs are not yours, you can ignore this diagnostic event.Please note this event will automatically clear itself as logs get claimed. Diagnostic Code: 6 “Other” ELD identified diagnostic: The other ELD identified is not supported. Driver’s actions for when an “other” ELD identified diagnostic occurs: The other ELD identified is not supported. This is also outlined in this document: https://goo.gl/b7Jyof | The product was tested using the FMCSA’s recommended testing procedures, supplemented by Netradyne and Geotab internal testing procedures. | |
| Driver•i | D210 | 2.5.18 and up | DRI210 | Download | Download | Netradyne | 1-833-476-9663 | driveri@netradyne.com | https://netradyne.com | 9171 Towne Centre Drive, Suite 110, San Diego, CA 92122 | Geotab Drive supports the telematics (electronic) data transfer method via wireless Web services and email. To enable this during a roadside inspection, the following steps will apply: 1) Upon launching the Geotab Drive, select HOS from the Dashboard. 2) From the top bar, select the Options tab and scroll to the bottom of the page. 3) Select the Transfer button next to Transfer logs, then choose between email or Web services. 4) Drivers may need to enter an output file comment provided by the inspector into the textbox when prompted. This is also outlined in this document: https://goo.gl/8x2PgF | ELD Malfunctions Malfunction Code P: Power data malfunction: An ELD must monitor the data it receives from the engine ECM or alternative sources, and data record history to identify instances when it might not have complied with the power requirements. Driver’s actions for when a power data malfunction occurs: This may be caused by an intermittent or disconnected connection to the vehicle ECM. This is likely due to an install issue.Contact your carrier to get the install inspected if you’re unable to check yourself. Once investigated and the problem is found you may clear this event. Malfunction Code E: Engine synchronization compliance malfunction: An ELD must set an engine synchronization compliance malfunction, if connectivity to any of the required data sources is lost for more than 30 minutes during a 24-hour period aggregated across all driver profiles. Driver’s actions for when a engine synchronization compliance malfunction occurs: This may be caused by an intermittent or disconnected connection to the vehicle ECM. This is likely due to an install issue. Contact your carrier to get the install inspected if you’re unable to check yourself. Once investigated and the problem is found you may clear this event. Malfunction Code T: Timing compliance malfunction: The ELD must periodically cross-check its time with an external UTC source, and must record a timing compliance malfunction when it can no longer meet the underlying timing requirement of less than 10 minutes’ time deviation. Driver’s actions for when a timing compliance malfunction occurs: Check your mobile device’s phone time. Ensure it is set to acquire time automatically. Once investigated and the problem is found you may clear this event. Malfunction Code L: Positioning Compliance malfunction: An ELD must monitor elapsed time during periods when the ELD fails to acquire a valid position measurement within five miles of the CMV’s movement. When such elapsed time exceeds a cumulative 60 minutes over a 24-hour period, the ELD must set and record a positioning compliance malfunction. Driver’s actions for when a positioning Compliance malfunction occurs: This can be caused by temporary or permanent loss of GPS by the Driver•i device. Contact your carrier to get the install inspected. If problem still persists, replace the Driver•i device.Once investigated and the problem is found you may clear this event. Malfunction Code R: Data recording compliance malfunction: An ELD must monitor its storage capacity and integrity and must detect a data recording compliance malfunction if it can no longer record or retain required events, or retrieve recorded logs that are not otherwise cataloged remotely by the motor carrier. Driver’s actions for when a data recording compliance malfunction occurs: Contact your carrier to get in touch with Support as soon as possible.Once investigated and the problem is found you may clear this event. Malfunction Code S: Data transfer compliance malfunction: After an ELD records a data transfer data diagnostic event, the ELD must increase the frequency of the monitoring function to check at least once every 24-hour period. If the ELD stays in the unconfirmed data transfer mode following the next three consecutive monitoring checks, the ELD must detect a data transfer compliance malfunction. Driver’s actions for when a data transfer compliance malfunction occurs: Check your internet connection. If problem persists, contact your carrier. Once investigated and the problem is found you may clear this event. Malfunction Code O: “Other” ELD identified malfunction: The other ELD identified malfunction is not supported. Diagnostic Code: 1 Power data diagnostic: An ELD must monitor the data it receives from the engine ECM and data record history to identify instances when it may not have complied with the power requirements. Driver’s actions for when a power data diagnostic occurs: This may be caused by an intermittent or disconnected connection to the vehicle ECM. This is likely due to an install issue. Once investigated and the problem is resolved, the system will auto clear the event. Diagnostic Code: 2 Engine synchronization diagnostic: An ELD is required to establish a link to the engine ECM,and must record an engine synchronization data diagnostics event, when it no longer can acquire values for the ELD parameters required for records within five seconds. Driver’s actions for when a engine synchronization diagnostic occurs: This may be caused by an intermittent or disconnected connection to the vehicle ECM. This is likely due to an install issue. This may also be caused if the ELD is unable to pick up the required engine data from the vehicle ECM.Contact your carrier if the problem persists. Once investigated, and the problem is resolved, the system will auto clear the event. Diagnostic Code: 3 Missing required data elements data diagnostic: An ELD must monitor the completeness of the ELD event record information in relation to the required data elements for each event type, and must record a missing data element and data diagnostics event for the driver, if any required field is missing at the time of recording. Driver’s actions for when a missing required data elements data diagnostic occurs:This can be caused by the creation of a manual log by the driver when there is temporary loss of GPS by the Driver•i device. If the driver does not enter an address manually when prompted by the “Where was this?” message, this diagnostic will be created. It can be resolved by selecting the “Where was this?” associated with the record and manually entering the missing data. Once investigated, and the problem is resolved, the system will auto clear the event. Diagnostic Code: 4 Data transfer data diagnostic: An ELD must implement in-service monitoring functions to verify that the data transfer mechanism(s) are continuing to function properly. An ELD must verify this functionality at least once every seven days. Driver’s actions for when a data transfer data diagnostic occurs: Check your internet connection. If problem persists, contact your carrier. Once investigated, and the problem is resolved, the system will auto clear the event. Diagnostic Code: 5 Unidentified driving records data diagnostic: If more than 30 minutes of driving in a 24-hour period shows unidentified driver on the ELD, the ELD must detect and record an unidentified driving record data diagnostic event, and the data diagnostic indicator must be turned on for all drivers logged in to that ELD for the current 24-hour period and the following seven days. Driver’s actions for when an unidentified driving records data occurs: Review all unassigned logs when logging in or logging out of the vehicle and ensure you have claimed any logs that may be applicable to yourself. If the unassigned logs are not yours, you can ignore this diagnostic event.Please note this event will automatically clear itself as logs get claimed. Diagnostic Code: 6 “Other” ELD identified diagnostic: The other ELD identified is not supported. Driver’s actions for when an “other” ELD identified diagnostic occurs: The other ELD identified is not supported. This is also outlined in this document: https://goo.gl/b7Jyof | The product was tested using the FMCSA’s recommended testing procedures, supplemented by Netradyne and Geotab internal testing procedures. | |
| Driver•i | D215 | 4.5.19.rc.5 and up | DRI215 | Download | Download | Netradyne | 1-833-476-9663 | driveri@netradyne.com | https://netradyne.com | 9171 Towne Centre Drive, Suite 110, San Diego, CA 92122 | Geotab Drive supports the telematics (electronic) data transfer method via wireless Web services and email. To enable this during a roadside inspection, the following steps will apply: 1) Upon launching the Geotab Drive, select HOS from the Dashboard. 2) From the top bar, select the Options tab and scroll to the bottom of the page. 3) Select the Transfer button next to Transfer logs, then choose between email or Web services. 4) Drivers may need to enter an output file comment provided by the inspector into the textbox when prompted. This is also outlined in this document: https://goo.gl/8x2PgF | ELD Malfunctions Malfunction Code P: Power data malfunction: An ELD must monitor the data it receives from the engine ECM or alternative sources, and data record history to identify instances when it might not have complied with the power requirements. Driver’s actions for when a power data malfunction occurs: This may be caused by an intermittent or disconnected connection to the vehicle ECM. This is likely due to an install issue.Contact your carrier to get the install inspected if you’re unable to check yourself. Once investigated and the problem is found you may clear this event. Malfunction Code E: Engine synchronization compliance malfunction: An ELD must set an engine synchronization compliance malfunction, if connectivity to any of the required data sources is lost for more than 30 minutes during a 24-hour period aggregated across all driver profiles. Driver’s actions for when a engine synchronization compliance malfunction occurs: This may be caused by an intermittent or disconnected connection to the vehicle ECM. This is likely due to an install issue. Contact your carrier to get the install inspected if you’re unable to check yourself. Once investigated and the problem is found you may clear this event. Malfunction Code T: Timing compliance malfunction: The ELD must periodically cross-check its time with an external UTC source, and must record a timing compliance malfunction when it can no longer meet the underlying timing requirement of less than 10 minutes’ time deviation. Driver’s actions for when a timing compliance malfunction occurs: Check your mobile device’s phone time. Ensure it is set to acquire time automatically. Once investigated and the problem is found you may clear this event. Malfunction Code L: Positioning Compliance malfunction: An ELD must monitor elapsed time during periods when the ELD fails to acquire a valid position measurement within five miles of the CMV’s movement. When such elapsed time exceeds a cumulative 60 minutes over a 24-hour period, the ELD must set and record a positioning compliance malfunction. Driver’s actions for when a positioning Compliance malfunction occurs: This can be caused by temporary or permanent loss of GPS by the Driver•i device. Contact your carrier to get the install inspected. If problem still persists, replace the Driver•i device.Once investigated and the problem is found you may clear this event. Malfunction Code R: Data recording compliance malfunction: An ELD must monitor its storage capacity and integrity and must detect a data recording compliance malfunction if it can no longer record or retain required events, or retrieve recorded logs that are not otherwise cataloged remotely by the motor carrier. Driver’s actions for when a data recording compliance malfunction occurs: Contact your carrier to get in touch with Support as soon as possible.Once investigated and the problem is found you may clear this event. Malfunction Code S: Data transfer compliance malfunction: After an ELD records a data transfer data diagnostic event, the ELD must increase the frequency of the monitoring function to check at least once every 24-hour period. If the ELD stays in the unconfirmed data transfer mode following the next three consecutive monitoring checks, the ELD must detect a data transfer compliance malfunction. Driver’s actions for when a data transfer compliance malfunction occurs: Check your internet connection. If problem persists, contact your carrier. Once investigated and the problem is found you may clear this event. Malfunction Code O: “Other” ELD identified malfunction: The other ELD identified malfunction is not supported. Diagnostic Code: 1 Power data diagnostic: An ELD must monitor the data it receives from the engine ECM and data record history to identify instances when it may not have complied with the power requirements. Driver’s actions for when a power data diagnostic occurs: This may be caused by an intermittent or disconnected connection to the vehicle ECM. This is likely due to an install issue. Once investigated and the problem is resolved, the system will auto clear the event. Diagnostic Code: 2 Engine synchronization diagnostic: An ELD is required to establish a link to the engine ECM,and must record an engine synchronization data diagnostics event, when it no longer can acquire values for the ELD parameters required for records within five seconds. Driver’s actions for when a engine synchronization diagnostic occurs: This may be caused by an intermittent or disconnected connection to the vehicle ECM. This is likely due to an install issue. This may also be caused if the ELD is unable to pick up the required engine data from the vehicle ECM.Contact your carrier if the problem persists. Once investigated, and the problem is resolved, the system will auto clear the event. Diagnostic Code: 3 Missing required data elements data diagnostic: An ELD must monitor the completeness of the ELD event record information in relation to the required data elements for each event type, and must record a missing data element and data diagnostics event for the driver, if any required field is missing at the time of recording. Driver’s actions for when a missing required data elements data diagnostic occurs:This can be caused by the creation of a manual log by the driver when there is temporary loss of GPS by the Driver•i device. If the driver does not enter an address manually when prompted by the “Where was this?” message, this diagnostic will be created. It can be resolved by selecting the “Where was this?” associated with the record and manually entering the missing data. Once investigated, and the problem is resolved, the system will auto clear the event. Diagnostic Code: 4 Data transfer data diagnostic: An ELD must implement in-service monitoring functions to verify that the data transfer mechanism(s) are continuing to function properly. An ELD must verify this functionality at least once every seven days. Driver’s actions for when a data transfer data diagnostic occurs: Check your internet connection. If problem persists, contact your carrier. Once investigated, and the problem is resolved, the system will auto clear the event. Diagnostic Code: 5 Unidentified driving records data diagnostic: If more than 30 minutes of driving in a 24-hour period shows unidentified driver on the ELD, the ELD must detect and record an unidentified driving record data diagnostic event, and the data diagnostic indicator must be turned on for all drivers logged in to that ELD for the current 24-hour period and the following seven days. Driver’s actions for when an unidentified driving records data occurs: Review all unassigned logs when logging in or logging out of the vehicle and ensure you have claimed any logs that may be applicable to yourself. If the unassigned logs are not yours, you can ignore this diagnostic event.Please note this event will automatically clear itself as logs get claimed. Diagnostic Code: 6 “Other” ELD identified diagnostic: The other ELD identified is not supported. Driver’s actions for when an “other” ELD identified diagnostic occurs: The other ELD identified is not supported. This is also outlined in this document: https://goo.gl/b7Jyof | The product was tested using the FMCSA’s recommended testing procedures, supplemented by Netradyne and Geotab internal testing procedures. | |
| DriverBook ELD / Android | PT30 | 1.01.01 | DRBK07 | Download | Download | DriverBook ELD | +14132969988 | driverbookeld@gmail.com | http://driverbookeld.com/ | 386 Commonwealth Avenue, Springfield / MA / 01108 | To transfer your ELD records to authorized safety officials, use the DOT Inspect menu at the bottom of the app’s screen. The DOT Inspect menu allows drivers to manage all the collected data regarding a truck and a trip, certify records, and view uncertified records. Choose the date from a calendar to see all the truck and trip data recorded for this date. Tap the Start Inspection button to launch an inspection. If you need to send the records to an authorized safety official, tap the Transfer Data to Roadside Inspector button. After that you will see three options to choose from: 1. send the records to the FMCSA using wireless web services 2. send the records to the FMCSA email 3. send the records to the Roadside Inspector’s personal email Choosing the FMCSA email or server, you can add a comment and press Send. If you select a personal email, you’ll have an option to select the file format (PDF or CSV). The next step is to choose your county ruleset (USA or Canada), then enter your recipient's mailbox. Finally, you'll be asked to generate a report for today or generate a report for the last 8/15 days (depending on the country which ruleset you follow). Add a comment if needed and press Send. | Using the application you may notice how the M/D icon in the top left corner turns red. It happens when the system detects any malfunctions (the M red letter becomes red) or data diagnostics failures (the D letter becomes red). Malfunctions may also appear in the Logs menu as a malfunctioning event. As of the malfunctions you may face such types of issues: Engine synchronization Positioning compliance Data recording compliance Unregistered odometer change Timing compliance As of the data diagnostics problems you may face such types of issues: Engine synchronization Missing data elements Unidentified driving records Data transfer To see what an exact problem occurred, the driver should tap the M/D icon and check the details. | We confirm that the application was thoroughly tested by the team of QA engineers and proven to perform in compliance with FMCSA requirements. | |
| DriverBook ELD / iOS | PT30 | 1.01.01 | DRBK07 | Download | Download | DriverBook ELD | +14132969988 | driverbookeld@gmail.com | http://driverbookeld.com/ | 386 Commonwealth Avenue, Springfield / MA / 01108 | To transfer your ELD records to authorized safety officials, use the DOT Inspect menu at the bottom of the app’s screen. The DOT Inspect menu allows drivers to manage all the collected data regarding a truck and a trip, certify records, and view uncertified records. Choose the date from a calendar to see all the truck and trip data recorded for this date. Tap the Start Inspection button to launch an inspection. If you need to send the records to an authorized safety official, tap the Transfer Data to Roadside Inspector button. After that you will see three options to choose from: 1. send the records to the FMCSA using wireless web services 2. send the records to the FMCSA email 3. send the records to the Roadside Inspector’s personal email Choosing the FMCSA email or server, you can add a comment and press Send. If you select a personal email, you’ll have an option to select the file format (PDF or CSV). The next step is to choose your county ruleset (USA or Canada), then enter your recipient's mailbox. Finally, you'll be asked to generate a report for today or generate a report for the last 8/15 days (depending on the country which ruleset you follow). Add a comment if needed and press Send. | Using the application you may notice how the M/D icon in the top left corner turns red. It happens when the system detects any malfunctions (the M red letter becomes red) or data diagnostics failures (the D letter becomes red). Malfunctions may also appear in the Logs menu as a malfunctioning event. As of the malfunctions you may face such types of issues: Engine synchronization Positioning compliance Data recording compliance Unregistered odometer change Timing compliance As of the data diagnostics problems you may face such types of issues: Engine synchronization Missing data elements Unidentified driving records Data transfer To see what an exact problem occurred, the driver should tap the M/D icon and check the details. | We confirm that the iOS application was thoroughly tested by the team of QA engineers and proven to perform in compliance with FMCSA requirements. | |
| DriverConnect | DC 200 Fleet | Android6.4;iOS2.3 | RMDC00 | Download | Download | Rand McNally | 1-800-789-6277 | fleetsales@randmcnally.com | http://www.randmcnally.com/category/e-logs | 8770 W. Bryn Mawr Avenue, Chicago, IL 60631 | Telematic (Web Service, Email) | The supported data transfer mechanism is Telematics using both the Email and Web Services options. A detailed description for drivers is provided in the attached user guide. | Compliance malfunctions supported: Power Engine synchronization Timing Positioning Data recording Data transfer Other Data Diagnostic Events supported: Power Engine synchronization Missing required data elements Data transfer Unidentified driving records Other | Rand McNally has tested this product using the Version 2.0 of the ELD test specification published at https://www.fmcsa.dot.gov/sites/fmcsa.dot.gov/files/docs/ELD_Test_Plan_and_Procedures_All_Chapters_11_2_2016.pdf using the Telematics option with Email and Web Services and validation of ELD output file mechanism at https://csa.fmcsa.dot.gov/ELD/Tools/Validator. |
| DriverConnect | DC 200 Retail | Android6.4;iOS2.3 | RMDC00 | Download | Download | Rand McNally | 1-800-789-6277 | fleetsales@randmcnally.com | http://www.randmcnally.com/category/e-logs | 8770 W. Bryn Mawr Avenue, Chicago, IL 60631 | Telematic (Web Service, Email) | The supported data transfer mechanism is Telematics using both the Email and Web Services options. A detailed description for drivers is provided in the attached user guide. | Compliance malfunctions supported: Power Engine synchronization Timing Positioning Data recording Data transfer Other Data Diagnostic Events supported: Power Engine synchronization Missing required data elements Data transfer Unidentified driving records Other | Rand McNally has tested this product using the Version 2.0 of the ELD test specification published at https://www.fmcsa.dot.gov/sites/fmcsa.dot.gov/files/docs/ELD_Test_Plan_and_Procedures_All_Chapters_11_2_2016.pdf using the Telematics option with Email and Web Services and validation of ELD output file mechanism at https://csa.fmcsa.dot.gov/ELD/Tools/Validator. |
| DriverConnect | VG 21 | Android6.6.1 | RMDC00 | Download | Download | Rand McNally | 1-800-789-6277 | fleetsales@randmcnally.com | http://www.randmcnally.com/category/e-logs | 8770 W. Bryn Mawr Avenue, Chicago, IL 60631 | Telematic (Web Service, Email) | The supported data transfer mechanism is Telematics using both the Email and Web Services options. A detailed description for drivers is provided in the attached user guide. | Compliance malfunctions supported: Power Engine synchronization Timing Positioning Data recording Data transfer Other Data Diagnostic Events supported: Power Engine synchronization Missing required data elements Data transfer Unidentified driving records Other | Rand McNally has tested this product using the Version 2.0 of the ELD test specification published at https://www.fmcsa.dot.gov/sites/fmcsa.dot.gov/files/docs/ELD_Test_Plan_and_Procedures_All_Chapters_11_2_2016.pdf using the Telematics option with Email and Web Services and validation of ELD output file mechanism at https://csa.fmcsa.dot.gov/ELD/Tools/Validator. |
| DriverConnect | DC 200S | Android6.3 | RMDC00 | Download | Download | Rand McNally | 1-800-789-6277 | fleetsales@randmcnally.com | http://www.randmcnally.com/category/e-logs | 8770 W. Bryn Mawr Avenue, Chicago, IL 60631 | Telematic (Web Service, Email) | The supported data transfer mechanism is Telematics using both the Email and Web Services options. A detailed description for drivers is provided in the attached user guide. | Compliance malfunctions supported: Power Engine synchronization Timing Positioning Data recording Data transfer Other Data Diagnostic Events supported: Power Engine synchronization Missing required data elements Data transfer Unidentified driving records Other | Rand McNally has tested this product using the Version 2.0 of the ELD test specification published at https://www.fmcsa.dot.gov/sites/fmcsa.dot.gov/files/docs/ELD_Test_Plan_and_Procedures_All_Chapters_11_2_2016.pdf using the Telematics option with Email and Web Services and validation of ELD output file mechanism at https://csa.fmcsa.dot.gov/ELD/Tools/Validator. |
| DriverConnect | ELD 50 6 pin | Android6.4;iOS2.3 | RMDC00 | Download | Download | Rand McNally | 1-800-789-6277 | fleetsales@randmcnally.com | http://www.randmcnally.com/category/e-logs | 8770 W. Bryn Mawr Avenue, Chicago, IL 60631 | Telematic (Web Service, Email) | The supported data transfer mechanism is Telematics using both the Email and Web Services options. A detailed description for drivers is provided in the attached user guide. | Compliance malfunctions supported: Power Engine synchronization Timing Positioning Data recording Data transfer Other Data Diagnostic Events supported: Power Engine synchronization Missing required data elements Data transfer Unidentified driving records Other | Rand McNally has tested this product using the Version 2.0 of the ELD test specification published at https://www.fmcsa.dot.gov/sites/fmcsa.dot.gov/files/docs/ELD_Test_Plan_and_Procedures_All_Chapters_11_2_2016.pdf using the Telematics option with Email and Web Services and validation of ELD output file mechanism at https://csa.fmcsa.dot.gov/ELD/Tools/Validator. |
| DriverConnect | ELD 50 9 pin | Android6.6.1;iOS2.6 | RMDC00 | Download | Download | Rand McNally | 1-800-789-6277 | fleetsales@randmcnally.com | http://www.randmcnally.com/category/e-logs | 8770 W. Bryn Mawr Avenue, Chicago, IL 60631 | Telematic (Web Service, Email) | The supported data transfer mechanism is Telematics using both the Email and Web Services options. A detailed description for drivers is provided in the attached user guide. | Compliance malfunctions supported: Power Engine synchronization Timing Positioning Data recording Data transfer Other Data Diagnostic Events supported: Power Engine synchronization Missing required data elements Data transfer Unidentified driving records Other | Rand McNally has tested this product using the Version 2.0 of the ELD test specification published at https://www.fmcsa.dot.gov/sites/fmcsa.dot.gov/files/docs/ELD_Test_Plan_and_Procedures_All_Chapters_11_2_2016.pdf using the Telematics option with Email and Web Services and validation of ELD output file mechanism at https://csa.fmcsa.dot.gov/ELD/Tools/Validator. |
| drivereldbook eld | DRS | 2.0 or higher | DRS137 | Download | Download | drivereldbook | 2678809255 | drivereldbook@gmail.com | www.drivereldbook.com | 9908 bustleton ave unit A11, Philadelphia PA 19115 | DRIVERELDBOOK ELD is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | DRIVERELDBOOK ELD monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The DRIVERELDBOOK ELD Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on DRIVERELDBOOK ELD during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | DRIVERELDBOOK ELD meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. DRIVERELDBOOK ELD was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| DriverLog | Piccolo BLE/USB | 3.0.7 and up | WLI001 | Download | Download | Wireless Links | 201 531 5906 | support@wlius.com | www.wlius.com | 1050 Wall St suite 340, Lyndhurst NJ 07071 | Telematic (Web Service, Email) | There is a one page document describing how the officer can enter “officer mode” by clicking on the icon on the top right “officer icon” present on all screens. Once in “officer mode” the Daily Header and Full Day ELD Record defined by the FMCSA are displayed. On the bottom of the page there is a button marked “send report.” Clicking this button brings up the window to email the report to any email address entered. It also features an option to submit the data to the FMCSA web services endpoint. This will utilize the SOAP protocol, per the FMCSA documentation, to transmit the ELD data file and the output file comment entered by the inspecting officer. | Each malfunction has been coded following the "Standard Coding for Required Compliance Malfunction and Data Diagnostic Event Detection" definitions regarding "Malfunction/Diagnostic Code", "Malfunction Description" and "Data Diagnostic Event." Power Compliance monitoring assures that the ELD will become fully functional within one minute of the engine on event and remain on as long as the vehicle's engine stays powered. Engine Synchronization monitoring determines our connection to the ECM. This alerts the driver if there is a loss of connectivity to the ECM. For Timing Compliance Monitoring, we periodically check UTC time via the internet. For Positioning Compliance the ELD records the location, and uses the last valid position measurement and includes the latitude and longitude coordinates and distance traveled in miles, since the last valid position measurement. We also measure the elapsed time during periods when the ELD does not require a valid position measurement within 5 miles. If the time exceeds 60 minutes in a 24 hour period, it is marked as a positioning compliance malfunction. An ELD monitors its storage capacity and integrity and detects data recording compliance malfunction if it can no longer record or retain required events or retrieve recorded logs that are not otherwise catalogued remotely by the motor carrier. The ELD monitors the completeness of the ELD event record information in relation to the required data elements for each event type and records a missing data elements data diagnostics event for the driver if any required field is missing at the time of recording. We check to make sure that our data transfer mechanism works properly at least once every 7 days. All Data Diagnostic events are handled similarly according to the mandate. | We certify that the our ELD application and related hardware have been tested to meet the FMCSA's test procedures except areas concerning the ELD Authentication Value, and the Registration ID and ELD Identifier that we can not acquire until we submit this form. |
| DriverLog | Piccolo Plus | 2.1.0 and up | WLI001 | Download | Download | Wireless Links | 201 531 5906 | support@wlius.com | www.wlius.com | 1050 Wall St suite 340, Lyndhurst NJ 07071 | Telematic (Web Service, Email) | The Driver or Officer presses the "Officer Icon" on the top right of the home screen. This brings up the "Officer View." Next click Send Report on the bottom of the screen. Enter the destination email and click "Send." | We developed DriverLog following the specifications of the final ruling. Every malfunction code and every diagnostic event has been tested with an ECM (Jbus) simulator at our lab and then we tested it driving in an SUV with the Piccolo Plus and BlueLink respectively connected to the ECM sending the data to the ELD . Every malfunction and/or diagnostic event is being registered with the respective code on the Officer screen and separately with full detailed explanation on the Driver Screen. Whenever a Diagnostic Event or Malfunction code occurs there is an alert and the officer icon changes from green to yellow or red depending on whether or not we are in or out of compliance. | We certify that our ELD applicatin and related hardware have been tested to meet the FMCSA's test procefures except areas concerning the ELD Authentication Value, the Registration ID, and the ELD Identifier that we can not acquire until this form is accepted and the Registration ID assigned. |
| DriverLog | BlueLink | 2.1.0 and up | WLI001 | Download | Download | Wireless Links | 201 531 5906 | support@wlius.com | www.wlius.com | 1050 Wall St suite 340, Lyndhurst NJ 07071 | Telematic (Web Service, Email) | When entering an inspection scenario, the driver follows the instructions provided on his printed one page manual which instructs the driver to press the "Officer Button" located on the top right of the DriverLog apps' home screen display. This will launch the Officer View. Following the guidance of the ELD section of the Federal Register...section "4.10.1. Data Transfer Mechanisms," we allow the officer to use both e-mail or Web Services to transfer the driver's data to an e-mail address or the the FMCSA's Web Service repository. Currently the e-mail is formatted exactly to section "4.10.1.2. Wireless Data Transfer Through Email" specifications stated in the Federal Register. Web Services are as fleshed out as possible and we are awaiting further instructions from the FMCSA to make this aspect fully functional. | Malfunction detection is robustly executed to contain all malfunction scenarios listed in "Table 4" of the Driver Log final rule. These malfunctions include, Power Compliance which monitors the Unidentified Driver activity. Engine Synchronization verifies that we are connected to the vehicle's ECM. Timing which validates successful synchronization with UTC time. Positioning continuously monitors the accuracy of our GPS data. Data Recording monitors available storage capacity on our device. Data Transfer checks at least once a week for connectivity to an online server. In addition to the FMCSA's required malfunction reports, our proprietary error checking, logs the wellness of the device and reports this data back to our support team for instant feedback. | We certify that the our ELD application and related hardware have been tested to meet the FMCSA's test procedures except areas concerning the ELD Authentication Value, and the Registration ID and ELD Identifier that we can not acquire until we submit this form. |
| driveTIME | Android & Geometris | 1.0.1905.190430 | DT0001 | Download | Download | Cartasite | 303-223-0240 | sales@cartasite.com | www.cartasite.com | 1123 Auraria Pkwy, Suite 200, Denver, CO 80204 | driveTIME provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. Selecting the Data Transfer button from the Main HOS Main Screen will display the list of supported data transfer options which are via Bluetooth, Email and USB. A Select Vehicle option is also available for selecting a vehicle upon performing the data transfer, this option enables driveTIME to produce a data file or a series of data files of ELD records for a subset of its vehicles used by the driver. Transfer via Bluetooth - this option enables the user to transfer files through Bluetooth. The ELD prompts for an output file comment which the driver may enter (optional). After the input, if Bluetooth is not yet turned on, a prompt will appear asking you to turn it on. You will then be asked to select the device name to which the data will be transmitted via Bluetooth. Transfer via Email - this option enables the user to transfer files through email. The ELD output file transferred is encrypted using AES-256 in FIPS Publication 197. Before sending, the ELD prompts for an output file comment which the driver may enter (optional). The device's default email application will then be opened before sending the email to which the data will be transferred. Transfer via USB - this option enables the user to transfer files through USB (external devices). However, prior to saving the driver’s ELD file to an external storage/device, the ELD re-authenticates the driver account by asking for its password. | The driveTIME ELD is capable of monitoring its compliance for various detectable malfunctions. At each instance when an ELD malfunction event is detected or cleared by the driveTIME ELD, the ELD records the event. The recorded malfunction events are inconsistencies found while monitoring the ELD against FMCSA compliance requirements. Malfunction occurrences are indicated in the application header and in the Android notification toolbar with the letter ‘M’, respectively. The following shows the list of detectable malfunctions: Power Malfunction Engine Synchronization Malfunction Timing Malfunction Position Malfunction Data Recording Malfunction Data Transfer Malfunction Once the Malfunctions indicator ‘M’ is tapped, a dialog will be displayed with a list of the detected malfunction events alongside a ‘Clear’ button for each event. Tapping the Clear button will clear out the detected malfunction event. | The driveTIME ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The driveTIME ELD was installed on various types and sizes of Android phones and tablets. Testing was performed through the use of a J1939 simulator and actual vehicles while having been connected to the Geometris engine connected devices. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the Hours of Service web application (portal) that can be accessed through a web browser. | |
| driveTIME ELD | iOS & Geometris | 1905.190415.1 | DT0001 | Download | Download | Cartasite | 303-223-0240 | sales@cartasite.com | www.cartasite.com | 1123 Auraria Pkwy, Suite 200, Denver, CO 80204 | driveTIME provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. Selecting the Data Transfer button from the Main HOS Main Screen will display the list of supported data transfer options which are via Bluetooth, Email and USB. A Select Vehicle option is also available for selecting a vehicle upon performing the data transfer, this option enables driveTIME to produce a data file or a series of data files of ELD records for a subset of its vehicles used by the driver. Transfer via Bluetooth - this option enables the user to transfer files through Bluetooth. The ELD prompts for an output file comment which the driver may enter (optional). After the input, if Bluetooth is not yet turned on, a prompt will appear asking you to turn it on. You will then be asked to select the device name to which the data will be transmitted via Bluetooth. Transfer via Email - this option enables the user to transfer files through email. The ELD output file transferred is encrypted using AES-256 in FIPS Publication 197. Before sending, the ELD prompts for an output file comment which the driver may enter (optional). The device's default email application will then be opened before sending the email to which the data will be transferred. Transfer via USB - this option enables the user to transfer files through USB (external devices). However, prior to saving the driver’s ELD file to an external storage/device, the ELD re-authenticates the driver account by asking for its password. | The driveTIME ELD is capable of monitoring its compliance for various detectable malfunctions. At each instance when an ELD malfunction event is detected or cleared by the driveTIME ELD, the ELD records the event. The recorded malfunction events are inconsistencies found while monitoring the ELD against FMCSA compliance requirements. Malfunction occurrences are indicated in the application header and in the iOS notification toolbar with the letter ‘M’, respectively. The following shows the list of detectable malfunctions: Power Malfunction Engine Synchronization Malfunction Timing Malfunction Position Malfunction Data Recording Malfunction Data Transfer Malfunction Once the Malfunctions indicator ‘M’ is tapped, a dialog will be displayed with a list of the detected malfunction events alongside a ‘Clear’ button for each event. Tapping the Clear button will clear out the detected malfunction event. | The driveTIME ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The driveTIME ELD was installed on various types and sizes of iOS phones and tablets. Testing was performed through the use of a J1939 simulator and actual vehicles while having been connected to the Geometris engine connected devices. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the Hours of Service web application (portal) that can be access through a web browser. | |
| DSG ELOGS | DSGLGS | 2.14.02 or above | DSL380 | Download | Download | DSG TRACKING LLC | 3217325454 | info@ds-group.us | http://dsgelogs.com | 10021 RANDAL WALK ST ORLANDO FL 32832, ORLANDO FL 32832 | Telematic (Web Service, Email) | Using the DSG ELOGS system, telematics data transfer is possible through email or web services. The driver can transfer logs by accessing the DOT Inspection Mode menu and clicking the "Send" button. Additionally, the driver can present the logs report to a DOT officer on their mobile device by utilizing a specific DOT Inspection Mode button. | The DSG ELOGS system ensures that technical requirements are met, recognizes malfunctions and data discrepancies, and documents such events. Compliance malfunctions and diagnostic events are coded using specific labels as following:: ➤ P for "Power compliance" malfunction, ➤ E for "Engine synchronization compliance" malfunction, ➤ T for "Timing compliance" malfunction, ➤ L for "Positioning compliance" malfunction, ➤ R for "Data recording compliance" malfunction, ➤ S for "Data transfer compliance" malfunction, ➤ O for "Other" ELD-detected malfunctions, ➤ 1 for "Power data diagnostic" event, ➤ 2 for "Engine synchronization data diagnostic" event, ➤ 3 for "Missing required data elements data diagnostic" event, ➤ 4 for "Data transfer data diagnostic" event, ➤ 5 for "Unidentified driving records data diagnostic" event, ➤ 6 for "Other" ELD-identified diagnostic events. The DSG ELOGS Malfunction and Diagnostic Event Records track all malfunctions that occurred during the applicable time frame, and active malfunctions are communicated to all ELD users. | According to FMCSA's testing procedures, DSG ELOGS underwent extensive testing to ensure compliance as an electronic logging system, which has been successfully completed. The system verifies that it adheres to the requirements of 49 CFR Part 395 Subpart B, which involves precise logging and transmission of hours of service data. |
| DSi eLogs | DSi eLogs-001 or higher | v4.6.0 or higher | DSIELD | Download | Download | Wynne Systems | 949-224-6300 | Marketing@wynnesystems.com | https://wynnesystems.com/products/logistics-solution/ | 2601 Main St, #270, Irvine, CA 92614 | Our product supports wireless transfer through web services, wireless services via email and USB2 1. DOT officer selects Export Logs from Inspection Mode screen 2. Transfer screen inputs: a. DOT officer selects Transfer method (email or USB) b. DOT officer selects PDF or CSV file c. DOT officer enters Output File Comment d. DOT officer selects OK 3. File is transfered | Power Compliance – Create a Power Compliance data diagnostic event if ELD does not meet Engine Power, Vehicle Motion, Vehicle Miles or Vehicle Engine Hours requirements. Create a Power Compliance malfunction when the aggregated in-motion driving time is understated by 30 minutes or more during a 24-hour period across all driver profiles, including the unidentified driver profile Engine Sync – Create an Engine Sync data diagnostic event when the ELD loses connection to the vehicle’s ECM. Create an Engine Sync malfunction when the connection to the ECM is lost for more than 30 minutes during a 24-hour period Timing Compliance – Create a Timing Compliance malfunction event when UTC time cannot be obtained Positioning Compliance – Monitors the elapsed time and distance between the last valid measurement point. Monitor the duration when a valid position measurement is not acquired within the most recent 5 miles of driving. Create a Positioning Compliance malfunction event when the elapsed time exceeds a cumulative 60 minutes over a 24-period since the last valid position measurement. Data Recording Compliance – Create a Data Recording Compliance malfunction when our app can no longer record or retain required events or retrieve recorded logs that do not reside on the motor carrier’s server. A Missing Required Data Elements data diagnostic event will be created when required data elements are missing from an ELD event. Unidentified Driver Profile – If unidentified driver mile records exist on an ELD, a new driver logging into the device will be prompted with a warning indicating the existence of new unidentified driver records. Create an Unidentified Driving Records data diagnostic event if more than 30 minutes of unidentified driving within a 24-hour period has occurred. Clear the Unidentified Driving Records data diagnostic event when the cumulative unidentified drive time drops below 15 minutes for the current 24 hour period + previous 7 days. Data Transfer Compliance – Monitor our data transfer mechanism. Create a Data Transfer Compliance data diagnostic event when data transfer mechanism does not function properly. Increase monitoring frequency to once every 24 hours. If the next 3 consecutive monitoring checks stay in unconfirmed data transfer mode then create a Data Transfer Compliance malfunction Other Technology – Visual indicators are used to inform the driver if the ELD is connected to the ECM and whether a malfunction or data diagnostic event has occurred. | We certify that we have tested this product and fulfilled the requirements as outlined in the Electronic Logging Device (ELD) Test Plan and Procedures which is published on the FMCSA website - FMCSA.dot.gov | |
| DT1000 | REV 8 | 6.08+ | DT1R08 | Download | Download | DriverTech LLC | 855-451-4621 | DTELD@DriverTech.com | https://www.drivertech.com/ | 1960 South Milestone Dr. #B, Salt Lake City, Utah 84104 | Telematics-type ELD supporting Web Services and Email. Tap HOS then OPTIONS Reference the OPTIONS tab when you are inspected and need to share your logs with enforcement. 1. Tap ENFORCEMENT VIEW before showing your device to law enforcement. You must certify all logs except for the current day’s log to enter ROADSIDE AUDIT mode 2. Tap YES when prompted to Require driver portal password to exit ‘Enforcement View Enter your password 3. Tap SEND LOGS TO ENFORCEMENT to send logs to law enforcement. a. Enter the file comment provided by the enforcement official, then tap SUBMIT b. Once the inspection is finished, tap BACK, then enter your DRIVER PORTAL PASSWORD to exit ENFORCEMENT VIEW | Malfunction/Diagnostic Code Malfunction Description P) Power compliance malfunction E) Engine synchronization compliance malfunction T) Timing compliance malfunction L) Positioning compliance malfunction R) Data recording compliance malfunction S) Data transfer compliance malfunction | DriverTech referenced Electronic Logging Device ELD Test Plan and Procedures Version 2.0 to ensure compliance with FMCSA regulations. | |
| DT4000 | REV 6 | 6.08.00 and Higher | DT4R06 | Download | Download | DriverTech LLC | 855-451-4621 | DTELD@DriverTech.com | https://www.drivertech.com/ | 1960 South Milestone Dr. #B, Salt Lake City, Utah 84104 | Telematics-type ELD supporting Web Services and Email. Tap HOS then OPTIONS Reference the OPTIONS tab when you are inspected and need to share your logs with enforcement. 1. Tap ENFORCEMENT VIEW before showing your device to law enforcement. You must certify all logs except for the current day’s log to enter ROADSIDE AUDIT mode 2. Tap YES when prompted to Require driver portal password to exit ‘Enforcement View Enter your password 3. Tap SEND LOGS TO ENFORCEMENT to send logs to law enforcement. a. Enter the file comment provided by the enforcement official, then tap SUBMIT b. Once the inspection is finished, tap BACK, then enter your DRIVER PORTAL PASSWORD to exit ENFORCEMENT VIEW | Malfunction/Diagnostic Code Malfunction Description P Power compliance malfunction E Engine synchronization compliance malfunction T Timing compliance malfunction L Positioning compliance malfunction R Data recording compliance malfunction S Data transfer compliance malfunction | DriverTech referenced Electronic Logging Device ELD Test Plan and Procedures Version 2.0 to ensure compliance with FMCSA regulations. | |
| DT4000 | REV 7 | 6.08.00 and Higher | DT4R07 | Download | Download | DriverTech LLC | 855-451-4621 | DTELD@DriverTech.com | https://www.drivertech.com/ | 1960 South Milestone Dr. #B, Salt Lake City, Utah 84104 | Telematics-type ELD supporting Web Services and Email. Tap HOS then OPTIONS Reference the OPTIONS tab when you are inspected and need to share your logs with enforcement. 1. Tap ENFORCEMENT VIEW before showing your device to law enforcement. You must certify all logs except for the current day’s log to enter ROADSIDE AUDIT mode 2. Tap YES when prompted to Require driver portal password to exit ‘Enforcement View Enter your password 3. Tap SEND LOGS TO ENFORCEMENT to send logs to law enforcement. a. Enter the file comment provided by the enforcement official, then tap SUBMIT b. Once the inspection is finished, tap BACK, then enter your DRIVER PORTAL PASSWORD to exit ENFORCEMENT VIEW | Malfunction/Diagnostic Code Malfunction Description P Power compliance malfunction E Engine synchronization compliance malfunction T Timing compliance malfunction L Positioning compliance malfunction R Data recording compliance malfunction S Data transfer compliance malfunction | DriverTech referenced Electronic Logging Device ELD Test Plan and Procedures Version 2.0 to ensure compliance with FMCSA regulations. | |
| DT4000 | REV 5 | 6.08.00 and Higher | DT4R05 | Download | Download | DriverTech LLC | 855-451-4621 | DTELD@DriverTech.com | https://www.drivertech.com/ | 1960 South Milestone Dr. #B, Salt Lake City, Utah 84104 | Telematics-type ELD supporting Web Services and Email. Tap HOS then OPTIONS Reference the OPTIONS tab when you are inspected and need to share your logs with enforcement. 1. Tap ENFORCEMENT VIEW before showing your device to law enforcement. You must certify all logs except for the current day’s log to enter ROADSIDE AUDIT mode 2. Tap YES when prompted to Require driver portal password to exit ‘Enforcement View Enter your password 3. Tap SEND LOGS TO ENFORCEMENT to send logs to law enforcement. a. Enter the file comment provided by the enforcement official, then tap SUBMIT b. Once the inspection is finished, tap BACK, then enter your DRIVER PORTAL PASSWORD to exit ENFORCEMENT VIEW | Malfunction/Diagnostic Code Malfunction Description P Power compliance malfunction E Engine synchronization compliance malfunction T Timing compliance malfunction L Positioning compliance malfunction R Data recording compliance malfunction S Data transfer compliance malfunction | DriverTech referenced Electronic Logging Device ELD Test Plan and Procedures Version 2.0 to ensure compliance with FMCSA regulations. | |
| DT4000 | REV 8 | 6.08+ | DT4R08 | Download | Download | DriverTech LLC | 855-451-4621 | DTELD@DriverTech.com | https://www.drivertech.com/ | 1960 South Milestone Dr. #B, Salt Lake City, Utah 84104 | Telematics-type ELD supporting Web Services and Email. Tap HOS then OPTIONS Reference the OPTIONS tab when you are inspected and need to share your logs with enforcement. 1. Tap ENFORCEMENT VIEW before showing your device to law enforcement. You must certify all logs except for the current day’s log to enter ROADSIDE AUDIT mode 2. Tap YES when prompted to Require driver portal password to exit ‘Enforcement View Enter your password 3. Tap SEND LOGS TO ENFORCEMENT to send logs to law enforcement. a. Enter the file comment provided by the enforcement official, then tap SUBMIT b. Once the inspection is finished, tap BACK, then enter your DRIVER PORTAL PASSWORD to exit ENFORCEMENT VIEW | Malfunction/Diagnostic Code Malfunction Description P Power compliance malfunction E Engine synchronization compliance malfunction T Timing compliance malfunction L Positioning compliance malfunction R Data recording compliance malfunction S Data transfer compliance malfunction | DriverTech referenced Electronic Logging Device ELD Test Plan and Procedures Version 2.0 to ensure compliance with FMCSA regulations. | |
| Dumax ELD | AT3646 | 1.1 | AT-000 | Download | Download | DUMAX GPS | 5129240447 | info@dumaxst.com | http://dumaxst.com | 106 EAST SIXTH STREET, SUITEE 900, AUSTIN, TX., 78701 | In order for the application to transfer data through Email Services the mobile User must click the Option "Send by Email" identified as a green button in the Binnacle tab of the main screen. After doing so, the device will creaft an email with the data in the XML format containing all the driver's information as well as other required information, such as Unidentified Drivers' records, Positioning of the vehicle during the time of duty of the User during the last number of days (according to the organizational number of days which may very from 7 to 8 in total) and the vehicle's information. If the user would like to retrieve the information through Web Services, the User may click the same button, but instead, select the tab "Send Through Web Services", the user will be prompted with a text box in which he must type the official's routing code. If the user has Internet connection, the data transfer will be made through the mobile phone to the FMCSA portal. | Malfunctiosn are recorded according to the Standard Coding Required for Compliance. They include Power Compliance Malfunction, Engine Syncrhonization Compliance Malfunctions and Timing Compliance Malfunctions; as well as Positioning Compliance Malfunction, Data Recording Malfunctions and Data Transfer Malfunctions. All of these, according to the rules regarding the vehicles' drivers responding or not to the ELD, the ELD having detected movement without proper management of the application and depending on the rules the driver is allowed to keep doing his or her duty. Data Recording compliance is checked through continous revision of data checksum of values. The data transfer malfunctions is registered when there are problems syncrhonizing data with the application and the required transfering. In the same manner, diagnostic events are registered prior to a malfunction code and the ELD registers a malfunction when they trespass the limits according to the rule. Unidentified driving records are registered whenever the device detects vehicle's movements for more than the specified amount of miles or minutes. These are registered and, whenever a driver is logged in to the application, is requested to review them until a driver claims them. Missing data elements diagnostics are registered when the device could not retrieve, transfer or calculate all the information required for all it's required functions. | I certify and declare under penalty of perjury that the foregoing is true and correct. Subscribed at Austin, State of Texas on behalf of DUMAX GPS that the model and version has been sufficiently tested to meet the functional requirements included in the technical specifications in the Appendix to subpart B of part 395, title 49 of the Code of Federal Regulations. | |
| Dumax ELD | PT30 | 1.0 | PT30-0 | Download | Download | DUMAX GPS | 5129240447 | info@dumaxst.com | http://dumaxst.com | 106 EAST SIXTH STREET, SUITEE 900, AUSTIN, TX., 78701 | In order for the application to transfer data through Email Services the mobile User must click the Option "Send by Email" identified as a green button in the Binnacle tab of the main screen. After doing so, the device will creaft an email with the data in the XML format containing all the driver's information as well as other required information, such as Unidentified Drivers' records, Positioning of the vehicle during the time of duty of the User during the last number of days (according to the organizational number of days which may very from 7 to 8 in total) and the vehicle's information. If the user would like to retrieve the information through Web Services, the User may click the same button, but instead, select the tab "Send Through Web Services", the user will be prompted with a text box in which he must type the official's routing code. If the user has Internet connection, the data transfer will be made through the mobile phone to the FMCSA portal. | Malfunctiosn are recorded according to the Standard Coding Required for Compliance. They include Power Compliance Malfunction, Engine Syncrhonization Compliance Malfunctions and Timing Compliance Malfunctions; as well as Positioning Compliance Malfunction, Data Recording Malfunctions and Data Transfer Malfunctions. All of these, according to the rules regarding the vehicles' drivers responding or not to the ELD, the ELD having detected movement without proper management of the application and depending on the rules the driver is allowed to keep doing his or her duty. Data Recording compliance is checked through continous revision of data checksum of values. The data transfer malfunctions is registered when there are problems syncrhonizing data with the application and the required transfering. In the same manner, diagnostic events are registered prior to a malfunction code and the ELD registers a malfunction when they trespass the limits according to the rule. Unidentified driving records are registered whenever the device detects vehicle's movements for more than the specified amount of miles or minutes. These are registered and, whenever a driver is logged in to the application, is requested to review them until a driver claims them. Missing data elements diagnostics are registered when the device could not retrieve, transfer or calculate all the information required for all it's required functions. | We certify the ELD Application is fully functional and provides reliable and accurate information; with proper mechanisms to avoid data tampering, modification or alteration in accordance to the FMCSA Electronic Logging Devices Rule. Thus providing a solid and proved solution to Log and Record Driver's Activities and Hour Violations as stipulated in the FMCSA rule. Under penalties of perjury, I, MARIA FERNANDA VILLARREAL AGUILAR, hereby certify on behalf of DUMAX GPS that ELD model FMB001 and version 1.0 has been sufficiently tested to meet the functional requirements included in the technical specifications in the Appendix to subpart B of part 395, title 49 of the Code of Federal Regulations, under the conditions in which the ELD would be used. | |
| Dumax ELD | FMB001 | 1.0 | FMB01A | Download | Download | DUMAX GPS | 5129240447 | info@dumaxst.com | http://dumaxst.com | 106 EAST SIXTH STREET, SUITEE 900, AUSTIN, TX., 78701 | In order for the application to transfer data through Email Services the mobile User must click the Option "Send by Email" identified as a green button in the Binnacle tab of the main screen. After doing so, the device will creaft an email with the data in the XML format containing all the driver's information as well as other required information, such as Unidentified Drivers' records, Positioning of the vehicle during the time of duty of the User during the last number of days (according to the organizational number of days which may very from 7 to 8 in total) and the vehicle's information. If the user would like to retrieve the information through Web Services, the User may click the same button, but instead, select the tab "Send Through Web Services", the user will be prompted with a text box in which he must type the official's routing code. If the user has Internet connection, the data transfer will be made through the mobile phone to the FMCSA portal. | Malfunctiosn are recorded according to the Standard Coding Required for Compliance. They include Power Compliance Malfunction, Engine Syncrhonization Compliance Malfunctions and Timing Compliance Malfunctions; as well as Positioning Compliance Malfunction, Data Recording Malfunctions and Data Transfer Malfunctions. All of these, according to the rules regarding the vehicles' drivers responding or not to the ELD, the ELD having detected movement without proper management of the application and depending on the rules the driver is allowed to keep doing his or her duty. Data Recording compliance is checked through continous revision of data checksum of values. The data transfer malfunctions is registered when there are problems syncrhonizing data with the application and the required transfering. In the same manner, diagnostic events are registered prior to a malfunction code and the ELD registers a malfunction when they trespass the limits according to the rule. Unidentified driving records are registered whenever the device detects vehicle's movements for more than the specified amount of miles or minutes. These are registered and, whenever a driver is logged in to the application, is requested to review them until a driver claims them. Missing data elements diagnostics are registered when the device could not retrieve, transfer or calculate all the information required for all it's required functions. | I certify and declare under penalty of perjury that the foregoing is true and correct. Subscribed at Austin, State of Texas on behalf of DUMAX GPS that the model and version has been sufficiently tested to meet the functional requirements included in the technical specifications in the Appendix to subpart B of part 395, title 49 of the Code of Federal Regulations. | |
| DY ELD | DRS | 2.0 or higher | DRS267 | Download | Download | YUSUF WORLD GLOBAL LLC | 2676252414 | dy.eld.department@gmail.com | www.dyeld.com | 5201 SWEET BAY ST APT 202, MASON, OH 45040 | DY ELD is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | DY ELD monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The DY ELD Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on DY ELD during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | DY ELD meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. DY ELD was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| DYNAMIC ELD | DYMIC | 2.25-6 or above | DRS242 | Download | Download | Midwestern Logistics LLC | 636-204-5424 | info@dynamiceld.us | www.dynamiceld.us | PO Box 901, Manchester, MO 63021 | Telematic (Web Service, Email) | Through the DYNAMIC ELD system, telematics data transfer is facilitated using either email or web services. The driver can perform the transfer by accessing the DOT Inspection Mode menu and clicking the "Send" button. Furthermore, a separate DOT Inspection Mode button is available for the driver to display the logs report to a DOT officer on their mobile device. | With the goal of maintaining compliance, detecting malfunctions and data inconsistencies, and documenting such occurrences, the DYNAMIC ELD system employs specific codes to classify compliance malfunctions and diagnostic events, such as: ■ P for "Power compliance" malfunction, ■ E "Engine synchronization compliance" malfunction, ■ T for "Timing compliance" malfunction, ■ L for "Positioning compliance" malfunction, ■ R for "Data recording compliance" malfunction, ■ S for "Data transfer compliance" malfunction, ■ O for "Other" ELD-detected malfunctions, ■ 1 for "Power data diagnostic" event, ■ 2 for "Engine synchronization data diagnostic" event, ■ 3 for "Missing required data elements data diagnostic" event, ■ 4 for "Data transfer data diagnostic" event, ■ 5 for "Unidentified driving records data diagnostic" event, ■ 6 for "Other" ELD-identified diagnostic events. The DYNAMIC ELD Malfunction and Diagnostic Event Records record all malfunctions that occurred during the relevant time period and relay active malfunctions to all ELD users. | The FMCSA´s testing procedures require thorough testing of DYNAMIC ELD to verify compliance as an electronic logging system, which has been completed. The system is able to confirm that it meets the requirements of 49 CFR Part 395 Subpart B, including the accurate logging and transmission of hours of service data. |
| E7 LOGS | E7LGV2 | 1.90 and higher | E7LG21 | Download | Download | E7 LOGS CORP | 5174994883 | info@e7logs.com | http://e7logs.com | 50593 SILVER TON DR, CANTON MI 48187 | ALL methods defined on the ELD Mandate specifications are supported: TELEMATICS: - Web services - Email LOCAL TRANSFER: - USB - Bluetooth To submit the Output File to an authorized safety official, the driver selects the “Export ELD Data File” from the Logbook screen. The driver, then, will select one of the following methods: - Agent External Storage: The ELD will first verify the external storage device is compatible with FMCSA specifications by validating the contents of file "ELDUSBTX.TXT". After positive validation the ELD will save the data file on the FMCSA-provided external storage device. - Bluetooth Transfer: After selecting this option, the authorized safety official will pair and verify PIN with the driver. Once the Bluetooth devices are paired, the safety official’s technology equipment will transfer the output file to the FMCSA website using Web services. - FMCSA web service: This option securely communicates to FMCSA's end-point ad obtains submission ID. | Low battery, network disconnection, low internal memory space, ECM data transfer failure, location sensor failure. In addition the following malfunctions are detected (and appropriate records created) by the StreetEagle ELD: - Power data diagnostic (diagnostic - 1) - Engine synchronization data diagnostic (diagnostic - 2) - Missing required data elements (diagnostic - 3) - Data transfer (diagnostic - 4) - Unidentified driving records data diagnostic (diagnostic - 5) - Other ELD diagnostics (diagnostic - 6 - Power compliance (malfunction - P) - Engine synchronization compliance (malfunction - E) - Timing compliance (malfunction - T) - Positioning compliance (malfunction - L) - Data recording compliance (malfunction - R) - Data transfer compliance (malfunction - S) - Other ELD malfunctions (malfunction - O) | The E7 LOGS ELD was tested on a diverse range of CMVs from different manufacturers and models as well drivers with different experience and backgrounds. Tests were also performed on different environments (indoor, outdoor, inside and outside CMVs). Procedures and areas of examinations were followed according to the “ELD Test Plan and Procedures” version 1.0 document released by FMCSA on April 25th 2016. The Requirement Traceability Matrix (RTM) was used and fully verified to ensure ELD compliance. Corrective actions and regression tests were made on all Failed test results. | |
| eBLUE SUN LOGS | EBLS | 2.17 or higher | ERS252 | Download | Download | Blue Sun Solutions LLC | 18885069811 | info@ebluesun.com | https://eld.ebluesun.com | 893 S Azusa Ave, City of Industry/CA/91748 | Telematic (Web Service, Email) | eBLUE SUN LOGS, or Electronic Logging Device, is a tool that offers a comprehensive overview of a driver's records during a roadside inspection. Not only does it provide this information within the app, but it also facilitates the transfer of telematics data through email or web services. The DOT Inspection mode allows the driver to choose the method that works best for them. To transfer ELD records through Web services, the driver needs to access the "DOT Inspection" menu and select the "Send Logs" option. Then, they should choose Web Service as the Data Transfer Type and click the "SEND" button. Similarly, to transfer ELD records via Email, the driver should follow the same steps but select Email as the Data Transfer Type before clicking the "SEND" button. | The eBLUE SUN LOGS system ensures compliance with technical requirements, identifies malfunctions and data inconsistencies, and maintains records of such occurrences. Compliance malfunctions and diagnostic events are classified with specific codes, including P for "Power compliance" malfunction, E for "Engine synchronization compliance" malfunction, T for "Timing compliance" malfunction, L for "Positioning compliance" malfunction, R for "Data recording compliance" malfunction, S for "Data transfer compliance" malfunction, O for "Other" ELD-detected malfunctions, 1 for "Power data diagnostic" event, 2 for "Engine synchronization data diagnostic" event, 3 for "Missing required data elements data diagnostic" event, 4 for "Data transfer data diagnostic" event, 5 for "Unidentified driving records data diagnostic" event, and 6 for "Other" ELD-identified diagnostic events. The eBLUE SUN LOGS Malfunction and Diagnostic Event Records document all malfunctions that occurred during the relevant time period. Active malfunctions are communicated to all drivers who may use the ELD. | eBLUE SUN LOGS has been thoroughly tested to ensure compliance with all the functional requirements outlined in Title 49, Part 395 of Section 4.9.1, Appendix A, Subpart B. eBLUE SUN LOGS can confidently certify that our ELD product adheres to all the necessary ELD regulations. |
| EDO ELD | ERS | 2.0 or higher | ERS109 | Download | Download | EDO ELD | 7077777770 | INFO@EDOELD.COM | http://WWW.EDOELD.COM | 7036 RANCHITO AVE, VAN NUYS/CA/91405 | EDO ELD is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | EDO ELD monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The EDO ELD Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on EDO ELD during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | EDO ELD meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. EDO ELD was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| EGREEN ELD | ERS | 2.24.01 or up | ERS170 | Download | Download | Egreen ELD | 8046251512 | egreeneldllc@gmail.com | www.egreeneld.com | 9500 Kimberly Lynn Cir, Glen Allen, VA, 23060 | Telematic (Web Service, Email) | EGREEN ELD system allows drivers to transfer log data through telematics methods in compliance with the regulations outlined in Title 49, Part 395, Section 4.9.1, Appendix A, Subpart B of the CFR. Drivers can also produce a report on their mobile display or transfer log data through web services or email if requested by an officer. | As per the regulations outlined in Appendix A, section 4.6, the EGREEN ELD system continuously monitors itself for malfunctions. If a malfunction or diagnostic event occurs, such as issues with data recording, data transfer, or power, EGREEN ELD system will display a visual alert to the driver. This includes alerts for any issues with engine synchronization, timing, positioning, or unidentified driving. | As per the FMCSA's testing procedures, EGREEN ELD has undergone thorough testing to ensure compliance as an electronic logging system. EGREEN ELD can confirm that the system meets the requirements of 49 CFR Part 395 Subpart B, including the correct logging and transmission of hours of service data. |
| ELD 2 GO | ERS | 2.15.0 and higher | ERS200 | Download | Download | ELD 2 GO | 1-8669401414 | info@eld2go.com | http://eld2go.com | 1390 Warrenton Road, Fredericksburg, Virginia 22406 | Telematic (Web Service, Email) | The data transfer system supported by ELD 2 GO is telematics: web services and email. The data is converted to the appropriate format, encrypted, and sent through the driver app. RODS can also be displayed on the screen for the officer | ELD 2 GO system monitors its functioning regularly to ensure compliance with the ELD Mandate. The malfunctions and diagnostic events the system detects are related to power, engine synchronization, timing, positioning, data recording, data transfer, required data elements, and unidentified driving, pursuant to section 4.6.1.2 of 49 CFR part 395, subpart B, Appendix A. | By means of this statement, ELD 2 GO certifies that the electronic logging device has been assessed according to FMCSA regulations and complies with all ELD requirements as per the ELD mandate. |
| ELD Chrome Cab-Mate Connect by Pedigree Technologies | Cab-Mate Connect | 4.55 | CMCN01 | Download | Download | Pedigree Technologies, LLC | 855-838-6941 | eld@pedigreetechnologies.com | http://www.eldcertified.com | 4776 28th Ave S, Fargo, ND 58104 | The CabMate ELD product will support the FMCSA Data Transfer via Wireless Web Services and Email once the FMCSA Web Services portal is operational. In the mean time, a driver is able to show the ELD screen to an authorized safety official by clicking on the 3 dot menu in the upper right corner of the ELD application and selecting Enforcement View. As an alternative, the logs can be emailed along with the ELD data file to any email address by clicking on the 3 dot menu in the upper right corner of the ELD application and selecting "Email Logs" and entering the email address for logs delivery. | ELD Malfunction lights Note: CabMate Open uses a circular malfunction light; CabMate One, Cab-Mate Connect, Cab-Mate Elite and Cab-Mate Flex use a light built into the cradle dock. Flashing Red: Tablet not in dock (CabMate One, Cab-Mate Connect, Cab-Mate Elite and Cab-Mate Flex Only) Flashing Green: Not connected or not logged into ELD Solid Red: ELD Malfunction Active Solid Green: ELD Data Diagnostic Active Malfunction and Data Diagnostic Events Definitions Power Data Diagnostic: The ELD was not able to power up within one minute of engine power up. Check the device connections are not loose. If this issue persists, contact your administrator. Power Compliance Malfunction: The ELD was not functional for more than 30 minutes over the last 24 hours. Check the device connections are not loose. If this issue persists, contact your administrator. Engine Synchronization Data Diagnostic: The ELD is not receiving data from the engine. Check that the Bluetooth is connected (or if using CabMate One, Cab-Mate Connect, Cab-Mate Elite or Cab-Mate Flex check that the tablet is in its cradle) and the diagnostic cable is connected to the vehicle. If this issue persists, contact your administrator. Engine Synchronization Compliance Malfunction: The ELD did not receive data from the engine for more than 30 minutes over the last 24 hours. Check that the Bluetooth is connected (or if using CabMate One, Cab-Mate Connect, Cab-Mate Elite and Cab-Mate Flex check that the tablet is in its cradle) and that the diagnostic cable is connected to the vehicle. If this issue persists, contact your administrator. Other Data Diagnostic (for Positioning Compliance): The ELD is not receiving GPS location. Check that the GPS is ON in this device, the vehicle antenna is not damaged and connections are tight. If this issue persists, contact your administrator. Positioning Compliance Malfunction: The ELD did not receive GPS location for more than 60 minutes over the last 24 hours. Check that the GPS is ON in this device, the vehicle antenna is not damaged and connections are tight. If this issue persists, contact your administrator. Timing Compliance Malfunction: The ELD time is off by more than 10 minutes. If this issue persists, contact your administrator. Missing Required Data Elements Data Diagnostic: The ELD is missing required data for creating ELD records. Check Engine Synchronization and Positioning Compliance. If this issue persists, contact your administrator. Data Recording Compliance Malfunction: The ELD has reached its storage capacity and can no longer record ELD records. Reduce the data stored on the ELD or replace the ELD. If this issue persists, contact your administrator. Unidentified Driving Records Data Diagnostic: The ELD has recorded more than 30 minutes worth of unidentified driving records in the last 24 hours. Ensure that drivers are logged into the ELD while the vehicle is in motion and accept any unidentified records that may belong to you. If this issue persists, contact your administrator. Data Transfer Compliance Malfunction: The ELD test of data transfer to the FMCSA via web services and email has failed for an extended period of time. Ensure that the ELD data connection is working. If this issue persists, contact your administrator. Will be enabled once the FMCSA Web Services portal is operational for Wireless Web Services and Email data transfer. Data Transfer Data Diagnostic: The ELD test of data transfer to the FMCSA via web services and email has failed. Ensure that the ELD data connection is working. If this issue persists, contact your administrator. Will be enabled once the FMCSA Web Services portal is operational for Wireless Web Services and Email data transfer. | The CabMate ELD product was tested, passed and certified in accordance with the FMCSA regulation 49 CFR 385, 390, and 395 regarding Electronic Logging Devices. | |
| ELD Chrome Cab-Mate Elite by Pedigree Technologies | Cab-Mate Elite | 5.1 | CMET01 | Download | Download | Pedigree Technologies, LLC | 855-838-6941 | eld@pedigreetechnologies.com | http://www.eldcertified.com | 4776 28th Ave S, Fargo, ND 58104 | The CabMate ELD product will support the FMCSA Data Transfer via Wireless Web Services and Email once the FMCSA Web Services portal is operational. In the mean time, a driver is able to show the ELD screen to an authorized safety official by clicking on the 3 dot menu in the upper right corner of the ELD application and selecting Enforcement View. As an alternative, the logs can be emailed along with the ELD data file to any email address by clicking on the 3 dot menu in the upper right corner of the ELD application and selecting "Email Logs" and entering the email address for logs delivery. | ELD Malfunction lights Note: CabMate Open uses a circular malfunction light; CabMate One, Cab-Mate Connect, Cab-Mate Elite and Cab-Mate Flex use a light built into the cradle dock. Flashing Red: Tablet not in dock (CabMate One, Cab-Mate Connect, Cab-Mate Elite and Cab-Mate Flex Only) Flashing Green: Not connected or not logged into ELD Solid Red: ELD Malfunction Active Solid Green: ELD Data Diagnostic Active Malfunction and Data Diagnostic Events Definitions Power Data Diagnostic: The ELD was not able to power up within one minute of engine power up. Check the device connections are not loose. If this issue persists, contact your administrator. Power Compliance Malfunction: The ELD was not functional for more than 30 minutes over the last 24 hours. Check the device connections are not loose. If this issue persists, contact your administrator. Engine Synchronization Data Diagnostic: The ELD is not receiving data from the engine. Check that the Bluetooth is connected (or if using CabMate One, Cab-Mate Connect, Cab-Mate Elite or Cab-Mate Flex check that the tablet is in its cradle) and the diagnostic cable is connected to the vehicle. If this issue persists, contact your administrator. Engine Synchronization Compliance Malfunction: The ELD did not receive data from the engine for more than 30 minutes over the last 24 hours. Check that the Bluetooth is connected (or if using CabMate One, Cab-Mate Connect, Cab-Mate Elite and Cab-Mate Flex check that the tablet is in its cradle) and that the diagnostic cable is connected to the vehicle. If this issue persists, contact your administrator. Other Data Diagnostic (for Positioning Compliance): The ELD is not receiving GPS location. Check that the GPS is ON in this device, the vehicle antenna is not damaged and connections are tight. If this issue persists, contact your administrator. Positioning Compliance Malfunction: The ELD did not receive GPS location for more than 60 minutes over the last 24 hours. Check that the GPS is ON in this device, the vehicle antenna is not damaged and connections are tight. If this issue persists, contact your administrator. Timing Compliance Malfunction: The ELD time is off by more than 10 minutes. If this issue persists, contact your administrator. Missing Required Data Elements Data Diagnostic: The ELD is missing required data for creating ELD records. Check Engine Synchronization and Positioning Compliance. If this issue persists, contact your administrator. Data Recording Compliance Malfunction: The ELD has reached its storage capacity and can no longer record ELD records. Reduce the data stored on the ELD or replace the ELD. If this issue persists, contact your administrator. Unidentified Driving Records Data Diagnostic: The ELD has recorded more than 30 minutes worth of unidentified driving records in the last 24 hours. Ensure that drivers are logged into the ELD while the vehicle is in motion and accept any unidentified records that may belong to you. If this issue persists, contact your administrator. Data Transfer Compliance Malfunction: The ELD test of data transfer to the FMCSA via web services and email has failed for an extended period of time. Ensure that the ELD data connection is working. If this issue persists, contact your administrator. Will be enabled once the FMCSA Web Services portal is operational for Wireless Web Services and Email data transfer. Data Transfer Data Diagnostic: The ELD test of data transfer to the FMCSA via web services and email has failed. Ensure that the ELD data connection is working. If this issue persists, contact your administrator. Will be enabled once the FMCSA Web Services portal is operational for Wireless Web Services and Email data transfer. | The CabMate ELD product was tested, passed and certified in accordance with the FMCSA regulation 49 CFR 385, 390, and 395 regarding Electronic Logging Devices. | |
| ELD Chrome Cab-Mate Flex by Pedigree Technologies | Cab-Mate Flex | 4.55 | CMFL01 | Download | Download | Pedigree Technologies, LLC | 855-838-6941 | eld@pedigreetechnologies.com | http://www.eldcertified.com | 4776 28th Ave S, Fargo, ND 58104 | The CabMate ELD product will support the FMCSA Data Transfer via Wireless Web Services and Email once the FMCSA Web Services portal is operational. In the mean time, a driver is able to show the ELD screen to an authorized safety official by clicking on the 3 dot menu in the upper right corner of the ELD application and selecting Enforcement View. As an alternative, the logs can be emailed along with the ELD data file to any email address by clicking on the 3 dot menu in the upper right corner of the ELD application and selecting "Email Logs" and entering the email address for logs delivery. | ELD Malfunction lights Note: CabMate Open uses a circular malfunction light; CabMate One, Cab-Mate Connect, Cab-Mate Elite and Cab-Mate Flex use a light built into the cradle dock. Flashing Red: Tablet not in dock (CabMate One, Cab-Mate Connect, Cab-Mate Elite and Cab-Mate Flex Only) Flashing Green: Not connected or not logged into ELD Solid Red: ELD Malfunction Active Solid Green: ELD Data Diagnostic Active Malfunction and Data Diagnostic Events Definitions Power Data Diagnostic: The ELD was not able to power up within one minute of engine power up. Check the device connections are not loose. If this issue persists, contact your administrator. Power Compliance Malfunction: The ELD was not functional for more than 30 minutes over the last 24 hours. Check the device connections are not loose. If this issue persists, contact your administrator. Engine Synchronization Data Diagnostic: The ELD is not receiving data from the engine. Check that the Bluetooth is connected (or if using CabMate One, Cab-Mate Connect, Cab-Mate Elite or Cab-Mate Flex check that the tablet is in its cradle) and the diagnostic cable is connected to the vehicle. If this issue persists, contact your administrator. Engine Synchronization Compliance Malfunction: The ELD did not receive data from the engine for more than 30 minutes over the last 24 hours. Check that the Bluetooth is connected (or if using CabMate One, Cab-Mate Connect, Cab-Mate Elite and Cab-Mate Flex check that the tablet is in its cradle) and that the diagnostic cable is connected to the vehicle. If this issue persists, contact your administrator. Other Data Diagnostic (for Positioning Compliance): The ELD is not receiving GPS location. Check that the GPS is ON in this device, the vehicle antenna is not damaged and connections are tight. If this issue persists, contact your administrator. Positioning Compliance Malfunction: The ELD did not receive GPS location for more than 60 minutes over the last 24 hours. Check that the GPS is ON in this device, the vehicle antenna is not damaged and connections are tight. If this issue persists, contact your administrator. Timing Compliance Malfunction: The ELD time is off by more than 10 minutes. If this issue persists, contact your administrator. Missing Required Data Elements Data Diagnostic: The ELD is missing required data for creating ELD records. Check Engine Synchronization and Positioning Compliance. If this issue persists, contact your administrator. Data Recording Compliance Malfunction: The ELD has reached its storage capacity and can no longer record ELD records. Reduce the data stored on the ELD or replace the ELD. If this issue persists, contact your administrator. Unidentified Driving Records Data Diagnostic: The ELD has recorded more than 30 minutes worth of unidentified driving records in the last 24 hours. Ensure that drivers are logged into the ELD while the vehicle is in motion and accept any unidentified records that may belong to you. If this issue persists, contact your administrator. Data Transfer Compliance Malfunction: The ELD test of data transfer to the FMCSA via web services and email has failed for an extended period of time. Ensure that the ELD data connection is working. If this issue persists, contact your administrator. Will be enabled once the FMCSA Web Services portal is operational for Wireless Web Services and Email data transfer. Data Transfer Data Diagnostic: The ELD test of data transfer to the FMCSA via web services and email has failed. Ensure that the ELD data connection is working. If this issue persists, contact your administrator. Will be enabled once the FMCSA Web Services portal is operational for Wireless Web Services and Email data transfer. | The CabMate ELD product was tested, passed and certified in accordance with the FMCSA regulation 49 CFR 385, 390, and 395 regarding Electronic Logging Devices. | |
| ELD Chrome Cab-Mate One by Pedigree Technologies | Cab-Mate One | 4.55 | CM0101 | Download | Download | Pedigree Technologies, LLC | 855-838-6941 | eld@pedigreetechnologies.com | http://www.eldcertified.com | 4776 28th Ave S, Fargo, ND 58104 | The CabMate ELD product will support the FMCSA Data Transfer via Wireless Web Services and Email once the FMCSA Web Services portal is operational. In the mean time, a driver is able to show the ELD screen to an authorized safety official by clicking on the 3 dot menu in the upper right corner of the ELD application and selecting Enforcement View. As an alternative, the logs can be emailed along with the ELD data file to any email address by clicking on the 3 dot menu in the upper right corner of the ELD application and selecting "Email Logs" and entering the email address for logs delivery. | ELD Malfunction lights Note: CabMate Open uses a circular malfunction light; CabMate One, Cab-Mate Connect, Cab-Mate Elite and Cab-Mate Flex use a light built into the cradle dock. Flashing Red: Tablet not in dock (CabMate One, Cab-Mate Connect, Cab-Mate Elite and Cab-Mate Flex Only) Flashing Green: Not connected or not logged into ELD Solid Red: ELD Malfunction Active Solid Green: ELD Data Diagnostic Active Malfunction and Data Diagnostic Events Definitions Power Data Diagnostic: The ELD was not able to power up within one minute of engine power up. Check the device connections are not loose. If this issue persists, contact your administrator. Power Compliance Malfunction: The ELD was not functional for more than 30 minutes over the last 24 hours. Check the device connections are not loose. If this issue persists, contact your administrator. Engine Synchronization Data Diagnostic: The ELD is not receiving data from the engine. Check that the Bluetooth is connected (or if using CabMate One, Cab-Mate Connect, Cab-Mate Elite or Cab-Mate Flex check that the tablet is in its cradle) and the diagnostic cable is connected to the vehicle. If this issue persists, contact your administrator. Engine Synchronization Compliance Malfunction: The ELD did not receive data from the engine for more than 30 minutes over the last 24 hours. Check that the Bluetooth is connected (or if using CabMate One, Cab-Mate Connect, Cab-Mate Elite and Cab-Mate Flex check that the tablet is in its cradle) and that the diagnostic cable is connected to the vehicle. If this issue persists, contact your administrator. Other Data Diagnostic (for Positioning Compliance): The ELD is not receiving GPS location. Check that the GPS is ON in this device, the vehicle antenna is not damaged and connections are tight. If this issue persists, contact your administrator. Positioning Compliance Malfunction: The ELD did not receive GPS location for more than 60 minutes over the last 24 hours. Check that the GPS is ON in this device, the vehicle antenna is not damaged and connections are tight. If this issue persists, contact your administrator. Timing Compliance Malfunction: The ELD time is off by more than 10 minutes. If this issue persists, contact your administrator. Missing Required Data Elements Data Diagnostic: The ELD is missing required data for creating ELD records. Check Engine Synchronization and Positioning Compliance. If this issue persists, contact your administrator. Data Recording Compliance Malfunction: The ELD has reached its storage capacity and can no longer record ELD records. Reduce the data stored on the ELD or replace the ELD. If this issue persists, contact your administrator. Unidentified Driving Records Data Diagnostic: The ELD has recorded more than 30 minutes worth of unidentified driving records in the last 24 hours. Ensure that drivers are logged into the ELD while the vehicle is in motion and accept any unidentified records that may belong to you. If this issue persists, contact your administrator. Data Transfer Compliance Malfunction: The ELD test of data transfer to the FMCSA via web services and email has failed for an extended period of time. Ensure that the ELD data connection is working. If this issue persists, contact your administrator. Will be enabled once the FMCSA Web Services portal is operational for Wireless Web Services and Email data transfer. Data Transfer Data Diagnostic: The ELD test of data transfer to the FMCSA via web services and email has failed. Ensure that the ELD data connection is working. If this issue persists, contact your administrator. Will be enabled once the FMCSA Web Services portal is operational for Wireless Web Services and Email data transfer. | The CabMate ELD product was tested, passed and certified in accordance with the FMCSA regulation 49 CFR 385, 390, and 395 regarding Electronic Logging Devices. | |
| ELD Chrome Cab-Mate Open by Pedigree Technologies | Cab-Mate Open | 4.55 | CMOP01 | Download | Download | Pedigree Technologies, LLC | 855-838-6941 | eld@pedigreetechnologies.com | http://www.eldcertified.com | 4776 28th Ave S, Fargo, ND 58104 | The CabMate ELD product will support the FMCSA Data Transfer via Wireless Web Services and Email once the FMCSA Web Services portal is operational. In the mean time, a driver is able to show the ELD screen to an authorized safety official by clicking on the 3 dot menu in the upper right corner of the ELD application and selecting Enforcement View. As an alternative, the logs can be emailed along with the ELD data file to any email address by clicking on the 3 dot menu in the upper right corner of the ELD application and selecting "Email Logs" and entering the email address for logs delivery. | ELD Malfunction lights Note: CabMate Open uses a circular malfunction light; CabMate One, Cab-Mate Connect, Cab-Mate Elite and Cab-Mate Flex use a light built into the cradle dock. Flashing Red: Tablet not in dock (CabMate One, Cab-Mate Connect, Cab-Mate Elite and Cab-Mate Flex Only) Flashing Green: Not connected or not logged into ELD Solid Red: ELD Malfunction Active Solid Green: ELD Data Diagnostic Active Malfunction and Data Diagnostic Events Definitions Power Data Diagnostic: The ELD was not able to power up within one minute of engine power up. Check the device connections are not loose. If this issue persists, contact your administrator. Power Compliance Malfunction: The ELD was not functional for more than 30 minutes over the last 24 hours. Check the device connections are not loose. If this issue persists, contact your administrator. Engine Synchronization Data Diagnostic: The ELD is not receiving data from the engine. Check that the Bluetooth is connected (or if using CabMate One, Cab-Mate Connect, Cab-Mate Elite or Cab-Mate Flex check that the tablet is in its cradle) and the diagnostic cable is connected to the vehicle. If this issue persists, contact your administrator. Engine Synchronization Compliance Malfunction: The ELD did not receive data from the engine for more than 30 minutes over the last 24 hours. Check that the Bluetooth is connected (or if using CabMate One, Cab-Mate Connect, Cab-Mate Elite and Cab-Mate Flex check that the tablet is in its cradle) and that the diagnostic cable is connected to the vehicle. If this issue persists, contact your administrator. Other Data Diagnostic (for Positioning Compliance): The ELD is not receiving GPS location. Check that the GPS is ON in this device, the vehicle antenna is not damaged and connections are tight. If this issue persists, contact your administrator. Positioning Compliance Malfunction: The ELD did not receive GPS location for more than 60 minutes over the last 24 hours. Check that the GPS is ON in this device, the vehicle antenna is not damaged and connections are tight. If this issue persists, contact your administrator. Timing Compliance Malfunction: The ELD time is off by more than 10 minutes. If this issue persists, contact your administrator. Missing Required Data Elements Data Diagnostic: The ELD is missing required data for creating ELD records. Check Engine Synchronization and Positioning Compliance. If this issue persists, contact your administrator. Data Recording Compliance Malfunction: The ELD has reached its storage capacity and can no longer record ELD records. Reduce the data stored on the ELD or replace the ELD. If this issue persists, contact your administrator. Unidentified Driving Records Data Diagnostic: The ELD has recorded more than 30 minutes worth of unidentified driving records in the last 24 hours. Ensure that drivers are logged into the ELD while the vehicle is in motion and accept any unidentified records that may belong to you. If this issue persists, contact your administrator. Data Transfer Compliance Malfunction: The ELD test of data transfer to the FMCSA via web services and email has failed for an extended period of time. Ensure that the ELD data connection is working. If this issue persists, contact your administrator. Will be enabled once the FMCSA Web Services portal is operational for Wireless Web Services and Email data transfer. Data Transfer Data Diagnostic: The ELD test of data transfer to the FMCSA via web services and email has failed. Ensure that the ELD data connection is working. If this issue persists, contact your administrator. Will be enabled once the FMCSA Web Services portal is operational for Wireless Web Services and Email data transfer. | The CabMate ELD product was tested, passed and certified in accordance with the FMCSA regulation 49 CFR 385, 390, and 395 regarding Electronic Logging Devices. | |
| ELD Complete (Android & IOS) | ELD-2000 | 207 or higher | GPSI03 | Download | Download | GPS Insight | 480-240-4414 | HOS@gpsinsight.com | http://gpsinsight.com | 7201 E. Henkel Way, Suite 400, Scottsdale, AZ 85255 | Telematic (Web Service, Email) | To submit the Output File to an authorized safety official, the driver selects the “Export ELD Data File” from the Logbook screen. The driver, then, will select one of the following methods: - FMCSA web service: This option securely communicates to FMCSA's end-point ad obtains submission ID. - ELD Email Interface: This option transfer an encrypted email to FMCSA email address | Low battery, network disconnection, low internal memory space, ECM data transfer failure, location sensor failure. In addition, the following malfunctions are detected (and appropriate records created) by the P3TS ELD: - Power data diagnostic (diagnostic - 1) - Engine synchronization data diagnostic (diagnostic - 2) - Missing required data elements (diagnostic - 3) - Data transfer (diagnostic - 4) - Unidentified driving records data diagnostic (diagnostic - 5) - Other ELD diagnostics (diagnostic - 6 - Power compliance (malfunction - P) - Engine synchronization compliance (malfunction - E) - Timing compliance (malfunction - T) - Positioning compliance (malfunction - L) - Data recording compliance (malfunction - R) - Data transfer compliance (malfunction - S) - Other ELD malfunctions (malfunction - O) | The GPS Insight ELD Complete (GPSI-2000) was tested on a diverse range of CMVs from different manufacturers and models as well drivers with different experience and backgrounds. Tests were also performed on different environments (indoor, outdoor, inside and outside CMVs). Procedures and areas of examinations were followed according to the “ELD Test Plan and Procedures” version 1.0 document released by FMCSA on April 25th 2016. The Requirement Traceability Matrix (RTM) was used and fully verified to ensure ELD compliance. Corrective actions and regression tests were made on all Failed test results. |
| ELD CONNECT | ERS | 2.0 or higher | ERS124 | Download | Download | ELDCONNECT LLC | 8885890682 | info@eldconnect.com | http://eldconnect.com | 3708 Park Ridge Drive, Evansville, IN 47715 | ELD CONNECT is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | ELD CONNECT monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The ELD CONNECT Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on ELD CONNECT during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | ELD CONNECT meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. ELD CONNECT was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| ELD Fleet | R3002 | 1.0.2011.200727 | RAV002 | Download | Download | Raven | +1 (716) 636-1092 | eld@buffautomation.com | https://www.trucks.buffautomation.com/ | 10236 Transit Rd, East Amherst, NY 14051, Amherst, NY - 14228 | Data Transfer Description – Android Registrations The Raven provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. This can be done by selecting the Roadside Inspection button from the main HOS dashboard and selecting the option for Data Transfer. A list of supported data transfer options is then displayed which include Bluetooth, Email, USB, and web service. A Select Vehicle option is also available for selecting a vehicle upon performing the data transfer, this option enables the Raven to produce a data file or a series of data files of ELD records for a subset of its vehicles used by the driver. • Transfer via Bluetooth - this option enables the user to transfer files through Bluetooth. The ELD prompts for an output file comment which the driver may enter (optional). After the input, if Bluetooth is not yet turned on, a prompt will appear asking you to turn it on. You will then be asked to select the device name to which the data will be transmitted via Bluetooth. • Transfer via Email - this option enables the user to transfer files through email. The ELD output file is encrypted using AES-256 in FIPS Publication 197. Before sending, the ELD prompts for an output file comment which the driver may enter (optional). The email is then automatically sent to the FMCSA email address specified in the ELD Provider Registration website: fmcsaeldsub@dot.gov • Transfer via USB - this option enables the user to transfer files through USB (external devices). However, prior to saving the driver’s ELD file to an external storage/device, the ELD re-authenticates the driver account by asking for its password. • Transfer via Web Service - this option enables the user to transfer files to FMCSA via Web Services. The Web Service data transfer follows the following standards: WSDL, SOAP, XML. Data Transfer Description – iOS Registrations The Raven provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. This can be done by selecting the Roadside Inspection button from the main HOS dashboard and selecting the option for Data Transfer. A list of supported data transfer options is then displayed which include Bluetooth, Email, and web service. A Select Vehicle option is also available for selecting a vehicle upon performing the data transfer, this option enables the Raven to produce a data file or a series of data files of ELD records for a subset of its vehicles used by the driver. • Transfer via Bluetooth - this option enables the user to transfer files through Bluetooth. The ELD prompts for an output file comment which the driver may enter (optional). After the input, if Bluetooth is not yet turned on, a prompt will appear asking you to turn it on. You will then be asked to select the device name to which the data will be transmitted via Bluetooth. • Transfer via Email - this option enables the user to transfer files through email. The ELD output file is encrypted using AES-256 in FIPS Publication 197. Before sending, the ELD prompts for an output file comment which the driver may enter (optional). The email is then automatically sent to the FMCSA email address specified in the ELD Provider Registration website: fmcsaeldsub@dot.gov • Transfer via Web Service - this option enables the user to transfer files to FMCSA via Web Services. The Web Service data transfer follows the following standards: WSDL, SOAP, XML. | Malfunctions The Raven ELD is capable of monitoring its compliance for various detectable malfunctions. At each instance when an ELD malfunction event is detected or cleared by the Raven ELD, the ELD records the event. The recorded malfunction events are inconsistencies found while monitoring the ELD against FMCSA compliance requirements. Malfunction occurrences are indicated in the application header and in the Android & iOS notification toolbar with the letter ‘M’, respectively. The following shows the list of detectable malfunctions: • Power Malfunction • Engine Synchronization Malfunction • Timing Malfunction • Position Malfunction • Data Recording Malfunction • Data Transfer Malfunction Once the Malfunctions indicator ‘M’ is tapped, a dialog will be displayed with a list of the detected malfunction events alongside a ‘Clear’ button for each event. Tapping the Clear button will clear out the detected malfunction event. | Certifying Statement of FMCSA Regulation Testing The Raven ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The Raven ELD was installed on various types and sizes of Android & iOS phones and tablets. Testing was performed through the use of a J1939 simulator and actual vehicles while having been connected to the Geometris engine connected device. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the Hours of Service web application (portal) that can be accessed through a web browser. | |
| ELD Fleet | R3001 | 1.0.2011.200727 | RAV001 | Download | Download | Raven | +1 (716) 636-1092 | eld@buffautomation.com | https://www.trucks.buffautomation.com/ | 10236 Transit Rd, East Amherst, NY 14051, Amherst, NY - 14228 | Data Transfer Description – Android Registrations The Raven provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. This can be done by selecting the Roadside Inspection button from the main HOS dashboard and selecting the option for Data Transfer. A list of supported data transfer options is then displayed which include Bluetooth, Email, USB, and web service. A Select Vehicle option is also available for selecting a vehicle upon performing the data transfer, this option enables the Raven to produce a data file or a series of data files of ELD records for a subset of its vehicles used by the driver. • Transfer via Bluetooth - this option enables the user to transfer files through Bluetooth. The ELD prompts for an output file comment which the driver may enter (optional). After the input, if Bluetooth is not yet turned on, a prompt will appear asking you to turn it on. You will then be asked to select the device name to which the data will be transmitted via Bluetooth. • Transfer via Email - this option enables the user to transfer files through email. The ELD output file is encrypted using AES-256 in FIPS Publication 197. Before sending, the ELD prompts for an output file comment which the driver may enter (optional). The email is then automatically sent to the FMCSA email address specified in the ELD Provider Registration website: fmcsaeldsub@dot.gov • Transfer via USB - this option enables the user to transfer files through USB (external devices). However, prior to saving the driver’s ELD file to an external storage/device, the ELD re-authenticates the driver account by asking for its password. • Transfer via Web Service - this option enables the user to transfer files to FMCSA via Web Services. The Web Service data transfer follows the following standards: WSDL, SOAP, XML. Data Transfer Description – iOS Registrations The Raven provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. This can be done by selecting the Roadside Inspection button from the main HOS dashboard and selecting the option for Data Transfer. A list of supported data transfer options is then displayed which include Bluetooth, Email, and web service. A Select Vehicle option is also available for selecting a vehicle upon performing the data transfer, this option enables the Raven to produce a data file or a series of data files of ELD records for a subset of its vehicles used by the driver. • Transfer via Bluetooth - this option enables the user to transfer files through Bluetooth. The ELD prompts for an output file comment which the driver may enter (optional). After the input, if Bluetooth is not yet turned on, a prompt will appear asking you to turn it on. You will then be asked to select the device name to which the data will be transmitted via Bluetooth. • Transfer via Email - this option enables the user to transfer files through email. The ELD output file is encrypted using AES-256 in FIPS Publication 197. Before sending, the ELD prompts for an output file comment which the driver may enter (optional). The email is then automatically sent to the FMCSA email address specified in the ELD Provider Registration website: fmcsaeldsub@dot.gov • Transfer via Web Service - this option enables the user to transfer files to FMCSA via Web Services. The Web Service data transfer follows the following standards: WSDL, SOAP, XML. | Malfunctions The Raven ELD is capable of monitoring its compliance for various detectable malfunctions. At each instance when an ELD malfunction event is detected or cleared by the Raven ELD, the ELD records the event. The recorded malfunction events are inconsistencies found while monitoring the ELD against FMCSA compliance requirements. Malfunction occurrences are indicated in the application header and in the Android & iOS notification toolbar with the letter ‘M’, respectively. The following shows the list of detectable malfunctions: • Power Malfunction • Engine Synchronization Malfunction • Timing Malfunction • Position Malfunction • Data Recording Malfunction • Data Transfer Malfunction Once the Malfunctions indicator ‘M’ is tapped, a dialog will be displayed with a list of the detected malfunction events alongside a ‘Clear’ button for each event. Tapping the Clear button will clear out the detected malfunction event. | Certifying Statement of FMCSA Regulation Testing The Raven ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The Raven ELD was installed on various types and sizes of Android & iOS phones and tablets. Testing was performed through the use of a J1939 simulator and actual vehicles while having been connected to the Pacific Track engine connected device. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the Hours of Service web application (portal) that can be accessed through a web browser. | |
| ELD FOR YOU | ERS | 2.0 or higher | ERS146 | Download | Download | ELD FOR YOU LLC | 8152978084 | eldforyou76@gmail.com | http://ELDFORYOULLC.COM | 346 HOMWOOD DR BOLINGBROOK,IL, BOLINGBROOK IL 40440 | ELD FOR YOU is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | ELD FOR YOU monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The ELD FOR YOU Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on ELD FOR YOU during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | ELD FOR YOU meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. ELD FOR YOU was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| ELD GO | IOGO | Android 1.0.3 | ELDGO1 | Download | Download | ELD GO | 772-577-7770 | sales@eldgo.com | http://www.eldgo.com | 2121 Biscayne Blvd, unit #1777, Miami, FL 33137 | Telematic (Web Service, Email) | ELD GO Supports Telematic Data transfer method including Webservice and email. ELD GO Makes it easy to transfer ELD data to authorized safety officials. To transfer the ELD Data from mobile device including phones, tablets etc. driver or authorized safety official have to follow these steps: 1. On main application screen navigate to Inspection section On the following screen choose a desired transfer method either Webservice or Email After choosing webservice option following screen will appear where driver or safety official will be able to input transfer code After choosing Email option following screen will appear where driver or safety official will be able to input desired email address After information is filled click “Submit” and ELD file will be transferred Depending on location and mobile data coverage at the area it may take up to 60 seconds for file to be transferred. | LD GO Have full capability to monitor and record malfunctions as described in ELD rule. Malfunctions including Power compliance, engine synchronization, timing, positioning, data recording, data transfer, unidentified hours and other will be recorded and displayed in ELD files with matching malfunction/Diagnostics code. ELD Hardware malfunctions – ELD Hardware have visual and colored indicators which indicate power, connectivity with vehicles computer and Bluetooth connectivity, in case of hardware malfunctions drivers have to follow steps described in ELD GO manual or contact ELD GO customer support for assistance. | This is a certifying statement that upon completing extensive testing ELD GO meets all of the ELD software requirements as described in ELD technical specifications. |
| ELD LINK | ERS | 2.0 or higher | ERS173 | Download | Download | ELD LINK | (312) 500-0350 | admin@eldlink.us | www.eldlink.us | 2618 N 75th Ct, 2, Elmwood Park, IL 60707 | ELD LINK is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | ELD LINK monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The ELD LINK Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on ELD LINK during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | ELD LINK meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. ELD LINK was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| ELD LOG ROD's App | ELDLOG | 2.5 or above | ERS145 | Download | Download | ELD LOD ROGS INC | 7735739725 | eldlogrods@gmail.com | http://www.eldlog.org | 1627 MCCORMACK DR, HOFFMAN ESTATES | Telematic (Web Service, Email) | Through the ELD LOG RODs App system, telematics data transfer is facilitated using either email or web services. The driver can perform the transfer by accessing the DOT Inspection Mode menu and clicking the "Send" button. Furthermore, a separate DOT Inspection Mode button is available for the driver to display the logs report to a DOT officer on their mobile device. | With the goal of maintaining compliance, detecting malfunctions and data inconsistencies, and documenting such occurrences, the ELD LOG RODs App system employs specific codes to classify compliance malfunctions and diagnostic events, such as: ■ P for "Power compliance" malfunction, ■ E "Engine synchronization compliance" malfunction, ■ T for "Timing compliance" malfunction, ■ L for "Positioning compliance" malfunction, ■ R for "Data recording compliance" malfunction, ■ S for "Data transfer compliance" malfunction, ■ O for "Other" ELD-detected malfunctions, ■ 1 for "Power data diagnostic" event, ■ 2 for "Engine synchronization data diagnostic" event, ■ 3 for "Missing required data elements data diagnostic" event, ■ 4 for "Data transfer data diagnostic" event, ■ 5 for "Unidentified driving records data diagnostic" event, ■ 6 for "Other" ELD-identified diagnostic events. The ELD LOG RODs App Malfunction and Diagnostic Event Records record all malfunctions that occurred during the relevant time period and relay active malfunctions to all ELD users. | The FMCSA´s testing procedures require thorough testing of ELD LOG RODs App to verify compliance as an electronic logging system, which has been completed. The system is able to confirm that it meets the requirements of 49 CFR Part 395 Subpart B, including the accurate logging and transmission of hours of service data. |
| ELD logbook ISPP | CTELD2 | 3.0.2116.210920 | CTELD2 | Download | Download | I.S.P.P. 9675868 Canada Inc. | 1-888 256-2464 | info@ispp.ca | www.ispp.ca | 2249 rue Saint-Jacques Suite 500, Montreal, Quebec, Canada H3J1H6 | The ELD Logbook ISPP provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. This can be done by selecting the Roadside Inspection button from the main HOS dashboard and selecting the option for Data Transfer. A list of supported data transfer options is then displayed which include Bluetooth, Email and USB. A Select Vehicle option is also available for selecting a vehicle upon performing the data transfer, this option enables the ELD Logbook ISPP to produce a data file or a series of data files of ELD records for a subset of its vehicles used by the driver. •Transfer via Bluetooth - this option enables the user to transfer files through Bluetooth. The ELD prompts for an output file comment which the driver may enter (optional). After the input, if Bluetooth is not yet turned on, a prompt will appear asking you to turn it on. You will then be asked to select the device name to which the data will be transmitted via Bluetooth. •Transfer via Email - this option enables the user to transfer files through email. The ELD output file transferred is encrypted using AES-256 in FIPS Publication 197. Before sending, the ELD prompts for an output file comment which the driver may enter (optional). The device's default email application will then be opened before sending the email to which the data will be transferred. Transfer via USB - this option enables the user to transfer files through USB (external devices). However, prior to saving the driver’s ELD file to an external storage/device, the ELD re-authenticates the driver account by asking for its password. | The ELD Logbook ISPP, ELD is capable of monitoring its compliance for various detectable malfunctions. At each instance when an ELD malfunction event is detected or cleared by the ELD Logbook ISPP, ELD, the ELD records the event. The recorded malfunction events are inconsistencies found while monitoring the ELD against FMCSA compliance requirements. Malfunction occurrences are indicated in the application header and in the Android notification toolbar with the letter ‘M’, respectively. The following shows the list of detectable malfunctions: •Power Malfunction •Engine Synchronization Malfunction •Timing Malfunction •Position Malfunction •Data Recording Malfunction •Data Transfer Malfunction Once the Malfunctions indicator ‘M’ is tapped, a dialog will be displayed with a list of the detected malfunction events alongside a ‘Clear’ button for each event. Tapping the Clear button will clear out the detected malfunction event. | Certifying Statement of FMCSA Regulation Testing The ELD Logbook ISPP, ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The ELD Logbook ISPP, ELD was installed on various types and sizes of Android phones and tablets. Testing was performed through the use of a J1939 simulator and actual vehicles while having been connected to the VBUS Geometris, engine connected devices. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the Hours of Service web application (portal) that can be accessed through a web browser. | |
| ELD logbook ISPP | CTELD2 | 3.0.2116.210920 | CTELD2 | Download | Download | I.S.P.P. 9675868 Canada Inc. | 1-888 256-2464 | info@ispp.ca | www.ispp.ca | 2249 rue Saint-Jacques Suite 500, Montreal, Quebec, Canada H3J1H6 | The ELD Logbook ISPP provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. This can be done by selecting the Roadside Inspection button from the main HOS dashboard and selecting the option for Data Transfer. A list of supported data transfer options is then displayed which include Bluetooth, Email and USB. A Select Vehicle option is also available for selecting a vehicle upon performing the data transfer, this option enables the ELD Logbook ISPP to produce a data file or a series of data files of ELD records for a subset of its vehicles used by the driver. •Transfer via Bluetooth - this option enables the user to transfer files through Bluetooth. The ELD prompts for an output file comment which the driver may enter (optional). After the input, if Bluetooth is not yet turned on, a prompt will appear asking you to turn it on. You will then be asked to select the device name to which the data will be transmitted via Bluetooth. •Transfer via Email - this option enables the user to transfer files through email. The ELD output file transferred is encrypted using AES-256 in FIPS Publication 197. Before sending, the ELD prompts for an output file comment which the driver may enter (optional). The device's default email application will then be opened before sending the email to which the data will be transferred. Transfer via USB - this option enables the user to transfer files through USB (external devices). However, prior to saving the driver’s ELD file to an external storage/device, the ELD re-authenticates the driver account by asking for its password. | The ELD Logbook ISPP, ELD is capable of monitoring its compliance for various detectable malfunctions. At each instance when an ELD malfunction event is detected or cleared by the ELD Logbook ISPP, ELD, the ELD records the event. The recorded malfunction events are inconsistencies found while monitoring the ELD against FMCSA compliance requirements. Malfunction occurrences are indicated in the application header and in the Android notification toolbar with the letter ‘M’, respectively. The following shows the list of detectable malfunctions: •Power Malfunction •Engine Synchronization Malfunction •Timing Malfunction •Position Malfunction •Data Recording Malfunction •Data Transfer Malfunction Once the Malfunctions indicator ‘M’ is tapped, a dialog will be displayed with a list of the detected malfunction events alongside a ‘Clear’ button for each event. Tapping the Clear button will clear out the detected malfunction event. | Certifying Statement of FMCSA Regulation Testing The ELD Logbook ISPP, ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The ELD Logbook ISPP, ELD was installed on various types and sizes of Android phones and tablets. Testing was performed through the use of a J1939 simulator and actual vehicles while having been connected to the VBUS Geometris, engine connected devices. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the Hours of Service web application (portal) that can be accessed through a web browser. | |
| ELD MANDATE PLUS | EMPPT30 | Android-1.12 iOS-2.3 | ELDP30 | Download | Download | ELD Mandate | 800-968-1869 | ratan@eldmandate.biz | http://eldmandate.biz | 3158 Redhill Ave, Suite 100, Costa Mesa, CA 92626 | Telematic (Web Service, Email) | We at ELD Mandate Plus Support two type of data transfer mechanism. 1. Wireless Web services 2. Email Wireless Web services : 1. ELD Mandate Plus convert ELD files into an XML using FMCSA provided files. 2. ELD Mandate Plus Generate XML files to the driver for Last 7 days+ current day. 3. ELD Mandate Plus supports upload the data(XML file) into the FMCSA. Wireless data transfer through EMail : We ELD Mandate Plus give an Instruction for a driver to produce and transfer the ELD records: ELD Mandate provides to create CSV File FMCSA: 1. ELD Mandate Plus create CSV file along with following information (under the FMCSA rule): company, driver details, trip details, co-driver details, shipping details, hours of service records, event log details, unidentified records for Vehicle (including comments for the inspection officer at the time of inspection). 2. ELD Mandate Plus encrypts the content of the CSV file using AES encryption standards with authentication value. 3. Create file name, subject of the email all are under the FMCSA rule. 4. Attach CSV file and send email to FMCSA provided email id. | ELD Mandate Plus support following malfunctions: Power compliance malfunction - If there is any issues while streaming vehicle data, we have recorded event log with power compliance. Engine synchronization compliance malfunction - If there are any issues while connecting to the vehicle, we have recorded event log with Engine synchronization. Timing compliance malfunction - When ELD no longer meet the underlying compliance requirement, we have recorded event log with timing compliance malfunction. Positioning compliance malfunction - If there are any issues from latitude and longitude coordinates, we have recorded event log with positioning compliance malfunction. Data recording compliance malfunction - If there is any issues while getting vehicle data like(VIN, Engine time, Odometer readings), we have recorded log for that incorrect data. Data transfer compliance malfunction event - While transfer to FMCSA if there is any issue, we have captured as a data transfer malfunction. Missing required data elements data diagnostic event - While recording the event if there is any required field missing, we have recorded log under missing required data elements data diagnostics (under FMCSA mandatory fields for the event). Unidentified driving records data diagnostic event - If any unidentified event is detected (without user login), we have recorded log under unidentified driving records data diagnostic event. | We hereby certify that we have executed FMCSA test plans and procedures and test procedure complies with the FMCSA regulations. |
| ELD Mandate Prime | EMPRM1 | Version 7 | EMPR63 | Download | Download | ELD Mandate | 800-968-1869 | ratan@eldmandate.biz | http://eldmandate.biz | 3158 Redhill Ave, Suite 100, Costa Mesa, CA 92626 | Local (USB, Bluetooth) , Telematic (Web Service, Email) | To submit the Output File to an authorized safety official, the driver selects the “Export ELD Data File” from the Logbook screen. The driver, then, will select one of the following methods: - FMCSA web service: This option securely communicates to FMCSA's end-point ad obtains submission ID. - ELD Email Interface: This option transfer an encrypted email to FMCSA email address | Low battery, network disconnection, low internal memory space, ECM data transfer failure, location sensor failure. In addition, the following malfunctions are detected (and appropriate records created) by the ELD Identifier: - Power data diagnostic (diagnostic - 1) - Engine synchronization data diagnostic (diagnostic - 2) - Missing required data elements (diagnostic - 3) - Data transfer (diagnostic - 4) - Unidentified driving records data diagnostic (diagnostic - 5) - Other ELD diagnostics (diagnostic - 6 - Power compliance (malfunction - P) - Engine synchronization compliance (malfunction - E) - Timing compliance (malfunction - T) - Positioning compliance (malfunction - L) - Data recording compliance (malfunction - R) - Data transfer compliance (malfunction - S) - Other ELD malfunctions (malfunction - O) | The Product Name (ELD Identifier) was tested on a diverse range of CMVs from different manufacturers and models as well drivers with different experience and backgrounds. Tests were also performed on different environments (indoor, outdoor, inside and outside CMVs). Procedures and areas of examinations were followed according to the “ELD Test Plan and Procedures” version 1.0 document released by FMCSA on April 25th 2016. The Requirement Traceability Matrix (RTM) was used and fully verified to ensure ELD compliance. Corrective actions and regression tests were made on all Failed test results. |
| ELD Mandate Pro | ELDPRO1 | 1.0 and above | ELDPR1 | Download | Download | ELD Mandate | 800-968-1869 | ratan@eldmandate.biz | http://eldmandate.biz | 3158 Redhill Ave, Suite 100, Costa Mesa, CA 92626 | Telematic (Web Service, Email) | This ELD uses the web services and email transmission method. | The malfunctions supported are: Power Compliance Malfunction Engine Synchronization Malfunction Timing Compliance Malfunction Positioning Compliance Malfunction Data Recording Malfunction Data Transfer Malfunction Each of these malfunctions appears prominently for the user to understand the issue. When the user is presented with this, he is able to rectify the situation, contact the manufacturer or use paper logs, as provided as part of the instruction guide, to remain compliant. The malfunctions and malfunction codes can be found in the instruction guide with the required details in order for the driver to understand what he needs to do next. | The product has been thoroughly tested by both internal and external, third party, testers. Each requirement of the ELD has been either met or exceeded. The process of review and testing included the full review of the ruling, testing procedures and debugging of any blocker found in the software package. It further included the retesting by additional quality assurance professionals. Ultimately, the programing and hardware operate as intended and are in compliance. Bizringer certifies that ELD Mandate Pro complies with FMCSA regulations. |
| ELD Plug-In | MW-ELD-J9C | 3.15 and higher | MW3764 | Download | Download | Mobile Warrior LLC | 888-474-9284 | customercare@mobilewarrior.com | http://www.mobilewarrior.com/corporate/ | 226 Marmalade Trail, Dawsonville, GA 30534 | From the Report Tab choose the ELD DOT Telemetry Report option and then choose to either send the Data Transfer File via the Wireless Web directly to the FMCSA Web Service account or to transfer the the file into an Email. Once the Email is displayed with the attached file, input the send to email required by the DOT and send it. | Power compliance P : If recorded event sequence find a possibility of in motion time then this ELD record will have a P set. A period of time of more then 30 minutes in the last 24 hours when a power on might have occurred. Field is set true. Time compliance T : If the data incoming from box indicates that the time is not consistent with the mobile device adjusted to the time zone of the driver. This field is set true if these are out of sync by 10 minutes. Engine sync compliance E : monitoring the data set of the last 24 hour of a period of time of more then 30 when the ELD was active and no j bus data is provided. This field is set true Position Location compliance L : must record a failure to track the current location for 60 minutes within 5 miles of the last known location. This will show last know location and time of recording it. Data Recording compliance R :This field is set true if the application is currently unable to create records or sync those records to the server. Monitoring record of unidentified drivers: If the vehicle has a 30 minute period in the last 7 days with unidentified driver time. This alert can be cleared if that time drops to 15 minutes. This field is true. | We modeled our testing using the FMCSA testing requirements along with our own internal testing and quality control procedures. | |
| ELD Plug-In | MW-ELD-J9D | 3.15 and higher | MW3792 | Download | Download | Mobile Warrior LLC | 888-474-9284 | customercare@mobilewarrior.com | http://www.mobilewarrior.com/corporate/ | 226 Marmalade Trail, Dawsonville, GA 30534 | From the Report Tab choose the ELD DOT Telemetry Report option and then choose to either send the Data Transfer File via the Wireless Web directly to the FMCSA Web Service account or to transfer the the file into an Email. Once the Email is displayed with the attached file, input the send to email required by the DOT and send it. | Power compliance P : If recorded event sequence find a possibility of in motion time then this ELD record will have a P set. A period of time of more then 30 minutes in the last 24 hours when a power on might have occurred. Field is set true. Time compliance T : If the data incoming from box indicates that the time is not consistent with the mobile device adjusted to the time zone of the driver. This field is set true if these are out of sync by 10 minutes. Engine sync compliance E : monitoring the data set of the last 24 hour of a period of time of more then 30 when the ELD was active and no j bus data is provided. This field is set true Position Location compliance L : must record a failure to track the current location for 60 minutes within 5 miles of the last known location. This will show last know location and time of recording it. Data Recording compliance R :This field is set true if the application is currently unable to create records or sync those records to the server. Monitoring record of unidentified drivers: If the vehicle has a 30 minute period in the last 7 days with unidentified driver time. This alert can be cleared if that time drops to 15 minutes. This field is true. | We modeled our testing using the FMCSA testing requirements along with our own internal testing and quality control procedures. | |
| ELD Plug-In | MW-ELD-O8D | 3.15 and higher | MW3846 | Download | Download | Mobile Warrior LLC | 888-474-9284 | customercare@mobilewarrior.com | http://www.mobilewarrior.com/corporate/ | 226 Marmalade Trail, Dawsonville, GA 30534 | From the Report Tab choose the ELD DOT Telemetry Report option and then choose to either send the Data Transfer File via the Wireless Web directly to the FMCSA Web Service account or to transfer the the file into an Email. Once the Email is displayed with the attached file, input the send to email required by the DOT and send it. | Power compliance P : If recorded event sequence find a possibility of in motion time then this ELD record will have a P set. A period of time of more then 30 minutes in the last 24 hours when a power on might have occurred. Field is set true. Time compliance T : If the data incoming from box indicates that the time is not consistent with the mobile device adjusted to the time zone of the driver. This field is set true if these are out of sync by 10 minutes. Engine sync compliance E : monitoring the data set of the last 24 hour of a period of time of more then 30 when the ELD was active and no j bus data is provided. This field is set true Position Location compliance L : must record a failure to track the current location for 60 minutes within 5 miles of the last known location. This will show last know location and time of recording it. Data Recording compliance R :This field is set true if the application is currently unable to create records or sync those records to the server. Monitoring record of unidentified drivers: If the vehicle has a 30 minute period in the last 7 days with unidentified driver time. This alert can be cleared if that time drops to 15 minutes. This field is true. | We modeled our testing using the FMCSA testing requirements along with our own internal testing and quality control procedures. | |
| ELD Plug-In | MW-ELD-J6D | 3.15 and higher | MW3914 | Download | Download | Mobile Warrior LLC | 888-474-9284 | customercare@mobilewarrior.com | http://www.mobilewarrior.com/corporate/ | 226 Marmalade Trail, Dawsonville, GA 30534 | From the Report Tab choose the ELD DOT Telemetry Report option and then choose to either send the Data Transfer File via the Wireless Web directly to the FMCSA Web Service account or to transfer the the file into an Email. Once the Email is displayed with the attached file, input the send to email required by the DOT and send it. | Power compliance P : If recorded event sequence find a possibility of in motion time then this ELD record will have a P set. A period of time of more then 30 minutes in the last 24 hours when a power on might have occurred. Field is set true. Time compliance T : If the data incoming from box indicates that the time is not consistent with the mobile device adjusted to the time zone of the driver. This field is set true if these are out of sync by 10 minutes. Engine sync compliance E : monitoring the data set of the last 24 hour of a period of time of more then 30 when the ELD was active and no j bus data is provided. This field is set true Position Location compliance L : must record a failure to track the current location for 60 minutes within 5 miles of the last known location. This will show last know location and time of recording it. Data Recording compliance R :This field is set true if the application is currently unable to create records or sync those records to the server. Monitoring record of unidentified drivers: If the vehicle has a 30 minute period in the last 7 days with unidentified driver time. This alert can be cleared if that time drops to 15 minutes. This field is true. | We modeled our testing using the FMCSA testing requirements along with our own internal testing and quality control procedures. | |
| ELD PRO CORP | ERS | 2.0 or higher | ERS154 | Download | Download | ELD Pro corp | 3313000132 | eldprocorp@gmail.com | http://eldprocorp.com | 671 Executive dr., Willowbrook, IL | ELD PRO CORP is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | ELD PRO CORP monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The ELD PRO CORP Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on ELD PRO CORP during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | ELD PRO CORP meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. ELD PRO CORP was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| ELD Rider | GEO-PT | 3.2.2 and higher | L86ELD | Download | Download | Darex Solutions | (708)221-9922 | info@eldrider.us | https://eldrider.us | 9550 Sergo Dr, Unit 104, Mc Cook, IL 60525, Mc Cook/IL/60525 | Telematic (Web Service, Email) | ELD Rider can transfer the ELD records via telematics transfer methods: wireless web services and email. For cases where the driver does not have an internet connection, ELD Rider supports an integrated display solution. To let a DOT Officer visually inspect daily logs, a driver must open the "DOT Inspection" tab from the app's left menu and tap "Begin Inspection". To send the Output File to a DOT Officer, a driver must tap "Transfer Data" from the same tab and insert Output File Comment if supplied by a DOT Officer. | ELD Rider software self-monitors for all malfunctions as required in section 4.6 of the ELD Mandate. It can detect all malfunctions and diagnostic events, including power, engine synchronization, timing, positioning, data recording, data transfer, required data elements, and unidentified driving. | ELD Rider certifies that it complies with the technical specification outlined in the 49 CFR Part 395 for Electronic Logging Devices, Subpart B. ELD Rider was tested according to the ELD Mandate as well as the ELD Compliance Test document in-house and also on a few fleets on the road and our test engineering team verified that the ELD Rider meets all the requirements from the ELD rule. |
| ELD Rider Lite | SIN-IOS | 3.2.2 and higher | L86ELD | Download | Download | Darex Solutions | (708)221-9922 | info@eldrider.us | https://eldrider.us | 9550 Sergo Dr, Unit 104, Mc Cook, IL 60525, Mc Cook/IL/60525 | Telematic (Web Service, Email) | ELD Rider Lite can transfer the ELD records via telematics transfer methods: wireless web services and email. For cases where the driver does not have an internet connection, ELD Rider Lite supports an integrated display solution. To let a DOT Officer visually inspect daily logs, a driver must open the “DOT Inspection” tab from the app’s left menu and tap “Begin Inspection”. To send the Output File to a DOT Officer, a driver must tap "Transfer Data" from the same tab and insert Output File Comment if supplied by a DOT Officer. | ELD Rider Lite software self-monitors for all malfunctions as required in section 4.6 of the ELD Mandate. It can detect all malfunctions and diagnostic events, including power, engine synchronization, timing, positioning, data recording, data transfer, required data elements, and unidentified driving. | ELD Rider Lite certifies that it complies with the technical specifications outlined in the 49 CFR Part 395 for Electronic Logging Devices, Subpart B. ELD Rider Lite was tested according to the ELD Mandate as well as the ELD Compliance Test document in-house and also on a few fleets on the road and our test engineering team verified that the ELD Rider Lite meets all the requirements from the ELD rule. |
| ELD RUNNER | ERS | 2.0 or higher | ERS257 | Download | Download | ELD RUNNER INC | 937-509-9829 | info@eldrunner.us | http://www.eldrunner.us | 541 INDIAN LAKE DR, MAINEVILLE/OH/45039 | ELD RUNNER is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | ELD RUNNER monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The ELD RUNNER Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on ELD RUNNER during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | ELD RUNNER meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. ELD RUNNER was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| ELD SEVEN | ERS | 2.0 or higher | ERS244 | Download | Download | MIORA GROUP INC | 630 566 0099 | go@eld7.com | http://eld7.com | 2446 W Arthington St, Oak Park, IL 60301 | ELD SEVEN is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | ELD SEVEN monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The ELD SEVEN Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on ELD SEVEN during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | ELD SEVEN meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations.ELD SEVEN was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| ELD SOLUTION | ERS | 2.18.2 and above | ERS155 | Download | Download | ELD Solution LLC | (864) 256-1427 | dannykobziev@gmail.com | portal.eldsol.com | 672 windward ln, Duncan SC 29334 | Local (Bluetooth) , Telematic (Web Service, Email) | In compliance with Title 49, Part 395 of Section 4.9.1, Appendix A, Subpart B CFR, drivers using ELD SOLUTION ELD system can transfer log data through telematics transfer methods. If an officer requires to review a driver's logs, the driver can produce a report on their mobile display or transfer logs data via web services or email. | The ELD SOLUTION ELD system self-monitors to identify malfunctions, as requested by Appendix A, section 4.6. A visual alert will indicate drivers of any malfunction or diagnostic event, including data recording, data transfer, required data elements, power, engine synchronization, timing, positioning, and unidentified driving. | The product has been tested as stated in the FMCSA's testing procedures. We certify that the hardware unit and mobile application combine into a compliant electronic logging system. Testing demonstrates that hours of service data is logged and transmitted correctly and that the functional requirements of 49 CFR Part 395 Subpart B are met. |
| ELD STAR | 1020 | 1.0 | ES2022 | Download | Download | ELD STAR LLC | 224 339-3345 | inbox@eldstar.com | http://eldstar.com | 1908 Thomes Avenue, Cheyenne, WY 82001, 1908 Thomes Avenue, Cheyenne, WY 82001 | Telematic (Web Service, Email) | ELD STAR is capable of producing and transferring the ELD records via Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “Inspection” menu item, select "Wireless Web Services" and press “SEND” button. In order to send the ELD records via Email, a driver must press “Inspection” menu item, select "Email" and press “SEND” button. | ELD monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The ELD STAR Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on ELD STAR during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | ELD STAR meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. ELD STAR was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. |
| ELD TAB | ERS | 2.0 or higher | ERS161 | Download | Download | ELD Tab | 7738707426 | eldtab2020@gmail.com | www.eldtab.site | 228 W Tanglewood Dr, Arlington Heights/Illinois/60004 | ELD TAB is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | ELD TAB monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The ELD TAB Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on ELD TAB during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | ELD TAB meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. ELD TAB was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| ELD Target | TEST000010 | 1.1 | ELD001 | Download | Download | Alexis Meyer | +55 21 96707-4127 | alexis.meyer@targetamericas.com | http://www.targetamericas.com/ | alexis.meyer@targetamericas.com, Mitre 1319 Florida Oeste, Buenos Aires, 1603 | The supported data transfer for ELD records are Web Service and Mail Insytructions to send the record Logs: 1.Log in to the Application 2.Navigate to inspection section 3.Tap on "Send Logs" and chose the method “Web Service” or “Mail” | EnablELD monitors the compliance for detectable malfunctions. When a malfunction is detected it appears on the bottom bar a "Malfunction icon" then when you touch it you see the error description: No Power (P) Engine Connection Malfunction (E) Timing malfunction (T) Position Malfunction (L) ELD Disconnection from App (R) Data Transfer Problem (S) | We certified the TargetELD through successful execution and verification of the FMCSA ELD Test Procedures. The TargetELD was certified installed on various types of Android and Apple phones, tested by few of the test procedures | |
| ELD Trucks 360 | ERS | 2.0 or higher | ERS162 | Download | Download | ELD Truck 360 | 2098147802 | info@eldtrucks360.com | http://eldtrucks360.com | 540 WINSTON CT, TRACY CA 95376 | ELD TRUCKS 360 is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | ELD TRUCKS 360 monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The ELD TRUCKS 360 Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on ELD TRUCKS 360 during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | ELD TRUCKS 360 meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations.ELD TRUCKS 360 was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| ELD VOLT | ERS | 2.0 or higher | ERS246 | Download | Download | Powe Deal Corp | 7735542463 | info@eldvolt.com | http://eldvolt.com | 8048 W CHARMAINE RD , Norridge IL 60706 | ELD VOLT is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | ELD VOLT monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The ELD VOLT Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on ELD VOLT during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | ELD VOLT meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. ELD VOLT was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| ELD-2000 | ELD-2000 | 10.0.4A or higher | GPSI01 | Download | Download | GPS Insight | 480-240-4414 | HOS@gpsinsight.com | http://gpsinsight.com | 7201 E. Henkel Way, Suite 400, Scottsdale, AZ 85255 | We have chosen to use wireless web services and email as our choice for the ELD output file. Instructions: Driver or Official will use the Options button on the driver overview screen Driver or Official will use the Roadside Inspection button on the drop down This button will navigate the user to a Logs Grid page The Logs Grid page will contain a button labeled "Transmit ELD Data File” The Officer will tap on the button and be instructed to choose email or wireless webservices and enter the instructions or code to send the data file to the FMCSA | Power - P; Device lost power during driving events for a total of 30 min or more over a 24-hour period Engine synchronization - E; Device lost connection to the ECM (or other data source) for a total of more than 30 min during a 24-hour period Timing - T; Device is not able to synchronize to UTC Positioning - L; Device is not able to acquire a valid position measurement within 5 mi of vehicle movement for a total of more than 60 min over a 24 hour period. Data recording - R; Device is no longer able to record or retain required event data or retrieve locally-stored recorded logs Data transfer- S; Device continues to fail checks of the roadside transfer mechanism for three days following a Data Transfer Diagnostic Event Other ELD detected - O; The eFleetSuite application has stopped working or is not responding as expected | GPS Insight certifies based on our completion of the testing procedures provided by the FMCSA in the Electronic Logging Device Test Plan and Procedures document version 2.0 dated 10/17/2016 that GPSI 2000 and complies with all Federal Motor Carrier Safety Administration (FMCSA) specifications as found in 49 CFR Part 395 for Electronic Logging Devices, Subpart B.Devices, Subpart B. | |
| ELD2020 Android | ELD2020A | 2.6.10.3231- higher | ELD20A | Download | Download | Hutch Systems Inc | 604-776-3564 | sales@hutchsystems.com | http://www.hutchsystems.com | 33443 Kirk Ave, Abbotsford, BC. V2S5Y8 | Telematic (Web Service, Email) | Hutch ELD2020A supports Wireless Web Services and Email data transport method. When the vehicle is stopped, an icon appears on the screen for the driver to transmit data to FMCSA via Web Services or Email. Once the driver chooses the option, ELD2020A allows the driver to enter a comment which will be included in the output file. The comment is left blank if driver does not enter any comment when generating the output file. After the comment, driver can click the transmit button to start the transmission of data to FMCSA (data transmitted is current 24hrs period and previous 7 or 8 days used be the motor carrier). When the transfer is completed, driver is displayed a message of successful transmission or an error. | The ELD 2020A is capable of monitoring its compliance for various required detectable malfunctions. When the ELD 2020 detects or clears each malfunction, an event is recorded. In the event a malfunction is recored, an Red light is displayed on the display describing to the user the malfunction logged. If the user clicks on the Icon, breif description is provide of the malfunction. The ELD2020A is capable of logging the Power Malfunction, Engine Synchronization Malfunction, Timing Compliance Malfunction, Postitioning Malfunction, Data Recording Malfunction, and Data Transfer Malfuntion. The ELD 2020A is capable of clearing malfunction automatically if the ELD 2020A becomes compliant with malfunction requirements. | This statement is to certify that the ELD 2020A android based application and the ELD 2020 hardware combined offering is in compliance with the U.S Department of Transportation ("DOT") and Federal Motor Carrier Safety Administration ("FMCSA") Electronic Logging Device ("ELD") for Hours-Of-Service ("HOS") requirements ("FMCSA ELD Requirements"), 49 CFR Part 395 Subpart B. The ELD 2020 has been verified with the testing procedures outlined by the FMCSA in Peterbilt 389 2015 model. The customers are required to operate the ELD2020A in accordance with opeartional instructions provided by Hutch Systems Inc. |
| ELD24K | IOSIX ELD | V 1.0 | TMX121 | Download | Download | Cromton Systems, Corp | 609-910-4210 | marketing@cromptonsystems.com | http://cromptonsystems.com | 50 Andover Dr , Kendal Park, NJ,08824 | We are using USB standard and the WinDriver USB toolkit, which supports this standard: • External connection, maximizing ease of use • Self-identifying peripherals supporting automatic mapping of function to driver and configuration • Dynamically attachable and re-configurable peripherals • Suitable for device bandwidths ranging from a few Kb/s to hundreds of Mb/s • Supports isochronous as well as asynchronous transfer types over the same set of wires • Supports simultaneous operation of many devices (multiple connections) • Supports a data transfer rate of up to 480 Mb/s (high-speed) for USB 2.0 (for the operating systems that officially support this standard) and up to 12 Mb/s (full-speed) for USB 1.1 • Guaranteed bandwidth and low latencies; appropriate for telephony, audio, etc. (isochronous transfer may use almost the entire bus bandwidth) • Flexibility: supports a wide range of packet sizes and a wide range of data transfer rates • Robustness: built-in error handling mechanism and dynamic insertion and removal of devices with no delay observed by the user • Synergy with PC industry; Uses commodity technologies • Optimized for integration in peripheral and host hardware • Low-cost implementation, therefore suitable for development of low-cost peripherals • Low-cost cables and connectors • Built-in power management and distribution • Specific library support for custom USB HID devices And provided for the Driver as a singled command button for to do this | Power Compliance Malfunction Engine Status Compliance Malfunction Positioning Compliance Malfunction Timing Compliance | The above mentioned unit has been tested in a simulated environment for 6 months. It has gone through an extensive field testing with actual field devices and truck for 3 months. All the documentation corresponds to the actual operating unit, as exits in the field. | |
| ELD24K | HDV100A3 | V 1.0 | TMX121 | Download | Download | Crompton Systems Corporation, Inc. | 609-910-4210 | SBK@Cromptonsystems.com | http://cromptonsystems.com | 50 Andover Dr., Kendall Park, NJ 08824 | We are using USB standard and the WinDriver USB toolkit, which supports this standard: • External connection, maximizing ease of use • Self-identifying peripherals supporting automatic mapping of function to driver and configuration • Dynamically attachable and re-configurable peripherals • Suitable for device bandwidths ranging from a few Kb/s to hundreds of Mb/s • Supports isochronous as well as asynchronous transfer types over the same set of wires • Supports simultaneous operation of many devices (multiple connections) • Supports a data transfer rate of up to 480 Mb/s (high-speed) for USB 2.0 (for the operating systems that officially support this standard) and up to 12 Mb/s (full-speed) for USB 1.1 • Guaranteed bandwidth and low latencies; appropriate for telephony, audio, etc. (isochronous transfer may use almost the entire bus bandwidth) • Flexibility: supports a wide range of packet sizes and a wide range of data transfer rates • Robustness: built-in error handling mechanism and dynamic insertion and removal of devices with no delay observed by the user • Synergy with PC industry; Uses commodity technologies • Optimized for integration in peripheral and host hardware • Low-cost implementation, therefore suitable for development of low-cost peripherals • Low-cost cables and connectors • Built-in power management and distribution • Specific library support for custom USB HID devices And provided for the Driver as a singled command button for to do this | Power Compliance Malfunction Engine Status Compliance Malfunction Positioning Compliance Malfunction Timing Compliance | The above mentioned unit has been tested in a simulated environment for 6 months. It has gone through an extensive field testing with actual field devices and truck for 3 months. All the documentation corresponds to the actual operating unit, as exits in the field. | |
| ELD365 | ELD386 | 2.1.399 | ATS001 | Download | Download | ELD365 | 888-858-1928 | support@eld365.com | http://www.eld365.com | 19083 COLIMA ROAD, ROWLAND HEIGHTS, CA 91748 | 1. Open the app 2. Click on View Logs 3. Click on Email Logs 4. Click send Logs (this page will both email logs and send them through the web service) | In addition to the malfunction and diagnostic event handling required by the ELD regulation, including all malfunction and data diagnostic events listed in table 4 of the FMCSA ELD Final Rule, we also alert the user when the vehicle is in motion and there is no identified driver, as well as instances where the driver’s business records indicate that he or she is not in the correct vehicle. P - "Power compliance" malfunction E - "Engine synchronization compliance" malfunction T - "Timing compliance" malfunction L - "Positioning compliance" malfunction R - "Data recording compliance" malfunction S - "Data transfer compliance" malfunction O - "Other" ELD detected malfunction 1 - "Power data diagnostic" event 2 - "Engine synchronization data diagnostic" event 3 - "Missing required data elements data diagnostic" event 4 - "Data transfer data diagnostic" event 5 - "Unidentified driving records data diagnostic" event 6 - "Other" ELD identified diagnostic event | A team of 11 developers and QA testers have performed unit and functional tests of the ELD across multiple version of Android software and hardware, using both simulators and actual vehicles to generate data. The Project Manager and Test Team Leader worked through the Requirements Traceability Matrix to create tasks for the developers to ensure every requirement was met in the ELD. As we came across any item we did not have available, we generated a project plan for that particular item and assigned it to a developer for completion. Once the item was complete, we released it to the testing team for testing. All of our testing is manual and done from the user’s point of view. We do not use any type of automated testing. For failed tests, the tester emails the result to the Test Team Leader. The developer assigned to the particular task fixes the error and completes the corrective action process. Once the corrective action process is complete, the new code is released and turned back over to the tester for regression testing. | |
| ELD365 ELOG | ELOG365 | 194 or higher | ELD365 | Download | Download | ELD365 | 9092221806 | support@eld365.com | http://www.eld365.com | 19069 COLIMA ROAD, ROWLAND HEIGHTS CA 91748 | To submit the Output File to an authorized safety official, the driver selects the “Export ELD Data File” from the Logbook screen. The driver, then, will select one of the following methods: - Agent External Storage: The ELD will first verify the external storage device is compatible with FMCSA specifications by validating the contents of file "ELDUSBTX.TXT". After positive validation the ELD will save the data file on the FMCSA-provided external storage device. - Bluetooth Transfer: After selecting this option, the authorized safety official will pair and verify PIN with the driver. Once the Bluetooth devices are paired, the safety official’s technology equipment will transfer the output file to the FMCSA website using Web services. | Low battery, network disconnection, low internal memory space, ECM data transfer failure, location sensor failure. In addition the following malfunctions are detected (and appropriate records created) by the Fleetilla ELD: - Power data diagnostic (diagnostic - 1) - Engine synchronization data diagnostic (diagnostic - 2) - Missing required data elements (diagnostic - 3) - Data transfer (diagnostic - 4) - Unidentified driving records data diagnostic (diagnostic - 5) - Other ELD diagnostics (diagnostic - 6 - Power compliance (malfunction - P) - Engine synchronization compliance (malfunction - E) - Timing compliance (malfunction - T) - Positioning compliance (malfunction - L) - Data recording compliance (malfunction - R) - Data transfer compliance (malfunction - S) - Other ELD malfunctions (malfunction - O) | The ELD365 ELOG was tested on a diverse range of CMVs from different manufacturers and models as well drivers with different experience and backgrounds. Tests were also performed on different environments (indoor, outdoor, inside and outside CMVs). Procedures and areas of examinations were followed according to the “ELD Test Plan and Procedures” version 1.0 document released by FMCSA on April 25th 2016. The Requirement Traceability Matrix (RTM) was used and fully verified to ensure ELD compliance. Corrective actions and regression tests were made on all Failed test results. | |
| Eld42 | Eld42-Android | 1.0.0 | ELD42A | Download | Download | BEMOREX, INC | (302) 406-0240 | info@safeeld.com | http:// | 1201 North Market Street, Suite 111-E58, Wilmington, DE 19801 | Local (USB, Bluetooth) , Telematic (Web Service, Email) | Data transfer is supported via telematics types, specifically web services and email. Open menu (upper left corner) Select “FMCSA” Select Send log to FMSCA via Web Send log to FMSCA via Email Enter data from inspector (if need) Press “Send” | Supported malfunctions: Power compliance, Engine synchronization compliance, Timing compliance, Positioning compliance, Data recording compliance, Data transfer compliance, Power data diagnostic, Engine synchronization data diagnostic, Missing required data elements data diagnostic, Data transfer data diagnostic, Unidentified driving records data diagnostic | The software was tested using the information provided in the Appendix to subpart B of part 395, title 49 of the code of Federal Regulations under the conditions in which the ELD would be used. The transfer files were tested using the FMCSA file validator. |
| ELD4TRUCKING | ERS | 2.21.32 and later | ERS174 | Download | Download | ELD4TRUCKING LLC | 8008464652 | info@eld4trucking.com | https://www.eld4trucking.com | 8 THE GRN STE 7923 , DOVER, DE 19901 | Telematic (Web Service, Email) | ELD4TRUCKING ELD software supports data transfer through telematics, meaning the driver can transfer their logs through wireless web services or email when an officer requests it. The app also enables the driver to display logs for the current shift and the previous seven consecutive days on their mobile device in case they do not have an internet connection during a roadside inspection. | ELD4TRUCKING has followed all necessary steps to ensure the hash feature functions properly. The hash feature is utilized to create a fixed-digit hexadecimal value to meet the requirements. ELD4TRUCKING allows cross-checking the authenticity of an ELD by adding both the “ELD Identifier” and the certificate part in the form of the provided authentication key. | ELD4TRUCKING ELD system has been subject to extensive testing according to the FMCSA's Test Plan and Procedures and has demonstrated compliance with the requirements for ELD solutions established in 49 CFR part 395, subpart B, appendix A. |
| ELD4Trucks | ELD4T200 | 1.0.0 or higher | E4TGPS | Download | Download | ELD4TRUCKS INC. | 630-410-9339 | support@eld4trucks.com | https://www.eld4trucks.com | 610 68TH ST WILLOWBROOK, IL 60527-5352, WILLOWBROOK/IL/60527-5352 | Telematic (Web Service, Email) | Transfer with FMCSA SOAP web services - ELD connects with FCMSA SOAP web services and submits: - our certificate (eld4truck_com.crt) - generated output file (Contents of the ELD output conforming to the standard outlined in section 4.8.2.1 of the Final Rule.) - output file comment - ELD Identifier (E4TGPS) - ELD Registration ID (An alphanumeric registration identifier assigned to the ELD provider that is registered with FMCSA during the ELD registration process) - output file name (Name of the ELD output file as defined in section 4.8.2.2 of the Final Rule). - version (a version of the ELD output file being submitted) Step by step instructions: To send your logs to an officer, from the main menu in the ELD4Trucks Mobile app, select Send logs and press button Send output file to send 8 logs (for current 24-hour period and the previous 7 consecutive days). You have to options: 1. Send email - transfer files through FMCSA email. ELD output file transferred is encrypted with AES-256 (AES cipher with a 256-bit key length) 2. Send with web services - transfer files with FMCSA’s public web services. If the roadside official tells you to enter an output file comment, enter text into Comment field. If you are not told to enter a comment, leave the field blank. 1. Email Press “Send Email” button. An XML file of your logs will be transferred through FMCSA email for the roadside official to access and review. 2. Web Services Press “Send with Web Services” button. An XML file of your logs will be transferred to the FMCSA for the roadside official to access and review. | Summary of Malfunctions: When a malfunction or data diagnostic event is detected or cleared by the ELD, the ELD records the event. The recorded malfunctions and data diagnostic events are inconsistencies found while monitoring the app/ELD against FMCSA compliance requirements. The malfunction codes are: Malfunction/Diagnostic Code Malfunction Description: • P “Power compliance” malfunction - The ELD missed 30 minutes or more of driving time due to not being powered across all driver profiles, including the unidentified driver profile • E “Engine synchronization compliance” malfunction - The ELD was unable to communicate with the vehicle for more than 30 minutes during a 24-hour period across all driver profiles, including the unidentified driver profile • T “Timing compliance” malfunction - The ELD detected that its clock was inaccurate by 10 minutes or more • L “Positioning compliance” malfunction - If ELD detects a problem acquiring a valid position measurement, a position malfunction is logged. The driver will also be prompted to make a manual location entry at the time of a duty status change if the ELD has not been able to acquire an accurate position measurement. The ELD will also log a position malfunction if the cumulative time between valid position measurements (within 5 miles) exceeds 60 minutes over a 24-hour period. • R “Data recording compliance” malfunction - The ELD ran out of available storage space for events. An ELD must monitor its storage capacity and integrity and must detect a data recording compliance malfunction if it can no longer record or retain required events or retrieve recorded logs that are not otherwise cataloged remotely by the motor carrier. • S “Data transfer compliance” malfunction - If ELD detects an issue with the data transfer mechanism or is unable to verify functionality within seven days, it will attempt to verify functionality every 24 hours for 72 hours. If it is unable to successfully verify data transfer through web services and email, a data transfer malfunction is logged. • O “Other” ELD detected malfunction - If ELD detects some other malfunction such as a hardware/software error, malfunction, or crash, it will log the event as Other Malfunction Malfunction/Diagnostic Code Data Diagnostic Event • 1 “Power data diagnostic” event - The ELD was not fully powered in under one minute, in which case, the ELD must record a power data diagnostics event for the corresponding driver(s), or under the unidentified driver profile if no drivers were authenticated at the time of detection. • 2 “Engine synchronization data diagnostic” event - Needed vehicle information was not able to be read within 5 seconds of needing the data from the vehicle’s data bus • 3 “Missing required data elements data diagnostic” event - Required fields for an event were not entered. If a new ELD event must be recorded at an instance when the ELD had failed to acquire a valid position measurement within the most recent elapsed 5 miles of driving, but the ELD has not yet set a positioning compliance malfunction, the ELD must record the character “X” in both the latitude and longitude fields, unless location is entered manually by the driver, in which case it must log the character “M” instead. If the ELD event is due to a change in duty status for the driver, the ELD must prompt the driver to enter location manually. If the driver does not enter the location information and the vehicle is in motion, the ELD must record a missing required data element • 4 “Data transfer data diagnostic” event - Tests to ensure the ELD is able to transfer logs during roadside safety inspections failed. This can also be triggered if there is an error while sending data from the app to the website, such as an incomplete upload, validation check error, or similar issue. If the monitoring mechanism fails to confirm proper in-service operation of the data transfer mechanism(s), an ELD must record a data transfer data diagnostic event and enter an unconfirmed data transfer mode • 5 “Unidentified driving records data diagnostic” event - The vehicle has drive time that is not associated with a driver. If more than 30 minutes of driving in a 24-hour period show unidentified driver on the ELD, the ELD must detect and record an unidentified driving records data diagnostic event and the data diagnostic indicator must be turned on for all drivers logged in to that ELD for the current 24-hour period and the following 7 days. An unidentified driving records data diagnostic event can be cleared by the ELD when driving time logged under the unidentified driver profile for the current 24-hour period and the previous 7 consecutive days drops to 15 minutes or less. | We declare that all FMCSA Regulation Testing Case were fulfilled and successfully passed |
| ELD995 | ELD995V15.1.0.19 | 1.1 and up | E99501 | Download | Download | Triesten Technologies LLC | 8473054030 (English), 2242155888 (Spanish) | submission@triesten.com | https://www.eld995.com/ | 4380 Redwood Hwy, Ste B8, San Rafael, CA - 94903 | Telematic (Web Service, Email) | Data Transfer Description× We at ELD995 support two type of data transfer mechanism. 1. Web services 2. Email Wireless data transfer : We will give out the following instructions to a driver to produce and transfer the ELD records, 1. We will create CSV file along with following information (under the FMCSA rule): company, driver details, trip details, co-driver details, shipping details, hours of service records, event log details, unidentified records for Vehicle (including comments for the inspection officer at the time of inspection). 2. For web service, we encrypt the content of the CSV file using AES encryption standards with authentication value and send it to the FMCSA API proviced. 3. For Email, we attach the CSV file and send it to FMCSA provided email id. Description of the supported and certified data transfer mechanisms and step-by-step instructions for a driver to produce and transfer the ELD records to an authorized safety official will be given to the driver. | ELD995 will support the following malfunctions: 1. Power compliance malfunction - If there is any issues while streaming vehicle data, we have recorded event log with power compliance. 2. Engine synchronization compliance malfunction - If there are any issues while connecting to the vehicle, we have recorded event log with Engine synchronization. 3. Timing compliance malfunction - When ELD no longer meet the underlying compliance requirement, we have recorded event log with timing compliance malfunction. 4. Positioning compliance malfunction - If there are any issues from latitude and longitude coordinates, we have recorded event log with positioning compliance malfunction. 5. Data recording compliance malfunction - If there is any issues while getting vehicle data like(VIN, Engine time, Odometer readings), we have recorded log for that incorrect data. 6. Data transfer compliance malfunction event - While transfer to FMCSA if there is any issue, we have captured as a data transfer malfunction. 7. Missing required data elements data diagnostic event - While recording the event if there is any required field missing, we have recorded log under missing required data elements data diagnostics (under FMCSA mandatory fields for the event). 8. Unidentified driving records data diagnostic event - If any unidentified event is detected (without user login), we have recorded log under unidentified driving records data diagnostic event. | We hereby certify that we have followed the process and procedures provided by FMCSA and executed cases that complies with the FMCSA regulations. |
| ELD-Express | ELDXP245 | 1 & up | EXP245 | Download | Download | ELD Express, LLC | + 1 (312) 7660177 | support@eld-express.com | www.eld-express.com | 1313 N Market St. Hercules Plaza, Wilmington, DE | ELD-Express solution supports Option 1 (Telematics Transfer methods) of 4.9.1 of Appendix A to Subpart B of 49 CFR 395. Using the driver app, drivers can initiate a data transfer using wireless webservices or using email. Drivers can initiate a data transfer via the "one-touch" DOT Inspection button on the HOS main page. This will allow for an Officer to review logs via the the mobile display , or transfer logs via webservices or email as desired | ELD Malfunctions On Logbook screen of ELD driver always sees the eld icon, if any malfunction occurs - the driver will be notified with a popup reporting information about the malfunction and suggestions on how the driver should try to resolve/fix it and eld icon will become red. Same time data about malfunction save into user history and will be displayed in inspection display/print data, eld data file. If any malfunctions are currently active - eld icon will be red and clicking on it will show current malfunctions information. Also, each eld customer will receive a printout, detailing possible malfunctions, how to identify them and steps to resolve it. If need any additional information - please provide more specific question, as nowhere in eld mandate/ELD Test Plan and Procedures specified what exactly should be pointed in this field(explanation, examples) Currently implemented malfunctions: -Power data diagnostic events - if ELD is not powered and fully functional within one minute of the vehicle’s engine receiving power -Power compliance malfunctions - if ELD is not powered for an aggregated in-motion driving time of 30 minutes or more over a 24-hour period across all driver profiles -Engine synchronization data diagnostic events - if no data comes from vehicle ecu's within five seconds of the need -Engine synchronization compliance malfunctions - if no data comes from vehicle ecu's for more than 30 minutes during a 24-hour period aggregated across all driver profiles. -Timing compliance malfunction - if ELD can no longer meet the underlying compliance requirement to record Coordinated Universal Time (UTC) -Positioning compliance malfunction - if ELD fails to acquire a valid position measurement within 5 miles of the commercial motor vehicle moving and 60 minutes has passed(gps failure) -Data recording compliance malfunction - occurs when an ELD can no longer record or retain required events or retrieve recorded logs that are not kept remotely by the motor carrier(memory limit, save failure) -Missing required data elements data diagnostic event - if any required data field is missing at the time of its recording(validation failure) -Data transfer data diagnostic event - if when the operation of the data transfer mechanism(s) is not confirmed(file generation failure, transfer failure) -Data transfer compliance malfunction - if ELD stays in the unconfirmed data transfer mode following the next three consecutive monitoring checks(file generation failure, transfer failure) -Unidentified driving records data diagnostic event - If ELD record driving event with no driver logged in for more than 30 minutes of driving time for an unidentified driver is recorded within a 24-hour period | ELD-Express was certified through successful execution and verification of the FMCSA ELD Test Procedures. The ELD-Expres was installed on various types and sizes of Android phones and tablets. Testing was performed through the use of a J1939 simulator and actual vehicles while having been connected to the Geometris, Digi WVA, CalAmp 4230, Pacific Track and IOSiX engine connected devices. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the Hours of Service web application (portal) that can be accessed through a web browser. | |
| ELDKIT | ERS | 2.0 or higher | ERS163 | Download | Download | Eldkit | 2242140990 | support@eldkit.net | http://eldkit.net | 700 Pintail Ct, Deerfield, IL 60015, Deerfield, IL 60015 | ELDKIT is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | ELDKIT monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The ELDKIT Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on ELDKIT during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | ELDKIT meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. ELDKIT was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| ELDMANDATE HOS | EMPT30 | 3.0.2212.220822 | EMpt30 | Download | Download | ELD Mandate | 800-968-1869 | ratan@eldmandate.biz | http://eldmandate.biz | 3158 Redhill Ave, Suite 100, Costa Mesa, CA 92626 | The ELDMANDATE HOS provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. Selecting the Data Transfer button from the Main HOS Main Screen will display the list of supported data transfer options which are via Bluetooth, Email, and USB. A Select Vehicle option is also available for selecting a vehicle upon performing the data transfer, this option enables the ELDMANDATE HOS to produce a data file or a series of data files of ELD records for a subset of its vehicles used by the driver. • Transfer via Bluetooth - this option enables the user to transfer files through Bluetooth. The ELD prompts for an output file comment which the driver may enter (optional). After the input, if Bluetooth is not yet turned on, a prompt will appear asking you to turn it on. You will then be asked to select the device name to which the data will be transmitted via Bluetooth. • Transfer via Email - this option enables the user to transfer files through email. The ELD output file transferred is encrypted using AES-256 in FIPS Publication 197. Before sending, the ELD prompts for an output file comment which the driver may enter (optional). The device's default email application will then be opened before sending the email to which the data will be transferred. • Transfer via USB - this option enables the user to transfer files through USB (external devices). However, prior to saving the driver’s ELD file to an external storage/device, the ELD re-authenticates the driver account by asking for its password | The ELDMANDATE HOS ELD is capable of monitoring its compliance for various detectable malfunctions. At each instance when an ELD malfunction event is detected or cleared by the ELDMANDATE HOS ELD, the ELD records the event. The recorded malfunction events are inconsistencies found while monitoring the ELD against FMCSA compliance requirements. Malfunction occurrences are indicated in the application header and in the Android notification toolbar with the letter ‘M’, respectively. The following shows the list of detectable malfunctions: • Power Malfunction • Engine Synchronization Malfunction • Timing Malfunction • Position Malfunction • Data Recording Malfunction • Data Transfer Malfunction Once the Malfunctions indicator ‘M’ is tapped, a dialog will be displayed with a list of the detected malfunction events alongside a ‘Clear’ button for each event. Tapping the Clear button will clear out the detected malfunction event. Procedure to validate an ELD authentication value 1. Concatenate the driver license number, ELD identifier, and ELD registration ID together. If there is no driver’s license number use the empty string for the driver license number. 2. Hash the value from step 1 using SHA-256. 3. Get the provider's public certificate in ASN.1 DER encoded form as a byte array. 4. Concatenate the byte array from step 2 with the byte array from step 3. 5. Hash the value from step 4 using SHA-256. 6. Take the first 16 bytes from the byte array in step 5 and convert the bytes into a hex string. The resulting 32-character string is the authentication value Certifying Statment of FMCSA Regulation Testing The ELDMANDATE ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The ELDMANDATE ELD was installed on various types and sizes of Android phones and tablets. Testing was performed using a J1939 simulator and actual vehicles while having been connected to the hardware device. A few of the test procedures, which are relevant to Motor Carriers, were verified using the Hours of Service web application (portal) that can be accessed through a web browser. | The ELDMANDATE ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The ELDMANDATE ELD was installed on various types and sizes of Android phones and Apple iOS phones and tablets. Testing was performed using a J1939 simulator and actual vehicles while having been connected to the hardware device. A few of the test procedures, which are relevant to Motor Carriers, were verified using the Hours of Service web application (portal) that can be accessed through a web browser. | |
| ELDROAD | ERS | 2.0 or higher | ERS142 | Download | Download | ELDROAD | 3129403513 | info@eldroad.com | http://eldroad.com | 370 whitewater dr apt 103, bolingbrook il 60440 | ELDROAD is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | ELDROAD monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The ELDROAD Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on ELDROAD during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | ELDROAD meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. ELDROAD was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| ELDWISE | EWS | 2.20.1 or up | EWS092 | Download | Download | NextParse LLC | +13028303677 | office@eldwise.app | https://www.eldwise.app/ | 16192 Coastal Highway, Lewes Delaware 19958 | Telematic (Web Service, Email) | ELDWISE system allows drivers to transfer log data through telematics methods in compliance with the regulations outlined in Title 49, Part 395, Section 4.9.1, Appendix A, Subpart B of the CFR. Drivers can also produce a report on their mobile display or transfer log data through web services or email if requested by an officer. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | As per the regulations outlined in Appendix A, section 4.6, the ELDWISE system continuously monitors itself for malfunctions. If a malfunction or diagnostic event occurs, such as issues with data recording, data transfer, or power, ELDWISE system will display a visual alert to the driver. This includes alerts for any issues with engine synchronization, timing, positioning, or unidentified driving. | As per the FMCSA's testing procedures, ELDWISE has undergone thorough testing to ensure compliance as an electronic logging system. ELDWISE can confirm that the system meets the requirements of 49 CFR Part 395 Subpart B, including the correct logging and transmission of hours of service data. |
| ELDX | XGEOAN | 1.0 and Above | ELDX03 | Download | Download | Gorilla Fleet Safety, LLC | 844-636-1360 | info@gorillasafety.com | http://www.gorillasafety.com | 22327 Gosling Rd, Spring, TX 77379 | This ELD uses the web services and email method of transmission. Driver, from the "Dashboard" page of their ELD, will tap on "Roadside Inspection," then "Send Logs." Once they tap send logs, any annotation or note requested by the inspecting officer can be entered by the driver prior to sending. | The malfunctions supported are: Power Compliance Malfunction Engine Synchronization Malfunction Timing Compliance Malfunction Positioning Compliance Malfunction Data Recording Malfunction Data Transfer Malfunction Each of these malfunctions appears prominently for the user to understand the issue. When the user is presented with this, he is able to rectify the situation, contact the manufacturer or use paper logs, as provided as part of the instruction guide, to remain compliant. The malfunctions and malfunction codes can be found in the instruction guide with the required details in order for the driver to understand what he needs to do next. | The product has been thoroughly tested by both internal and external, third party, testers. Each requirement of the ELD has been either met or exceeded. The process of review and testing included the full review of the ruling, testing procedures and debugging of any blocker found in the software package. It further included the retesting by additional quality assurance professionals. Ultimately, the programing and hardware operate as intended and are in compliance. | |
| ELEVEN ELD | ERS | 2.0 or higher | ERS183 | Download | Download | ELEVEN ELD | 2672558998 | eleveneld@gmail.com | www.11eld.com | 745 greymont st, Philadelphia PA 19116 | ELEVEN ELD is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | ELEVEN ELD monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The ELEVEN ELD Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on ELEVEN ELD during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | ELEVEN ELD meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. ELEVEN ELD was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| ELITE ELD | ERS | 2.0 or higher | ERS245 | Download | Download | ALPHA ELD INC | 9294128323 | saleseliteeld@gmail.com | http://eliteeld.com | 1461 EAST 28TH STREET 1 FLOOR BROOKLYN NY 11210, 1461 EAST 28TH STREET 1 FLOOR BROOKLYN NY 11210 | ELITE ELD is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | ELITE ELD monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The ELITE ELD Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on ELITE ELD during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | ELITE ELD meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. ELITE ELD was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| E-LOG | 1403 | 17081801 | ELOG01 | Download | Download | RM2J inc. | 844-440-4464 | info@e-codriver.com | www.e-codriver.com | 1490 Local A, Joliot-Curie, Boucherville, Quebec, J4B7L9 | Description of the supported and certified data transfer mechanisms: Option 1—Telematics transfer methods (Email) and Wireless Web service (when available). Step-by-step instructions for a driver to produce and transfer the ELD records to an authorized safety official: Starting from the ELD_Overview menu: * Select the "Inspection" button * {A comment may be entered in the comment textbox } To transfer to web service: *Click the "Send to web service" button To transfer over email : *Click the "Send over email" button For on-screen verification: *Click the "Show on screen" button | [1] DIAGNOSTIC_POWER A difference of at least 1 min was found between the engineHours reading of an engine turn-off and engine turn-on records, meaning that Eld was not powered within 1 minutes of the vehicle engine receiving power. [P] MALFUNCTION_POWER A cummulated difference of over 30 minute in the last 24h was detected. [2] DIAGNOSTIC_ENGINE_SYNC Access to motion status, engine operation, odometer and engine hour took at least 5 seconds to access when required. [E] MALFUNCTION_ENGINE_SYNC A cummulative 30 minutes of failed access to engine parameters in the last 24h was detected [3] DIAGNOSTIC_MISSING_DATA At the moment on record creation, either the location was unavailable, or the last known position was 5 mile or more from current location. [4] DIAGNOSTIC_DATA_TRANSFER The ELD failed to generate and/or transfer at least one of the possible report type. [S] MALFUNCTION_DATA_TRANSFER The ELD failed 4 consecutive time the report generation and transfer test. [5] DIAGNOSTIC_UNIDENTIFIED_DRV More than 30 minutes in a 24 hour period of driving time recorded to the unassigned driver profile. (in the last 7 day) [6] DIAGNOSTIC_OTHER The system is running low on memory [O] MALFUNCTION_OTHER System memory critically low [T] MALFUNCTION_TIMING System clock detected an offset of over 10 minutes when compared to UTC. [L] MALFUNCTION_POSITIONING The system failed to aquire GPS location for at least 5 driven miles, for a total of at least 60 minutes in a 24h period. OR The system failed to aquire GPS location at the moment of a record creation. [R] MALFUNCTION_RECORDING The system failed to save a record and had to remove previously synchronised record to keep working, report generation compromised... | Using the ELD_Test_Plan_and_Procedure_All_Chapters_11_2_2016.pdf file as a guideline, We created an excel file where row represent all test from 4.1.1-1 to 4.10.2.-1 (As of this writing, the file is available for download at https://www.fmcsa.dot.gov/hours-service/elds/eld-test-procedures) The column used for the file are • Id: Identification of the test matching the specification section (eg.4.10.1.3) • Part: Sub-section defining specific test (number following the “-” character (eg:4.10.1.3-2) • Date: Date of the test • Start: Starting time of the test • Stop: Ending time of the test • Status: Define the test actual status (Either Passed of Facultative) • Tester: Initials of the individual who did the test • Comment: Extra detail left by the tester about the test. (Either justification or Explanation) • Definition: Brief explanation of the test goal All tests were made manually by the development team. When a test passed, all field would be filled by tester. When a test Failed a comment detailing the reason was inputted in the comment column to be addressed by the developer, said test were re-done from the start once the problem was deemed fixed. | |
| Elog Driver | FM3001 | 2.51 | SS17EL | Download | Download | My Safe Fleet | 845-478-0011 | sales@mysafefleets.com | http://mysafefleets.com | 3193 Buffalo Ave, Niagara Falls, New York, 14303 | Description: Data Transfer through Web Services: Use the web service client (created from the schema available online), to submit the CSV file. Dim eldCLient As New EldSubmissionWebService.ELDSubmissionServiceClient Assign the certificate to the web service client through client credentials by declaring it as a new X509Certificate2. eldCLient.ClientCredentials.ClientCertificate = New X509Certificate2(certPath) Create the submission instance: Dim submission As New EldSubmissionWebService.ELDSubmission Assign the values to the submission instance of OutputFileComment (provided by the inspector), ELDIdentifier (provided by the FMCSA), ELDRegistrantId (the value registered with the FMCSA during registration process), OutputFilename (based on the 4.8.2.2 standard), OutputFileBody (reading the file as string and assigning it), Version (version1 based on the ENUM EldSubmissionWebService.FileVersion.V1) and Test (setting to True when testing and false in production). Submit the ELD submission instance through the web service client: Dim response As EldSubmissionWebService.ELDSubmissionResponse = eldCLient.Submit(submission) Data Transfer through Email: Data Transfer: We will be using the 256 bit key from the certificate to encrypt the CSV file and send it as an email. Steps to Decrypt: 1. Declare instance of AES with a key size of 256 and Block size of 128. Initialization vector (IV) is bytes from base64string of LmbXiR1IHfEqEBzlMV5N9Q== and 256 bytes from the RSA key of the public key certificate 2. Create AES decryption instance from the key and IV provided above 3. Use the decryption instance to decry-pt the the .AES file to .CSV Sending S/MIME Email: Declare SMTP instance for the email provided in the certificate Attach encrypted CSV and add the subject (routing information) and body (output file comment) as required Encrypt the email with AES 256 cipher and sign the email with our private key | 1. Power compliance: The tablet’s disconnection from power is recorded right then. The disconnection of the LMU results in LMU returning disconnected from power message through its internal battery. 2. Engine Synchronization: LMU device sends invalid identifier to the tablet if unable to read the engine parameters needed for the logs which is then recorded by the tablet as engine synchronization failure code. 3. Timing Compliance: Timings are measured through the LMU device’s GPS readings and the tablet’s UTC time which tablets sync with an online server. If unable to get the timing compliance, malfunction is recorded. 4. Positioning Compliance: Positions are received from LMU every 5 seconds and every minute from the inbuilt GPS of the tablet. If there is no valid GPS reading, the appropriate malfunction indicator is recorded. 5. Data Recording: If the device is unable to record or is missing the required elements to complete log event it is recorded. 6. Data Transfer: The application runs a background service which is awake and monitors the health of LMU device and tablet. Checks all the transmission of data requirements | I hereby certify that the device was tested as per FMCSA regulation testing. We tested it on Trans99 for over 1500 hours on 4 different units. Devices submitted logs at every action by the user and the monitoring services (which check the status of sensors, ECM reader, storage integrity checking etc) for further verification of the application working in compliance with the regulations. | |
| E-Log Plus | ELP0100 | 1.0.1905.190710 | ELP010 | Download | Download | E-Log Plus | 877-843-4773 | info@e-logplus.com | http://www.e-logplus.com | PO Box 201865, San Antonio Texas 78220 | The E-Log Plus provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. Selecting the Data Transfer button from the Main HOS Main Screen will display the list of supported data transfer options which are via Bluetooth, Email and USB. A Select Vehicle option is also available for selecting a vehicle upon performing the data transfer, this option enables the E-Log Plus to produce a data file or a series of data files of ELD records for a subset of its vehicles used by the driver. • Transfer via Bluetooth - this option enables the user to transfer files through Bluetooth. The ELD prompts for an output file comment which the driver may enter (optional). After the input, if Bluetooth is not yet turned on, a prompt will appear asking you to turn it on. You will then be asked to select the device name to which the data will be transmitted via Bluetooth. • Transfer via Email - this option enables the user to transfer files through email. The ELD output file transferred is encrypted using AES-256 in FIPS Publication 197. Before sending, the ELD prompts for an output file comment which the driver may enter (optional). The device's default email application will then be opened before sending the email to which the data will be transferred. • Transfer via USB - this option enables the user to transfer files through USB (external devices). However, prior to saving the driver’s ELD file to an external storage/device, the ELD re-authenticates the driver account by asking for its password. | The E-Log Plus ELD is capable of monitoring its compliance for various detectable malfunctions. At each instance when an ELD malfunction event is detected or cleared by the E-Log Plus ELD, the ELD records the event. The recorded malfunction events are inconsistencies found while monitoring the ELD against FMCSA compliance requirements. Malfunction occurrences are indicated in the application header and in the Android notification toolbar with the letter ‘M’, respectively. The following shows the list of detectable malfunctions: • Power Malfunction • Engine Synchronization Malfunction • Timing Malfunction • Position Malfunction • Data Recording Malfunction • Data Transfer Malfunction Once the Malfunctions indicator ‘M’ is tapped, a dialog will be displayed with a list of the detected malfunction events alongside a ‘Clear’ button for each event. Tapping the Clear button will clear out the detected malfunction event. | The E-Log Plus ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The E-Log Plus ELD was installed on various types and sizes of Android phones and tablets. Testing was performed through the use of a J1939 simulator and actual vehicles while having been connected to the Geometris, Digi WVA engine connected devices. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the Hours of Service web application (portal) that can be access through a web browser. | |
| E-Log Plus iOS | ELPiOS | 1905.190710 | ELP010 | Download | Download | E-Log Plus | 877-843-4773 | info@e-logplus.com | http://www.e-logplus.com | PO Box 201865, San Antonio Texas 78220 | The E-Log Plus provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. Selecting the Data Transfer button from the Main HOS Main Screen will display the list of supported data transfer options which are via Bluetooth, Email and USB. A Select Vehicle option is also available for selecting a vehicle upon performing the data transfer, this option enables the E-Log Plus to produce a data file or a series of data files of ELD records for a subset of its vehicles used by the driver. • Transfer via Bluetooth - this option enables the user to transfer files through Bluetooth. The ELD prompts for an output file comment which the driver may enter (optional). After the input, if Bluetooth is not yet turned on, a prompt will appear asking you to turn it on. You will then be asked to select the device name to which the data will be transmitted via Bluetooth. • Transfer via Email - this option enables the user to transfer files through email. The ELD output file transferred is encrypted using AES-256 in FIPS Publication 197. Before sending, the ELD prompts for an output file comment which the driver may enter (optional). The device's default email application will then be opened before sending the email to which the data will be transferred. • Transfer via USB - this option enables the user to transfer files through USB (external devices). However, prior to saving the driver’s ELD file to an external storage/device, the ELD re-authenticates the driver account by asking for its password. Description of the supported and certified data transfer mechanisms and step-by-step instructions for a driver to produce and transfer the ELD records to an authorized safety official | The E-Log Plus ELD is capable of monitoring its compliance for various detectable malfunctions. At each instance when an ELD malfunction event is detected or cleared by the E-Log Plus ELD, the ELD records the event. The recorded malfunction events are inconsistencies found while monitoring the ELD against FMCSA compliance requirements. Malfunction occurrences are indicated in the application header and in the Android notification toolbar with the letter ‘M’, respectively. The following shows the list of detectable malfunctions: • Power Malfunction • Engine Synchronization Malfunction • Timing Malfunction • Position Malfunction • Data Recording Malfunction • Data Transfer Malfunction Once the Malfunctions indicator‘M’ is tapped, a dialog will be displayed with a list of the detected malfunction events alongside a ‘Clear’ button for each event. Tapping the Clear button will clear out the detected malfunction event. | The E-Log Plus ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The E-Log Plus ELD was installed on various types and sizes of iOS phones and tablets. Testing was performed through the use of a J1939 simulator and actual vehicles while having been connected to the Geometris, Digi WVA engine connected devices. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the Hours of Service web application (portal) that can be access through a web browser. | |
| E-Log Plus Pacific Track | ELP-PC100 | 1.0.1905.190710 | ELP010 | Download | Download | E-Log Plus | 877-843-4773 | info@e-logplus.com | http://www.e-logplus.com | PO Box 201865, San Antonio Texas 78220 | The E-Log Plus provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. Selecting the Data Transfer button from the Main HOS Main Screen will display the list of supported data transfer options which are via Bluetooth, Email and USB. A Select Vehicle option is also available for selecting a vehicle upon performing the data transfer, this option enables the E-Log Plus to produce a data file or a series of data files of ELD records for a subset of its vehicles used by the driver. • Transfer via Bluetooth - this option enables the user to transfer files through Bluetooth. The ELD prompts for an output file comment which the driver may enter (optional). After the input, if Bluetooth is not yet turned on, a prompt will appear asking you to turn it on. You will then be asked to select the device name to which the data will be transmitted via Bluetooth. • Transfer via Email - this option enables the user to transfer files through email. The ELD output file transferred is encrypted using AES-256 in FIPS Publication 197. Before sending, the ELD prompts for an output file comment which the driver may enter (optional). The device's default email application will then be opened before sending the email to which the data will be transferred. • Transfer via USB - this option enables the user to transfer files through USB (external devices). However, prior to saving the driver’s ELD file to an external storage/device, the ELD re-authenticates the driver account by asking for its password. Description of the supported and certified data transfer mechanisms and step-by-step instructions for a driver to produce and transfer the ELD records to an authorized safety official | The E-Log Plus ELD is capable of monitoring its compliance for various detectable malfunctions. At each instance when an ELD malfunction event is detected or cleared by the E-Log Plus ELD, the ELD records the event. The recorded malfunction events are inconsistencies found while monitoring the ELD against FMCSA compliance requirements. Malfunction occurrences are indicated in the application header and in the Android notification toolbar with the letter ‘M’, respectively. The following shows the list of detectable malfunctions: • Power Malfunction • Engine Synchronization Malfunction • Timing Malfunction • Position Malfunction • Data Recording Malfunction • Data Transfer Malfunction Once the Malfunctions indicator‘M’ is tapped, a dialog will be displayed with a list of the detected malfunction events alongside a ‘Clear’ button for each event. Tapping the Clear button will clear out the detected malfunction event. | The E-Log Plus ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The E-Log Plus ELD was installed on various types and sizes of iOS phones and tablets. Testing was performed through the use of a J1939 simulator and actual vehicles while having been connected to the Geometris, Digi WVA engine connected devices. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the Hours of Service web application (portal) that can be access through a web browser. | |
| E-Log Plus iOSI | ELP-iOSI100 | 1.0.1905.190710 | ELP010 | Download | Download | E-Log Plus | 877-843-4773 | info@e-logplus.com | http://www.e-logplus.com | PO Box 201865, San Antonio Texas 78220 | The E-Log Plus provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. Selecting the Data Transfer button from the Main HOS Main Screen will display the list of supported data transfer options which are via Bluetooth, Email and USB. A Select Vehicle option is also available for selecting a vehicle upon performing the data transfer, this option enables the E-Log Plus to produce a data file or a series of data files of ELD records for a subset of its vehicles used by the driver. • Transfer via Bluetooth - this option enables the user to transfer files through Bluetooth. The ELD prompts for an output file comment which the driver may enter (optional). After the input, if Bluetooth is not yet turned on, a prompt will appear asking you to turn it on. You will then be asked to select the device name to which the data will be transmitted via Bluetooth. • Transfer via Email - this option enables the user to transfer files through email. The ELD output file transferred is encrypted using AES-256 in FIPS Publication 197. Before sending, the ELD prompts for an output file comment which the driver may enter (optional). The device's default email application will then be opened before sending the email to which the data will be transferred. • Transfer via USB - this option enables the user to transfer files through USB (external devices). However, prior to saving the driver’s ELD file to an external storage/device, the ELD re-authenticates the driver account by asking for its password. Description of the supported and certified data transfer mechanisms and step-by-step instructions for a driver to produce and transfer the ELD records to an authorized safety official | The E-Log Plus ELD is capable of monitoring its compliance for various detectable malfunctions. At each instance when an ELD malfunction event is detected or cleared by the E-Log Plus ELD, the ELD records the event. The recorded malfunction events are inconsistencies found while monitoring the ELD against FMCSA compliance requirements. Malfunction occurrences are indicated in the application header and in the Android notification toolbar with the letter ‘M’, respectively. The following shows the list of detectable malfunctions: • Power Malfunction • Engine Synchronization Malfunction • Timing Malfunction • Position Malfunction • Data Recording Malfunction • Data Transfer Malfunction Once the Malfunctions indicator‘M’ is tapped, a dialog will be displayed with a list of the detected malfunction events alongside a ‘Clear’ button for each event. Tapping the Clear button will clear out the detected malfunction event. | The E-Log Plus ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The E-Log Plus ELD was installed on various types and sizes of iOS phones and tablets. Testing was performed through the use of a J1939 simulator and actual vehicles while having been connected to the iOSI, Digi WVA engine connected devices. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the Hours of Service web application (portal) that can be accessed through a web browser. | |
| E-Log Plus IOSI iOSver | ELP-iOS100i | 1905.190710 | ELP010 | Download | Download | E-Log Plus | 877-843-4773 | info@e-logplus.com | http://www.e-logplus.com | PO Box 201865, San Antonio Texas 78220 | The E-Log Plus provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. Selecting the Data Transfer button from the Main HOS Main Screen will display the list of supported data transfer options which are via Bluetooth, Email and USB. A Select Vehicle option is also available for selecting a vehicle upon performing the data transfer, this option enables the E-Log Plus to produce a data file or a series of data files of ELD records for a subset of its vehicles used by the driver. • Transfer via Bluetooth - this option enables the user to transfer files through Bluetooth. The ELD prompts for an output file comment which the driver may enter (optional). After the input, if Bluetooth is not yet turned on, a prompt will appear asking you to turn it on. You will then be asked to select the device name to which the data will be transmitted via Bluetooth. • Transfer via Email - this option enables the user to transfer files through email. The ELD output file transferred is encrypted using AES-256 in FIPS Publication 197. Before sending, the ELD prompts for an output file comment which the driver may enter (optional). The device's default email application will then be opened before sending the email to which the data will be transferred. • Transfer via USB - this option enables the user to transfer files through USB (external devices). However, prior to saving the driver’s ELD file to an external storage/device, the ELD re-authenticates the driver account by asking for its password. Description of the supported and certified data transfer mechanisms and step-by-step instructions for a driver to produce and transfer the ELD records to an authorized safety official | The E-Log Plus ELD is capable of monitoring its compliance for various detectable malfunctions. At each instance when an ELD malfunction event is detected or cleared by the E-Log Plus ELD, the ELD records the event. The recorded malfunction events are inconsistencies found while monitoring the ELD against FMCSA compliance requirements. Malfunction occurrences are indicated in the application header and in the Android notification toolbar with the letter ‘M’, respectively. The following shows the list of detectable malfunctions: • Power Malfunction • Engine Synchronization Malfunction • Timing Malfunction • Position Malfunction • Data Recording Malfunction • Data Transfer Malfunction Once the Malfunctions indicator‘M’ is tapped, a dialog will be displayed with a list of the detected malfunction events alongside a ‘Clear’ button for each event. Tapping the Clear button will clear out the detected malfunction event. | The E-Log Plus ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The E-Log Plus ELD was installed on various types and sizes of iOS phones and tablets. Testing was performed through the use of a J1939 simulator and actual vehicles while having been connected to the iOSI, Digi WVA engine connected devices. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the Hours of Service web application (portal) that can be accessed through a web browser. | |
| E-Log Plus Pacific Track iOS | ELP-PC110 | 1905.190710 | ELP010 | Download | Download | E-Log Plus | 877-843-4773 | info@e-logplus.com | http://www.e-logplus.com | PO Box 201865, San Antonio Texas 78220 | The E-Log Plus provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. Selecting the Data Transfer button from the Main HOS Main Screen will display the list of supported data transfer options which are via Bluetooth, Email and USB. A Select Vehicle option is also available for selecting a vehicle upon performing the data transfer, this option enables the E-Log Plus to produce a data file or a series of data files of ELD records for a subset of its vehicles used by the driver. • Transfer via Bluetooth - this option enables the user to transfer files through Bluetooth. The ELD prompts for an output file comment which the driver may enter (optional). After the input, if Bluetooth is not yet turned on, a prompt will appear asking you to turn it on. You will then be asked to select the device name to which the data will be transmitted via Bluetooth. • Transfer via Email - this option enables the user to transfer files through email. The ELD output file transferred is encrypted using AES-256 in FIPS Publication 197. Before sending, the ELD prompts for an output file comment which the driver may enter (optional). The device's default email application will then be opened before sending the email to which the data will be transferred. • Transfer via USB - this option enables the user to transfer files through USB (external devices). However, prior to saving the driver’s ELD file to an external storage/device, the ELD re-authenticates the driver account by asking for its password. Description of the supported and certified data transfer mechanisms and step-by-step instructions for a driver to produce and transfer the ELD records to an authorized safety official | The E-Log Plus ELD is capable of monitoring its compliance for various detectable malfunctions. At each instance when an ELD malfunction event is detected or cleared by the E-Log Plus ELD, the ELD records the event. The recorded malfunction events are inconsistencies found while monitoring the ELD against FMCSA compliance requirements. Malfunction occurrences are indicated in the application header and in the Android notification toolbar with the letter ‘M’, respectively. The following shows the list of detectable malfunctions: • Power Malfunction • Engine Synchronization Malfunction • Timing Malfunction • Position Malfunction • Data Recording Malfunction • Data Transfer Malfunction Once the Malfunctions indicator‘M’ is tapped, a dialog will be displayed with a list of the detected malfunction events alongside a ‘Clear’ button for each event. Tapping the Clear button will clear out the detected malfunction event. | The E-Log Plus ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The E-Log Plus ELD was installed on various types and sizes of iOS phones and tablets. Testing was performed through the use of a J1939 simulator and actual vehicles while having been connected to the Geometris, Digi WVA engine connected devices. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the Hours of Service web application (portal) that can be access through a web browser. | |
| ELOG365 | ERS | 2.26.99 or higher | ERS127 | Download | Download | EZ ELD Solutions Inc | 18005567105 | sales@ezeldsolutions.com | http://www.ezeldsolutions.com | 5856 E Erin Ave, Fresno, CA 93727 | Telematic (Web Service, Email) | The ELOG365 ELD system transfers driver logs through an electronic data transfer method. Drivers can use the mobile app to send their logs via email or web services when needed. | Following Appendix A, section 4.6, the ELOG365 ELD system self-monitors for malfunctions, and any detected malfunctions are appropriately recorded in ELD data files; the driver receives visual alerts. | The product was thoroughly tested according to the ELD Compliance Test Procedures to meet all ELD Mandate requirements. We certify that these tests' results demonstrate the ELD meets the Functional Specifications for the ELD product. |
| ELOG42 | ERS | 2.18.4 and later | ERS156 | Download | Download | Leko INC | 850-724-1150 | elogs42@gmail.com | http://elog42.com | 653 Timberline Dr, Bolingbrook IL 60490 | Telematic (Web Service, Email) | The data transfer method utilized by ELOG42 ELD is telematics, which includes web services and email. To access DOT Inspection Mode, the driver can select "Start Inspection" to display logs for the safety officer, or choose "Email logs" to send them via email or "Send logs" to transfer them through web services. | ELOG42 ELD records any engine synchronization diagnostics or other malfunctions as per 49 CFR part 395, subpart B, Appendix A, section 4.6.1.2. The malfunction procedures are outlined in a document provided to users. | ELOG42 ELD certifies that the ELD has been tested and found to adhere to FMCSA's testing procedures, demonstrating compliance with federal legislation. Therefore, it meets the requirements of the ELD mandate. |
| E-Logbook | UE910-N3G | Version6.2 | TGL500 | Download | Download | I-Soft Global Software Solutions | 1-855-922-9700 | shan@trucksoft.net | http://trucksoft.net | 2020 W. Whitendale Ave, Visalia, CA 93277 | Method: Telematics. Both Web-services and Email is Available. 1. The Vehicle data is Transmitted via telematics. NOT Blue tooth. This Means even if the Mobile Device (Phone, Tablet etc.) is off, the driver's driving time is still monitored and Saved. And it's kept on the server. 2. The "DRIVING" MODE ON THE APP IS DETERMINED BY THE DATA PROVIDED BY THE VEHICLE AND ALWAYS WILL BE. NO MANUEL SELECTION IS ALLOWED WHILE IN MOTION / DRIVING MODE. THIS ENABLES TO KEEP THE DRIVING TIME TO ‘ACTUAL’ 3. ONCE THE VEHICLE IS STOPPED IF THE ENGINE IS TURNED OFF - IT WILL GO TO THE PREVIOUS MODE (OFF DUTY, ON DUTY, SLEEPER BIRTH) IF THE ENGINE IS IDLING – STILL ON DRIVE MODE FOR 210 SECONDS. THEN IT WILL GET OFF THE DRIVE MODE AND GO BACK TO THE PREVIOUS STATUS KNOWN. (OFF DUTY, ON DUTY, SLEEPER BIRTH) 4. The Driver logbook Graph is originated at the server level. So if the driver or any authority needs to see the logbook, once pressed the ‘Graph’ Button, the data and the graph is retrieved from the server and displayed. 5. Upon Request when pressed the "Report' button on the mobile device, the graph is being sent for view. 6. ALL DATA IS SAVED ONLY IN THE SERVER. | 1. Power compliance malfunction: Unless Plugged out of ECM port, there will be NO response from the device 2. Engine synchronization compliance malfunction: This failure occurs when ECM connectivity to any required data source such as engine power status, miles driven, engine hour, etc., is lost for more than 30 minutes during a 24-hour period aggregated across all drivers. 3. Positioning compliance malfunction: This occurs when the ELD is unable to obtain a valid position measurement within five miles of the truck moving and during a 60 minute period. 4. Data recording compliance malfunction: This happens when the ELD can’t record or retain events or can’t retrieve recorded logs that aren’t kept remotely. 5. Data transfer compliance malfunction: This failure occurs if the operation of the data transfer mechanism is in the unconfirmed data transfer mode during three consecutive monitoring checks | Under penalties of perjury, I, Shan, hereby certify on behalf of Shan Somasundaram that ELD model TGL500 and version Version6.2 has been sufficiently tested to meet the functional requirements included in the technical specifications in the Appendix to sub part B of part 395, title 49 of the Code of Federal Regulations, under the conditions in which the ELD would be used. | |
| eLogsPlus ELD | ELGPLS 2201 | 215 or higher | ELGP22 | Download | Download | E-Log Plus | 877-843-4773 | info@e-logplus.com | http://www.e-logplus.com | PO Box 201865, San Antonio Texas 78220 | Local (USB, Bluetooth) , Telematic (Web Service, Email) | To submit the Output File to an authorized safety official, the driver selects the “Export ELD Data File” from the Logbook screen. The driver, then, will select one of the following methods: - FMCSA web service: This option securely communicates to FMCSA's end-point ad obtains submission ID. - ELD Email Interface: This option transfer an encrypted email to FMCSA email address | Low battery, network disconnection, low internal memory space, ECM data transfer failure, location sensor failure. In addition, the following malfunctions are detected (and appropriate records created) by the ELGP22: - Power data diagnostic (diagnostic - 1) - Engine synchronization data diagnostic (diagnostic - 2) - Missing required data elements (diagnostic - 3) - Data transfer (diagnostic - 4) - Unidentified driving records data diagnostic (diagnostic - 5) - Other ELD diagnostics (diagnostic - 6 - Power compliance (malfunction - P) - Engine synchronization compliance (malfunction - E) - Timing compliance (malfunction - T) - Positioning compliance (malfunction - L) - Data recording compliance (malfunction - R) - Data transfer compliance (malfunction - S) - Other ELD malfunctions (malfunction - O) | The eLogsPlus ELD (ELGP22) was tested on a diverse range of CMVs from different manufacturers and models as well drivers with different experience and backgrounds. Tests were also performed on different environments (indoor, outdoor, inside and outside CMVs). Procedures and areas of examinations were followed according to the “ELD Test Plan and Procedures” version 1.0 document released by FMCSA on April 25th 2016. The Requirement Traceability Matrix (RTM) was used and fully verified to ensure ELD compliance. Corrective actions and regression tests were made on all Failed test results. |
| EMPIRE LOGS | EMPLGS | 2.18.02 and higher | EMP829 | Download | Download | EMPIRE ROADS LLC | 2678313744 | support@empirelogs.org | http://empirelogs.us | 1609 WHISPER GLEN DR PLAINFIELD, IL 60586, 1609 WHISPER GLEN DR PLAINFIELD, IL 60586 | Telematic (Web Service, Email) | EMPIRE LOGS, or Electronic Logging Device, is a tool that offers a comprehensive overview of a driver's records during a roadside inspection. Not only does it provide this information within the app, but it also facilitates the transfer of telematics data through email or web services. The DOT Inspection mode allows the driver to choose the method that works best for them. To transfer ELD records through Web services, the driver needs to access the "DOT Inspection" menu and select the "Send Logs" option. Then, they should choose Web Service as the Data Transfer Type and click the "SEND" button. Similarly, to transfer ELD records via Email, the driver should follow the same steps but select Email as the Data Transfer Type before clicking the "SEND" button. | The EMPIRE LOGS system ensures compliance with technical requirements, identifies malfunctions and data inconsistencies, and maintains records of such occurrences. Compliance malfunctions and diagnostic events are classified with specific codes, including P for "Power compliance" malfunction, E for "Engine synchronization compliance" malfunction, T for "Timing compliance" malfunction, L for "Positioning compliance" malfunction, R for "Data recording compliance" malfunction, S for "Data transfer compliance" malfunction, O for "Other" ELD-detected malfunctions, 1 for "Power data diagnostic" event, 2 for "Engine synchronization data diagnostic" event, 3 for "Missing required data elements data diagnostic" event, 4 for "Data transfer data diagnostic" event, 5 for "Unidentified driving records data diagnostic" event, and 6 for "Other" ELD-identified diagnostic events. The EMPIRE LOGS Malfunction and Diagnostic Event Records document all malfunctions that occurred during the relevant time period. Active malfunctions are communicated to all drivers who may use the ELD. | EMPIRE LOGS has been thoroughly tested to ensure compliance with all the functional requirements outlined in Title 49, Part 395 of Section 4.9.1, Appendix A, Subpart B. EMPIRE LOGS can confidently certify that our ELD product adheres to all the necessary ELD regulations. |
| Ensi Log | ENSIL | 2.16.01 or higher | ENS329 | Download | Download | Ensi Log | (317)775-8665 | info@ensilog.us | http:// | 1755 Park St suite 200, Naperville IL 60563 | Telematic (Web Service, Email) | ENSI LOG, or Electronic Logging Device, is a tool that offers a comprehensive overview of a driver's records during a roadside inspection. Not only does it provide this information within the app, but it also facilitates the transfer of telematics data through email or web services. The DOT Inspection mode allows the driver to choose the method that works best for them. To transfer ELD records through Web services, the driver needs to access the "DOT Inspection" menu and select the "Send Logs" option. Then, they should choose Web Service as the Data Transfer Type and click the "SEND" button. Similarly, to transfer ELD records via Email, the driver should follow the same steps but select Email as the Data Transfer Type before clicking the "SEND" button. | The ENSI LOG system ensures compliance with technical requirements, identifies malfunctions and data inconsistencies, and maintains records of such occurrences. Compliance malfunctions and diagnostic events are classified with specific codes, including P for "Power compliance" malfunction, E for "Engine synchronization compliance" malfunction, T for "Timing compliance" malfunction, L for "Positioning compliance" malfunction, R for "Data recording compliance" malfunction, S for "Data transfer compliance" malfunction, O for "Other" ELD-detected malfunctions, 1 for "Power data diagnostic" event, 2 for "Engine synchronization data diagnostic" event, 3 for "Missing required data elements data diagnostic" event, 4 for "Data transfer data diagnostic" event, 5 for "Unidentified driving records data diagnostic" event, and 6 for "Other" ELD-identified diagnostic events. The ENSI LOG Malfunction and Diagnostic Event Records document all malfunctions that occurred during the relevant time period. Active malfunctions are communicated to all drivers who may use the ELD. | ENSI LOG has been thoroughly tested to ensure compliance with all the functional requirements outlined in Title 49, Part 395 of Section 4.9.1, Appendix A, Subpart B. ENSI LOG can confidently certify that our ELD product adheres to all the necessary ELD regulations. |
| EPG Connect | EPG ELD 1 | 1.2.2 | EPGELD | Download | Download | EPG Solutions | 7275073130 | info@epgsolutions.net | http://www.epgsolutions.net | 13141 66th St. N, Largo, FL 33782 | EPG Connect uses the telematics data transfer option. Driver will select the "Email Logs" link or the "Transfer Logs" link on the records page to share the records via email or web services. User manual includes instructions and screenshots of the application. | EPG Connect will recognize the main malfunctions: Power, Engine Synchronization, Timing, Positioning, Data Recording and Other. The malfunctions are programmed using FMCSA technical documentation as a guide. Power Malfunction: No power information from ECM while Vehicle is in motion for an aggregated 30 minutes or more, over a 24-hour period. Engine Synchronization: No engine information or no link to the vehicle ECM, for more than an aggregated 30 minutes during a 24-hour period. Timing: Unable to verify its timing accuracy Positioning: No valid position measurement within 5 miles of the CMV’s movement, while the malfunction persists for 60 minutes over a 24-hour period. Data Recording: No recording or retaining of required events or no ability to retrieve recorded logs that are not otherwise stored remotely. Other: All other malfunctions not covered in the previous categories. Data Test Malfunctions: EPG Connect has been tested to verify the data transfer functionality and the data output file, using the FMCSA data file checker. The web service transfer was tested in house, utilizing the FMSCA web service coding schema. Additionally the data transfer through email was tested in house utilizing FMCSA email format as guide, to check for functionality and correct format. Data transfer check will occur once every 7 days automatically, without driver input. In the event that data transfer is not able to complete the self-test, EPG Connect will start checking every 24 hours. After 3 failed data transfer checks, EPG Connect will save the event as data transfer malfunction. | I am certifying that EPG Solutions, EPG Connect, has been tested to the best of my knowledge, to meet the functional requirements included in the ELD specifications, under the conditions in which the ELD would be used. I am self certifying that EPG Connect ELD constitutes an electronic signature conveying acceptance of the rules of behavior in FMCSA mandate. | |
| EPG Connect iOS Phone | EPG ELD 2 | 1.4 | EPGIPH | Download | Download | EPG Solutions | 7275073130 | info@epgsolutions.net | http://www.epgsolutions.net | 13141 66th St. N, Largo, FL 33782 | EPG Connect uses the telematics data transfer option. Driver will select the "Email Logs" link or the "Transfer Logs" link on the Roadside Inspection page to share the records via email or web services, and enter the required output comments. User manual includes instructions and screenshots of the application. | EPG Connect will recognize the main malfunctions: 1. Power Malfunction: No power information from ECM while Vehicle is in motion for an aggregated 30 minutes or more, over a 24-hour period. 2. Engine Synchronization: No engine information or no link to the vehicle ECM, for more than an aggregated 30 minutes during a 24-hour period. 3. Timing: Unable to verify its timing accuracy. 4. Positioning: No valid position measurement within 5 miles of the CMV’s movement, while the malfunction persists for 60 minutes over a 24-hour period. 5. Data Recording: No recording or retaining of required events or no ability to retrieve recorded logs that are not otherwise stored remotely. 6. Other: All other malfunctions not covered in the previous categories. Data Test Malfunctions: EPG Connect has been tested to verify the data transfer functionality and the data output file, using the FMCSA data file checker. The web service transfer was tested in house, utilizing the FMSCA web service coding schema. Additionally, the data transfer through email was tested in house utilizing FMCSA email format as guide, to check for functionality and correct format to include the Data Transfer check will occur once every 7 days automatically, without driver input. If data transfer is not able to complete the self-test, EPG Connect will start checking every 24 hours. After 3 failed data transfer checks, EPG Connect will save the event as data transfer malfunction. The malfunctions are programmed using FMCSA technical documentation as a guide. | I am certifying that EPG Solutions, EPG Connect, has been tested to the best of my knowledge, to meet the functional requirements included in the ELD specifications, under the conditions in which the ELD would be used. The testing was done on J1939 capable vehicles, and utilizing the FMCSA testing procedures document as guide. I am self-certifying that EPG Connect ELD constitutes an electronic signature conveying acceptance of the rules of behavior in FMCSA mandate. | |
| EPG Connect iOS Tablet | EPG ELD 3 | 1.3 | EPGIOS | Download | Download | EPG Solutions | 7275073130 | info@epgsolutions.net | http://www.epgsolutions.net | 13141 66th St. N, Largo, FL 33782 | EPG Connect uses the telematics data transfer option. Driver will select the "Email Logs" link or the "Transfer Logs" link on the Roadside Inspection page to share the records via email or web services, and enter the required output comments. User manual includes instructions and screenshots of the application. | EPG Connect will recognize the main malfunctions: 1. Power Malfunction: No power information from ECM while Vehicle is in motion for an aggregated 30 minutes or more, over a 24-hour period. 2. Engine Synchronization: No engine information or no link to the vehicle ECM, for more than an aggregated 30 minutes during a 24-hour period. 3. Timing: Unable to verify its timing accuracy. 4. Positioning: No valid position measurement within 5 miles of the CMV’s movement, while the malfunction persists for 60 minutes over a 24-hour period. 5. Data Recording: No recording or retaining of required events or no ability to retrieve recorded logs that are not otherwise stored remotely. 6. Other: All other malfunctions not covered in the previous categories. Data Test Malfunctions: EPG Connect has been tested to verify the data transfer functionality and the data output file, using the FMCSA data file checker. The web service transfer was tested in house, utilizing the FMSCA web service coding schema. Additionally, the data transfer through email was tested in house utilizing FMCSA email format as guide, to check for functionality and correct format to include the Data Transfer check will occur once every 7 days automatically, without driver input. If data transfer is not able to complete the self-test, EPG Connect will start checking every 24 hours. After 3 failed data transfer checks, EPG Connect will save the event as data transfer malfunction. The malfunctions are programmed using FMCSA technical documentation as a guide. | I am certifying that EPG Solutions, EPG Connect, has been tested to the best of my knowledge, to meet the functional requirements included in the ELD specifications, under the conditions in which the ELD would be used. The testing was done on J1939 capable vehicles, and utilizing the FMCSA testing procedures document as guide. I am self-certifying that EPG Connect ELD constitutes an electronic signature conveying acceptance of the rules of behavior in FMCSA mandate. | |
| ERETH ELD | ERS | 2.0 or higher | ERS238 | Download | Download | ERETH ELD INC | (786) 654-8900 | info@eretheld.com | http://eretheld.com | 17150 N Bay Rd , Apt 2419, Sunny Isles Beach, FL, 33160 | ERETH ELD is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | ERETH ELD monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The ERETH ELD Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on ERETH ELD during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | ERETH ELD meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations.ERETH ELD was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| EROAD ELD | Ehubo 2 | v1.73.309 or higher | EROAD1 | Download | Download | EROAD | 855-503-7623 | eld@eroad.com | www.eroad.com/eld | 15110 Avenue of Science Suite 100, San Diego,CA,92128 | Telematic (Web Service, Email) | EROAD ELD supports Option 1, Telematics transfer methods, of both the Wireless Web services and Email to transfer the generated ELD data output to the computing environment used by the authorized safety official. Instructions for a driver to produce and transfer the ELD records using EROAD ELD: Email Transfer Step 1. From the driver’s “Logs” screen, tap the “Roadside” icon. Step 2. Tap the “Transfer” button. Step 3. Select the option for “Email”. Step 4. Enter the Safety Official Code in the “Comment” field. Step 5. Tap the “Send” button to complete the transfer. A confirmation message will confirm whether the file was transferred successfully. Web Services Transfer Step 1. From the driver’s “Logs” screen, tap the “Roadside” icon. Step 2. Tap the “Transfer” button. Step 3. Select the option for “Web Services”. Step 4. Enter the Safety Official Code in the “Comment” field. Step 5. Tap the “Send” button to complete the transfer. A confirmation message will confirm whether the file was transferred successfully. EROAD certifies that the capability for the Wireless Web Services and Email methods to transfer the ELD data output has been developed and will validate against FMCSA’s test procedures, when they are finalized. | EROAD ELD has the capability to monitor, detect and record events related to malfunctions and data inconsistencies. Malfunction Events Code P – “Power Compliance” – is caused by more than 30 minutes of driving time lost in a 24-hour period. Code E – “Engine Synchronization Compliance” – is caused by more than 30 minutes without ECM engine synchronization over a 24-hour period. Code T – “Timing Compliance” – is caused by a clock discrepancy equal to or exceeding 10 minutes when the ELD synchronizes its time. Code L – “Positioning Compliance” – is caused by the accumulated driving time without a valid position in the first 5 miles of movement exceeding 60 minutes in a 24-hour period. Code R – “Data Recording Compliance” – is caused by an inability to store new events due to either a lack of free storage capacity or a hardware fault. Code S – “Data Transfer Compliance” – is caused by a failure to communicate for three days following a Data Transfer Data Diagnostic event. Data Diagnostic Events Code 1 - “Power Data Diagnostic” - is caused by the ELD not fully functioning within one minute of the engine power on and may be due to wiring or power source fault. Code 2 – “Engine Synchronization Data Diagnostic” – is caused by a wiring or connection fault resulting in a delay of more than 5 seconds in acquiring ECM data. Code 3 – “Missing Required Data Elements Data Diagnostic” – is caused by missing required data due to either a loss of position fix or failed connection to the vehicle’s ECM. Code 4 – “Data Transfer Data Diagnostic” – is caused by the ELD failing to communicate records to the back-end system for seven continuous days. Code 5 – “Unidentified Driving Records Data Diagnostic” – is caused by vehicle being utilized for more than 30 minutes in a 24-hour period without a driver logging in. | We certify that EROAD ELD has been tested to meet the requirements as specified in the "Functional Specifications for All ELDs" document and has been tested against "Test Plan and Procedures" provided by FMCSA. EROAD ELD product has been tested on different levels - back-end, service layer, firmware, UI/screen based - with a mix of automated and manual testing using a number of different environments. Testing and verification of the ELD product has been conducted using: - Test benches with USB-to-CAN adapters to generate specific ECM messages and malfunctions when needed, - Test labs for automated testing of vehicle speed, distance, engine speed and response to VIN and engine hours requests, - Real vehicles to validate our ECM connection works correctly and complies with the mandate in real world situations. We have internal controls and standards to document and track our test processes, development tasks, and any issues that arise during the testing and ensure that all issues are resolved to comply with the technical regulatory requirements. Final end-to-end testing has been performed by a group of test engineers, executing and signing off every test procedure from the "Test Plan and Procedures" documents provided by FMCSA. |
| ETS ELD | ERS | 2.0 or higher | ERS268 | Download | Download | ETS ELD | +1 (612) 268-5715 | provider@etseld.com | http://www.etseld.com/ | 9N RITTERS LN, OWINGS MILLS, MD 21117, OWINGS MILLS, MD 21117 | ETS ELD is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | ETS ELD monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The ETS ELD Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on ETS ELD during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | ETS ELD meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. ETS ELD was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| EveryFleet | LMU-4230 | v1 | VC4230 | Download | Download | EveryFleet | +1 (401) 821-2900 | efsupport@everyfleet.com | https://everyfleet.com | 141 James P. Murphy Ind. Hwy, West Warwick, RI 02893 | Data Transfer Description Vika ELD Data can be transferred to FMCSA through email or web service. To produce and transfer the ELD records to an authorized safety official driver need to follow these steps. Login to vika driver app Go to HOS page from left navigation menu From HOS page click on DOT button available in header section This page can be shown to safety officer for logs of that day and last 7 days Click on paper plane icon in header section of the DOT Page to transfer to FMCSA It will show 2 methods to transfer the data (Email or web service) Driver can choose a method to transfer logs of that day to FMCSA | Summary of Malfunctions “Power compliance” malfunction: An ELD must be powered and become fully functional within 1 minute of the vehicle’s engine receiving power and must remain powered for as long as the vehicle’s engine stays powered. ELD app monitor when the device may not have complied with the power source. If the aggregated in-motion driving time increases 30 minutes or more on the ELD over a 24-hour without power source, it creates power compliance malfunction. “Engine synchronization compliance” malfunction: ELD app monitor the data it receives from the engine ECM for power, vehicle motion status, vehicle miles, Engine hours. ELD set an engine synchronization compliance malfunction if connectivity to any of these data sources is lost for more than 30 minutes during a 24-hour period aggregated. “Timing compliance” malfunction: The ELD periodically cross-check its compliance with respect to an accurate external UTC source and it record a timing compliance malfunction when it no longer meet the requirement. “Positioning compliance” malfunction: ELD monitor elapsed time during periods when the ELD fails to acquire a valid position measurement within 5 miles of the CMV’s movement. When such elapsed time exceeds a cumulative 60 minutes over a 24 hour period, the ELD set and record a positioning compliance malfunction “Data recording compliance” malfunction: ELD detect a data recording compliance malfunction if it can no longer record or retain required events “Data transfer compliance” malfunction: ELD verifies data transfer functionality once every 7 days. If the monitoring mechanism fails to confirm proper in-service operation of the data transfer mechanism, ELD increases the frequency of the monitoring function to check at least once every 24-hour period. If the ELD stays in the unconfirmed data transfer mode following the next three consecutive monitoring checks, the ELD detect a data transfer compliance malfunction. | Certifying Statement of FMCSA Regulation Testing: I hereby certify that the Vika ELD / HOS / DVIR device has been built and tested to the specifications and regulations promulgated by the FMCSA and complies with all record keeping standards and requirements. Appendix to subpart B of part 395, title 49 of the Code of Federal Regulations, eldtestplanandprocedures07-18-201721-all-chapters.pdf ELD_ICD_Development_Handbook.pdf | |
| EVO ELD 1 | EVO 1 | 1.0.0 | G711H2 | Download | Download | Evo ELD Inc. | 585-877-0777 | sales@evoeld.com | https://evoeld.com | 3864 Center rd Unit-A12, Brunswick OH 44212 | Evo ELD platform work for recording, storing and transferring the ELD information through telematics method of transferring. To transfer information, client should utilize Web services and Email. Transferring information to authorized safety official with web service makes two strides, first go to "INSPECTION" from menu bar and afterward press "SEND ELD OUTPUT FILE". All together, send the ELD information with Email, Driver ought to go to "INSPECTION" from menu bar and press "EMAIL LOGS" then, at that point, press "SEND LOGS". | The Evo ELD hardware fit for observing its consistence with specialized prerequisite and identifies malfunctions and tracks its malfunction. Adhering to guideline coding is executed for required consistence malfunction and data symptomatic event location: P - "Power consistence" malfunction, E - "Motor synchronization consistence" malfunction, T - "Timing consistence" malfunction, L - "Situating consistence" malfunction, R - "Data recording consistence" malfunction, S - "Data move consistence" malfunction, O - "Other" ELD recognized malfunction, 1 - "Power data indicative" event, 2 - "Motor synchronization data analytic" event, 3 - "Missing required data elements data demonstrative" event, 4 - "Data move data symptomatic" event, 5 - "Unidentified driving records data demonstrative" event, 6 - "Other" ELD distinguished indicative event. All Evo ELD malfunctions are put away and can pull out when data required for additional examination. Assuming that any malfunction happens - driver will be told with a popup portraying data about the malfunction. | Evo ELD was tested utilizing the FMCSA's suggested testing systems. This was enhanced by Evo ELD inside testing strategies. | |
| EXPRESS LINE ELD | ERS | 2.0 or higher | ERS147 | Download | Download | Express Line ELD | 8312125558 | expresslineeld@gmail.com | http://www.expressline.site | #786 South Street , Hollister California 95023 | EXPRESS LINE ELD is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | EXPRESS LINE ELD monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The EXPRESS LINE ELD Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on EXPRESS LINE ELD during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | EXPRESS LINE ELD meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. EXPRESS LINE ELD was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. | |
| EXPRESS WAY ELD | ERS | 2.13.15 and later | ERS172 | Download | Download | Eco Trans Inc | 4407971101 | expresswayeld@gmail.com | www.expresstrucking.xyz | 3920 Gallatin Pike, Nashville/TN/37216 | Telematic (Web Service, Email) | EXPRESS WAY electronic logging system supports telematics data transfer through email or web services. Details on how to transfer logs are outlined in the instructions provided to drivers. Logs report can also be shown to a DOT officer directly on the driver's mobile device in a seprate DOT Inspection Mode. | EXPRESS WAY ELD monitors its compliance continuously to detect malfunctions and diagnostic events. Inconsistencies found as a result of the self-monitoring function are considered malfunction events, and all detected or cleared events are recorded. | After the successful implementation of the FMCSA's ELD Test Plan and Procedures, EXPRESS WAY ELD compliance has been verified. EXPRESS WAY ELD certifies that the system is fully compliant. |
| EXTENDED ROAD ELD | ERS | 2.20.5 & above | ERS215 | Download | Download | Extended Road LLC | 6468868899 | Extendedroadllc@gmail.com | http://www.extendedroadllc.com | 7340 Cayman way, Mainville, OH 45039 | Telematic (Web Service, Email) | Our system supports Web Services and Email data transfers in which the data for the submitted period is aggregated and converted to the appropriate CSV notation. The file is appropriately encrypted and submitted via the selected method. To initiate a transfer a driver must navigate to the Inspection tab in the App, select the transfer method, and fill out the comment field, as indicated by the officer conducting the inspection, then press send. | EXTENDED ROAD ELD system self-monitors for all appropriate malfunctions as specified in Appendix A section 4.6. Also as required in section 4.6, when a malfunction is detected, it is reported as required in ELD data file(s) and visually indicated on the ELD system as required by 4.6.2.1. | We hereby certify that we have executed FMCSA test plans and procedures and test procedure complies with the FMCSA regulation. |
| EYELOG | ELD-SM-JA | 1.2.7 | ELOG01 | Download | Download | EYERIDE | 833 EYERIDE | info@eyeride.io | https://eyeride.io | 113 E Main St , Pflugerville, TX 78660 | EYERIDE’s ELD supports wireless data transfer methods via email or web services. The following steps outline the process of transferring ELD records to an authorized safety official. 1. Navigate to the “Roadside Inspections” screen by clicking on the “Roadside” tab in the main tabbed navigation bar. 2. Click on “Begin Inspection” button. 3. The driver can then review logs. 4. If logs are accurate click on “Send Logs” 5. Choose the appropriate transfer method 6. If email is chosen then the user may input multiple email addresses to where the logs will be sent. Finally, click “Send” 7. If web services is chosen, the App will automatically send the logs to FMCSA servers | If an ELD malfunctions and connection is lost between the host tablet and client Bluetooth device, the ELD will display a warning stating that connection to the ECM has been lost. In this case, the connection will try to be recovered automatically. The ELD will make periodic requests to reconnect to the last known Bluetooth device. Also, the ECM connected hardware will automatically restart itself at a specified interval if there is no communication to the host device. This is to make sure that the ECM connected hardware is not in a blocked state. The ELD uses the required Web Services/Email output options. However, both of these options require internet connectivity. Therefore, a malfunction may be observed if an attempt is made to send logs while the ELD does not have internet connection. To work around this, we have also implemented local USB transfer methods. Even if this malfunction is encountered, drivers may still export their logs via portable USB drives. | We have used the test procedures provided by the FMCSA, and have had positive test results on all test cases. | |
| EZ DriverLog | BlueLink | 4.4.9 | WLI001 | Download | Download | EZ TRACK | 011526864887010 | contacto@eztrack.mx | http://www.eztrack.mx | 1101 Ollie Ave #3906, Calexico, CA , 92232 | When entering an inspection scenario, the driver follows the instructions provided on his printed one page manual which instructs the driver to press the "Officer Button" located on the top right of the DriverLog app home screen display. This will launch the Officer View. The Officer view features a "Send" button and an Add comment button, which allows the officer to enter his identifier and send out the ELD data file through web services or email (Both options are available) Following the guidance of the ELD Section of the Federal Register...section "4.10.1. Data Transfer Mechanisms", we allow the officer to use both e-mail or Web Services to transfer the driver's data to the official FMCSA ELD e-mail address or the FMCSA's Web Service repository, Currently the e-mail is formatted exactly to section "4.10.1.2. Wireless Data Transfer Through Email", specifications stated in the Federal Register. Web Services will utilize the SOAP protocol, per the FMCSA documentation, to transmit the ELD data file and the output file comment entered by the inspecting officer. | Malfunction detection is robustly executed to contain all malfunction scenarios listed in "Table 4" of the Driver Log final rule. this malfunctions include, Power compliance which monitor the unidentified Driver activity. Engine Synchronization verifies that we are connected to the vehicle's ECM. Timing which validates successful synchronization with UTC time. Positioning continuously monitor the accuracy of our GPS data. Data Recording monitors available storage capacity on our device. Data Transfer checks at least ones a week for connectivity to an online service . in addition to the FMCSA's required malfunctions reports, our proprietary error checking , logs the wellness of the device and reports this data back to our support team for instant feedback. | We certify that our ELD application and related hardware have been tested to meet the FMCSA's test procedures except areas concerning the ELD Authentication Value, and the registration ID and ELD identifier that we can not acquire until we submit this form. | |
| Ez ELD | BB0101 | 215 or higher | EZFLT1 | Download | Download | Ez Fleet Telematics Inc. | +1-403-619-7760 | info@ezfleet.tech | http://ezfleet.tech | 31 SaddleCrest Way NE, Calgary, AB, T3J 5N4 | Local (USB, Bluetooth) , Telematic (Web Service, Email) | To submit the Output File to an authorized safety official, the driver selects the “Export ELD Data File” from the Logbook screen. The driver, then, will select one of the following methods: - FMCSA web service: This option securely communicates to FMCSA's end-point ad obtains submission ID. - ELD Email Interface: This option transfer an encrypted email to FMCSA email address | Low battery, network disconnection, low internal memory space, ECM data transfer failure, location sensor failure. In addition, the following malfunctions are detected (and appropriate records created) by the BB0101: - Power data diagnostic (diagnostic - 1) - Engine synchronization data diagnostic (diagnostic - 2) - Missing required data elements (diagnostic - 3) - Data transfer (diagnostic - 4) - Unidentified driving records data diagnostic (diagnostic - 5) - Other ELD diagnostics (diagnostic - 6 - Power compliance (malfunction - P) - Engine synchronization compliance (malfunction - E) - Timing compliance (malfunction - T) - Positioning compliance (malfunction - L) - Data recording compliance (malfunction - R) - Data transfer compliance (malfunction - S) - Other ELD malfunctions (malfunction - O) | The EZ ELD (BB0101) was tested on a diverse range of CMVs from different manufacturers and models as well drivers with different experience and backgrounds. Tests were also performed on different environments (indoor, outdoor, inside and outside CMVs). Procedures and areas of examinations were followed according to the “ELD Test Plan and Procedures” version 1.0 document released by FMCSA on April 25th 2016. The Requirement Traceability Matrix (RTM) was used and fully verified to ensure ELD compliance. Corrective actions and regression tests were made on all Failed test results. |
| Ez ELD Tracking Management System | EZELD4230 | 0.0.1 | EZTELD | Download | Download | EZ TRACK | 011526864887010 | contacto@eztrack.mx | http://www.eztrack.mx | 1101 Ollie Ave #3906, Calexico, CA , 92232 | Ez ELD Management System utilizes the Telematics option (Email and Web Services) as the method of electronically transferring the output file to the authorized safety official. In the Menu of the Ez ELD App enter on the DOT Section, a window will appear, to continue to see the records, tap of the INSPECT button then the interested log to open it. To share your records tap the DATA TRANSFER button and a window with 2 options appear to select the preferred: Email: which allows drivers to send ELD data in a multipart POST request containing a CSV file with the ELD data inside it. The file will be sent to the server, encrypted and then sent to the FMCSA enforcement personnel for decryption and verification. After the data transfer process is successful, will display a message that “Successfully Transferred”. Web Service: which allows drivers to send ELD data in a plain POST request that will in turn submit the data to the FMCSA web service, where it will be validated. After the data transfer process is successful, will display a message that “Successfully Transferred”. In both cases, If has an invalid information will display a dialog with the Data Transfer Error. | Power compliance malfunction: There has been a hardware issue or possible tampering with the unit that is installed in your vehicle. The recorded engine on and off events do not match between the mobile device and the vehicle unit. Possibly the CMV has been operated with the hardware unit unplugged. Engine synchronization compliance malfunction: The mobile device has lost connectivity to the vehicle unit for more than 30 minutes during a 24-hour period. During this time the data on engine power status, vehicle motion status, miles driven, and engine hours could no longer be accessed. Timing compliance malfunction: There was a discrepancy of more than 5 minutes, either between the mobile device's time and the hardware unit’s time, or, between the ECM’s time and the hardware unit’s time. Positioning compliance malfunction: The GPS connection has been lost and the mobile device has not been able to retrieve a valid location for more than 60 minutes within a 24-hour period. Check your GPS aerial. Data recording compliance malfunction: The mobile device is unable to properly record required data, because there is not enough storage space available on the device. The mobile device can no longer record new events and you might lose events that have not been uploaded yet. Data transfer compliance malfunction: The automatic data transfer check that is done once within each 24-hour period has failed more than 3 times. This means that you might have issues if you try to transfer your data. | The device was installed on a truck to obtain the values of the ECM as required by the new regulations stipulated by the FCMSA. After that, an access administrator was created to register the ELD profile and the application was installed on the driver's phone for testing | |
| EZ LYNK ELD Android | Auto Agent | 1.0 and above | EZLAND | Download | Download | EZ LYNK, SEZC | (877) 207-5530 | support@ezlynk.com | www.ezlynk.com | 125 Owen Roberts Drive, Georgetown, Grand Cayman Cayman Islands | Telematic (Web Service, Email) | EZ LYNK ELD supports telematics data transfer methods as defined in the Appendix to subpart B of part 395 (4.9.1 (b)(1)), title 49 of the Code of Federal Regulations. Data transfer steps: 1. Tap the navigation menu icon to access navigation menu and tap to select DOT Inspection. 2. Tap Send Logs button. 3. Select transfer method (web or email). 4. Enter routing code or comment provided by a safety officer. 5. Tap Send button. | All malfunction events, except for Data recording compliance malfunction, can only be cleared automatically and will be cleared once the corresponding problem is resolved. EZ LYNK ELD supported malfunctions: 1. Power compliance malfunction - More than 30 minutes of driving time lost in the last 24-hour period, cumulatively for all drivers, including the unidentified driver. 2. Engine synchronization compliance malfunction - While the CMV engine is on, the engine’s power status, vehicle’s motion status, miles driven value and engine hours value for the last 24-hour period (cumulatively for all drivers, including the unidentified driver) can’t be determined within 30 minutes or more. 3. Timing compliance malfunction - Absolute deviation from the Coordinated Universal Time (UTC) exceeds 10 minutes at any point in time. 4. Positioning compliance malfunction - The ELD determines a location at least every 5 miles while the vehicle is in motion. If the cumulative period when the ELD fails to acquire a valid position measurement within 5 miles of CMV’s movement exceeds 60 minutes for the last 24-hour period, then this event will be recorded. 5. Data record compliance malfunction - The ELD is unable to record logs or retrieve logs from the server due to insufficient memory or other technical problems of the mobile device. 6. Data transfer compliance malfunction - Once a Data transfer data diagnostic event occurs, the ELD will enter the unconfirmed data transfer mode and start checking data transfer compliance every 24 hours. If the problem doesn’t go away after three consecutive checks, then this event will be recorded. | EZ LYNK ELD was tested using FMCSA provided ELD Compliance Test Procedure outlined in "Electronic Logging Device (ELD) Test Plan and Procedures" to meet the functional requirements included in the technical specifications in the Appendix to subpart B of part 395, title 49 of the Code of Federal Regulations. |
| EZ LYNK ELD iOS | Auto Agent | 1.0 and above | EZLIOS | Download | Download | EZ LYNK, SEZC | (877) 207-5530 | support@ezlynk.com | www.ezlynk.com | 125 Owen Roberts Drive, Georgetown, Grand Cayman Cayman Islands | Telematic (Web Service, Email) | EZ LYNK ELD supports telematics data transfer methods as defined in the Appendix to subpart B of part 395 (4.9.1 (b)(1)), title 49 of the Code of Federal Regulations. Data transfer steps: 1. Tap the navigation menu icon to access navigation menu and tap to select DOT Inspection. 2. Tap Send Logs button. 3. Select transfer method (web or email). 4. Enter routing code or comment provided by the safety officer. 5. Tap Send button. | All malfunction events, except for Data recording compliance malfunction, can only be cleared automatically and will be cleared once the corresponding problem is resolved. EZ LYNK ELD supported malfunctions: 1. Power compliance malfunction - More than 30 minutes of driving time lost in the last 24-hour period, cumulatively for all drivers, including the unidentified driver. 2. Engine synchronization compliance malfunction - While the CMV engine is on, the engine’s power status, vehicle’s motion status, miles driven value and engine hours value for the last 24-hour period (cumulatively for all drivers, including the unidentified driver) can’t be determined within 30 minutes or more. 3. Timing compliance malfunction - Absolute deviation from the Coordinated Universal Time (UTC) exceeds 10 minutes at any point in time. 4. Positioning compliance malfunction - The ELD determines a location at least every 5 miles while the vehicle is in motion. If the cumulative period when the ELD fails to acquire a valid position measurement within 5 miles of CMV’s movement exceeds 60 minutes for the last 24-hour period, then this event will be recorded. 5. Data record compliance malfunction - The ELD is unable to record logs or retrieve logs from the server due to insufficient memory or other technical problems of the mobile device. 6. Data transfer compliance malfunction - Once a Data transfer data diagnostic event occurs, the ELD will enter the unconfirmed data transfer mode and start checking data transfer compliance every 24 hours. If the problem doesn’t go away after three consecutive checks, then this event will be recorded | EZ LYNK ELD was tested using FMCSA provided ELD Compliance Test Procedure outlined in "Electronic Logging Device (ELD) Test Plan and Procedures" to meet the functional requirements included in the technical specifications in the Appendix to subpart B of part 395, title 49 of the Code of Federal Regulations. |
| Ez-Hard-Wire ELD by Ezlogz | ST20 | 273 | EZSUN1 | Download | Download | Ezlogz Inc | (800)670-7807 | support@ezlogz.com | https://ezlogz.com | 201 NE Park Plaza dr, suite 148, Vancouver, WA 98684 | The Ezlogz Device uses email, officer inspection mode, Bluetooth, and web services (Output file). Description of the supported and certified data transfer mechanisms and step-by-step instructions for a driver to produce and transfer the ELD records to an authorized safety official Step 1.In main menu of the application choose "Inspection mode" Step 2. On right top corner of the screen press "share" button Step 3. In popup window select "Send output file", then out of two available, choose one option "Web service" or "Email" Step 4. After Inspector inputs comment, press button "Send" | On the Logbook screen of ELD driver always see's the eld icon, if any malfunction occurs - the driver will be notified with a popup describing information about the malfunction and recommendations on how a driver should try to resolve/fix it and eld icon will become red. Same time information about malfunction save into user history and will be displayed in inspection display/print data, eld data file. If any malfunctions are currently active - the eld icon will be red and clicking on it will show current malfunctions information. Also, each eld client will receive a printout, describing possible malfunctions, how to detect them and steps to resolve them. If need any additional information - please provide more specific question, as nowhere in eld mandate/ELD Test Plan and Procedures specified what exactly should be pointed in this field(explanation, examples) Currently implemented malfunctions: -Power data diagnostic events - if ELD is not powered and fully functional within one minute of the vehicle’s engine receiving power -Power compliance malfunctions - if ELD is not powered for an aggregated in-motion driving time of 30 minutes or more over a 24-hour period across all driver profiles -Engine synchronization data diagnostic events - if no data comes from vehicle ecu's within five seconds of the need -Engine synchronization compliance malfunctions - if no data comes from vehicle ecu's for more than 30 minutes during a 24-hour period aggregated across all driver profiles. -Timing compliance malfunction - if ELD can no longer meet the underlying compliance requirement to record Coordinated Universal Time (UTC) -Positioning compliance malfunction - if ELD fails to acquire a valid position measurement within 5 miles of the commercial motor vehicle moving and 60 minutes has passed(gps failure) -Data recording compliance malfunction - occurs when an ELD can no longer record or retain required events or retrieve recorded logs that are not kept remotely by the motor carrier(memory limit, save failure) -Missing required data elements data diagnostic event - if any required data field is missing at the time of its recording(validation failure) -Data transfer data diagnostic event - if when the operation of the data transfer mechanism(s) is not confirmed(file generation failure, transfer failure) -Data transfer compliance malfunction - if ELD stays in the unconfirmed data transfer mode following the next three consecutive monitoring checks(file generation failure, transfer failure) -Unidentified driving records data diagnostic event - If ELD record driving event with no driver logged in for more than 30 minutes of driving time for an unidentified driver is recorded within a 24-hour period | The Ezlogz techs fallowed all the FMCSA step by step procedures and came back with a positive (P) pass result and ELD device complies with FMCSA safety regulations (ELD Rule) Ezlogz Certifies that the ELD device complies with FMCSA safety regulations (ELD Rule) | |
| FACTOR ELD | FRS | 2.6.13 or higher | FRS278 | Download | Download | FACTOR ELD | +1 216 293 5050 | support247@factoreld.com | factoreld.com | 16192 Coastal Highway Lewes, Delaware 19958 USA, 16192 Coastal Highway Lewes, Delaware 19958 USA | Local (USB, Bluetooth) , Telematic (Web Service, Email) | FACTOR ELD is capable of producing and transferring the ELD records via telematics transfer methods: Wireless Web services and Email. In order to send the ELD records via Web services, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Web Service as the Data Transfer Type and press “SEND” button. In order to send the ELD records via Email, a driver must press “DOT Inspection” menu item, then press “Send Logs” button, select Email as the Data Transfer Type and press “SEND” button. | FACTOR ELD monitors its compliance with the technical requirements and detects malfunctions and data inconsistencies and keeps records of its malfunction and data diagnostic event detection. Following standard coding is implemented for required compliance malfunction and data diagnostic event detection: P - “Power compliance” malfunction, E - “Engine synchronization compliance” malfunction, T - “Timing compliance” malfunction, L - “Positioning compliance” malfunction, R - “Data recording compliance” malfunction, S - “Data transfer compliance” malfunction, O - “Other” ELD detected malfunction, 1 - “Power data diagnostic” event, 2 - “Engine synchronization data diagnostic” event, 3 - “Missing required data elements data diagnostic” event, 4 - “Data transfer data diagnostic” event, 5 - “Unidentified driving records data diagnostic” event, 6 - “Other” ELD identified diagnostic event. The FACTOR ELD Malfunction and Diagnostic Event Records list all ELD malfunctions that have occurred on FACTOR ELD during the time period for which this file is generated. Active malfunctions are indicated to all drivers who may use that ELD. | FACTOR ELD meets the technical specifications set forth in the Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations. FACTOR ELD was tested to comply with FMCSA regulations by completing steps and testing procedures described in the Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. |
| FACTOR Electronic Logging | ELDTrak | 8.0 | ELDv80 | Download | Download | Factor | 877-854-7888 | css@factor.com | http://factor.com | 3030 NW Expressway Suite 1500, Oklahoma City, OK 73112 | USB and Bluetooth To transfer the data to a USB 2.0 device: • From the Driver Logs tab, press the Generate Report button. • Click “Yes” to confirm you wish to generate a report. • Select the output type of the report (USB). o Insert a USB drive. o If the drive does not show in the drop down, click the refresh icon. o Select the drive letter for the USB drive. o Prompt the driver for the path to the authentication file on the safety official's USB drive • Enter comment if needed. • Click OK To transfer the data using Bluetooth: • From the Driver Logs tab, press the Generate Report button. • Click “Yes” to confirm you wish to generate a report | Summary of Malfunctions Power Compliance Engine Synchronization Timing Compliance Positioning Compliance Data Recording Monitor Unidentified Driver Data Transfer | The software was tested using the information provided in the Appendix to subpart B of part 395, title 49 of the code of Federal Regulations under the conditions in which the ELD would be used. The transfer files were tested using the FMCSA file validator. | |
| FALCON ELD | FTX ELD | 1.0.0 | FTX007 | Download | Download | Falcon Telematics LLC | 3026000128 | support@falconeld.com | https://falconeld.com | 1207 Delaware Ave #600, Wilmington, DE 19806 | Telematic (Web Service, Email) | Falcon ELD is capable of producing and transferring eRODS via telematics transfer methods (Webservices and Email). In order to send the eRODS a driver must navigate to the "Reports" tab in the app, choose the transfer method, fill out the inspection code field as instructed by the authorized official conducting the inspection, then press the "SEND" button. | Falcon ELD Is capable of monitoring its compliance and detect various malfunctions. When a malfunction is detected the user will be notified of this via a prompt. Falcon ELD is capable of detecting the following: Power Malfunctions, Engine Synchronization Malfunctions, Timing Malfunctions, Position Malfunctions, Data Recording Malfunctions, Data Transfer Malfunctions. | We hereby certify that we have executed FMCSA test plans and procedures and test procedure complies with the FMCSA regulation. |
| FC BigRoad ELD | DL-100 / DL-200 | 33.1 or higher | FCBR20 | Download | Download | BigRoad Inc | 1-888-305-8777 | support@bigroad.com | www.bigroad.com | 180 Columbia St. W., Waterloo, Ontario, N2L 3L3 | Telematic (Web Service, Email) | Data transfer is supported via telematics types, specifically web services and email. Step by step instructions: 1) Tap Inspect Logs 2) Select 7 days (US) 3) Tap Send to FMCSA 4) Select either "Via web services" or "Via email" 5) Tap Send 6) Fill in the provided output file comment 7) Tap Send | Supported Malfunctions include: Engine Synchronization Malfunction - indicated when the ELD is unable to sense required engine and vehicle information such as odometer, hours, VIN, road speed, engine on/off Timing Compliance Malfunction - indicated when the ELDs clock diverges by more than 10 minutes from the external, reliable source (GPS Time) Positioning Compliance Malfunction - indicated when the ELD is continually unable to determine an accurate location and >5 miles of driving have elapsed Data Recording Malfunction - indicated when the ELD is unable to store data Power Compliance Malfunction - indicated when the ELD is unable to power on within sufficient time Data Transfer Malfunction - indicated when the ELD has been unable to transfer required information to FMCSA servers for an extended period of time | The Fleet Complete ELD has been tested in accordance with BigRoad testing procedures to be compliant with FMSCA regulation 49 CFR part 395, subpart B, appendix A; describing the functional requirements for ELD solutions. |
| FC BigRoad ELD | MGS700 (GNX6) / MGS800 | 33.1 or higher | FCBR20 | Download | Download | BigRoad Inc | 1-888-305-8777 | support@bigroad.com | www.bigroad.com | 180 Columbia St. W., Waterloo, Ontario, N2L 3L3 | Telematic (Web Service, Email) | Data transfer is supported via telematics types, specifically web services and email. Step by step instructions: 1) Tap Inspect Logs 2) Select 7 days (US) 3) Tap Send to FMCSA 4) Select either "Via web services" or "Via email" 5) Tap Send 6) Fill in the provided output file comment 7) Tap Send | Supported Malfunctions include: Engine Synchronization Malfunction - indicated when the ELD is unable to sense required engine and vehicle information such as odometer, hours, VIN, road speed, engine on/off Timing Compliance Malfunction - indicated when the ELDs clock diverges by more than 10 minutes from the external, reliable source (GPS Time) Positioning Compliance Malfunction - indicated when the ELD is continually unable to determine an accurate location and >5 miles of driving have elapsed Data Recording Malfunction - indicated when the ELD is unable to store data Power Compliance Malfunction - indicated when the ELD is unable to power on with sufficient time during vehicle use Data Transfer Malfunction - indicated when the ELD has been unable to transfer required information to FMCSA servers for an extended period of time | The Fleet Complete ELD has been tested in accordance with BigRoad testing procedures to be compliant with FMSCA regulation 49 CFR part 395, subpart B, appendix A; describing the functional requirements for ELD solutions. |
| FC BigRoad ELD | FT1 / FT2 / FT3 | 33.1 or higher | FCBR20 | Download | Download | BigRoad Inc | 1-888-305-8777 | support@bigroad.com | www.bigroad.com | 180 Columbia St. W., Waterloo, Ontario, N2L 3L3 | Telematic (Web Service, Email) | Data transfer is supported via telematics types, specifically web services and email. Step by step instructions: 1) Tap Inspect Logs 2) Select 7 days (US) 3) Tap Send to FMCSA 4) Select either "Via web services" or "Via email" 5) Tap Send 6) Fill in the provided output file comment 7) Tap Send | Supported Malfunctions include: Engine Synchronization Malfunction - indicated when the ELD is unable to sense required engine and vehicle information such as odometer, hours, VIN, road speed, engine on/off Timing Compliance Malfunction - indicated when the ELDs clock diverges by more than 10 minutes from the external, reliable source (GPS Time) Positioning Compliance Malfunction - indicated when the ELD is continually unable to determine an accurate location and >5 miles of driving have elapsed Data Recording Malfunction - indicated when the ELD is unable to store data Power Compliance Malfunction - indicated when the ELD is unable to power on with sufficient time during vehicle use Data Transfer Malfunction - indicated when the ELD has been unable to transfer required information to FMCSA servers for an extended period of time | The Fleet Complete ELD has been tested in accordance with BigRoad testing procedures to be compliant with FMSCA regulation 49 CFR part 395, subpart B, appendix A; describing the functional requirements for ELD solutions. |
| FIRST ELD | FRST | 2.20.08 or higher. | FRS185 | Download | Download | FIRST ELD LLC | 7542313300 | info@firsteld.com | http://firsteld.com/ | 2821 NE 163rd St, North Miami Beach, FL 33160 | Telematic (Web Service, Email) | FIRST ELD, or Electronic Logging Device, is a tool that offers a comprehensive overview of a driver's records during a roadside inspection. Not only does it provide this information within the app, but it also facilitates the transfer of telematics data through email or web services. The DOT Inspection mode allows the driver to choose the method that works best for them. To transfer ELD records through Web services, the driver needs to access the "DOT Inspection" menu and select the "Send Logs" option. Then, they should choose Web Service as the Data Transfer Type and click the "SEND" button. Similarly, to transfer ELD records via Email, the driver should follow the same steps but select Email as the Data Transfer Type before clicking the "SEND" button. | The FIRST ELD system ensures compliance with technical requirements, identifies malfunctions and data inconsistencies, and maintains records of such occurrences. Compliance malfunctions and diagnostic events are classified with specific codes, including P for "Power compliance" malfunction, E for "Engine synchronization compliance" malfunction, T for "Timing compliance" malfunction, L for "Positioning compliance" malfunction, R for "Data recording compliance" malfunction, S for "Data transfer compliance" malfunction, O for "Other" ELD-detected malfunctions, 1 for "Power data diagnostic" event, 2 for "Engine synchronization data diagnostic" event, 3 for "Missing required data elements data diagnostic" event, 4 for "Data transfer data diagnostic" event, 5 for "Unidentified driving records data diagnostic" event, and 6 for "Other" ELD-identified diagnostic events. The FIRST ELD Malfunction and Diagnostic Event Records document all malfunctions that occurred during the relevant time period. Active malfunctions are communicated to all drivers who may use the ELD. | FIRST ELD has been thoroughly tested to ensure compliance with all the functional requirements outlined in Title 49, Part 395 of Section 4.9.1, Appendix A, Subpart B. FIRST ELD can confidently certify that our ELD product adheres to all the necessary ELD regulations. |
| Fleet Systems USA | FSPND670ELD | 2.11 | FSPND6 | Download | Download | Fleet Systems USA | (949) 423-6209 | rdemeritt@fleetsystemsusa.com | www.fleetsystemsusa.com | 1730 Pomona Ave Suite #4, Costa Mesa CA 92627 | Fleet Systems USA is utilizing transponders certified on Verizon data services network and transmits data in real time to cloud services provided to our customer base with secure access. Driver instructions to transfer information. Select via Bluetooth, thumb drive, or mini usb cable transfer. Identify the device being transferred to, select transfer. System will identify when required records have completed. | Version 2.11 is currently running on our productions servers with no malfunctions identified. | Units have been tested to meet all technical requirements internally with our sandbox and production servers as well as real time customer use. We have verified and ensured all technical specifications have been been fulfilled. | |
| FleetHunt ELD | Android & IOSIX | Version 1.2.2+ | FHELD4 | Download | Download | Fleethunt Technologies | 1-888-448-4868 | info@fleethunt.ca | www.fleethunt.ca | 625 Marion St, Winnipeg,MB.R2J0K3 | FLEETHUNT ELD uses an electronic data transfer method to deliver driver logs. The driver has an option to send the logs to FMCSA via email or web services from the application. Below are the step by step instructions: 1. Navigate to the Inspections Sections from the Navigation bar at bottom of the Fleethunt ELD Mobile application. Here driver has the option to print view and send logs to FMCSA. 2. To send to FMCSA, Click on "DOT Inspection". 3. A new screen appears and the driver is presented with 2 options: i. Email logs to FMCSA ii. Send via Webservice. The driver can add the routing code in the Comment field and hit the "SEND" button. | Fleethunt ELD Logbook checks for following malfunctions: 1. Power Compliance Malfunction – This is the responsibility of the Motor Carrier and Driver to ensure that the Tablet with the Logbook Application has sufficient power to be used. 2. Engine Synchronization Compliance Malfunction – The app periodically checks that it has connectivity to the vehicle ECM. If connectivity is lost for more than 30 minutes in a 24 hour period, malfunction is detected and appropriate event is recorded and presented to driver for correction. 3. Timing Compliance Malfunction – App checks the local time of device with Fleethunt server time and if there is a discrepancy of more than 5 minutes. 4. Positioning Compliance Malfunction – The GPS signal has been lost and the mobile device has not been able to retrieve a valid location for more than 60 minutes in a 24 hour period. 5. Data Recording Compliance Malfunction – The mobile device is unable to properly record the required data due to not enough storage space on the device. The mobile device can no longer record new events and events that have not been uploaded might be lost. 6. Data Transfer Compliance Malfunction – The automatic data transfer check (that is performed once every 24 hours) has failed. Malfunctions once detected are recorded and presented to driver for verification and driver has option to clear malfunctions. | After extensive testing of the FleetHunt ELD App and Device on vehicles of different make and models, we certify that the FleetHunt ELD functions as per FMCSA guidelines. Our ELD App runs on Android Phones and Tablets and has been tested extensively for compatibility across various models. The admin panel is available on our web application and can be accessed via a web browser. The FleetHunt ELD is tested against various test cases in real-time for accuracy and durability. | |
| FleetHunt ELD | Android & Xirgo 6300 Series | Version 2+ | FHELD1 | Download | Download | Fleethunt Technologies | 1-888-448-4868 | info@fleethunt.ca | www.fleethunt.ca | 625 Marion St, Winnipeg,MB.R2J0K3 | Telematic (Web Service, Email) | FLEETHUNT ELD uses an electronic data transfer method to deliver driver logs. The driver has an option to send the logs to FMCSA via email or web services from the application. Below are the step by step instructions: 1. Navigate to the Inspections Sections from the Navigation bar at bottom of the Fleethunt ELD Mobile application. Here driver has the option to print view and send logs to FMCSA. 2. To send to FMCSA, Click on "DOT Inspection". 3. A new screen appears and the driver is presented with 2 options: i. Email logs to FMCSA ii. Send via Webservice. The driver can add the routing code in the Comment field and hit the "SEND" button. | Fleethunt ELD Logbook checks for following malfunctions: 1. Power Compliance Malfunction – This is the responsibility of the Motor Carrier and Driver to ensure that the Tablet with the Logbook Application has sufficient power to be used. 2. Engine Synchronization Compliance Malfunction – The app periodically checks that it has connectivity to the vehicle ECM. If connectivity is lost for more than 30 minutes in a 24 hour period, malfunction is detected and appropriate event is recorded and presented to driver for correction. 3. Timing Compliance Malfunction – App checks the local time of device with Fleethunt server time and if there is a discrepancy of more than 5 minutes. 4. Positioning Compliance Malfunction – The GPS signal has been lost and the mobile device has not been able to retrieve a valid location for more than 60 minutes in a 24 hour period. 5. Data Recording Compliance Malfunction – The mobile device is unable to properly record the required data due to not enough storage space on the device. The mobile device can no longer record new events and events that have not been uploaded might be lost. 6. Data Transfer Compliance Malfunction – The automatic data transfer check (that is performed once every 24 hours) has failed. Malfunctions once detected are recorded and presented to driver for verification and driver has option to clear malfunctions. | After extensive testing of the FleetHunt ELD App and Device on vehicles of different make and models, we certify that the FleetHunt ELD functions as per FMCSA guidelines. Our ELD App runs on Android Phones and Tablets and has been tested extensively for compatibility across various models. The admin panel is available on our web application and can be accessed via a web browser. The FleetHunt ELD is tested against various test cases in real-time for accuracy and durability. |
| FleetHunt ELD | iOS & IOSIX | Version 1+ | FHELD5 | Download | Download | Fleethunt Technologies | 1-888-448-4868 | info@fleethunt.ca | www.fleethunt.ca | 625 Marion St, Winnipeg,MB.R2J0K3 | FLEETHUNT ELD uses an electronic data transfer method to deliver driver logs. The driver has an option to send the logs to FMCSA via email or web services from the application. Below are the step by step instructions: 1. Navigate to the Inspections Sections from the Navigation bar at bottom of the Fleethunt ELD Mobile application. Here driver has the option to print view and send logs to FMCSA. 2. To send to FMCSA, Click on "DOT Inspection". 3. A new screen appears and the driver is presented with 2 options: i. Email logs to FMCSA ii. Send via Webservice. The driver can add the routing code in the Comment field and hit the "SEND" button. | Fleethunt ELD Logbook checks for following malfunctions: 1. Power Compliance Malfunction – This is the responsibility of the Motor Carrier and Driver to ensure that the Tablet with the Logbook Application has sufficient power to be used. 2. Engine Synchronization Compliance Malfunction – The app periodically checks that it has connectivity to the vehicle ECM. If connectivity is lost for more than 30 minutes in a 24 hour period, malfunction is detected and appropriate event is recorded and presented to driver for correction. 3. Timing Compliance Malfunction – App checks the local time of device with Fleethunt server time and if there is a discrepancy of more than 5 minutes. 4. Positioning Compliance Malfunction – The GPS signal has been lost and the mobile device has not been able to retrieve a valid location for more than 60 minutes in a 24 hour period. 5. Data Recording Compliance Malfunction – The mobile device is unable to properly record the required data due to not enough storage space on the device. The mobile device can no longer record new events and events that have not been uploaded might be lost. 6. Data Transfer Compliance Malfunction – The automatic data transfer check (that is performed once every 24 hours) has failed. Malfunctions once detected are recorded and presented to driver for verification and driver has option to clear malfunctions. | After extensive testing of the FleetHunt ELD App and Device on vehicles of different make and models, we certify that the FleetHunt ELD functions as per FMCSA guidelines. Our ELD App runs on Android Phones and Tablets and has been tested extensively for compatibility across various models. The admin panel is available on our web application and can be accessed via a web browser. The FleetHunt ELD is tested against various test cases in real-time for accuracy and durability. | |
| FleetHunt ELD | Android & ATrack AK11 Series | Version 1.2.2+ | FHELD3 | Download | Download | Fleethunt Technologies | 1-888-448-4868 | info@fleethunt.ca | www.fleethunt.ca | 625 Marion St, Winnipeg,MB.R2J0K3 | FLEETHUNT ELD uses an electronic data transfer method to deliver driver logs. The driver has an option to send the logs to FMCSA via email or web services from the application. Below are the step by step instructions: 1. Navigate to the Inspections Sections from the Navigation bar at bottom of the Fleethunt ELD Mobile application. Here driver has the option to print view and send logs to FMCSA. 2. To send to FMCSA, Click on "DOT Inspection". 3. A new screen appears and the driver is presented with 2 options: i. Email logs to FMCSA ii. Send via Webservice. The driver can add the routing code in the Comment field and hit the "SEND" button. | Fleethunt ELD Logbook checks for following malfunctions: 1. Power Compliance Malfunction – This is the responsibility of the Motor Carrier and Driver to ensure that the Tablet with the Logbook Application has sufficient power to be used. 2. Engine Synchronization Compliance Malfunction – The app periodically checks that it has connectivity to the vehicle ECM. If connectivity is lost for more than 30 minutes in a 24 hour period, malfunction is detected and appropriate event is recorded and presented to driver for correction. 3. Timing Compliance Malfunction – App checks the local time of device with Fleethunt server time and if there is a discrepancy of more than 5 minutes. 4. Positioning Compliance Malfunction – The GPS signal has been lost and the mobile device has not been able to retrieve a valid location for more than 60 minutes in a 24 hour period. 5. Data Recording Compliance Malfunction – The mobile device is unable to properly record the required data due to not enough storage space on the device. The mobile device can no longer record new events and events that have not been uploaded might be lost. 6. Data Transfer Compliance Malfunction – The automatic data transfer check (that is performed once every 24 hours) has failed. Malfunctions once detected are recorded and presented to driver for verification and driver has option to clear malfunctions. | After extensive testing of the FleetHunt ELD App and Device on vehicles of different make and models, we certify that the FleetHunt ELD functions as per FMCSA guidelines. Our ELD App runs on Android Phones and Tablets and has been tested extensively for compatibility across various models. The admin panel is available on our web application and can be accessed via a web browser. The FleetHunt ELD is tested against various test cases in real-time for accuracy and durability. | |
| FleetHunt ELD | iOS & Xirgo 6300 Series | Version 1+ | FHELD6 | Download | Download | Fleethunt Technologies | 1-888-448-4868 | info@fleethunt.ca | www.fleethunt.ca | 625 Marion St, Winnipeg,MB.R2J0K3 | FLEETHUNT ELD uses an electronic data transfer method to deliver driver logs. The driver has an option to send the logs to FMCSA via email or web services from the application. Below are the step by step instructions: 1. Navigate to the Inspections Sections from the Navigation bar at bottom of the Fleethunt ELD Mobile application. Here driver has the option to print view and send logs to FMCSA. 2. To send to FMCSA, Click on "DOT Inspection". 3. A new screen appears and the driver is presented with 2 options: i. Email logs to FMCSA ii. Send via Webservice. The driver can add the routing code in the Comment field and hit the "SEND" button. | Fleethunt ELD Logbook checks for following malfunctions: 1. Power Compliance Malfunction – This is the responsibility of the Motor Carrier and Driver to ensure that the Tablet with the Logbook Application has sufficient power to be used. 2. Engine Synchronization Compliance Malfunction – The app periodically checks that it has connectivity to the vehicle ECM. If connectivity is lost for more than 30 minutes in a 24 hour period, malfunction is detected and appropriate event is recorded and presented to driver for correction. 3. Timing Compliance Malfunction – App checks the local time of device with Fleethunt server time and if there is a discrepancy of more than 5 minutes. 4. Positioning Compliance Malfunction – The GPS signal has been lost and the mobile device has not been able to retrieve a valid location for more than 60 minutes in a 24 hour period. 5. Data Recording Compliance Malfunction – The mobile device is unable to properly record the required data due to not enough storage space on the device. The mobile device can no longer record new events and events that have not been uploaded might be lost. 6. Data Transfer Compliance Malfunction – The automatic data transfer check (that is performed once every 24 hours) has failed. Malfunctions once detected are recorded and presented to driver for verification and driver has option to clear malfunctions. | After extensive testing of the FleetHunt ELD App and Device on vehicles of different make and models, we certify that the FleetHunt ELD functions as per FMCSA guidelines. Our ELD App runs on Android Phones and Tablets and has been tested extensively for compatibility across various models. The admin panel is available on our web application and can be accessed via a web browser. The FleetHunt ELD is tested against various test cases in real-time for accuracy and durability. | |
| Fleetilla ELD | FLELD1 Mod1 | 194 or higher | FLELD1 | Download | Download | Fleetilla, LLC | 734-995-5100 | Sales@fleetlla.com | http://fleetilla.com | 4220 Varsity Drive, Suite F, Ann Arbor, MI, 48108 | Local (USB, Bluetooth) , Telematic (Web Service, Email) | To submit the Output File to an authorized safety official, the driver selects the “Export ELD Data File” from the Logbook screen. The driver, then, will select one of the following methods: - Agent External Storage: The ELD will first verify the external storage device is compatible with FMCSA specifications by validating the contents of file "ELDUSBTX.TXT". After positive validation the ELD will save the data file on the FMCSA-provided external storage device. - Bluetooth Transfer: After selecting this option, the authorized safety official will pair and verify PIN with the driver. Once the Bluetooth devices are paired, the safety official’s technology equipment will transfer the output file to the FMCSA website using Web services. | Low battery, network disconnection, low internal memory space, ECM data transfer failure, location sensor failure. In addition the following malfunctions are detected (and appropriate records created) by the Fleetilla ELD: - Power data diagnostic (diagnostic - 1) - Engine synchronization data diagnostic (diagnostic - 2) - Missing required data elements (diagnostic - 3) - Data transfer (diagnostic - 4) - Unidentified driving records data diagnostic (diagnostic - 5) - Other ELD diagnostics (diagnostic - 6 - Power compliance (malfunction - P) - Engine synchronization compliance (malfunction - E) - Timing compliance (malfunction - T) - Positioning compliance (malfunction - L) - Data recording compliance (malfunction - R) - Data transfer compliance (malfunction - S) - Other ELD malfunctions (malfunction - O) | he Fleetilla ELD was tested on a diverse range of CMVs from different manufacturers and models as well drivers with different experience and backgrounds. Tests were also performed on different environments (indoor, outdoor, inside and outside CMVs). Procedures and areas of examinations were followed according to the “ELD Test Plan and Procedures” version 1.0 document released by FMCSA on April 25th 2016. The Requirement Traceability Matrix (RTM) was used and fully verified to ensure ELD compliance. Corrective actions and regression tests were made on all Failed test results. |
| FleetLink ELD | FleetLink-ELD-GMS | 1.0.1816 and up | FLELD1 | Download | Download | Fleetmind Solutions | 1-888-639-1666 | info@fleetmind.com | www.fleetmind.com | 1751 Richardson, Suite 7200, Montreal, Quebec, H3K 1G6 | The FleetLink ELD provides a standardized single-step compilation for the driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. This can be done by selecting the Roadside Inspection button from the main HOS dashboard and selecting the option for Data Transfer. A list of supported data transfer options is then displayed which include Bluetooth, Email, USB, and web service. A Select Vehicle option is also available for selecting a vehicle upon performing the data transfer, this option enables FleetLink ELD to produce a data file or a series of data files of ELD records for a subset of its vehicles used by the driver. • Transfer via Bluetooth - this option enables the user to transfer files through Bluetooth. The ELD prompts for an output file comment which the driver may enter (optional). After the input, if Bluetooth |