Initially added MirrorV2 with replay files for AEC2025
parent
048f47ef38
commit
df9dcb64b1
56
ReadMe.md
56
ReadMe.md
|
|
@ -1 +1,55 @@
|
|||
# <u>Name of Demo</u>
#### [Find Repository](https://git.intrepidcs.de/explore/repos)

## General showcase
Short description what will be demonstrated
## Requirements
Used devices, cabeling ...
Maybe adding links to devices (WEB) and files (Internal)\
e.g.
```
[Remote datalogger](https://intrepidcs.com/products/data-loggers/) (neoVI-RED2/Fire3/Connect)
```
[Remote datalogger](https://intrepidcs.com/products/data-loggers/) (e.g. neoVI-RED2/Fire3/Connect)\
## Setup I
Used setups with internal links.\
e.g.
```
Upload [Setup file](OBD_and_GPS_Collection.vs3zip)
```
Upload [Setup file](OBD_and_GPS_Collection.vs3zip)
### Showcase
Individual description of setup
## Setup II
If multiple setups are available
### Showcase
Individual description of setup
|
||||
# <u>Service Oriented Middleware over IP (SOME/IP) DEMO
|
||||
\
|
||||
Instead of RAD-Pluto (discontinued) also RAD-Epsilon could be taken\
|
||||
|
||||
## 1. Preparing neoVI-PIs (working on Ubuntu20.04 OS laptop and Raspberry Pi 4 Model B)
|
||||
* Use [PuTTY](https://www.putty.org/) or [MobaXterm](https://mobaxterm.mobatek.net) to connect to the PIs
|
||||
### 1.1 Building VSOMEIP Stack (Extract from [SOME_IP User Manual.docx](.resources/SOME_IPUser_Manual.docx)
|
||||
* Install dependencies:\
|
||||
``` sudo apt-get install g++ cmake make libboost-all-dev asciidoc source-highlight doxygen graphviz ```
|
||||
* Download VSOMEIP from GENIVI into your home directory:\
|
||||
``` git clone https://github.com/GENIVI/vsomeip ```
|
||||
* Build process:\
|
||||
``` cd vsomeip ```\
|
||||
``` mkdir build ```\
|
||||
``` cd build ```\
|
||||
``` cmake -DENABLE_SIGNAL_HANDLING=1 ..```
|
||||
* Creates the libraries for VSOMEIP: ``` make ```
|
||||
- libvsomeip3: for SOME/IP
|
||||
- libvsomeip3-sd: for SOME/IP Service Discovery
|
||||
* ``` sudo make install ```
|
||||
|
||||
### 1.2 Setting up the network
|
||||
* Set static IP addresses
|
||||
- <u>IP Address:</u>\
|
||||
192.168.10.100 - <b>Server</b>\
|
||||
192.168.10.101 - <b>Client 1</b> and\
|
||||
192.168.10.102 - <b>Client 2</b>
|
||||
- <u>Netmask:</u>\
|
||||
255.255.255.0
|
||||
- <u>Gateway:</u> \
|
||||
192.168.10.101
|
||||
* Add routing for supporting multicast messages \
|
||||
``` sudo route add -nv 224.224.224.245 dev eth0 ```
|
||||
|
||||
### 1.3 Copy examples to PIs
|
||||
* Copy the [configuration examples](./resources/DEMO_EXAMPLES) to the PIs (e.g. into ./vsomeip/DEMO_EXAMPLES)
|
||||
* take care and change the ``` "unicast" ``` entrys in the JSON files, so they fit to the <b>devices IP address</b>
|
||||
* Build appications (starting in folder ./DEMO_EXAMPLES):\
|
||||
``` cd CLIENT1 ```\
|
||||
``` mkdir build ```\
|
||||
``` cd build ```\
|
||||
|
||||
### 1.4. Preparing Jupyter
|
||||
You need to load the switch configuration into the Jupiter using the automotive switch utility.
|
||||
The utility has the filename ending in ``.scf`` it will mirror all the ports to the CoreMini.
|
||||
Otherwise the vspy configuration won't work.
|
||||
|
||||
## 2. Running setup
|
||||
### 2.1 Starting Server and clients
|
||||
* [Enable SSH](https://www.raspberrypi.org/documentation/remote-access/ssh/) access on the PIs
|
||||
* Use [PuTTY](https://www.putty.org/) or [MobaXterm](https://mobaxterm.mobatek.net) to connect to the PIs
|
||||
|
||||
* Run application using the shell script e.g. ```nohup ./EX1.sh
|
||||
### 2.2 Starting Vehicle Spy
|
||||

|
||||
Binary file not shown.
Binary file not shown.
File diff suppressed because one or more lines are too long
Loading…
Reference in New Issue