Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
flash_prepare_pi_zero_image [2020/02/19 12:55] wf68spef |
flash_prepare_pi_zero_image [2021/06/16 13:54] wf68spef |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| Each camera in the plane is driven by a pi zero. There is a prepared image for this usecase, but some planespecific parameters need to be set for each image. | Each camera in the plane is driven by a pi zero. There is a prepared image for this usecase, but some planespecific parameters need to be set for each image. | ||
| - | * Download image from Gitlab: https://gitlab.com/searchwing/development/searchwing-pi-gen | + | * Download image: https://cloud.hs-augsburg.de/s/6cia2g5xpoCjjZX |
| * Flash image to SD Card (e.g. using Etcher Tool) | * Flash image to SD Card (e.g. using Etcher Tool) | ||
| - | * Set HostName to a unique name in ''/etc/hostname'' and in ''/etc/hosts'' : e.g. Freddy-cam-l | + | * Set Accesspoint and NetworkHostname depending on left / right camera : |
| - | * Set Accesspoint depending on left / right camera in ''/etc/wpa_supplicant/wpa_supplicant.conf'' : | + | * Open the ''/boot'' partition (which normally gets automounted in windows) |
| - | + | * open the file ''wpa_supplicant.conf'': | |
| - | cam-r : AP1 | + | * Get info for AP names and passwords from [[image-download-station|the network description.]] |
| - | cam-l : AP2 | + | * Write info in ''wpa_supplicant.conf'' : |
| - | + | * cam-r : ''ssid="AP1"'' | |
| - | <code> | + | * cam-l : ''ssid="AP2"'' |
| - | network={ | + | * WIFI Password : ''psk="AP-Password"'' |
| - | ssid="AP1" | + | * Open the file ''unattended'': |
| - | psk="AP-Password" | + | * Replace the hostname of the drone according the name scheme: e.g. ''DRONENAME-L/R'' -> ''freddy-l'' |
| - | } | + | |
| - | </code> | + | |
| * Insert image into plane and power up | * Insert image into plane and power up | ||
| * First bootup the filesystem of image (~2Gb) is enlarged to the SD-Card size (64Gb) | * First bootup the filesystem of image (~2Gb) is enlarged to the SD-Card size (64Gb) | ||
| - | * Implemented by creating a ''/data'' partition where the image will be saved | + | * Implemented by creating a ''/data'' partition where the image will be saved |
| - | * Takes ~3-5Minutes | + | * Takes ~3-5Minutes |
| - | * Afterwards filesystem resize the camera-capture & webserver service is started | + | * Afterwards filesystem resize the camera-capture & webserver service is started |
| - | * You can access each camera via its hostname: ssh searchwing@Freddy-cam-l.local | + | * You can access each camera via its hostname: ''ssh searchwing@freddy-l.local'' |
| - | * The recorded images can be checked via webserver in the webbrowser: e.g. http:\\Freddy-cam-l.local | + | * Check proper system function |
| - | * Preflightcheck can be done with the searchwing-pi-manager on the laptop | + | * Check output of image payload: ''journalctl -f -u searchwing-payloads-camera.service'' |
| + | * Check output of dht22 payload: ''journalctl -f -u searchwing-payloads-temp-humid.service'' | ||
| + | * The recorded images can be checked via webserver in the webbrowser using a laptop in the same WLAN : e.g. ''http:\\freddy-l.local'' | ||
| + | * Most recent image is saved in ''0_latest.jpg@'' | ||
| + | * Preflight check images are saved and overwritten as ''preflight.jpg'' | ||
| + | * Preflightcheck | ||
| + | * can be done with the searchwing-pi-manager on the laptop | ||
| + | * is sent via Mavlink to QGC for the UART TX RX connected Pi zero | ||
| + | |||