| Electronic Logging Device | EveryFleet EveryFleet |
| Model Number | LMU-4230 |
| ELD ID Number | VC4230 |
| Software Version | v1 |
Model Information
| Data Transfer Methods | Data Transfer Description Vika ELD Data can be transferred to FMCSA through email or web service. To produce and transfer the ELD records to an authorized safety official driver need to follow these steps. Login to vika driver app Go to HOS page from left navigation menu From HOS page click on DOT button available in header section This page can be shown to safety officer for logs of that day and last 7 days Click on paper plane icon in header section of the DOT Page to transfer to FMCSA It will show 2 methods to transfer the data (Email or web service) Driver can choose a method to transfer logs of that day to FMCSA |
| Malfunction Notes | Summary of Malfunctions “Power compliance” malfunction: An ELD must be powered and become fully functional within 1 minute of the vehicle’s engine receiving power and must remain powered for as long as the vehicle’s engine stays powered. ELD app monitor when the device may not have complied with the power source. If the aggregated in-motion driving time increases 30 minutes or more on the ELD over a 24-hour without power source, it creates power compliance malfunction. “Engine synchronization compliance” malfunction: ELD app monitor the data it receives from the engine ECM for power, vehicle motion status, vehicle miles, Engine hours. ELD set an engine synchronization compliance malfunction if connectivity to any of these data sources is lost for more than 30 minutes during a 24-hour period aggregated. “Timing compliance” malfunction: The ELD periodically cross-check its compliance with respect to an accurate external UTC source and it record a timing compliance malfunction when it no longer meet the requirement. “Positioning compliance” malfunction: ELD monitor elapsed time during periods when the ELD fails to acquire a valid position measurement within 5 miles of the CMV’s movement. When such elapsed time exceeds a cumulative 60 minutes over a 24 hour period, the ELD set and record a positioning compliance malfunction “Data recording compliance” malfunction: ELD detect a data recording compliance malfunction if it can no longer record or retain required events “Data transfer compliance” malfunction: ELD verifies data transfer functionality once every 7 days. If the monitoring mechanism fails to confirm proper in-service operation of the data transfer mechanism, ELD increases the frequency of the monitoring function to check at least once every 24-hour period. If the ELD stays in the unconfirmed data transfer mode following the next three consecutive monitoring checks, the ELD detect a data transfer compliance malfunction. |
| Certifying Statement | Certifying Statement of FMCSA Regulation Testing: I hereby certify that the Vika ELD / HOS / DVIR device has been built and tested to the specifications and regulations promulgated by the FMCSA and complies with all record keeping standards and requirements. Appendix to subpart B of part 395, title 49 of the Code of Federal Regulations, eldtestplanandprocedures07-18-201721-all-chapters.pdf ELD_ICD_Development_Handbook.pdf |
Company Information
| Manufacturer | EveryFleet |
| Website | https://everyfleet.com |
| Contact Email | [email protected] |
| Contact Phone Number | +1 (401) 821-2900 |
| Address | 141 James P. Murphy Ind. Hwy, West Warwick, RI 02893 |
Devices From EveryFleet
| Device | ID |
|---|---|
| EveryFleet EveryFleet | VC4230 |
Related ELDs
| ELD | ELD ID |
|---|---|
| Navistar, Inc. OnCommand(R) Connection Electronic Driver Log | OCC001 |
| HCSS HCSSELD | GEO84A |
| GPS Trackit ELD Fleet | ELDFLT |
| AAMP Global (Formerly M2M In Motion) M2MIM ELD | M2M018 |
| GPS Trackit ELD Fleet | ELDFLT |
| InTouch InTouch ELD - Android | ITELD1 |
| Satinder Singh Keep Truckin | KTIELD |