Skip to content

Commit

Permalink
All documents for 3.0
Browse files Browse the repository at this point in the history
  • Loading branch information
natashadsouza authored and ycool committed Jul 3, 2018
1 parent 2cef6f8 commit 2fa884a
Show file tree
Hide file tree
Showing 100 changed files with 1,404 additions and 80 deletions.
17 changes: 17 additions & 0 deletions RELEASE.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,20 @@
# Release 3.0

Apollo 3.0 enables L4 product level solution that allows vehicles to drive in a closed venue setting at a low speed. Automakers can now leverage this one stop solution for autonomous driving without having to customize on their own.

## Major Features And Improvements
* New Safety module called Guardian
* Enhanced Surveillance module - Monitor
* Hardware service layer that will now act like a platform and not a product, giving developers the flexibility to integrate their own Hardware
* Apollo Sensor Unit (ASU)
* New Gatekeeper - Ultrasonic Sensor
* Perception module changes:
- **CIPV detection/ Tailgating** – moving within a single lane
- Whole lane line support - bold line support for long range accuracy. There are 2 different types on installations for Camera, low and high installation.
- **Online pose estimation** – determines angle change and estimates it when there are bumps or slopes to ensure that the sensors move with the car and the angle/pose changes accordingly
- **Visual localization** – we now use camera for localization. This functionality is currently being tested.
- **Ultrasonic Sensor** – Currently being tested as the final gatekeeper to be used in conjunction with Guardian for Automated Emergency brake and vertical/perpendicular parking.

# Release 2.5
This release allows the vehicle to autonomously run on geo-fenced highways. Vehicles are able to do lane keeping cruise and avoid collisions with the leading vehicles.

Expand Down
14 changes: 14 additions & 0 deletions docs/howto/How_to_use_a_different_vehicle.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
# How to use a different vehicle

