SUMMARY:

• 1. Introduction

  • 1.1 Package contents
  • 1.2 System requirements

• 2. Device overview

  • 2.1 Description
  • 2.2 Device components
  • 2.3 Indicator lights
• 3. Preparation for use

• 4. Initial setup

  • 4.1 Activating Bluetooth
  • 4.2 Connecting the device

• 5. Data download procedure

  • 5.1 Download start
  • 5.2 Transferring data
  • 5.3 Completing the download
  • 5.4 Verifying and managing files
  • 5.5 Scheduling and reminders

• 6. Consulting driving times

  • 6.1 Function access
  • 6.2 Displayed information
  • 6.3 Monitored parameters
• 7. Maintenance and usage precautions
• 8. Technical specifications
• 9. Technical support
• 10. Legal notes and additional information

1. Introduction

DDD Key is the wireless solution designed by SIAK SISTEMI for directly communicating with the digital tachograph. The device connects to the front interface of the tachograph and, through the Bluetooth module, transmits data to the DDD Connect application installed on a smartphone or tablet. The system allows both the download of DDD files (driver card data and tachograph memory) and real-time consultation of the driver's driving and rest times.

This manual describes the procedures for configuring, connecting and using the device, with reference to the features of the DDD Connect application closely related to its operation.

1.1 Package contents

• 1 × DDD Key

1.2 System requirements

To use the device correctly, make sure you have:

• a digital tachograph with 6 pins front interface;

• smartphone or tablet with Android 7.0 (Nougat) or later, or iOS 15 or later operating system;

• DDD Connect application installed and updated to the latest available version;

• Bluetooth enabled on the mobile device, with location and notification permissions granted to the application.

2. Device Overview

2.1 Description

DDD Key is a Bluetooth dongle that acts as a communication bridge between the digital tachograph and the DDD Connect mobile application. The device is compatible with any digital tachograph that has a 6-pin front connector.

2.2 Device Components

2.3 Light Indicators

DDD Connect allows to manage the brightness of the two LEDs through the Advanced settings.

3. Preparation for use

Before starting, make sure that the mobile device and the tachograph are ready for use.

1. Make sure that the mobile device has Bluetooth enabled.

2. Check that you have installed DDD Connect application.

3. Ensure that the tachograph is compatible with the device.

4. Locate and connect the USB key to the 6-pin interface.

4. Initial configuration

To use the device, follow these steps.

4.1 Activating Bluetooth

Turn on Bluetooth on the smartphone or tablet you will use for data download. On first launch, DDD Connect application will request permission to access Bluetooth features and nearby devices; on Android 12 and later versions, Bluetooth scanning and connection permissions are required, while on earlier versions, location permission is needed. Grant permission even for notifications, essential for receiving alerts related to completed downloads and deadlines.

4.2 Device Connection

1. Connect DDD Key to the corresponding tachograph interface;

2. wait for the device to start;

3. open DDD Connect application;

4. go to the section dedicated to device connection (Home) to scan for available keys;

5. select the DDD Key from the list of available devices;

6. wait for pairing (if necessary) and the establishment of the connection.

Once the procedure is completed, the device will be ready for use. At every connection, the application checks the firmware version installed on the DDD Key. If an update is available, the corresponding procedure starts automatically: during this phase, LED 1 flashes and no user intervention is required. Do not remove the DDD Key or close the application until the update is complete.

5. Data Download Procedure

5.1 Download Start

Subject to the points in section 4:

1. Insert the driver card or the company card into one of the two slots of the tachograph and wait for the loading of it/them. The application automatically detects the status of each slot;

2. If necessary, from the Advanced settings, configure the output file format (available: .DDD, .TGD, .ESM. By default, the selected extension is .DDD).

3. Select the download type among the options provided by the application:

• Driver card: captures the entire content of the card inserted in the selected slot;

• Tachograph: captures the data from the tachograph memory for the specified period;

• Both: performs both tachograph memory and driver card download.

If two driver cards are inserted, the application offers the choice on which slot you want to download (Driver 1, Driver 2, or both).

1. Wait for the completion of the download procedure.

Notes on the tachograph download: the application downloads a preview with license plate, vin, and tachograph generation, then requests which of the sections you want to download (Activities, Technical data, Events and faults, Detailed speeds) and the reference time period (only if Activities is selected). If available, the last download date for that vehicle is marked as a reference for the period to be selected.

5.2 Data transfer

During transfer, keep the device connected to the tachograph and make sure that the Bluetooth connection remains active. The application shows a progress bar with the percentage of completion and the description of the current step (overview, data technical, events and faults, speed, activities, driver card). The duration of the operation varies depending on the amount of data to be transferred, the selected period, the distance between the mobile device and the key, and the characteristics of the tachograph. Download also continues by navigating to other sections of the application: in this case, a miniaturized status bar remains visible at the bottom of the screen.

