Vehicle Communication Box: Appendix 1 Technical Specification

System
TS
Teknisk specifikation
Ansvarig enhet Handläggare Sida

LogSyst Alf Andersson, 08-782 6393 1 (32)
Dokumentidentitet Version Datum
Appendix 1 to 367283-AI841441 1.1 2012-07-04
Appendix 1
Vehicle Communication Box
Technical specification
___________________________________________________________________________
Utarbetat av
Alf Andersson (Datum + Signatur)
Granskat av
Peter Sohlberg (Datum + Signatur)
Beslutat av
Kjell-Åke Sjöberg (Datum + Signatur)
System
TS

Appendix 1 to 367283-AI841441 1.1 2012-07-04
TABLE OF CONTENTS
1 INTRODUCTION .......................................................................................................... 4
1.1 PURPOSE .................................................................................................................................................. 4
1.2 APPLICATION ......................................................................................................................................... 4
1.3 REVISION HISTORY .............................................................................................................................. 4
1.4 DEFINITIONS AND ABBREVIATIONS ................................................................................................ 4
2 SYSTEM DESCRIPTION, PRECONDITIONS .............................................................. 6
2.1 GENERAL................................................................................................................................................. 6
2.2 OVERALL SYSTEM DESCRIPTION ..................................................................................................... 8
2.2.1 Procurement object ........................................................................................................................... 8
2.2.2 Overall system .................................................................................................................................. 8
2.2.3 Cooperative, ancillary system .......................................................................................................... 9
2.3 OPERATIONAL USE ............................................................................................................................. 10
2.3.1 Operational tasks ............................................................................................................................ 10
2.3.2 Operational profile, mission profile ............................................................................................... 11
2.3.3 Planned life..................................................................................................................................... 11
2.4 OPERATING CONDITIONS ................................................................................................................. 11
2.4.1 Operation organization ................................................................................................................... 12
3 FUNCTIONAL AND PERFORMANCE REQUIREMENTS ........................................ 13
3.1 FUNCTIONS ........................................................................................................................................... 13
3.1.1 Functional structure ........................................................................................................................ 13
3.1.2 Main functions ............................................................................................................................... 14
3.1.3 Bootloader ...................................................................................................................................... 19
3.2 SYSTEM STATES AND DIFFERENT SYSTEM MODS ..................................................................... 19
3.2.1 Power modes .................................................................................................................................. 19
3.3 FUNCTIONS AND PERFORMANCE IN DIFFERENT OPERATIONAL PHASES ........................... 20
3.3.1 Startup ............................................................................................................................................ 20
3.3.2 Visual feedback .............................................................................................................................. 20
3.3.3 BOX to PC host communication performance ............................................................................... 20
4 HARDWARE AND INTERFACE REQUIREMENT ................................................... 21
4.1 GENERAL............................................................................................................................................... 21
4.1.1 Mechanical ..................................................................................................................................... 21
4.1.2 Processing and memory capabilities .............................................................................................. 22
4.1.3 VCAB............................................................................................................................................. 22
4.2 ELECTRICAL ......................................................................................................................................... 22
4.3 EXTERNAL INTERFACE ..................................................................................................................... 23
4.3.1 Supply ............................................................................................................................................ 23
4.3.2 Signal interface............................................................................................................................... 23
4.3.3 Optical interfaces ........................................................................................................................... 24
4.4 MEN-MACHINE INTERFACE .............................................................................................................. 25
4.4.1 Manoeuvring, presentation and management ................................................................................. 25
5 ENVIROMENTAL REQUIREMENT .......................................................................... 26
5.1 GENERAL............................................................................................................................................... 26
5.2 ENVIROMENTAL DURABILITY ........................................................................................................ 26
5.2.1 Mechanical environment ................................................................................................................ 26
5.2.2 The climate in the environment ...................................................................................................... 26
5.2.3 Electromagnetic environment......................................................................................................... 27
5.2.4 Special and combined environments .............................................................................................. 28
6 SYSTEM SAFETY REQUIREMENTS ........................................................................ 28
7 RELIABILITY AND MAINTENANCE REQUIREMENTS ........................................ 29
System
TS

Appendix 1 to 367283-AI841441 1.1 2012-07-04
7.1 RELIABILITY AND MAINTAINABILITY .......................................................................................... 29

7.2 SOFTWARE ............................................................................................................................................ 29
7.2.1 Software structuring ....................................................................................................................... 29
7.2.2 Software language .......................................................................................................................... 29
7.2.3 Software license ............................................................................................................................. 29
7.2.4 Delivery form ................................................................................................................................. 29
7.2.5 Access control systems................................................................................................................... 29
8 DOCUMENTATION REQUIREMENTS ..................................................................... 30
8.1 GENERAL............................................................................................................................................... 30
8.1.1 Document types .............................................................................................................................. 30
8.1.2 Language ........................................................................................................................................ 30
8.2 INFORMATIVE DOCUMENTS ............................................................................................................ 30
8.2.1 Drawing document ......................................................................................................................... 30
8.2.2 The basis for the supply data .......................................................................................................... 30
8.3 SOFTWARE DOCUMENTATION ........................................................................................................ 30
9 References .................................................................................................................... 31
System
TS

Appendix 1 to 367283-AI841441 1.1 2012-07-04
1 INTRODUCTION
1.1 PURPOSE
This document stipulates the technical requirements. A future Contractor’s undertaking will
include all activities necessary to meet the requirements, including referenced documents. The
Contractor will also be responsible for any actions not explicitly stated, or omitted, but
required to fulfil the Contractor’s undertakings.
In summary, the Contractor shall supply a series of hardware boxes containing embedded
software plus PC software that enables communication with electronic equipment (typically
the control network of a vehicle).
The following sections outline the details of the scope of supply.
1.2 APPLICATION
This RFQ document is intended for suppliers of electronic diagnostic devices.
1.3 REVISION HISTORY

Date Version Author Description
2012-06-25 1.0 KS Approved
2012-07-04 1.1 KS Approved
1.4 DEFINITIONS AND ABBREVIATIONS

All “shall” requirements are mandatory and shall be met, unless otherwise specified.
Requirements are labeled TS-x, where x is a running number, unless otherwise specified.
Concepts Explanation
API Application Programming Interface
BMS Battle Management System
BOX On-Board Box, the box or circuit board that contain the main
computational power and hardware
CAN Controller Area Network
CDR Critical Design Review
DHCP Dynamic Host Configuration Protocol
DLL Dynamic Link Library
ECU Electronic Control Unit
EMC Electromagnetic compatibility
FMV Swedish Defence Materiel Administration
System
TS

