Beruflich Dokumente
Kultur Dokumente
TS
Teknisk specifikation
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
Teknisk specifikation
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
Teknisk specifikation
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).
1.2 APPLICATION
This RFQ document is intended for suppliers of electronic diagnostic devices.
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
Teknisk specifikation
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
Teknisk specifikation
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 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
Teknisk specifikation
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.
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.
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
Teknisk specifikation
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.
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.
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.
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.
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.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.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
Teknisk specifikation
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.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.
TS-87 It shall be possible to configure the voltage level (between 0-UBAT) used
for startup or wakeup.
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.
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
Teknisk specifikation
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.
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.
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.
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.
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.
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.
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: ??
ISO15765-2 ISO 15765-2:2011 Road vehicles -- Diagnostic
communication over Controller Area Network
System
TS
Teknisk specifikation