Warning: do not disconnect the device and do not voluntarily interrupt the procedure while the download is in progress.

5.3 Completion of the download

At the end of the operation, the application shows a summary with the names of the generated files and sends a push notification with the result of the download. If an error occurs, a specific message is displayed (connection error, unauthorized card, no card in the slot, etc.) with the option to retry the operation.

In the second case:

• check if the operation has been completed correctly;

• check if one of the “Possible Causes” has occurred (see button).

5.4 File verification and management

Files acquired via DDD Key are stored locally in the DDD Connect application and can be found in the following sections:

• Archive: chronological list of all downloaded files, indicating the type (driver card or vehicle memory), the associated identifier (license plate or name) and the acquisition date. Each file can be shared, exported individually or in a ZIP archive, or deleted. A search and filter function is available for name, license plate, VIN, card number, and date range;

• Registry: automatically collects the information of drivers and vehicles extracted from the imported and/or downloaded files. For each driver, the following are reported: name, surname, date of birth, card number, expiration, country of issuance, and date of the last download. For each vehicle: license plate, VIN, date of the last download, next calibration, and name of the tachograph. The application automatically manages the recognition and merging of duplicate entities (for example, in case of driver card renewal or vehicle license plate change);

• Import and export: in addition to files downloaded directly via DDD Key, it is possible to import DDD, ESM, TGD files or ZIP archives from other sources. The export operation supports both sending via the operating system's sharing sheet and, on Android, direct saving to a chosen folder.

5.5 Deadline and reminders

DDD Connect application integrates an automatic reminder system linked to the data acquired via DDD Key. The deadline monitor tracks:

• download deadlines: for drivers, within 28 days of the last download; for vehicles, within 90 days. Once the threshold is exceeded, the application signals the delay with color coding (green, yellow, red);

• expiration of the driver card: scheduled notification 60 days before the deadline;

• calibration deadline for the vehicle: scheduled notification 45 days before the deadline.

A summary widget on the Home screen shows the most pressing deadlines, which can be found in the dedicated section. Notifications can be enabled or disabled for individual entities from their respective profile tab.

6. Consultation of driving times

Other than downloading tachograph files, DDD Key and the tachograph connection allows consultation of real-time driver's driving and rest times directly from the DDD Connect application.

6.1 Access to the function

The system queries the tachograph and displays real-time information related to the driver through the speedometer button exhibited in the application header. The requirements are the connected DDD Key device and the driver card inserted into the first slot of the tachograph.

6.2 Information displayed

The screen header displays the driver's name, the current date and time of the tachograph, and the current activity status, identified by a dedicated icon and color code:

• Driving (red): driving in progress;

• Rest (green): ongoing rest period;

• Work (blue): other work activity;

• Availability (yellow): availability period.

The conditions of multi-manning and Out of Scope are also reported when active. The data can be shown in two modes:

• Graphs mode: progress bars showing the elapsed time and the remaining time for each parameter, with automatic highlighting of the most restrictive constraints;

• Data mode: numerical tables grouped by category: general information, driving interruptions, daily driving, weekly driving, daily rests (with multi-manning detail) and weekly rests.

6.3 Monitored parameters

The system monitors the following counters, in accordance with the limits set by Regulation (EC) No. 561/2006:

• current rest, with automatic classification of the type: driving interruption, reduced or regular daily rest, reduced or regular weekly rest;

• continuous driving block;

• daily driving;

• weekly driving;

• daily and weekly commitment;

• remaining extended drives in the current week;

• remaining reduced daily rests in the current week.

The application automatically highlights the most restrictive constraint among those in progress, facilitating the identification of the parameter that determines the next mandatory break or the end of allowed driving.

7. Maintenance and usage precautions

To ensure the correct functioning of the device over time, follow these instructions:

• use the device exclusively for the intended purposes;

• avoid impacts, falls, and mechanical stress;

• protect the device from moisture and exposure to liquids;

• do not attempt to disassemble or modify the device;

• avoid the exposure to temperatures outside the operating range specified by the manufacturer.

• use only compatible accessories, if provided.

In case of malfunction, stop using it and contact the support service.

8. Technical specifications

9. Technical support

DDD Connect application includes a Frequently Asked Questions (FAQ) section, accessible from Settings, which covers the most common usage scenarios. For issues not resolved through the FAQ, contact the technical support service or open a support ticket through the website.

When you contact support, we recommend indicating:

• the device model;

• the model of the tachograph used;

• the version of the application;

• a description of the action and the problem encountered;

• any error messages displayed.

DDD Key firmware and application version can be consulted from the Advanced Settings screen, under the Information section. This data will help identify quickly the cause of the problem.

10. Legal notes and additional information

The information contained in this manual refers to 0.1.5 firmware version of DDD Key.

The manufacturer reserves the right to make changes to the device and its related documentation to improve functionality and performance.