Appendix 1 to 367283-AI841441 1.1 2012-07-04
IP Internet Protocol
MTBF Mean Time Between Failure
NA Not Applicable
OBA The FMV application that executes on the BOX
OBD On-Board Diagnostics, Legislation suit for commercial vehicles
OEM Original Equipment Manufacturer, e.g., Volvo Trucks and Scania
CV
PC Personal Computer
RSF Tactical Resource allocation and management support System for
Forward logistics units
SAF Swedish Armed Forces
SLA Service Level Agreement
SSH Secure Shell
TCP Transmission Control Protocol
TS Technical Specification
UBAT The vehicle battery voltage
VCAB Vehicle cables. The cable between BOX and the vehicle
System
TS

Appendix 1 to 367283-AI841441 1.1 2012-07-04
2 SYSTEM DESCRIPTION, PRECONDITIONS
2.1 GENERAL
The following picture illustrates the different parts of the system, which is composed of both
hardware and software. It can be described as three separate parts, functioning together: the
BOX (including hardware and software), the PC-host software (device drivers and DLLs) and
the VCAB.
Figure 1. Overview of the system.

System
TS

Appendix 1 to 367283-AI841441 1.1 2012-07-04
The following table explains each figure position shown in Figure 1.
Figure Description
Position
#1 The OBA is one or several applications running on the
operating system. The applications are developed and
maintained by FMV.
#2 The J2534 API handles communication with the Vehicle
Interface Module for the OBA. The Vehicle Interface
Module handles communication with the vehicle for the
OBA and for the PC-host.
#3 The USB Device is used for communication with the PC
host.
#4 Two USB host controllers that shall be possible to use
with device drivers that are developed and maintained by
FMV.
#5 The Ethernet module handles Ethernet communication
10/100 MBit/s using Con F-G (optical) and Con H.
#6 The RSF is an application running on a standard PC
Laptop and can communicate with the BOX for diagnostic
and forward-logistics purposes (PC-host to USB device).
#7 The PC shall contain communication API:s and device
drivers according to the standards: ISO 22900-2, J2534
and RP1210 API.
#8 The Visual Feedback System shall show the current
operational status of the BOX to the user.
#9 The Generic I/O API is an interface for running
applications to the analog, digital and serial I/O inputs and
outputs.
System
TS

Appendix 1 to 367283-AI841441 1.1 2012-07-04
2.2 OVERALL SYSTEM DESCRIPTION

2.2.1 Procurement object
The following list specifies procurement objects that shall be delivered by the Contractor.
• Hardware BOX containing Software.
• Technical documentation
• Software for the BOX, PC and Development environment.
• Vehicle cables, VCAB.
2.2.2 Overall system

2.2.2.1 The BOX
The BOX is a device mainly used for vehicle diagnostic purposes protected by a rugged
casing. It contains an embedded computer system, several connectors, and a visual feedback
system.
The computer system is a microprocessor system including an operating system, persistent
and non-persistent memory devices, and several hardware controllers for communication,
both with the PC-host and the vehicle. The OBA is applications running on the BOX that is
developed and maintained by FMV. They can use the connection features of the BOX through
various software APIs e.g. for communication with the vehicle and the PC-host.
The connectors of the BOX are denoted Con A to Con I. Con A is used to connect the BOX
to the actual vehicle, and is the main power source. It is also possible to connect an external
power source to Con B.
For USB communication there are three connectors, Con C-E. Con C acts as a USB device.
A typical scenario is that a PC-host connects to Con C in order to collect diagnostic
information. There are also two USB-host connectors, Con D and Con E. For example, in
order to provide wireless internet connectivity for the BOX, a Wi-Fi-device can be attached to
one of the USB-host connectors.
The BOX also supports Ethernet, which is provided through Con F-H. Con F and con G are
optical connectors whereas con G is a “standard” Ethernet connector. The BOX supports
optical Ethernet due to the need to minimize electromagnetic emissions from the BOX and its
attached cables. Moreover, there is also a connector, Con I, which can be used for various
purposes. It is composed of both analog and digital inputs and outputs as well as a connector
for serial communication (RS232).
2.2.2.2 PC-Host Software

The PC-host software consists of several dedicated DLLs and device drivers, especially
designed for communication with the BOX. Consequently, it provides means for the PC to
communicate with the BOX in order to collect diagnostic information, or communicate with
System
TS

Appendix 1 to 367283-AI841441 1.1 2012-07-04
application specific servers. Using the PC-host software, it is possible for PC-side
applications, i.e. OEM diagnostics tools, to communicate with the BOX using APIs such as
J2534 and RP1210.
2.2.2.3 VCAB
The VCAB is the vehicle cable used to connect to the vehicle’s internal communication
network e.g. CAN. It is also used to power the BOX. However, the design and properties of
the VCAB may vary depending on the vehicle model.
2.2.3 Cooperative, ancillary system

The system, i.e. the BOX, PC-host software and VCAB, cooperates with several external
systems in order to provide the desired functionality for Swedish defence staff and other end
users. These external systems include the RSF, the BMS, OEM Diagnostic applications, and
standard client-host software like SSH.
The RSF is a FMV application mainly used for maintenance and forward logistics purposes.
The RSF application runs on a PC-system and uses the provided PC-host software to connect
to the vehicle via the BOX and VCAB.
The BMS is a battle management system which may be found in certain vehicles. The BOX
may connect to the BMS communication network through the optical Ethernet connection.
Since the BMS network is classified as a restricted network the way that the BOX interacts
with it is strictly limited. The interaction with BMS is handled by specific OBA applications
provided by FMV.
The OEM Diagnostic applications are applications provided by vehicle manufacturer for
diagnostic purposes. For example, they can be used to retrieve vehicle status information and
error codes via CAN. Like RSF, the OEM Diagnostic applications run on a standard PC and
use the provided PC-host software to connect to the vehicle via the BOX and VCAB.
For e.g. BOX debugging, configuration and general maintenance purposes, a qualified
operator may also use standard applications like SSH to interact with the BOX. The SSH
client runs on a standard PC and use the provided PC-host software to connect to a SSH
server running on the BOX.
System
TS

Appendix 1 to 367283-AI841441 1.1 2012-07-04
2.3 OPERATIONAL USE

2.3.1 Operational tasks
The purpose of this section is to give the Contractor an overview of the operational tasks that FMV
want to accomplish using the BOX.
2.3.1.1 Pre-requisites tasks A-B

