Announcement of EOSS-147/148

Flight Coordinator: Jim Langsted, kc0rps@eoss.org

LAUNCH DATE: November 7th, 2009 (wx delay +1 day)
LAUNCH TIME: 

• EOSS-147: 06:50 MST (13:50 UTC)
• EOSS-148: 07:10 MST (14:10 UTC)

LAUNCH SITE: Windsor, Colorado (directions)

Payload Experiment Designer

• Colorado University

Experimenters are welcome to submit websites for linking or overviews which I will post on a page on the EOSS website.

EOSS Flight Day Frequencies:

Tracking and Recovery Frequencies

• Preflight Net:
  • 147.225 MHz 8 pm local time the evening preceding the flight
    • 145.160 MHz simulcast in the Springs
  • 146.640 MHz will serve as a backup frequency
• Tracking and Recovery Operations
  • 449.450 MHz RMRL (103.5 Hz Tone)
  • 146.550 MHz simplex (same simplex for field and launch ops)
  • 146.580 MHz simplex (field ops for eoss-148 if needed)
  • Repeater Coverage Pages - Listings of all repeaters available in the expected flight areas.
  • There may be FRS operations see THIS PAGE for a list of channel numbers and their associated UHF Frequencies.
  • 7.228 MHz HF

 

EOSS-147 Balloon Payload Frequencies

• Beacons
  • 147.555 MHz
    • CW ID: AE0SS

• APRS
  • 144.340 MHz
    • ID: AEØSS-11
    • DIGI: EOSS
    • Node: BALNOD
    • APRS Time Slotted Every 30 seconds at 0:00 and 0:30
      • power up at 58 seconds past the GPS minute to properly slot telemetry
    • Telemetry once a minute
    • Sample Data

EOSS-148 Balloon Payload Frequencies

• Beacons
  • 145.600 MHz
    • CW ID: W5VSI

• APRS
  • 144.340 MHz
    • ID: KC0YA-11
    • DIGI: EOSS
    • Node: BALND2
    • APRS Time Slotted Every 30 seconds at 0:15 and 0:45
      • power up at 13 seconds past the GPS minute to properly slot telemetry
    • Telemetry once a minute
    • Sample Data

Flight Systems:

EOSS-147  

EOSS-148  

Payload Configuration: 

• EOSS-147_Payload_Plan_Rev_E.pdf
• EOSS-148_Payload_Plan_Rev_E.pdf

Internet Gateway Stations:

Future I-Gaters:

EOSS is always in need of I-Gate stations. Check out the EOSS I-Gate page for information on how to participate and why we need you.

Current I-Gate Station:

If you are present at your iGate during the flight try and monitor the tracking and recovery frequency. The ground station likes to check the frequency prior to launch to find out if any stations are out there ready to igate the traffic onto the net for the FAA to monitor.

The prediction program used to determine the track of the balloon prior to flight can now output a prediction for the Rise, Closest Approach, and Set of the balloon for each of your stations. I have posted a prediction page for stations that I have been able to discover geographic coordinates. See the I-Gate prediction page for an example. The page will not be updated daily, however, it will be updated the evening prior to flight for I-gate planning purposes.

I have often been asked by iGaters when they should expect to either start receiving signals (AOS) or expect to see those signals disappear (LOS). This prediction page should answer all those questions for you.

Your Log Files

Our technical committee members would also request you open a log file and record all the packets you hear and forward onto APRS-IS. Whenever there is a technical failure of a package it is always helpful to have the most complete dataset possible to attempt to determine the cause of failure and possible fixes. After a flight send your data files to me (webmaster) and I will distribute them to the appropriate payload builders. They appreciate these logs even if all goes fine during a flight.

Tracking and Recovery 

Quick Links are a new method being used to connect payloads together on the flight string. SEE THIS PAGE on instructions on how to properly open them upon recovery enabling easy transport of shorter lengths of the payload train.

Breakfast

• Johnson’s Corner (I-25 exit 254 east side)

• 04:30 and 05:15

• Need to depart to the field no later than 05:30.

EOSS Grid

Tactical Call Signs.