Fleet Edge System Specification & User Guide

Fleet Edge Overview

Fleet Edge is an edge compute system designed for deployment on Amazon delivery vehicles. It provides an in-vehicle machine learning platform for map data acquisition, route generation, and driver metrics, offering significant business value to Last Mile organizations. The system is built as a flexible edge-compute platform with an API for developing and deploying applications by various Amazon business teams.

The initial version of the Fleet Edge system features a 6-core Intel CPU architecture for its large compute capacity and ease of development with existing AWS frameworks. Intel MyriadX VPUs were chosen for their low cost and small size, enabling parallel execution of multiple independent ML tasks. A modular VPU-card approach allows for integration of next-generation Intel VPU performance improvements without altering the system architecture. Future cost-optimized SoC-based Fleet Edge systems may use more monolithic ML processors, but this multi-VPU architecture allows for broader exploration of the application space before optimization.

Compute Hardware

Physical Characteristics

All connectivity is consolidated on one side for enhanced protection and ease of installation. The system features a fan-less design for improved reliability. The system dimensions are 260mm x 313mm x 80mm.

Test Specs

• ISO16750_4.2.2 shock
• IEC 60068-2

Power Supply

The power supply input range is 9-36VDC. It must maintain system performance even when vehicle voltage drops as low as 7V for 100ms during engine cranking. The power supply must be automotive-grade and capable of filtering noisy signals from the alternator and starter. A relay, controlled by the watchdog MCU, is in-line with the +12VDC input. When this relay is open, only the MCU and its sensors receive power.

CPU

The FE system is designed to work with any 35W Intel Coffee Lake CPU, with the i5-8500T being a particular focus. Amazon is collaborating with Intel to confirm the optimal CPU for this application.

Chipset

Cannon Lake Q370 is recommended due to its thermal operation range.

RAM

1 SO-DIMM @2666MHz, with 8GB or 16GB capacity to be determined (TBD), specified for high-temperature operation.

Storage

M.2 SATA SSD, with 512GB or 1TB capacity TBD, also specified for high-temperature operation. The system includes 2 M.2 slots, allowing for a more cost-effective 1TB storage solution using two 512GB drives.

Watchdog System

For enhanced reliability, the system incorporates a watchdog microcontroller capable of cutting the 12V power to the rest of the system. This ensures minimal power draw from the vehicle battery when the system is off. This microcontroller also manages system power-up and power-down based on the ignition signal. It controls the system's power button signal to turn the Intel Core processor on and off.

The microcontroller is equipped with sensors to monitor ambient temperature, battery voltage, and the wall clock time. These sensors ensure the vehicle battery and Fleet Edge system are protected at all times. Sensor data is logged continuously, even when the system is powered off, and later uploaded to the cloud by the Fleet Edge OS.

The following parameters can be configured from the Intel Core processor to the watchdog MCU via a serial interface:

• Power on delay: [0,360] seconds (default 10 seconds)
• Power off delay: [0,360] minutes (default 5 minutes)
• Low and high temperature safety limits: each [-30, -100] °C range (defaults [0-60] °C)
• Low voltage shutdown level: [1-30] volts (default 11 volts)

Log Data

Sensor data is logged internally when the system is off, storing up to 7 days of data. Upon system power-up, the CPU can retrieve this logged data using UART protocol. A keep-alive watchdog mechanism from the CPU triggers a reboot via relay if a heartbeat message is not received within 1 minute.

The Watchdog MCU supports ROM bootloader and COM firmware update protocols for secure firmware updates.

Error Status

The system features a two-digit seven-segment display to show error codes for installation or service technicians. This display is controlled by the system's UEFI BIOS during boot and by the operating system once available. A service checklist will be generated based on error codes to aid in system or sensor service.

Automotive GPIO

General-purpose Input/Output (GPIO) connections are available for monitoring vehicle functions or controlling peripherals. For instance, an input can track the state of a vehicle door via a simple switch, or a GPIO output can control an indicator light on the vehicle dashboard.