1. The Technician installs the PC software for the BOX on the PC.
2. The Technician connects the BOX to the PC via USB.
3. The Technician connects the BOX to the VCAB.
2.3.1.2 Task A – Service and Repair (maintenance)
Figure 2. Task A.
1. The Technician puts the diagnostic cord of VCAB into the diagnostic outlet of the truck
and turns on the ignition.
2. The Technician starts the RSF client application and read out data from the truck.
3. The readout data from the vehicle is mainly used for service and repair scenarios.
2.3.1.3 Task B – Repair (maintenance)
Figure 3. Task B.
1. The Technician puts the diagnostic cord of VCAB into the diagnostic outlet of the truck and
turns on the ignition.
System
TS

Appendix 1 to 367283-AI841441 1.1 2012-07-04
2. The Technician starts the Diagnostic software issued by a Truck OEM (e.g., Volvo Trucks),
which is in compliance with the RP1210B standard [RP1210B].
3. The Diagnostic software is used to communicate with the Truck mainly for repair scenarios.
2.3.1.4 Task C – Logging of vehicle operational data (operation)
Figure 4. Task C.
1. A vehicle contractor mounts the BOX in the vehicle to collect vehicle operational data
during use.
2. The BOX is connected to the BMS system through optical Ethernet.
3. The Technician reads out data from the BMS network at regular intervals for general
maintenance, repair and forward logistics purposes.
2.3.2 Operational profile, mission profile

In Task A and B the technician uses the BOX for maintenance. For intermittent errors,
logging may occur for several days by temporarily mounting the BOX in the vehicle.
In Task C the technician uses the BOX to create an operating profile of the vehicle. This
means continuous logging of vehicle data during use of vehicle.
2.3.3 Planned life

Planned life for the BOX is 10-15 years.
2.4 OPERATING CONDITIONS

The BOX, mounted in the vehicle for logging of operating data or used in diagnostic tasks,
must be expected to perform in a wide variety of operating conditions. Typically it will be
mounted in different kinds of vehicles used by the military. Consequently it must be able to
System
TS

Appendix 1 to 367283-AI841441 1.1 2012-07-04
function in temperate climate zones, e.g. Sweden, as well as in arid and rugged terrain with
extreme temperature variations, e.g. Afghanistan.
Furthermore, the performance of the BOX shall also not degrade due to expected
electromagnetic interference, shock, or vibrations, in its intended operating environments. For
these reasons there are a number of technical requirements related to environmental issues
that needs to be fulfilled (see Chapter 5 for more information).
The EMC emission requirements for the BOX are high so that the communication equipment,
in military vehicles, cannot be adversely affected.
The BOX will be integrated into current military maintenance kits. Therefore, the
requirements for the transportation and handling will be described limited.
2.4.1 Operation organization

Operating organization is mainly military maintenance and services units.
System
TS

Appendix 1 to 367283-AI841441 1.1 2012-07-04
3 FUNCTIONAL AND PERFORMANCE

REQUIREMENTS
3.1 FUNCTIONS
3.1.1 Functional structure
Figure 5 shows an architectural view of the BOX and the PC-host. The diagnostic tool uses
the Vehicle Communication Interface to communicate with the vehicle through the Vehicle
Interface Module. Onboard applications also communicate directly with the vehicle using the
Vehicle Interface Module, through the J2534 API. The OBA can also use the Generic I/O API
for serial communication, as well as access the analog and digital input and outputs.
In order to communicate with the BOX internal applications, however, PC-side applications
(controlled and maintained by FMV) must use the Device Communication Interface through
an application specific server. For example, a SSH client (PC-side) connects to a SSH server
on the BOX-side.
For communication between the BOX and the PC, it is possible to connect over both USB
and Ethernet, using a USB network adapter and an Ethernet adapter respectively.
Figure 5. Architectural view.

System
TS

Appendix 1 to 367283-AI841441 1.1 2012-07-04
3.1.2 Main functions

3.1.2.1 Hardware controllers
3.1.2.1.1 CAN controllers

TS-1 The BOX shall have 2 CAN 2.0B controllers capable of operating
simultaneously at speeds up to 1Mbps.
3.1.2.1.2 J1708/J1587 Controller

TS-2 The BOX shall have one J1708/J1587 controller capable of operating with
baud rates up to 115 200 bps.
TS-3 The J1708/J1587 controller shall be implemented according to the J1708
[J1708] and J1587 [J1587] specification.
TS-4 The J1708/J1587 controller shall support “Raw Mode” to allow the client
application to handle the raw J1708 bus traffic.
TS-5 The J1708/J1587 controller shall implement a collision avoidance
mechanism.
TS-6 The J1708/J1587 controller shall be able to operate with 24V electrical
systems as described in J2534-2 [J2534-2].
3.1.2.1.3 K-line
TS-7 The BOX shall have a controller to handle communication over K-Line
with baud rates up to 19200 bps.
3.1.2.1.4 L-Line
TS-8 The BOX shall have a controller to handle communication over L-Line
with baud rates up to 19200 bps.
3.1.2.1.5 UART controller

TS-9 The BOX shall have a UART controller.
TS-10 The UART controller shall operate at baud rates up to 115 200 bps.
TS-11 The UART controller shall support serial communication according to RS-
232, RS-422 and RS-485 (pin-selection may be used for switching between
protocols if applicable).
3.1.2.1.6 USB controllers

TS-12 The BOX shall have one USB Device Controller.
System
TS

Appendix 1 to 367283-AI841441 1.1 2012-07-04
TS-13 The BOX shall have two USB Host Controllers.

TS-14 The USB host controllers shall be compliant with the USB 2.0 specification
defined by USB.org or higher such as USB 3.0 [USB1] or equivalent.
TS-15 The USB Device Controller shall be USB 2.0 (High-Speed) or USB 3.0
(Super-Speed) and comply with the corresponding specification defined by
USB.org [USB1].
TS-16 The USB Device shall pass the appropriate USBCV compliance test tool or
equivalent. If USB 2.0 is used all of the USB20CV tests shall pass [USB2].
If USB 3.0 is used all of the USB30CV tests shall pass [USB3].
3.1.2.2 Vehicle Interface Module
3.1.2.2.1 Communication with external applications

TS-17 The PC host shall be able to communicate with the Vehicle Interface
Module using the J2534-2 API [J2534-2].
Module using the RP1210B API [RP1210B].
Module using the ISO22900-2 API [ISO22900-2].
TS-20 The Vehicle Interface Module shall only accept communication with one
external application at a time.
3.1.2.2.2 Communication with internal applications

TS-21 The application running, e.g., OBA (see Figure 1), on the BOX shall be
able to communicate with the Vehicle Interface Module using the J2534-2
API.
TS-22 The OBA shall be able to communicate with all hardware controllers in
parallel via the J2534-2 API and the generic I/O API.
TS-23 If a diagnostic session is initiated by the host PC the Vehicle Interface
Module shall close any connections made by the BOX operating system
and deny any communication attempts from the OBA returning
ERR_DEVICE_IN_USE according to the J2534 specification, or
equivalent, to indicate that the device is used by the host PC [J2534-1].
3.1.2.2.3 Communication with the vehicle (Vehicle Interface)

