Trailblazer

1. Trailblazer ECE 419 Nathan Henry Jarred Kozlick Sponsor Brian Zufelt COSMIAC

2. Presentation Outline Project Description Project Goals CubeSat 101 Roles and Responsibilities Challenges and Concerns Why Is This a Good Senior Project? Upcoming Tasks

3. Project Description • Develop a standardized way for components on a CubeSat to communicate • Can result in a satellite being built exponentially quicker than current technology. • Cost of satellite is pocket change compared to others. • Code will be published online as part of a GUI that automatically develops ASIM software for individual components. • Project will possibly be translated to multiple microcontrollers

4. Project Goals • Software must efficiently use memory • Satellite must be operational for an extended length of time • ASIMs must have the ability to handle both master and slave I2C communication roles • Software will be published online to communities nationwide • Everything must comply to Mini PnP standards

5. What is a CubeSat? CubeSats are miniaturized satellites, approximately 1 liter (10cm x 10cm x 10cm) Typically used for space research Specifications were developed in 1999 as a joint venture between California Polytechnics Institute and Stanford University

6. Trailblazer CubeSat

7. CubeSats are fully compliant with the Stanford/CalPoly CubeSat and Poly-Picosatellite Orbital Dispenser (PPOD) standards. These standards deal mostly with the size and shape of the CubeSat and its launcher Why not extend this idea to the components of the CubeSat? Under sponsorship by the Operationally Responsive Space (ORS) office, the Air Force Research Laboratory (AFRL) developed a modular nanosatellite approach where hardware and software “black-box” elements can be combined very quickly (possibly less than an hour) to form simple, but functional spacecraft. CubeFlow

8. Mini PnP/I2C • Open standard that allows for versatile development with a variety of hardware • Utilizes the I2C Standard built by Phillips • 7 bit address with 1 bit fro read/write commad (Limit 112 addresses, 16 reserved) • Voltage level either 3.3V or 5V • Speeds from 10kbits/s to 400kbits/sec • Multi-master bus architecture

9. xTEDS Devices and applications are self describing using electronic data sheets referred to as extensible Transducer Electronic Datasheets (xTEDS) • <?xml version="1.0" encoding="utf-8" ?> • <xTEDS xmlns="http://www.interfacecontrol.com/SPA/xTEDS" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.interfacecontrol.com/SPA/xTEDS ../Schema/xTEDS02.xsd" name="Temp_AT90" version="1.0"> > • <Device name="Temp_AT90" kind="tempSensor" /> <Interface name="Temp_data" id="1" > <Variable name="TempF" kind="temperature" format="FLOAT32"/> • <Notification> <DataMsg name="Temp_F" id="1" msgArrival="PERIODIC" msgRate="1.00"> <VariableRef name="TempF" /> </DataMsg> </Notification> </Interface> </xTEDS

10. Self-organizing Networks

11. Mini PnP Operation Address Resolution ASIM 1 Address 0x11 ASIM 2 Address 0x12 ASIM 3 Address ? C&DH ASIM 3 is an unknown device to the network. Once a new ASIM is connected to the network, the address resolution process begins.

12. Mini PnP Operation Address Resolution ASIM 1 Address 0x11 ASIM 2 Address 0x12 ASIM 3 Address 0x11 GUID 0x11 C&DH ASIM 3 starts to find its address by starting at polling address 0x11 to see if there is already and ASIM at this address Since ASIM 1 already has this address it response with it's Global Unique Identifier Number

13. Mini PnP Operation Address Resolution ASIM 1 Address 0x11 ASIM 2 Address 0x12 ASIM 3 Address 0x12 GUID 0x12 C&DH ASIM 3 increments its address and preforms another poll this time at address 0x12 Once again an ASIM already has that address and response with its Global Unique Identifier Number

14. Mini PnP Operation Address Resolution ASIM 1 Address 0x11 ASIM 2 Address 0x12 ASIM 3 Address 0x13 0x13 C&DH NACK ASIM 3 increments its address one more time to 0x13 and preforms another poll. Since there is no ASIM with that address no acknowledgment will be sent to ASIM 3 and thus ASIM 3 has found its address on the Network. Now the Enumeration process can begin

15. Why is this a good Senior Design Project? • Has the potential to transform the world of satellites as we know it • Organizations with less funding will be able to perform research in space • Lots to learn about communication between devices with microcontrollers • The opportunity to work on something being shot into space! • First satellite UNM will launch

16. The Team • Team Leader/Mentor/Technical Advisor: Brian Zufelt • Presently: • Both members are familiarizing themselves with the PIC microcontroller • UART operation for debugging • ADC operations • I2C bus protocol • After developing a flowchart for the ASIM, further tasks will assigned to individual team members.

17. Major Schedule Milestones • ASIM Flowchart – December 5th • I2C driver – February 2nd • Develop ASIM program – March 15th • Port code to ASIC – April 15th • Final Testing – May 1st

18. Deliverables • Program documentation • ASIM Flowchart • ASIM software to be published online • Code ported to ASIC

19. Challenges & Concerns • Very low power consumption • Memory Overload • Space is very limited • Hardware must be able to withstand solar radiation • Other challenges will be encountered in the future

20. Not So Distant Future Plans • Finalizing familiarization with PIC16F690 microprocessor • ADC • EUSART • I2C • ASIM flow chart • All ASIM coding will happen next semester