Skip to content

Latest commit

 

History

History
100 lines (68 loc) · 6.13 KB

README.md

File metadata and controls

100 lines (68 loc) · 6.13 KB
Raw

Shared Vehicle Manager with IOT

Team “Millennium”

Team Leader: Minchan Jung

Team Members: Dahyun Ko, Hokyung Park, Junho Kim, Sujong Ha

Table of Contents

  1. Project Overview
  2. Current Market Situation of Shared Vehicle Management
  3. Project Description
  4. Potential Improvement

Project Overview

This project aims to provide a customized management solution for the shared vehicle industry, enhancing the experience for both vehicle providers and users. To achieve this, we developed a shared vehicle management system utilizing the latest digital twin technology, along with a user-customized application.

Current Market Situation of Shared Vehicle Management

The future of the automotive industry demands Sofware Defined Vehicle (SDV), requiring changes in the shared vehicle market. With the growing shared vehicle market, there is an urgent need to improve vehicle management and user experience. The diverse needs of customers are increasing, and providing efficient vehicle management and enhanced user experiences has become a key factor in market competition.

Project Description

Project Architecture

Ideal Structure

ideal

For Hackathon

hackathon

Shared Vehicle Management System

  • Overview

    The shared vehicle management system utilizes digital twin technology to monitor and manage aspects such as the vehicle's battery life, consumable status, and accident occurrences in real-time. New vehicles, when introduced, are efficiently managed centrally through cloud connection, enabling cost reduction in maintenance and quicker response to accidents.

  • Features

    1. Monitors and manages shared vehicles in real-time, including battery life, consumable status, and accident occurrences, using digital twin technology.
    2. When new vehicles are connected our ECU(with custom Leda image), they automatically connect to fleet management system.
    3. Without hardware change, can connect to ECU via eCAL, SOME/IP, CAN
    4. Allows for real-time assessment of vehicle condition, reducing maintenance costs.
    5. Shortens response time to car accidents.
    6. Shared vehicle companies can transparently provide the vehicle's condition to customers.

User-Customized HUD Application

  • Overview

    The user-customized application provides personalized HUD and vehicle settings, ensuring a consistent user experience regardless of the shared vehicle used. The ability to control and set up vehicles through smartphones and customization features based on user accounts contribute to increasing customer satisfaction and loyalty.

  • Features

    1. Provides customized HUDs as desired by customers.
    2. Users enjoy a consistent, personalized experience with any shared vehicle, without the need for adaptation to new vehicles, contributing to increased customer loyalty and satisfaction.
    3. Offers vehicle operation and custom HUD through smartphones, including seat adjustments, air conditioning settings, and audio profiles, from anywhere.
    4. When users login to the vehicle application with their accounts, personalized settings stored in their accounts are applied to the vehicle, allowing customization across different types of shared vehicles.
    5. Supports customization of the dashboard through the Head Up Display, encouraging users to choose the same shared vehicle provider to maintain familiar dashboard settings and configurations.
    6. Updates for the app and firmware are possible through Leda's OTA (Over-The-Air).
    7. There is No need for companies to provide hardware for HUD.

Potential Improvement

  1. Beyond HUD, the possibility of providing customized Head Units and Instrument Clusters.
  2. Emphasizing scalability for integration with future vehicle technologies.
  3. Expanding service scope through continuous technological innovation.
  • Change MonitorIP in forwarder-setting.env
  • Send influxdb.token to /etc/forwarder/influxdb.token

on the (local) host that you have started the back end components on

docker exec -it influxDB cat /tmp/out/fms-demo.token > /tmp/influxdb.token

The FMS Forwarder needs to read the token required for authenticating to influxdb.

scp -P 2222 /tmp/influxdb.token root@127.0.0.1:/data/usr/fms/forwarder

Run leda images built by yocto

qemu-system-x86_64 -net nic -net user,hostfwd=tcp::2222-:22,hostfwd=tcp::1880-:1880,hostfwd=tcp::1884-:1883,hostfwd=tcp::8888-:8888,hostfwd=tcp::30555-:30555 -device virtio-blk,drive=hd,bootindex=1 -drive if=none,id=hd,file=sdv-image-all-qemux86-64.wic.qcow2,format=qcow2 -usb -device usb-tablet -serial mon:stdio -object can-bus,id=canbus0 -device kvaser_pci,canbus=canbus0 -bios ovmf.qcow2 -cpu IvyBridge -machine q35 -smp 4 -m 4G