Products with ELD "SPARK6"
- Spark-ELD Version 1.0.0 and higher
- Sparkle-ELD Version 1.0.0 and higher
- Sparkle-ELD Version 3.6.0 and higher
Below you will find a list of products with the ELD "" obtained from our database, including their available manuals, documentation, and images.
Click the corresponding vendor name to obtain additional information on the manufactorer, as well as contact information for further troubleshooting.
Spark ELD
Vendor | Device Name | Model Number | Approved Version |
---|---|---|---|
Wema Solutions LLC | Spark ELD | PT40SIM | 1.0.0 and higher |
Data Transfer and Reporting Procedures
> Telematic (Web Service, Email)Malfunctions and Testing
We support the telematics transfer methods specified by the FMCSA: (1) wireless web services and (2) email. We also keep an in-app visual display for cases where the driver has no internet connection. The visual display includes a record of the current 24-hour period and the previous seven consecutive days of the driver’s logs, as required in section 4.10 of the mandate. For a driver to transfer their log information to a DOT officer, they will tap the “DOT Inspection” option from the mobile app’s menu and tap “Begin Inspection” for a visual inspection or “Transfer Data” to transfer log information via email or web services.Certification Statement
Our software continuously monitors our ELD system for compliance with the data requirements of the mandate. It supports the 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, as required in section 4.6 of the mandate.
Sparkle ELD
Vendor | Device Name | Model Number | Approved Version |
---|---|---|---|
Spark Technologies Inc. | Sparkle ELD | PT40SIM | 1.0.0 and higher |
Data Transfer and Reporting Procedures
> Telematic (Web Service, Email)Malfunctions and Testing
We support the telematics transfer methods specified by the FMCSA: (1) wireless web services and (2) email. We also keep an in-app visual display for cases where the driver has no internet connection. The visual display includes a record of the current 24-hour period and the previous seven consecutive days of the driver’s logs, as required in section 4.10 of the mandate. For a driver to transfer their log information to a DOT officer, they will tap the “DOT Inspection” option from the mobile app’s menu and tap “Begin Inspection” for a visual inspection or “Transfer Data” to transfer log information via email or web services.Certification Statement
Our software continuously monitors our ELD system for compliance with the data requirements of the mandate. It supports the 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, as required in section 4.6 of the mandate.
Sparkle ELD
Vendor | Device Name | Model Number | Approved Version |
---|---|---|---|
Spark Technologies Inc. | Sparkle ELD | PT40SIM | 3.6.0 and higher |
Data Transfer and Reporting Procedures
> Telematic (Web Service, Email)Malfunctions and Testing
We support the telematics transfer methods specified by the FMCSA: (1) wireless web services and (2) email. We also keep an in-app visual display for cases where the driver has no internet connection. The visual display includes a record of the current 24-hour period and the previous seven consecutive days of the driver’s logs, as required in section 4.10 of the mandate. For a driver to transfer their log information to a DOT officer, they will tap the “DOT Inspection” option from the mobile app’s menu and tap “Begin Inspection” for a visual inspection or “Transfer Data” to transfer log information via email or web services.Certification Statement
Our software continuously monitors our ELD system for compliance with the data requirements of the mandate. It supports the 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, as required in section 4.6 of the mandate.