| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| guides:documents [2018/01/10 16:55] – [Payload Document] daveake | guides:documents [2021/05/28 16:28] (current) – randomskk |
|---|
| DO NOT create a flight document weeks before your flight. It's just not possible to be confident that far out that the wind and weather will allow for a safe flight. Generally predictions are very variable until about 3-4 days prior to the flight, so that's a good time to create the flight document. | DO NOT create a flight document weeks before your flight. It's just not possible to be confident that far out that the wind and weather will allow for a safe flight. Generally predictions are very variable until about 3-4 days prior to the flight, so that's a good time to create the flight document. |
| |
| To create a flight document, go to http://habitat.habhub.org/genpayload/ and choose the appropriate button. Again, you can work from an existing flight document if you have one, but otherwise start from scratch. Enter the details of the flight, and add the payload document **the one that you created earlier and have tested so you know it works**. When you save the flight document you will be shown a document ID - copy this and save it somewhere. | To create a flight document, go to http://habitat.habhub.org/genpayload/ and choose the appropriate button. Again, you can work from an existing flight document if you have one, but otherwise start from scratch. Enter the details of the flight, and add the payload document **the one that you created earlier and have tested so you know it works**. If you made multiple payload documents for the tracker (e.g. one for RTTY and one for LoRa) then add all payload documents to the flight document. |
| | When you save the flight document you will be shown a document ID - copy this and save it somewhere. |
| |
| Now you are ready to get the flight document approved - until then it will not get added to the calendar or the flight list in dl-fldigi. Approval is done on the #habhub IRC channel which you can join here - http://webchat.freenode.net/?channels=habhub. Once joined, paste your flight document ID and a bot will display a status message, including whether you tested the payload document or not (and if you didn't, give yourself a slap for not following the instructions above!). Of course you did follow those, so the bot will show "Tested 5 minutes ago" or similar, so you can now ask for the flight document to be approved. If an admin is around then, assuming the flight document is in order (which essentially means that it references a payload document which you have successfully tested) then they will approve it. | Now you are ready to get the flight document approved - until then it will not get added to the calendar or the flight list in dl-fldigi. Approval is done on the #habhub IRC channel which you can join here - https://web.libera.chat/#highaltitude. Once joined, paste your flight document ID and a bot will display a status message, including whether you tested the payload document or not (and if you didn't, give yourself a slap for not following the instructions above!). Of course you did follow those, so the bot will show "Tested 5 minutes ago" or similar, so you can now ask for the flight document to be approved. If an admin is around then, assuming the flight document is in order (which essentially means that it references a payload document which you have successfully tested) then they will approve it. |
| |
| If nobody replies, hang around for a while or come back later. You can join at any time and paste your flight document ID; a bot will display a message showing if it's been approved or not. | If nobody replies, hang around for a while or come back later. You can join at any time and paste your flight document ID; a bot will display a message showing if it's been approved or not. |
