TruckRec

Electronic Logging DeviceCesiumai USA Inc. TruckRec
Model NumberH100
ELD ID NumberC201EX
Software Version2.0

Model Information

Data Transfer MethodsAfter 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.
Malfunction NotesOur 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.
Certifying StatementThis 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.

Company Information

ManufacturerCesiumai USA Inc.
Websitehttp://www.cesiumai.com/us/
Contact Email[email protected]
Contact Phone Number5109289909
Address925 Adams St., Albany, CA, 94706

Devices From Cesiumai USA Inc.


Related ELDs


This site's data is aggregated programmatically and provided "as is" without any representations or warranties, express or implied. Transportation.report is not affiliated with the DOT, the NHTSA, or the US government in any way.

© 2024 Transportation.Report | ELDs | About