Electronic Logging DeviceHawk Eye Log Global Technology Ltd HawkEye ELD IOSIX
Model NumberHELD01
Software VersionV2.0.0

Model Information

Data Transfer MethodsHawkeye 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.
Malfunction NotesHawkeye 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.
Certifying StatementHawkeye 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 11. ElD Device (IOSIX ELD) was verified to compliance with the ELD rule

Company Information

ManufacturerHawk Eye Log Global Technology Ltd
Contact Email[email protected]
Contact Phone Number855.588.4295
Address311-3381 Cambie St, Vancouver, BC. V5Z 4R3

Devices From Hawk Eye Log Global Technology Ltd

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.

© 2022 Transportation.Report | Definitions