User Manual Part 7

ManualsBrandsContinental Automotive Systems ManualsElectronicsTachograph

131

RoadLog Files

The Company Vehicle DVIR Data file includes:

• DVIR reports recorded no more than 30 days from the

last download.

The Company Vehicle DVIR Data file name structure is:

• Only created by the RoadLog: Carrier_CompanyID_

TractorNumber_yymmddhhmmss.CVD

• CompanyID: the USDOT number.

• yymmddhhmmss: time the file is created.

COMPANY CONFIGURATION SESSION FILE

The Company Configuration Session file contains

configuration session data recorded by RoadLog during

company log sessions. The file is created by RoadLog

whenever a user requests its download on a Driver Key or

Fleet Key belonging to the logged in company.

The Company Configuration Session File includes:

• The last 100 calibration sessions records.

The Company Configuration Session File name

structure is:

• Only created by RoadLog: Carrier_CompanyID_

TractorNumber_CalibrationData_yymmddhhmmss.CVD

• CompanyID: the USDOT number.

• TractorNumber is the number on which the RoadLog

device is installed.

• yymmddhhmmss is the time when the file is created.

COMPANY ASSETS PARTS LIST FILE

The Company Assets Parts List file contains the list of

predefined asset types used during RoadLog DVIR

inspection. It is uploaded to RoadLog memory during

company log in. The file is created by RoadLogFleet during

activation of the Fleet Key. The file is downloaded, when

requested by the user, only onto Fleet Keys belonging to the

logged in company.

The Company Assets Parts List file includes:

• A predefined list of vehicle parts, along with the related

possible defects for each part.

• A predefined list of trailer parts, along with the related

possible defects for each part.

• Optional: The predefined list of other asset types, along

with related defects. “Other assets” refers to any other

asset (except trailers) that might be attached to the

vehicle.

The Company Assets Parts List file name structure is:

• When created by RoadLog: Carrier_ CompanyID_

DVIRPartsList.DPL

• When created by RoadLogFleet: Carrier_CompanyID_

DVIRPartsList_yymmddhhmmss.DPL

• CompanyID: the USDOT number.

• yymmddhhmmss: time the file is created.

Device Related Files

Device-related files contain data recorded by RoadLog, or

data related to the vehicle. These files are not recorded

during company log in sessions. At the user’s request, the

files can be downloaded onto a Fleet Key, Driver Key or any

USB flash drive formatted in FAT32, irrespective of a

company’s log in status.

DEVICE CONFIGURATION PARAMETERS DATA

The Device Configuration Parameters Data file contains

RoadLog’s original set up configuration.

The Device Configuration Parameters Data file

includes:

• Configuration Parameters based on default values.

The Device Configuration Parameters Data file name

structure is:

• Only created by RoadLog.

• EOBR_SerialNumber_Configuration Parameters_

yymmddhhmmss.CLB

Summary of content (18 pages)

