> For the complete documentation index, see [llms.txt](https://docs.sky-pulse.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sky-pulse.org/documentation/software-and-getting-started/helios-getting-started.md).
# Helios - Getting started
Getting started with the companion computer which is a part of the Helios stack
In order to connect to the Helios, connect the attached ethernet adapter to the Interface connector, and power up the unit with an adequate power source (Recommended: 12V 3A, but anything from 7 to 36v and over 3A is fine)
The companion computer inside the Helios runs Linux Bookworm desktop by default (Debian 12), with the following configuration:
#### Default login credentials and IP:
```bash
Username: skypulse
Hostname: Skypulse
Password: pass
IP: 192.168.168.33 (static IPv4)
```
### Connection options
#### Connecting through SSH via ethernet:
In order to connect via SSH through ethernet, you have to be on the same subnet as the Helios:
* Define your computer’s static IP for ethernet with 192.168.168.X network, for example:
Network configuration on your PC
* Connect with `ssh skypulse@192.168.168.33` through your terminal of choice (CMD / Terminal / Putty etc...)
* If needed, add the hostkey to known list of keys (done automatically in most platforms)
* Enter ‘pass’ as password
* You’re in!
#### Connecting through VNC:
VNC enables a graphical interface (just like a desktop), and it's enabled in the PI by default, so you could connect directly through apps like Remmina or RealVNC- just enter ‘Skypulse.local’ in the address line, then username and password - and you’re in.
***
### Communication between the computer and the flight controller
The companion computer and the flight controller are connected through **`Serial 3 (UART4)`** port of the flight controller. The serial port used in the computer is the **`ttyAMA0`** port.
In Ardupilot, the following parameters should be defined to ensure proper communication between the controller and the computer:
**SERIAL3\_PROTOCOL = Mavlink2****SERIAL3\_BAUD = 921600 (recommended)**
{% hint style="info" %}
SERIAL3\_BAUD can be defined as any baud rate you'd like, we recommend using 921600, which is helpful if you're planning on passing large amounts of data between the flight controller and the computer (such as IMU data for navigation), just make sure to define it in your python script / mavproxy settings.
{% endhint %}
To check the communication between the computer and the controller, ssh into the computer and install these Python packages:
* **PySerial**
* **PyMavlink**
* **MAVproxy**
* **Future**
After installing, you can run this command, which opens a communication link between the flight controller and the computer via MAVlink:
```bash
~/.local/bin/mavproxy.py --master=/dev/ttyAMA0 --baudrate=921600
```
{% hint style="info" %}
Make sure that the baud rate defined here is the same as your ardupilot configuration (SERIAL3\_BAUD)
{% endhint %}
You should see the flight controller connected and some data, and specifically:
`MAV> Detected vehicle 1:1 on link 0`
This means that you have successfuly established a communication link between the companion computer and the flight controller.
### Connecting through SSH via WiFi
After the first setup (using ethernet), you can define your own Wifi's credentials.
Using Wifi, you can SSH wirelessly to the Helios (which is useful when it's mounted inside of your platform).
Make sure that your computer is on the same network as the Helios, and connect via **** - Capital letters do matter here!
Want to disable the Wifi interface? use this command:
```bash
sudo rfkill block wifi
```
If you want to restore the Wifi connection:
```bash
sudo rfkill unblock wifi
```
For getting internet connection (in case you need to install packages, etc) you can reset the DHCP client:
```bash
sudo dhclient -r wlan0 && sudo dhclient wlan0
```