TS-24 The vehicle interface protocols shall be implemented according to the
specifications in J2534-2, RP1210B and ISO22900-2 specifications [J2534-
2] [RP1210B] [ISO22900-2].
TS-25 The BOX shall support J1939 [J1939] at different baud rates (e.g., 250
kbit/s and 500 kbit/s).
TS-26 The BOX shall support communication using the ISO15765 protocol
System
TS

Appendix 1 to 367283-AI841441 1.1 2012-07-04
according to the ISO15765-2 and the ISO15765-4 standards [ISO15765-2]

[ISO15765-4].
TS-27 The BOX shall support the ISO9141-2 protocol over both the K-Line and
the L-Line bus according to [ISO9141].
TS-28 The BOX shall support ISO 14230-4 (KWP2000) protocol.
3.1.2.3 BOX Operating System
3.1.2.3.1 General
TS-29 The operating system of the BOX shall be Linux or BSD.
TS-30 The BOX operating system shall have support for both USB host and
device controllers and support for plug and play of USB peripheral devices.
TS-31 It shall be possible to install new driver modules on the BOX on kernel and
user level.
TS-32 The operating system shall run a journaling file system e.g. ext4.
TS-33 The operating system shall be able to mount an external storage media.
TS-34 The operating system shall allow execution of applications.
TS-35 The operating system shall support communication via SSH over USB
connections using a TCP/IP connection.
TS-36 The operating system shall support communication via SSH over Ethernet
connections using a TCP/IP connection.
TS-37 The BOX operating system shall be able to run application-specific servers
for communication with PC-host applications.
TS-38 When the BOX is connected to a PC via USB, the BOX shall support a
virtual Ethernet network over a USB connection, e.g. using an appropriate
Linux module for Ethernet over USB support.
TS-39 The BOX shall be able to function as a USB device that can be connected
to a PC-host.
TS-40 The BOX shall be able to function as a USB host.
3.1.2.3.2 Network features

TS-41 TCP/IP (IPv4 and IPv6) shall be supported over the virtual Ethernet
network (USB), and the Ethernet adapter.
TS-42 It shall be possible to configure the IP-address for Ethernet and the virtual
Ethernet network (USB).
TS-43 DHCP shall be supported over Ethernet and the virtual Ethernet network
(USB).
TS-44 The operating system network controller device shall by default be
assigned a static IP but shall also be able to support dynamic IP
configuration.
System
TS

Appendix 1 to 367283-AI841441 1.1 2012-07-04
3.1.2.3.3 J2534 API

TS-45 The operating system shall provide a library and development header files
for J2534 to communicate with the Vehicle Interface Module.
TS-46 The J2534 interface of the BOX shall comply with the J2534-2 standard
according to [J2534-2] and support CAN [CAN], J1708/J1587 [J1708]
[J1587], J1939 [J1939], ISO15765 [ISO15765-2] [ISO15765-4], and K-line
protocols [ISO14230-4] [ISO9141].
TS-47 The optional feature of the J2534-2 standard named CAN Mixed format
shall be implemented (BOX side).
TS-48 The optional feature of the J2534-2 standard named Pin Selection shall be
implemented (BOX side).
TS-49 The optional feature of the J2534-2 standard named Repeat Messaging
TS-50 The optional feature of the J2534-2 standard named Discovery Mechanism
3.1.2.3.4 Miscellaneous APIs

TS-51 The operating system shall provide a generic I/O API to running
applications for using the analog inputs and outputs, the digital inputs and
outputs and the external start signal in Connector I, as well as for
communication using RS232. The API shall also provide functionality for
pin-selection of the UART controller.
3.1.2.4 PC-Host software
3.1.2.4.1 General
TS-52 All PC Host software shall function under Windows 7 x64.
TS-53 All PC Host software shall function under Windows 7 x32.
TS-54 When the BOX is connected to a PC via USB, the PC-software shall
support a virtual Ethernet network over a USB connection.
TS-55 TCP/IP (IPv4 and IPv6) shall be supported over the virtual Ethernet
network (USB).
TS-56 The PC-host shall be able to communicate with the BOX operating system
using a TCP/IP network socket.
TS-57 It shall be possible to configure the IP-address for the virtual Ethernet
network (USB).
TS-58 DHCP shall be supported over the virtual Ethernet network (USB).
TS-59 It shall be possible to connect more than one BOX to the PC-host, and
System
TS

Appendix 1 to 367283-AI841441 1.1 2012-07-04
select which BOX to communicate with (by selecting the actual IP-address)
TS-60 The PC-host shall have an API and a DLL for installing all software
components in the BOX, and report the progress level of the installation.
3.1.2.4.2 Device Drivers

TS-61 All drivers shall be implemented using Windows Driver Foundation [MS-
WDF].
TS-62 All drivers shall be digitally signed by Windows Hardware Quality Labs
[WHQL].
TS-63 All drivers shall at least pass the “Unclassified device” classification in
Windows Logo Kit [MS-WLK] or equivalent.
TS-64 There shall be one USB driver for communication with the Vehicle
Interface Module.
3.1.2.4.3 Dynamic Link Libraries

TS-65 There shall be one J2534-2 DLL to allow external tools to connect to the
BOX Vehicle Module Interface using the J2534 API.
TS-66 There shall be one RP1210B DLL to allow external tools to connect to the
BOX Vehicle Module Interface using the RP1210 API.
TS-67 There shall be one ISO22900 DLL to allow external tools to connect to the
BOX Vehicle Module Interface using the ISO22900 API.
3.1.2.4.4 Vehicle Communication Interface
3.1.2.4.4.1 RP1210 API

TS-68 The RP1210 interface shall comply with the RP1210 standard according to
[RP1210B] and support CAN [CAN], J1708/J1587 [J1708] [J1587], J1939
[J1939], ISO15765 [ISO15765-2] [ISO15765-4], and K-line protocols
[ISO14230-4].
3.1.2.4.4.2 ISO 22900-2 API

TS-69 The ISO 22900-2 interface shall comply with the ISO 22900-2 standard
according to [ISO22900-2] and support CAN [CAN], J1708/J1587 [J1798]
[J1587], J1939 [J1939], ISO15765 [ISO15765-2] [ISO15765-4], and K-line
protocols [ISO14230-4].
3.1.2.4.4.3 J2534-2 API

TS-70 The J2534-2 interface shall comply with the J2534-2 standard according to
System
TS

