91����

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.

• Download 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 : ��������=“A��1”
        • cam-l : ��������=“A��2”
        • WIFI Password : �����=“A��-�ʲ������ɴǰ���”
    • 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
• 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
  • 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