There are 4 GPIO Inputs and 4 GPIO outputs available. All GPIO connections are isolated from the mainboard. Inputs should register 0V as FALSE and 7-20V as TRUE. GPIO Outputs are designed with relays capable of switching 20A at 12V for up to 200,000 cycles.

Other I/O

• CAN: Currently via DB-9 connector (Amazon will review). Supports 250kbps or 125kbps.
• 4x USB ports
• HDMI-out: For system bring-up and testing purposes only.
• 1 Automotive Ethernet port: Via Marvell 88Q2122 and TE MATENET 9-2304372-9 connector.
• 1 Standard Ethernet port: (Or use USB Ethernet for non-production items - NPI).

System Power-on Timing

Hardware Components

Several hardware components are involved in the power-on sequencing of the Fleet Edge system. The supervisor MCU is directly connected to the vehicle battery and is always active. It utilizes low-power sleep modes and hardware watchdog monitoring to prevent crashes or battery depletion. The supervisor MCU receives input from various sensors to determine vehicle status and controls a virtual power button for the main compute subsystem. This allows it to monitor the vehicle state and power the high-power compute subsystem on or off accordingly. Examples include powering down the computer due to low battery voltage or preventing power-up if the air temperature is too high.

Ignition Signal

The ignition signal is a 12V wire connected to the vehicle, active when the key is in the active state (even without starting the engine). This signal connects to the supervisor MCU and is also sent to the Fleet Edge mainboard, allowing the operating system to monitor the ignition switch state independently.

Battery Voltage

Both the supervisor MCU and the operating system can monitor battery voltage via an analog-to-digital converter. The supervisor MCU uses this data for decisions on powering the compute subsystem up or down. The operating system monitors voltage to manage its power consumption. The OS can determine if the engine is running (battery voltage > 13.8V, indicating alternator function). Only in this state will full compute resources be engaged. If the engine is off but the ignition is on (e.g., during loading), the OS will maintain a 'low power' state before powering down.

Timing Parameters

Several configurable timings control the power-on sequence, with current default values:

• Ignition on to system power on: 10 second default. This delay allows the vehicle to start up before the Fleet Edge system draws power, preventing issues during engine cranking on ICE vehicles.
• Ignition off to system power down: 3 minute default. This delay prevents the system from powering down when the vehicle is briefly parked between delivery stops. Analysis indicates this covers about 90% of stops.
• Overnight system wake time: 0200 default. The supervisor MCU can wake the compute system at a set time. The system can then check if ignition is enabled and remain in low-power mode, or monitor battery voltage to prevent drainage.

AI Hardware

The Fleet Edge system includes specialized hardware processors for machine-learning tasks. To support multiple independent ML tasks, multiple small Visual Processing Units (VPUs) are preferred over a single, monolithic GPU-style processor.

GPS Interface

Fleet Edge utilizes a Precision GNSS module from Swift Navigation. GPS module antenna connectors are routed through the motherboard and terminated with Fakra connectors on the interface panel.

CAN

The preferred CAN interface for 2020 involves custom UIM firmware developed by the OEM to create a private CAN network for Amazon devices, supplying necessary vehicle information while ensuring safety and reliability. The private interface connector is typically located in the dashboard in front of the passenger seat, connected via a CAN-certified shielded twisted-pair cable to the PC's DB-9 connector. This private Amazon network is being explored for Ford vehicles, with similar interfaces planned for other OEMs.

For installations prior to the Amazon-private network's readiness, the Fleet Edge system can connect directly to the UIM module in Ford vehicles. The UIM location is consistent with the Amazon private network hub, requiring only a connector change.

Antenna

Antennas are roof-mounted for optimal GPS performance in urban environments. Installation requires drilling a 1" hole in the vehicle's sheet metal roof, sealing the exposed metal, routing cables, and securing with adhesive. The Fleet Edge team collaborates with vehicle OEMs and upfitters to ensure installation integrity.