Appendix 1 to 367283-AI841441 1.1 2012-07-04
[J2534-2] and support CAN [CAN], J1708/J1587 [J1708] [J1587], J1939

[J1939], ISO15765 [ISO15765-2] [ISO15765-4], and K-line protocols
[ISO14230-1] [ISO9141].
TS-71 The optional feature of the J2534-2 standard named CAN Mixed format
shall be implemented.
TS-72 The optional feature of the J2534-2 standard named Pin Selection shall be
implemented.
TS-73 The optional feature of the J2534-2 standard named Repeat Messaging
TS-74 The optional feature of the J2534-2 standard named Discovery Mechanism
3.1.2.5 Accelerometer
TS-75 The BOX shall contain one accelerometer.
TS-76 The accelerometer shall be able to measure G-forces in the x, y, z-plane.
TS-77 The accelerometer shall at least have 10-bit resolution of G.
TS-78 The operating system shall provide an API to running applications for
using all features of the accelerometer.
3.1.3 Bootloader
TS-79 The BOX shall have a boot loader mode that allows firmware updates via
USB and Ethernet connection.
TS-80 The boot loader shall check firmware consistency during start-up. If the
firmware check fails the device shall stay in boot loader mode and notify
the user of firmware corruption.
TS-81 If the boot loader fails to start the operating system the device shall stay in
boot loader mode and notify the user of operating system failure.
TS-82 The BOX shall be able to boot from a USB mass storage.
TS-83 It shall be possible to force the BOX into boot loader mode.
3.2 SYSTEM STATES AND DIFFERENT SYSTEM MODS

3.2.1 Power modes
TS-84 The BOX shall be possible to turn off from OBA when the power supply is
on (sleep mode).
TS-85 The BOX shall start when the power supply is connected.
TS-86 The BOX shall be able to start, and wakeup, on an input signal
(5-UBAT V) via the external start signal input in Connector I.
System
TS

Appendix 1 to 367283-AI841441 1.1 2012-07-04
TS-87 It shall be possible to configure the voltage level (between 0-UBAT) used
for startup or wakeup.
3.3 FUNCTIONS AND PERFORMANCE IN DIFFERENT

OPERATIONAL PHASES
3.3.1 Startup
TS-88 The BOX operating system shall be operational within 15 seconds from
power-on.
3.3.2 Visual feedback

TS-89 Indicating in Visual Feedback System shall be possible to turn off.
3.3.3 BOX to PC host communication performance

3.3.3.1 J2534 Throughput for J1708
In all the requirements of this section time shall be measured from calling
PassThruWriteMsgs to when the echoed message is received with
PassThruReadMsgs. The time for a sequence of 100 messages shall be used. These
requirements apply to an adapter connected via USB when no other nodes are
connected on the J1708 bus.
TS-90 100 messages of length 21 at 9600 baud must be finished in less than 3100
ms.
TS-91 100 messages of length 128 at 9600 baud must be finished in less than
14500 ms.
27100 ms.
1900 ms.
7500 ms.
13800 ms.
1000 ms.
2000 ms.
2900 ms.
System
TS

Appendix 1 to 367283-AI841441 1.1 2012-07-04
3.3.3.2 J2534 Throughput for CAN

TS-99 A busload of 100 % on the CAN network shall be supported with full
performance. This means the adapter shall be able to receive frames on the
CAN network and send them on the USB link to the PC without missing
any frames during infinite (or a very long > 24 hours) time.
3.3.3.3 J2534 Throughput for IS0151765

TS-100 The maximum time from the start of sending 1 000 000 bytes in the
Transmitter until all the data has been received in an identical unit
connected back to back performing a loopback test is given by the
following table:
CAN-bus baud rate 250 kbit/s 500 kbit/s 1 Mbit/s
Maximum time (seconds) 79 39 20
4 HARDWARE AND INTERFACE REQUIREMENT

.
4.1 GENERAL
BOX with connectors and cable shall be sealed, shielding and filtering to fulfill
environmental requirements when used in tasks for logging of vehicle operational
data.
TS-101 All connectors shall comply with environmental requirements both plugged
(unused) and connected (used).
TS-102 All connectors shall be female unless otherwise specified.
4.1.1 Mechanical
TS-103 The casing shall be in metal.
TS-104 The color shall be military green (color code: 0x0022FF).
TS-105 The box shall have a designated chassis ground connection point.
TS-106 The BOX shall be prepared with holes, rails or nuts for in-vehicle
mounting.
TS-107 The BOX shall be minimized regarding to physical volume.

TS-108 The BOX shall be of a rectangular shape, with maximum dimensions as
follows:
Length: 25 cm
Width: 15 cm
Height: 5 cm
System
TS

Appendix 1 to 367283-AI841441 1.1 2012-07-04
4.1.2 Processing and memory capabilities

TS-109 The CPU shall have the performance of an ARM9 with a clock frequency
of 400MHz, or higher.
TS-110 The system shall have at least 128 MB of RAM free for custom
applications.
TS-111 The hardware shall have at least 256 MB of persistent storage free for
custom applications.
4.1.3 VCAB
TS-112 The VCAB shall have an OBD-II Type B 24V capable of operating on both
24 V and 12 V vehicles.
TS-113 The pin-out definition shall be according to SAE1962[J1962] for the
VCAB.
TS-114 The pin-selection shall be according to SAEJ2534-2[J2534-2] for the
VCAB.
TS-115 The length of VCAB cable shall be between 2-3 meters.
TS-116 The CAN wire method, shielding and dimensions shall comply with the
hardware requirements of each communication method (e.g., J1939) for the
VCAB.
TS-117 The VCAB shall fit in to BOX without adapters.
TS-118 The EMC properties and solution of VCAB shall be addressed in the EMC
control plan regarding EMC issues when connected to different kinds of
vehicles and machinery.
4.2 ELECTRICAL
TS-119 The BOX shall be able to be powered through the VCAB.
TS-120 The BOX shall be able to be powered by an external power supply other
than through the VCAB.
TS-121 The VCAB power source shall be prioritized over the external power
supply.
TS-122 The BOX shall be able to operate on input voltage between 7-38V on both
power connectors.
TS-123 A switch between the two power supplies shall not affect the performance
of the BOX or OBA, e.g., if the power from VCAB is lost and power is
now drawn from an external source the operating system shall still be
running.
TS-124 The BOX shall not have power consumption over 4 W when no external
components are connected via USB.
TS-125 The BOX in sleep mode shall not consume over 150 mW.
System
TS

Appendix 1 to 367283-AI841441 1.1 2012-07-04
TS-126 The impedance between chassis ground and the case shall fulfill
requirements according to DIT03.B DEF-STAN 61-5 part 6 or equivalent.
TS-127 All subsystem shall be galvanically isolated, e.g., power supply and signal
interfaces.
4.3 EXTERNAL INTERFACE

