RDD status

Vehicle

Vehicle format. This info can be set in Settings > Management > Formatting.

Technical number

The technical number of the vehicle.

Code

Vehicle code chosen by the customer. This code can be modified under Settings > Management > Vehicles.

Device type

• Quattro(+)
• TX-MAX (GO)
• TX-SKY / TX-GO

Is the contact ON?

Activated

Is this functionality activated on the on-board computer and correctly configured?

GPRS latest date

Date of the latest GPRS connection.

Company card

Different types of company card are supported and will be visible. If you are using several company cards, the correct company card needs to be specified for each vehicle. This can be done in "Vehicle management" > "Identification".

RDD status

RDD communication flow

1

Request sent to OBC

As soon as the data download is started from TX-CONNECT, a request is sent to the OBC to start an RDD session.

2

RDD request successfully received by OBC

When the request is received on the OBC, a confirmation request is sent to the back office.

3

RDD request started

The OBC will start the treatment of the RDD request by requesting authentication with the company card in the backoffice. A company card must be available in a card reader in the backoffice.

4

Authentication started

5

Successful authentication

If the authentication is successful, the RDD status is updated in TX-CONNECT and a message is sent to the OBC to confirm the RDD session is allowed.

6

Download started

As soon as the authentication confirmation is received, the download is automatically started on the OBC. No action is required by the driver.

Note (only valid for TX-SKY / TX-GO):

In case a driver card is inserted in the tachograph, the RDD session will download the data from the mass memory AND from the tacho driver card.

In case no driver card is inserted in the tachograph, the RDD session will only download the data from the mass memory.

7

Successful download

When the download was completed, the RDD status is updated in TX-CONNECT.

Errors

In order for the RDD session to be successful, a number of conditions must be met. Different states will indicate errors during the RDD process.

Note: An alarm can be configured to notify the TX-CONNECT user in case an RDD session fails (cf. Remote data download alarm).

Authentication has failed

For the authentication, a valid company card must be available in the company card reader.

Download has failed

To start the download process, the vehicle must be driving or the vehicle contact must be ON (cf. Is the contact ON? column)

No company card selected

In case multiple company cards are used, a company card should be selected in "Vehicle management" (cf. Company card).

RDD is not configured

• RDD must be configured / activated in the backoffice software:

• in TX-SERVICE for TX-SKY / TX-GO devices (SKY environment)

• in the TCS configuration file for TX-MAX (GO) / Quattro+ devices (FLEET environment)

• RDD must be configured/activated on the OBC:

• • in the control panel on TX-SKY devices

  • using TX-CONFIG on TX-GO devices

  • in the manager menu on TX-MAX / Quattro+ devices (fleet)

• TX-CLIENT service must be installed on the workstation with the company card reader(s) to handle the authentication (see also Supported card readers).

• RDD requires the following tacho firmware versions:

• • Siemens: VDO version 1.3A or above

  • Stoneridge: SE5000 version 7.1 or above

  • Actia: AC965124 ind B; AC966060ind A; AC965123 ind B

SCM Microsystems Inc. SCR33x USB Smart Card Reader

Identive CLOUD 2700 F Smart Card Reader