400 likes | 693 Views
Communication Subsystem. Introduction. Hardware Protocol Description Interface Examples Test Link Budget Conclusion. Table of Contents. Hardware Protocol Description Interface Examples Test Link Budget Conclusion. Hardware. OSSS Vital Part Testing MIL-STD-1540
E N D
Introduction • Hardware • Protocol Description • Interface • Examples • Test • Link Budget • Conclusion
Table of Contents • Hardware • Protocol Description • Interface • Examples • Test • Link Budget • Conclusion
Hardware • OSSS • Vital Part • Testing • MIL-STD-1540 • Power Interface?
Specifications • Frequency: 430-450 MHz • Bitrate: 9600 baud • Voltage: 3.3-5 V and 7.5-12 V • Power output: 2W@9.6V • Current Drain: • Transmitting: 940mA@2W • Receiving: 60mA • Mass: 100 g
Ground Station • Modem from OSSS • No Final Solution • Yagi Antenna 16 dB gain • NOVA Rotor Control • Price 10.000 - 20.000 Kr. • Brian Lodahl from KOM
Table of Contents • Hardware • Protocol Description • Interface • Examples • Test • Link Budget • Conclusion
Requirements • Flawless Link • Support Call-names • Pause / Resume • Prioritizing • Channels • Half Duplex
AX.25 • Error Detection • Supports Call-names • Supports Half Duplex • Connections • Widely Used • Well Documented
T55X Transport Layer • Channels • 16 Channels • Priorities • Fixed Priorities • Pause / Resume
Data-A Packet-A1 Packet-A1 Packet-A1 Data-B Packet-A2 Packet-B1 Packet-B1 Packet-B1 Data-B Packet-A2 Packet-A2 Data-A Example Channel 1 Channel 2 Channel 1 Channel 2 Scheduler Application Application De-Mul
Table of Contents • Hardware • Protocol Description • Interface • Examples • Test • Link Budget • Conclusion
Interface • Callback Functions • Receive Data • Receive Events / Beacon • Send Connection Less Data • Send Data • Connect / Disconnect • Complete API on WWW • www.control.auc.dk/~01gr555/api/
Table of Contents • Hardware • Protocol Description • Interface • Examples • Test • Link Budget • Conclusion
Start Communication Satellite: while(true) do sendConLess(housekeeping) sleep(rtt+ct) if status=CONNECTED then break sleep(30 s) Ground Station: SetupCall-back(handleEvent(type, data)) handleEvent(type,data) { If type=DATA_RECEIVED then store(data) connect }
sendConLess Lost in space getStatus 30 sec sendConLess handleEvent connect getStatus Sequence Chart Ground Satellite Satellite Ground protocol protocol applications applications
Send/Receive Ground Station: Start: createChannel(8,receiveImage) createChannel(2,commandChannel) Main: ....... sendData(2,Take Picture) ........ Callback: receiveImage(data){ Save(data) sendEventToAdmin(Received Image) }
Send/Receive Satellite: Start: createChannel(8,imageChannel) createChannel(2,receiveCommand) Callback: receiveCommand(data){ if data=’take image’ then takeImage sendData(8,image) }
Time Synchronization • Several Solutions • Connection Less • Channel With Estimation • No Requirements Yet
Table of Contents • Hardware • Protocol Description • Interface • Examples • Test • Link Budget • Conclusion
Modelling and Verification • Why? • Short Implementation Test Time • New Protocol • Satellite • What: • SDL Modelling • Exhaustive Testing • Code Generation • Tools: • ObjectGeode
Table of Contents • Hardware • Protocol Description • Interface • Examples • Test • Link Budget • Conclusion
Link Budget • Link Budget equation or Ebno • EIRP: • (Equivalent Isotropically Radiated Power) • G/T: • Quality factor of receiver
Link Budget • Max distance to satellite • Using Pythagoras: • Inserting into the equation
Effective Throughput • I frame size: 24 - 276 bytes • 23 bytes overhead • S frame size: 19 bytes
Effective Throughput • Data: • Beacon:
Table of Contents • Hardware • Protocol Description • Interface • Examples • Test • Link Budget • Conclusion
Conclusion • Work So Far: • Analysis / Design / Modelling / API • Hardware • To Do: • Implementation • Verification / Test • Purchase from OSSS • Ground Station