4.3.1 Supply
4.3.1.1 Connector A (con A)
TS-128 The connector A of BOX shall be used for VCAB.
TS-129 The connector A of BOX shall be classified according to MIL STD or
equivalent.
TS-130 The connector A shall be of bayonet type.
TS-131 The connector A shall have a protective cap to be used when the connector
is unplugged.
TS-132 The connector A shall be of male type.
TS-133 The connector A shall be of shielded type.
4.3.1.2 Connector B (con B)

TS-134 The connector B shall be used for a 7-38V DC 3-pin external power
supply.
TS-135 The connector B shall be an Amphenol 62IN-12E-8-33P-622-RH, or a
compatible connector of matching quality.
TS-136 The connector B shall have a protective cap (Amphenol 62IN-738-08-622-
RH, or a compatible connector of matching quality) to be used when the
connector is unplugged.
TS-137 The connector B of BOX shall be classified according to MIL-DTL-26482
or equivalent.
TS-138 The connector B shall be of male type.
4.3.2 Signal interface

4.3.2.1 Connector C (Con C)
TS-139 The connector C shall contain 1 USB device.
TS-140 The connector C shall have a protective cap to be used when the connector
is unplugged.
System
TS

Appendix 1 to 367283-AI841441 1.1 2012-07-04
4.3.2.2 Connector D (Con D)

TS-141 The connector D shall contain 1 USB host.
TS-142 The connector D shall have a protective cap to be used when the connector
is unplugged.
4.3.2.3 Connector E (Con E)

TS-143 The connector E shall contain 1 USB host.
TS-144 The connector E shall have a protective cap to be used when the connector
is unplugged.
4.3.2.4 Connector I (Con I)

TS-145 The connector I shall be composed of one or several connectors.
TS-146 The connector I shall contain one input for external start signal.
TS-147 The connector I shall contain 4 x digital inputs.
TS-148 The connector I shall contain 4 x digital outputs.
TS-149 The connector I shall contain 4 x 4-20mA analog inputs.
TS-150 The connector I shall contain 4 x analog outputs, 0-20mA, 0-10V and 5%
tolerance.
TS-151 The connector I shall support the flexible UART (TS-9 to TS-11).
TS-152 The connector I shall be a MIL-STD classified coupling or corresponding.
TS-153 The connector I shall be of bayonet type or equivalent.
TS-154 The connector I shall have a protective cap to be used when the connector
is unplugged.
TS-155 The connector I shall be of shielded type.
4.3.2.5 Connector H (con H)

TS-156 The connector H of BOX shall be used for Ethernet.
TS-157 The connector H shall be an 8P8C modular connector (RJ-45).
TS-158 The connector H shall have a protective cap to be used when the connector
is unplugged.
4.3.3 Optical interfaces

4.3.3.1 Connector F (con F)
TS-159 The connector F of BOX shall be used for optical Ethernet.
TS-160 The IP fiber cables and panel connectors shall be PRO BEAM Jr.
Connectors, or equivalent.
System
TS

Appendix 1 to 367283-AI841441 1.1 2012-07-04
TS-161 The connector F shall have a protective cap to be used when the connector
is unplugged.
TS-162 The connector F shall be in compliance with MIL-DTL-38999 or
equivalent.
TS-163 The connector F shall be of bayonet type or equivalent.
4.3.3.2 Connector G (con G)

TS-164 The connector G of BOX shall be used for optical Ethernet.
TS-165 The IP fiber cables and panel connectors shall be PRO BEAM Jr.
Connectors, or equivalent.
TS-166 The connector G shall have a protective cap to be used when the connector
is unplugged.
TS-167 The connector G shall be in compliance with MIL-DTL-38999 or
equivalent.
TS-168 The connector G shall be of bayonet type or equivalent.
4.4 MEN-MACHINE INTERFACE

4.4.1 Manoeuvring, presentation and management
4.4.1.1 Visual Feedback System
TS-169 The Visual Feedback System shall indicate to the user if the power is on or
off.
TS-170 The Visual Feedback System shall indicate to the user if the firmware is
OK or not.
TS-171 The Visual Feedback System shall indicate to the user if there is a USB
connection or not.
TS-172 The Visual Feedback System shall indicate to the user if there is a USB
communication in progress or not.
TS-173 The Visual Feedback System shall indicate to the user if there is an
Ethernet connection established or not.
TS-174 The Visual Feedback System shall indicate to the user if there is an
Ethernet communication in progress or not.
TS-175 The Visual Feedback System shall indicate to the user if there is a
connection to the vehicle or not.
TS-176 The Visual Feedback System shall indicate to the user if there is bus
activity in the vehicle or not.
System
TS

Appendix 1 to 367283-AI841441 1.1 2012-07-04
5 ENVIROMENTAL REQUIREMENT
5.1 GENERAL
The environmental requirements in Chapter 5 do not necessarily need to be verified by an external
party or officially certified. It is up to the Contractor to choose an appropriate method of testing and
evaluation, and prove to FMV that the requirements will be sufficiently met, and that the BOX will
function properly in its intended operating environments.
5.2 ENVIROMENTAL DURABILITY

At specified susceptibility tests the following performance criteria applies. Any loss of
function during testing shall be recorded in the Test Report.
Performance Criterion A: Full function during stress

The system shall continue to operate as intended during and after each test. No degradation
of performance or loss of function or unwanted operation is allowed.
Performance Criterion B:
The system shall continue to operate as intended after the disturbance is removed. After the
test, no degradation of performance or loss of function or unwanted operation is allowed.
However, no malfunctioning considering data consistency in transmission or display is
allowed during test.
5.2.1 Mechanical environment

TS-177 The system shall be resistant to vibrations at a level in accordance with IEC
60068-2-64, [IEC60068-2-64], or equivalent.
TS-178 The system shall be resistant to free fall at a level in accordance with IEC
TS-179 The system shall be resistant to shock at a level in accordance with IEC
5.2.2 The climate in the environment

TS-180 The system shall be possible to store and use with full functionality,
performance criteria A, in temperatures between -25°C to +55°C and
relative humidity of up to 98 %.
TS-181 The system shall be resistant to changes in temperature, humidity and
vibration in accordance with IEC 60068-2-53 [IEC60068-2-53], or
equivalent.
System
TS

Appendix 1 to 367283-AI841441 1.1 2012-07-04
TS-182 The system shall be resistant to changes in temperature in accordance with

