The Presentation should start with an About Me. Then it should go over my work at Proteus Space for the First year, then dive into M1. Including the general timeline, my responsibilities. Then dive into the FSW aspect, why we choose F Prime, what F Prime is, and big architectural design and why the architecture was chosen this way. Then it should dive into 485. What is it, what it means for it to be a full duplex bus drop blah blah. Then dive into what a 485 transceiver does. How most components required an external transceiver. And keep going from there
The Presentation should start with an About Me. Then it should go over my work at Proteus Space for the First year, then dive into M1. Including the general timeline, my responsibilities. Then dive into the FSW aspect, why we choose F Prime, what F Prime is, and big architectural design and why the architecture was chosen this way. Then it should dive into 485. What is it, what it means for it to be a full duplex bus drop blah blah. Then dive into what a 485 transceiver does. How most components required an external transceiver. And keep going from there
Created using ChatSlide
Explore the evolution of satellite software development through my journey from NASA's Jet Propulsion Lab to Proteus Space. This keynote will delve into groundbreaking projects like Mercury 1 and its ESPA-class architecture, the adoption of the F Prime framework, and the innovations driving accelerated satellite production timelines. We'll discuss key design techniques, challenges in communication protocols, and the transformative MERCURY™ automated design system. With a focus on...