For best performance, the GPS antenna should be mounted on a flat surface, parallel to the ground. If separate, the LTE antenna should also be mounted flat, though its positioning is less critical than the GPS antenna. If separate, the two antennas require a minimum spacing.

Power

The power interface consists of three signals: +12V, Ground, and Ignition. Vehicle types typically provide a +12V stud connection for upfitter applications. The Fleet Edge wiring harness includes a power wire with a 6mm ring terminal for interfacing with the +12V CCP1 post (marked "B" in the diagram).

The ground wire features a similar eyelet connector for attachment to one of the vehicle's provided ground studs.

Ignition Signal Connection

The ignition signal is sourced from a vehicle-specific connection point. For Ford vehicles, this is accessible via a 10-pin connector located under the driver seat. Fleet Edge systems configured for Ford Transit vehicles are supplied with this connector for expedited installation.

Appendix: Power on procedure and Error Codes

Power on procedure

1. Connect the Fleet Edge box using an Ethernet cable and the LTE/Wi-Fi Antenna, then turn on the power switch.
2. Wait approximately 3 minutes for DV units to complete initialization, indicated by a code. If 'U9' is displayed, initialization is successful, and no diagnostic issues were detected.
3. If a code other than U9 appears, follow the debugging guide for correction. Log the error code for reporting to Amazon.
4. Turn off the PC during repair. After repair completion, turn the system on again and repeat from step 1.

Error Codes

Error Corrections

• GNSS_MODULE_FAIL: The PC cannot communicate with the GNSS module. Suggested action: Replace the GNSS module or verify internal connection.
• LTE_MODULE_FAIL: The PC cannot communicate with the LTE module. Suggested action: Replace the LTE module or verify internal connection.
• SIM_NOT_PRESENT: The PC cannot detect the SIM card in the LTE module. Suggested action: Verify SIM card presence. If present, replace the SIM card.
• REPLACE_SIM_CARD: The PC cannot communicate with the SIM card via the LTE module. Suggested action: Replace the SIM card.
• TPM_MODULE_FAIL: The PC cannot communicate with the TPM module. Suggested action: Replace the TPM module on the main board. If no TPM issue, clear TPM using BIOS and reinstall Amazon OS.
• WIFI_MODULE_FAIL: The PC cannot communicate with the Wi-Fi module. Suggested action: Replace the Wi-Fi module or verify internal connections.
• VPU_MODULE_FAIL: The PC cannot communicate with the Movidus module. Suggested action: Replace the Movidus module or verify internal connections.
• SSD_MODULE_FAIL: Critical errors detected on the SSD during deep checks. Suggested action: Replace the SSD and reinstall the Amazon OS image.
• RE_INSTALL_OS: The Fleet Edge box is in an unstable state. Suggested action: Reinstall the Amazon OS and reconnect to the internet.
• NO_INTERNET_ACCESS: The Fleet Edge box cannot access the internet. Suggested action: Check Ethernet connection and reboot the machine.

FCC Compliance

This device complies with Part 15 of the FCC Rules. Operation is subject to conditions that prevent harmful interference and require acceptance of any received interference. The equipment has been tested and found to comply with Class B digital device limits, designed for reasonable protection against harmful interference in residential installations. It generates radio frequency energy and may cause interference if not installed per instructions.

Users experiencing interference are encouraged to try one or more of the following measures:

• Reorient or relocate the receiving antenna.
• Increase separation between the equipment and receiver.
• Connect the equipment to a different circuit than the receiver.
• Consult a dealer or experienced radio/TV technician.

FCC Caution: Any changes or modifications not expressly approved by the responsible party could void the user's authority to operate this equipment. This transmitter must not be co-located or operated with any other antenna or transmitter.

This device meets other requirements specified in Part 15E, Section 15.407 of the FCC Rules.

Radiation Exposure Statement: This equipment complies with FCC radiation exposure limits for an uncontrolled environment. It should be installed and operated with a minimum distance of 20cm between the radiator and your body.