IEC 60068-2-14, test Na [IEC60068-2-14], or equivalent.
TS-183 The system shall be resistant to a low-temperature environment in
accordance with IEC 60068-2-1, test A [IEC60068-2-1], or equivalent,
under duration of at least 16 hours.
TS-184 The system shall be resistant to a high-temperature environment in
accordance with IEC 60068-2-2, test B [IEC60068-2-2], or equivalent,
under duration of at least 16 hours.
TS-185 The system shall be resistant to corrosion and salt mist at a level in
accordance with IEC 60068-2-52, severity level 2 [IEC60068-2-52], or
equivalent.
5.2.3 Electromagnetic environment

5.2.3.1 Radiated emissions
TS-186 Radiated emissions, electric field. The system shall comply with the
requirements for electric field emissions in accordance with MIL-STD-
461F, RE102, Army Ground, a tailored 10 dB more stringent requirement
(14 dB µV/m) in the frequency range 2 MHz to 470 MHz has to be met, or
equivalent.
5.2.3.2 Conducted emissions

TS-187 Conducted emissions, power leads. The system shall comply with the
requirements for conducted electromagnetic emissions for power input
leads, including returns, in the frequency range 10 kHz to 10 MHz in
accordance with and tested according to MIL-STD-461F, CE102, or
equivalent.
TS-188 The system shall comply the requirements for ripple and exported
transients in feeding in accordance with and tested according to DEF
STAN 61-5 (Part 6), Issue 6, DET01.B, DET02.B, or equivalent.
5.2.3.3 Radiated susceptibility, electric fields

TS-189 The system shall comply with the Performance Criterion A when exposed
to radio and radar fields in accordance with MIL-STD-461F, RS103, Army
Ground (50 V/m), 2 MHz - 18 GHz, or equivalent.
5.2.3.4 Conducted susceptibility

TS-190 Conducted susceptibility, power leads. The system shall comply with the
System
TS

Appendix 1 to 367283-AI841441 1.1 2012-07-04
Performance Criterion A when sinusoidal voltage in the frequency range 30

Hz - 50 kHz are coupled onto input power leads in accordance with and
tested according to MIL-STD-461E, CS101, equivalent.
TS-191 Bulk cable injection. The system shall comply with the Performance
Criterion A when RF signals are coupled onto the BOX associated cabling
in accordance with and tested to MIL-STD-461F, CS114, Army Ground, or
equivalent.
TS-192 Susceptibility to transients. The system shall comply with the Performance
Criterion A in accordance with and tested according to DEF STAN 61-5
(Part 6), DIT07.B, or equivalent.
TS-193 Susceptibility to voltage variations and transients. The system shall comply
with the Performance Criterion A at voltage variations and transients on
DC input in accordance with and tested according to DEF STAN 61-5 (Part
6), Issue 6, DIT06.B, DIT07.B, or equivalent.
TS-194 Susceptibility to voltage variations and transients. The system shall comply
with the Performance Criterion B at voltage variations and transients in
feeding DC in accordance with and tested according to DEF STAN 61-5
(Part 6), Issue 6, DIT04.B, DIT05.B, DIT08.B, or equivalent.
5.2.3.5 Exported transients

TS-195 The system shall meet the requirements for exported transients in
accordance with and tested according to DEF STAN 61-5 (Part 6),
DET02.B, or equivalent.
5.2.3.6 Immunity to electrostatic discharge, ESD

TS-196 The system shall comply with the Performance Criterion A (B for highest
test level) when the equipment is exposed to electrostatic discharge during
normal handling in accordance with and tested according EN 61000-4-2,
Test level 4, or equivalent.
TS-197 Equipment or parts of equipment sensitive to ESD during repair and
maintenance shall be labeled.
5.2.4 Special and combined environments

TS-198 The BOX shall at least have a level of ingress protection according to the
IP65 classification [IEC60529], or equivalent.
6 SYSTEM SAFETY REQUIREMENTS

TS-199 The BOX shall comply with the EU product legislation according to
electrical products.
System
TS

Appendix 1 to 367283-AI841441 1.1 2012-07-04
7 RELIABILITY AND MAINTENANCE

REQUIREMENTS
7.1 RELIABILITY AND MAINTAINABILITY
TS-200 The MTBF of each component in the system shall be at least 100000 hours.
TS-201 The system shall not require reoccurring maintenance to enhance the
corrosion protection.
7.2 SOFTWARE
TS-202 There shall be a toolchain supplied to build user level applications (OBA)
as well as the BOX operating system.
TS-203 The toolchain shall use GCC[GCC] to cross-compile for the specific target
used by the BOX.
7.2.1 Software structuring

TS-204 It shall be possible to read the version number of all delivered software
components.
7.2.2 Software language

TS-205 The language in the software/source code for any written text, comments,
variable names, etc. shall be English.
7.2.3 Software license

TS-206 There shall not be any licensing costs for software that is running at the
BOX.
7.2.4 Delivery form

TS-207 A complete version of the operating system that can be installed to the
BOX’s persistent storage shall be delivered.
7.2.5 Access control systems

TS-208 Default passwords shall be provided for all user accounts.
TS-209 A default password shall be provided for SSH.
System
TS

Appendix 1 to 367283-AI841441 1.1 2012-07-04
8 DOCUMENTATION REQUIREMENTS
8.1 GENERAL
8.1.1 Document types
The document types that the Contractor shall deliver can be described as follows.
• Drawing for spare part catalog – Chapter 8.2.1.
• List for supply registration – Chapter 8.2.2.
• Software documentation – Chapter 8.3.
8.1.2 Language
TS-210 All delivered documents shall be in English or Swedish.
8.2 INFORMATIVE DOCUMENTS

8.2.1 Drawing document
TS-211 The Contractor shall deliver a CAD image of the overall system for use in
spare part catalog or kit list.
8.2.2 The basis for the supply data

TS-212 The Contractor shall provide data terms for registration of supplies.
TS-213 The data of supplies shall include articles that facilitate overall accounting
of supplies as well as inventory management of spare parts and
disposables.
8.3 SOFTWARE DOCUMENTATION

TS-214 Documentation on how to setup, develop and build user-applications
(OBA) for the BOX operating system shall be delivered.
TS-215 Documentation on how to setup, develop and build PC-host DLLs and
device drivers shall be delivered.
TS-216 The supplier’s development environment including operating system and
source code shall be packaged as a virtual machine and placed in a location
determined in consensus between FMV and the Contractor. All hardware
Design specifications, CAD figures, Bill of materials, descriptions of the
manufacturing process and the supplier’s contacts shall be deposited as
well.
System
TS

