1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
|
# AGL_Demo_Control_Panel
A PyQt5 application to simulate CAN Bus signals using Kuksa.val for the AGL Demo platform. This application is to be used in parallel to the relevant AGL Images or any application that subscribes to VSS signals using [Kuksa.val-server](https://github.com/eclipse/kuksa.val/tree/master/kuksa-val-server) or [Kuksa-databroker](https://github.com/eclipse/kuksa.val/tree/master/kuksa_databroker).
## # Installation
- Clone repository:
```bash
# Gerrit (Recommended)
$ git clone "https://gerrit.automotivelinux.org/gerrit/src/agl-demo-control-panel"
# Or GitHub
$ git clone https://github.com/suchinton/AGL_Demo_Control_Panel.git
```
- Install the Python dependencies:
- _Note_:
If errors occure in Debian based/Rasbian OS during installation:
```bash
$ nano requirements.txt
# -> Comment pyqt5 dependency using "#"
$ sudo apt install python3-pyqt5 python3-qtpy pyqt5-dev-tools
```
and skip to step 2
- Step 1
```bash
$ python3 -m venv control-panel
$ source control-panel/bin/activate
```
- Step 2
```bash
$ pip3 install -r requirements.txt
$ pyrcc5 assets/res.qrc -o res_rc.py
```
## # Usage
First, we run the kuksa-val-server on the machine, you can also run the [docker image](https://github.com/eclipse/kuksa.val/tree/master/kuksa-val-server#quick-start) for the same. It is important to note that `kuksa-val-server` uses websockets and `databroker` uses grpc, so adjust settings accordingly.
### 1. Running the Docker Image for Kuksa-val-server/ kuksa databroker:
By default, the server runs on `localhost`, so the settings mentioned below can be used,
### 2. AGL Image
If you are using an AGL image (using QEMU/KVM or VirtualBox) to test the application, you need to set up a bridged network to communicate with the server. You can do so by running the [setup_tap_wireless_int.sh](/Scripts/setup_tap_wireless_int.sh) script. The script creates a bridged network `br0`.
```bash
sudo bash AGL_Demo_Control_Panel/Scripts/setup_tap_wireless_int.sh
```
#### Start the QEMU instance with elevated privileges
```bash
sudo qemu-system-x86_64 ... netdev=net0, -netdev bridge, br=br0, id=net0
## for example ##
$ sudo qemu-system-x86_64 -device virtio-net-pci,netdev=net0,mac=52:54:00:12:35:02 -netdev bridge,br=br0,id=net0 \
-drive file=agl-cluster-demo-platform-flutter-qemux86-64.ext4,if=virtio,format=raw -usb -usbdevice tablet -device virtio-rng-pci \
-snapshot -vga virtio \
-soundhw hda -machine q35 -cpu kvm64 -cpu qemu64,+ssse3,+sse4.1,+sse4.2,+popcnt -enable-kvm \
-m 2048 -serial mon:vc -serial mon:stdio -serial null -kernel bzImage \
-append 'root=/dev/vda rw console=tty0 mem=2048M ip=dhcp oprofile.timer=1 console=ttyS0,115200n8 verbose fstab=no'
```
_Note_: Make sure to update the `file=` argument accordingly.
- Run the server in AGL with the following command,
```bash
$ pkill kuksa
$ kuksa-val-server --address 0.0.0.0
$ pkill databroker
$ databroker --address 0.0.0.0 --tls-cert /etc/kuksa-val/Server.pem --tls-private-key /etc/kuksa-val/Server.key --jwt-public-key /usr/lib/python3.10/site-packages/kuksa_certificates/jwt/jwt.key.pub --vss /usr/share/vss/vss.json
# To make the launch persistant edit /etc/default/kuksa-databroker.agl
$ vi /etc/default/kuksa-databroker.agl
# now add `--address 0.0.0.0` to the series of arguments
```
## Running the `AGL_Demo_Control_Panel`
As `AGl demo control panel` defaults to grpc (databroker), you can edit the default `ip` addres in `extras/config.py` to the address of the server for faster connection. (Optional)
```bash
$ cd AGL_Demo_Control_Panel
$ source control-panel/bin/activate # If using python venv
$ python -u main.py
```
Once the main window is visible, we go to the settings page
1. Start Client _(Loads default config values)_
2. Enter IP address _(if running databroker locally use `localhost` or `127.0.0.1`)_
3. Reconnect
4. Connection Status
- Red: Couldn't find the server at the specified address
- Yellow: Faulty settings
- Green: Connected
## # Testing Against AGL Image on RPi 4
The `AGL_Demo_Control_Panel` can be tested against the [IC application](https://github.com/aakash-s45/ic) by running the `agl-cluster-demo-platform-flutter` image on a Raspberry Pi 4
### Building for RPi 4
For building the `agl-cluster-demo-platform-flutter` image for the Raspberry Pi 4 please follow the steps after setting up your [build environment](https://docs.automotivelinux.org/en/master/#01_Getting_Started/02_Building_AGL_Image/03_Downloading_AGL_Software/).
```bash
source meta-agl/scripts/aglsetup.sh -f \
-m raspberrypi4 -b build-flutter-cluster agl-demo agl-devel
source agl-init-build-env
bitbake agl-cluster-demo-platform-flutter
```
_Note_: you can also add `agl-demo-preload` as a feature to the build to make databroker (or) kuksa-val-server run on `0.0.0.0` by default (optional)
### Flashing Image to SD Card
Simply use the raspberry [Pi Imager Tool](https://www.raspberrypi.com/software/) to flash the custom image. You can also follow AGL's official documentation for the same.
### Connecting to the Pi using Ethernet
Since the IC Flutter demo app does not provide a GUI method to find the IP address of the Pi, and also does not connect to the WiFi by default, We can enable communication using a LAN cable.
To enable the Ethernet port to find the Pi on local network, the following steps can be taken in the Gnome Settings Panel, similar settings should be available in other network configuration tools.
- Settings -> Network -> Wired -> IPv4
- IPv4 Method -> Shared to other computers
```bash
# Find IP addr of the ethernet
ip address show eno1
ping <ip-address-for-eno1>
# Resolve all available IP addresses on network,
# recommend turning off WiFi
arp -a
ssh root@<ip-address-raspberrypi>
```
After successfully `ssh`-ing into the session, we kill the existing `kuksa` service (since it runs on localhost) and restart `kuksa-val-server` on special ip address `0.0.0.0`.
```bash
$ pkill databroker
$ databroker --address 0.0.0.0
# To make databroker persistantly run on `0.0.0.0`
$ vi /etc/default/kuksa-databroker
```
## # Demo Video
https://github.com/suchinton/AGL_Demo_Control_Panel/assets/75079303/b1d08461-f39b-42d4-97d8-ed7307df1fa2
|
