[[flash_prepare_pi_zero_image]]

This is an old revision of the document!


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.

  • Flash image to SD Card (e.g. using Etcher Tool)
  • Set Accesspoint and NetworkHostname depending on left / right camera :
    • Open the /boot partition (which normally gets automounted in windows)
      • open the file wpa_supplicant.conf:
        • Get info for AP names and passwords from the network description.
        • Write info in wpa_supplicant.conf :
          • cam-r : ssid=“AP1”
          • cam-l : ssid=“AP2”
          • WIFI Password : psk=“AP-Password”
      • Open the file unattended:
        • Replace the name of the drone according the name scheme: e.g. DRONENAME-L/Rfreddy-l
  • Insert image into plane and power up
  • 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
    • 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
  • The recorded images can be checked via webserver in the webbrowser: 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
  • flash_prepare_pi_zero_image.1623842250.txt.gz
  • Last modified: 2021/06/16 13:17
  • by wf68spef