Appendix 1 to 367283-AI841441 1.1 2012-07-04
9 References
CAN ISO11898, Road vehicles – Controller area
network (CAN) – Part 1: Data link layer and
physical signaling
EMCS DI-EMCS-80199C, Electromagnetic Interference
Control Procedures
ESMP Ministry of Defence – Defence Standard 61-5
Part 6, Issue 6 Publication Date 6th February
2009, Nominal 12V and 24V DC Electrical
Systems in Military Platforms
GCC GNU Compiler Collection, http://gcc.gnu.org/
IEC60068-2-1 Environmental testing - Part 2-1: Tests - Test A:
Cold
IEC60068-2-2 Environmental testing - Part 2-2: Tests - Test B:
Dry heat
IEC60068-2-14 Environmental testing – Part 2-14: Test Na,
Rapid change of temperature with prescribed
time of transfer
IEC60068-2-27 Environmental testing - Part 2-27: Tests - Test Ea
and guidance: Shock
IEC60068-2-32 Environmental testing - Part 2-31: Tests - Test
Ec: Rough handling shocks, primarily for
equipment-type specimens
IEC60068-2-52 Environmental testing - Part 2-52: Tests –
Corrosion and salt mist, severity level 2
IEC 60068-2-53 Environmental testing - Part 2-53: Tests and
guidance – Combined climatic
(temperature/humidity)
and dynamic (vibration/shock) tests
IEC60068-2-64 Environmental testing - Part 2-64: Tests - Test
Fh: Vibration, broadband random and guidance
IEC60529 IEC 60529, Degrees of protection provided by
enclosures (IP Code).
ISO11452-1 Road vehicles -- Component test methods for
electrical disturbances from narrowband radiated
electromagnetic energy -- Part 1: General
principles and terminology
ISO14230-4 ISO 14230-1:1999 Road vehicles -- Diagnostic
systems -- Keyword Protocol 2000 -- Part 4: ??
communication over Controller Area Network
System
TS

Appendix 1 to 367283-AI841441 1.1 2012-07-04
(DoCAN) -- Part 2: Transport protocol and

network layer services
communication over Controller Area Network
(DoCAN) -- Part 4: Requirements for emissions-
related systems
ISO16750-3 ISO 16750-3:2007 Road vehicles --
Environmental conditions and testing for
electrical and electronic equipment -- Part 3:
Mechanical loads
ISO22900-2 ISO 22900-2:2009. Road vehicles -- Modular
vehicle communication interface (MVCI) -- Part
2: Diagnostic protocol data unit application
programming interface (D-PDU API)
ISO9141 International Standard ISO 9141 Road Vehicles –
Diagnostic systems – Requirements for
interchange or digital information
J1587 SAE J1587 Surface vehicle recommended
practice
J1708 SAE J1708 Serial data communications between
microcomputer systems in heavy-duty vehicle
applications.
J1939 SAE J1939/71 Surface vehicle recommended
practice
J1962 SAE, “J1962”, 2002
J2534-1 SAE, ”J2534-1”, 2004.
J2534-2 SAE, ”J2534-2” , 2009.
MS-WDF Microsoft, ”Windows Driver Foundation,”
Microsoft, [Online]. Available:
http://msdn.microsoft.com/en-
us/windows/hardware/gg463268.aspx.
MS-WLK Microsoft, ”WLK Logo Tests,” Microsoft,
[Online]. Available:
http://msdn.microsoft.com/en-
us/library/ff564396%28v=VS.85%29.aspx.
RP1210B TMC, ”RP 1210B,” 2007.
USB1 USB.org, ”USB Specifications,” [Online].
Available: http://www.usb.org/developers/docs/.
USB2 USB.org, ”USB20CV,” [Online]. Available:
http://www.usb.org/developers/tools/.
USB3 USB.org, ”USB30CV,” [Online]. Available:
http://www.usb.org/developers/ssusb/ssusbtools.

Vehicle Communication Box: Appendix 1 Technical Specification

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Vehicle Communication Box: Appendix 1 Technical Specification

Transféré par

Droits d'auteur :

Formats disponibles

System

Ansvarig enhet Handläggare Sida

Ansvarig enhet Handläggare Sida

Ansvarig enhet Handläggare Sida

7.1 RELIABILITY AND MAINTAINABILITY .......................................................................................... 29

Ansvarig enhet Handläggare Sida

The following sections outline the details of the scope of supply.

1.3 REVISION HISTORY

1.4 DEFINITIONS AND ABBREVIATIONS

Ansvarig enhet Handläggare Sida

Ansvarig enhet Handläggare Sida

2 SYSTEM DESCRIPTION, PRECONDITIONS

Figure 1. Overview of the system.

Ansvarig enhet Handläggare Sida

The following table explains each figure position shown in Figure 1.

Ansvarig enhet Handläggare Sida

2.2 OVERALL SYSTEM DESCRIPTION

2.2.2 Overall system

2.2.2.2 PC-Host Software

Ansvarig enhet Handläggare Sida

2.2.3 Cooperative, ancillary system

Ansvarig enhet Handläggare Sida

2.3 OPERATIONAL USE

2.3.1.1 Pre-requisites tasks A-B

2.3.1.2 Task A – Service and Repair (maintenance)

2.3.1.3 Task B – Repair (maintenance)

Ansvarig enhet Handläggare Sida

2.3.1.4 Task C – Logging of vehicle operational data (operation)

2.3.2 Operational profile, mission profile

2.3.3 Planned life

2.4 OPERATING CONDITIONS

Ansvarig enhet Handläggare Sida

2.4.1 Operation organization

Ansvarig enhet Handläggare Sida

3 FUNCTIONAL AND PERFORMANCE

Figure 5. Architectural view.

Ansvarig enhet Handläggare Sida

3.1.2 Main functions

3.1.2.1.1 CAN controllers

3.1.2.1.2 J1708/J1587 Controller

3.1.2.1.5 UART controller

3.1.2.1.6 USB controllers

Ansvarig enhet Handläggare Sida

TS-13 The BOX shall have two USB Host Controllers.

3.1.2.2 Vehicle Interface Module

3.1.2.2.1 Communication with external applications

3.1.2.2.2 Communication with internal applications

3.1.2.2.3 Communication with the vehicle (Vehicle Interface)

Ansvarig enhet Handläggare Sida

according to the ISO15765-2 and the ISO15765-4 standards [ISO15765-2]

3.1.2.3 BOX Operating System

3.1.2.3.2 Network features

Ansvarig enhet Handläggare Sida

3.1.2.3.3 J2534 API

3.1.2.3.4 Miscellaneous APIs

3.1.2.4 PC-Host software

Ansvarig enhet Handläggare Sida

3.1.2.4.2 Device Drivers

3.1.2.4.3 Dynamic Link Libraries

3.1.2.4.4 Vehicle Communication Interface

3.1.2.4.4.1 RP1210 API

3.1.2.4.4.2 ISO 22900-2 API