SEDSAT-2 Communications
From SEDSWiki
This is the page for the SEDSAT-2 Communications subsystem team. Subsystems design notes are filed in Category:SEDSAT-2 Communications. A categorised overview of our design notes is accessible at SEDSAT-2 Communications Design Notes.
Create new design note: SEDSAT-2 Communications Design Notes 20081007
Contents |
Team
The Communications team is made up of students in Manila (Phillipines), Vellore (India), Edinburgh (UK), Pune (India), Trichy (India) and Kathmandu (Nepal).
Students
- Nikko Torcita
- P. Suman (on leave)
- Steve Maughan (team leader)
- Bryan Carl Chug
- Madhula Sathyamoorthy (on leave)
- Satish Ravindran
- Ansu Man Singh
Contact details for the team are available on the wiki meet-the-team page. Also, you can contact us through protoforge - just log in to protoforge, find our team member profile (see the links in the paragraph above) and click on the "send ... an e-mail" link.
Team status
This is a list of things we're currently working on. To edit the list, click here.
Status as of 3rd August 2008
- Steve: work out MCU hardware choice and application details
- Steve: produce 2D drafts of comms components for Robert (Structures)
- Bryan: Implement header and message checksumming functions in the Packet code
- Add code inside the Packet class constructor to generate a checksum of the Packet fields id, cksum, dest, src, type.
- Add code inside the CmdPacket class constructor to generate a checksum of the CmdPacket fields. Call this.toString() from inside CmdPacket and you'll get all of the CmdPackets fields and also all the subfields of the CmdPacket sub-class (eg. XmitCmdPacket). Then generate the checksum based on the result of the this.toString() call.
- Nikko: Start porting the Packet/CmdPacket/XmitCmdPacket classes over to the MCU.
- Implement a C code function packet_init(...) which initialises a packet structure with the required fields (see Packet.java)
- Implement a C code function cmd_packet_init(...) which initialises a command packet (which consists of the packet datastructure plus command packet fields). Use the packet_init(...) function to initialise the packet datastructure.
- Implement a C code function xmit_cmd_packet_init(...) which initialises an XMIT control packet (which consists of a cmd_packet datastructure)
Availability this week:
- Steve: 2 hours
- Nikko: 2 hours
- Bryan: 2 hours
This information is taken from the comms team meeting minutes, please look at the minutes from previous weeks if you're interested in what we got up to in previous weeks! You can find the minutes on protoforge.
Weekly Reports
The weekly reports give a brief overview of what each of our team members have been working on in the past week. SEDSAT-2 Comms Weekly Reports
Finances
Our team finances are listed on the SEDSAT-2 Communications Finances page.
System Design
Overview
Requirements
System diagram
The above image was created with xcircuit. I would have liked to use Dia as it is more cross-platform and appears to have wider support in SEDSAT-2, but after spending about 30 minutes fiddling with it trying to draw the above, I gave up and just used xcircuit. Maybe someone with more Dia knowledge than me could start me off by beginning to re-draw the above in Dia? I just can't figure out how to get Dia to give me what I want...
Interface Tables
Template:SEDSAT-2 Interface Communications
Documentation
- SEDSAT-2 Communications Design Review 2, 2008/04/06
- SEDSAT-2 Communications Subsystem: Design Specification (coming soon)
SVN
We use Subversion to keep hold of all our project material - reference documents, design documents, program code, schematics, simulations, mathematical models etc...
You can browse through the repository online using the very basic web-interface - just click on the repository URL: http://svn2.assembla.com/svn/SEDSAT-2
See the general SEDSAT-2 SVN page for an introduction to and setup instructions for SVN. In the SEDSAT-2 SVN database, there is a directory called "comms". This is where all the Communications team stuff goes! Within the "comms" directory, there are two important directories: "docs" and "design".
- In the "docs" directory, we keep documents written by other people eg. design reports from other cubesat projects, datasheets, reference manuals etc. Try to rename documents before putting them in here, to give them a meaningful name - the title of the document, the author and the date of publishing are good things to include in the file name.
- In the "design" directory, we keep everything generated by us. This could be MCU program code or it could be a design document detailing transceiver choices.
References
We keep all our links to our reference material on our SEDSAT-2 Communications References page.
