Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision Next revision Both sides next revision | ||
flash_prepare_pi_zero_image [2020/02/16 14:15] wf68spef created |
flash_prepare_pi_zero_image [2021/06/16 13:53] 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. | ||
- | * Unordered List Item 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) |
- | <code> | + | * open the file ''wpa_supplicant.conf'': |
- | network={ | + | * Get info for AP names and passwords from [[image-download-station|the network description.]] |
- | ssid="AP1" | + | * Write info in ''wpa_supplicant.conf'' : |
- | psk="AP-Password" | + | * cam-r : ''ssid="AP1"'' |
- | } | + | * cam-l : ''ssid="AP2"'' |
- | </code> | + | * WIFI Password : ''psk="AP-Password"'' |
+ | * Open the file ''unattended'': | ||
+ | * Replace the hostname of the drone according the name scheme: e.g. ''DRONENAME-L/R'' -> ''freddy-l'' | ||
* Insert image into plane and power up | * Insert image into plane and power up | ||
- | * You can access each camera via its hostname: ssh searchwing@Freddy-cam-l.local | + | * First bootup the filesystem of image (~2Gb) is enlarged to the SD-Card size (64Gb) |
- | * The recorded images can be checked via webbrowser: e.g. http:\\Freddy-cam-l.local | + | * Implemented by creating a ''/data'' partition where the image will be saved |
- | * Preflightcheck can be done with the searchwing-pi-manager: | + | * Takes ~3-5Minutes |
+ | * Afterwards filesystem resize the camera-capture & webserver service is started | ||
+ | * You can access each camera via its hostname: ''ssh searchwing@freddy-l.local'' | ||
+ | * Check proper system function | ||
+ | * Login to drone via SSH | ||
+ | * Check output of image payload: ''journalctl -f -u searchwing-payloads-camera.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 | ||
+ |