PAGE 1
RoadLog Files The Company Vehicle DVIR Data file includes: • DVIR reports recorded no more than 30 days from the last download. • yymmddhhmmss is the time when the file is created. Company Assets Parts List File • CompanyID: the USDOT number. The Company Assets Parts List file contains the list of predefined asset types used during RoadLog DVIR inspection. It is uploaded to RoadLog memory during company log in. The file is created by RoadLogFleet during activation of the Fleet Key.
PAGE 2
RoadLog Files • Serial Number is the device serial number. • yymmddhhmmss is the time when the file is created. Device Diagnostic Events Data The Device Diagnostic Events Data file contains the RoadLog diagnostic events that were recorded in the last 30 days, irrespective of whether the events occurred during a company log session or not. The Vehicle Data file includes: • Vehicle travelling periods. • Records of system time synchronization with GPS time.
PAGE 3
RoadLog Files Device Software Update History File The Device Software Update History file contains the list of software packages installed on a specific RoadLog. Device Software Update History file name structure is: • Only created by RoadLog: EOBR_SerialNumber_ SWUpdates_yymmddhhmmss.EVD The Device Software Update History file contains: • Serial Number is the RoadLog serial number. • Installed software packages in this RoadLog. • yymmddhhmmss is the time when the file is created.
PAGE 4
RoadLog Files The Driver Support Data File contains: • Predefined list of trailers assigned to the Driver by the RoadLog Fleet Software, along with each trailer’s related DVIR record. Up to 20 DVIR records can be stored in the file. This data is available to the Driver during pre-trip or post-trip trailer inspection. • List of Shipment Documents assigned to the Driver. Up to 20 Shipment Documents can be stored in the file.
PAGE 5
RoadLog Files The Driver RODS Text Data file name structure is: • Created only by RoadLog: RODS_CompanyID_ DriverID_yymmddhhmmss.TXT • CompanyID is the company identification as assigned by FMCSA (USDOT number). Printouts RoadLog provides the following types of printouts: • Daily Log • DVIR Report • Supporting Document • Diagnostic Events • Configuration Parameters 135 • DriverID is the Driver identification number as it was assigned by the company • yymmddhhmmss is the time when the file is created.
PAGE 6
RoadLog Files Daily Log 1. VDO Logo 2. Title of the printout 3. Time and date of printing 4. Date log was recorded 5. Driver’s home terminal time offset. 6. The name of the Driver whose log is printed. 7. Start time of the 24-hour period. 8. Total miles Driver travelled on the date the log was recorded per day. 9. Name and address of the primary company. 10. Carriers worked for: Companies for which the Driver worked on the day the log is or was printed, as well as: 11.
PAGE 7
RoadLog Files DVIR Report 1. VDO Logo. 2. Title of printout. 3. Date and time of printing. 4. Driver’s home terminal time zone. 5. Vehicle registration plate number. 6. Type of asset for which DVIR inspection has been performed. 7. Asset identification number. 8. Post-trip inspection 9. 10. 137 • Date/Time Date and time the post-trip inspection was performed. • Driver ID Identification of the Driver who performed the post-trip inspection.
PAGE 8
RoadLog Files Supporting Document Company Log Out from RoadLog No. Explanation 1 VDO Logo. 2 Time of printing. 3 Vehicle’s license plate registration number. 4 Number of the supporting document generated for the given activity. 5 Activity for which the supporting document was generated. 6 Time the supporting document was generated. 7 Nearest populated area at the time the supporting document was added. 8 Coordinates of the location at which the supporting document was generated.
PAGE 9
RoadLog Files Event Code Occurrence / Condition LOWVLT Low voltage detected. BATLOW Battery energy level is low. CLKERR A deviation of greater than 60 seconds between RoadLog time and the time received from the GPS has been detected. CLKADJ RoadLog has adjusted its system time to GPS time. HIGHVT High voltage detected. IGN_ON Ignition signal is ON. IGNOFF Ignition is OFF. SWC_ON RoadLog has woken up from sleep mode. SWCOFF RoadLog has entered sleep mode.
PAGE 10
RoadLog Files Event Code Occurrence / Condition DLOADY RoadLog has successfully downloaded data onto the USB key. DLOADN The inserted USB key is not authenticated as a valid Fleet Key or Driver Key. FATERR The inserted USB key is not formatted according FAT32 file system. CLSERR The inserted USB device is not recognized by RoadLog. USPERR USB power supply error. USP_OK USB power supply is OK. NODRID No Drivers have logged into RoadLog, but the vehicle is in motion.
PAGE 11
RoadLog Files Event Code Occurrence / Condition PLSERR RoadLog is configured to synchronize with the vehicle via speed pulses… AND During the timeframe of the GPS plausibility check, no vehicle motion is detected. CDSTER RoadLog is calibrated to be synchronized with vehicle via CAN interface… AND Vehicle total distance data has not been received from CAN bus. CSPERR RoadLog is calibrated to be synchronized with vehicle via CAN interface… AND Vehicle speed data has not been received from CAN bus.
PAGE 12
Support / Warranty 18. Support / Warranty Access to support for VDO RoadLog and VDO RoadLog Fleet Management Software is available directly through the Fleet Software. Click the Support button for links to software updates, data backups, and “NetViewer” software that will allow RoadLog Technical Support personnel to share your computer screen online, to help diagnose problems and answer questions. VDO RoadLog support is available at: Technical Support Email: RoadLog-support@vdo.com Tel.
PAGE 13
Glossary 19. Glossary Adverse driving conditions Conditions that interfere with normal safe driving that were not known to the person dispatching the run at the time it began. Includes snow, sleet, fog, ice or unusual road or traffic conditions. DVIR Driver Vehicle Inspection Report. The report on vehicle functions, parts and accessories that must be completed by Drivers at the completion of each day and the beginning of the next day. HOS Hours of Service.
PAGE 14
Glossary FMCSA Sleep mode Active mode Deactivated mode Download Upload GPS GPRS GSM USB Driver Key Fleet Key Daily reset condition 144 Federal Motor Carrier Safety Administration. RoadLog’s low power consumption mode. RoadLog functionalities are not available in this mode and the display is turned off. Operation mode in which RoadLog has all functionalities available. RoadLog is not connected to power supply. Data transfer from RoadLog to a flash drive, usually a RoadLog Driver Key or Fleet Key.
PAGE 15
Legal Notices 20. Legal Notices This product may contain software available under open source licenses. Some of this software in source code, object code or other forms may be available at www.vdoroadlog.com/oss5_2012 or upon request to: Technical Support Continental 6755 Snowdrift Rd The libraries are distributed in the hope that they will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
PAGE 16
Legal Notices Acknowledgements go, in no particular order, to: The Regents of the University of Michigan Livingston Enterprises, Inc. Paul Mackerras Alan Curry Michal Ostrowski Mitchell Blank Jr. Carnegie Mellon University The Regents of the University of California RSA Data Security, Inc. Lars Fenneberg WIDE Project. Francis.Dupont@inria.fr, INRIA Rocquencourt Jean-loup Gailly Mark Adler Kungliga Tekniska Hoegskolan Eric Rosenquist Pedro Roque Marques Matjaz Godec Miguel A.L.
PAGE 17
Legal Notices CONTINENTAL AUTOMOTIVE SYSTEMS US, INC. , A DELAWARE CORPORATION, CERTIFIES THAT THIS VDO ROADLOG™ ELECTRONIC ON BOARD RECORDER COMPLIES WITH ALL REQUIREMENTS OF 49 CFR 395.15 (AUTOMATIC ON-BOARD RECORDING DEVICES) WHEN MAINTAINED IN PROPER WORKING ORDER AND OPERATED AS INSTRUCTED IN THIS OWNER’S MANUAL. NEITHER CONTINENTAL AUTOMOTIVE SYSTEMS US, INC. NOR ITS PARENT, SUBSIDIARIES OR AFFILIATES ARE RESPONSIBLE FOR ANY DRIVER ERROR OR FOR SYSTEMS NOT MAINTAINED IN PROPER WORKING ORDER.
PAGE 18
Continental Commercial Vehicles & Aftermarket 6755 Snowdrift Road, Allentown, PA 18106 USA www.vdoroadlog.com For more information and to become a VDO RoadLog distributor or retailer call: 1-800-564-5066 or 610-366-8489 E-mail: roadlog-sales@vdo.com For installation and service questions contact: VDO Technical Support: Tel: (855)-ROADLOG, or (855) 762-3564 E-mail: roadlog-support@vdo.com VDO and RoadLog - Trademarks of the Continental Corporation ©2013 Continental Corporation Printed in the USA TD00.3290.