FMCSA - Federal Motor Carrier Safety Adminstration

Registered ELDs

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 Email Company Website Address Data Transfer Methods ELD Malfunctions Certifying Statement
Hours Of Service Android & Atlas 1.0.1801.11819 HOS001 Download Download VisTracks, Inc. 630-596-5420 info@vistracks.com http://www.vistracks.com/ 801 Warrenville Road, Lisle, IL 60565 The 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 the 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. The 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, 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 VisTracks Hours of Service (HOS) App was certified by the VisTracks testing team through successful execution and verification of the FMCSA ELD Test Procedures. The HOS App 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 Atlas engine connected device. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the VisTracks HOS web application (portal) that can be accessed through a web browser.
ELD Plug-In MW-ELD-J6D 3.30 and higher MW3914 Download Download Mobile Warrior LLC 888-474-9284 m.greear@mobilewarrior.com http://www.mobilewarrior.com/corporate/ 4009 Cardiel Road, Washougal, WA 98671 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.
InTouch ELD - iOS Pacific Track 1621.6202 or higher ITELD1 Download Download InTouch (800) 881-6343 eld@intouchgps.com http://www.InTouchGPS.com 439 S Florida Ave STE 100B, Lakeland, FL 33801 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 InTouch 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 InTouch 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 InTouch 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. InTouch ELD was tested in compliance with the Electronic Logging Device (ELD) Test Plan and Procedures
Red Dog Elog RD0001 1.0.1806 or higher RD0001 Download Download Red Dog Logistics 844.683.0077 rdsales@reddoglogistics.com http://www.reddoglogistics.com P.O. Box 649, Mansfield, PA 16933 Data Transfer The Red Dog Logistics 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 vehicleupon performing the data transfer, this option enables the Red Dog Logistics 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 Red Dog Logistics 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 Red Dog Logistics 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 Red Dog Logistics ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The Red Dog Logistics 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 Device Names 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 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 Connect uses a light built into the cradle dock. Flashing Red: Tablet not in dock (CabMate Connect 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 Connect 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 Connect 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.
Isotrak Mobile Compliance Pack G3000 1.0.1718-1719 IMCP01 Download Download Isotrak Inc. 855-806-0821 evi.stalcup@isotrak.com http://isotrak.com/ 3455 Peachtree Rd NE, suite 566, Atlanta, GA 30326 Data Transfer The Isotrak Mobile Compliance Pack 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 Isotrak Mobile Compliance Pack 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 Isotrak Mobile Compliance Pack 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 Isotrak Mobile Compliance Pack 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 Isotrak Mobile Compliance Pack ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The Isotrak Mobile Compliance Pack 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 and CalAmp LMU-4233 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.
HCSSELD GEO84A 1.0.1816.180904 GEO84A Download Download HCSS 7132704000 sales@hcss.com www.hcss.com 13151 W Airport Blvd, Sugar Land/Texas/77478 HCSS eLogs 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 HCSS eLogs 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 HCSS eLogs 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 HCSS eLogs 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 HCSS eLogs ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The HCSS eLogs 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.
" 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
AT&T Fleet Complete ELD MGS700 (GNX6) / MGS800 21.0 and higher FCBGRD Download Download BigRoad Inc 1-888-305-8777 support@bigroad.com www.bigroad.com 180 Columbia St. W., Waterloo, Ontario, N2L 3L3 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.
Skeiron ELD SKAR03 1.1 SKAR03 Download Download SKEIRON LOGISTICS SOFTWARE 8303098789 info@skeiron.pro http://www.skeiron.pro/ 108 Danielle Drive, DEL RIO, TEXAS, 78840 TELEMATICS (EMAIL AND WEBSITE): In order to share your current log with a safety official please use the ‘Audit’ option in the app. Introduce the proper email address and select ‘SEND’. This will automatically forward current BOL HOS status to the selected receiver. Up to 6 Month audits can be consulted and shared through email in the included Skeiron TMS© Driver’s dashboard menu(www.skeironeld.com) (1)ERROR POWER DATA DIAGNOSTICS EVENT (2)ERROR POWER COMPLIANCE MALFUNCTION (3)ERROR ENGINE SYNCHRONIZATION DATA DIAGNOSTICS EVENT (4)ERROR ENGINE SYNCHRONIZATION COMPLIANCE MALFUNCTION (5)ERROR TIMING COMPLIANCE MALFUNCTION (6)ERROR POSITIONING COMPLIANCE MALFUNCTION (7)ERROR DATA RECORDING COMPLIANCE MALFUNCTION (8)ERROR MISSING REQUIRED DATA ELEMENTS DATA DIAGNOSTIC EVENT (9)ERROR DATA TRANSFER DATA DIAGNOSTIC EVENTS (10)ERROR UNIDENTIFIED DRIVING RECORDS DATA DIAGNOSTIC EVENT Skeiron ELD certifies that all FMCSA regulations have been considered in the design and development of this device. Our ELD modeL complies with all Federal Regulations.
ELD Fleet Android & CalAmp Veosphere 1.0.1721.8683 ELDFLT Download Download GPS Trackit (866) 320-5810 FleetAdvisor@GPSTrackit.net https://gpstrackit.com/eld-fleet/ 27244 Vía Industria, Temecula, CA, 92590 Data Transfer Description – Android Registrations The ELD Fleet™ 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 ELD Fleet™ 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 ELD Fleet™ 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 ELD Fleet™ 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 ELD Fleet™ 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 Fleet™ 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 ELD Fleet™ ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The ELD Fleet™ 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 CalAmp Veosphere 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.
Samsara ELD VG 1.1.8+ SAMELD Download Download Samsara (415) 985-2400 eld@samsara.com https://www.samsara.com/eld 444 De Haro St, Suite 101, San Francisco CA 94107 Samsara's ELD solution supports Option 1 (Telematics Transfer methods) of 4.9.1 of Appendix A to Subpart B of 49 CFR 395. Using the Samsara 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. Samsara's 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. Samsara's ELD was tested according to the ELD Compliance Test Plan and Procedures provided by the FMCSA to ELD Manufacturers at https://www.fmcsa.dot.gov/hours-service/elds/eld-test-procedures. Samsara test personnel performed each required test according to the provided test steps in order to verify that the actual test outcome matched the expected test outcome as provided.
TrackM2M-VisTracks ELD-VTGM00-A 1.0.1801.11540 & up TM2M01 Download Download TrackM2M.com Inc. 416 259 9842 tim.demonte@trackm2m.com http://trackm2m.com 98 Lake Crescent, Toronto, Ontario M8V 1W1 TrackM2M-VisTracks Data Transfer TrackM2M-VisTracks 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 TrackM2M-VisTracks 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. TrackM2M-VisTracks Malfunctions TrackM2M-VisTracks 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 TrackM2M-VisTracks 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. TrackM2M-VisTracks Certifying Statement of FMCSA Regulation Testing The TrackM2M-VisTracks ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The TrackM2M-VisTracks ELD was installed on various types and sizes of Android and Apple phones and tablets. Testing was performed through the use of a J1939/J1708 simulator and actual vehicles while having been connected to the Geometris whereQube 84 Series 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.
Locus ELD ELD003 1.0.1801.11819+ ELD001 Download Download Locus GPS (888) 643-6862 info@locusgps.com www.locusgps.com 2920 Arabian PL, Marietta, GA 30062 The Locus 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 the Locus 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. The Locus 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 Locus 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 Locus ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The Locus 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 Pacific Track 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.
TSO INCABIN PLUS TSO100 2.0 or higher TSO100 Download Download TSO MOBILE by Tracking Solutions Corp 18774772922 sales@tsomobile.com https://www.incabinplus.com/ 7791 NW 46th st Suite 306, Miami,Florida 33166 Data Transfer According to 4.9. (b) from Appendix A of the ELD final rule, it indicates : (b) “When a driver uses the single-step driver interface, as described in section 4.3.2.4 of this appendix, to indicate that the ELD compile and transfer the driver’s ELD records to authorized safety officials, the ELD must transfer the generated ELD data output to the computing environment used by authorized safety officials via the standards referenced in this section. To meet roadside electronic data transfer requirements, an ELD must do at least one of the following: (1) Option 1—Telematics transfer methods. Transfer the electronic data using both: (i) Wireless Web services, and (ii) Email, or (2) Option 2—Local transfer methods. Transfer the electronic data using both: (i) USB2 (incorporated by reference, see § 395.38), and (ii) Bluetooth (incorporated by reference, see § 395.38).” Our ELD can transfer data via “ Local transfer methods” and can transfer the electronic data using both: • USB2- Our ELD allows the driver to download data from the ELD to the USB drive, and return it to the safety official. The safety official will then transfer data from the USB drive to a computer. • Bluetooth – Our ELD allows the safety official to activate Bluetooth or his/her computer and provide the driver a Bluetooth code to enter into the ELD. The driver will then transfer data from the ELD to the safety official’s computer. The ELD manual has instructions with details on how to transfer data. Summary of Malfunctions Our ELD is in compliance with the regulations for the malfunctions and diagnostic event requirements. The following malfunctions status will appear in the display: • Power compliance • Engine synchronization compliance • Timing compliance • Positioning compliance • Data recording compliance • Data transfer compliance These malfunctions will appear when the ELD detects any type of the malfunctions mentioned above. The following diagnostic events will appear in the display: • Power data diagnostic • Engine synchronization data diagnostic • Missing required data elements data diagnostic • Data transfer data diagnostic • Unidentified driving records data diagnostic The diagnostic events will also appear in the ELD records. Our ELD utilizes the Android operative system. Which was tested as it was on the Electronic Loggin Device (ELD) document. Test Plan and produce of DOTFMCSA 2 cycles of test where done following all the instructions of the document. Various resources were utulized : 1. Different android tablets and 2. Differrent CMV 3. Emulators etc. for the specific points that the ELD was needed to record the missing required data elements diagnostic events This was done : Our ELD does not allow to save spaces without information, it is needed that the driver inputs the information in order to be saved.
Hours Of Service iOS & Xirgo 1.0.1801.11819 HOS001 Download Download VisTracks, Inc. 630-596-5420 info@vistracks.com http://www.vistracks.com/ 801 Warrenville Road, Lisle, IL 60565 The 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 the 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. The 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, 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 VisTracks Hours of Service (HOS) App was certified by the VisTracks testing team through successful execution and verification of the FMCSA ELD Test Procedures. The HOS App 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 Xirgo engine connected device. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the VisTracks HOS web application (portal) that can be accessed through a web browser.
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 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.
Matrack ELD MA3000 4.0 and up LOG247 Download Download Matrack Inc 872-256-2669 support@matrackinc.com http://www.matrackinc.com 2410 Camino Ramon, Suite 267, San Ramon, California, 94583 Matrack ELD support data transfer using telematics(Web Service and Email) 1. Login into Matrack ELD app 2. Select DOT Inspection icon from the Home screen. 3. Select Data Transfer option in DOT Inspection screen. 4. Enter option text in the comments field that might be provided by authorized safely official during the roadside inspection. 5. Select transfer method - either Web service or Email. 6. If Email transfer method was selected then enter a return email address to receive the FMCSA confirmation. 7. Select send button to perform data transfer. Data transfer will send the ELD output file to FMCSA server that will be made available to authorized safely official. (by FMCSA server) Malfunction summary: 1. Matrack ELD app changes the screen banner from green to red for malfunction indication. It will include the malfunction code inside the bracket. The values of malfunction code contain values ‘P’, ‘E’, ‘T’, ‘L’, ‘R’, ‘S’, or ‘O’ as per FMCSA Table-4 of Appendix A Subpart B of Part 395. 2. Onboard device's blue LED will blink once every 3 seconds; if the blink interval is not 3 seconds, then the device is malfunctioning 3. Onboard device's green LED will blink when there is no CAN bus data detected, otherwise it will stay steady. Matrack ELD was developed according to FMCSA's ELD specification, tested using FMCSA test Plan and Procedures and results were recorded.
Omnitracs XRS ELD SYSTEM XRS Mobile & Relay 4.6 > XRSAN1 Download Download Omnitracs, LLC 1.800.348.7227 ELD@omnitracs.com http://WWW.OMNITRACS.com 717 N Hardwood, Suite 1300, Dallas, TX 75201 ERODS TRANSFER WEB SERVICES and EMAIL Instructions on Driver CARD in Manual also 1. From the HOS Log screen, select the 3-dot menu, located in the top-right corner of the screen. 2. Select ERODS File Transfer. The ERODS File Transfer screen appears. 3. Select a Transfer Method, either Web Services or Email. Enter Comment if requested, Select Send. 4. The message ERODS File is Being Processed by Omnitracs appears. If the transfer fails, the HOS Log screen display is considered a compliant secondary record. MALFUNCTIONS AND DIAGNOSTICS If you receive any of the following errors or malfunctions on your ELD you are required to keep paper logs until the malfunction has been corrected. • Power - An ELD must be powered and function within one minute of the vehicle’s engine receiving power and remain powered for as long as the vehicle’s engine stays powered. • Engine Synchronization - An ELD is required to establish a link to the engine ECM and monitor its connectivity to the engine ECM and its ability to retrieve the vehicle parameters. • Timing - The ELD must cross-check its compliance with the external UTC source and must record any timing compliance malfunction. • Positioning - An ELD must monitor the availability of position measurements meeting the listed accuracy requirements and track the distance and time from the last valid measured point. Data Recording - 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. • Data Transfer - An ELD must implement inservice monitoring functions to verify that the data transfer mechanism(s) are continuing to function properly. • Other - Any other ELD-detected malfunction such as Bluetooth, relay, etc. Omnitracs XRS (XRSAN1) FMCSA Certifying Statement on Product Testing for ELD Regulation Compliance Omnitracs has distributed and supported AOBRDs in the marketplace since 1989 and has developed testing processes that would assess all areas of the compliance requirements for 49CFR 395.8 and 49CFR 395.15. We have a quality assurance process that follows the creation of story cards for each section of the ELD Mandate specifications. This QA process has been standard operating procedure for Omnitracs and has increased with the ELD mandate requirements. We have used the ELD Testing document issued by FMCSA as a reference to ensure that our testing parallels or exceeds the requirements. Additionally, tests have been created that evaluate fringe cases that are not included in the FMCSA document. Omnitracs employs automated script testing processes for testing of individual elements to ensure consistent and repeatable testing as well the ability to add fringe case scenarios to ensure that in each section of the ELD Mandate, compliance is achieved. We have modified our product through variance changes in the vehicle ECM, changes by OEM and SAE standards, and maintained compliance to ensure that we are continually able to supply information from the ECM. This has ensured that we comply with all the data capture and motion detection requirements specified in the ELD Mandate for the engine ECM. Our testing process includes testing in actual CMV class 6- 8 vehicles as well as using vehicle ECM simulators in testing labs. We additionally use GPS simulators to validate recovery and diagnostics for various situations that can occur in vehicles or environments when GPS may be compromised. With this and other testing processes we are able to test each requirement for diagnostics and malfunctions as required by the ELD Mandate specifications. Additionally, we have provided to Volpe an eRODS test file requested by FMCSA and that file has been accepted. We understand that the actual eRODS transfer process has not been finalized and it will require additional testing and some modifications once all information is available from FMCSA. Omnitracs information security program is based on NIST 800-53 Revision 4. We have ensured that the specified additional security requirements referenced in the regulation for PKI, FIPS, and other NIST specifications have been achieved for compliance to support eRODS transfer.
TSO ELD TSO101 1621.6202 or higher TSO101 Download Download TSO MOBILE by Tracking Solutions Corp 18774772922 sales@tsomobile.com https://www.incabinplus.com/ 7791 NW 46th st Suite 306, Miami,Florida 33166 Data Transfer Description – Android Registrations The TSO 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 the TSO 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 Malfunctions The TSO 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 TSO 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 TSO ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The TSO ELD. Testing was performed through the use of a J1939 simulator and actual vehicles while having been connected to IOSiX 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.
Zonar Logs ANDROID ELD1.0 ZONAR1 Download Download Zonar 2068782459 info@zonarsystems.com http://zonarsystems.com/ 18200 Cascade Ave S, SEATTLE, WA 98188 Exporting Logs to Electronic File A driver may be asked to send an electronic output file of their logs to an officer at roadside or inspection point. Detail Instructions: 1. Driver can click on the left hand menu to open up Roadside view - A display view for the field officer. 2. This report can be exported to the FMCSA on demand. 3. Select the export button on the right hand corner of the Roadside View. 4. Select the export method - Email or web service. 5. Add annotation and click Export. The flat file will be sent. Malfunction and Diagnostics Diagnostic events are generated when information required to maintain compliance is inaccurate or missing. If the diagnostic event is not resolved within a specific time frame, it will result in a malfunction. If a Diagnostic event is generated, a warning is displayed: ELD Diagnostic Event - If the ELD continues to have diagnostic events, please talk with your dispatcher. If a malfunction occurs, a notification will be displayed to any driver logged in while the malfunction is active. If a driver experiences a malfunction proceed as follows: 1. Note the malfunction of the ELD and provide written notice of the malfunction to the motor carrier within 24 hours; 2. Reconstruct the record of duty status for the current 24-hour period and the previous seven consecutive days, and record the records of duty status on graph-grid paper logs that comply with § 395.8, unless the driver already possesses the records or the records are retrievable from the ELD; and 3. Continue to manually prepare a record of duty status in accordance with § 395.8 until the ELD is serviced and brought back into compliance (no longer in a malfunction state). Please refer to pages 28-30 on the user’s manual for additional details. Zonar’s Electronic Logging Solution is certified to be in compliance to the requirements of title 49 CFR 395 Electronic Logging Devices and Hours of Service Supporting Documents; Final Rule published by the United States Federal Motor Carrier Safety Administration (FMCSA) in effect at the time of its commercial release. Certification procedure follows the guidelines set forth by the Electronic Logging Device (ELD) Test Plan and Procedures published by the FMCSA.
REAL ELD WILIR01 ANDR1.0 WLRA01 Download Download Real ELD 708-983-7325 stan@real.us http://www.real.us 2100 W 21st St, Broadview/IL/60155 INSPECTION REAL ELD provides an easy way for a driver to produce and transfer the ELD records to an authorized safety official. TELEMATICS EMAIL: 1. Click “Send Logs” from “Inspection Module” screen. 2. Select the checkbox next to each log you want to email. 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. Click “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 REAL ELD App if you choose to provide the authorized safety official a copy. REAL ELD 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. 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. When notified by fleet manager, REAL 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). REAL ELD will monitor and report malfunction data according to 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 Electronic Logging Device (ELD) Test Plan and Procedures document, version 2.0 dated 10/17/2016 provided by FMCSA to conduct testing of REAL ELD. Upon completion of necessary tests outlined in the above-named document we certify that REAL 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.
Super ELD ELD 2.0 2.19.4 or higher 2Xy8aB Download Download Super Dispatch 816-974-7002 support@mysuperdispatch.com https://www.mysuperdispatch.com/ 905 McGee St #210, Kansas City, MO 64106, Kansas City/ MO/ 64106 The Super ELD supports telematics data transfer via Web Service and Email. To generate a report, and transfer it to an authorized safety official, the driver must: 1. Tap on the "Inspection" button at the top of Super Dispatch's Hours of Service section. This will bring you into Inspection Mode. 2. Once in Inspection Mode, select "Send via Web Service." 3. Type any comments you would like to associate with the inspection before it is sent. This is an output file comment. 4. Tap "OK" or "Send" after your comment to continue. 5. Or choose “Send via Email” and enter an output file comment. 6. Click “Send” and the report will be sent to the FMCSA email. List of supported malfunctions: 1. Power compliance 2. Engine synchronization compliance 3. Timing compliance 4. Positioning compliance 5. Data recording compliance 6. Data transfer compliance 7. Other Under penalties of perjury, I, Jahongir Rahmonov, hereby certify on behalf of Super Dispatch that ELD model ELD 2.0 and version 2.19.4 or 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, under the conditions in which the ELD would be used.
ArionT ELD AT5000 10.1 AR1ONT Download Download Arion Tech Inc. 18772104711 sales@ariontech.ca www.ariontech.ca 20-1200 Derry Road East, Mississauga ON L5T 0B3 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 decrypt 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 Malfunctions: 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 Orbit freight for over 1200 hours on 5 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.
CarrierWeb CarrierMate MDT5700 MDT5700 4.31.50 and above CW5700 Download Download CarrierWeb LLC 404-762-1995 info.us@carrierweb.com http://www.carrierweb.com 200 Technology Ct., Suite E, Smyrna, GA, 30082 The MDT 5700 implements the Telematics option for data transfer at roadside inspection. In addition, the unit provides for a backup method of displaying ELD data when onsite communications is not possible. There are two choices, display ‘on screen’ – used if device has been installed to allow for passing out of vehicle, or ‘print’ to utilize the optional printer when device is installed in a way that does not al low for passing outside the vehicle. Additionally, the MDT5700 allows for E-Log history to be emailed or faxed to an address provided by the inspector. Telematics option – FMCSA Secure Webservice and FMCSA Secure Email: 1. Press the green ‘ELD’ button on the main menu of the MDT. 2. Press the ‘ELD’ tab at the top of the screen. 3. Press the ‘Inspect’ button on lower left bottom of the screen. 4. Choose either the option ‘FMCSA Secure Webservice’ or ‘FMCSA secure email’ as directed by inspector. 5. Touch ‘Press Here’ on the screen and enter the output file comment information as instructed by inspector. 6. Press ‘Send’ at screen bottom. Back up methods – Display on screen or print 1. Press the green ‘ELD’ button on the main menu of the MDT. 2. Press the ‘ELD’ tab at the top of the screen. 3. Press the ‘Inspect’ button on lower left bottom of the screen. 4. If passing unit out of cab – choose ‘On Screen’ from the inspection options choice screen and hand the device to roadside official. 5. Roadside official reads instructions on device regarding navigating the screen to choose days/reports and chooses ‘Next’ and reviews data. 6. If using print option – driver chooses ‘Print’ from the inspection options choice screen and hands the printed output to the roadside official. Standard Email or Fax 1. Press the green ‘ELD’ button on the main menu of the MDT. 2. Press the ‘ELD’ tab at the top of the screen. 3. Press the ‘Inspect’ button on lower left bottom of the screen. 4. Press ‘Insecure Email’ or ‘Insecure Fax’ 5. Touch ‘Press Here’ and enter the email address or fax number provided by the roadside inspector. 6. Press ‘Send’ at bottom screen. MDT Malfunctions Power Malfunction, Reason: The events in a 24 hour period. MDT has detected that it has been driven for 30 minutes without creating driving records., Solution: Check the connection to the Canbus (ECU), and check that the MDT is always powered before driving. Contact your carrier and revert to paper logs. Engine Sync Malfunction, Reason: The MDT has detected that it has missed data from the ECU for at least 30 minutes over a 24 hour period., Solution: Check the connection to the Canbus (ECU), and check that the MDT is always powered before driving. Contact your carrier and revert to paper logs. Timing Sync Malfunction, Reason: The MDT has failed to sync the clock with either the server, or GPS for too long, and it is possible that the clock may not be correct., Solution: Check the connection to the internet and GPS antenna - the malfunction should clear once a valid Fix is obtained.  Contact your carrier and revert to paper logs. Position Sync Malfunction, Reason: The MDT has been driven for too long without a GPS Fix., Solution: Check the GPS antenna - the malfunction should clear once a valid Fix is obtained. Contact your carrier and revert to paper logs. Data Recording Malfunction, Reason: The MDT cannot record any more ELD Events., Solution: An internal fault has occurred in the MDT which will need to be serviced. Contact your carrier and revert to paper logs. Data Transfer Malfunction, Reason: The MDT has failed to contact the FMCSA too many times to test the remote roadside inspection connection., Solution: Check the connection to the internet. Contact your carrier and revert to paper logs. Data Diagnostic Malfunctions Power Event, Reason: The MDT has detected that it has been driven without creating events., Solution: Check the connection to the Canbus (ECU), and check that the MDT is always powered before driving. Engine Sync Event, Reason: The MDT has detected that it is not receiving the required data from the vehicle ECU., Solution: Check the connection to the Canbus (ECU), and check that the MDT is always powered before driving. Missing Data Event, Reason: The MDT is missing required data for one or more events., Solution: Check the connection to the GPS antenna, or edit the events and add the missing data. Data Transfer Event, Reason: The MDT has failed to contact the FMCSA to test the remote roadside inspection connection., Solution: Check the connection to the internet. Unidentified Driving Event, Reason: The MDT has recorded driving when no driver was logged in., Solution: Always login before driving. You should also assuming the unidentified driving time if you are responsible for it when prompted after login. The ELD has been tested to confirm that the device meets the ELD requirements under the conditions in which the ELD will be used.
ELD Plug-In MW-ELD-J9D 3.30 and higher MW3792 Download Download Mobile Warrior LLC 888-474-9284 m.greear@mobilewarrior.com http://www.mobilewarrior.com/corporate/ 4009 Cardiel Road, Washougal, WA 98671 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.
LB Tech HOS (Android ELM327) LBT26009 1.0.1719.8478 ELDLB1 Download Download LB Technology Inc. 901-480-8834 woxley@lbtelematics.com www.lbtelematics.com 5100 Poplar Ave Suite 2104, Memphis TN 38137 The LB Technology 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 LB Technology 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 LB Technology's 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 LB Technology 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. The LB Technology ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The LB Technology 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 a ELM327 engine connected 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.
ELD Fleet Android & Geometris 1621.6202 or higher ELDFLT Download Download GPS Trackit (866) 320-5810 FleetAdvisor@GPSTrackit.net https://gpstrackit.com/eld-fleet/ 27244 Vía Industria, Temecula, CA, 92590 Data Transfer Description – Android Registrations The ELD Fleet™ 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 ELD Fleet™ 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 ELD Fleet™ 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 ELD Fleet™ 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 ELD Fleet™ 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 Fleet™ 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 ELD Fleet™ ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The ELD Fleet™ 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.
DT4000 REV 6 6.01.04 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 valid email address, 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.
Coretex DRIVE ELD01 1.6.x or higher TMUDRI Download Download Coretex 888-887-0935 sales@coretex.com www.coretex.com One Bridge Plaza, Suite 100, Fort Lee, NJ 07024 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
GFI eLogs iOS Calamp 4230 and 3030 1.0.1805.14019 GFI001 Download Download GFI Systems Inc. 1-855-434-4477 eld@gfisystems.ca http://www.gfisystems.ca 500 10709 Jasper Ave., Edmonton, Alberta The GFI eLogs 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 GFI eLogs 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 GFI eLogs 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 GFI eLogs 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 GFI eLogs ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The GFI eLogs 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 CalAmp 4230 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.
HCSSELDIOS GEO84A 1816.181017 GEO84A Download Download HCSS 7132704000 sales@hcss.com www.hcss.com 13151 W Airport Blvd, Sugar Land/Texas/77478 HCSS eLogs 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 HCSS eLogs 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 HCSS eLogs 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 HCSS eLogs 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 HCSS eLogs ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The HCSS eLogs 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.
KTELD Pro GNX-6 1.10 kteldp Download Download 10207110 CANADA INC. 647-906-8225 support@kteldpro.com https://www.kteldpro.com/ 188 Wilkinson Road, unit 2&3, Toronto We at KTELD Pro Support two type of data transfer mechanism. 1)Wireless Web services 2)Email Wireless Web services : 1)KTELD Pro convert ELD files into an XML using FMCSA provided files. 2)KTELD Pro Generate XML files to the driver for Last 7 days+ current day. 3)KTELD Pro supports upload the data(XML file) into the FMCSA. Wireless data transfer through E-Mail : We KTELD Pro give an Instruction for a driver to produce and transfer the ELD records: KTELD Pro provides to create CSV File FMCSA: 1. KTELD Pro 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. KTELD Pro 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. KTELD Pro 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 is any issues while connect 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 is any issues from latitude, longitude co-ordinates, we have recorded event log with positioning compliance malfunction. Data recording compliance malfunction If there is any issues while getting vehicle data's like(VIN number,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's 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.
Geowiz ELD IO100 v 2.0 and higher FF44EE Download Download GeoSpace Labs 877.4.GEOWIZ david@geowiz.biz https://www.geospacelabs.com 4460 Florida National Driv,, Lakeland, FL 33813 Geowiz 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. Enter the email address of the authorized safety official and tap the send button. 4. NOTE: Driver may check the 'copy me on this email' option to also receive a copy of the log transfer 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. 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 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.
CyntrX ELD Pro Pacific Track and Android 1.0.1805.14019 & up FlexCX Download Download CyntrX 9203380479 compliance@cyntrx.com http://www.cyntrx.com 1302 South Broadway, De Pere, WI, 54115 Data Transfer The CyntrX ELD Pro 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 CyntrX ELD Pro 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 CyntrX ELD Pro 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 CyntrX ELD Pro 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 CyntrX ELD Pro ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The CyntrX ELD ProELD 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 Pacific Track 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.
TrackOn ELD Powered by Gorilla Safety TrackOn HOS ELD 1.0 and above TO0001 Download Download Gorilla Fleet Safety, LLC 844-636-1360 info@gorillasafety.com http://www.gorillasafety.com 22327 Gosling Rd, Spring, TX 77379 Web Services and Email is used to transfer the data. 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.
Hours Of Service iOS & Astus 1.0.1805.180723 HOS001 Download Download VisTracks, Inc. 630-596-5420 info@vistracks.com http://www.vistracks.com/ 801 Warrenville Road, Lisle, IL 60565 The Hours of Service 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 the Hours of Service 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. The 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, 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 VisTracks Hours of Service (HOS) App was certified by the VisTracks testing team through successful execution and verification of the FMCSA ELD Test Procedures. The HOS App 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 engine connected device. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the VisTracks HOS web application (portal) that can be accessed through a web browser.
OBDTrac OBDTrac 6.0 and up MA3000 Download Download Matrack Inc 872-256-2669 support@matrackinc.com http://www.matrackinc.com 2410 Camino Ramon, Suite 267, San Ramon, California, 94583 Matrack ELD support data transfer using telematics(Web Service and Email) 1. Login into Matrack ELD app 2. Select DOT Inspection icon from the Home screen. 3. Select Data Transfer option in DOT Inspection screen. 4. Enter option text in the comments field that might be provided by authorized safely official during the roadside inspection. 5. Select transfer method - either Web service or Email. 6. If Email transfer method was selected then enter a return email address to receive the FMCSA confirmation. 7. Select send button to perform data transfer. Data transfer will send the ELD output file to FMCSA server that will be made available to authorized safely official. (by FMCSA server) 1. Matrack ELD app changes the screen banner from green to red for malfunction indication. It will include the malfunction code inside the bracket. The values of malfunction code contain values ‘P’, ‘E’, ‘T’, ‘L’, ‘R’, ‘S’, or ‘O’ as per FMCSA Table-4 of Appendix A Subpart B of Part 395. 2. Onboard device's blue LED will blink once every 3 seconds; if the blink interval is not 3 seconds, then the device is malfunctioning 3. Onboard device's green LED will blink when there is no CAN bus data detected, otherwise it will stay steady. We certify that our model MA3000, used in conjunction with an Android/iPhone Matrack ELD 6.0 or above App, conforms to the ELD specifications.We are fully tested to the best of our knowledge and the results of our testing were recorded.
My20 MY20ELD02 18.10.1.1 or higher KNXL02 Download Download Konexial, Inc. 865-888-6920 contact@konexial.com https://konexial.com 127 Dillon Ct, Johnson City, TN 37615 My20 will support web services and/or secure email to FMCSA when these services are released to ELD manufacturers. My20 also supports the display and/or print as the backup mechanism for inspection. 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 My20 monitors connection of the hardware recorder to the ECM, and connection of the hardware to the ELD software. In addition, as required by 4.6.1 of the ELD Rule, My20 monitors for the conditions listed in Table 4. Malfunction/Diagnostic Codes: P-"Power compliance" malfunciton; 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 Any detected malfunctions are prominently displayed to the user in the My20 Log screen. My20 has been extensively tested in accordance with the ELD Test Plan & Procedures Version 2.0 as published by FMCSA on 10.17.2016 using software simulators and live Class 8 vehicles.
HawkEye ELD BT3647 V2.0.0 BT3647 Download Download Hawk Eye Log Global Technology Ltd 855.588.4295 info@hawkeyelogs.com www.hawkeyelogs.com 311-3381 Cambie St, Vancouver, BC. V5Z 4R3 Hawkeye ELD supports both telematics and local transfer methods. Hawkeye ELD provides standardized single-step driver interface for compilation of driver’s ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection. When the vehicle is stopped, Hawkeye ELD displays 'transfer' icon on the touch-screen display, by which the driver can start single-step data transfer. The driver can select the transfer method by simply touching the transfer method icon, local (Bluetooth or USB) or telematic (Email or web service). Hawkeye ELD inputs the data transfer request from the driver, requires driver's confirmation, presents and requests selection of the supported data transfer options by the ELD, and prompts for entry of the output file comment. Upon confirmation, it generates the compliant output file and perform the data transfer. Hawkeye ELD supports monitoring and reporting following malfunctions: 1) Power Compliance Malfunction. Hawkeye ELD keeps monitoring data it receives from the engine ECM and data record history to identify instances when it may not have complied with the power requirements, in which case, it will 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. And it will set a power compliance malfunction if the power data diagnostics event 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. 2) Engine Synchronization Compliance Malfunction. Hawkeye ELD keeps monitoring the data it receives from the engine ECM and data record history to identify instances and duration's of its non-compliance with the ELD engine synchronization requirement in the spec. It will record an engine- synchronization data diagnostics event when it no longer can acquire updated values for the ELD parameters required for records within 5 seconds of the need. It will 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, including the unidentified driver profile. 3) Timing Compliance Malfunction. Hawkeye ELD periodically cross-checks its RTC clock with respect to an accurate external UTC source and will record a timing compliance malfunction when it can no longer meet the underlying compliance requirement. 4) Positioning Compliance Malfunction. Hakweye ELD continually monitors the availability of valid position measurements meeting the listed accuracy requirements in the spec and tracks the distance and elapsed time from the last valid measurement point. It 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, it will set and record a positioning compliance malfunction. 5) Data Recording Compliance Malfunction. Hawkeye ELD keeps monitoring its storage capacity and integrity and will 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. Hawkeye ELD keep monitoring 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 elements data diagnostics event for the driver if any required field is missing at the time of recording. 6) Data Transfer Compliance Malfunction. If the monitoring mechanism fails to confirm proper in-service operation of the data transfer mechanism(s), Hawkeye ELD will record a data transfer data diagnostic event and enter an unconfirmed data transfer mode. Once recording data transfer data diagnostic event, Hawkeye ELD will 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, it will detect a data transfer compliance malfunction. Hawkeye undergoes thorough functional and system test to ensure compliance of FMSCA regulation, covering following requirements: 1. ELD User Accounts Test (Account Types, Account Creation, Account Security, Account Management, Non-Authenticated Operation) 2. ELD-OBD Vehicle Interface Test 3. ELD Inputs Test 3.1 ELD-OBD Inputs Test (Engine Power Status, Vehicle Motion Status, Vehicle Miles, Engine Hours, CMV Position, CMV VIN 3.2 Driver’s Manual Entries (Driver’s Entry of Required Event Data Fields, Driver’s Status Inputs, Driver’s Indication of Duty Status, Driver’s Indication of Situations Impacting Driving Time Recording, Driver’s Certification of Records, Driver’s Data Transfer Initiation Input, Driver’s Entry of an Output File Comment, Driver’s Annotation of Records, Driver’s Entry of Location Information, Driver’s Record Entry/Edit) 3.3 Motor Carrier’s Manual Entries (ELD Configuration, Configuration of Available Categories Impacting Driving Time Recording Configuration of Using ELDs Motor Carrier’s Post-Review Electronic Edit Request) 4. ELD Processing and Calculations 4.1 Automatic Setting of Duty Status (Automatic Setting of Duty Status to Driving, Automatic Setting of Duty Status to On-Duty Not Driving, Other Automatic Duty-Status Setting Actions Prohibited) 4.2 Geo-Location Conversions 4.3 Date and Time Conversions 4.4 Setting of Event Parameters in Records, Edits, and Entries Event Sequence Identifier (ID) number, Event Record Status, Event Record Origin, Event Type Setting Records Automatically Logged by ELD, Driver Edits, Driver Entries ,Driver’s Assumption of Unidentified Driver Logs, Motor Carrier Edit Suggestions, Driver’s Actions Over Motor Carrier Edit Suggestions 4.5. Data Integrity Check Functions Event Data Check Event Checksum Calculation Event Data Check Calculation Line Data Check Line Checksum Calculation. Line Data Check Calculation Line Data Check Value Inclusion in Output File File Data Check File Checksum Calculation File Data Check Value Calculation File Data Check Value Inclusion in Output File. 5 ELD Recording Events and Data to Record Event: Change in Driver’s Duty Status Event: Intermediate Logs Event: Change in Driver’s Indication of Allowed Conditions that Impact Time Recording Event: Driver’s Certification of Own Records Event: Driver’s Login/Logout Activity Event: CMV’s Engine Power Up and Shut Down Activity Event: ELD Malfunction and Data Diagnostics Occurrence 6 ELD’s Self-Monitoring of Required Functions 6.1 Compliance Self-Monitoring Malfunctions and Data Diagnostic Events Power Compliance Monitoring Engine Synchronization Compliance Monitoring Timing Compliance Monitoring Positioning Compliance Monitoring Data Recording Compliance Monitoring Monitoring Records Logged under the Unidentified Driver Profile Data Transfer Compliance Monitoring Other Technology-Specific Operational Health Monitoring 6.2 ELD Malfunction Status Indicator Visual Malfunction Indicator ELD Data Diagnostic Status Indicator Visual Data Diagnostics Indicator 7 Special Purpose ELD Functions Driver’s ELD Volume Control Driver’s Access to Own ELD Records Privacy Preserving Provision for Use During Personal Uses of a CMV 8. ELD Outputs Information To Be Shown on the Printout and Display at Roadside ELD Data File ELD Output File Standard Header Segment User List CMV List ELD Event List for Driver’s Record of Duty Status Event Annotations, Comments, and Driver’s Location Description ELD Event List for Driver’s Certification of Own Records Malfunction and Diagnostic Event Records ELD Login/Logout Report CMV’s Engine Power-Up and Shut Down Activity ELD Event Log List for the Unidentified Driver Profile File Data Check Value ELD Output File Name Standard 9. Data Transfer Capability Requirements Data Transfer During Roadside Safety Inspections Motor Carrier Data Reporting 10. Communications Standards for the Transmittal of Data Files from ELDs 10.1. Data Transfer Mechanisms (Wireless Data Transfer via Web Services, Wireless Data Transfer Through E-Mail) 10.2. Motor Carrier Data Transmission
DT4000 REV 7 6.01.04 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 valid email address, 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.
TM-ELD TM-200 2.2.50 TM0002 Download Download TFM GROUP INC. 833-214-7670 sales@tmeld.us http://www.tmeld.us 714 ENTERPRISE DR, OAK BROOK/ILLINOIS/60523 TM-ELD provides an easy way for authorized officers to inspect driver’s logs. After logging in to TM-ELD following the steps described in TM-ELD User Manual, a driver must tap on DOT Inspection Mode in the bottom of the main screen. TM-ELD supports three different ways to provide driver’s logs to DOT inspector: 1. Direct inspection • In order to let an authorized officer inspect a driver’s logs directly from mobile device, a driver has to tap Begin button. • Driver’s logs will appear on the screen in the standard daily log format. Driver needs to hand the authorized officer his/her mobile device. • An authorized officer can use the arrows to navigate days. • Driver must tap on the back arrow to exit DOT Inspection Mode. 2. E-mail driver’s logs • In this case driver needs to tap on Send logs button. • On the screen opened driver chooses Via E-mail and tap on Send button. • Before sending, driver can also add a comment. • Driver must tap on the back arrow to exit DOT Inspection Mode. 3. Send driver’s logs via Webservice • In this case driver needs to tap on Send logs button. • On the screen opened driver chooses Via Webservice and tap on Send button. • Before sending, driver can also add a comment. • Driver must tap on the back arrow to exit DOT Inspection Mode. P Power compliance malfunction E Engine syncronization compliance malfunction T Timing compliance malfunction L Positioning compliance malfunction R Data record compliance malfunction S Data transfer compliance malfunction O Other ELD detected malfunction 1 Power data diagnostic error 2 Engine syncronization data diagnostic error 3 Missing required data elements data diagnostic error 4 Data transfer data diagnostic error 5 Unidentified driving records data diagnostic error 6 Other ELD identified diagnostic error ELD malfunctions and data diagnostic events (§ 395.34) (a) Recordkeeping during ELD malfunctions. In case of an ELD malfunction, a driver must do the following: - Note the malfunction of the ELD and provide written notice of the malfunction to the motor carrier within 24 hours; - Reconstruct the record of duty status for the current 24-hour period and the previous 7 consecutive days, and record the records of duty status on graph-grid paper logs that comply with § 395.8, unless the driver already possesses the records or the records are retrievable from the ELD; and - Continue to manually prepare a record of duty status in accordance with § 395.8 until the ELD is serviced and brought back into compliance with this subpart. (b) Inspections during malfunctions. When a driver is inspected for hours of service compliance during an ELD malfunction, the driver must provide the authorized safety official the driver's records of duty status manually kept as specified under paragraphs (a)(2) and (3) of this section. (c) Driver requirements during ELD data diagnostic events. If an ELD indicates that there is a data inconsistency that generates a data diagnostic event, the driver must follow the motor carrier's and ELD provider's recommendations in resolving the data inconsistency. (d) Motor carrier requirements: - Provide drivers with an instruction sheet describing the various ELD malfunction events and recordkeeping procedures (§395.22) - Provide drivers with a supply of 8 days’ worth of blank paper driver records (§395.22) - Repair, replace, or service (395.34) TM-ELD Model TM-200 and version 2.2.50. 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. Certification procedure follows the guidelines set forth by the Electronic Logging Device (ELD) test Plan and Procedures published by the United States Federal Motor Carrier Safety Administration (FMCSA).
LiveViewGPS Hours Of Service ELD-OBD-LE 1.0.1723 or Higher LVEND1 Download Download LiveViewGPS 661-294-6805 info@liveviewgps.com https://www.liveviewgps.com 29021 Ave Sherman STE 103, Valencia, CA 91355 The LIVEVIEWGPS HOURS OF SERVCE 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 LIVEVIEWGPS HOURS OF SERVICE 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 LIVEVIEWGPS HOURS OF SERVICE 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 LIVEVIEWGPS HOURS OF SERVICE 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 LIVEVIEWGPS HOURS OF SERVICE ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The LIVEVIEWGPS HOURS OF SERVICE 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 ELD-OBD-LE 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.
liveDispatch LDNX7 2.00 mJs552 Download Download Compatible Technology Systems, Inc. 888-287-9779 info@ctswest.com http://ctswest.com 14737 Catalina Street, San Leandro, CA 94577 1. Choose Inspection Mode: inspector can see the header, time-line graph and event list. 2. If the officer request to transfer data, the driver click on Transfer Data button. 3. The application will pop up the Input form for the officer enter the comment (optional) 4. Driver can choose: Transfer by Web Service, or Email, or Cancel 5. The progress bar will be shown to indicate data is transfering 6. Show status when done 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 We have tested and met for all required functions and procedures according to all ELD rules and regulations in compliance of FMCSA.
Trimble Duo - eDriver Logs ELD Trimble Duo .23XXX or higher DUO001 Download Download PeopleNet 888-346-3486 info@peoplenetonline.com www.peoplenetonline.com 4400 Baker Road, Minnetonka, MN 55343 Wireless Web services and Email 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”. To transmit an ELD Data File for the current 24-hour period and the previous 7 consecutive days to the FMCSA, tap the Data File Transfer button. Tap to select either Web Service or Email, enter a comment, and tap Done to complete the request and send the file. To allow the eRODS system to transmit the file directly to you, the inspecting officer, enter only your code (such as “US1234” or “IA12345”) in the comments field. Do not include the word “code” or any other text. 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 eDriver Logs ELD application has stopped working or is not responding as expected PeopleNet 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 01/24/2019 that DUO001 and complies with all Federal Motor Carrier Safety Administration (FMCSA) specifications as found in 49 CFR Part 395 for Electronic Logging Devices, Subpart B.
TrackOn Lite ELD TOLWL01 TOLA1.0 TWLA01 Download Download TrackOn LLC. 888-512-2198 info@trackonfleet.com http://www.trackonfleet.com P.O. Box 731, Orland Park, IL 60462, 6825 Hobson Valley Drive, Woodridge,IL 60517 *There is a section in uploaded manual that describes and showcases data transfer mechanism with colors and visual cues. INSPECTION TrackOn Lite provides an easy way for a driver to produce and transfer the ELD records to an authorized safety official. TO PRODUCE LOGS ON THE SCREEN: 1. Tap on the Menu icon on the top left. 2. Select Inspection Module from the Menu. 3. To let an authorized safety official inspect your logs directly from your device, tap Begin Inspection. 4. Give the authorized safety official your mobile device. 5. Tap the Back arrow on the top left to exit Inspection Module. TO EMAIL OR FAX LOGS TO THE AUTHORIZED SAFETY OFFICIAL: 1. Tap Send Logs from Inspection Module screen. 2. Tap the checkbox next to each log you want to send. 3. Choose the transfer method by clicking on Email or Fax tab. 4. Enter the email address or fax number of the authorized safety official. 5. Tap Send to email 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 GPSTab ELD Edition App if you choose to provide the authorized safety official with hard copy. TrackOn Lite 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 through output file is available for TrackOn Lite ELD users. *There is a section in uploaded manual that describes and showcases Malfunctions with colors and visual cues. How does the driver know if TrackOn Lite is malfunctioning? The TrackOn Lite 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 TrackOn Lite support immediately after discovering a malfunction at 888-512-2198 or support@trackonfleet.com 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, TrackOn Lite 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). TrackOn Lite 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 TrackOn Lite ELD. Upon completion of necessary tests outlined in the above named document we certify that TrackOn Lite 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
GPSTab ELD Edition GELD01 GELDA1.0 GBFA01 Download Download Utech Inc. 888-228-4460 sales@utechcorp.com www.utechcorp.com 2100 W. 21st Street, Broadview, IL 60155 *There is a section in uploaded manual that describes and showcases data transfer mechanism with colors and visual cues. INSPECTION GPSTab ELD Edition provides an easy way for a driver to produce and transfer the ELD records to an authorized safety official. TO PRODUCE LOGS ON THE SCREEN: 1. Tap on the Menu icon on the top left. 2. Select Inspection Module from the Menu. 3. To let an authorized safety official inspect your logs directly from your device, tap Begin Inspection. 4. Give the authorized safety official your mobile device. 5. Tap the Back arrow on the top left to exit Inspection Module. TO EMAIL OR FAX LOGS TO THE AUTHORIZED SAFETY OFFICIAL: 1. Tap Send Logs from Inspection Module screen. 2. Tap the checkbox next to each log you want to send. 3. Choose the transfer method by clicking on Email or Fax tab. 4. Enter the email address or fax number of the authorized safety official. 5. Tap Send to email 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 GPSTab ELD Edition App if you choose to provide the authorized safety official with hard copy. GPSTab – ELD Edition 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. *There is a section in uploaded manual that describes and showcases Malfunctions with colors and visual cues. How does the driver know if GPSTab ELD is malfunctioning? The GPSTab 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 UTECH support immediately after discovering a malfunction at 888-228-4460 or support@utechcorp.com 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, UTECH 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). GPSTab ELD Edition 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 GPSTab ELD Edition. Upon completion of necessary tests outlined in the above named document we certify that GPSTab ELD Edition 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
Petro ELD SAMTAB 1.6.74.1A or greater PELD01 Download Download SkyBitz 888-760-4477 eld@skybitz.com http://www.skybitz.com 2300 Dulles Station Blvd, suite 600, Herndon/VA/20171 Petro ELD uses Wireless Web Services and email for our method of data transfer. The driver will use the Options feature in our application, tap on a button to send logs to enforcement that will initiate the procedure. 1 - Power Data Diagnostic - The engine was running for at least a minute before the device was connected/powered on Or The vehicle was driven without the device connected/powered on 2 - Engine Synchronization Data Diagnostic - The device hasn’t received required engine data within the required time (see Appendix A – Data Requirements) 3 - Missing Required Data Elements Data Diagnostic - The device records an event without all the required fields 4 - Data Transfer Data Diagnostic - It has been more than a week since the device has last successfully verified that it can transfer data to the FMSCA 5 - Unidentified Driving Records Data Diagnostic - There is more than 30 minutes of unclaimed unidentified driving time within the last 24 hours P - Power Compliance Malfunction - Over the last 24 hours, there has been at least 30 minutes of missing drive time E - Engine Synchronization Compliance Malfunction - Over the last 24 hours, there has been at least 30 minutes of time when the device wasn’t receiving all the required engine data T - Timing Malfunction - The system clock is more than ten minutes off from UTC (GPS Time) L - Positioning Compliance Malfunction - Over the last 24 hours, the vehicle has traveled more than five miles and hasn’t received valid GPS for over 60 minutes R - Data Recording Compliance Malfunction - The amount of space left on the device is less than 5MB Or The file system has been tampered with S - Data Transfer Compliance Malfunction - A ELD Data Transfer check failed and subsequent checks continued to fail for another 3 days O - Other Malfunction - eFleetSuite has been manually stopped, is not responding, or is otherwise not running Skybitz Petroleum Logistics certifies that Petro ELD system complies with and is tested against the United States Department of Transportation (USDOT) Federal Motor Carrier Safety Administration (FMCSA) specifications as found in 49 CFR Part 395 for Electronic Logging Devices, Subpart B.
Fleet-Tec ELD FT-ANDROID-GEOMETRIS 1.0.1804 and up FTHOS1 Download Download Fleet-Tec Solutions Inc 833-533-8832 info@fleet-tec.com http://fleet-tec.com 2079 CULMINATION LN, Las Vegas/Nevada/89119 The Fleet-Tec HOS app 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 Fleet-Tec HOS app 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 Fleet-Tec HOS app 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 Fleet-Tec HOS app 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 Fleet-Tec 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 Fleet-Tec 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. The Fleet-Tec HOS ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The Fleet-Tec HOS 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 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 L4000 with iOS 1.0.1801.11819 or up ELDFLT Download Download GPS Trackit (866) 320-5810 FleetAdvisor@GPSTrackit.net https://gpstrackit.com/eld-fleet/ 27244 Vía Industria, Temecula, CA, 92590 Data Transfer Description – Android Registrations The ELD Fleet™ 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 ELD Fleet™ 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 ELD Fleet™ 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 ELD Fleet™ 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 ELD Fleet™ 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 Fleet™ 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 ELD Fleet™ ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The ELD Fleet™ 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 L4000 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.
Prospero Mobi PM1000 1.0+ PM1000 Download Download CAMS Software Corporation 604-777-2267 mobi@prospero.com http://www.prospero.com Unit 200 - 8651 Eastlake Drive, Burnaby, British Columbia, V5A 4T7 Prospero Mobi supports option one (1) of the ELD data transfer requirements – telematics. It supports both web services and email. Mobi uses a standardized single-step driver interface to initiate data transfer and allows the driver to select the data transfer method. The driver first taps the HOS icon on the Mobi home screen and then taps the DOT Inspection icon to display the daily header, 24-hour duty status grid and record of certified events. The driver can then tap a mail icon to email their driver logs to a pre-configured DOT address. The driver can also tap a web service icon to send their driver logs to a pre-configured FMCSA website. Prospero Mobi alerts the driver of any system malfunction(s). The driver can navigate to a prioritized listing of the malfunction code(s) and its description. The driver has a malfunction guide, illustrated below, outlining each malfunction and the recommended steps for its resolution. Code Description Resolution P Power compliance Undock and redock the tablet. Wait a moment and see if power is established. If problem persists, contact your system administrator. E Engine synchronization compliance Undock and redock the tablet. Wait a moment and see if the engine connection is established. If problem persists, contact your system administrator. T Timing compliance Undock the tablet. Turn off the tablet, wait a moment and then turn the tablet back on. Redock the tablet and see if problem is resolved. If problem persists, contact your system administrator. L Positioning compliance Undock the tablet. Turn off the tablet, wait a moment and then turn the tablet back on. Redock the tablet and see if problem is resolved. If problem persists, contact your system administrator. R Data recording compliance Undock the tablet. Turn off the tablet, wait a moment and then turn the tablet back on. Redock the tablet and see if problem is resolved. If problem persists, contact your system administrator. S Data transfer compliance Ensure there is either WiFi or cellular connectivity and manually check for data transfer connectivity. Undock the tablet. Turn off the tablet, wait a moment and then turn the tablet back on. Redock the tablet and see if problem is resolved. If problem persists, contact your system administrator. O Other detected malfunction Contact your company system administrator. The Mobi product was tested against the FMCSA ELD test procedures using a combination of road testing and J1939 simulation to provide engine telemetry. Test data was created to ensure that the requisite test case conditions were met and the tests cases were executed and validated.
Maven ELD MELD_Android 3.19.2 or higher MMELDA Download Download Maven Machines, Inc. 412.499.3877 info@mavenmachines.com https://www.MavenMachines.com 4117 Liberty Ave, Pittsburgh, PA 15224 ELD Records are transferred via encrypted email and Web Services to the FMCSA. Instructions: 1. Driver presses large blue button labeled 'DOT Inspection Mode'. 2. On following screen driver presses large blue button labeled, 'Send Logs to FMCSA'. 3. Alternatively, driver presses button labeled, 'Inspect Logs on Device', in order to show inspection officer the previous 7 days logs plus today's Maven Machines detects, logs, and codes all malfunctions and diagnostic events listed in Table 4 of the ELD Rule. Specifically; 1. The Maven ELD monitors for power compliance and will record a power data diagnostic event if a driving time understatement is calculated per the power requirements specified in section 4.3.1.1 of the ELD Rule. 2. The Maven ELD monitors for engine synchronization compliance and will record an engine synchronization diagnostic event when it can no longer can acquire updated values for the ELD parameters as specified in section 4.3.1 and 4.2 of the ELD Rule. 3. The Maven ELD monitors for positioning compliance and will set and record a positioning compliance malfunction if location or timing values exceed the tolerances specified in section 4.6.1.4 of the ELD Rule. Additionally, Maven ELD will record a missing required element data diagnostic event for positioning malfunctions as described in 4.6.1.4 4. The Maven ELD monitors for data recording compliance and will record a missing data elements data diagnostics event if it detects missing data, or is no longer able to record or retain records as specified in section 4.6.1.5. 5. The Maven ELD monitors for data transfer compliance and will record a data transfer data diagnostic event or a data transfer compliance malfunction depending on the states described in section 4.6.1.7 6. The Maven ELD monitors for unidentified driving activity and will record an unidentified driving records data diagnostic event upon the conditions described in 4.6.1.6 7. The Maven ELD user interface conforms to user alerting as described in sections 4.6.2 and 4.6.3 for communicating recorded diagnostic events and malfunctions to the driver. We, Maven Machines Inc., certify that Maven ELD, including the cloud portal, mobile app, and the Maven VDA logging device mounted in the truck are all designed and operationally tested to meet the specified FMCSA ELD requirements set forth in the ELD Rule and Appendix to Subpart B of Part 395 of title 49, Code of Federal Regulations.
.eTracELD LMU4230H 2.2 VB0G10 Download Download iConnect Inc. 888-353-5624 sales@eldsmartphone.com http://eldsmartphone.com/ P.O. Box 598, Westfield, Indianapolis 46074 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.
Transflo ELD T7, T9 5.7.1711 or above TFMELD Download Download Transflo-Pegasus Transtech 813.386.6000 sales@transflo.com http://www.transflo.com 4301 W. Boy Scout Blvd. Suite 550, Tampa/FL/33607 Transflo 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 Transflo HOS app, select Login & Manage HOS. 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. Our data transfer description for drivers is outlined in this document: https://goo.gl/9Fqpbf 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 Transflo HOS device. Contact your carrier to get the install inspected. If problem still persists, replace the Transflo HOS 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 Transflo HOS 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. Our malfunctions description for drivers is outlined in this document: https://goo.gl/vf6rJi Product was tested using the FMCSA’s recommended testing procedures, supplemented by Pegasus Transflo’s internal testing procedures.
ELD Fleet iOS & CalAmp4230 1621.6202 or higher ELDFLT Download Download GPS Trackit (866) 320-5810 FleetAdvisor@GPSTrackit.net https://gpstrackit.com/eld-fleet/ 27244 Vía Industria, Temecula, CA, 92590 Data Transfer Description – Android Registrations The ELD Fleet™ 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 ELD Fleet™ 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 ELD Fleet™ 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 ELD Fleet™ 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 ELD Fleet™ 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 Fleet™ 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 ELD Fleet™ ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The ELD Fleet™ 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 CalAmp4230 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.
ALS-ELD ALS-E100 v2.0.10 ALS100 Download Download Arethos 7789294567 mail@arethos.com http://www.arethos.com 4-7651 Moffatt Road, Richmond , BC, Richmond/BC/V6Y1X9 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.
Penske Driver™ App – HOS Module for iOS PTL-Driver-HOS-iOS-2 5.0 or higher PTLI02 Download Download Penske Truck Leasing 844-426-4555 connectedfleet@penske.com http://gopenske.com/hos PO Box 563, 19603 Transfers can be initiated by tapping on the ‘Start Inspection’ link from the bottom of the ‘Daily Log’ screen. Two options will then appear ‘View on Screen’ or ‘Send to ERODS’. When ‘Send to ERODS’ is tapped an optional output comment field will appear. Once continue is tapped the process to transfer data will begin via Web Service following standards set forth in the mandate. If Web Service fail the transfer via email standards set forth in the mandate will occur. The transfer will default to using the devices cellular connection and tested sending via a Bluetooth PAN using a secondary device with internet access. The Penske Driver App – Hours of Service is capable of monitoring its compliance for various detectable malfunctions. If an ELD malfunction event is detected or cleared by the Penske Driver App – Hours of Service, the ELD records the event. If active a red icon in the application header with a ‘!’ will appear, and full screen warning will appear. When viewing the details of an active malfunction help text will provide feedback on next steps. Generally, if a driver is unable to resolve a malfunction, they would be directed switch to paper logs. When the criteria for clearing is met the malfunction indicator will become inactive/grey. Below is a list of all malfunctions: • Data Recording Compliance Malfunction • Data Transfer Compliance Malfunction • Engine Synchronization Compliance Malfunction • Position Compliance Malfunction • Power Compliance Malfunction • Timing Compliance Malfunction The Penske Driver App – Hours of Service was certified through successful execution and verification based upon the FMCSA ELD Test Procedures. The Penske Driver App – Hours of Service was installed on various types of iOS devices. The devices must have a minimum iOS OS of 10 and have a 64bit CPU (iphone 5s or newer). Testing was performed through the use of USB-Link 2 vehicle simulators, and actual vehicles with a Nexiq Blue-Link ELD adapter. The support portal systems were tested via a laptop using a web browser
CloudHawk ELD CELD01 1.0.1816.181015 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.
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.
E-Logbook UE910-N3G Version6.2 TGL500 Download Download I-Soft Global Software Solutions 1-855-922-9700 info@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.
CyntrX ELD Pro Geometris and iOS 1805.0315 & up FlexCX Download Download CyntrX 9203380479 compliance@cyntrx.com http://www.cyntrx.com 1302 South Broadway, De Pere, WI, 54115 Data Transfer The CyntrX ELD Pro 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 CyntrX ELD Pro 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 CyntrX ELD Pro 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 CyntrX ELD Pro 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 CyntrX ELD Pro ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The CyntrX ELD ProELD 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 accessed through a web browser.
TruckX-ELD XELD 1.0 TRX927 Download Download TruckX Inc 650-600-0008 contact@truckx.com http://www.truckx.com/ 257 Castro St STE 107, Moutain View, CA 94041 Web Services and email are supported for data transfer 1. Open TruckX app on mobile or tablet. 2. Make sure the ELD device is connected. Link icon on the top left should be green 3. Click on right bottom on "More" 4. Click on "Dot Inspection" 5. From four options to "View", "Print", "Email" and/or transfer data is available. More instructions in the user manual Malfunctions are collected per 395.34 of ELD mandate rule described under section 4.6 and per table 4 RED error icon is shown on every screen when ELD malfunction is detected • Driver is required to contact their company within 24 hours • Driver needs to regenerate paper logs for past 7 days when this happens • Continue maintaining paper logs until the time ELD is serviced • Company can create inspection report and send it to TruckX for diagnostic We have tested HOS rules for more than 3 months and certify we pass the tests.
Garmin eLog - dēzl 780/dēzlCam 785 GE1D01 6.50 or later GE1D01 Download Download Garmin International (800)-800-1020 product.support@garmin.com http://garmin.com/elog 1200 East 151st Street, Olathe, Kansas 66062 Garmin eLog dēzl supports the following Data Transfer methods: A. Data Transfer via Bluetooth B. Data Transfer via USB 2.0 A. Transferring Data to an Inspector Using a USB Device You can transfer data to a USB mass storage device to provide it to an authorized safety official. The Garmin eLog adapter supports USB mass storage devices formatted using the FAT32 file system. 1. From the Garmin eLog app, select "Inspection". 2. Select > Yes. 3. If necessary, enter an annotation. 4. Connect a USB mass storage device to the USB port on your Garmin eLog adapter. The adapter glows green when it is ready to send the inspection report. 5. Enter your password. 6. Select "Send to USB Device". The Garmin eLog app notifies you when the transfer is complete. 7. Remove the USB mass storage device from the adapter. B. Transferring Data to an Inspector Using Bluetooth Wireless Technology 1. From the Garmin eLog app, select "Inspection". 2. Select > Yes. 3. If necessary, enter an annotation. 4. Select Enable Pairing Mode. 5. Follow the on-screen instructions in the app to pair the Garmin eLog adapter with the inspector's mobile device. The inspection report transfers automatically after the pairing process is complete. SUMMARY of DIAGNOSTIC AND MALFUNCTION CODES Diagnostic Code 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 Malfunction 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 O Other ELD detected malfunction SUMMARY OF MALFUNCTIONS: Garmin eLog supports the following Malfunctions specified below. Each Malfunction follows on with instructions which are provided to the driver in the Driver Reference Guide to help troubleshoot the issue. P: “Power compliance” malfunction The adapter did not receive power, or was not fully functional, for a period of time. At least 30 minutes of driving time may not have been correctly recorded across all drivers over the past 24 hours. Perform the following actions: 1 Check the vehicle diagnostic port connections. 2 Verify the adapter is firmly plugged into the vehicle diagnostic port. 3 Review all affected driver logs for missing or incorrect data E: “Engine synchronization compliance” malfunction The adapter failed to synchronize with the vehicle engine computer to record required engine data for driver logs. At least 30 minutes of inaccurate data may have been recorded across all drivers over the past 24 hours. Perform the following actions: 1 Check the vehicle diagnostic port connections. 2 Verify the adapter is firmly plugged into the vehicle diagnostic port. 3 Review all affected driver logs for missing or incorrect data. T: “Timing compliance” malfunction The Garmin eLog system failed to accurately verify the calendar date or time of day required for driver logs. Perform the following actions: 1 Verify the adapter is firmly plugged into the vehicle diagnostic port. 2 Check the Bluetooth settings on the device running the Garmin eLog app, and verify the device and the adapter are connected. 3 Check the date and time settings on the device running the Garmin eLog app. 4 Review all affected driver logs for missing or incorrect data. L: “Positioning compliance” malfunction The Garmin eLog system failed to acquire valid location positions required for driver logs. At least 60 minutes of inaccurate data may have been recorded across all drivers over the past 24 hours. Perform the following actions: 1 Verify the Garmin eLog app is running and a driver is logged in when driving the vehicle. 2 Check the Bluetooth settings on the device running the Garmin eLog app, and verify the device and the adapter are connected. 3 Check the GPS settings on the device running the Garmin eLog app, and verify the device settings allow location positions to be shared with the Garmin eLog app. 4 Review all affected driver logs for missing or incorrect data. R: “Data recording compliance” malfunction The Garmin eLog system has reached the maximum storage capacity for driver logs and cannot store or retrieve more logs. Perform the following actions: 1 Create a RODS report for each driver for record keeping. 2 Log in as an administrator. 3 Back up the system data. 4 Remove unneeded files from the storage of the device running the Garmin eLog app. S: “Data transfer compliance” malfunction Multiple failures occurred with the method for transferring roadside inspection reports. Perform the following actions: 1 Check the Bluetooth settings on the device running the Garmin eLog app, and verify the device and the adapter are connected. 2 Verify all USB storage devices used to transfer roadside inspection reports are operating correctly and are formatted using the FAT32 file system. 3 If you have not performed a data backup within the previous seven days, back up your recorded Garmin eLog data to a USB storage device. O: "Other" malfunction" Garmin eLog supports an "Other" type malfunction, namely "Adapter Firmware Malfunction". Adapter Firmware Malfunction is a placeholder in the event it is not possible for the eLog app to update the eLog adapter firmware. This malfunction is not an anticipated malfunction but is made available as a placeholder. Perform the following actions: 1 A serious error occurred attempting to update the adapter firmware. Contact Garmin® customer support for further help. 2 Outdated adapter firmware may not maintain compliance. Garmin recommends keeping paper logs until the adapter firmware is successfully updated. SUMMARY OF DIAGNOSTICS: Garmin eLog supports the following Diagnostics. Each Diagnostic follows on with instructions which are provided to the driver in the Driver Reference Guide in order to help troubleshoot the issue. 1: “Power data diagnostic” event The adapter did not receive power, or was not fully functional, for a period of time. Perform the following actions: 1 Check the vehicle diagnostic port connections. 2 Verify the adapter is firmly plugged into the vehicle diagnostic port. 3 Review all affected driver logs for missing or incorrect data. 2: “Engine synchronization data diagnostic” event The adapter failed to synchronize with the vehicle engine computer to record required engine data for driver logs. Perform the following actions: 1 Check the vehicle diagnostic port connections. 2 Verify the adapter is firmly plugged into the vehicle diagnostic port. 3 Review all affected driver logs for missing or incorrect data. 3: “Missing required data elements data diagnostic” event The Garmin eLog system failed to obtain one or more required data elements when recording driver logs. Perform the following actions: 1 Check the vehicle diagnostic port connections. 2 Verify the adapter is firmly plugged into the vehicle diagnostic port. 3 Check the Bluetooth settings on the device running the Garmin eLog app, and verify the device and the adapter are connected. 4 Check the GPS settings on the device running the Garmin eLog app, and verify the device settings allow location positions to be shared with the Garmin eLog app. 5 Review all affected driver logs for missing or incorrect data. 4: “Data transfer data diagnostic” event A failure occurred with the method for transferring roadside inspection reports. Perform the following actions: 1 Check the Bluetooth settings on the device running the Garmin eLog app, and verify the device and the adapter are connected. 2 Verify all USB storage devices used to transfer roadside inspection reports are operating correctly. 3 If you have not performed a data backup within the previous seven days, back up your recorded Garmin eLog data to a USB storage device. 5: “Unidentified driving records data diagnostic” event At least 30 minutes of unidentified driving was recorded within the current 24 hour period, and over the previous 7 days. Perform the following actions: • Drivers: Review and claim the unidentified driving time. • Administrator: Review and assign the unidentified driving time to the respective drivers. Each functional requirement specified in the APPENDIX A TO SUBPART B OF PART 395—FUNCTIONAL SPECIFICATIONS FOR ALL ELECTRONIC LOGGING DEVICES (ELDS) has been individually tested by Garmin Software Quality (SQ) Team. Each requirement has been validated according to meeting the specified requirement as is written in the specification. The FMCSA Test Plan and Procedures (Version 2.0) were consulted when verifying each requirement. The Garmin eLog dēzl solution is a local-type ELD solution supporting USB and BT data transfer methods at the roadside and meets all technical specifications detailed in the ELD rule with the following assumptions/caveats: (1) Electronic Motor Carrier Edit requests is an optional requirement noted in the ELD Technical Specifications (4.3.3.1.3). This is not supported since it is not an essential requirement for a local-type ELD. (2) The ELD data and formats required to be recorded for each event type were verified by viewing the generated FMCSA ELD Data File whereas the FMCSA Test Plan Procedures implied that the application user interface would provide this capability.
ELD Fleet CalAmp 4230 Hardwire with Android 1621.6202 or higher ELDFLT Download Download GPS Trackit (866) 320-5810 FleetAdvisor@GPSTrackit.net https://gpstrackit.com/eld-fleet/ 27244 Vía Industria, Temecula, CA, 92590 Data Transfer Description – Android Registrations The ELD Fleet™ 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 ELD Fleet™ 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 ELD Fleet™ 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 ELD Fleet™ 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 ELD Fleet™ 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 Fleet™ 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 ELD Fleet™ ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The ELD Fleet™ 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 CalAmp 4230 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.
GoodDealGPS GDELD1000 3.0.1 GDGGPS Download Download Bransys 8663555552 contact@gooddealgps.com https://www.gooddealgps.com 333 S Wabash Ave, Ste 2700, Chicago/IL/60604 Transfer with FMCSA SOAP web services - ELD connects with FCMSA SOAP web services and submits: - our certificate (gps_gooddealgps_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 (GDGGPS) - 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. Currently there is only a single valid version of the file as defined by the Final Rule published December 16, 2015.) Step by step instructions: To send your logs to an officer, from the main menu in the GoodDealGps Mobile app, select Send logs and press button Send logs to send 8 logs (for current 24-hour period and the previous 7 consecutive days). You have to options: 1. Send logs by 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 logs 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. ● Available apps display. Note that depending on what apps you have installed on your device, you may see different sharing apps on this screen. ● Using your preferred email method, send the automatically attached CSV file. 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. 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.
PrePass ELD PPELD100 1.0 PPELD1 Download Download HELP Inc. Provider of PrePass 800-773-7277 sales@prepass.com http://www.prepass.com 101 North 1st Ave Suite 1900, Phoenix/AZ/85003 The ELD supports the telematics transfer methods. This includes Wireless Web services and Email transfer. The following is the process for a user to complete web service and email transfer: 1. Driver taps on the “Inspections” main menu. 2. Touch the menu icon in the upper right (three vertical dots) 3. Touch the “Share logs” option 4. Type in the text requested by the inspector 5. Touch either “1Send Email” button or “Send to Web Service” button Note: Until FMCSA provides beta version of email submission vendors cannot fully test the function. Malfunction Diagnostics Code Description Type P “Power compliance” malfunction Malfunction E “Engine synchronization compliance” malfunction Malfunction T “Timing compliance” malfunction Malfunction L “Positioning compliance” malfunction Malfunction R “Data recording compliance” malfunction Malfunction S “Data transfer compliance” malfunction Malfunction O “Other” ELD detected malfunction Malfunction 1 “Power data diagnostic” event Diagnostic 2 “Engine synchronization data diagnostic” event Diagnostic 3 “Missing required data elements data diagnostic” event Diagnostic 4 “Data transfer data diagnostic” event Diagnostic 5 “Unidentified driving records data diagnostic” event Diagnostic 6 “Other” ELD identified diagnostic event Diagnostic The FMCS Electronic Logging Device (ELD) Test Plan and Procedures were used to develop the baseline functional requirements and the individual acceptance criteria for each piece of required functionality of the application. Extensive manual and automated testing was performed to ensure compliance during both during the initial application development and continues to be used during subsequent feature development to test for possible regressions.
Hours Of Service iOS & ATrack AK11 1.0.1816.180904 HOS001 Download Download VisTracks, Inc. 630-596-5420 info@vistracks.com http://www.vistracks.com/ 801 Warrenville Road, Lisle, IL 60565 The 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 the 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. The 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, 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 VisTracks Hours of Service (HOS) App was certified by the VisTracks testing team through successful execution and verification of the FMCSA ELD Test Procedures. The HOS App 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 ATrack AK11 engine connected device. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the VisTracks HOS web application (portal) that can be accessed through a web browser.
InTouch ELD - iOS Geometris 1621.6202 or higher ITELD1 Download Download InTouch (800) 881-6343 eld@intouchgps.com http://www.InTouchGPS.com 439 S Florida Ave STE 100B, Lakeland, FL 33801 The InTouch 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. 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 InTouch 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 InTouch 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 InTouch 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. InTouch ELD was tested in compliance with the Electronic Logging Device (ELD) Test Plan and Procedures
1ELD CTG4 1.H CTG4BT Download Download Cartrack USA 4245008601 support@cartrack.us https://www.cartrack.us/ 3617 Hayden Avenue, Suite 101, Culver City 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
IVIS Next Generation IVIS_NG 1.00 UPS123 Download Download United Parcel Service N/A na@ups.com http://ups.com 55 Glenlake Pkwy, Atlanta, GA 30328 We have implemented option 1, the electronic transfer of data to an authorized safety official on demand via wireless Web services and email. Steps for Driver on Mobile Device. 1. Select DOT Log 2. Select DOT Transfer Log Option 3. Select the transfer mode from the Transfer mode drop down – Web Service or Email 4. Update the start and end date as required by the requesting official 5. Update the Comment as required by the requesting official 6. Select Done 7. Verify that you want to transfer the DOT log when the confirmation pop up appears. We account for the following: 1. Power Compliance Data Diagnostic and Malfunction Recording and Monitoring 2. Engine Synchronization Data Diagnostic and Malfunction Recording and Monitoring 3. Timing Compliance Data Diagnostic and Malfunction Recording and Monitoring 4. Positioning Compliance Data Diagnostic and Malfunction Recording and Monitoring 5. Data Recording Compliance Data Diagnostic and Malfunction Recording and Monitoring 6. Data Transfer Compliance Recording and Monitoring IVIS next generation has been tested using the test plan provided by FMCSA. All functionality has been shown to be in compliance with FMCSA requirements.
ELD Fleet iOS & Pacific Track 1.0.1801.11819 ELDFLT Download Download GPS Trackit (866) 320-5810 FleetAdvisor@GPSTrackit.net https://gpstrackit.com/eld-fleet/ 27244 Vía Industria, Temecula, CA, 92590 Data Transfer Description – Android Registrations The ELD Fleet™ 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 ELD Fleet™ 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 ELD Fleet™ 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 ELD Fleet™ 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 ELD Fleet™ 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 Fleet™ 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 ELD Fleet™ ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The ELD Fleet™ 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.
Compliance Now iOS & Pacific Tracks 1.0.1801.11819 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.
Trakopolis ELD 3799 1.3.37.1 TRK001 Download Download Trakopolis IoT Corp 4034507854 eld@trakopolis.com http://www.trakopoliscorp.com 1711 10th Ave SW, Suite 300, Calgary, Alberta T3C 0K1 The means selected for certified data transfer mechanism is Web Services and Email interface. The application user will be able to select a delivery of data through web service or email delivery. The user will be prompted for any additional information prior to submitting through the FMCSA Web Services procedure or to the FMCSA ELD email address. A receipt file from web service response or reply email will be reviewed to confirm successful delivery or investigation of any errors. Malfunctions in the system are monitored through the Trakopolis Fleet Management Systems and supported by a 7/24/365 direct and extended support team. Specifically, from the Non-Reporting Terminal and Engine Diagnostics reporting the category malfunctions of Power, Engine Synchronization, Timing, Positioning and Data Recording. Overview of the Trakopolis ELD Compliance Audit 1. The Trakopolis Compliance Audit is designed to provide a summary of ELD test results outlined in the FMCSA document Electronic Logging Device Test Plan and Procedures. 2. The Compliance Audit lists all elements of the Requirements Tractability Matrix (RTM) in the same groupings and order as Electronic Logging Device Test Plan and Procedures. a) Accounts b) Vehicle interface c) ELD Inputs d) Processing e) Recording f) Monitoring g) ELD Outputs h) Data Transfer 3. The Electronic Logging Device Test Plan and Procedures shall be the reference document for the Trakopolis ELD Quality Assurance Program and the Compliance Audit shall be a summary of the test results. All test results shall trace back to the decomposed requirements of CFR-395 Subpart B - Electronic Logging Devices and Appendix A to Subpart B -Functional Specifications for Electronic Logging Devices. Steps For Completing The Compliance Audit 1. Testing shall be completed by a person who is knowledgeable and competent in the subject matter of Functional Specifications being tested. 2. The tester shall use the Electronic Logging Device Test Plan and Procedures as the working document for conducting an examination of the ELD. 3. The tester shall record the results of the examination as a PASS or Fail on the Compliance Audit as well as any descriptive notes. 4. The column “Item #.” indicates the specific functional requirement to be validated through the test procedures. 5. The column “Functional Requirement” provides the basic description that needs to be met. 6. The “Response” column is to indicate whether the Auditor was positive (+), negative (-), or non-committal (n.c.) in his/her responses. 7. The "Notes" column is to describe circumstances that affected the test or the auditors response or notes regarding the strengths or suggested improvements of the specific function being tested.
iFleetELD tisels1 1.1.5 TISELD Download Download Transportation Information Systems 888-464-8471 info@tisfleet.com http://www.tisfleet.com 5435 Cahuenga Blvd. Suite D, North Hollywood, CA 91601 The iFleetELD provides Data Transfer Capabilities as specified in section 4.9 of ELD Test Plan and Procedures. Data Transfer to an Authorized Safety Official is provided using the standards Option (1) Telematics transfer methods(4.10.1). This transfer can occur either via email(4.10.1.1) or Wireless Web services(4.10.1.4, 4.10.2, Appendix to subpart B of 395) With this feature, a safety inspector will easily be able to retrieve Driver data in the form of a text file. The text file will be attached to an email or as part of an web services request. The text file is formatted according to section 4.8.2 of ELD Test Plan and Procedures. It includes Driver data from the previous 7 days up to the the time of the inspection. At the beginning of a safety inspection, the inspector will enter an "Inspection Mode" in the iFleetELD. From there he will perform a visual inspection of the Driver's data for the current 24-hour period, with the ability to go back and view records from the previous 7 days. If the inspector feels the need to retrieve the Driver's data electronically he or she will press a button labeled "E-File". This will then generate the output file and automatically send it to the desired FMCSA endpoint(4.3.2.4 Driver’s Data Transfer Initiation Input). The iFleetELD is connected to the engine ECM via a Bluetooth or serial interface. This connection monitors a number of engine functions including power, engine hours, engine on/off, VIN, and speed. The status of the Bluetooth connection with the ECM is displayed to the driver in the main view of the ELD. In the case of a malfunction the corresponding codes are sent as part of the ELD Output File. The malfunction codes used are referenced from Table 4 of the federal Register: Power Compliance Engine Synchronization compliance Timing Compliance Positioning Compliance Data Recording Compliance Data Transfer The following is a description of the measures taken to comply with the above rules. Power Compliance (P) To use the iFleetELD, we require that driver power on the device and login using his or her credentials before turning the engine on. In the case that the driver mistakenly turns the engine on before logging in, the event is still logged under a pre-assigned unidentified driver id, where it can later be “re-attached” to the driver through a Unidentified ELD Event Confirmation view in the app. In addition to this, tablet shutdown and low battery events are logged to monitor a suspected premature shutdown by the driver. Engine Synchronization Compliance (E) Connectivity to the Engine ECM is constantly monitored at intervals of less than 5 seconds. As a visual aid to the driver, we have designated an button icon which is set to RED(ECM Connected) or GREEN(ECM Disconnected). This will alert the driver along with an auditory beep of a loss in engine connectivity. If a failure occurs for more the 30 minutes, we ask the driver report the issue to tech support and any faulty hardware is replaced. Timing Compliance (T) All Driver and CMV data is recorded in UTC time on the iFleetELD’s database. Drivers and Managers do not have the ability to alter or generate the timestamps that are sent with any data. In the case of a Driver making a mistake in producing his or her data, the Driver can create an annotation according to the rule in 4.3.2.6. In addition to the timestamp of the ELD Event, we are also saving the time each record made it to the server, providing an effective crosscheck of when the Event was created and when it was saved. Positioning Compliance(L) This procedure is in compliance with 4.3.1.6 CMV position of the federal Register appendix. Our monitoring procedure validates Latitude and longitude coordinates and distance traveled in miles and timestamp since the last position. If we detect a failure in accordance with 4.6.1.4 (a), (b), (c), (d) we will record an event whereby the ELD record the character ‘X’ in both Latitude and Longitude. In the case of hardware failures, faulty devices will be replaced within an 8 day timeframe. Data Recording Compliance (R) All ELD Data is stored locally on the tablet for the previous 7 days up to the current 24 hour period. The iFleetELD ensures data synchronization between the device and the server is consistent and up to date. Loss of network and a driver who has not logged in yet are the edge cases that we have accounted for. For a loss of network, the event is logged as a malfunction and upon reconnection, the data is synced. For unidentified records, the Driver is provided the option of identifying his or her data via an Unidentified ELD Event Confirmation view. Data Transfer compliance (S) The iFleetELD offers option 1 (Telematics) according to 4.10.1.1 and 4.10.1.2 rules (i-Web services, ii-email) as a means for a sending an ELD Output File to an authorized safety official during a roadside inspection. As a self monitoring procedure, the ELD connects to the FMCSA Web Services endpoint to identify itself as a certified device, and any status errors received are logged as malfunctions. This ELD identification process is run every time the Driver logs in as well as right before attempting to send an ELD Output File. The iFleetELD was tested to fulfill the Functional Requirements located in section 4 of ELD Test Plan and Procedures. Testing was conducted by engineers at the software level as well as manual testing done by QA. In addition, a focused group of beta users were selected to take part in a lengthy pre-release phase of the iFleetELD(Versions 0.0.1 - 1.1.2). For software tests, mock data was utilized for the purpose of simulating the data generated by a Driver and his/her CMV. With this data our engineers will be able to easily conduct automated regression tests as features are added to subsequent releases of the iFleetELD, thus creating a stable release cycle. In addition to mock data, our engineers were provide the convenience of using an OBDII J1939 Simulator to test and develop the iFleetELD. The simulator allows emulated Engine Synchronization data to be attached to Driver status events and so on. Despite the convenience of simulated data, the actual tests to satisfy the Pass/Fail requirements of ELD Test Procedures were done using a combination of manual tests conducted by QA and Beta user feedback. The Beta users consisted of several small fleets consisting of 10 trucks or less with owner/ operators willfully testing our product. By testing using real engine data and drivers over time, we were able to hone in on issues or edge case bugs that would otherwise be obscured or untestable at the software level. This especially came in handy when testing the reliability of any ELD Function that requires a physical dimension outside of the office environment. These include: Geolocation Auto Driving/On Duty detection Vehicle Speed Spotty Network Connectivity Testing in the field with Beta users also allowed us to look at the behavior over a prolonged period of time(2 weeks or more), aiding our testing of the following features: Weekly On Duty/ Driving Limit Calculations Shift Reset Calculations With these tests described, we certify that we have complied with FMCSA requirements
INTELELOGS INTERP-01 1.68 or higher ITELD1 Download Download Intelligent Telematics Inc. 707-653-5647 sales@intelelogs.com http://www.intelelogs.com 28130 Ave Crocker Ste 302, Valencia/CA/91355 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. The INTELELOGS 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.
ISR FleetTrack® HOS ELD Module HOS-1 Version 1.9 ISR500 Download Download ISR Corporation 410-536-9989 x 302 sales@isrfleettrack.com www.isrfleettrack.com 1502 Joh Avenue, Baltimore, MD 21227 Please see ISR HOS Electronic Logging Device User’s Guide, pages 11-12, attached to this application. The ISR Corporation Hours of Service ELD product, model # HOS-1 has the capability to self-monitor the device’s compliance with the technical requirements as they presently exist. The HOS-1 is designed to be an add-on accessory to the fleet management telematics solution produced by ISR Corporation, called ISRFleetTrack®. The summary list of monitored detectable malfunctions which trigger a logged event are as follows: Power compliance, Engine synchronization compliance, Timing compliance, Position Compliance, Data Recording compliance, Data Transfer compliance, and “Other” for all other ELD detected malfunctions. In addition, the following Data Diagnostic events will be detected and logged as events: Power Data, Engine Synchronization, Missing Required Data Elements, Data Transfer, Unidentified Driving Records Data and “Other” for any additional ELD identified diagnostic events. For each malfunction event listed above, a visual malfunction indicator is automatically displayed on the ELD touch screen display. Similarly, for each triggered Data Diagnostic event listed above, a separate Data Diagnostic visual status event indicator is displayed on the ELD touchscreen for the purpose of informing the current driver that a Data Diagnostics event has occurred. All tests performed on the ISR Corporation HOS-1 electronic Logging Device were performed in accordance with the ELD Test Plan document produced by ISR Corporation and in compliance with the current updated ELD Test Procedures furnished by the FMCSA. These tests verify that the HOS-1 unit meets the functional requirements as stated in the technical specifications of the Appendix to subpart B of part 395, title 49, CFR.
Rigbot RBV002 7.1 and Newer RBELD2 Download Download Rigbot LLC 1844 474 4268 contactus@rigbot.com http://www.rigbot.com 316, W Washington Avenue, Suite 675, Madison WI 53703 Rigbot data transfer happens through Option1 specified by FMCSA via internet by email and data transfer to FMCSA Web services. Following is the step-by-step instructions for the driver to produce and transfer the ELD records to an authorized safety official: - 'DOT Inspection Mode' can be accessed by by tapping the main menu on top left corner of the screen - Device can be physically removed from the cradle and handed to the official with the DOT Inspection Mode screen for the officer to review on screen - As instructed by the official, 'Transfer' button can be clicked to transfer the ELD records electronically to the official - 'Transfer' button will open a window with options to either a) email or to b) transfer to FMCSA Web services - Tapping one of the two options will trigger automatic transfer of the ELD records to the authorized safety official - Above step will generate an acknowledgement indicating that the information has been sent via email per the selected option - Two LED lights will indicate any ELD malfunctions - Green LED light if not solid, suggests loss of power to the ELD, Orange light if not solid, loss of internet connectivity - In addition, driver receives an alert on the screen header - Following malfunctions with the ELD will be indicated with a ‘stop’ icon in the alert center and will require the driver to start using paper logs • P : Power Compliance malfunction • E : Engine Synchronization compliance malfunction • T : Timing Compliance malfunction • L : Positioning Compliance • R : Data recording Compliance malfunction • S : Data transfer Compliance malfunction • O : Other ELD detected malfunction - Following diagnostic codes will show in the Alert Center along with time stamp. Continued accumulation of such events will lead to the compliance malfunctions listed above • 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 Rigbot ELD system was tested successfully with the test procedures described by FMCSA in the ELD Test Plan Procedures guide. - The Mobile ELD device that can be used by drivers for recording their activities compliant with the FMCSA Hours of Service rules was tested on different Android versions and in different screen sizes and form factors. - The truck’s Engine Control Unit activity interaction with the Rigbot ELD device was tested using both simulated Virtual Truck Device (AU Group Electronics - SAE J1939 Gen II) and using actual trucks following J1939 and J1708 protocols with Cummins ISX diesel engines. - A web portal to help the motor carrier(dispatch manager) to keep track of their drivers’ activities, daily records and their trucks was also against the relevant FMCSA ELD test plan procedures.
Hours Of Service iOS & Pacific Track 1.0.1801.11819 HOS001 Download Download VisTracks, Inc. 630-596-5420 info@vistracks.com http://www.vistracks.com/ 801 Warrenville Road, Lisle, IL 60565 The 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 the 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. The 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, 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 VisTracks Hours of Service (HOS) App was certified by the VisTracks testing team through successful execution and verification of the FMCSA ELD Test Procedures. The HOS App 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 VisTracks HOS web application (portal) that can be accessed through a web browser.
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.
PMS Electronic Logging Device PMSE01 1.0 PMSELD Download Download Propane Management Systems (270)538-1717 warren@propanemanagementsystems.com www.propanemanagementsystems.com P.O. Box 2532, Paducah, KY 42002 The ELD Output file is composed of records from the cached data. It will pull all users that have driven the CMV currently in use by the driver, the unidentified driver record will be retrieved, and it will pull all CMVs the driver has operated in the time period. Any events related to the driver, truck, and unidentified driver records will be included after the header, user list, and truck list in the order outlined in section 4.8.2 of the functional requirements document. The file is saved to a CSV using the ELD Output File Name Standard outlined in 4.8.2.2. Each method of data transfer selected must go through the process of gathering the required data, and generating the CSV file. There are three methods currently available to the driver for transferring the generated file. The methods are Web Service, Email, and USB. The Web Service method will generate the CSV file, and package it in the outlined format FMCSA requires for their web service. The Email method will encrypt and sign the generated file into SMIME using RSA, and encrypt again using the provided AES key before sending over SMTP. The USB method will detect the USB device, and transfer the file to the authorized official. The first step for the driver is to press the "Officer" button on the main screen. A new screen will pop up to select Web Service, Email, or USB. They will press one of the options, and press "Proceed to Output". It will prompt the driver to enter in an output file comment using the form's on-screen keyboard. Once they are finished entering in the comment, they will press "Accept". The data transfer process will start for the selected option, and the screen will inform the driver when the transfer completes. If records are being requested outside of the cached data window, the authorized officials can request the information from the office. The office program allows for up to 6 months or older to be retrieved. The office program allows for selecting based off of driver, trucks, or terminal, and will generate a file with a requested date range. Multiple files will be generated following the required naming convention, and will include the same format as a truck generated output file. The device has been developed to monitor and record the malfunctions and diagnostics listed in Table 4 of the ELD ruling. Power Data Diagnostic and Power Compliance Malfunction: The device will check to see if it was the engine had been running before the device had started monitoring. The device will check to see if and aggregated 30 or more minutes of driving time has occurred that was not recorded otherwise by the device in the last 24 hour period. Engine Synchronization Data Diagnostic and Engine Synchronization Compliance Malfunction: The device continually monitors it's connection with the CMV's ECM. The device also checks if 30 or more minutes of aggregated connection loss occurs withing the last 24 hour period. Timing Compliance Malfunction: The device will synchronize its clock with an Internet time server. Positioning Compliance Malfunction: The device continually monitors its ability to obtain the current GPS position and will check if an aggregated 60 or more minutes of inability to obtain current position in the past 24 hour period. Data Recording Compliance Malfunction: The device monitors its ability to record all events. Data Transfer Data Diagnostic and Data Transfer Compliance Malfunction: The device will periodically check if it is able to communicate with FMCSA web services and if any initiated data transfers fail. Other ELD Identified Diagnostic and Other ELD Detected Malfunction: In the event a device specific error the it monitors occurs that is not otherwise listed in Table 4, the device will record it. Missing Required Data Elements Data Diagnostic: The device will check if any user entered data is missing required elements. Unidentified Driving Records Data Diagnostic: The device will check if an aggregated 30 or minutes of recorded, but otherwise unidentified driving time occurred within the past 24 hour period. We certify in our model PMSE01 used in conjunction with a Windows Tablet conforms to the ELD requirements, as proven with the successful execution of the test procedures. The following details test procedures used for certification: The ELD utilizes an internal geo-location mechanism under Windows 10 location services with optional support for external mechanisms. The Geo-Location protocol undergoes constant monitoring, and the program will ping the service to ensure a response can be obtained and a valid location is present. Any failure to log geo-locations are recorded as a diagnostic or malfunction for the current driver as outlined in Section 4.6.1.4. CMV communication is ensured through both an internal run of diagnostic port commands in a mock vehicle interface, and utilizing appropriate CMV with diagnostic ports. In order to verify operational status with CMV, varied manufacturer years were utilized in testing older vehicles compared to newer vehicles. Any information the ELD is unable to retrieve from the CMV is logged under the appropriate compliance monitoring diagnostic or malfunction as outlined in 4.6.1. Each ELD is placed under a test plan involving each driver status, and all malfunction and diagnostic scenarios to validate proper log recording. The malfunction and diagnostic cases are run in an automated process to force the ELD into the appropriate state, and cross checked with recorded record. Selected CMV drivers were instructed to include prototype versions in conjunction with their existing systems in order to verify a real-time environment for driver records. The upload file has been sent through FMCSA’s file verification portal to ensure the format meets certification. Any changes that were made to the generation process utilized the portal to re-certify the authenticity of the format. The contents of each generated file was cross-checked with the outline in the Functional Requirements for each segment of the output file under various usage scenarios. The FMCSA Web Service is pinged in regular intervals to verify communication to the portal is achievable. During test file submissions the test credentials provided by FMCSA were utilized to certify successful upload to FMCSA Web Service. USB Transfer was verified utilizing the provided authentication file, and a flash drive maintained for testing ELD. This flash drive was plugged into the ELD, and the procedure was executed resulting in reliable and secure file transfer over USB. Each attempt was verified by examining the USB flash drive for the output file. Bluetooth Transfer was verified by successfully testing Bluetooth pairing with an appropriate device, and utilizing the connection for Web Service communication. The Web Service transfer procedure was utilized to successfully verify the ability to ping the service, and certify capability to upload the file.
Trimble FieldMaster Logs FML003 (TVG 675 & Android tablet) v3.3 or higher FML003 Download Download Trimble 877-728-7623 fsm_sales@trimble.com http://www.trimble.com/ 10368 Westmoor Dr, Westminster, CO 80021 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 officers 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 Trimble FieldMaster Logs application has stopped working or is not responding as expected Trimble 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 Trimble FieldMaster Logs v3.3 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.
MobileTRAQ ELD Link1 MA-MBLT-ELD1 3.1.5 WLI001 Download Download Mobile Awareness, LLC 866-653-5036 info@mobileawareness.com http://www.mobileawareness.com 6573-A Cochran Road, Solon, Ohio 44139 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. Now that Web Services are available, we have completed the Web Services transfer method. 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 have sufficiently completed testing of the MobileTRAQ ELD Link1 to meet all of the functional requirements according to the FMCSA’s 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.
BIT OBD ELD for Android BIT17002 2.1.0 BITOBD Download Download Blue Ink Tech (304) 840 0142 support@blueinktech.com https://blueinktech.com 1102 3rd Ave; Suite 401, Huntington, WV 25701 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. We have sent data exchange emails to the FMCSA email, but we are waiting on full implementation of this email endpoint (FMCSA's server is not currently sending responses). 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. This OBD-II ELD was tested on multiple medium duty vehicles from Dodge, Ford, and Chevrolet however it is unlikely to work in all medium duty vehicles because there is not a standard way of acquiring the odometer reading in ODB-II vehicles.
FleetRover WiFi FleetRover ELD-WiFi 1.42.7 FR1427 Download Download FleetRover 647-680-9876 help@fleetrover.com http://fleetrover.com/ 2 Barnham Street, Ajax/Ontario/L1Z 0M5 1. Send Logs To a Printer - From the home screen, tap on the "eye" in the top right corner to enter Inspection Mode - You will now see "INSPECTION MODE - Please hand this device over to the Inspector" - Select "BEGIN INSPECTION" on the bottom of the screen by pressing it with your finger. - To send your logs to a printer, select the "printer icon" in the top right corner. - Click the arrow in the top right corner to select the appropriate printer - You also have the option to download the logs to the device as a PDF. It will appear as "Save as PDF" (which can then be viewed and/or emailed). - Choose the appropriate printer from the list provided in the "Select printer" drop-down. 2. Email Logs to Yourself or a Fleet Manager - From the home screen, select "Send daily logs". - Choose which timeframe you would like to share by selecting the correct period (24 hours, 7 days, or 14 days) - Enter the email address in the "Enter email address" field - You will see an "Email sent successfully". This confirms your logs have been sent. 3. Web Services/Email Logs to an Inspector - From the home screen, tap on the "eye" in the top right corner to enter Inspection Mode - You will now see "INSPECTION MODE - Please hand this device over to the Inspector" - Select "BEGIN INSPECTION" on the bottom of the screen by pressing it with your finger. - To send logs to the Inspector, select the arrow in the top right corner of the screen - Choose which timeframe you would like to share by selecting the correct period (24 hours, 7 days, or 14 days) - Enter the routing number provided by the inspector into the "Enter routing number" field - Logs will be sent through both Web Services and email with the routing number provided - You will see "sent successfully". This confirms your logs have been sent. Data Diagnostic events Code and Description: 1: Your ELD has been off for over a minute. Please re-start the vehicle, or check your ELD’s connection -Occurs when an ELD is not powered and fully functional within one minute of the vehicle engine power up, and the ELD does not remain powered while the vehicle engine is powered. 2: Your ELD has lost connection. Please re-start the vehicle, or check your ELD’s connection -Occurs when an ELD loses connection to the ECM and cannot obtain any required data sources (engine power, vehicle motion, miles driven, and engine hours) and their updated values within 5 seconds. 2: Your ELD has lost connection. Please re-start the vehicleor check your ELD’s connection -NOTE: If upon re-connect, the ELD is still not obtaining required data sources 'Engine Synchronization Failure' alert will be sent to FMCSA. Driver will be notified, and issue will be resolved by FleetRover within 24 hours -Occurs when an ELD loses connection to the ECM and cannot obtain any required data sources (engine power, vehicle motion, miles driven, and engine hours) for more than 30 minutes during a 24-hour period. 3: Missing required data elements. Please check your ELD's connection. -Occurs when any required data element is missing at the time of its recording. 3: Please enter your location -Occurs when an ELD doesn’t acquire a valid position measurement within 5 miles of the vehicle’s movement during a cumulative 60-minute or greater period over 24 hours. -Note 1: If this malfunction is due to a change in driver duty status, the ELD will prompt the driver to enter a location. If the driver does not enter the location, and the vehicle is moving, the ELD will record a “missing required data element” diagnostic event for the driver. -Note 2: If the driver does not enter the location within 120 minutes a 'Position Compliance Failure' alert will be triggered 4: Due to a connection error, the data transfer process has failed. Please retry and check your internet connection -Occurs when user attempts to use the Telematics services and the attempt is unsuccessful for connectivity reasons 4: Due to an encryption error, the data transfer process has failed. Please retry and check your internet connection -Occurs when user attempts to use the Telematics services and the attempt is unsuccessful because the encryption process was somehow corrupted 5: You are currently in unidentified driving mode. Please assign a driver to the vehicle. -Occurs when an unidentified driver record has been recorded on the ELD for more than 30 minutes of driving in a 24-hour period. -NOTE: If a driver is not assigned immediately, an 'Unidentified Driving Records Data Diagnostic Failure' alert will be triggered and recorded ** 6: No other diagnostic event alerts are implemented in the FleetRover application at this time. Malfunction Code and Description: P: Your ELD has been off for over 30 minutes in the past 24 hours. Please check your connection, and keep a paper log of your driving activity. -NOTE: If upon re-start, the ELD is still not obtaining required data sources 'Engine Synchronization Failure' alert will be sent to FMCSA. Driver will be notified, and issue will be resolved by FleetRover within 24 hours -Occurs when the ELD is not powered on while the vehicle is in motion for longer than 30 minutes during the 24 hour period. ECM data or ECM connectivity data must be captured when the engine is powered, but the ELD is not prohibited from recording information when the engine is off. E: You are not connected to your ELD due to a synchronization failure. We will resolve the issue within 24 hours, and have notified the FMCSA of our malfunction. -Occurs when an ELD loses connection to the ECM and cannot obtain any required data sources (engine power, vehicle motion, miles driven, and engine hours) for more than 30 minutes during a 24-hour period, the vehicle and ELD have been re-started to resolve the issue, and the issue is still occurring T: Your ELD is not properly synchronized with your current time zone. Please re-start the vehicle or check your connection. -NOTE: If upon re-connect, the ELD is still not obtaining required data sources Timing Compliance Failure' alert will be sent to FMCSA. Driver will be notified, and issue will be resolved by FleetRover within 24 hours -Occurs when the ELD time is not properly synchronized with Coordinated Universal Time (UTC) so that the time is inaccurate by 10 minutes or more at any time. L: Occurs when an ELD doesn’t acquire a valid position measurement within 5 miles of the vehicle’s movement during a cumulative 60-minute or greater period of 24 hours. Driver will be notified, and issue will be resolved by FleetRover within 24 hours R: Data recording to your ELD device has continuously failed. This malfunction will be noted to the FMCSA and a FleetRover representative will contact you shortly for resolution -Occurs when an ELD can no longer record or retain required data or retrieve recorded logs. R: You have not entered your location. We will notify the FMCSA of the malfunction and the non-entry -Occurs when an ELD doesn’t acquire a valid position measurement within 5 miles of the vehicle’s movement during a cumulative 60-minute or greater period over 24 hours, the driver has been asked to enter their location and has not for 24 hours S: The data transfer process has failed because your profile is missing some vital information. Please check that you are not in Unidentified Driving Mode and that timing is synchronized. -Occurs when user attempts to use the Telematics services and the attempt is unsuccessful because some necessary information is missing from the application ** O: No other malfunction event alerts are implemented in the FleetRover application at this time. This is to confirm that the FleetRover ELD has been deemed to be fully FMCSA compliant by FleetRover Inc. Thorough testing of the procedures outlined in the FMCSA-released document "Electronic Logging Device (ELD) Test Plan and Procedures" was conducted throughout the development process to ensure that the model met the technical specifications required.
ISE Fleet Services powered by eFleetSuite ANDA317 1.2.70.0A or higher ISE001 Download Download ISE Fleet Services, LLC 888-316-3533 eld-support@isefleetservices.com www.isefleetservices.com 2850 Coral Court, Suite #100, Coralville/IA/52241 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 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 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 ISE Fleet Services 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 eFleetSuite ANDA317 complies with all Federal Motor Carrier Safety Administration (FMCSA) specifications as found in 49 CFR Part 395 for Electronic Logging Devices, Subpart B.
Flex_HOS HOS_BL Ver. 4.3.7 WLI001 Download Download FlexGPS 212-660-4994 sales@flexgps.net http://www.flexgps.net 12973 SW 112 Street Suite 239, Miami, FL 33186 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. All Malfunctions (Engine synchronization, power compliance, etc.) are recorded and given the appropriate Diagnostic Code. See example below. HOS Log, For Fleet Date From 3/1/2017 12:00 AM to 3/10/2017 11:59 PM Time Back Time Event Type Location Notes 3/2/2017 03:31:14 AM Malfunction Troy, NY Code E, Description Malfunction - Engine Syncronization compliance Odometer:559800 We have tested all features according to the regulation and have tested for Failures in Communication and HW Failure as well as we have integrated remote management to provide the companies excellent remote management of the trucks for our support department to expedite any Malfunctions or Driver education that may be needed while the truck is on the road.
"EDGE MDT" IGBL-E215 v. 55 or higher IGBE61 Download Download iGlobal LLC 734-585-7878 info@igloballlc.com www.igloballlc.com 315 NE 14th Street, Ocala FL 34470 The Edge MDT 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. iGlobal LLC Quality Assurance Testers completed each test thoroughly and indicated their approvals. Secondly, Eric Bauer, Company President reviewed each test case with the IT Project Manager, Tiffany Brock, and Quality Assurance testers to ensure every test passed. Finally, Annette Sandberg from TransSafe Consulting was hired to review every test case, and she too passed every one. We have her written final report where she indicates "In December 2016, TransSafe Consulting was retained to review iGlobal LLC’s (iGlobal) certification process for Electronic Logging Devices (ELDs) as contemplated in the Federal Motor Carrier Safety Administration (FMCSA) Electronic Logging Device Regulation. This process involved going through all the testing procedures in the FMCSA Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0 released on October 17, 2016. "I conducted a majority of the review of iGlobal’s testing. All in-truck testing was conducted by Jerad Childress, Associate Attorney, Scopelitis, Garvin, Light Hanson and Feary. We found the iGlobal system tested met all the ELD requirements as contemplated in the FMCSA ELD Test Plan and Procedures, Version 2, release date October 17, 2016. A copy of her final review is on file at the iGlobal LLC offices.
Hours Of Service Android & BAFX/ELM327 1.0.1723.9940 HOS001 Download Download VisTracks, Inc. 630-596-5420 info@vistracks.com http://www.vistracks.com/ 801 Warrenville Road, Lisle, IL 60565 The 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 the 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. The 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, 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 VisTracks Hours of Service (HOS) App was certified by the VisTracks testing team through successful execution and verification of the FMCSA ELD Test Procedures. The HOS App 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 BAFX/ELM327 engine connected device. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the VisTracks HOS web application (portal) that can be accessed through a web browser.
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.
Trux ELD TRUX100 v2.0 and Higher FF55EE Download Download GeoSpace Labs 877.4.GEOWIZ david@geowiz.biz https://www.geospacelabs.com 4460 Florida National Driv,, Lakeland, FL 33813 TRUX ELDr 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 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.
ELDMANDATE (PT30) EMPT30 1.0.1723.10043 EMpt30 Download Download Bizringer Inc 800-968-1869 info@eldmandate.biz http://eldmandate.biz 1221 E. Dyer Road Suite 250, Santa Ana, CA 92705 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 a PT30 engine connected 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 a PT30 engine connected 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.
TruckRec H100 2.0 C201EX Download Download Cesiumai USA Inc. 5109289909 TruckRec@cesiumai.com http://www.cesiumai.com/us/ 925 Adams St., Albany, CA, 94706 After logging in our ELD APP, the driver is able to select “RODS” from the left main navigation bar to go to “RODS” page. Select the log of the day(s) to be sent by clicking the corresponding box(es). Click “Send” to go to “Send Log” page. Select “To FMCSA (Web Service)” or “To FMCSA (Email)” and then click “Send”. The logs of the day(s) is then sent to the authorized safety official through FMSCA web service or FMSCA designated email address accordingly. Please also refer to the User Manual for captured pictures for the pages of our ELD APP. Our ELD has the ability to detect malfunctions related to power, data synchronization, missing data, timing, positioning, data recording, data transfer, and unidentified driver records requirements. When such malfunctions occur in our ELD, we do the following or request the users to act as follows so as to resolve the data inconsistencies: 1.“Power compliance” malfunction We request the driver to keep logging into the APP or log into the APP before the vehicle’s engine is powered. When the vehicle’s engine is receiving power, our ELD shall receive data from Engine ECM and indicate the data transfer on the APP. If the driver observes there is no shown status or status request in the APP, this implies a “power compliance” malfunction and the driver shall report to the carrier’s administrator. Our system shall record this malfunction. 2.“Engine synchronization compliance” malfunction Our ELD, after installation, will record in our system once it is removed accidentally or intentionally from the interface and a notice will be provided to the driver through APP to prompt the driver to rectify. The notice will be also given to the carrier’s administrator to follow up. 3.“Timing compliance” malfunction The system clock of our ELD is structured to be cross-checked periodically with an accurate external UTC source. When it does not meet the underlying compliance requirement (although it is very unlikely to occur), our ELD shall record a timing compliance malfunction and we shall rectify immediately. No action is necessary for any carriers and drivers. 4.“Positioning compliance” malfunction Our ELD records valid position measurements normally every 10 seconds in the contiguous United States as long as the 2G mobile network is available. If the vehicle is in remote or enclosed areas which is not covered by the network, our ELD will record according to the requirements in section 4.3.1.6 and 4.6.1.4. No action is necessary for any carriers and drivers. 5.“Data recording compliance” malfunction Our ELD store the data in system which has an almost unlimited capacity and the system is structured to monitor its storage capacity itself. When it does not meet the underlying compliance requirement our ELD shall record a data recording compliance malfunction and we shall rectify immediately. We shall inform the related carriers and drivers for manual recording if necessary. 6.“Data transfer compliance” malfunction ELD records valid position measurements normally every 10 seconds in the contiguous United States as long as the 2G mobile network is available. If the vehicle is in remote or enclosed areas which is not covered by the network, our ELD will record according to the requirements in section 4.3.1.6 and 4.6.1.4. No action is necessary for any carriers and drivers. 7.“Other” ELD detected malfunction No other ELD malfunction is categorized. This is to certify that our ELD model and version, including device and software, 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. In addition, I confirm acceptance of the following rules of behavior: 1.I will not knowingly interfere with, disable, circumvent, or compromise any and all security controls, auditing, or monitoring enabled on FMCSA networks supporting ELDs. I will not knowingly introduce any malicious code into the system or the DOT network. 2.I will not share security-related information about the FMCSA information systems, software, or networks with entities outside the FMCSA unless otherwise authorized and approved in writing. I will not share any ELD-specific data, such as authentication values or private key information. 3.I will not pursue any other unspecified activities using FMCSA information systems resources that I know to be wrong, or that is patently outside the purpose of those systems in supporting FMCSA programs and the FMCSA mission. 4.I understand that violations of the above principles and practices may lead to reprimand and or civil or criminal prosecution. 5.I understand that the system is an official U.S. Federal Government web-based system and that my acceptance expressly gives assurance that I will comply with all U. S. Federal Government and Department of Transportation (DOT) regulations, policies, and procedures governing the protection, handling, processing, transmission, distribution, and destruction of sensitive unclassified information utilized by the system. I understand that I must comply with all restrictions, procedures, and processes specified in the ELD Rule.
Locus ELD ELD004 1.0.1801.11819+ ELD001 Download Download Locus GPS (888) 643-6862 info@locusgps.com www.locusgps.com 2920 Arabian PL, Marietta, GA 30062 Data Transfer The Locus 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. 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 Locus 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. Malfunctions The Locus 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 Locus 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 Locus ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The Locus 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.
Hutch ELD Mercury V 1.2.3 or higher HELD16 Download Download Hutch Systems Inc 360-353-4093 sales@hutchsystems.com http://www.hutchsystems.com 33443 Kirk Ave, Abbotsford Hutch ELD system 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, ELD 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. Hutch ELD system supports the following Malfunctions. There are 2 icons with number of malfunction and diagnostic events. Both are color coded to make it easier for the driver to distinguish. The driver is allowed to review the malfunction and diagnostic events. Supported Malfunctions: Power Compliance Engine synchronization Compliance Timing compliance Position compliance Data recording compliance Internal battery health check Cellular network connectivity check The product was tested using the ELD testing procedure developed by FMCSA. Hutch ELD has been also tested in heavy duty vehicles. The following make and model of vehicles were tested: 2015 Peterbilt 389 2014 Freightliner Cascadia 2015 Volvo VNL 670 2005 Kenworth W900 2005 Western Star
Right Trucking RTRWL01 RTRA1.0 RWLA01 Download Download Right Truck Deal LLC 314 931 0707 mmmk@stltruckers.com http://www.righttruckdeal.com 4139 West Vine Street, Unit-111 Kissimmee, Florida. 34741, St. Charles / MO / 63301 INSPECTION Right Trucking 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 Right Trucking App if you choose to provide the authorized safety official a copy. Right Trucking 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. Right Trucking 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 Right Trucking ELD. Upon completion of necessary tests outlined in the above named document we certify that Right Trucking 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.
Trackit Android 14.4.9 and newer T560NZ Download Download Command Alkon Inc. 205-879-3282 5csalesteamall@commandalkon.com http://www.commandalkon.com/ 1800 international Park Drive, Suite 400, Birmingham, AL 35243 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 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 The Trackit system complies with and is tested against the United States Department of Transportation (USDOT) Federal Motor Carrier Safety Administration (FMCSA) specifications as found in 49 CFR Part 395 for Electronic Logging Devices, Subpart B.
Omnitracs Intelligent Vehicle Gateway IVG DA038XR or later IVG001 Download Download Omnitracs, LLC 1.800.348.7227 ELD@omnitracs.com http://WWW.OMNITRACS.com 717 N Hardwood, Suite 1300, Dallas, TX 75201 A Follow these steps to transmit HOS records via Web Services or Email. 1.Tap the Day Log tab. 2. If you are still in “Inspector mode” tap on the Driver button. 3. Tap the ERODS button 4. Select Web Services or Email on the left 5. Enter a comment if requested then tap Send 6. A confirmation screen will appear. 7. If the transfer is unsuccessful, the display is a considered a compliant secondary record of duty status Omnitracs provides the driver a visual image instruction card with the screens identified and letter codes that relate to the areas of the screen the driver needs to use. Was not able to attach. Malfunctions and Diagnostics If you receive any of the following errors or malfunctions on your ELD you are required to keep paper logs until the malfunction has been corrected. * Power – An ELD must be powered and functional within one minute of the vehicle’s engine receiving power and remain powered for as long as the vehicle’s engine stays powered. * Engine Synchronization – An ELD is required to establish a link to the engine ECM and monitor its connectivity to the engine ECM and its ability to retrieve the vehicle parameters. * Timing – The ELD must cross-check its compliance with the external UTC source and must record any timing compliance malfunction. * Positioning – An ELD must monitor the availability of position measurements meeting the listed accuracy requirements and track the distance and time from the last valid measurement point. * Data Recording – 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. * Data Transfer – An ELD must implement in-service monitoring functions to verify that the data transfer mechanism(s) are continuing to function properly * Other – Any other ELD detected malfunction such as Bluetooth, relay, etc You as a driver are required to notify your carrier or administrator the malfunction as been identified on your device with in 24 hours, Omnitracs will additionally identify the issues at the host system to the administrator. Omnitracs provides the driver a visual image instruction card with the screens identified and letter codes that relate to the areas of the screen the driver needs to use. Was not able to attach. ELD Certifying Statement for: Omnitracs Intelligent Vehicle Gateway (IVG001) Omnitracs IVG001 FMCSA Certifying Statement on Product Testing for ELD Regulation Compliance Omnitracs has distributed and supported AOBRDs in the marketplace since 1989 and has developed testing processes that would assess all areas of the compliance requirements for 49CFR 395.8 and 49CFR 395.15. We have a quality assurance process that follows the creation of story cards for each section of the ELD Mandate specifications. This QA process has been standard operating procedure for Omnitracs and has increased with the ELD mandate requirements. We have used the ELD Testing document issued by FMCSA as a reference to ensure that our testing parallels or exceeds the requirements. Additionally, tests have been created that evaluate fringe cases that are not included in the FMCSA document. Omnitracs employs automated script testing processes for testing of individual elements to ensure consistent and repeatable testing as well the ability to add fringe case scenarios to ensure that in each section of the ELD Mandate, compliance is achieved. We have modified our product through variance changes in the vehicle ECM, changes by OEM and SAE standards, and maintained compliance to ensure that we are continually able to supply information from the ECM. This has ensured that we comply with all the data capture and motion detection requirements specified in the ELD Mandate for the engine ECM. Our testing process includes testing in actual CMV class 6- 8 vehicles as well as using vehicle ECM simulators in testing labs. We additionally use GPS simulators to validate recovery and diagnostics for various situations that can occur in vehicles or environments when GPS may be compromised. With this and other testing processes we are able to test each requirement for diagnostics and malfunctions as required by the ELD Mandate specifications. Additionally, we have provided to Volpe an eRODS test file requested by FMCSA and that file has been accepted. We understand that the actual eRODS transfer process has not been finalized and it will require additional testing and some modifications once all information is available from FMCSA. Omnitracs information security program is based on NIST 800-53 Revision 4. We have ensured that the specified additional security requirements referenced in the regulation for PKI, FIPS, and other NIST specifications have been achieved for compliance to support eRODS transfer.
HD 100 HD 100 iOS 6.04.03 and higher RMDT00 Download Download Rand McNally 1-800-789-6277 fleetsales@randmcnally.com http://www.randmcnally.com/category/e-logs 9855 Woods Drive , Skokie, IL 60077 The supported data transfer mechanism is Telematics using both the Email and Web Services options. The step by step instructions for a driver are - 1. Tap HOS > OPTIONS 2. 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 3. Tap YES when prompted to “Require driver portal password to exit ‘Enforcement View?’. Enter your password 4. Tap SEND LOGS TO ENFORCEMENT to send logs to law enforcement. 5. Once the inspection is finished, tap BACK, then enter your DRIVER PORTAL PASSWORD again to exit ENFORCEMENT VIEW 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.
Qv21 ELD Compliance Module Qv21ELD V2.26 TN0262 Download Download Qv21 Technologies, Inc. 855-853-7821 eld@qv21.com http://www.qv21.com 609 Castle Ridge Rd, Suite 320, Austin, TX 78746 Qv21 Technologies will use 4.9.1 (1) Option 1 - Telematics transfer methods. Transfer the electronic data using both (i) Wireless Web services, and (ii) Email, as described below: 1. Onscreen Log Inspection a. To let an official inspect the driver logs from the handset, the driver would tap on the ‘graph’ icon from the tools bar or select from the dropdown. This will bring up the driver logs. The driver would hand the handset to the safety official for inspection. 2. Driver Log Review a. A safety official can review Current, Summary (history), and Changes by selecting the desired tab to see the graphs and also by scrolling on the associated records. 3. Qv21 uses the Web services option for transferring data to the FMCSA server. a. Once the official has reviewed the logs on the handset, they can have the driver simply tap on the ‘transmit logs’ button to transfer data via Web services using a routing code provided by the safety official. Malfunction/Diagnostic Bluetooth Comms Power Power TN * 10/1000 Power TN & Power Asset Normal CAN Fail * SD Fail * GPS Fail * BT Connected BT Not Connected BT Fail * Normal Diagnostic * 400/400 duty cycle Malfunction * 750/750 duty cycle No SD card or card failure * * 800/400 duty cycle BT startup failure * * * 800/400 duty cycle Driving without login * * * * 250/250 duty cycle Firmware update started * Flashing firmware * Validating firmware * Firmware update complete * * * * 3 seconds then reboot Firmware update failed * * * * 3 seconds then reboot The company certifies the Qv21 ELD Compliance Module is compliant based on various forms of successful testing including a CMV simulator, installation and testing in an actual CMV, and the successful completion of the extensive and detailed ELD Test Plan as provided by the FMCSA.
Trimble FieldMaster Logs FML002 (TVG 850 & Samsung) v3.0 or Higher FML002 Download Download Trimble 877-728-7623 fsm_sales@trimble.com http://www.trimble.com/ 10368 Westmoor Dr, Westminster, CO 80021 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 officers 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 Trimble FieldMaster Logs application has stopped working or is not responding as expected Trimble 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 Trimble FieldMaster Logs v3 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.
Verizon Connect Reveal ELD Logbook Android - Formerly Fleetmatics Logbook XIRGO XT-6300 Series ELD 3.14.0 or higher RAXI31 Download Download Verizon Connect 844-617-1100 Logbook@verizonconnect.com https://www.verizonconnect.com 1100 Winter Street, Suite 4600, Waltham/MA/02451 Verizon Connect Reveal ELD Logbook 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: • Navigate to the Logs Sections from the Navigation bar at bottom of the Reveal ELD Logbook Mobile application • Enable Inspector Mode • Click on the download icon next to the ‘Inspector Mode’ • A pop-up appears; Driver presented with 2 options: 1. Email to logs to FMCSA or 2. Print friendly version (PDF); Select the ‘Email to logs to FMCSA’ option • Driver navigates to next screen; Select between the 2 options: 1. Email it to FMCSA 2. Web-transfer it to FMCSA • Add the routing code in the Comment field and hit the ‘Submit’ button. Note: Driver will have to enter their password to leave Inspector Mode Verizon Connect Reveal ELD Logbook supports the following malfunctions: • 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. • 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 Reveal Server timestamp and the mobile device. • 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. This statement is to certify that the Verizon Connect Reveal ELD Logbook Android application and the hardware unit (XIRGO XT-6300 Series) 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 Connect Reveal ELD Logbook 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 record, transmit and store all hours of service information according to the functional requirements as detailed in the FMCSA regulations noted above.
Chamelogs G01 1.0.95+ CELD01 Download Download Chameleon Innovation Technology 18558888353 support@chamelogs.com http://chamelogs.com 224 Melrose Ave, Monrovia/ca/91016 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.
FOCUS ELD Android & CalAmp 3640 1.0.1824.190107 LM423X Download Download Focus fleet and fuel management inc 800-670-7220 ELD@focusoptimization.com http://www.focusoptimization.com 780 West King st., Office 250, Sherbrooke, Quebec, J1H-1R7 The FOCUS 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 the FOCUS 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. Summary of Malfunctions the FOCUS 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 FOCUS 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 FOCUS ELD was certified by the VisTracks testing team through successful execution and verification of the FMCSA ELD Test Procedures. The FOCUS 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 HOS web application (portal) that can be accessed through a web browser.
Verizon Connect WorkPlan & HOS ELD - Formerly Telogis WorkPlan & HOS VT400 Workplan 4/HOS 3.3 TVT400 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 (VT400) 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.
Verizon Connect WorkPlan & HOS ELD - Formerly Telogis WorkPlan & HOS Xirgo XT6300 Series Workplan 4/HOS 3.3 TX6300 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 Mo 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 (Xirgo 6300) 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.
.ELD-Discounts LMU4230K 2.2 VB0G12 Download Download iConnect Inc. 888-353-5624 sales@eldsmartphone.com http://eldsmartphone.com/ P.O. Box 598, Westfield, Indianapolis 46074 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.
V-Series with iOn Hours - G3000 1.0.1625.6584 HOS001 Download Download CalAmp Inc (949) 600-5600 salesteam@calamp.com https://www.calamp.com/ 15635 Alton Parkway, Suite 250, Irvine, CA 92618 The V-Series with iOn Hours 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 V-Series with iOn Hours 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 V-Series with iOn Hours 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 V-Series with iOn Hours 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 V-Series with iOn Hours ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The V-Series with iOn Hours 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 V-Series with iOn Hours 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.
FleetOperate ELD JF-2017-01 1.0 KR1SHN Download Download Jackfruit Systems Inc. +1 888-849-5477 info@fleetoperate.com http://www.fleetoperate.com/ Unit#200, 421 Mulvey Ave E, Winnipeg, MB, R3L1Z8 ELD Data file transfer is supported through both email and webservices. 1. Following are the instructions to transfer ELD records through email: a.Access Inspection View, tap on the Inspection View option under hamburger Menu b. Click Email and then enter date range, your email id and optionally input your notes if applicable c. click submit to send transfer the ELD data file 2. Following are the instructions to transfer ELD records through webservice: a. Access Inspection View, tap on the Inspection View option under hamburger Menu b. Click 'Send Via Web-service' and then enter date range, and optionally input your notes if applicable c. click submit to send transfer the ELD data file 1. Following are the supported malfunctions: Engine Synchronization compliance malfunction Timing compliance malfunction Positioning compliance malfunction Data recording compliance malfunction Data transfer compliance malfunction Other ELD Malfunction 2. Following are the supported Data Diagnostic Events: Power data diagnostic event Engine synchronization data diagnostic event Missing required data element data diagnostic event Data transfer data diagnostic event Unidentified driving records data diagnostic event 1. I will not knowingly interfere with, disable, circumvent, or compromise any and all security controls, auditing, or monitoring enabled on FMCSA networks supporting ELDs. I will not knowingly introduce any malicious code into the system or the DOT network. 2. I will not share security-related information about the FMCSA information systems, software, or networks with entities outside the FMCSA unless otherwise authorized and approved in writing. I will not share any ELD-specific data, such as authentication values or private key information. 3. I will not pursue any other unspecified activities using FMCSA information systems resources that I know to be wrong, or that is patently outside the purpose of those systems in supporting FMCSA programs and the FMCSA mission. 4. I understand that violations of the above principles and practices may lead to reprimand and or civil or criminal prosecution. 5. I understand that the system is an official U.S. Federal Government web-based system and that my acceptance expressly gives assurance that I will comply with all U. S. Federal Government and Department of Transportation (DOT) regulations, policies, and procedures governing the protection, handling, processing, transmission, distribution, and destruction of sensitive unclassified information utilized by the system. I understand that I must comply with all restrictions, procedures, and processes specified in the ELD Rule.
ST20 ELD Suntech ELD 1.8 or higher SNST20 Download Download Suntech International USA Inc 760-295-5006 sales@suntechint.com http://www.suntechint.com 2598 Fortune Way, Suite I, Vista/CA/92078 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 Suntech 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 Suntech 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.
driveTIME ELD iOS & Geometris 1721.1107 or greater 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.
Vnomics ELD ELD-572 15 or later 57215A Download Download Vnomics Corp 5853779700 info@vnomicscorp.com https://www.vnomicscorp.com 175 Sullys Trail Suite 203, Pittsford NY 14534 Vnomics supports Telematics transfers. Step by Step: Press “Roadside Inspection” Press “Webservice” or “Email” Add a comment if directed by Enforcement Press “Confirm and Send Logs” Power Malfunction: ELD is running and vehicle engine is running, but no power-up event was found. It is assumed that the vehicle may have been in motion without recording events, so a Power Malfunction is set. The power malfunction is reset when the next power-up event is written. Engine Sync Malfunction: data connection to the vehicle data bus has been lost for more than 30 minutes aggregated over previous 24 hours Timing Malfunction: ELD has detected that its time is off by more than 10 minutes from actual time Positioning Malfunction: ELD has lost GPS connection when the vehicle has moved more than 5 miles. The malfunction is set if GPS has been missing for than 60 minutes over the past day. Data Recording Malfunction: ELD is unable to write new events and/or read previously recorded logs Data Transfer Unavailable: ELD has detected that the Vnomics backend cannot connect to FMCSA email or webservices. Driver is advised to use display to review logs with Enforcement. Vnomics tested this ELD against a test plan created to closely track the FMCSA-provided "Test Plan and Procedures" document, with specific details added to apply directly to Vnomics ELD software. Tests are performed by multiple testers with oversight and results are stored electronically for a historical record illustrating ELD compliance with FMCSA regulations, with traceability to the "Test Plan and Procedures" document.
Compliance Now Android & CalAmp Veosphere 1.0.1721.8683 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.
FOCUS ELD LM423X 1625.6584 or higher LM423X Download Download Focus fleet and fuel management inc 800-670-7220 ELD@focusoptimization.com http://www.focusoptimization.com 780 West King st., Office 250, Sherbrooke, Quebec, J1H-1R7 Data Transfer The FOCUS 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 FOCUS 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. Malfunctions The FOCUS 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 FOCUS 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 FOCUS ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The FOCUS 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 CalAmp 4233 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.
Rigbot RBV001 2.2 and newer RBELD1 Download Download Rigbot LLC 1844 474 4268 contactus@rigbot.com http://www.rigbot.com 316, W Washington Avenue, Suite 675, Madison WI 53703 Rigbot data transfer happens through Option1 specified by FMCSA via internet by email and data transfer to FMCSA Web services. Following is the step-by-step instructions for the driver to produce and transfer the ELD records to an authorized safety official: - 'DOT Inspection Mode' can be accessed by by tapping the main menu on top left corner of the screen - Device can be physically removed from the cradle and handed to the official with the DOT Inspection Mode screen for the officer to review on screen - As instructed by the official, 'Transfer' button can be clicked to transfer the ELD records electronically to the official - 'Transfer' button will open a window with options to either a) email or to b) transfer to FMCSA Web services - Tapping one of the two options will trigger automatic transfer of the ELD records to the authorized safety official - Above step will generate an acknowledgement indicating that the information has been sent via email per the selected option - A toaster message will indicate it, anytime the tablet is removed from the cradle - Four LED lights will indicate any ELD malfunctions including loss of GPS connectivity, loss of power to the ELD, loss of data transfer from the ELD device, and loss of internet connectivity on the physical device - In addition, driver receives an alert on the screen header - Following malfunctions with the ELD will be indicated with a ‘stop’ icon in the alert center and will require the driver to start using paper logs • P : Power Compliance malfunction • E : Engine Synchronization compliance malfunction • T : Timing Compliance malfunction • L : Positioning Compliance • R : Data recording Compliance malfunction • S : Data transfer Compliance malfunction • O : Other ELD detected malfunction - Following diagnostic codes will show in the Alert Center along with time stamp. Continued accumulation of such events will lead to the compliance malfunctions listed above • 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 Both back-office and in-vehicle tests listed in the recommended test plan have been completed and resulting ELD output files have been validated using the Validation tool provided by FMCSA
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.
PRO-ELOG PRO4230_HSPA 6.0 or higher 414230 Download Download Propel GPS, LLC 1-844-776-7354 sales@propelgps.com www.propelgps.com 11501 Sunset Hills Rd. Ste 350, Reston, VA 20190 The driver has the ability to email the log book using the driver display tablet to a requesting DOT officer directly from the driver application that has a continuous wireless internet connection via the global SPRINT wireless cellular network or by manually removing the driver display tablet from the truck as a handheld mobile device so that the DOT officer can independently review the log book. The driver display tablet also runs a continuous web services XML feed to our back-end data base that supplies our GUI with real time data so that the motor carrier home office can access information via the internet on the Propel GPS web portal. We have a fully functional web service and as soon as the FMCSA is ready to receive data transfers at roadside and provide us with the specs we will make the necessary changes to meet the requirements. Currently, the DDLs (Driver Daily Logs) can be emailed from the driver app or from Admin, if the inspection official requests them To use the electronic transfer method via email form the driver display tablet: 1. click the "email logs" tab from the View Logs Page on the driver application dashboard 2. The options are the current daily log or the last 8 days of daily logs (current day plus last 7 days) 3. enter the email address of the requesting officer and press "Send Logs" button NOTE : The subject, name of recipient and control number fields are optional The below list of malfunction events that will be detected and displayed on the driver display tablet and retained as part of the driver logs for time, date and trip associated . 1. Power malfunction 2. Engine Sync malfunction 3. Timing malfunction 4.Positioning malfunction 5.Data recording malfunction 6.Data transfer malfunction 7.Other ELD malfunctions 8.Power data diagnostic event 9.Engine Sync data diagnostic event 10. Missing transfer data diagnostic event 11 Unidentified driving records data diagnostic event 12. Other ELD identified diagnostic event Propel GPS and its authorized employee Jason M Gafa certify that our device model PRO4230 used in conjunction with our Samsung TAB_E driver dashboard meets and conforms to the ELD specifications required by the Department of Transpiration, Federal Motor Carrier Safety Administration rule. Software & hardware testing dates April 6 through June 16, 2017 Testing Procedure and specifications followed Version 2.0 Electronic Logging Device Test plan and Procedures Testing completed by Jason M. Gafa - Vice President of Sales Engineering
BIT OBD ELD for Apple BIT17002 2.1.0 BITOBD Download Download Blue Ink Tech (304) 840 0142 support@blueinktech.com https://blueinktech.com 1102 3rd Ave; Suite 401, Huntington, WV 25701 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. We have sent data exchange emails to the FMCSA email, but we are waiting on full implementation of this email endpoint (FMCSA's server is not currently sending responses). 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. This OBD-II ELD was tested on multiple medium duty vehicles from Dodge, Ford, and Chevrolet however it is unlikely to work in all medium duty vehicles because there is not a standard way of acquiring the odometer reading in ODB-II vehicles.
ELD logbook ISPP CTELD2 1713-1715 or higher 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.
TrackEnsure ELD PT30 0.0.6 and higher TE0101 Download Download TrackEnsure Incorporated 4165516300 info@trackensure.com https://www.trackensure.com 121-80 Harrison Garden Blvd, Toronto, Ontario, M2N7E3 The driver will be able to transfer the report by doing the following 1. open DOT Inspect tab in the application and will press the "Initiate Data Transfer" button on top of the screen. 2. select data transfer method "Email to FMCSA" or select "Web Service Transfer" method. 3. enter optional comment information, this can be used to enter report identifying information for the inspector 4. press the 'Send' button. The driver can also provide the printout of the report on the screen of the device to the inspector. P - Power Compliance (30 minutes in 24 hours) E - Engine Synchronization (30 minutes in 24 hours) T - Timing (Calibrate UTC - 10 minutes) L - Position (Tested every 5 miles) R - Data Recording (Specific to Field) S - Data Transfer (7 day test cycle) O - Other - Unidentified driving record (Diagnostic only) We certify that our model PT30, used in conjunction with Android platform conforms to the ELD specifications.
.ELDSmartPhone LMU4230J 2.2 VB0G11 Download Download iConnect Inc. 888-353-5624 sales@eldsmartphone.com http://eldsmartphone.com/ P.O. Box 598, Westfield, Indianapolis 46074 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.
GPSTab ELD Edition GELDN01 GELDNI1.0 GNA002 Download Download Utech Inc. 888-228-4460 sales@utechcorp.com www.utechcorp.com 2100 W. 21st Street, Broadview, IL 60155 *There is a section in uploaded manual that describes and showcases data transfer mechanism with colors and visual cues. INSPECTION GPSTab ELD Edition provides an easy way for a driver to produce and transfer the ELD records to an authorized safety official. TO PRODUCE LOGS ON THE SCREEN: 1. Tap on the Menu icon on the top left. 2. Select Inspection Module from the Menu. 3. To let an authorized safety official inspect your logs directly from your device, tap Begin Inspection. 4. Give the authorized safety official your mobile device. 5. Tap the Back arrow on the top left to exit Inspection Module. TO EMAIL OR FAX LOGS TO THE AUTHORIZED SAFETY OFFICIAL: 1. Tap Send Logs from Inspection Module screen. 2. Tap the checkbox next to each log you want to send. 3. Choose the transfer method by clicking on Email or Fax tab. 4. Enter the email address or fax number of the authorized safety official. 5. Tap Send to email 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 GPSTab ELD Edition App if you choose to provide the authorized safety official with hard copy. GPSTab – ELD Edition 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. *There is a section in uploaded manual that describes and showcases Malfunctions with colors and visual cues. How does the driver know if GPSTab ELD is malfunctioning? The GPSTab 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 UTECH support immediately after discovering a malfunction at 888-228-4460 or support@utechcorp.com 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, UTECH 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). GPSTab ELD Edition 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 GPSTab ELD Edition. Upon completion of necessary tests outlined in the above named document we certify that GPSTab ELD Edition 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
LoadTrek LX2000 3.19 LX2000 Download Download LoadTrek 8772260107 info@loadtrek.net http://www.loadtrek.net PO Box 122346, Arlington TX 76012 Instantly transfer ELD records upon demand using: 1. Telematics transfer. Wireless Web Services and EMail (SMTP) submission to a single, central email address. 2. USB2 file transfer, via port in driver terminal. In the truck the driver from the home screen by selecting "HOS". Swiping the screen back and forth advances the HOS graph/grid from day to day. 3. Additionally, motor carrier may transfer to an email address. The LX2000 has an LED that illuminates continuously during an active malfunction. Additionally, the driver display terminal shows a detailed view of ELD functions: GPS position, strength, and status; HOS ruleset/profile; engine-derived readings of speed, odometer, RPM; fault file logging; software version and update status; wide-area communications status and quality. Diagnostic Trouble Codes (DTC), known in the ELD rule as Malfunction/Diagnostic Codes: Power data diagnostic event: 1 Engine synchronization event: 2 Require Data Elements Missing data diagnostics event: 3 Data transfer data diagnostic data diagnostics event: 4 Unidentified driving records data diagnostics event: 5 "Other" ELD identified diagnostic event: 6 Power compliance malfunction: P Engine synchronization compliance malfunction: E Timing compliance malfunction: T GPS Positioning compliance malfunction: L Data recording compliance malfunction: R Data transfer compliance malfunction: S Other ELD detected malfunction: O The LoadTrek system complies with FMCSA regulations for electronic logging devices (ELDs). All system components including the onboard recording hardware, driver interface devices, communications, GPS locating systems, and administrative systems have been extensively tested under conditions of intended use. This includes the Electronic Logging Device (ELD) Test Plan and Procedures as published by FMCSA. This also includes hardware testing; 2,500,000 fleet miles All climates testing, summer and winter Focused testing, far northern and southern US climates. Software reliability testing Temperature extremes testing Moisture resistance testing Vibration testing
PosiTrace ELD System MDTGX6 1.0.0 ELD001 Download Download Global Fleet Management inc. +1 877-787-2231 gfmsupport@positrace.com https://www.positrace.com/en/about-us/contact-us 1515 Broadway St #104, Port Coquitlam, BC V3C 6M2, Port Coquitlam, British Columbia PosiTrace ELD System allows to make the initiation of the data transfer process to an authorized security officer upon request during a roadside survey in one step. Sending to USB - Connect the USB device to the tablet. - Go to the main application screen and click on "Roadside Inspection". - Select the method of sending - "USB". - Enter a comment to the report file, in the dialog that appears, and click "DONE". - Enter the driver’s password, and click "Ok" - Select from the provided USB list the device of the authorized security officer. - Press "Save" - Wait for the message of record finishing. - Remove the USB device from the tablet. Sending to Web Service FMCSA - Go to the main App screen and click on "Roadside Inspection". - Select the method of sending - "Web Service". - Enter a comment to the report file, in the dialog that appears, and click "DONE". - Wait until the data transfer to the FMCSA service is completed. Sending by Bluetooth: - Open Android settings - Enable Bluetooth support (if it was OFF) - Select in the list of available devices the device of the FMCSA officer - Enter password, which should be provided by the FMCSA officer - You should get an internet connection to send the report using the Email or Web Service described above PosiTrace ELD System is able to monitor diagnostic events and monitor the occurrence of malfunctions in accordance with the requirements described in the document ELD Test Plan and Procedures p. 4.6 Power Malfunction An ELD must set a power compliance malfunction if the power data diagnostics event 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. Engine Synchronization 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, including the unidentified driver profile. Timing Malfunction The ELD must periodically cross-check its compliance with the requirement 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. Position 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 vehicle’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. Data Recording 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. Data Transfer Malfunction (a) 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 7 days.These monitoring functions may be automatic or may involve manual steps for a driver. (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 90 consecutive monitoring checks, the ELD must detect a data transfer compliance malfunction. Certifying Statement of FMCSA Regulation Testing PosiTrace ELD System has been certified due to successful implementation and checking of FMCSA ELD testing procedures. PosiTrace ELD System was installed and tested on an MDT tablet with the Android operating system. Testing was carried out using actual vehicles by connecting to GNX-6 device using bluetooth and a wired connection. Some of the testing procedures that are relevant to the carrier have been verified using the web application https://locate.positrace.com, which can be accessed through a web browser.
TSO ELD TSO102 1621.6202 or higher TSO101 Download Download TSO MOBILE by Tracking Solutions Corp 18774772922 sales@tsomobile.com https://www.incabinplus.com/ 7791 NW 46th st Suite 306, Miami,Florida 33166 Data Transfer Description – Android Registrations The TSO 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 the TSO 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 Malfunctions The TSO 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 TSO 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 TSO ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The TSO ELD. Testing was performed through the use of a J1939 simulator and actual vehicles while having been connected to CalAmp Veosphere 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.
TND 760 TND 760 6.04.03 and higher RMDT00 Download Download Rand McNally 1-800-789-6277 fleetsales@randmcnally.com http://www.randmcnally.com/category/e-logs 9855 Woods Drive , Skokie, IL 60077 The supported data transfer mechanism is Telematics using both the Email and Web Services options. The step by step instructions for a driver are - 1. Tap HOS > OPTIONS 2. 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 3. Tap YES when prompted to “Require driver portal password to exit ‘Enforcement View?’. Enter your password 4. Tap SEND LOGS TO ENFORCEMENT to send logs to law enforcement. 5. Once the inspection is finished, tap BACK, then enter your DRIVER PORTAL PASSWORD again to exit ENFORCEMENT VIEW 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.
Astus ELD Astus & Android 1.01805.14219 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.
Hours Of Service iOS & ATrack AX7B 1.0.1816.180904 HOS001 Download Download VisTracks, Inc. 630-596-5420 info@vistracks.com http://www.vistracks.com/ 801 Warrenville Road, Lisle, IL 60565 The 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 the 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. The 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, 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 VisTracks Hours of Service (HOS) App was certified by the VisTracks testing team through successful execution and verification of the FMCSA ELD Test Procedures. The HOS App 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 ATrack AX7B engine connected device. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the VisTracks HOS web application (portal) that can be accessed through a web browser.
LoadTrek ELD ELD LX0.4.1 LT ELD Download Download LoadTrek 8772260107 info@loadtrek.net http://www.loadtrek.net PO Box 122346, Arlington TX 76012 Instantly transfer ELD records upon demand using: 1. Telematics transfer. Wireless Web Services and EMail (SMTP) submission to a single, central email address. 2. USB2 file transfer, via port in driver terminal. In the truck the driver from the home screen by selecting "HOS". Swiping the screen back and forth advances the HOS graph/grid from day to day. 3. Additionally, motor carrier may transfer to any email address. LED that illuminates continuously during an active malfunction. The driver display terminal shows a detailed view of ELD functions: GPS position, strength, and status; HOS ruleset/profile; engine-derived readings of speed, odometer, RPM; fault file logging; software version and update status; wide-area communications status and quality. Diagnostic Trouble Codes (DTC), known in the ELD rule as Malfunction/Diagnostic Codes: Power data diagnostic event: 1 Engine synchronization event: 2 Require Data Elements Missing data diagnostics event: 3 Data transfer data diagnostic data diagnostics event: 4 Unidentified driving records data diagnostics event: 5 "Other" ELD identified diagnostic event: 6 Power compliance malfunction: P Engine synchronization compliance malfunction: E Timing compliance malfunction: T GPS Positioning compliance malfunction: L Data recording compliance malfunction: R Data transfer compliance malfunction: S Other ELD detected malfunction: O The LoadTrek system complies with FMCSA regulations for electronic logging devices (ELDs). All system components including the onboard recording hardware, driver interface devices, communications, GPS locating systems, and administrative systems have been extensively tested under conditions of intended use. This includes the Electronic Logging Device (ELD) Test Plan and Procedures as published by FMCSA. This also includes hardware testing; 2,500,000 fleet miles All climates testing, summer and winter Focused testing, far northern and southern US climates. Software reliability testing Temperature extremes testing Moisture resistance testing Vibration testing
InTouch ELD - iOS IOSiX 1621.6202 or higher ITELD1 Download Download InTouch (800) 881-6343 eld@intouchgps.com http://www.InTouchGPS.com 439 S Florida Ave STE 100B, Lakeland, FL 33801 The InTouch 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. 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 InTouch 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 InTouch 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 InTouch 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. InTouch ELD was tested in compliance with the Electronic Logging Device (ELD) Test Plan and Procedures
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.
ZUS Smart Vehicle Health Monitor ZUHMBKBTV TDA66 B201_2.X.22B6 ZUSOBD Download Download Nonda +1 (408)-387-3876 ecommerce@nonda.us http://www.nonda.co No NDA Inc, 4010 Moorpark Ave. #214 San Jose, CA 95117, San Jose/CA/95117 Supported Mechanisms: Wireless Web Services, Email Instructions: Driver goes to HOS Tab >> DOT Inspection : Log Transfer Button. The driver is then prompted for transfer type (Web Services or Email), inspector's file output comments, confirm date range and submit. This product supports the following malfunctions: (1) Power compliance (2) Engine synchronization (3) Timing compliance (4) Positioning compliance (5) Data recording compliance (6) Data transfer compliance We certify that this product 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.
CarrierWeb CarrierMate MDT7000 MDT7000 4.31.50 and above CW7000 Download Download CarrierWeb LLC 404-762-1995 info.us@carrierweb.com http://www.carrierweb.com 200 Technology Ct., Suite E, Smyrna, GA, 30082 The MDT 7000 implements the Telematics option for data transfer at roadside inspection. In addition, the unit provides for a backup method of displaying ELD data when onsite communications is not possible. There are two choices, display ‘on screen’ – used if device has been installed to allow for passing out of vehicle, or ‘print’ to utilize the optional printer when device is installed in a way that does not al low for passing outside the vehicle. Additionally, the MDT5700 allows for E-Log history to be emailed or faxed to an address provided by the inspector. Telematics option – FMCSA Secure Webservice and FMCSA Secure Email: 1. Press the green ‘ELD’ button on the main menu of the MDT. 2. Press the ‘ELD’ tab at the top of the screen. 3. Press the ‘Inspect’ button on lower left bottom of the screen. 4. Choose either the option ‘FMCSA Secure Webservice’ or ‘FMCSA secure email’ as directed by inspector. 5. Touch ‘Press Here’ on the screen and enter the output file comment information as instructed by inspector. 6. Press ‘Send’ at screen bottom. Back up methods – Display on screen or print 1. Press the green ‘ELD’ button on the main menu of the MDT. 2. Press the ‘ELD’ tab at the top of the screen. 3. Press the ‘Inspect’ button on lower left bottom of the screen. 4. If passing unit out of cab – choose ‘On Screen’ from the inspection options choice screen and hand the device to roadside official. 5. Roadside official reads instructions on device regarding navigating the screen to choose days/reports and chooses ‘Next’ and reviews data. 6. If using print option – driver chooses ‘Print’ from the inspection options choice screen and hands the printed output to the roadside official. Standard Email or Fax 1. Press the green ‘ELD’ button on the main menu of the MDT. 2. Press the ‘ELD’ tab at the top of the screen. 3. Press the ‘Inspect’ button on lower left bottom of the screen. 4. Press ‘Insecure Email’ or ‘Insecure Fax’ 5. Touch ‘Press Here’ and enter the email address or fax number provided by the roadside inspector. 6. Press ‘Send’ at bottom screen. MDT Malfunctions Power Malfunction, Reason: The events in a 24 hour period. MDT has detected that it has been driven for 30 minutes without creating driving records., Solution: Check the connection to the Canbus (ECU), and check that the MDT is always powered before driving. Contact your carrier and revert to paper logs. Engine Sync Malfunction, Reason: The MDT has detected that it has missed data from the ECU for at least 30 minutes over a 24 hour period., Solution: Check the connection to the Canbus (ECU), and check that the MDT is always powered before driving. Contact your carrier and revert to paper logs. Timing Sync Malfunction, Reason: The MDT has failed to sync the clock with either the server, or GPS for too long, and it is possible that the clock may not be correct., Solution: Check the connection to the internet and GPS antenna - the malfunction should clear once a valid Fix is obtained.  Contact your carrier and revert to paper logs. Position Sync Malfunction, Reason: The MDT has been driven for too long without a GPS Fix., Solution: Check the GPS antenna - the malfunction should clear once a valid Fix is obtained. Contact your carrier and revert to paper logs. Data Recording Malfunction, Reason: The MDT cannot record any more ELD Events., Solution: An internal fault has occurred in the MDT which will need to be serviced. Contact your carrier and revert to paper logs. Data Transfer Malfunction, Reason: The MDT has failed to contact the FMCSA too many times to test the remote roadside inspection connection., Solution: Check the connection to the internet. Contact your carrier and revert to paper logs. Data Diagnostic Malfunctions Power Event, Reason: The MDT has detected that it has been driven without creating events., Solution: Check the connection to the Canbus (ECU), and check that the MDT is always powered before driving. Engine Sync Event, Reason: The MDT has detected that it is not receiving the required data from the vehicle ECU., Solution: Check the connection to the Canbus (ECU), and check that the MDT is always powered before driving. Missing Data Event, Reason: The MDT is missing required data for one or more events., Solution: Check the connection to the GPS antenna, or edit the events and add the missing data. Data Transfer Event, Reason: The MDT has failed to contact the FMCSA to test the remote roadside inspection connection., Solution: Check the connection to the internet. Unidentified Driving Event, Reason: The MDT has recorded driving when no driver was logged in., Solution: Always login before driving. You should also assuming the unidentified driving time if you are responsible for it when prompted after login. The ELD has been tested to confirm that the device meets the ELD requirements under the conditions in which the ELD will be used.
Kuktrack ELD BlueLink 3.0.6 WLI001 Download Download KUK Track SA de CV +526646346659 administracion@kuktrack.net http://www.kuktrack.com antonio@kuktrack.net, Paseo de los Heroes 10093, Tijuana Baja California 22010 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. Now that Web Services are available, we are completing the Web Services transfer method development. 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.
Gorilla Safety Compact ELD GS0002 2.1.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 Gorilla Safety Supports Web Services and Email Transfer. In order to view and transfer the date, the user can tap the documents icon on the dashboard and then present either the .pdf logs to the inspector or tap transfer, where the user can enter the code provided by the officer. 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.
Hours Of Service Android & CalAmp 4230 1621.6202 or higher HOS001 Download Download VisTracks, Inc. 630-596-5420 info@vistracks.com http://www.vistracks.com/ 801 Warrenville Road, Lisle, IL 60565 The 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 the 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. The 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, 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 VisTracks Hours of Service (HOS) App was certified by the VisTracks testing team through successful execution and verification of the FMCSA ELD Test Procedures. The HOS App 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 CalAmp 4230 engine connected device. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the VisTracks HOS web application (portal) that can be accessed through a web browser.
iPIMM™ TMS AX9-BT-iOS 3.7.3 or higher AX9IOS Download Download Procuro, Inc 858-457-8160 tgordon@procuro.com www.procuro.com 10590 W Ocean Air Drive, Suite 175, San Diego/CA/92130 All data transfers will be conducted by Telematics transfer in either supported method "web services" or "email". The iPIMM™ TMS application running on an iOS device supports the Telematics Web Services data transfer mechanism as outlined by FMCSA in the design document “ELECTRONIC LOGGING DEVICE Interface Control Document and ELD Web Services Development Handbook (Version 1.2)”. The driver/user can enter into a DOT/Roadside inspection mode with one click from the main view of the application. Inside of the inspection mode the driver has the ability for the inspecting officer to review the current day Record of Duty Status (RODS) report along with the previous 7-8 days of historical data. To electronically transfer the data the driver user will: 1. Click on the ELD Transfer icon 2. Enter an Output File Comment (if provided) 3. Select transfer type: Web Services or Email 4. Press send button, which will command the Procuro server to send the data file to FMCSA via web services or email. 5. Officer/inspector should confirm that data was transferred successfully Power Events: The ELD hardware (Atrack AX9) is configured to be powered on permanently even when the power unit/engine is shut off. An alert/event will be triggered if the device is not powered on while the power unit is powered on to comply with Power Events diagnostic events and malfunctions. Engine Events: The system is designed to collect all required ECM data on any event (power up/down, motion on/off, etc) and configured to read the ECM data on 1 minute interval in the absence of an event. If the unit is unable to collect the ECM data during any of these periods and Engine Synchronization Data diagnostic event is raised, and the unit automatically repairs the Bluetooth connection to request the data again. If the collective diagnostic events go above 30 minutes during any 24-hr period a compliance malfunction event will be recorded. Timing Events: The unit is configured to synchronize to server to maintain updated and accurate time-stamps in Coordinated Universal Time (UTC). Positioning Compliance: The ELD monitoring device (Atrack AX9) serves as the primary source of gps/location. If the gps is not available our system reverts to the backup gps/location to be collected from our iOS application (iPIMM TMS) running on Apple hardware. Data diagnostic malfunction events will be recorded when a valid position measurement is not recorded with 5 miles of the vehicle moving or 60 minutes have passed. This is unlikely since we are collecting location/gps on each ELD event and during set intervals of 1 minute. Data Recording Compliance: When a user logs into our system, after credentials are verified, the driver’s hours-of-service record and ELD event history is downloaded for the past 7 or 8 days (depending on driver’s set schedule). After historical events are downloaded all data is cached to the client and the client is responsible to locally maintain the data in the event that it cannot reach the server. A diagnostic event will occur if that initial download is not completed successfully. Missing Data Elements: The system is designed to enter all required information for each ELD event. In the event the data is missing from the ECM/system the user will be alerted to enter the fields before certifying/submitting the data to our server at the end of work day. Data Transfer Compliance: Similar setup to Data Recording Compliance. A diagnostic event will also occur when the user attempts to end the current session on the client and there are any events that have not been successfully uploaded to the server. The normal behavior the client is to send each ELD event directly to the server after it is cached locally to storage. Because GSM/cellular networks might not be available when each event occurs, the event is queued to send to the server once GSM/cellular network is available again. The system relies of ACK to know which events have been successfully uploaded to the server. Unidentified Driving Record Any driving event detect on the ELD device (Atrack AX9) without a user logged into the system will be sent to the server as an unidentified driving event. When the collective events within a 24-hour period exceed 30 minutes the event is logged as a Unidentified Driving records data diagnostic event. Visual Indicators for ELD: At all times in the UI a driver will be able to visually view the current status of the ELD system including if a data diagnostic or malfunction event is active. When any of these events occur and audible alert and pop-up display with appear for the driver on the iOS device. Under penalties of perjury, I, Thomas, John, Gordon, hereby certify on behalf of Procuro, Inc that 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.
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.
InTouch ELD - Android CalAmp 3640 1621.6202 or higher ITELD1 Download Download InTouch (800) 881-6343 eld@intouchgps.com http://www.InTouchGPS.com 439 S Florida Ave STE 100B, Lakeland, FL 33801 The InTouch 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. 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 InTouch 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 InTouch 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 InTouch 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 InTouch ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The InTouch 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 CalAmp 3640 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.
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.
ELD ONE OELD01 GELDWA1.0 OWLA01 Download Download TMS ONE 773 572 6422 info@eldone.us http://www.tmsone.us 202 Christina Dr., East Dundee, IL 60118, East Dundee / Illinois / 60118 INSPECTION ELD ONE provides an easy way for a driver to produce and transfer the ELD records to an authorized safety official. ELD ONE supports Telematics transfers including both Wireless Web and Email methods. TO EMAIL OR FAX LOGS: 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 or Fax tab. 4. Enter the email address or fax number of the authorized safety official. 5. Tap “Send” to email your logs. TO SUBMIT OUTPUT FILE THROUGH WIRELESS WEB SERVICE: 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. ELD ONE 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, ELD ONE 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 ELD ONE. Upon completion of necessary tests outlined in the above named document we certify that ELD ONE 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.
GFI eLogs Calamp 4230 and Calamp 3030 1.0.1805.0315 GFI001 Download Download GFI Systems Inc. 1-855-434-4477 eld@gfisystems.ca http://www.gfisystems.ca 500 10709 Jasper Ave., Edmonton, Alberta The GFI eLogs 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 GFI eLogs 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 GFI eLogs 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 GFI eLogs 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 GFI eLogs ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The GFI eLogs 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 CalAmp 4230 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.
BridgeHaul ELD Bluelink 2.1.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.
Geotab GO Device - J. J. Keller Android BYOD and Compliance Tablet G7A Version 3 and higher G7A003 Download Download J. J. Keller & Associates, Inc. 800-327-1342 support@jjkeller.com www.jjkeller.com/elogs 3003 Breezewood Lane, Neenah, WI 54957 The J. J. Keller solution follows the "Telematics" approach. The ELD is capable of transferring data via email and web service. When choosing the Roadside Inspection icon from the Dashboard, drivers are presented with two options. The first allows the driver to send an output file (Data Transfer) to the roadside inspection official. The second (Roadside Inspection Mode) allows the official to review the necessary hours of service information on the mobile device. To perform the data transfer, the driver selects the "Data Transfer" option and then chooses the method (email or web service). The driver is able to enter a comment and will then receive a confirmation of the transfer success. To show the ELD data via display, the driver selects "Roadside Inspection Mode." All ELD data is available onscreen and includes the required header, graph grid, event detail, and unassigned events. These are the malfunction codes (7 codes): Code - Malfunction Description P - “Power Compliance” Malfunction – indicates that the ECM, its onboard sensors and data record history has identified that the ELD may not have complied with power requirement, and has caused an understatement of 30 minutes or more has elapsed over a 24-hr period. E - “Engine Synchronization Compliance” malfunction – indicates connectivity to any of the required data sources is lost for more than 30 min during a 24-hr period. T - “Timing Compliance” Malfunction – indicates that the ELD can no longer meet the requirement to cross-check it’s time to an accurate external UTC Source. L - “Positioning Compliance” Malfunction – indicates that the ELD fails to acquire a valid position measurement within 5 miles of the CMV’s movement and the elapsed time exceeds a cumulative 60 min over a 24-hr period. R - “Data Recording Compliance” Malfunction – indicates that the ELD 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 – indicates that the ELD’s monitoring of the data transfer mechanism has failed for three consecutive monitoring checks (each occurring at least once every 24-hr period). O - “Other” ELD detected malfunction – ELD provider-specific malfunction values to communicate the ELD’s malfunction or non-compliant state to the operator. These are the Data Diagnostic codes (6 codes): Code - Data Diagnostic Event 1 - “Power data diagnostic” event – indicates that the ELD may not have complied with the power requirements. 2 - “Engine synchronization data diagnostic” event – occurs when connectivity to required data sources is lost and the ELD can no longer acquire updated values for the ELD parameters with 5 seconds of the need. 3 - “Missing required data elements data diagnostic” event – occurs when the ELD event record information is deficient in relation to the required data elements for each event type. 4 - “Data transfer data diagnostic” event – occurs when the ELD fails to confirm proper in-service operation of the data transfer mechanism (this check is performed at least once every 7 days). 5 - “Unidentified driving records data diagnostic” event – occurs when more than 30 min of driving in a 24hr period show the ‘unidentified driver’ on the ELD. This event triggers an indicator that is then turn on for all drivers logged into that ELD for the current 24-hr period and the following 7 days. 6 - “Other” ELD identified diagnostic event – ELD provider-specific data diagnostic values to communicate the ELD’s malfunction or non-compliant state to the operator We created a suite of both manual and automated tests, based on each of the individual regulations and the testing procedures document, and executed them both at our testing benches and in vehicles.
E-Log Plus iOSI ELP-iOSI100 1.0.1805.180731 ELP040 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.
Astus ELD Astus & iOS 1.0.1805.180723 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.
ELDMANDATE (Android ELM327) LBT26017 1.0.1719.8478 EMpt30 Download Download Bizringer Inc 800-968-1869 info@eldmandate.biz http://eldmandate.biz 1221 E. Dyer Road Suite 250, Santa Ana, CA 92705 The LB Technology 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 LB Technology 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 LB Technology's 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 LB Technology 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. The LB Technology ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The LB Technology 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 a ELM327 engine connected 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.
Connect ELD by Gorilla Safety MAX 01 MAX GSMAX1 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 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.
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.
"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 10401 CEDAR LAKE RD UNIT 212, MINNETONKA, MN 55305 "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.
DT4000 REV 5 6.01.04 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 valid email address, 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.
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.
ELD365 ELD386 2.1.399 ATS001 Download Download JAMES TSENG 18888581928 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.
Hours Of Service iOS & Atlas 1.0.1801.11819 HOS001 Download Download VisTracks, Inc. 630-596-5420 info@vistracks.com http://www.vistracks.com/ 801 Warrenville Road, Lisle, IL 60565 The 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 the 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. The 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, 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 VisTracks Hours of Service (HOS) App was certified by the VisTracks testing team through successful execution and verification of the FMCSA ELD Test Procedures. The HOS App 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 Atlas engine connected device. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the VisTracks HOS web application (portal) that can be accessed through a web browser.
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 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 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, 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 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 FleetLink 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 FleetLink 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 FleetLink ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The FleetLink 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.
NexTraq ELD Android 1.0 and above 1.0.1625.6584 HOS001 Download Download NexTraq 800-358-6178 Eldsupport@nextraq.com http://nextraq.com 1200 Lake Hearn Dr NE, Suite 500, Atlanta, GA, 30319 The NexTraq 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 the NexTraq 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. Summary of Malfunctions The NexTraq ELDELD is capable of monitoring its compliance for various detectable malfunctions. At each instance when an ELD malfunction event is detected or cleared by the NexTraq 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 NexTraq ELD was certified by the NexTraq testing team through successful execution and verification of the FMCSA ELD Test Procedures. The NexTraq 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 CalAmp 3640 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.
TXT E Solutions Inc. ELD TXTELD-5 5.0 M17V84 Download Download TXT Esolutions Inc. 1-833-TXT-ELOG sales@txtesolutions.com http://txtesolutions.com 1450 Meyerside Drive, Suite 601, Mississauga/Ontario/L5T 2N5 The Data is transferred from the ECM of the Commercial Motor Vehicle to our ELD device in the following methods: 1. Wifi - Our Device is equipped with high quality WIFI - Hotspot. The Device can communicate with any WIFI capable device such as Cellular or other Wifi Capable Device such as Tablets mounted on to the dash-board of the Commercial Motor Vehicle. The Data is then registered onto the memory of the data receiving device by way of our mobile APP/ website ; 2. Stable 2G/3G network- Each of our device is built to support a 2G/3G SIM Card. The 2G/3G data connects and transmits the data to our AWS Server by way of Socket Server Code, and thereby registering the data onto our SQL Server database, located on the Cloud and hosted at AWS Hosted Server Facilities. Each user will be able to retrieve the data registered onto the data base through web portal and/or through a Mobile APP. 3. The data is stored on to the physical hard drive of our ELD device. The ELD Device has an internal memory of 25 MB, sufficient to store 14 days worth of ELOG data. 1. A “Data Recording Compliance Malfunction” notification is pushed to mobile application upon a loss connection. 2. A “Timing” malfunction detection notification is pushed when, the ELD fails to synchronize with Coordinated Universal Time (UTC) in each 5-minute interval. 3. A “Power Data Diagnostic Events” notification is pushed to mobile application, when an ELD is not powered and fully functional within one minute of the vehicle’s engine receiving power and does not remain powered for as long as the vehicle’s engine stays powered. 4. A “Power Compliance Malfunctions” a notification is pushed to mobile application, when an 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. 5. A “Position Compliance Malfunction” a notification is pushed to mobile application when an ELD fails to acquire a valid position measurement within 5 miles of the commercial motor vehicle moving and 60 minutes has passed. 6. A “Data Transfer and/or Data Diagnostic Event” a notification is pushed to mobile application when the operation of the data transfer mechanism(s) is not confirmed. 7. A “Data Transfer Compliance” is a notification is pushed to mobile application, when a malfunction occurs when the ELD stays in the unconfirmed data transfer mode following the next three consecutive monitoring checks. 8. An “Unidentified Driving Records Data Diagnostic Event” a notification is pushed to mobile application, when more than 30 minutes of driving time for an unidentified driver is recorded within a 24-hour period. Under penalties of perjury, I, Prince Saini, hereby certify on behalf of TXT Esolutions Inc. that ELD model 5.0 and version 5.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.
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.
DriverConnect DC 700 Android 5.4 RMDC00 Download Download Rand McNally 1-800-789-6277 fleetsales@randmcnally.com http://www.randmcnally.com/category/e-logs 9855 Woods Drive , Skokie, IL 60077 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.
FleetUp 3G 1.0.0 AAAAAA Download Download FleetUp 855-274-2886 hello@fleetup.com www.fleetup.com 500 Yosemite Dr., Suite 120, Milpitas/CA/95035 a a a
Logbooks ELD100 1.0.0 PLS100 Download Download 2701545 Canada Inc. 0000000000 notpublic@example.com http://example.com 312-300 Rue de la Berge du Canal, Lachine, QC, H8R 1H3 Method 1: Bluetooth File Transfer 1. Click on the Share button (top-right) on the home screen. 2. Select the Bluetooth option, then press the Send button. 3. Choose from the available Bluetooth devices which are nearby. Selecting the device in the list immediately starts the file transfer to the recipient. Method 2: Email File Transfer 1. Click on the Share button (top-right) on the home screen. 2. Select the Email option, then press the Send button. 3. Type in the recipient's email address, then press the Send button to finalize the transfer. Method 3: USB File Transfer 1. The Safety Officer / Roadside Inspector will provide a USB flash drive ("USB key") to the driver. 2. Plug in the USB flash drive to the ELD (tablet) first. 3. Click on the Share button (top-right) on the home screen. 4. Select the USB Drive file transfer option and then press the Send button. The ELD is capable of self-monitoring the following required functions: Power, Engine synchronization, Timing, Positioning, Data Recording and Data Transfer (all functions listed in chapter 4.6 in the testing guide). The ELD also has Visual Malfunction and Data Diagnostic Indicators as outlined in chapters 4.6.2.1 and 4.6.3.1. Data Transfer Malfunctions are checked three (3) times in a 24 hour period. The ELD was rigorously tested to comply with FMCSA regulations. The document "ELD Test Plan and Procedures" by the FMCSA was followed very carefully, and all testing procedures (in all 3 chapters) were carried out and documented accordingly. Several internal "pilot" cases were carried out with select drivers to ensure the ELDs function as designed and to meet all required FMCSA guidelines.
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.
V-Track V-HOS1 1.0.15 VSAND1 Download Download Velocitor Solutions 7047315388 sales@velsol.com http://www.vtrackfm.com 851 Blairhill Rd, Charlotte/NC/28217 Electronic Transfer supported via Web Service and Email. Tap on DOT Inspection Mode. Choose Email or Web Service. Enter File Comment if necessary. Tap Send. Power Compliance, Engine Synchronization Compliance, Time Compliance, Positioning Compliance, Data Recording Compliance, Data Transfer Compliance. I certify after extensive testing that V-Track complies with the rules set within FMCSA's requirements for ELD.
FOCUS ELD Android & GNX-6 1.0.1805.14593 LM423X Download Download Focus fleet and fuel management inc 800-670-7220 ELD@focusoptimization.com http://www.focusoptimization.com 780 West King st., Office 250, Sherbrooke, Quebec, J1H-1R7 The FOCUS 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 the FOCUS 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. Summary of Malfunctions the FOCUS 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 FOCUS 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 FOCUS ELD was certified by the VisTracks testing team through successful execution and verification of the FMCSA ELD Test Procedures. The FOCUS 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 HOS web application (portal) that can be accessed through a web browser.
CyntrX ELD Pro Geometris and Android 1.0.1805.14019 & up FlexCX Download Download CyntrX 9203380479 compliance@cyntrx.com http://www.cyntrx.com 1302 South Broadway, De Pere, WI, 54115 The CyntrX ELD Pro 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 CyntrX ELD Pro 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 CyntrX ELD Pro 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 CyntrX ELD Pro 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 CyntrX ELD Pro ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The CyntrX ELD Pro 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.
Omnitracs Mobile Computing Platform 200 AA1654R or Later MCP200 Download Download Omnitracs, LLC 1.800.348.7227 ELD@omnitracs.com http://WWW.OMNITRACS.com 717 N Hardwood, Suite 1300, Dallas, TX 75201 © 2017 Omnitracs, LLC 717 N. Harwood Street, Suite 1300 Dallas, TX 75201 U.S.A. All rights reserved. DCN: 80-JA402-1 Rev. A Follow these steps to transmit HOS records via Web Services or Email. 1. Tap the Day Log tab. (D) 2. If you are still in “Inspector mode” tap on the Driver button (B). 3. Tap the ERODS button (C). 4. Select Web Services or Email on the left (D). 5. Enter a comment if requested then tap Send (E). 6. A confirmation screen will appear. 7. If the transfer is unsuccessful, the display is a considered a compliant secondary record of duty status Malfunctions and Diagnostics If you receive any of the following errors or malfunctions on your ELD you are required to keep paper logs until the malfunction has been corrected. Omnitracs, LLC 717 N. Harwood Street, Suite 1300 Dallas, TX 75201 U.S.A September 2017 FMCSA Registration ID: xxxxxx ELD ID: MCP200 Copyright © 2017 Omnitracs, LLC. All rights reserved. Omnitracs is a trademark of Omnitracs, LLC. All other trademarks are the property of their respective owners. Omnitracs endeavors to ensure that the information in this document is correct and fairly stated, but Omnitracs is not liable for any errors or omissions. Published information may not be up to date, and it is important to confirm current status with Omnitracs. This technical data may be subject to U.S. and international export, re-export or transfer (export) laws. Diversion contrary to U.S. and international law is strictly prohibited. * Power – An ELD must be powered and functional within one minute of the vehicle’s engine receiving power and remain powered for as long as the vehicle’s engine stays powered. * Engine Synchronization – An ELD is required to establish a link to the engine ECM and monitor its connectivity to the engine ECM and its ability to retrieve the vehicle parameters. * Timing – The ELD must cross-check its compliance with the external UTC source and must record any timing compliance malfunction. * Positioning – An ELD must monitor the availability of position measurements meeting the listed accuracy requirements and track the distance and time from the last valid measurement point. * Data Recording – 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. * Data Transfer – An ELD must implement in-service monitoring functions to verify that the data transfer mechanism(s) are continuing to function properly * Other – Any other ELD detected malfunction such as Bluetooth, relay, etc. Omnitracs MCP200 FMCSA Certifying Statement on Product Testing for ELD Regulation Compliance Omnitracs has distributed and supported AOBRDs in the marketplace since 1989 and has developed testing processes that would assess all areas of the compliance requirements for 49CFR 395.8 and 49CFR 395.15. We have a quality assurance process that follows the creation of story cards for each section of the ELD Mandate specifications. This QA process has been standard operating procedure for Omnitracs and has increased with the ELD mandate requirements. We have used the ELD Testing document issued by FMCSA as a reference to ensure that our testing parallels or exceeds the requirements. Additionally, tests have been created that evaluate fringe cases that are not included in the FMCSA document. Omnitracs employs automated script testing processes for testing of individual elements to ensure consistent and repeatable testing as well the ability to add fringe case scenarios to ensure that in each section of the ELD Mandate, compliance is achieved. We have modified our product through variance changes in the vehicle ECM, changes by OEM and SAE standards, and maintained compliance to ensure that we are continually able to supply information from the ECM. This has ensured that we comply with all the data capture and motion detection requirements specified in the ELD Mandate for the engine ECM. Our testing process includes testing in actual CMV class 6- 8 vehicles as well as using vehicle ECM simulators in testing labs. We additionally use GPS simulators to validate recovery and diagnostics for various situations that can occur in vehicles or environments when GPS may be compromised. With this and other testing processes we are able to test each requirement for diagnostics and malfunctions as required by the ELD Mandate specifications. Additionally, we have provided to Volpe an eRODS test file requested by FMCSA and that file has been accepted. We understand that the actual eRODS transfer process has not been finalized and it will require additional testing and some modifications once all information is available from FMCSA. Omnitracs information security program is based on NIST 800-53 Revision 4. We have ensured that the specified additional security requirements referenced in the regulation for PKI, FIPS, and other NIST specifications have been achieved for compliance to support eRODS transfer.
FleetWaze eLog SRS01 1.0.1625.6584 SRS413 Download Download SRS Technologies, LLC 855-663-2833 info@srstllc.com http://fleetwaze.com 28175 Haggerty Road, Novi, MI 48377 Data Transfer The FleetWaze eLog app 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 FleetWaze eLog app 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 FleetWaze eLog 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 FleetWaze eLog 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 FleetWaze eLog ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The FleetWaze eLog 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, CalAmp 4230 and Pacific Track 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.
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.
Ashavi Global ASHT01 1.0 ASHAV1 Download Download Ashavi Global 18006761244 cs@ashaiglobal.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.
Swiss Log VNA-ELD2 1.10 IMVNA2 Download Download IIMSWISS CORP. 4166138011 info@iimswiss.com https://iimswiss.com #20, 7001 Steeles Ave. W, , Toronto, ON, M9W 0A2 1. Tap on inspection mode. 2. In the resulting window tap on Export 3. Select desired export type and tap on OK Export types are: USB, Email and Web Service. SwissLog is monitors itself to keep it in compliance for various detectable malfunctions. When a malfunction is detected then code of the malfunction appears on the status bar. 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 When a malfunction icon is displayed on screen then user can tap on the icon and then tap on 'Clear' to clear malfunction. SwissLog was thoroughly tested on various models and makes of trucks using J1939 and J1708 protocols. Test procedures and results were verified from web portal.
Ingtech Delta Delta001 1.0 and higher DELTA1 Download Download INGTECH 5148163555 sales@ingtech.com http://www.ingtechdelta.com 3310 100e ave, suite 310, Laval/Québec/H7T0J7 This product supports Web Services and email services as mean of Data Transfer. Step-by-step instruction: 1. Login on the app on the tablet with a valid driver account; 2. Show HOS page by clicking on the driver’s name on the top of the page; 3. Click on “INSPECTION”; 4. Drag the page to the bottom and add comments; 5. Select “Send to Web Service” or "Send by Email" depending on the preferred mean of transfer. All compliance malfunctions are listed in the User Manual as required in the ruling 1. Power Compliance Monitoring 2. Engine Synchronization Compliance Monitoring 3. Timing Compliance Monitoring 4. Positioning Compliance Monitoring 5. Data Recording Compliance Monitoring 6. Data Transfer Compliance Monitoring The user manual contains a brief description of each type of malfunction and the actions to be taken. No additional malfunctions are using the malfunction status indicator of the ELD device. All tests have been performed in accordance to the ELD Test Plan and Procedures V2.0 to comply with FMCSA regulations.
PeopleNet Mobile Gateway - eDriver Logs ELD (for WinCE) PMG002 .19xxx or higher PMG002 Download Download PeopleNet 888-346-3486 info@peoplenetonline.com www.peoplenetonline.com 4400 Baker Road, Minnetonka, MN 55343 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”. User is able to type in the white dialog box for a reference information that will be sent with the file. Select either Email or Web Service once your selection is made the Done button will become active. Tap Done to send the file. 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 eDriver Logs ELD application has stopped working or is not responding as expected. PeopleNet 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 PMG002 and complies with all Federal Motor Carrier Safety Administration (FMCSA) specifications as found in 49 CFR Part 395 for Electronic Logging Devices, Subpart B.
Forward Thinking Systems - Field Warrior ELD (BYOD) FW-BYOD 3.0.0 or Higher FTSFW1 Download Download Forward Thinking Systems LLC 866-221-1864 eld@ftsgps.com https://www.ftsgps.com 575 Jericho Turnpike, Suite 301, Jericho / NY / 11753 We use web services and email for the telematics transfer options. Step-by-step instructions for the driver: - From the main ELD screen, tap on the “Export Logs” icon. - You will then be prompted to choose web services or email as the transfer method. - After choosing a transfer method, you will be prompted to enter a output file comment. - Tap the “Export” button, and the data transfer will be completed. Field Warrior® monitors its own compliance with ELD regulations. If a malfunction is detected, the app will notify the user by displaying an alert. The malfunction will also be logged in the ELD Malfunction Log that will be visible upon inspection. To see any malfunctions, open the menu drawer and select Alerts & Notifications. Malfunctions are also visible in Inspection Mode, which displays all event logs including malfunction events. Power Malfunction If Field Warrior® loses power or is disconnected from the vehicle, a warning message is displayed noting that the ELD is no longer being powered by the vehicle, and a malfunction event is logged. Engine Synchronization Malfunction If Field Warrior® detects a problem retrieving information from the vehicle’s ECU or detects a loss in ECU connectivity, a warning message is displayed and the event is logged. Timing Malfunction Field Warrior® periodically checks an external source for the current time to keep accurate logs. If the ELD is unable to get the current time from an outside source, a timing compliance malfunction is logged. Positioning Malfunction If Field Warrior® 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. Data Recording Malfunction Field Warrior® stores data locally and also sends driver data to be stored remotely. A data recording malfunction event is logged and a warning is displayed if a data malfunction is detected, a local database error occurs, or the device is unable to download the remotely stored logs. Data Transfer Malfunction If Field Warrior® 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. Other Malfunctions If Field Warrior® detects some other malfunction such as a hardware/software error, malfunction, or crash, it will log the event as Other Malfunction. We certify that Forward Thinking Systems LLC (a) develops the referenced Product in accordance with the requirements of 49 CFR 395 subpart B; and (b) performs the tests specified Electronic Logging Device (ELD) Test Plan and Procedures dated October 17, 2016, Version 2.0, which are promulgated by the U.S. Department of Transportation, Federal Motor Carrier Safety Administration, to test compliance with FMCSA regulations.
Inthinc Connect Pro400 7.8 PRO400 Download Download Orbcomm 1-866-294-8637 support@inthinc.com http://inthinc.com 341 S Main St, Salt Lake City, UT, 84103 Inthinc Connect offers USB, Bluetooth and Email File Transfer Options The user will use the one touch button located on the ELD dashboard to open the Transfer option bar. The transfer option bar will let the driver touch the transfer option they wish to use. To initiate USB transfer the driver selects the USB option a window will open for the drier to add a comment. The driver then chooses export and the ELD output file will export to the attached usb device. To initiate a Bluetooth transfer the driver makes the Bluetooth connection to the officers device . The driver then selects the Bluetooth transfer option on the transfer option bar. A comment window will pop up for the driver to add a comment. The driver then selects export an the ELD output file will be made to the attached bluetooth device. To initiate email transfer the driver will select the email transfer option a comment box will pop up for the driver to add a comment . The then selects export and the ELD output file will be sent to fmcsaeldsub@dot.gov Malfunction List DIAG_POWER = '1'; DIAG_ENGINE = '2'; DIAG_MISSING = '3'; DIAG_TRANSFER = '4'; DIAG_UNIDENTIFIED = '5'; DIAG_OTHER = '6'; MALFUNC_POWER = 'P'; MALFUNC_ENGINE = 'E'; MALFUNC_TIMING = 'T'; MALFUNC_POSITION = 'L'; MALFUNC_RECORDING = 'R'; MALFUNC_TRANSFER = 'S'; MALFUNC_OTHER = 'O'; These are the ones we ARE checking for, and reporting: DIAG_ENGINE DIAG_MISSING DIAG_UNIDENTIFIED MALFUNC_POSITION MALFUNC_ENGINE Test cases were created from each item in the ELD Mandate to verify compliance. Test cases included validation against the FLMCSA provided files and tools including the online file validation tool. During development these test cases were used to validate compliance. This ensured items were implemented correctly and not missed. These test cases became our regression tests which were used during the final test phase before releasing to production.
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.
SIMPLETRUCKELD STEELDV15.1.0.19 1.0.19 STEELD Download Download SimpleTruckELD INC 224 248 8651 info@simpletruckeld.com www.simpletruckeld.com 3701, Algonquin Road, , Rolling Meadows/Illonois/60008 We simpletruckeld Supports two type of data transfer mechanism. 1)Wireless Web services 2)Email Wireless Web services : 1)Simpletruckeld convert ELD files into an XML using FMCSA provided files. 2)Simpletruckeld Generate XML files to the driver for Last 7 days+ current day. 3)Simpletruckeld supports upload the data(XML file) into the FMCSA. Wireless data transfer through E-Mail : We simpletruckeld give an Instruction for a driver to produce and transfer the ELD records: Simpletruckeld provides to create CSV File FMCSA: 1. Simpletruckeld 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. Simpletruckeld 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. SimpletruckELD 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 is any issues while connect 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 is any issues from latitude, longitude co-ordinates, we have recorded event log with positioning compliance malfunction. Data recording compliance malfunction – If there is any issues while getting vehicle data's like(VIN number,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's 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. Testing procedures: 1. Accounts, Inputs, and Vehicle Interface 2. Processing, Monitoring and Recording 3. Outputs and Data Transfer On these heads as per the FMCSA procedure test has been conducted.
NexTraq ELD iOS 1.0 and above 1.0.1625.6584 HOS001 Download Download NexTraq 800-358-6178 Eldsupport@nextraq.com http://nextraq.com 1200 Lake Hearn Dr NE, Suite 500, Atlanta, GA, 30319 The NexTraq 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 the NexTraq 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. The NexTraq ELDELD is capable of monitoring its compliance for various detectable malfunctions. At each instance when an ELD malfunction event is detected or cleared by the NexTraq 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 NexTraq ELD was certified by the NexTraq testing team through successful execution and verification of the FMCSA ELD Test Procedures. The NexTraq 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 CalAmp 3640 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.
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.
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..
Load Logistics TMS LOGI-APPS 1.35 or higher LLSAPP Download Download Support Resources,Inc. 770-702-0701 contactus@load-logistics.com www.load-logistics.com 3330 Cobb Pkwy. / Suite 17-H, Acworth / Ga / 30101 Apps have the capability to transfer required information. Additionally, the server systems have the capability to transfer required files/documents. Please refer to the User's Manual for instructions regarding file transfers. Malfunctions are communicated in "real-time" to the server and forwarded to the designated individuals. Testing for the ELD has been performed over many months using "live" environments. The recent new requirements have also been tested in actual vehicles.
Linxup ELD AGLX01 1.4.72 or higher AGLX01 Download Download Agilis Systems 314 732 4925 Option 1 for Sales sales@agilissystems.com http://www.agilissystems.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 Linxup 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 Linxup-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 AGLX01 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.
MapAnything ELD MapAnything 1.0 and Above MAELD1 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.
MapAnything ELD Lite com.mapanything.eldlite 1.0.1625.6584 HOS001 Download Download MapAnything ELD Lite (866) 547-8016 support@mapanything.com https://mapanything.com/products/mapanything-live/eld 5200 77 Centre, Suite 400, Charlotte/NC/28217 Data Transfer Description – iOS MapAnything ELD Lite 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 MapAnything ELD Lite 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 MapAnything ELD Lite is capable of monitoring its compliance for various detectable malfunctions. At each instance when an ELD malfunction event is detected or cleared by the MapAnything ELD Lite, 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- MapAnything ELD Lite was certified through successful execution and verification of the FMCSA ELD Test Procedures. MapAnything ELD Lite 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 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.
Apollo ELD (e-Dash) Apollo 1.0.28 or higher APOLLO Download Download Apollo ELD 305-971-6777 eldinfo@apolloeld.com http://www.apolloeld.com 8230 Coral Way, Miami FL 33155 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.
BIT ELD for Apple BIT17001 1.5.7 or higher BITELD Download Download Blue Ink Tech (304) 840 0142 support@blueinktech.com https://blueinktech.com 1102 3rd Ave; Suite 401, Huntington, WV 25701 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. We have sent data exchange emails to the FMCSA email, but we are waiting on full implementation of this email endpoint (FMCSA's server is not currently sending responses). 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. Full compliance will have to be re-confirmed after FMCSA has their email account for data transfer set up and returning responses.
ThinAir ELD Android & Geometris 1.0.1719 or higher TTHOS1 Download Download ThinAir Telematics LLC 1-888-285-8780 sales@thinair.co http://www.thinair.co 5773 Woodway Dr. #100, Houston, Texas 77057 The ThinAir 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 ThinAir 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 ThinAir 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 ThinAir 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. ThinAir ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The ThinAir 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 the following engine connected devices: Geometris, Digi WVA, CalAmp 4230, Pacific Track. 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 1713-1715 or higher 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.
TrackEnsure ELD PT30 1.2 or higher TE0101 Download Download TrackEnsure Incorporated 4165516300 info@trackensure.com https://www.trackensure.com 121-80 Harrison Garden Blvd, Toronto, Ontario, M2N7E3 The driver will be able to transfer the report by doing the following 1. open DOT Inspect tab in the application and will press the "Initiate Data Transfer" button on top of the screen. 2. select data transfer method "Email to FMCSA" or select "Web Service Transfer" method. 3. enter optional comment information, this can be used to enter report identifying information for the inspector 4. press the 'Send' button. The driver can also provide the printout of the report on the screen of the device to the inspector. P - Power Compliance (30 minutes in 24 hours) E - Engine Synchronization (30 minutes in 24 hours) T - Timing (Calibrate UTC - 10 minutes) L - Position (Tested every 5 miles) R - Data Recording (Specific to Field) S - Data Transfer (7 day test cycle) O - Other - Unidentified driving record (Diagnostic only) We certify that our model PT30, used in conjunction with iOS platform conforms to the ELD specifications.
SP Logbook VTSSPLB 1.0 or higher SPLB01 Download Download Vehicle Tracking Solutions 1-800-671-5222 Contact@VehicleTracking.com https://vehicletracking.com/ 152 Veterans Memorial Highway, Commack/NY/11725 Inside Silent Passenger Logbook the driver can load inspection mode to present to an officer at the time of a roadside inspection. Silent Passenger Logbook stores the 7 past days of history plus todays current data. To start inspection mode: 1) log in to Silent Passenger Logbook 2) Provide your 4 digit driver PIN 3) At the Dashboard you will see a “Generate Report” button. 4) Click “Generate Report” you will then be provided with 3 options a. Inspection Mode- this will lock down the tablet to provide the last 7 days plus todays current data, for the roadside inspection. b. Send Via Email- This allows you to enter an email address to send the last 7 days plus todays current data via email c. Submit Via Internet- This will upload the last 7 days plus todays current data to the Federal Motor Carrier Safety Association 5) Click Inspection Mode 6) Inside Inspection Mode the driver will be able to provide the device at this point to the officer. a. The officer will be able to send via email to email the last 7 days + todays data to himself for further review. b. They can use the arrows to go back and forth between days or pick a date to review the data. 7) To exit Inspection Mode click the back arrow on the top left corner. a. You will be requested to put in your 4 digit driver pin Standard Coding for Required Compliance Malfunction and Data Diagnostic Event Detection 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 O “Other” ELD detected malfunction 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 SP Logbook was tested by hundreds of users for 18 months using the final rule provided by the FMCSA to conduct test procedures on all aspects of the ruling - https://www.fmcsa.dot.gov/sites/fmcsa.dot.gov/files/docs/FMCSA-ELD-Final-Rule_12-10-2015.pdf
FleetUp 3GL 1.0 or higher TLT3GL Download Download FleetUp 855-274-2886 hello@fleetup.com www.fleetup.com 500 Yosemite Dr., Suite 120, Milpitas/CA/95035 Open the FleetUP HOS application and sign in. Locate the Logs Tab and go to the RODS page. After driver signs his or her report from the mobile application directly, the driver can use the save button on the top left corner to export data into a PDF file. Once a driver signs his or her report, the report cannot be altered or edited. The driver can send the PDF to an authorized safety official. On the FleetUP HOS application, a malfunction will occur if there is no data being recorded. 3GL will show that there is no data being recorded. Driver managers must then contact FleetUP Support for a repair or an exchange and it will be processed within the next 8 days. There are three indicators on 3GL. Power GSM network, and GPS communication. *Power Status Solid On = Connected with the engine and Reading protocol/engine data, Solid Off = Not reading engine data. (Tracker Mode), Blinking = Searching for engine data *GSM Network Status Solid On = Connected to GSM Network Solid Off = Not connected to GSM network. Blinking Fast = Searching for network/No SIM card Blinking Slow = connecting to GSM Network. *GPS Communication Status Solid On = Successful GPS Communication Solid Off = No GPS Communication Blinking = Trying to connect Blinking once Orange LED is on = Connected and is recording data. FleetUP system fully tested step by step with technical specification in FMCSA ELD FInal Rule (Dec 12, 2015 Version) and meets all required functions.
HD 100 HD 100 Android 6.04.03 and higher RMDT00 Download Download Rand McNally 1-800-789-6277 fleetsales@randmcnally.com http://www.randmcnally.com/category/e-logs 9855 Woods Drive , Skokie, IL 60077 The supported data transfer mechanism is Telematics using both the Email and Web Services options. The step by step instructions for a driver are - 1. Tap HOS > OPTIONS 2. 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 3. Tap YES when prompted to “Require driver portal password to exit ‘Enforcement View?’. Enter your password 4. Tap SEND LOGS TO ENFORCEMENT to send logs to law enforcement. 5. Once the inspection is finished, tap BACK, then enter your DRIVER PORTAL PASSWORD again to exit ENFORCEMENT VIEW 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.
Garmin eLog GE1I01 6.50 or later GE1I01 Download Download Garmin International (800)-800-1020 product.support@garmin.com http://garmin.com/elog 1200 East 151st Street, Olathe, Kansas 66062 Garmin eLog supports the following Data Transfer methods: A. Data Transfer via Bluetooth B. Data Transfer via USB 2.0 A. Transferring Data to an Inspector Using a USB Device You can transfer data to a USB mass storage device to provide it to an authorized safety official. The Garmin eLog adapter supports USB mass storage devices formatted using the FAT32 file system. 1. From the Garmin eLog app, select "Inspection". 2. Select > Yes. 3. If necessary, enter an annotation. 4. Connect a USB mass storage device to the USB port on your Garmin eLog adapter. The adapter glows green when it is ready to send the inspection report. 5. Enter your password. 6. Select "Send to USB Device". The Garmin eLog app notifies you when the transfer is complete. 7. Remove the USB mass storage device from the adapter. B. Transferring Data to an Inspector Using Bluetooth Wireless Technology 1. From the Garmin eLog app, select "Inspection". 2. Select > Yes. 3. If necessary, enter an annotation. 4. Select Enable Pairing Mode. 5. Follow the on-screen instructions in the app to pair the Garmin eLog adapter with the inspector's mobile device. The inspection report transfers automatically after the pairing process is complete. DIAGNOSTIC AND MALFUNCTION CODES TABLE Diagnostic Code 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 Malfunction 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 O Other ELD detected malfunction SUMMARY OF MALFUNCTIONS: Garmin eLog supports the following Malfunctions specified below. Each Malfunction follows on with instructions which are provided to the driver in the Driver Reference Guide to help troubleshoot the issue. P: “Power compliance” malfunction The adapter did not receive power, or was not fully functional, for a period of time. At least 30 minutes of driving time may not have been correctly recorded across all drivers over the past 24 hours. Perform the following actions: 1 Check the vehicle diagnostic port connections. 2 Verify the adapter is firmly plugged into the vehicle diagnostic port. 3 Review all affected driver logs for missing or incorrect data E: “Engine synchronization compliance” malfunction The adapter failed to synchronize with the vehicle engine computer to record required engine data for driver logs. At least 30 minutes of inaccurate data may have been recorded across all drivers over the past 24 hours. Perform the following actions: 1 Check the vehicle diagnostic port connections. 2 Verify the adapter is firmly plugged into the vehicle diagnostic port. 3 Review all affected driver logs for missing or incorrect data. T: “Timing compliance” malfunction The Garmin eLog system failed to accurately verify the calendar date or time of day required for driver logs. Perform the following actions: 1 Verify the adapter is firmly plugged into the vehicle diagnostic port. 2 Check the Bluetooth settings on the device running the Garmin eLog app, and verify the device and the adapter are connected. 3 Check the date and time settings on the device running the Garmin eLog app. 4 Review all affected driver logs for missing or incorrect data. L: “Positioning compliance” malfunction The Garmin eLog system failed to acquire valid location positions required for driver logs. At least 60 minutes of inaccurate data may have been recorded across all drivers over the past 24 hours. Perform the following actions: 1 Verify the Garmin eLog app is running and a driver is logged in when driving the vehicle. 2 Check the Bluetooth settings on the device running the Garmin eLog app, and verify the device and the adapter are connected. 3 Check the GPS settings on the device running the Garmin eLog app, and verify the device settings allow location positions to be shared with the Garmin eLog app. 4 Review all affected driver logs for missing or incorrect data. R: “Data recording compliance” malfunction The Garmin eLog system has reached the maximum storage capacity for driver logs and cannot store or retrieve more logs. Perform the following actions: 1 Create a RODS report for each driver for record keeping. 2 Log in as an administrator. 3 Back up the system data. 4 Remove unneeded files from the storage of the device running the Garmin eLog app. S: “Data transfer compliance” malfunction Multiple failures occurred with the method for transferring roadside inspection reports. Perform the following actions: 1 Check the Bluetooth settings on the device running the Garmin eLog app, and verify the device and the adapter are connected. 2 Verify all USB storage devices used to transfer roadside inspection reports are operating correctly and are formatted using the FAT32 file system. 3 If you have not performed a data backup within the previous seven days, back up your recorded Garmin eLog data to a USB storage device. O: "Other" malfunction" Garmin eLog supports an "Other" type malfunction, namely "Adapter Firmware Malfunction". Adapter Firmware Malfunction is a placeholder in the event it is not possible for the eLog app to update the eLog adapter firmware. This malfunction is not an anticipated malfunction but is made available as a placeholder. Perform the following actions: 1 A serious error occurred attempting to update the adapter firmware. Contact Garmin® customer support for further help. 2 Outdated adapter firmware may not maintain compliance. Garmin recommends keeping paper logs until the adapter firmware is successfully updated. SUMMARY OF DIAGNOSTICS: Garmin eLog supports the following Diagnostics. Each Diagnostic follows on with instructions which are provided to the driver in the Driver Reference Guide in order to help troubleshoot the issue. 1: “Power data diagnostic” event The adapter did not receive power, or was not fully functional, for a period of time. Perform the following actions: 1 Check the vehicle diagnostic port connections. 2 Verify the adapter is firmly plugged into the vehicle diagnostic port. 3 Review all affected driver logs for missing or incorrect data. 2: “Engine synchronization data diagnostic” event The adapter failed to synchronize with the vehicle engine computer to record required engine data for driver logs. Perform the following actions: 1 Check the vehicle diagnostic port connections. 2 Verify the adapter is firmly plugged into the vehicle diagnostic port. 3 Review all affected driver logs for missing or incorrect data. 3: “Missing required data elements data diagnostic” event The Garmin eLog system failed to obtain one or more required data elements when recording driver logs. Perform the following actions: 1 Check the vehicle diagnostic port connections. 2 Verify the adapter is firmly plugged into the vehicle diagnostic port. 3 Check the Bluetooth settings on the device running the Garmin eLog app, and verify the device and the adapter are connected. 4 Check the GPS settings on the device running the Garmin eLog app, and verify the device settings allow location positions to be shared with the Garmin eLog app. 5 Review all affected driver logs for missing or incorrect data. 4: “Data transfer data diagnostic” event A failure occurred with the method for transferring roadside inspection reports. Perform the following actions: 1 Check the Bluetooth settings on the device running the Garmin eLog app, and verify the device and the adapter are connected. 2 Verify all USB storage devices used to transfer roadside inspection reports are operating correctly. 3 If you have not performed a data backup within the previous seven days, back up your recorded Garmin eLog data to a USB storage device. 5: “Unidentified driving records data diagnostic” event At least 30 minutes of unidentified driving was recorded within the current 24 hour period, and over the previous 7 days. Perform the following actions: • Drivers: Review and claim the unidentified driving time. • Administrator: Review and assign the unidentified driving time to the respective drivers. Each functional requirement specified in the APPENDIX A TO SUBPART B OF PART 395—FUNCTIONAL SPECIFICATIONS FOR ALL ELECTRONIC LOGGING DEVICES (ELDS) has been individually tested by Garmin Software Quality (SQ) Team. Each requirement has been validated according to meeting the specified requirement as is written in the specification. The FMCSA Test Plan and Procedures (Version 2.0) were consulted when verifying each requirement. The Garmin eLog solution is a local-type ELD solution supporting USB and BT data transfer methods at the roadside and meets all technical specifications detailed in the ELD rule with the following assumptions/caveats: (1) Electronic Motor Carrier Edit requests is an optional requirement noted in the ELD Technical Specifications (4.3.3.1.3). This is not supported since it is not an essential requirement for a local-type ELD. (2) The ELD data and formats required to be recorded for each event type were verified by viewing the generated FMCSA ELD Data File whereas the FMCSA Test Plan Procedures implied that the application user interface would provide this capability.
GpsBorder eLog BlueLink 4.3.3 WLI001 Download Download GpsBorder +1-956-467-1190 jose.balderas@gpsborder.com http://www.gpsborder.com/ 701 N. Int. Ste. 119-313, Hidalgo/TX/78557 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. 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 All Malfunctions (Engine synchronization, power compliance, etc.) are recorded and given the appropriate Diagnostic Code. See example below. HOS Log, For Fleet Date From 3/1/2017 12:00 AM to 3/10/2017 11:59 PM Time - 3/2/2017 2:31:14 AM Back Time Event Time - Malfunction Location - Troy, NY Note - Code: E, Description: Malfunction - Engine synchronization compliance, Odometer : 559800.0 I certified that the Bluelink and Android APP were rigorously tested and meets or exceeds all standards.
ELD Plug-In MW-ELD-J9C 3.30 and higher MW3764 Download Download Mobile Warrior LLC 888-474-9284 m.greear@mobilewarrior.com http://www.mobilewarrior.com/corporate/ 4009 Cardiel Road, Washougal, WA 98671 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.
Forward Thinking Systems - Field Warrior ELD (Garmin) FW-Garmin 3.0.0 or Higher FTSFW2 Download Download Forward Thinking Systems LLC 866-221-1864 eld@ftsgps.com https://www.ftsgps.com 575 Jericho Turnpike, Suite 301, Jericho / NY / 11753 We use web services and email for the telematics transfer options. Step-by-step instructions for the driver: - From the main ELD screen, tap on the “Export Logs” icon. - You will then be prompted to choose web services or email as the transfer method. - After choosing a transfer method, you will be prompted to enter a output file comment. - Tap the “Export” button, and the data transfer will be completed. Field Warrior® monitors its own compliance with ELD regulations. If a malfunction is detected, the app will notify the user by displaying an alert. The malfunction will also be logged in the ELD Malfunction Log that will be visible upon inspection. To see any malfunctions, open the menu drawer and select Alerts & Notifications. Malfunctions are also visible in Inspection Mode, which displays all event logs including malfunction events. Power Malfunction If Field Warrior® loses power or is disconnected from the vehicle, a warning message is displayed noting that the ELD is no longer being powered by the vehicle, and a malfunction event is logged. Engine Synchronization Malfunction If Field Warrior® detects a problem retrieving information from the vehicle’s ECU or detects a loss in ECU connectivity, a warning message is displayed and the event is logged. Timing Malfunction Field Warrior® periodically checks an external source for the current time to keep accurate logs. If the ELD is unable to get the current time from an outside source, a timing compliance malfunction is logged. Positioning Malfunction If Field Warrior® 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. Data Recording Malfunction Field Warrior® stores data locally and also sends driver data to be stored remotely. A data recording malfunction event is logged and a warning is displayed if a data malfunction is detected, a local database error occurs, or the device is unable to download the remotely stored logs. Data Transfer Malfunction If Field Warrior® 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. Other Malfunctions If Field Warrior® detects some other malfunction such as a hardware/software error, malfunction, or crash, it will log the event as Other Malfunction. We certify that Forward Thinking Systems LLC (a) develops the referenced Product in accordance with the requirements of 49 CFR 395 subpart B; and (b) performs the tests specified Electronic Logging Device (ELD) Test Plan and Procedures dated October 17, 2016, Version 2.0, which are promulgated by the U.S. Department of Transportation, Federal Motor Carrier Safety Administration, to test compliance with FMCSA regulations.
Hours Of Service Android & Geometris 1615.5628 or higher HOS001 Download Download VisTracks, Inc. 630-596-5420 info@vistracks.com http://www.vistracks.com/ 801 Warrenville Road, Lisle, IL 60565 The 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 the 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. The 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, 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 VisTracks Hours of Service (HOS) App was certified by the VisTracks testing team through successful execution and verification of the FMCSA ELD Test Procedures. The HOS App 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 VisTracks HOS web application (portal) that can be accessed through a web browser.
!A1 ELD on Blockchain by Ezlogz Ezlogz DApp 1 v237 or newer EZDApp 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.
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.
CommandGPS ELD AGCM01 1.4.72 or higher AGCM01 Download Download Agilis Systems 314 732 4925 Option 1 for Sales sales@agilissystems.com http://www.agilissystems.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 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.
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.
GPSTab ELD Edition GELDN01 GELDNA1.0 GNA001 Download Download Utech Inc. 888-228-4460 sales@utechcorp.com www.utechcorp.com 2100 W. 21st Street, Broadview, IL 60155 *There is a section in uploaded manual that describes and showcases data transfer mechanism with colors and visual cues. INSPECTION GPSTab ELD Edition provides an easy way for a driver to produce and transfer the ELD records to an authorized safety official. TO PRODUCE LOGS ON THE SCREEN: 1. Tap on the Menu icon on the top left. 2. Select Inspection Module from the Menu. 3. To let an authorized safety official inspect your logs directly from your device, tap Begin Inspection. 4. Give the authorized safety official your mobile device. 5. Tap the Back arrow on the top left to exit Inspection Module. TO EMAIL OR FAX LOGS TO THE AUTHORIZED SAFETY OFFICIAL: 1. Tap Send Logs from Inspection Module screen. 2. Tap the checkbox next to each log you want to send. 3. Choose the transfer method by clicking on Email or Fax tab. 4. Enter the email address or fax number of the authorized safety official. 5. Tap Send to email 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 GPSTab ELD Edition App if you choose to provide the authorized safety official with hard copy. GPSTab – ELD Edition 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. *There is a section in uploaded manual that describes and showcases Malfunctions with colors and visual cues. How does the driver know if GPSTab ELD is malfunctioning? The GPSTab 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 UTECH support immediately after discovering a malfunction at 888-228-4460 or support@utechcorp.com 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, UTECH 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). GPSTab ELD Edition 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 GPSTab ELD Edition. Upon completion of necessary tests outlined in the above named document we certify that GPSTab ELD Edition 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
Saucon Prox ELD PROXST16 20170221 or higher PROXST Download Download Saucon Technologies, Inc 4842412514 tdsinfo@saucontech.com saucontds.com 2455 Baglyos Circle, Bethlehem/PA/18020 Saucon Prox ELD will use the telematics option (web services and email) to transfer the data during a roadside inspection. From the main screen, the driver taps the red menu button, and selects “Inspection Mode.” Once there, the driver taps the “Transfer” button. The driver is then prompted to select the method of transfer specified by the inspector (Web Services or email). Once the method of transfer is selected, the driver is prompted to enter an Output File Comment (if provided by officer). The driver enters the Comment, and taps ‘Send,’ or just taps ‘Send’ if the Comment is not required. The driver will receive on-screen confirmation that the request has been submitted. Saucon Prox ELD provides the following diagnostic and malfunction events, as specified in the ELD regulation, Section 4.6 Table 4: “Power compliance” malfunction; “Engine synchronization compliance” malfunction; “Timing compliance” malfunction; “Positioning compliance” malfunction; “Data recording compliance” malfunction; “Data transfer compliance” malfunction; “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 (Positioning diagnostic event). When no Data Diagnostic Events or Malfunctions are active, a light indicator will display green. When any of the above Data Diagnostics events are active, the light indicator will display yellow. When any of the above Malfunctions are active, the light indicator will display red. Saucon Prox ELD was tested in accordance with the “Electronic Logging Device (ELD) Test Plan and Procedures,” dated 4/25/2016, Version 1.0. Testing was completed using the Saucon Prox ELD within a vehicle, as well as using simulated data from our test lab.
Switchboard SB1 0.88 or above SWITCH Download Download Switchboard 1-844-5-FLEETS sales@onswitchboard.com https://www.onswitchboard.com 1632 E 4th Avenue, Vancouver, British Columbia, V5N 1J8 On the Switchboard ELD device, select the "Authority" button on the driver screen. In this "Authority View", regulators can view the hours-of-service logs for the driver. In addition to viewing the hours-of-service graph, ELD Events, Malfunction recordings, Switchboard's Electronic Logging Devices have the following methods to transfer hours-of-service data over to authorities and regulators: 1. Faxing Logs to a Fax Number By selecting "Share Logs" on the top right of the "Authority View", one can select the "Fax" option and enter a fax number to send the last 7 to 14 days of logs to. 2. Email Transfer By selecting "Share Logs" on the top right of the "Authority View", one can select the "Email" option and enter an email address to send the last 7 to 14 days of logs to. 3. Wireless Web Services When the FMCSA has set up its server to be able to send the Hours-of-Service logs, Switchboard has the appropriate processes to send driver log data to the servers ready to go. When sending the logs via fax or email, the data should be sent instantly. If the tablet is outside of data coverage, log data should be sent once the tablet obtains data coverage. The user can view the summary of malfunctions through the "Authority View" on the Switchboard Electronic Logging Device. On the Switchboard ELD device, select the "Authority" button on the driver screen. There you will be able to see your ELD Events (Duty Status Changes, Malfunctions, Login/Logout Events, Engine Events). To see more details regarding the malfunctions, select "View Malfunctions" to view the list of ELD Malfunction records. On the list of the malfunctions, you will see the Date/Time of the malfunction, the malfunction code as well as the malfunction description. Switchboard was tested in two phases: Short Distance Focus Testing, and Full Cycle Testing. During Short Distance Focus Testing, Switchboard tested functionality of ELD Event Properties recording; a test account was logged into a Switchboard ELD connected to a vehicle ECM. The vehicle was driven to ensure that the automatic Driving duty status switching occurred, and that duty status recordings were saved with the proper properties (Event Record Origin, Type, Status, Sequence ID, etc.). Switchboard also tested the device as it was logged off to ensure that proper unidentified driver records were saving, and could be assigned accordingly. Full Cycle Testing involved installing Switchboard Electronic Logging Devices on vehicles that completed multiple line hauls. For weeks, drivers' logs were monitored as they completed multiple cycles and resets across both the United States and Canada. Through this testing Switchboard ELDs were verified to be operationally function across the various Cycle Rules in US and Canada, and also across time zones in different States and Provinces. ELD Events were checked to see if proper GPS locations were being recorded to the events. Both single drivers and team drivers had Switchboard ELDs installed, to test proper function of the device with or without a co-driver present. Switchboard Electronic Logging Devices were compared with paper logs that the drivers were completing and the devices were being tested. Through both Short Distance Focus and Full Cycle Testing, it was ensured that throughout the usage of the Switchboard Electronic Logging Devices across multiple weeks, there have been no malfunctions observed. As of the most recent software version (1.0), drivers can properly use Switchboard Electronic Logging Devices to record ELD Events as mandated by the FMCSA without issue. Switchboard certifies that the SB1 model is compliant with the test plan and procedures as stated in tests ELD-FUNC-4.4.1.1-1 to ELD-FUNC-4.10.2-1, minus the exceptions regarding web portal services: 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
Contractor Elogs - 3030 LMU-3030 1.5.5 LMU030 Download Download MachineLINK (573) 310-7902 info@estrack.com https://www.estrack.com 2511 Broadway Bluffs Dr Ste 202, Columbia, MO 65201 The certified method of transferring data is via email. 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. 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 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 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, Kristopher O. Dunn , hereby certify on behalf of EquipmentShare that ELD model LMU030 and version 1.5.5 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.
GFI eLogs Android and iOS Xirgo XT6300 1.0.1905.190415 GFI001 Download Download GFI Systems Inc. 1-855-434-4477 eld@gfisystems.ca http://www.gfisystems.ca 500 10709 Jasper Ave., Edmonton, Alberta The GFI eLogs 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 GFI eLogs 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 GFI eLogs 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 GFI eLogs 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 GFI eLogs ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The GFI eLogs 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 CalAmp 4230 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.
Geotab Drive Cloud ELD GO6, GO7, GO8, GO9 or PEP-GO7. PEP-GO8 or ATT-GO7, ATT-GO8 or FL7 (by Spireon), FL8 (by Spireon) or RI7/8 (by BSM) 5.7.1804 or above GEOTAB Download Download Geotab Inc. 1 877-436-8221 salesteam@geotab.com https://www.geotab.com Unit 21, 1075 North Service Rd W, Oakville/Ontario/L6M2G2 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/i6BphA 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 GO device. Contact your carrier to get the install inspected. If problem still persists, replace the GO 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 GO 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 Geotab internal testing procedures.
!A1 ELD by HOS247 A1 2.2 and up 1A1ELD Download Download HOS247 LLC 415-839-9977 hello@hos247.com www.hos247.com 10401 CEDAR LAKE RD UNIT 212, MINNETONKA, MN 55305 !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.
Hours Of Service iOS & CalAmp4230 1.0.1801.11819 HOS001 Download Download VisTracks, Inc. 630-596-5420 info@vistracks.com http://www.vistracks.com/ 801 Warrenville Road, Lisle, IL 60565 The 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 the 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. The 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, 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 VisTracks Hours of Service (HOS) App was certified by the VisTracks testing team through successful execution and verification of the FMCSA ELD Test Procedures. The HOS App 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 CalAmp 4230 engine connected device. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the VisTracks HOS web application (portal) that can be accessed through a web browser.
MasterELD MELD01 MELDA1.0 MBFA01 Download Download NATIONAL TRANSPORTATION PARTNERS LLC 630-422-7497 eld@mastersafetyinc.com http://www.mastereld.com 1040 BORDEN DR., ROSELLE, IL 60172, ROSELLE / IL / 60172 *There is a section in uploaded manual that describes and showcases data transfer mechanism with colors and visual cues. INSPECTION MasterELD provides an easy way for a driver to produce and transfer the ELD records to an authorized safety official. TO PRODUCE LOGS ON THE SCREEN: 1. Tap on the Menu icon on the top left. 2. Select Inspection Module from the Menu. 3. To let an authorized safety official inspect your logs directly from your device, tap Begin Inspection. 4. Give the authorized safety official your mobile device. 5. Tap the Back arrow on the top left to exit Inspection Module. TO EMAIL OR FAX LOGS TO THE AUTHORIZED SAFETY OFFICIAL: 1. Tap Send Logs from Inspection Module screen. 2. Tap the checkbox next to each log you want to send. 3. Choose the transfer method by clicking on Email or Fax tab. 4. Enter the email address or fax number of the authorized safety official. 5. Tap Send to email 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 MasterELD App if you choose to provide the authorized safety official with hard copy. GPSTab – ELD Edition 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. *There is a section in uploaded manual that describes and showcases Malfunctions with colors and visual cues. How does the driver know if MasterELD is malfunctioning? The MasterELD 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 MasterELD support immediately after discovering a malfunction at support@mastereld.com 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, MasterELD 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). MasterELD 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 MasterELD. Upon completion of necessary tests outlined in the above named document we certify that MasterELD 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
Verizon Connect WorkPlan & HOS ELD - Formerly Telogis WorkPlan & HOS Calamp LMU 3640 Series Workplan 4/HOS 3.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.
Hours Of Service Android & Astus 1.0.1805.14219 HOS001 Download Download VisTracks, Inc. 630-596-5420 info@vistracks.com http://www.vistracks.com/ 801 Warrenville Road, Lisle, IL 60565 The 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 the 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. The 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, 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 VisTracks Hours of Service (HOS) App was certified by the VisTracks testing team through successful execution and verification of the FMCSA ELD Test Procedures. The HOS App 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 engine connected device. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the VisTracks HOS web application (portal) that can be accessed through a web browser.
PeopleNet Connected Gateway - eDriver Logs ELD PCG001 .18x or higher PCG001 Download Download PeopleNet 888-346-3486 info@peoplenetonline.com www.peoplenetonline.com 4400 Baker Road, Minnetonka, MN 55343 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”. User is able to type in the white dialog box for a reference information that will be sent with the file. Select either Email or Web Service once your selection is made the Done button will become active. Tap Done to send the file. 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 eDriver Logs ELD application has stopped working or is not responding as expected. PeopleNet 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 PCG001 and complies with all Federal Motor Carrier Safety Administration (FMCSA) specifications as found in 49 CFR Part 395 for Electronic Logging Devices, Subpart B.
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 Connect uses a light built into the cradle dock. Flashing Red: Tablet not in dock (CabMate Connect 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 Connect 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 Connect 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.
VDOS ELD VDOS ELD iOS/Geotab 2.5.0 or greater SUNBLT Download Download Sunbelt Rentals 800-667-9328 Customerservice@sunbeltrentals.com http://www.sunbeltrentals.com 2341 Deerfield Driver, Fort Mill, SC 29715 Option 1: Telematics Web Services and Email initiated through mobile device. Step by step instructions to transfer records to FMCSA are included in the In Cab Instruction Manual. they include logging into the service on the iOS device using the employees unique clock ID and password. From here they will choose the Hours of Service option from the main menu, at the status page (default, main page) select the share button located in the upper right corner of the screen (icon looks like a square with an arrow pointing out of the top). They will select the type of transfer (eMail, or Web service), enter the code received from the enforcement officer and hit submit. Warnings and alerts appear as a banner at the bottom of the screen on the handheld device. The following malfunctions are supported: Power data malfunction, Engine sync malfunction, Timing compliance malfunction, Positioning compliance malfunction, Data recording malfunction, Data transfer compliance malfunction, Unidentified driver compliance. All testing is complete with exception of web service transfer. We have to obtain ELD Identifier to implement this procedure.
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
Hours Of Service iOS & IOSiX 1.0.1801.11819 HOS001 Download Download VisTracks, Inc. 630-596-5420 info@vistracks.com http://www.vistracks.com/ 801 Warrenville Road, Lisle, IL 60565 The 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 the 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. The 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, 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 VisTracks Hours of Service (HOS) App was certified by the VisTracks testing team through successful execution and verification of the FMCSA ELD Test Procedures. The HOS App 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 IOSiX engine connected device. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the VisTracks HOS web application (portal) that can be accessed through a web browser.
Descartes Telematics - Smart Device DSG ELD SD 4200 18.01 or higher DSGSD1 Download Download The Descartes Systems Group Inc + 1 519.746.8110 info@descartes.com www.descartes.com 120 Randall Drive, Waterloo Ontario N2V 1C6 To view the HOS records on the Display: 1. Select the HoS Review icon on the Main Menu 2. Select the Driver Reference number 3. Select the date for records that you wish to view. The current 24-hour period can be selected (Today) or one of the previous seven days. 4. The DOT Inspection Header is displayed. Depending on the size of the screen the Safety Official may need to swipe left to view all this information. 5. Swipe up to view the HoS graph. 6. Swipe Up to view the details of each HoS Record. To send records to the FMCSA (email and Web Service supported): 1. Select Transfer RODS 2. Select email or Web Service 3. Enter Optional Comment 4. Select OK Records will be sent to the FMCSA by the selected method. The comment will be included with the records sent. The Descartes Telematics solution monitors for the following malfunctions in the described scenarios: 1. The Descartes Telematics solution monitors and ensures that the solution connects to the vehicle after engine start up. If it does not become fully functional within 1 minute of receiving power or does not remain powered for as long as the vehicle engine is powered then a Power Compliance Malfunction is recorded. 2. An Engine Synchronization Compliance Malfunction when 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, including the unidentified driver profile. 3. Timing Compliance Malfunction is rasied when the Date/Time of the ELD is not synchronized with Google Services UTC time. We check every hour. 4. Positioning Compliance Malfunction - Our ELD monitors elapsed time during periods when we fail 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 sets and records a positioning compliance malfunction 5. Data Recording Compliance Malfunction - Our ELD offering monitors the storage capacity. A Data Recording Compliance Malfunction is recorded when the ELD and can no longer record or retrieve previously recorded logs. 6. Data Transfer Compliance Malfunction is recorded when our ELD fails to confirm proper in-service operation of the data transfer mechanism(s) - we frequently check if there was a connection to our servers from the ELD device in the past seven days and if not we record a malfunction. 7. Other Malfunction – 'ELD Device Disconnected' - we record this malfunction If the ELD device is disconnected from engine for more than 30 minutes when vehicle was in engine power ON state. 8. Other Malfunction - a Back office user can set ELD Device malfunction named 'Other malfunction' event - with remark visible on RODS and annotation set to Malfunction added manually. Descartes Systems Group, Inc. (“Descartes”) hereby certifies that, pursuant to the United States Federal Motor Carrier Safety Administration Self-Certification provisions for ELD Descartes Fleet Center Version 18.01 or later Descartes Smart Fleet Version 18.01 or later (collectively, the “System”) has been reviewed by Descartes and deemed compliant with the requirements of the United States Department of Transportation, Federal Motor Carrier Safety Administration 49 CFR Parts 385, 386, 390 and 395 Electronic Logging Devcies and Hours of Service Supporting Documents Final Rule as they exist on the date of this certification, when maintained in proper working order and operated as instructed in the manuals for the System. Descartes is not responsible for the accuracy or completeness of information input in to the System or non-Descartes technology interacting with the System. Certified on: 12/21/2017 Descartes Authorized Signatory Kenneth E. Wood Executive Vice President of Product Management
IntegrityELD ELD-S 1.0.1801.11540 INT001 Download Download Integrity Fleet Solutions 1.888.407.6807 info@integrityfleetsolutions.com http://www.integrityfleetsolutions.com PO Box 1045, Jackson, WY 83001 IntegrityELD 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 IntegrityELD 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 IntegrityELD 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 IntegrityELD 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 IntegrityELD ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The IntegrityELD 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.
FleetRover WiFi FleetRover ELD-WiFi 1.42.7 FR1427 Download Download FleetRover 647-680-9876 help@fleetrover.com http://fleetrover.com/ 2 Barnham Street, Ajax/Ontario/L1Z 0M5 1. Send Logs To a Printer - From the home screen, tap on the "eye" in the top right corner to enter Inspection Mode- You will now see "INSPECTION MODE - Please hand this device over to the Inspector" - Select "BEGIN INSPECTION" on the bottom of the screen by pressing it with your finger. - To send your logs to a printer, select the "printer icon" in the top right corner. - Click the arrow in the top right corner to select the appropriate printer - You also have the option to download the logs to the device as a PDF. It will appear as "Save as PDF" (which can then be viewed and/or emailed). - Choose the appropriate printer from the list provided in the "Select printer" drop-down. 2. Email Logs to Yourself or a Fleet Manager - From the home screen, select "Send daily logs". - Choose which timeframe you would like to share by selecting the correct period (24 hours, 7 days, or 14 days) - Enter the email address in the "Enter email address" field - You will see an "Email sent successfully". This confirms your logs have been sent. 3. Web Services/Email Logs to an Inspector - From the home screen, tap on the "eye" in the top right corner to enter Inspection Mode - You will now see "INSPECTION MODE - Please hand this device over to the Inspector" - Select "BEGIN INSPECTION" on the bottom of the screen by pressing it with your finger. - To send logs to the Inspector, select the arrow in the top right corner of the screen - Choose which timeframe you would like to share by selecting the correct period (24 hours, 7 days, or 14 days) - Enter the routing number provided by the inspector into the "Enter routing number" field - Logs will be sent through both Web Services and email with the routing number provided - You will see "sent successfully". This confirms your logs have been sent. Data Diagnostic events Code and Description: 1: Your ELD has been off for over a minute. Please re-start the vehicle, or check your ELD’s connection -Occurs when an ELD is not powered and fully functional within one minute of the vehicle engine power up, and the ELD does not remain powered while the vehicle engine is powered. 2: Your ELD has lost connection. Please re-start the vehicle, or check your ELD’s connection -Occurs when an ELD loses connection to the ECM and cannot obtain any required data sources (engine power, vehicle motion, miles driven, and engine hours) and their updated values within 5 seconds. 2: Your ELD has lost connection. Please re-start the vehicleor check your ELD’s connection -NOTE: If upon re-connect, the ELD is still not obtaining required data sources 'Engine Synchronization Failure' alert will be sent to FMCSA. Driver will be notified, and issue will be resolved by FleetRover within 24 hours -Occurs when an ELD loses connection to the ECM and cannot obtain any required data sources (engine power, vehicle motion, miles driven, and engine hours) for more than 30 minutes during a 24-hour period. 3: Missing required data elements. Please check your ELD's connection. -Occurs when any required data element is missing at the time of its recording. 3: Please enter your location -Occurs when an ELD doesn’t acquire a valid position measurement within 5 miles of the vehicle’s movement during a cumulative 60-minute or greater period over 24 hours. -Note 1: If this malfunction is due to a change in driver duty status, the ELD will prompt the driver to enter a location. If the driver does not enter the location, and the vehicle is moving, the ELD will record a “missing required data element” diagnostic event for the driver. -Note 2: If the driver does not enter the location within 120 minutes a 'Position Compliance Failure' alert will be triggered 4: Due to a connection error, the data transfer process has failed. Please retry and check your internet connection -Occurs when user attempts to use the Telematics services and the attempt is unsuccessful for connectivity reasons 4: Due to an encryption error, the data transfer process has failed. Please retry and check your internet connection -Occurs when user attempts to use the Telematics services and the attempt is unsuccessful because the encryption process was somehow corrupted 5: You are currently in unidentified driving mode. Please assign a driver to the vehicle. -Occurs when an unidentified driver record has been recorded on the ELD for more than 30 minutes of driving in a 24-hour period. -NOTE: If a driver is not assigned immediately, an 'Unidentified Driving Records Data Diagnostic Failure' alert will be triggered and recorded ** 6: No other diagnostic event alerts are implemented in the FleetRover application at this time. Malfunction Code and Description: P: Your ELD has been off for over 30 minutes in the past 24 hours. Please check your connection, and keep a paper log of your driving activity. -NOTE: If upon re-start, the ELD is still not obtaining required data sources 'Engine Synchronization Failure' alert will be sent to FMCSA. Driver will be notified, and issue will be resolved by FleetRover within 24 hours -Occurs when the ELD is not powered on while the vehicle is in motion for longer than 30 minutes during the 24 hour period. ECM data or ECM connectivity data must be captured when the engine is powered, but the ELD is not prohibited from recording information when the engine is off. E: You are not connected to your ELD due to a synchronization failure. We will resolve the issue within 24 hours, and have notified the FMCSA of our malfunction. -Occurs when an ELD loses connection to the ECM and cannot obtain any required data sources (engine power, vehicle motion, miles driven, and engine hours) for more than 30 minutes during a 24-hour period, the vehicle and ELD have been re-started to resolve the issue, and the issue is still occurring T: Your ELD is not properly synchronized with your current time zone. Please re-start the vehicle or check your connection. -NOTE: If upon re-connect, the ELD is still not obtaining required data sources Timing Compliance Failure' alert will be sent to FMCSA. Driver will be notified, and issue will be resolved by FleetRover within 24 hours -Occurs when the ELD time is not properly synchronized with Coordinated Universal Time (UTC) so that the time is inaccurate by 10 minutes or more at any time. L: Occurs when an ELD doesn’t acquire a valid position measurement within 5 miles of the vehicle’s movement during a cumulative 60-minute or greater period of 24 hours. Driver will be notified, and issue will be resolved by FleetRover within 24 hours R: Data recording to your ELD device has continuously failed. This malfunction will be noted to the FMCSA and a FleetRover representative will contact you shortly for resolution -Occurs when an ELD can no longer record or retain required data or retrieve recorded logs. R: You have not entered your location. We will notify the FMCSA of the malfunction and the non-entry -Occurs when an ELD doesn’t acquire a valid position measurement within 5 miles of the vehicle’s movement during a cumulative 60-minute or greater period over 24 hours, the driver has been asked to enter their location and has not for 24 hours S: The data transfer process has failed because your profile is missing some vital information. Please check that you are not in Unidentified Driving Mode and that timing is synchronized. -Occurs when user attempts to use the Telematics services and the attempt is unsuccessful because some necessary information is missing from the application ** O: No other malfunction event alerts are implemented in the FleetRover application at this time. This is to confirm that the FleetRover ELD has been deemed to be fully FMCSA compliant by FleetRover Inc. Thorough testing of the procedures outlined in the FMCSA-released document "Electronic Logging Device (ELD) Test Plan and Procedures" was conducted throughout the development process to ensure that the model met the technical specifications required.
Descartes Telematics - G Tablet DSG ELD TT GO 18.05 or higher DSGGT1 Download Download The Descartes Systems Group Inc + 1 519.746.8110 info@descartes.com www.descartes.com 120 Randall Drive, Waterloo Ontario N2V 1C6 To view the HOS records on the Display: 1. Select the HoS Review icon on the Main Menu 2. Select the Driver Reference number 3. Select the date for records that you wish to view. The current 24-hour period can be selected (Today) or one of the previous seven days. 4. The DOT Inspection Header is displayed. Depending on the size of the screen the Safety Official may need to swipe left to view all this information. 5. Swipe up to view the HoS graph. 6. Swipe Up to view the details of each HoS Record. To send records to the FMCSA (email and Web Service supported): 1. Select Transfer RODS 2. Select Web Service or email 3. Enter Optional Comment 4. Select OK Records will be sent to the FMCSA by the selected method. The comment will be included with the records sent. The Descartes Telematics solution monitors for the following malfunctions in the described scenarios: 1. The Descartes Telematics solution monitors and ensures that the solution connects to the vehicle after engine start up. If it does not become fully functional within 1 minute of receiving power or does not remain powered for as long as the vehicle engine is powered then a Power Compliance Malfunction is recorded. 2. An Engine Synchronization Compliance Malfunction when 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, including the unidentified driver profile. 3. Timing Compliance Malfunction is rasied when the Date/Time of the ELD is not synchronized with Google Services UTC time. We check every hour. 4. Positioning Compliance Malfunction - Our ELD monitors elapsed time during periods when we fail 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 sets and records a positioning compliance malfunction 5. Data Recording Compliance Malfunction - Our ELD offering monitors the storage capacity. A Data Recording Compliance Malfunction is recorded when the ELD and can no longer record or retrieve previously recorded logs. 6. Data Transfer Compliance Malfunction is recorded when our ELD fails to confirm proper in-service operation of the data transfer mechanism(s) - we frequently check if there was a connection to our servers from the ELD device in the past seven days and if not we record a malfunction. 7. Other Malfunction - a Back office user can set ELD Device malfunction named 'Other malfunction' event - with remark visible on RODS and annotation set to Malfunction added manually. Descartes Systems Group, Inc. (“Descartes”) hereby certifies that, pursuant to the United States Federal Motor Carrier Safety Administration Self-Certification provisions for ELD Descartes Fleet Center Version 18.05 or later Descartes Smart Fleet Version 18.05 or later (collectively, the “System”) has been reviewed by Descartes and deemed compliant with the requirements of the United States Department of Transportation, Federal Motor Carrier Safety Administration 49 CFR Parts 385, 386, 390 and 395 Electronic Logging Devcies and Hours of Service Supporting Documents Final Rule as they exist on the date of this certification, when maintained in proper working order and operated as instructed in the manuals for the System. Descartes is not responsible for the accuracy or completeness of information input in to the System or non-Descartes technology interacting with the System. Certified on: 05/03/2018 Descartes Authorized Signatory Kenneth E. Wood Executive Vice President of Product Management
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 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.
Compliance Now Android & Pacific Tracks 1712.7443 or higher 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.
PeopleNet Mobile Gateway - eDriver Logs ELD PMG001 .18x or higher PMG001 Download Download PeopleNet 888-346-3486 info@peoplenetonline.com www.peoplenetonline.com 4400 Baker Road, Minnetonka, MN 55343 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. 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 eDriver Logs ELD application has stopped working or is not responding as expected PeopleNet 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 PMG001 and complies with all Federal Motor Carrier Safety Administration (FMCSA) specifications as found in 49 CFR Part 395 for Electronic Logging Devices, Subpart B.
Rapid On The GO! Rapid GO! Tab 1.1.20 or higher ROTGO! Download Download Rapid Apps Group, LLC 303.500.3050 vesko@rapidappsinc.com http://rapidappsinc.com 4393 Pierson Street, Wheat Ridge, CO 80033 Telematics Option 1: Web Service and E-mail Data Transfer Process Here are the exact steps of how this happens through our ELD mobile application: 1. Driver must open the mobile app Rapid On the GO! from its device desktop icon 2. Driver must login to the app using his Company's Client ID, Username, Password and Language choice. 3. Driver must press on a button titled "DOT". visible on the home screen after login 4. Driver must choose the number of log days he wishes to display to the safety official from a collection of possible choices: 8 Days, 7 days, 6-Days, 5-Days. 5. Driver must press on the "Generate Report" button that follows after step 4 6. Once the report is generated, the Driver can show the screen of the device to the safety official for a visual audit of the generated driving log report. 7. At bottom of the report there will be 2 buttons: - Send Report - Send Email Driver/Official may press on either of the two buttons to send the DOT HOS report to the FMCSA. Pressing the "Send Report" button will send the DOT HOS report using the web service endpoints located at https://eldws.fmcsa.dot.gov. Pressing the "Email Report" button will send the DOT HOS report using the secure e-mail process to fmcsaeldsub@dot.gov. In the event that an ELD malfunctions, the driver is required to immediately begin completing a paper log and to reconstruct logs for each of the past 7 days, unless the driver already possesses the records or the records are retrievable from the ELD. ELDs must be repaired within 8 days, subject to an FMCSA-approved extension. All diagnostic malfunction codes are being handled through a 3rd party DOT-compliant device called "GeoTab". These diagnostic events and their codes could be captured using our ELD mobile application ROTG and displayed as part of the rolling daily DOT HOS logs. Here is a summary of all the malfunctions codes that are capable of being captured: P - Power Compliance Error E - Engine Synchronization Compliance Error T - Timing Compliance Error L - Geo-positioning Compliance Error R - Data Recording Compliance Error S - Data Transfer Compliance Error O - Other Compliance Issues 1 - Power Data Diagnostic Event 2 - Engine Synchronization Data Diagnostic Event 3 - Missing Required Data Elements Diagnostic Event 4 - Data Transfer Diagnostic Event 5 - Unidentified Data Transfer Records Diagnostic Event 6 - Other Diagnostic Events The product was tested through a Q&A process between on-field operators navigating concrete pumping equipment through the use of an ELD device bundled with the mobile application Rapid On The GO! The generated ELD Report File was tested without errors using the publicly provided FMCSA online validator located at: https://csa.fmcsa.dot.gov/ELD/Tools/Validator We certify that our mobile application Rapid On The GO! version, used in conjunction with AT&T tablet SAMSUNG-SM-T337A and any GeoTab Hardware Unit conforms to the ELD specifications.
3MD ELD 3MD100 1.0.1715 or higher 3MD100 Download Download 3MD Solutions, LLC. 708-698-1000 info@3mdinc.com http://www.3mdinc.com 6475 Joliet Road, Countryside, IL 60525 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.
Hours Of Service Android & Pacific Track 1.0.1712.7443 HOS001 Download Download VisTracks, Inc. 630-596-5420 info@vistracks.com http://www.vistracks.com/ 801 Warrenville Road, Lisle, IL 60565 The 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 the 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. The 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, 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 VisTracks Hours of Service (HOS) App was certified by the VisTracks testing team through successful execution and verification of the FMCSA ELD Test Procedures. The HOS App 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 VisTracks HOS web application (portal) that can be accessed through a web browser.
FleetUp 3NX-a 1.0 or Higher TLT3NX Download Download FleetUp 855-274-2886 hello@fleetup.com www.fleetup.com 500 Yosemite Dr., Suite 120, Milpitas/CA/95035 Open the FleetUP HOS application and sign in. Locate the Logs Tab and go to the RODS page. After driver signs his or her report from the mobile application directly, the driver can use the save button on the top left corner to export data into a PDF file. Once a driver signs his or her report, the report cannot be altered or edited. The driver can send the PDF to an authorized safety official. On the FleetUP HOS application, a malfunction will occur if there is no data being recorded. 3NX will show that there is no data being recorded. Driver managers must then contact FleetUP Support for a repair or an exchange and it will be processed within the next 8 days. There are three indicators on 3NX. Power GSM network, and GPS communication. *Power Status Solid On = Connected with the engine and Reading protocol/engine data, Solid Off = Not reading engine data. (Tracker Mode), Blinking = Searching for engine data *GSM Network Status Solid On = Connected to GSM Network Solid Off = Not connected to GSM network. Blinking Fast = Searching for network/No SIM card Blinking Slow = connecting to GSM Network. *GPS Communication Status Solid On = Successful GPS Communication Solid Off = No GPS Communication Blinking = Trying to connect Blinking once Orange LED is on = Connected and is recording data. FleetUP system fully tested step by step with technical specification in FMCSA ELD Final Rule (Dec 12, 2015 Version) and meets all required functions.
FleetRover FleetRover ELD 1.40.5 FR1405 Download Download FleetRover 647-680-9876 help@fleetrover.com http://fleetrover.com/ 2 Barnham Street, Ajax/Ontario/L1Z 0M5 1. Send Logs To a Printer - From the home screen, click on the “eye” icon in the top right corner. - You will now see “INSPECTION MODE - Please hand this device over to the Inspector” - Select “BEGIN INSPECTION” on the bottom of the screen by pressing it with your finger. - To send your logs to a printer, select the “printer icon” in the top right corner. - Press “Select printer” at the top of the screen. - You also have the option to download the logs to the device as a PDF. It will appear as “Save as PDF” (which can then be viewed and/or emailed). - Choose the printer that the Inspector has provided. 2. Email Logs to an Inspector - From the home screen, select “Send daily logs”. - Choose which timeframe you would like to share by selecting the correct period (24 hours, 7 days, or 14 days) - Enter the email address the inspector has provided to you in the “Enter email address” field - You will see an “Email sent successfully”. This confirms your logs have been sent. 3. Telematics - Web Services - From the home screen, select “Send daily logs”. - Choose which timeframe you would like to share by selecting the correct period (24 hours, 7 days, or 14 days) - Select “Web transfer” and enter the routing code given to you by the authorized safety official into the “Routing Code” field - You will see “transfer successful”. This confirms your logs have been sent. Data Diagnostic events Code and Description: 1: Your ELD has been off for over a minute. Please re-start the vehicle, or check your ELD’s connection -Occurs when an ELD is not powered and fully functional within one minute of the vehicle engine power up, and the ELD does not remain powered while the vehicle engine is powered. 2: Your ELD has lost connection. Please re-start the vehicle, or check your ELD’s connection -Occurs when an ELD loses connection to the ECM and cannot obtain any required data sources (engine power, vehicle motion, miles driven, and engine hours) and their updated values within 5 seconds. 2: Your ELD has lost connection. Please re-start the vehicleor check your ELD’s connection -NOTE: If upon re-connect, the ELD is still not obtaining required data sources 'Engine Synchronization Failure' alert will be sent to FMCSA. Driver will be notified, and issue will be resolved by FleetRover within 24 hours -Occurs when an ELD loses connection to the ECM and cannot obtain any required data sources (engine power, vehicle motion, miles driven, and engine hours) for more than 30 minutes during a 24-hour period. 3: Missing required data elements. Please check your ELD's connection. -Occurs when any required data element is missing at the time of its recording. 3: Please enter your location -Occurs when an ELD doesn’t acquire a valid position measurement within 5 miles of the vehicle’s movement during a cumulative 60-minute or greater period over 24 hours. -Note 1: If this malfunction is due to a change in driver duty status, the ELD will prompt the driver to enter a location. If the driver does not enter the location, and the vehicle is moving, the ELD will record a “missing required data element” diagnostic event for the driver. -Note 2: If the driver does not enter the location within 120 minutes a 'Position Compliance Failure' alert will be triggered 4: Due to a connection error, the data transfer process has failed. Please retry and check your internet connection -Occurs when user attempts to use the Telematics services and the attempt is unsuccessful for connectivity reasons 4: Due to an encryption error, the data transfer process has failed. Please retry and check your internet connection -Occurs when user attempts to use the Telematics services and the attempt is unsuccessful because the encryption process was somehow corrupted 5: You are currently in unidentified driving mode. Please assign a driver to the vehicle. -Occurs when an unidentified driver record has been recorded on the ELD for more than 30 minutes of driving in a 24-hour period. -NOTE: If a driver is not assigned immediately, an 'Unidentified Driving Records Data Diagnostic Failure' alert will be triggered and recorded ** 6: No other diagnostic event alerts are implemented in the FleetRover application at this time. Malfunction Code and Description: P: Your ELD has been off for over 30 minutes in the past 24 hours. Please check your connection, and keep a paper log of your driving activity. -NOTE: If upon re-start, the ELD is still not obtaining required data sources 'Engine Synchronization Failure' alert will be sent to FMCSA. Driver will be notified, and issue will be resolved by FleetRover within 24 hours -Occurs when the ELD is not powered on while the vehicle is in motion for longer than 30 minutes during the 24 hour period. ECM data or ECM connectivity data must be captured when the engine is powered, but the ELD is not prohibited from recording information when the engine is off. E: You are not connected to your ELD due to a synchronization failure. We will resolve the issue within 24 hours, and have notified the FMCSA of our malfunction. -Occurs when an ELD loses connection to the ECM and cannot obtain any required data sources (engine power, vehicle motion, miles driven, and engine hours) for more than 30 minutes during a 24-hour period, the vehicle and ELD have been re-started to resolve the issue, and the issue is still occurring T: Your ELD is not properly synchronized with your current time zone. Please re-start the vehicle or check your connection. -NOTE: If upon re-connect, the ELD is still not obtaining required data sources Timing Compliance Failure' alert will be sent to FMCSA. Driver will be notified, and issue will be resolved by FleetRover within 24 hours -Occurs when the ELD time is not properly synchronized with Coordinated Universal Time (UTC) so that the time is inaccurate by 10 minutes or more at any time. L: Occurs when an ELD doesn’t acquire a valid position measurement within 5 miles of the vehicle’s movement during a cumulative 60-minute or greater period of 24 hours. Driver will be notified, and issue will be resolved by FleetRover within 24 hours R: Data recording to your ELD device has continuously failed. This malfunction will be noted to the FMCSA and a FleetRover representative will contact you shortly for resolution -Occurs when an ELD can no longer record or retain required data or retrieve recorded logs. R: You have not entered your location. We will notify the FMCSA of the malfunction and the non-entry -Occurs when an ELD doesn’t acquire a valid position measurement within 5 miles of the vehicle’s movement during a cumulative 60-minute or greater period over 24 hours, the driver has been asked to enter their location and has not for 24 hours S: The data transfer process has failed because your profile is missing some vital information. Please check that you are not in Unidentified Driving Mode and that timing is synchronized. -Occurs when user attempts to use the Telematics services and the attempt is unsuccessful because some necessary information is missing from the application ** O: No other malfunction event alerts are implemented in the FleetRover application at this time. This is to confirm that the FleetRover ELD has been deemed to be fully FMCSA compliant by FleetRover Inc. Thorough testing of the procedures outlined in the FMCSA-released document "Electronic Logging Device (ELD) Test Plan and Procedures" was conducted throughout the development process to ensure that the model met the technical specifications required.
Contractor Elogs MC3 1.5.5 MC3ELD Download Download MachineLINK (573) 310-7902 info@estrack.com https://www.estrack.com 2511 Broadway Bluffs Dr Ste 202, Columbia, MO 65201 The certified method of transferring data is via email. 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. 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 1.5.5 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.
Trimble Oil & Gas - WinCE ELD 5531+PD4 20043 or higher TOGS03 Download Download Trimble Oil and Gas Services 1.877.261.2962 support@geotracinternational.com http://oilandgas.trimble.com 4400 Baker Road, Minnetonka/MN/55343-8684 The solution will use Option 1 - Wireless Data Transfer Mechanism. The ELD will support both the Web Services method and the email Method. To use the Data Transfer mechanism over Email or Web Service the Driver or Official will follow these steps: 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” Driver or Official will be presented with 2 buttons labelled Email and Web Service respectively. Pressing the Email button will initiate the Email data transfer mechanism. Pressing the Web Services button will initiate the web services data transfer mechanism. Note that the latter will be disabled until the FMCSA has released the URL to send the data to. 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 Trimble Oil and Gas - WinCE ELD certifies based on Trimble Transportation 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 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.
LB Tech HOS (iOS Geometris) LBT26011 1805.0315.1 ELDLB1 Download Download LB Technology Inc. 901-480-8834 woxley@lbtelematics.com www.lbtelematics.com 5100 Poplar Ave Suite 2104, Memphis TN 38137 The LB Technology 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 LB Technology 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 LB Technology's 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 LB Technology 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. The LB Technology ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The LB Technology ELD was installed on various types and sizes of iOS phones and tablets. Testing was performed using a J1939 simulator and actual vehicles while having been connected to a Geometris.
Compliance Now - Hours of Service - IFTA Android & CalAmp 4230 1621.6202 or higher 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.
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 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 can only be cleared automatically and will be cleared once the corresponding problem addressed by a motor carrier. 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.
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.
Locus ELD ELD002 1625.6584 or higher ELD001 Download Download Locus GPS (888) 643-6862 info@locusgps.com www.locusgps.com 2920 Arabian PL, Marietta, GA 30062 The Locus 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 the Locus 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. The Locus 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 Locus 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 Locus ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The Locus 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 Pacific Track 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.
Hours Of Service Android & Xirgo 1.0.1801.11819 HOS001 Download Download VisTracks, Inc. 630-596-5420 info@vistracks.com http://www.vistracks.com/ 801 Warrenville Road, Lisle, IL 60565 The 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 the 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. The 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, 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 VisTracks Hours of Service (HOS) App was certified by the VisTracks testing team through successful execution and verification of the FMCSA ELD Test Procedures. The HOS App 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 Xirgo engine connected device. A few of the test procedures, which are relevant to Motor Carriers, were verified through the use of the VisTracks HOS web application (portal) that can be accessed through a web browser.
Uptake ELD UP001 1.1 or above UPELD1 Download Download Uptake Technologies, Inc +13122422300 support@uptake.com https://www.uptake.com/ 600 W Chicago Ave #620, Chicago, IL 60654, Chicago, IL, 60654 Step 1. If not logged in, login to Uptake ELD with driver email and password. Step 2. Select Inspections tab at bottom of screen. Step 3. Select Share icon in upper right of screen. Step 4. Under “Choose Delivery Method,” select Email or Web transfer. Step 5. If necessary, add an annotation by selecting the notes field. Step 6. Select the “Send” button at bottom of the screen. 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. 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. 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. 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. 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. 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. Uptake conducted a thorough review of the Appendix to Subpart B of Part 395 of CFR Title 49 and mapped the Appendix's requirements against Uptake's solution's features and functions. Uptake tested its developed solution by activating the solution (i.e., logging in to the application and pairing with the telematics device in a motor vehicle) and by otherwise following certain procedures described in the FMCSA's Electronic Logging Device (ELD) Test Plan and Procedures, Version 2.1 (published July 18, 2017).
Konnect Shift ELD GS01 1.0.0 or above KS1ELD Download Download KonnectShift Technologies Inc. +1(855) 244-1755 info@konnectshift.com http://konnectshift.com 1 King St. W Suite 4800 - 121 Toronto, ON, M5H 1A1, Toronto We support Telematics Transfer methods of 4.9.1 of Appendix A to Subpart B of 49 CFR 395. Using the Konnect Shift Driver app, drivers can initiate a data transfer using wireless webservices or using email. Drivers can initiate a data transfer via the Inspection button on the HOS main page. This will allow for an Inspection Officer to review logs via the the mobile display, or transfer logs via webservices or email as desired. As required by 4.6.1 of the ELD Rule, our ELD self-monitors for the conditions listed in Table 4. Any detected malfunctions are visually indicated on the ELD system as required by 4.6.2.1. and is reported as required in ELD data file. KonnectShift's ELD was certified by the KonnectShift's testing team through successful execution and verification of the FMCSA ELD Test Procedures.The ELD was tested according to the ELD Compliance Test Plan and procedures provided by the FMCSA to ELD Manufacturers at https://www.fmcsa.dot.gov/hours-service/elds/eld-test-procedures. KonnectShift test personnel performed each required test according to the provided test steps in order to verify that the actual test outcome matched the expected test outcome as provided.The ELD complies the FMCSA safety regulations (ELD Rule).
MasterELD MELD02 MELDA2.0 MWLA01 Download Download NATIONAL TRANSPORTATION PARTNERS LLC 630-422-7497 eld@mastersafetyinc.com http://www.mastereld.com 1040 BORDEN DR., ROSELLE, IL 60172, ROSELLE / IL / 60172 *There is a section in uploaded manual that describes and showcases data transfer mechanism with colors and visual cues. INSPECTION MasterELD provides an easy way for a driver to produce and transfer the ELD records to an authorized safety official and supports TELEMATICS transfer method. TO PRODUCE LOGS ON THE SCREEN: 1. Tap on the Menu icon on the top left. 2. Select Inspection Module from the Menu. 3. To let an authorized safety official inspect your logs directly from your device, tap “Begin Inspection”. 4. Give the authorized safety official your mobile device. 5. Tap the Back arrow on the top left to exit Inspection Module. TELEMATICS WIRELESS TRASFER: 1. Tap on the Menu icon on the top left. 2. Select Inspection Module from the Menu. 3. To submit ELD Output File directly to the DOT, tap “Send Output File”. 4. Give the authorized safety official your mobile device to enter the code. 5. Tap “Send” to submit ELD Output File. TELEMATICS EMAIL: 1. Tap Send Logs from Inspection Module screen. 2. Tap the checkbox next to each log you want to send. 3. Choose the transfer method by clicking on “Email” or “Fax” tab. 4. Enter the email address or fax number of the authorized safety official. 5. Tap Send to email 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 MasterELD App if you choose to provide the authorized safety official with hard copy. MasterELD is made to transfer data wirelessly via Web Services and follows the standards put forward by FMCSA in article 4.10.1.1. MasterELD 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. Contact MasterELD support immediately at support@mastereld.com 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, MasterELD 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 MasterELD. Upon completion of necessary tests outlined in the above named document we certify that MasterELD 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
Titan GPS Logbook TT1800 ELD Android 1.0.1619.5947 and up THOS01 Download Download Certified Tracking Solutions 7803913800 info@ctstracking.com http://titangps.ca 4320 Savaryn Dr SW, Edmonton/Alberta/T6X 1Z9 The Titan Logbooks 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. 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 Titan Logbooks 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 Titan Logbooks 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 Titan Logbooks 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 Titan Logbooks ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The Titan Logbooks 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 access through a web browser.
Mobile Dispatch VNA2-ELD MD App 47 or higher ACVNA2 Download Download Acordex, LLC 978-975-8000 web-service@acordex.com acordex.com 37 Walker Rd, N Andover, MA 01845 Data transfer is by e-mail wireless transfer through e-mail or web services as described in section 4.10.1.2 of the FMCSA Electronic Logging Devices and Hours of Service Supporting Documents. Driver Procedure 1. On the tablet, tap on "ELD" at the bottom of the screen. 2. Tap on "Send". 3. There is a comment field to put in a key phrase or code given by the DOT official. 4a. To send by e-mail, type the appropriate e-mail address in the Email field then tap "Send by Email". This will e-mail the ELD date for the current day and the previous 7 days. 4b. To send by web services just tap "Send by Web". This will transmit the ELD data for the current day and the previous 7 days. DIAGNOSTICS 1: Power data diagnostic event No response from the Engine Connection Device (ECD, hardware on the J-bus), after multiple retries to connect. 2: Engine synchronization data diagnostic event If data is not provided when required, a Diagnostic 2 will be issued in less than 5 seconds. Multiple data points are required at least twice per minute while the truck is moving. 3: Missing required data elements data diagnostic event Location unavailable when duty status changes. 4: Data transfer data diagnostic event Failure at the tablet will generate Malfunction R. Email or web-service failures are logged/displayed at the office. 5: Unidentified driving records data diagnostic event Total driving time in 24 hours exceeds 30 minutes with no driver logged in. MALFUNCTIONS P: Power compliance Diagnostic 1 occurs for more than 30 minutes in a 24 hour period E: Engine synchronization compliance Diagnostic 2 occurs for more than 30 minutes in a 24 hour period T: Timing Compliance Difference between time at server and time on tablet is 3 or more minutes. L: Positioning Compliance No geoposition from ECD after startup Last geoposition received 5 or more minutes ago Last geoposition invalid R: Data recording compliance Out of room on tablet for saving records that should be uploaded to the server (prolonged, persistent cell network failure). S: Data transfer compliance Failed to send the ELD data output file Testing of the ELD has been performed following the protocol described in the ELD Test Plan and Procedures Version 1.0 dated 4/25/2016.
GPSi Fleet RDT5 1.0 CFMRDT Download Download GPSi 8552511010 chris.rotolo@gpsindustries.com http://www.gpsindustries.com/ 1074 N Orange Avenue, Sarasota, Florida 34236 The RDT5 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. Data transfer is initiated by touching the HOS button on RDT5 screen to display the HOS inspection view, then the Send button to select the transfer function. The RDT5 then prompts for the Output File Comment, which must be entered before the transfer can be initiated. Once a comment has been entered, the Send button is touched to initiate the transfer. The transfer is completed via Web Service using the FMCSA SOAP endpoint. The RDT5 continually self-monitors for a variety of malfunctions, including: • Device power (loss of power causing gaps in vehicle odometer) • Vehicle synchronization (errors in diagnostic port communications) • Timing (failure in server UTC synchronization) • Position (failure in GPS subsystem) • Data recording (failure to store events locally or transfer to server) • Data transfer (failure to initiate a requested data transfer to FMCSA) • Other (failures that impair accuracy or completeness of ELD operation, such as memory corruption, file system failure, or input device failure) In each case the RDT5 records a data diagnostic event at the beginning and end of the malfunction condition. While any malfunction is occurring, the RDT notifies the driver by indicating the failure type in the footer section of the display, with white lettering on red background. The RDT5 was certified through successful execution and verification of the FMCSA ELD Test Procedures. Testing was performed using a J1939 simulator, and by connection to a variety of vehicles via the J1939 and J1708 diagnostic connectors. Some of the test procedures, which are relevant to Motor Carriers, were verified using the companion Web application, accessible from computer, tablet, or smart phone.
Transmission Transmission 1.0 1.0 TMSN01 Download Download Transmission, LLC ‭1-855-220-0790‬ sales@transmissionapp.com http://www.transmissionapp.com/ 760 Market St. 8th Floor, San Francisco, CA Transmission’s ELD supports both email and web transfer mechanisms for transferring ELD records to an authorized safety official. In order to produce and transfer ELD records, a driver must take the following actions within the mobile application: 1. Tap "DOT Inspection" in the "Logs tab." 2. Select "Send Logs." 3. After selecting "Send Logs," the user may select either "email" or "web transfer." Transmission’s ELD supports all functional requirements pursuant to Appendix A, Subpart B of Part 395 of the ELD Final Rule and can detect diagnostic events and malfunctions accordingly. Transmission's ELD is capable of detecting the following malfunctions: “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 I certify, on behalf of Transmission LLC (“Transmission”), that the Transmission 1.0 product meets the functional requirements pursuant to Appendix A, Subpart B of Part 395 of the ELD Final Rule. Transmission LLC tested its Transmission 1.0 product using the Electronic Logging Device (ELD) Test Plan and Procedures published by the FMCSA, dated July 18, 2017. The Transmission product and engineering team completed the testing exercises outlined in the Test Plan and Procedures, and coordinated with our third party service provider as necessary in the completion of the testing exercises.
GFI eLogs Android Calamp 4230 and Calamp 3030 1.0.1805.0315 GFI002 Download Download GFI Systems Inc. 1-855-434-4477 eld@gfisystems.ca http://www.gfisystems.ca 500 10709 Jasper Ave., Edmonton, Alberta The GFI eLogs 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 GFI eLogs 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 GFI eLogs 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 GFI eLogs 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 GFI eLogs ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The GFI eLogs 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 CalAmp 4230 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.
Zeek GPS Blue Link 3.0.6 WLI001 Download Download ARGUS TECNOLOGIAS S.A. DE C.V. +52 664 215 0657 info@zeekgps.com http://zeekgps.com Blvd. Las americas, 4271 Fracc. El paraiso , Tijuana, B.C. 22106 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 our ELD application and related hardware have been tested to meet the FMCSA's test procedures.
StreetEagle ELD with Samsung Galaxy Tab E (Verizon) ELDSAM 1.1.0.0 or above ELDSAM Download Download InSight Mobile Data, Inc. (301) 866-1990 info@insightmobiledata.com www.insightmobiledata.com 23330 Cottonwood Parkway, Suite 333, California, MD 20619 1. Open the app 2. Click on View Logs 3. Click on Email Logs 4. Click send Logs In addition to the malfunction and diagnostic event handling required by the ELD regulation, 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. 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.
ELD Fleet Android & Calamp 3640 1.0.1824.190107 ELDFLT Download Download GPS Trackit (866) 320-5810 FleetAdvisor@GPSTrackit.net https://gpstrackit.com/eld-fleet/ 27244 Vía Industria, Temecula, CA, 92590 Data Transfer Description – Android Registrations The ELD Fleet™ 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 ELD Fleet™ 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 ELD Fleet™ 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 ELD Fleet™ 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 ELD Fleet™ 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 Fleet™ 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 ELD Fleet™ ELD was certified through successful execution and verification of the FMCSA ELD Test Procedures. The ELD Fleet™ 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 CalAmp 4230 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.
TheTMS ELD Product Solution 1.118 1.111 060215 Download Download THETMS Inc 7083307920 jrediehs@t-tms.com www.t-tms.com 800 W 79th St Suite 4, Willowbrook/IL/60527 • Description of the supported and certified data transfer mechanisms and step-by-step instructions for a driver to transfer ELD records to an authorized safety official. • During a Roadside DOT inspection you can enter the “DOT Inspection Mode • Navigate to the Home Screen Click on “DOT Inspection Mode” and hand it to the officer • The next screen will give the officer two options: o 1. Inspect Logs for previous 7 days + today “Begin Inspection ? If the officer chooses this option he can easily navigate the last 7 days in logs directly on the screen o 2. “Send Logs” Choice will email the logs to the officer for further review ? It will prompt the user to enter an email address ? Once the email is entered hit submit and the system will send DOT certified formatted Logs to the officers or governing bodies email account, with the correct Subject headers and format ? The Officer than can navigate between dates with the arrows on either side of the date ? When the officer is complete navigate back to the home page by selecting home from the accordion option o All Malfunctions will be reported in pop up form for the user to easily Identify from any screen on the device, it will report the error occurring and suggest activities for correcting the error the unit and user are experiencing. Below is a list of Malfunctions required by the FMCSA and the corresponding error in theTMS ELD solution. o P – “Power Compliance” malfunction ? TheTMS equivalent – “P” - “Plug in Device is not powered on” o E – “ Engine Synchronization compliance ? TheTMS equivalent – “E” – “Engine synchronization data diagnostic” – Explaination: Looks like the ECM has lost connection with the ELD. Please restart the engine, check the connection of your ELD device and restart mobile app” o T – “Timing compliance: malfunction ? TheTMS equivalent – “T” “ELD timing is not working properly” ? Explaination: Looks like the ELD device has a timing issue. Please restart the engine, check the connection of your ELD device and restart mobile app” o L – “Positioning Compliance” malfunction ? TheTMS equivalent – “L” ELD system cannot not properly determine positioning ? Explanation: Looks like the ELD device has a GPS issue. Please restart the engine, check the connection of your ELD device and restart mobile app” o R – “Data recording Compliance” Malfunction ? TheTMS equivalent – “R” “Missing Required Data Elements data diagnostics” ? Explanation: Looks like some of the data fields are missing at the time of recording, please restart the engine, check the connection of your eld device and restart the mobile app. o S – “ Data Transfer compliance” Malfunction ? TheTMS equivalent – “S” “Data transfer data compliance” ? Explanation: Looks like the data is not getting transferred from the ELD please restart the engine, check the connection of your ELD device and restart the mobile app. o O – “Other” ELD detected Malfunction ? TheTMS equivalent – “O” “Un-identified error is occring” ? Explanation: Something went wrong restart the engine, check the ? connection of your ELD device and restart the mobile app. o 1 – Power Data diagnostics ? Thetms Equivalent: “1” Power diagnostics issues --- prompt user to restart system o 2 – Engine synchronization data diagnostics ? Thetms Equivalent: “2” Engine and ELD synchronization diagnostics issues --- prompt user to restart system, check connection of device, and reconnect to the ELD o 3 – Missing required data elements data diagnostics ? Thetms Equivalent: “3” Data “xyz” elements are missing from ELD logs --- Prompt user to restart system, check connection of device, and reconnect to the ELD o 4 – Data Transfer data diagnostic ? Thetms Equivalent: “4” Attempting to Reconnect Data Transfer --- prompt user to restart system if connection is not made o 5 – Unidentified Driving Record Data Diagnostics ? Thetms Equivalent: “5” Unidentified Driving Record Found ---- Prompt user to sign into the APP to claim unassigned events o 6 – Other ? Thetms Equivalent: “6” An error has occurred --- Prompt user to let them know that a general system diagnostic is taking place to Identify issue TheTMS ELD Product Solution was against all of the command, scenarios, and criterias listed out in the "Electronic Logging Device (ELD) Test Plan and Procedures Version 2.0. The testing environment for in lab and outside in CMV met the criteria for testing. Testing was performed between the dates of 10/15/16 through 1/03/2017 by Darpan Dalal and Yatendra Singh. Each Specific requirement was tested and documented per the requirements of the document of Date, ID, Outcome, and comments. If any component did fail we documented as a deficiency/defect and had to re run it again. All test were performed three time before a passing mark was given and each time the unit needed to pass the requirement 3 times in a row. Regression testing was implemented where necessary, for elements that failed any part of the testing. To best of our knowledge based on the results from testing this product meets all of the qualifications listed in Appendix to subpart B of part 395, title 49 of the Code of Federal Regulations.
GTS ELD GTSELD_TK_100 V1.5.8 GETK10 Download Download Global Telecommunication Services, Inc. 5127458888 eld@elog123.com https://elog123.com 209 E Newman Ave., , Arcadia, CA 91006 ELD collected raw data is transferred via wireless data transfer prototype in JSON format to company specified URL. ELOG required data and report are generated and stored in company ELOG server cluster. All ELOG required data/report have two ways to obtain: 1 download from website 2 email as PDF attachment. ELD raw and intermediate log and tracking related data is available by output to flat and delimtered text file or excel file and email out. Power failure Data collection failed Data local storage full Data transfer failed Device heartbeat lost GTS ELD has been tested through hardware and software in order to comply with FMCSA ELD regulation. Hardware testing has phases of power, data collection, data precision, data transfer. Software testing has unit tests over Fleet Management Module, Trip and Event Module, ELOG Report Module (including sub modules of Generation, Certification, Final Preparation, Report Delivery Service), Roadside Inspection. An integrated system testing is followed thereafter.
V-Track V-HOS2 1.0 VSIOS1 Download Download Velocitor Solutions 7047315388 sales@velsol.com http://www.vtrackfm.com 851 Blairhill Rd, Charlotte/NC/28217 Electronic Transfer Supported via Web Service and Email. Tap on DOT Inspection Mode. Choose Email or Web Service. Enter File Comment if necessary. Tap Send. Power Compliance, Engine Synchronization Compliance, Time Compliance, Positioning Compliance,Data Recording Compliance, Data Transfer Compliance. I certify after extensive testing that V-Track complies with the rules set within FMCSA's requirements for ELD.
ACCURATE ONE RT-ONE-BT01 1.3.3.241 (02/13/19) RTOA47 Download Download Rollingtrans.com (844) 538-7267 info@rollingtrans.com https://rollingtrans.com 10501 Valley Blvd Suite 1806, Pasadena, CA, 91101 Please click MENU - OTHERS - DOT. Except showing current day’s HOS chart, you can also find Icons on the bottom which allows you to export and transfer your HOS data in the following method. Data Transfer will follow FMCSA ELD final rule data transfer option 1 (4.10.1.1)to transfer exported data via wireless web service and email to safety authority officer's designated mail address. Export Data and email By Click Export Log data, you can export your Log data to your wireless device local storage.The ELD App will attach a file to an email message to be sent using RFC 5321 Simple Mail Transfer Protocol (SMTP) , to a specific email address. When the ELD system app or ELD hardware fail to perform log record please check Malfunction code and Data Diagnostic code as following to identify system problem. Malfunction Code 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 Diagnostic Code 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 According to the ELD final rule and technical specification sheet on FMCSA website. Rollingtrans has performed necessary test, do hereby certify that ACCURATE ONE has met the technical specifications base on the following testing: • ELD hardware interpreter has performed vehicle connection test that can capture more than 30 different brand and model’s truck which using SAE J1939 and SAE J 1708 protocol. • The vehicle ECM operating data can be read and transferred to wireless device (Smartphone and Tablet) from ELD interpreter via Bluetooth connection. • ELD hardware interpreter can read the following data and transfer to Wireless device via Bluetooth connection o Engine On/Off o Engine RPM o Vehicle Velocity o Vehicle miles o Engine hours • ELD system App can capture following information from wireless device o GPS location o Date and Time ELD HOS log data display and transfer • ELD System App can keep driver’s HOS log data in local device for at least 7 consecutive days. • ELD System App can display driver’s HOS chart at current day and past 7 days • With connection to wireless web service, ELD system App can transfer HOS chart and Log data to authorized safety officers via email, message in PDF and text file format. • Android ELD System App can export driver’s log data to wireless device’s local storage. The data file can transfer to authorized safety officer’s laptop or computer via USB 2.0 cable.
RCO ELD RCO001 1.3.21 AGF001 Download Download RCO Services 310-451-3735 royn@rco.com http://www.rco.com 2170 Georgina Avenue, Santa Monica, CA 90402 RCO ELD for iOS supports telematics Data Transfer. To transfer data the driver needs to tap in the "Logs" button from the bottom toolbar in the Logs Screen, and then select "Log". The driver will see the ELD Screen which displays ELD information for the current day and the list of the events. To transfer data the driver needs to tap on the "Action" button from the top toolbar (top right) and select from the list: "Transfer RODS". This will show a popup that will ask the driver to select data Transfer method: Email or Web Services, after selecting the method a popup a popup with a input will be shown to enter the "Output File Comment". After entering the comment driver needs to tap on the "Add" button and the transfer will be made using the selected method to the FMCSA. Email ELD Transfer File requires several steps: 1.) The entire email is encrypted using AES encryption with the FSCSMA public key. 2.) The email is signed using SHA with the ELD provider private key. At the FSCMA to validate the ELD the following steps: 1.) The email is decrypted using the FSCMA certificate privated key 2.) The signature of the ELD email is checked by decrypting using the provider public key ELD functionality has 2 components: 1. iOS application that is running on a iOS device (iPhone or iPad with a data plan) 2. Digi WVA (Wireless Vehicle Bus Adapter) J1939 device iOS application is connecting wireless to the WVA d