Products with ELD "ISACTL"
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.
ISAAC InControl
| Vendor | Device Name | Model Number | Approved Version |
|---|---|---|---|
| | ISAAC InControl | WRU1K2-HNx, WRU1K8-HNx, WRU201 | 4.50 and higher |
Data Transfer and Reporting Procedures
> Telematic (Web Service, Email)Malfunctions and Testing
The solution supports the option 1 of the ELD requirements. Option 1—Telematics transfer methods. Transfer the electronic data using both: 1) Wireless Web services 2) Email The step-by-step instructions to produce and transfer the ELD records to an authorized safety official are: 1) Tap Roadside inspection on the activities page. 2) Tap the Transfer ELD button. 3) Select the transfer method: Web services or Email. 4) Enter a comment. 5) Tap Send.Certification Statement
Compliance Malfunctions and Data Diagnostic Events Power diagnostic event Description: the electronic logging device (tablet) 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 Required action - Make sure the key in the ignition is in the ON position, and the tablet is correctly inserted in its cradle. For further diagnostics, contact ISAAC Instruments technical support team. Power compliance malfunction Description: The electronic logging device (tablet) is not powered for an aggregated in-motion driving time of 30 minutes or more over a 24-hour period across all driver profiles Required action: Inform the transporter of the malfunction. Use compliant paper logs to reconstruct the record of service hours for the current 24-hour period and the previous 7 consecutive days. Continue recording hours of service on compliant paper logs until the electronic logging system is back in compliance. Engine synchronization diagnostic event Description: The electronic logging system loses ECM connectivity to any of the required data sources (engine power status, vehicle motion status, miles driven, and engine hours) and can no longer acquire updated values for the required ELD parameters within five seconds of the need. Required action: This usually occurs while the recorder is performing a firmware update. Communication generally returns on its own after a few minutes. If this state persists, contact ISAAC’s technical support team. Engine synchronization compliance malfunction Description: The electronic logging system connectivity to any of the required data sources (engine power status, vehicle motion status, miles driven, and engine hours) is lost for more than 30 minutes during a 24-hour period aggregated across all driver profiles Required action: Inform the transporter of the malfunction. Use compliant paper logs to reconstruct the record of service hours for the current 24-hour period and the previous 7 consecutive days. Continue recording hours of service on compliant paper logs until the electronic logging system is back in compliance Time Compliance malfunction Description: The electronic logging system can no longer 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 Required action: Inform the transporter of the malfunction. Use compliant paper logs to reconstruct the record of service hours for the current 24-hour period and the previous 7 consecutive days. Continue recording hours of service on compliant paper logs until the electronic logging system is back in compliance Positioning Compliance malfunction Description: The electronic logging system fails to acquire a valid position measurement within 5 miles of the commercial motor vehicle moving and 60 minutes has passed, a “position compliance malfunction” will be recorded in the data diagnostic Required action: Inform the transporter of the malfunction. Use compliant paper logs to reconstruct the record of service hours for the current 24-hour period and the previous 7 consecutive days. Continue recording hours of service on compliant paper logs until the electronic logging system is back in compliance. Data recording Compliance malfunction Description: The electronic logging system can no longer record or retain required events or retrieve recorded logs that are not kept remotely by the motor carrier Required action: Inform the transporter of the malfunction. Use compliant paper logs to reconstruct the record of service hours for the current 24-hour period and the previous 7 consecutive days. Continue recording hours of service on compliant paper logs until the electronic logging system is back in compliance Missing required data elements diagnostic event Description: Any required data field is missing at the time of its recording Required action: No immediate action is required. Missing data events are monitored by ISAAC’s electronic logging system, and in the event they persist, will generate a compliance malfunction listed in this table. Data transfer diagnostic event Description: The operation of the data transfer mechanism(s) is not confirmed Required action: Alternatively, you can display requested information to roadside authorities directly on the tablet. The data transfer mechanism will be unsuccessful when no cellular communication is available, and will resume when communication returns. If data transfer fails when cellular communication IS available, contact ISAAC’s technical support team. Data transfer Compliance malfunction Description: The electronic logging device (tablet) stays in the unconfirmed data transfer mode following the next three consecutive monitoring checks Required action: Inform the transporter of the malfunction. Use compliant paper logs to reconstruct the record of service hours for the current 24-hour period and the previous 7 consecutive days. Continue recording hours of service on compliant paper logs until the electronic logging system is back in compliance Unidentified (unassigned) driving records diagnostic event Description: More than 30 minutes of driving time for an unidentified driver is recorded within a 24-hour period Required action: No immediate action is required. When logging into ISAAC’s tablet, you are advised of and can claim unidentified (unassigned) driving time for the vehicle. Remaining unclaimed driving hours are visible to office personnel with ISAAC’s reporting.
User Manual: 
ISAAC OnTheGo - Basic Quick Reference - Rev2.pdf
ISAAC InControl
| Vendor | Device Name | Model Number | Approved Version |
|---|---|---|---|
| | ISAAC InControl | WRU1K2-HNx, WRU1K8-HNx, WRU201 | 5.08 and higher |
Data Transfer and Reporting Procedures
> Telematic (Web Service, Email)Malfunctions and Testing
The solution supports the option 1 of the ELD requirements. Option 1—Telematics transfer methods. Transfer the electronic data using both: 1) Wireless Web services 2) Email The step-by-step instructions to produce and transfer the ELD records to an authorized safety official are: 1) Tap Roadside inspection on the activities page. 2) Tap the Transfer ELD button. 3) Select the transfer method: Web services or Email. 4) Enter a comment. 5) Tap Send.Certification Statement
Compliance Malfunctions and Data Diagnostic Events Power diagnostic event Description: the electronic logging device (tablet) 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 Required action - Make sure the key in the ignition is in the ON position, and the tablet is correctly inserted in its cradle. For further diagnostics, contact ISAAC Instruments technical support team. Power compliance malfunction Description: The electronic logging device (tablet) is not powered for an aggregated in-motion driving time of 30 minutes or more over a 24-hour period across all driver profiles Required action: Inform the transporter of the malfunction. Use compliant paper logs to reconstruct the record of service hours for the current 24-hour period and the previous 7 consecutive days. Continue recording hours of service on compliant paper logs until the electronic logging system is back in compliance. Engine synchronization diagnostic event Description: The electronic logging system loses ECM connectivity to any of the required data sources (engine power status, vehicle motion status, miles driven, and engine hours) and can no longer acquire updated values for the required ELD parameters within five seconds of the need. Required action: This usually occurs while the recorder is performing a firmware update. Communication generally returns on its own after a few minutes. If this state persists, contact ISAAC’s technical support team. Engine synchronization compliance malfunction Description: The electronic logging system connectivity to any of the required data sources (engine power status, vehicle motion status, miles driven, and engine hours) is lost for more than 30 minutes during a 24-hour period aggregated across all driver profiles Required action: Inform the transporter of the malfunction. Use compliant paper logs to reconstruct the record of service hours for the current 24-hour period and the previous 7 consecutive days. Continue recording hours of service on compliant paper logs until the electronic logging system is back in compliance Time Compliance malfunction Description: The electronic logging system can no longer 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 Required action: Inform the transporter of the malfunction. Use compliant paper logs to reconstruct the record of service hours for the current 24-hour period and the previous 7 consecutive days. Continue recording hours of service on compliant paper logs until the electronic logging system is back in compliance Positioning Compliance malfunction Description: The electronic logging system fails to acquire a valid position measurement within 5 miles of the commercial motor vehicle moving and 60 minutes has passed, a “position compliance malfunction” will be recorded in the data diagnostic Required action: Inform the transporter of the malfunction. Use compliant paper logs to reconstruct the record of service hours for the current 24-hour period and the previous 7 consecutive days. Continue recording hours of service on compliant paper logs until the electronic logging system is back in compliance. Data recording Compliance malfunction Description: The electronic logging system can no longer record or retain required events or retrieve recorded logs that are not kept remotely by the motor carrier Required action: Inform the transporter of the malfunction. Use compliant paper logs to reconstruct the record of service hours for the current 24-hour period and the previous 7 consecutive days. Continue recording hours of service on compliant paper logs until the electronic logging system is back in compliance Missing required data elements diagnostic event Description: Any required data field is missing at the time of its recording Required action: No immediate action is required. Missing data events are monitored by ISAAC’s electronic logging system, and in the event they persist, will generate a compliance malfunction listed in this table. Data transfer diagnostic event Description: The operation of the data transfer mechanism(s) is not confirmed Required action: Alternatively, you can display requested information to roadside authorities directly on the tablet. The data transfer mechanism will be unsuccessful when no cellular communication is available, and will resume when communication returns. If data transfer fails when cellular communication IS available, contact ISAAC’s technical support team. Data transfer Compliance malfunction Description: The electronic logging device (tablet) stays in the unconfirmed data transfer mode following the next three consecutive monitoring checks Required action: Inform the transporter of the malfunction. Use compliant paper logs to reconstruct the record of service hours for the current 24-hour period and the previous 7 consecutive days. Continue recording hours of service on compliant paper logs until the electronic logging system is back in compliance Unidentified (unassigned) driving records diagnostic event Description: More than 30 minutes of driving time for an unidentified driver is recorded within a 24-hour period Required action: No immediate action is required. When logging into ISAAC’s tablet, you are advised of and can claim unidentified (unassigned) driving time for the vehicle. Remaining unclaimed driving hours are visible to office personnel with ISAAC’s reporting.
User Manual: ISAAC OnTheGo - Quick Reference - V5.11 - Rev1.pdf