To add a different Vehicle, you must first follow the [Readme Installation steps](https://github.com/ApolloAuto/apollo/blob/master/README.md) to assemble and launch Apollo successfully.

In order to support a new vehicle in DreamView, please follow the steps below:

1. Create a new folder for your vehicle under `modules/calibration/data`

2. There is already a sample file in the `modules/calibration/data` folder named `mkz_example`. Refer to this structure and include all necessary configuration files in the same file structure as “mkz_example”. Remember to update the configuration files with your own parameters if needed.

3. Restart DreamView and you will be able to see your new vehicle (name is the same as your newly created folder) in the `Vehicle` dropdown menu.

4. Select the newly configured vehicle.

173 changes: 173 additions & 0 deletions docs/quickstart/apollo_3_0_hardware_system_installation_guide.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,173 @@
# Apollo 3.0 Hardware and System Installation Guide

* [About This Guide](#about-this-guide)
* [Document Conventions](#document-conventions)
* [Introduction](#introduction)
* [Documentation](#documentation)
* [Key Hardware Components](#key-hardware-components)
* [Additional Components Required](#additional-components-required)
* [Steps for the Installation Tasks](#steps-for-the-installation-tasks)
* [At the Office](#at-the-office)
* [In the Vehicle](#in-the-vehicle)
* [Prerequisites](#prerequisites)
* [Diagrams of the Major Component Installations](#diagrams-of-the-major-component-installations)
* [Additional Tasks Required](#additional-tasks-required)
* [Next Steps](#next-steps)


## About This Guide

The *Apollo 3.0 Hardware and System Installation Guide* provides the instructions to install all of the hardware components and system software for the **Apollo Project**. The system installation information included pertains to the procedures to download and install the Apollo Linux Kernel.

### Document Conventions

The following table lists the conventions that are used in this document:

| **Icon** | **Description** |
| ----------------------------------- | ---------------------------------------- |
| **Bold** | Emphasis |
| `Mono-space font` | Code, typed data |
| _Italic_ | Titles of documents, sections, and headings Terms used |
| ![info](images/info_icon.png) | **Info** Contains information that might be useful. Ignoring the Info icon has no negative consequences. |
| ![tip](images/tip_icon.png) | **Tip**. Includes helpful hints or a shortcut that might assist you in completing a task. |
| ![online](images/online_icon.png) | **Online**. Provides a link to a particular web site where you can get more information. |
| ![warning](images/warning_icon.png) | **Warning**. Contains information that must **not** be ignored or you risk failure when you perform a certain task or step. |

## Introduction

The **Apollo Project** is an initiative that provides an open, complete, and reliable software platform for Apollo partners in the automotive and autonomous driving industries. The aim of this project is to enable these entities to develop their own self-driving systems based on the Apollo software stack.

### Documentation

The following set of documentation describes Apollo 3.0:

- ***<u>[Apollo Hardware and System Installation Guide]</u>*** ─ Provides the instructions to install the hardware components and the system software for the vehicle:

- **Vehicle**:

- Industrial PC (IPC)
- Global Positioning System (GPS)
- Inertial Measurement Unit (IMU)
- Controller Area Network (CAN) card
- GPS Antenna
- GPS Receiver
- Light Detection and Ranging System (LiDAR)
- Camera
- Radar
- Apollo Sensor Unit (ASU)

- **Software**:
- Ubuntu Linux
- Apollo Linux Kernel
- NVIDIA GPU Driver

- ***<u>[Apollo Quick Start Guide]</u>*** ─ The combination of a tutorial and a roadmap that provides the complete set of end-to-end instructions. The Quick Start Guide also provides links to additional documents that describe the conversion of a regular car to an autonomous-driving vehicle.

## Key Hardware Components

The key hardware components to install include:

- Onboard computer system ─ Neousys Nuvo-6108GC
- Controller Area Network (CAN) Card ─ ESD CAN-PCIe/402-B4
- General Positioning System (GPS) and Inertial Measurement Unit (IMU) ─
You can select one of the following options:
- NovAtel SPAN-IGM-A1
- NovAtel SPAN® ProPak6™ and NovAtel IMU-IGM-A1
- Navtech NV-GI120
- Light Detection and Ranging System (LiDAR) ─ You can select one of the following options:
- Velodyne HDL-64E S3
- Velodyne Puck series
- Innovusion LiDAR
- Hesai's Pandora
- Cameras — You can select one of the following options:
- Leopard Imaging LI-USB30-AR023ZWDR with USB 3.0 case
- Argus Camera
- Wissen Camera
- Radar — You can select one of the following options:
- Continental ARS408-21
- Delphi ESR 2.5
- Racobit B01HC

### Additional Components Required

You need to provide these additional components for the Additional Tasks Required:

- Apollo Sensor Unit (ASU)
- A 4G router for Internet access
- A USB hub for extra USB ports
- A monitor, keyboard, and mouse for debugging at the car onsite
- Cables: a Digital Visual Interface (DVI) cable (optional), a customized cable for GPS-LiDAR time synchronization
- Apple iPad Pro: 9.7-inch, Wi-Fi (optional)

The features of the key hardware components are presented in the subsequent sections.

## Steps for the Installation Tasks

This section describes the steps to install:

- The key hardware and software components
- The hardware in the vehicle

### At the Office

Perform the following tasks:

- Prepare the IPC:
- Install the CAN card
- Install or replace the hard drive
- Prepare the IPC for powering up

- Install the software for the IPC:
- Ubuntu Linux
- Apollo Kernel
- Nvidia GPU Driver

The IPC is now ready to be mounted on the vehicle.

### In the Vehicle

Perform these tasks:

- Make the necessary modifications to the vehicle as specified in the list of prerequisites
- Install the major components:
- GPS Antenna
- IPC
- GPS Receiver and IMU
- LiDAR's
- Cameras
- Radar


#### Prerequisites

**![warning_icon](images/warning_icon.png)WARNING**: Prior to mounting the major components (GPS Antenna, IPC, and GPS Receiver) in the vehicle, perform certain modifications as specified in the list of prerequisites. The instructions for making the mandatory changes in the list are outside the scope of this document.

The list of prerequisites are as follows:

- The vehicle must be modified for “drive-by-wire” technology by a professional service company. Also, a CAN interface hookup must be provided in the trunk where the IPC will be mounted.
- A power panel must be installed in the trunk to provide power to the IPC and the GPS-IMU. The power panel would also service other devices in the vehicle such as a 4G LTE router. The power panel should be hooked up to the power system in the vehicle.
- A custom-made rack must be installed to mount the GPS-IMU Antenna, the cameras and the LiDAR's on top of the vehicle.
- A custom-made rack must be installed to mount the GPS-IMU in the trunk.
- A custom-made rack must be installed in front of the vehicle to mount the front-facing radar.
- A 4G LTE router must be mounted in the trunk to provide Internet access for the IPC. The router must have built-in Wi-Fi access point (AP) capability to connect to other devices, such as an iPad, to interface with the autonomous driving (AD) system. A user would be able to use the mobile device to start AD mode or monitor AD status, for example.

#### Diagrams of the Major Component Installations

The following two diagrams indicate the locations of where the three major components (GPS Antenna, IPC, GPS Receiver and LiDAR) should be installed on the vehicle:

![major_component_side_view](https://github.com/ApolloAuto/apollo/blob/master/docs/demo_guide/images/Hardware_overview.png)

![major_component_rear_view](images/Car_Rearview.png)

## Additional Tasks Required

Use the components that you were required to provide to perform the following tasks:

1. Connect a monitor using the DVI or the HDMI cables and connect the keyboard and mouse to perform debugging tasks at the car onsite.

2. Establish a Wi-Fi connection on the Apple iPad Pro to access the HMI and control the Apollo ADS that is running on the IPC.

## Next Steps

After you complete the hardware installation in the vehicle, see the [Apollo Quick Start](https://github.com/ApolloAuto/apollo/blob/master/docs/quickstart/apollo_3_0_quick_start.md) for the steps to complete the software installation.

87 changes: 87 additions & 0 deletions docs/quickstart/apollo_3_0_quick_start.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,87 @@
# Apollo 3.0 Quick Start Guide

The following guide serves as a user manual for launching the Apollo 3.0
software and hardware stack on vehicle.

The Apollo 3.0 Quick Start Guide focuses on Apollo 3.0's new features. For general
Apollo concepts, please refer to
[Apollo 1.0 Quick Start](https://github.com/ApolloAuto/apollo/blob/master/docs/quickstart/apollo_1_0_quick_start.md).

## Contents

- [Calibration Guide](#calibration-guide)
- [Hardware and Software Installation](#hardware-and-software-installation)
- [Dreamview Usage Table](#dreamview-usage-table)
- [Onboard Test](#onboard-test)

## Calibration Guide

For the vehicle's onboard testing make sure you have calibrated all the sensors. For
sensor calibration, please refer to
[Apollo 2.0 Sensor Calibration Guide](https://github.com/ApolloAuto/apollo/blob/master/docs/quickstart/apollo_2_0_sensor_calibration_guide.md)
before you proceed.

## Hardware and Software Installation

Please refer to
[Apollo 3.0 Hardware and System Installation Guide](https://github.com/ApolloAuto/apollo/blob/master/docs/quickstart/apollo_3_0_hardware_system_installation_guide.md)
for the steps to install the hardware components and the system software, as well as
[Apollo Software Installation Guide](https://github.com/ApolloAuto/apollo/blob/master/docs/quickstart/apollo_software_installation_guide.md).

## Dreamview Usage Table

For questions regarding Dreamview icons refer to the
[Dreamview Usage Table](https://github.com/ApolloAuto/apollo/blob/master/docs/specs/dreamview_usage_table.md).

## Onboard Test

1. Plug-in an external hard-drive to any available USB port in the host machine.

2. Turn on the vehicle, and then the host machine.

3. Launch Docker Release Container.

4. Launch DreamView.

Note\: Use your favorite browser to access Dreamview web service in your host
machine browser with URL http://localhost:8888.

![](images/dreamview_2_5.png)

5. Select Mode, Vehicle and Map.

![](images/dreamview_2_5_setup_profile.png)

Note\: You'll be required to setup profile before doing anything else. Click
the dropdown menu to select **Navigation** mode, the HDMap and vehicle you
want to use. The lists are defined in
[HMI config file](https://raw.githubusercontent.com/ApolloAuto/apollo/master/modules/dreamview/conf/hmi.conf).

Note\: It's also possible to change the profile on the right panel of the
HMI, but just remember to click `Reset All` on the top-right corner to
restart the system.

6. Start the Modules.

Click the `Setup` button.

![](images/dreamview_2_5_setup.png)

Go to **Module Controller** tab, check if all modules and hardware are ready.
(Note\: In your offline environment, the hardware modules such as GPS,
CANBus, Velodyne, Camera and Radar cannot be brought up.)
(Note\: You may need to drive around a bit to get a good GPS signal.)

![](images/dreamview_2_5_module_controller.png)

7. Under `Default Routing` select your desired route.

8. Under Tasks click `Start Auto`. (Note: Be cautious when starting the autonomous
driving, you should now be in autonomous mode.)

![](images/dreamview_2_5_start_auto.png)

9. After the autonomous testing is complete, under Tasks click `Reset All`, close all
windows and shutdown the machine.

10. Remove the hard drive.
Loading

0 comments on commit 2fa884a

Please sign in to comment.