Embedded - 195: A Bunch of Sputniks
Episode Date: April 12, 2017We discussed CubeSats with their co-inventor, Professor Jordi Puig-Suari, Professor of Aerospace Engineering at CalPoly SLO and co-founder of Tyvak Nano-Satellite Systems. The 2017 CubeSat conference ...is in San Luis Obispo, CA on April 26-28. More details at CubeSat.org. Information about CubeSats at CalPoly SLO can be found at PolySat.org. Tyvak is hiring for a number of different positions: tyvak.com/careers. For more satellite goodness, we spoke with Patrick Yeon of Planet about their CubeSat-based platform and deployment mechanism in Embedded episode 153: Space Nerf Gun. Thank you to Embedded Patreon supporters for Jordi’s microphone!Â
Transcript
Discussion (0)
Welcome to Embedded.
I am Elysia White.
My co-host is Christopher White.
This week we're going to talk about satellites,
specifically CubeSats.
And we have Jordi Pujsuare,
Professor of Aerospace Engineering at Cal Poly,
and he's one of the organizers of the upcoming CubeSat conference.
Hi, Jordi. Nice to talk to you today.
Hi, guys.
So that was a little bit of introduction, but could you tell us about yourself as though
you were on a panel at an engineering conference?
Okay, just a little bit about myself. I'm Jordi Putsuari. I'm a professor of aerospace
engineering. I'm an academic, started my career dreaming about airplanes and satellites
and things like that and went to school and
ended up teaching aerospace which is
a wonderful thing to do and I was lucky enough
that because of my interest in teaching
and the fact that at Cal Poly
where I was teaching we pride ourselves in learn by
doing we want our
students to do what they're learning. Since we were teaching spacecraft, we needed to figure out
a way of getting them to actually build spacecraft and fly them. And at that time, the student
satellite market was very small and it was very difficult to get those satellites built and flown.
So we got together with Stanford, with Professor Rod Twiggs there, and came up with this idea of doing much smaller spacecraft and kind of standardized spacecraft for students, which was the CubeSat.
And it's one of those, you know, the rest is history type of events where we managed to kind of have a significant impact on the industry quite by surprise to everybody. And that has kind of occupied a large percentage of my
waking hours for the last almost 20 years, both in academia and now more recently in the
commercial side where we started a small company that's not so small anymore called Tyvek, based on the same idea of building small satellites at a lower cost.
Excellent.
And we have questions for all of that.
But before we dig more into CubeSats, I want to do lightning round, where we ask you short questions and hope
for short answers.
Okay.
You may get long pauses, though, but go for it.
I can take those out.
I'll go first?
Yeah.
Favorite airplane or otherwise identified flying object?
Oh, gosh, that's an easy one. My favorite airplane is the Mosquito,
which is a, for airplane buffs, is a well-known World War II British plane. But it was a wooden
airplane that was, at the time it came out, it was one of the fastest airplanes around,
and it could do anything. And it was extremely capable, and I've always liked it. I don't know why.
Kerbal Space Program.
Is this the ultimate evil or something every first grader should have the opportunity to play with?
Which space program?
Oh, Kerbal Space Program. It's a computer game that actually uses orbital mechanics to launch rockets.
Oh, yeah.
I think I know which one you're talking about.
I think space simulations are wonderful.
And anything that gets students to understand travel in space
is not like Star Wars where you point and shoot
and go in a straight line.
It's a great thing.
Favorite man-made space object.
I'm sensing a theme here.
Ooh, favorite space. Favorite man-made space object? I'm sensing a theme here.
Ooh, favorite space.
CP4, which was our first CubeSat to operate in space.
Okay.
Because my team built it, so I'm biased.
That's fair.
Okay, what about the whole solar system and things that are still up there?
Favorite solar system object?
Favorite solar system object? Favorite solar system object?
Wow.
Voyager.
Yeah.
Yeah.
That's pretty good.
It has to be Voyager, because it's going places.
A few thousand more years, and we can't even call it in the solar system anymore.
Exactly. Well, they already sort of said it depends on your definition.
I know.
Yeah.
Favorite movie or book that you encountered for the first time in 2016?
Oh, the new Star Wars movie, Rogue One.
That was good.
As a little kid that remembers sitting on the original Star Wars,
watching the movie and going gaga, that prequel was very special.
Yes, yes.
Okay, this one's a little strange.
And I'm hoping you know about this animal.
Have you ever touched a pangolin?
No.
And I've heard the name, but at this moment I don't recollect what they look like. They're the ones that are super armored on the name, but at this moment, I don't recollect what they look like.
They're the ones that are super armored on the outside, and they curl up into little balls.
They're like anteaters with armor.
Yeah.
Okay.
Wow.
I think that's fine.
Nobody's touched any penguins, and nobody's touched any pangolins.
I keep asking.
No.
I keep asking.
But that's as exotic as I got.
Okay.
So now that the important stuff is out of the way, CubeSats.
I have one thing that is sort of a problem with CubeSats, and they're not cubes.
Is that right?
Well, you are cool um they were cubes when we started um you need to
understand how little we knew about how to standardize things um they are cubes the thing
that was very interesting is we we started with the 10 centimeter cube and then um later after we make that decision we decided we need a way
of deploying them into space and for a variety of crazy reasons um we decided to put them in a in a
deployer with three cubes at inside and and then we realized if we put the cubes next to each other
they're going to bunk into one another. And that's not a good thing.
So we added these little, you know, six millimeter feet on the corners.
And that took us out of spec.
But that's the story behind that.
The main spacecraft dimension is still 10 centimeters.
And as you start going into 3U, which is basically adding up the three CubeSats in a
deployer and making it into a single spacecraft, then those six millimeters keep adding up and you
end up with very weird dimensions. But that was never our intent, but I think it's close enough
for engineering. 10%, it's fine. You are a co-inventor of this standard.
Yeah.
And you started out wanting, as you mentioned in the beginning, wanting to do this for students.
But it has become an important industry standard.
We've talked to the planet folks making flocks of imaging satellites, and they were all over how many U's their satellites were.
Yeah.
How did that transition happen?
That's a very interesting question.
Truly, that's a million-dollar question, because the better we understand that, the better
we can maybe try to do it again and make revolutionary changes, not just in in space but in all kinds of of of areas
of engineering and science and technology um there's a number of things that happen um
the first one that's actually very interesting is that these the requirements for these vehicles
were zero uh they didn't have to do anything because their primary objective was to teach students.
And in some ways, they didn't even have to work when they got to space because most of the
learning the students get is before they fly. It is the design, the integration, the testing in
particular was something that we were really having a struggling time or we were struggling at the time trying to get the students to
to get experience in in in flight testing and doing vibrations and thermal back and all the
things you need to do to to put a spacecraft in orbit um so so all the satellites needed to do is
train students and that allowed us to take a tremendous amount of risk. And it also meant we didn't really need a lot of funding.
So that's the first, you know, important piece of information about the program is that it wasn't on anybody's, you know, technology roadmap.
Nobody really needed it.
It just happened.
The thing that followed that was very surprising to everybody is we had a bunch of really bright students. And it's basically racing. We put them in a highly constrained environment. They didn't have enough resources to do what we wanted them to do or to do anything interesting we expected them to build a bunch of sputniks and that would have been wonderful but they they were not happy with that they wanted to put cameras and
sensors and experiments and all kinds of stuff um and what they did is they said okay we cannot
build these things the way traditional space is building spacecraft because then we cannot do what
we want to do so we'll start doing it our way and see what what's necessary and and interesting things
happen they started to take a lot more risk and eliminate a lot of the redundancies that was one
of the first things that happened you know we'll have one battery and we'll have one radio and
we're going to take the risk that that things may go wrong um and then they started looking for the
highest performance components they could find.
And those were not anywhere near the space parts that we used on BigSpaceGraph.
They were all commercial of the shelf components on cell phones, on laptop computers, all things like that.
And they started launching these things and they worked. And that's something that was at the time impossible for the
main space industry to do because they couldn't take the risk. They were always using well-understood,
highly reliable, flown before parts, which meant they were really falling behind
the computer revolution because they couldn't keep up.
If you needed something to fly for five or six years before you could use it again, or you could use it for real, that meant you started five years behind the curve as far
as the latest technology.
So that was very interesting.
And when they started working fairly well, industry started to pay attention because
the value proposition changed radically. You had lower
cost components that had higher performance, but higher risk. And a few people in the commercial
side realized that, well, you can make it up with numbers. I can launch 10 satellites,
probably in some cases, 50 satellites for the price of one of the traditional spacecraft.
And that allows me to take some risk.
And I can use the latest technology and that allows me to get the performance that a much larger spacecraft would get.
And that really had an impact when people realized we could do that. And to this day, if you think about companies like
Planet or Spire, even Skybox, which became Terra Bella and now is Planet, the way they build a
spacecraft is not traditional. They do things differently. And I think that that's kind of a
little bit of the path that it took. The other thing that was in there that was very important, and maybe we didn't realize at the time as much as we should have,
but the fact that we had a standard meant that launch opportunities were viewed in a very different way than before.
There was a number of launch vehicles that started putting accommodations for CubeSats on those vehicles.
And they did very interesting things.
They would put accommodations on the rocket without knowing who was going to fly there,
which is unheard of on the space business.
But they knew that there's these standard satellites and some will show up and will go fly.
And in the same moment, the satellite developers were like,
well, we're going to start building the spacecraft
and then we'll figure out where we launch. And traditionally, especially like university
satellites, we would always be thinking about what's the launch before we really committed to
building the spacecraft because you needed to have the right dimensions and make sure you fit
and which rocket is going to let me go. And CubeSats kind of stopped that. And that was kind of a confluence of very interesting, strange, non-traditional space things that came together that made it all happen.
But it's a very interesting process that I think has some lessons for the future. And what we're seeing now, and I mean, at Tyvek, we're doing this,
where we take the philosophy that started with small CubeSats,
and it keeps moving to bigger and bigger spacecraft.
And now we're working on 50-kilogram satellites,
but still primarily using commercial-on-the-shelf components.
We've learned ways to make those more reliable now,
both by design and by redundancies
and other things but but it's kind of different from the way it was done before a lot of it
was very well established and very immobile and now we have very dynamic very
vibrant industry where we we were pushing things up.
We start with small satellites.
We test them in one U-cube sets or two U-cube sets when things work.
Then they move up to, you know, three use and 12 use and 50 kilogram microsats.
And the reliability keeps going up because people are learning and using lesson learned.
And we're doing that very quickly because we get to fly very often.
People will, somebody was talking about the fly, learn, fly again. learn and we're doing that very quickly because we get to fly very often uh people will somebody
was talking about the the fly learn fly again uh philosophy which was not feasible with 100 to 100
million lot of spacecraft because the initial cost is too high um but with cubesats you can do a lot
of that did i answer your question because i know i just went in a rant on a rant and no no no
that was that was great you asked you answered that question and about three more so i'm fine
with that chris i was about to ask how important the iss is as a launch not necessarily platform
but a secondary launch platform but it sounds like it's been more the the rocket providers
making accommodations even speculatively that that's really caused things to grow.
Well, that's how we started.
We started with secondaries.
And I think the station is all kind of this realization that people are getting comfortable with the concept.
When we started, we had very few opportunities to launch, you know,
in the US, oh, that's too risky, you know, who's going to put these things on our rocket,
we have a very expensive satellite on top. And as things flew, and I think that that's one of
those things, you know, we were using the Peapod at the time, which Cal Poly developed the first
deployer. And we were using the same thing every time.
So by the time we had launched 10 or 12 of those
and they had all worked and nothing had happened,
people started saying, well, maybe they're not that dangerous.
So we'll put them on our more expensive rockets.
And I think the station was kind of the next step.
Can these things go to the space station?
There's astronauts, there's safety was something
that people were very concerned about but everybody got comfortable with it because it flew so much and we were we were
doing it so often and and successfully that it's like hey yeah we can do that um the other thing
that happened that was very interesting is people started to realize that these things are really
small um they don't carry large batteries they don't carry large batteries. They don't carry large transmitters. They're pretty benign spacecraft and quite safe.
But at the beginning, that was not the case. It was quite interesting.
Did you get a lot of pushback from the old space folks who considered a small satellite to be 500 kilograms?
I mean, it just seems like someone would be saying, no, no, you can't do that.
That's wrong. It was really bad at the beginning.
And I always tell people that one of the great things that helped us initially is that we had no funding.
Because if we did, they would have canceled it.
Because everybody would tell us, it's too small.
You cannot do anything with something that small.
It's just a toy.
It's a waste of time.
And for us, it didn't matter because we were teaching the students and that was we knew we could do that with with those spacecraft but there were some people that
didn't even think you could do that it's like it's too small it's too different um
it's not going anywhere but no we heard a lot of that in the beginning. It was quite depressing. Yes, of course.
Do you interact with the people who were naysayers then,
who are now maybe converted?
Oh, yeah, we have lots of those.
We have a lot of great supporters that I wish I had a recording
because I remember what they said before.
But no, but it was understandable.
I don't hold it against anybody that when we started,
because we had to prove ourselves.
And once we did that, the smart people changed their mind,
which is the right thing to do.
You said that the students get most of the education from the satellite
before it ever gets to space, which makes sense.
The building is the educational part.
Do you ever just not launch them? I mean, do the students graduate and you're like,
oh yeah, it was going to be on the next launch. Goodbye.
Yes, that happens. And it's frustrating because the whole point is we wanted to get them to launch.
And there's actually an interesting nuance to that sentence that it happens before the launch. And there's actually an interesting nuance to that sentence that it happens before the launch.
And it does happen before the launch, but up to the day of the launch,
because, or the day you send it to the integration facility, because all the final testing
and qualification is very important. And that's one of the things that was hard to do when you didn't have a launch opportunity.
So these days, even when satellites, you know,
sit in a shelf for a while,
they're usually completed and fully tested
and ready to fly
because they have a very good understanding
of what their launch will look like
because they'll go in a standardized deployment mechanism
and that's the launch vehicle, and they can do it.
Luckily, the lifecycle of these things is relatively short.
So what we find is with our students, for example,
they'll probably, if they're around for four or five years,
they'll probably be around for, or almost always will be around for a launch.
It may not be the satellite they design,
and that actually is another interesting thing.
We'll have students do operations before they design
because there's this active lab that launches satellites,
you know, every year or two.
And when you join the effort, hey, we're doing operations.
That's what you're going to do.
Go talk to our spacecraft.
But yeah, sometimes satellites don't launch,
but there's still a significant amount of learning
that goes on through the process.
You said you didn't have a lot of budget to start this,
and I understand for making the hardware.
Yeah, you don't need a huge bankroll
for the 10 by10x10 satellite, but launches still are quite expensive.
How do you get funding for that?
Well, launches were not that expensive when we started.
It was interesting.
The first launch we did with Cal Poly, we got a Russian launch for $40,000 a cube.
So that was really, really cheap.
And those prices have gone up.
So you cannot do it at that price anymore.
But in the U.S., we're fortunate because NASA,
after a few years and a few launches of their own,
with their own missions,
they decided that this was really worthwhile.
And they stood up the Atlanta program to launch these satellites at no cost to the universities.
So as long as it's an educational program or it's flying missions of interest to NASA,
they will try to find them a ride.
And a lot of satellites in the U.S. have flown without launch cost.
In Europe, they have similar programs.
With ESA, Japan has the same thing.
India has similar things.
So everybody's starting to see these as a very important workforce development activity
and supporting the launch cost.
Do you know off the top of your head if Australia has that program too? Because
I know there's one person who's just shouting at the show right now and wanting to know.
I don't know. I know that Australia has very good connections with the United States. So we're
trying to help as much as we can make that connection and see if there's a way to get
some of the university satellites launched. I know that they have a launch coming up from a mission that's a joint venture
between Australian Ministry of Defense and a couple of universities.
It's called Buccaneer.
And I don't know exactly how the costing was handled,
but it's launching on a U.S. vehicle.
I think it's fascinating that they're supporting schools that way.
It makes a lot of sense because it is not only a learning opportunity for the builders, but as you say, for the operation people.
And you don't have to be at Cal Poly in your operations department to listen to these satellites.
Anybody can listen to them.
Absolutely. Most universities will have ham radio beacons on their spacecraft,
and that allows anybody with a ham radio setup to listen to the beacons. And actually,
during the early parts of missions, we find it very useful to have the ham community
supporting the launch and listening for the satellites because we i mean we may have a few and it's hard to find them all it's on my list of things to try at some
point yeah it's a lot of fun i've watched some other people do some contacts and it's you need
four arms yes to you know track the satellite and and manage your your uh there's some drift
things that happen but it sounds like fun no and there's some drift things that happen, but it sounds like fun.
No, and there's some automation
that the software you can get out there
is getting better.
So that's a lot of fun.
How long did it take for you to think,
well, let's standardize these satellites,
make them small,
and use them as learning ideas,
learning tools.
How long from this idea conception to the first launch of one of them?
That's an interesting question.
And actually, that's an important point because it wasn't overnight.
The first concept was 1999.
Yeah, 1999 is when we started talking about it
because both Bob and I had experience with bigger spacecraft
and how hard it is to fly them.
And we were looking for a different way.
Our first launch was in 2003.
So that's four years, which is not terribly long.
That's fast.
That's fast.
For space, it's very fast, but for CubeSats
is actually pretty slow. The second launch was in 2006. So that gives you an idea that initially
wasn't this, you know, every six months you have a launch. That's seven years. I think it took about,
I claim, or I would like to say that it's about 10 years until things got really serious and people started realizing this is going somewhere.
Which when you think about, you know, standardization and coming up with a standard and putting it out, that's quite a while.
And a lot of people are saying, oh, we'll just come up with a new standard and then it'll be great.
And it's like, yeah, it'll be great, but it may take a while.
It's not going to be like a two-year process.
Are there challenges you see every year with the students and their satellites?
Are there constant problems that everybody runs into trying to make a CubeSat?
Yes. Yes.
And we get better and there's tribal knowledge that evolves. And actually, that's one of the big differences between industry and the university students. And I'm lucky because my gosh that's what companies get when we send you guys out because in the university one of the things that we have to be very conscious of is all the students
is their first time and and for us as faculty it sometimes we want to go do the next thing
because we did this already let's move to the next step. And we have to make those steps very slowly
because the students are, it's the first time.
So that we'll make the same mistakes again
because we're doing it the first time.
That's what we're seeing with some of the companies.
They're doing it for the 15th time or the 100th time.
And you really have it dialed.
But the university is different.
But that's the whole point.
You're training people.
And we do move forward and we do better things, but it's a different pace.
In general, what things do people keep getting wrong, both in industry and school?
Because I suspect they're different.
Yeah, they're different, but they're similar in some ways.
And actually, I would say that a lot of the things that people do keep having issues with
in industry are very similar because it's primarily people that do this for the first
time.
And in some cases, even very experienced people may be doing a satellite for the first time.
Like CubeSats have brought on a lot of payload developers
that have decided, oh, we'll do the entire spacecraft now.
And that first time is more of a struggle than people realize
because the integration process
and the qualification process and all the testing and interfacing with the launch vehicle
that's still rocket science um if you've never done it before it's interesting um
we we that the students have some issues and this is this is and they're just learning, so I'm not trying to put them down, but there is a lack of understanding of the end when you start.
So sometimes you're designing a spacecraft, and you're not thinking about, oh, I have to put it together, and maybe I'll have to disassemble it because something will go wrong. We'll have a lot of people that will schedule testing the day before you deliver because you test and then you deliver.
And he's like, no, no, no, no.
You test to make sure that nothing goes wrong, which means most of the time something may go wrong.
So let's put a month in there between testing and delivery.
So there's a lot of things like that, you know, putting connectors in places where you cannot get to because you've
never put a spacecraft together and that thought of, oh, my hands need to fit in places may
not come along.
So there's some very interesting things that we keep seeing over and over.
However, if you pay attention, sometimes you can stop them before they become dramatic the second time around.
Because then, you know, some of the senior students, myself, we've seen it before.
So we kind of prepare for it.
And I think that's what ends up being the great thing with industry and with CubeSat industries,
that you gain experience very quickly because you build satellites frequently and you
get good at it and you don't get rusty because you don't stop and now do design for two years
and go build the next spacecraft. You have a team that's always building, always testing,
and those guys get really, really good at it.
So I'm hoping that answered the question.
So I'm interested to, because I don't really know, can you describe the basic architecture
of one of these, maybe a student device?
What goes into it electronically and software-wise?
This is actually another thing that's very interesting
because there's a tremendous diversity of designs and just philosophies.
You can go buy yourself a spacecraft and you get it
and then you put your payload, you integrate it, and you go fly it.
At Cal Poly, we started before there were commercial components.
We developed a really good electrical engineering team
that does a lot of our boards.
But in any case, whatever you design it or you buy it or whatever,
the architecture is very similar.
And it's basically a laptop.
You'll have a microprocessor, ARM class in many cases,
a few FPGAs that runs the show.
Even more sophisticated satellites that need more computational capability
may have a second computer on board,
either for additional control or for the payload or for other components.
You'll have some sort of power system that regulates solar power and charges and protects batteries.
And then you have some sort of communications device.
Lots of UHF ham radio systems.
A few S-band systems are coming along, and now the more advanced CubeSats are moving into X-band and KA and all the bands that are traditional in the space business.
That's the core.
And then you may have a pointing attitude determination control system with reaction wheels and star trackers or magnetometers or sun sensors, depending on what your requirements are.
And at the end, you put a payload on the spacecraft to do something.
And in some cases, the student satellites may not have a payload per se.
The communications package is really all they fly, or they're testing some components
in their spacecraft.
We'll have universities that say, we're just testing our bus.
We're making sure that the basic architecture of the spacecraft works.
And then next time we'll put a payload on it.
And then the payloads are all over the place.
You have NASA payloads doing biology experiments.
We have science instruments measuring the upper atmosphere,
taking pictures of the earth,
going to the moon and looking for water.
So the payload is a big open question.
You can almost do anything.
I just have this idea of spores in space.
But I wanted to go back to you have an ARM processor.
But this is a big one.
This is running Linux it's it's really
more like a laptop than what I think of as an embedded system like a microwave or yeah Fitbit
okay yes and when we actually like at Cal Poly and Tyvek both we learn it's a Linux machine
you can log into the spacecraft and treat it like a computer. This seems like a very interdisciplinary project.
You mentioned software and hardware and placing connectors where you can get to them, which
is definitely mechanical.
Yeah.
Do you end up with students from different majors, or is this an aerospace major that
is learning lots of different things?
We have an extremely multidisciplinary team, both of faculty and students.
We could not do this without software people and electronics students, as well as mechanical and aerospace.
But it's truly a reflection of what the real world looks like.
If you go to Lockheed Martin up there in Sunnyvale, they're not a bunch of arrows.
They have everybody.
We will have science students join us from physics to help with payload.
So it is extremely multidisciplinary and based on commercial electronics components.
And that is that the training is not just aerospace training.
We have a lot of the electronic students or the software students or the mechanical students that will go work for what you would consider, you know, Silicon Valley traditional high-tech companies,
you know, the Googles and the Apples and the Facebooks of the world,
because a lot of what they learn translates directly on those devices. And it was a surprise to me initially how positively their experience on our satellites was viewed by companies like Apple. for a microcontroller and use batteries and all the things that to some extent
is the same thing as a phone.
You just think about it and there's radios in there
and you understand electromagnetic interference between electronics
and the radio and GPS and all that kind of stuff.
So we have found that these are extremely good systems engineering training packages
for whatever you want to do when you
get out. And systems engineering is a great way to understand, even if you want to specialize
in software, getting that perspective is amazing. Absolutely. When college students ask me how can
they prepare for a career in doing embedded systems, I've always suggested joining the
robotics team because it is so hands-on and
so interdisciplinary. And you're talking me around to like, join the robotics team or your CubeSat
team. Yeah. And the reality that is very interesting is that in many cases, and we've had
tons of cases like this, the training for some of those students is very centered around their discipline
so we'll have a lot of double e's that are very good at circuit design but the idea that the
circuit design needs to be made into a board that fits in a specific location and has bolts and
connectors and screws and all that that's that's kind of the next step and same thing with software
you know you're building software but now i need to put instead of putting your software a nice well understood stable you know pc or mac
you have to put in a computer that's also part of the project we we had a we've had a couple of
times when we were developing a computer board and we were having problems and the computer guys
were finding them but their initial reaction is the software is wrong. Because that's the way it is in class.
If you do something wrong, it's the software.
It's never the computer.
And it was like, wait a minute, it could be the computer.
And they're like, oh my gosh, you're right.
It could be the computer because it's new.
And it was.
It was the computer.
So that's a great experience for them.
Given that it is their first time working in this sort of environment,
and that they don't have preconceived notions about what satellites should be
or what they should do or how it should all go,
have you ever been surprised by something that a student did
because they didn't know it was impossible?
Yes, and actually that's when we talked about didn't know it was impossible? Yes.
And actually, that's when we talked about the fact that CubeSats were successful
because people use components and methods that are not used in space.
That was the great advantage they had.
They didn't know that you're not supposed to do it that way.
And we actually had some students that said,
we're going to put a
camera on a CubeSat. And we're like, no, it's not going to work. It's a cell phone camera. It will
never work in space. And the next thing we know, they're sending us pictures. You know, look,
we did it. So not knowing what you're doing, it's a big advantage when you're dealing with
highly innovative environments. And we have to be very careful because we were all in this innovative
mode, you know, 15 years ago. And now we think we know how to do it, which probably means
some kid will come up and try to do something that we think is really crazy and it will work.
So that is a good thing. And I think we should provide them
guidance. And there's some things that don't change, you know, vibrations are like this,
and they're going to shake your boards really hard. So you need to make sure they don't fall
apart. But there's a lot of opportunities for doing things differently that do work,
if you do it right.
And one thing that's nice with CubeSats is we're trying everything.
I mean, we're flying so many of them that we're trying lots of things.
And some don't work, and some work.
And every once in a while, there's a brilliant one.
There's like, oh my gosh, that works and works really, really well.
And that moves on to bigger satellites.
Switching subjects a bit, you are one of the organizers for the CubeSat conference in April.
Let's see, April
26th to the 28th in San
Luis Obispo. Correct.
Who should go to that?
Everybody should go to that.
It's actually interesting because
there is lots of conferences and lots
of workshops and we work very
closely with the SmallSat conference in Utah in August,
in the summer, which is a huge event.
But one of the things that we've tried to do since we started this workshop,
and the reason we started it, is to be extremely CubeSat focused.
So it's the very small satellite conference, And we want to keep it that way.
And one of the things that that does is it brings together people that have very, very similar problems.
And that's important because you get to talk with everybody that's working on these really small satellites.
We also try to cater to new developers.
There's a lot of people
starting on CubeSats. And when we started, it was easy. Everybody was in the same boat. You know,
we were all kind of trying to do these very simple missions and get them to work. Now it's more
dangerous in a way because you start and you see what JPL is doing or what Tyvek is doing or what
other companies are doing.
And they have these phenomenal CubeSats that can do all kinds of stuff.
And the temptation is to just go there on your first mission.
And that's not going to work.
So we do spend a lot of time kind of talking with new people. A lot of new developers will come up and talk with teams that have more experience.
But a big theme is to try to help out
and give people advice on how to get started and remember.
And we try to allocate a few presentations every year
for new teams, even if they're doing very simple things.
We'll have high schoolers come and talk
because we want everybody to remember that there's
a bunch of people out there that are doing it for the first time.
Just be nice to them and help them out and give them credit for what they're doing, even
though it's not the most advanced Gipsad ever.
When you were in high school, could you have imagined that kids now, that high school students now could send things to space
when i was doing my phd i couldn't imagine phds would do a satellite no it's no absolutely not
i mean the idea of of student satellites at universities when i was at university it was
it was like yeah mit may do it you it. You know, Stanford's doing it.
It's a few schools.
It's extremely difficult.
And now high schools are doing it.
And they're doing it successfully.
I mean, it's not just like, yeah, they're trying, but they're not going to go anywhere.
I mean, we're working with a couple of schools.
We're working with Irvine School District and a school in Florida.
And they're being very successful.
Part of it is that there is a whole infrastructure now that you can go and get help and get parts and get support that was not there before.
And I think it's like everything in technology.
You have a computer in your desk that's more powerful than the Apollo systems and everybody uses one.
So technology kind of trickles down.
And, you know, at some point, high school started doing robotics, which was like, oh, my God, robotics was this really advanced thing.
And now that's an easy segue into, yeah, it's the same idea.
You just put it in space.
And I think it's marvelous that they're doing it.
I still pinch myself sometimes because it's crazy.
But, yeah, it's happening.
It's crazy and amazing.
And what will they be amazed by when they're our age
and some high school student is doing something they couldn't have imagined?
Preschool students will be sending satellites up.
Yeah, it's really impressive what happens.
And the thing that's very interesting that I'm very proud of is that it's a huge motivator.
Everybody talks about how fourth graders are into dinosaurs and space.
And I cannot bring dinosaurs back. Um, but I can maybe make
them feel like they can get to space. Uh, so that, that's, that's been great to see. Um, because we,
we have, whenever we've worked with high school students, the percentage of those students that
pursue careers in science and engineering, whether it's space or biotech or cell phones or whatever,
it's extremely high.
And I think a large part of it is,
one, they realize that this is really exciting stuff
and it's actually kind of cool to do science and engineering.
But the other thing that I think happens
is that if they can do a satellite,
they feel like they can do anything.
And at that point, the sky is no longer the limit,
and they just feel extremely empowered.
Okay, changing subjects again.
Tyvac, it's a company you co-founded
to bring some of these lessons learned about CubeSats into industry.
Is that right, or was it founded for a different reason?
Well, it's a number of things,
but there was a few things that were happening.
Cal Poly was doing a lot of launch activity
as kind of a sole source
because we were the only game in town.
And at some point,
it became more of a commercial activity
with a number of companies participating.
And we decided, well, it's not really something you
know the research part is done the university should move away from that and let the industry
do it but a few of us and a few of the staff said well but we're really good at this and we want to
keep doing it so let's start a company that can do that so that's one of the sides of tyvek which is that the
the launch and integration services uh component and then the other part was this idea that that
we we kind of knew what the next thing we would do would be if if we could continue you know it's
like we've done this satellite and we've learned all these things and now the students graduate
and go work for somebody else.
But if we could keep them, what would we do?
And we said, oh, there's all these really interesting projects that we would like to do and we think we can get the funding to do it.
And that's kind of where the nugget of the whole idea came um we we decided to do a company that's in some ways
different uh from some of the companies that were evolving at the time there was a number of
companies pumpkin and gumspace were were selling components we saw that as a yeah it's an interesting
market uh and then spire and planet were mission companies that were like we're gonna image the
earth we're gonna go track ships.
You know, we'll do something.
But we felt there wasn't anybody that was saying, OK, we're going to be, you know, the lockheed of the small sats.
When JPL wants to fly a mission, they need somebody.
When somebody has a payload they want to fly at the very high end. They need somebody.
And we felt that was an open niche in the industrial Fiverr ecosystem of CubeSats.
And that's kind of where we went.
And it worked fairly well.
I mean, we're still alive, which as a startup, that's always a great thing to make it past five years and beyond. And one of the things that has happened is we have learned what the capabilities of these satellites, when you go and push the envelope technologically with a very experienced team,
then you can start looking at payloads that are beyond what you could do with CubeSat.
So we're looking at 12 views and we're looking at 50 kilogram satellites that can do synthetic aperture radar or high definition imaging, signals intelligence, all kinds of things
that you never thought you could do with small satellites. And the same way that you can do
amazing things with a 1U, if you apply the same philosophy and the same principles to a
30 kilogram spacecraft, you can do really impressive stuff.
I imagine.
What about the other way?
Have you ever looked at doing even tinier satellites?
We actually, there's a few groups looking at, you know,
we have pocket cubes, which are, you know,
like five centimeters instead of 10 centimeters.
We've seen fractions of the U's, like half a U, which is 10 by 10 by 5.
And we have seen a few efforts to go that way.
And I think that that's going to be the tech demo satellites for CubeSats will be those satellites. We'll test new, smaller sensors and components.
What we have seen is that the 3U, 1U is really small.
And we're trying to push the envelope what you can do with those
and keep moving the capability out while maintaining the size
instead of looking at smaller satellites with lower capability.
And there's an issue from the commercial side.
You have the utility line where you need to get the thing funded and it needs to do a
certain amount of stuff.
And then the amount of stuff you can do on a 3U keeps going up, but you have to do a certain amount of stuff. And then the amount of stuff you can do on a 3U keeps going up.
But you have to do a minimum.
But we've done some 1U missions, and they've been successful.
So there's a lot you can do with a small satellite.
But we haven't pushed really hard onto smaller than 1Us.
That makes sense. I just am boggled by the idea that you can do something
in this 1U 10 centimeters cube.
And as I say that, Chris is holding up his iPhone
and pointing out that you can do a lot more.
What's interesting is, and this is one of the,
there is a curse that comes with standards.
And that is that once you standardize something, it's very easy to do things if you match the
standard. If you go away from it, it's harder. So coming up with a smaller standard or doing
things smaller, it's hard because it's so easy to launch one use um so so that that's an interesting
potential negative with with standardization is that now you're stuck with this 10 centimeter
by 10 centimeter and why is it not 12 i don't know because it was 10 and you know that the
the lighter connector on your car that's everything that you buy to connect electrically to your car, uses this connector that makes no sense as a connector.
And it was really funny.
We were talking, I was talking with my son recently, and he thought that people call it the lighter plug because that was the name.
He had no idea that that actually was a lighter when
he was first designed because he's never seen one um and i realized yeah he's never seen that
the actual original use for this thing that created all the specifics of the standard you
know there's a plug in the middle and the things on the side and all that was to light your cigarette
and now it's it's how you pump your tires in the middle of nowhere.
We used to put a facility for you to light small fires inside your car.
It's perfectly fine.
Do you have any advice for someone who's listening out there
who wants to get into aerospace,
but isn't it Cal Poly in your department?
Well, they would be much better off if they were Cal Poly in my department.
I'm just joking.
I think it's a tremendously valid and tremendously rewarding career.
I think if you have a passion for space or for aerospace, you should go for it and pursue it.
Even though sometimes, you know, I've heard a lot of parents concerned that their students are going into aerospace engineering, but that's limiting their options.
I'm like, no, they're going to be great engineers and they can do all kinds of things.
But that actually works the other way.
If you're very interested in physics, don't become an aerospace engineer,
become a physicist and go into space to do physics. If you're really interested in electronics,
but you want to work in space, pursue a career in electronics and then do electronics in space.
Software, we need everybody. So pursue what you're passionate about and everything can take you to space.
Um, and actually we've, we've, we've had students working with us from liberal arts, uh, from,
from graphic arts, from journalism, and they're tremendously valuable, uh, members of our
team.
Um, so, so that's what I would, that's one of the things that I think is important to
tell people sometimes is that you don't have to be an aerospace engineering student to work in aerospace.
But you do have to be passionate about it.
And then just go do things that you're good at and you enjoy and work in that direction.
That sounds like good advice for all kinds of careers.
Yeah, and I think it's truly advice for all kinds of careers yeah that's and i think it's it's truly advice for all kinds of and these days um you know a few years back if you wanted to work on
cars you have to be a mechanical engineer these days i don't know i think we probably see more
software engineers working in cars than mechanicals. For better or for worse.
For better or for worse, yeah.
So I wanted to ask you to look to the future a little bit.
And if launch costs come down, like SpaceX is trying to do,
if they make reusability a thing,
how does that change things for CubeSats if, say, launch costs are cut in half or down to a quarter?
Does that mean more risk, more innovation, or does it just mean more satellites? sets if, say, launch costs are cut in half or down to a quarter.
Does that mean more risk, more innovation, or does it just mean more satellites?
That's an interesting question.
And I think one of the big risk reducers or one of the things that reduce the risk posture on satellites is launch cost.
And when you start thinking about, you know, a big rocket costs hundreds of millions of dollars,
lowering the cost of the spacecraft by increasing risk doesn't make any sense because your cost will not go below the cost of the launch.
If that number goes down, the ability to take risk really goes up.
And with CubeSats, we are already low enough that people feel comfortable taking some risk.
But it's a big investment.
You know, when you have a $250,000, $300,000 launch cost for a 3U, that is a steep check to write.
If you lower that number, then you get to innovate even more.
And I think it's not just more satellites,
but I think we'll see more people having access,
which means more ideas being tried.
And that's only a good thing.
Is there a limit to how many of these we can put up? I mean, they all have to be
tracked, right? And there's always this question of debris.
The big debris question, I always
brace for it because it's like it's your fault
you're putting all this garbage up there. Especially when we were doing a lot of university
satellites where, with many universities, the universities the first satellite hey if it works for a few days we're
awesome you know we did great um but then it stays in space for a while we we're very conscious of
the rules and and most of the cubesats these days are launching into relatively low orbits
uh well below the limit which is 25 years, uh, station orbits last six months, three months. So
they're, they're out of there very quickly. Um, uh, an example, or, or to see the numbers, we,
we put about 500 and something cubesats in orbit, um, total, uh, more than a hundred were from
station. So they're not there anymore. So that, um, And then of the others, many were low that are back on deorbited
and burning the atmosphere.
What we're seeing is we're probably going to reach a steady state
that's not as large as people think.
Maybe we'll get to the thousands at some point, but maybe not.
And as an example, the Chinese intercept test was many thousands of objects being deployed into space or created as debris in a single event.
So I don't think we're going to be responsible for a large percentage of the object uh the object being tracked i think right now they're tracking like 20 000 or 23 000 or something
um however people are talking about very large constellations you know spacex is talking about
thousands of satellites and one web is talking about many hundreds to a thousand um
and those constellations will be interesting to see how we handle the the collision risk and all
those kinds of things uh and those are not cubesats they're bigger yeah but but yeah debris is an
important issue i just do not think cubesats are are the big problem that people like to say sometimes.
They're there, they're players like everybody else, but we're trying to do our best to play by the rules and minimize our impact.
And I think we're doing a good job of that.
Cool.
And I think the planned obsolescence that is built into CubeSats allows for a bit more risk as well.
They're not supposed to be there for 50 years.
No.
And actually, that's one of the things that was very interesting when we were kind of challenging the traditional space people.
We were saying, you guys are using technology that's 10 years old, so we're going to use the latest and greatest. And one of
the things that we didn't realize is that we also had a tendency to become attached to things we had
tried before. And it's like, oh, but I've flown it before, so I'm going to use it again. And one of
the great things about using commercial on the shelf components is that they they stop making them uh when they're not when
they're not at the top of the the hip so so you have to plan for we will have to change them um
as as the industry evolves and you know these these other markets are investing billions of
dollars in in making better components and we'll have to just follow what they do um the one thing
that has happened though is a lot of the effort
is being in learning how to use those things in space and minimize the risk, you know,
built in electrical and software redundancies that, that help you with some of the things,
you know, will go wrong because the parts are not space qualified and radiation will have an effect
and we'll have flash apps and single event upsets and we we have to find all these tricks to to minimize
how that hurts us um and those tricks work whatever the parts are so as the new model comes out
you get a lot of confidence that well i've flown this architecture before the camera is new
but but it's just an upgrade of the one I already flew.
So people are getting kind of comfortable
with that mentality
that the fact that it's a new specific component
carries the same risks that we always fly.
The fact that we have an architecture
we've proven before
that we feel is, or we know is robust and reliable, that remains.
That makes a lot of sense. Well, I think we have kept you for about long enough.
Wow, right. I just realized how late it is.
Then, Jordi, do you have any thoughts you want to close this with? Yeah, and I don't know if we've made this clear,
but one of the things that I always like to get out there
is that one of the reasons or one of the most important things
that made CubeSat successful was this move to use things from a different industry.
We were using things that were developed for cell phones and laptops and things like that.
And I think in the current technological climate, when there is so much going on, so many changes,
so many advances in materials, in all kinds of things, in electronics and software, that's a very important thing to do, to be
capable or spend the time or have the disposition to look outside your area of expertise and
the group of people that you work with and the traditional methods that we've always
used and go see if there's something out there that somebody is doing for a completely different application that all of a sudden you go, oh, wait a minute.
What if I use this for something completely different?
And we've seen that be extremely successful in space.
And I think we have lots of examples of those kinds of things happening in other industries.
But I think it's amazing how difficult it is to do it because we all tend to like our own stuff and be very good at something and be experts.
And then we stay within that world.
So just something for everybody to think about whatever you do, whatever your industry is every once in a while, you know, take a glance sideways to what those guys over there that are doing something
different, um, are doing. And every once in a while,
there may be a surprise.
Cool.
That is excellent. It has been wonderful to talk to you, Jordy.
Thank you. It was a pleasure. And if you
guys have the time, just come for the workshop.
It's a lot of fun.
It's just really tempting.
We hope the weather will be
good.
Maybe. I mean,
April in California is often very
nice. It is, indeed.
And you guys are not that far away.
Before we go, you're hiring at Tyvek.
And we should note that because you are hiring for hardware and embedded software and software people.
And it's in Irvine, is that correct?
Correct.
Our main operation is in Irvine.
We also have a small office in San Luis Obispo that does the launch services.
And we have a small group working out in Colorado.
And we're starting to have some people in D.C. as well as we get more contracts with the government.
So we have people in several places, but the primary job location is Irvine, which is not a bad place to be.
And we do hire everything, software, hardware, electronics.
And one of the things that's interesting is we've been very successful at creating a group of people that has a very good mix of traditional space people,
as well as people that come from completely different markets
and bring that expertise to the
table. And that combination has been very successful. So we have a number of individuals
we've hired that were not coming from the aerospace industry, and they're great contributors.
So I would say if you're interested in space, even if you're not a space person,
there's still a spot there for you.
All right.
Thank you.
Thank you.
Our guest has been Jordi Puchsuare, professor of aerospace engineering at Cal Poly San
Luis Obispo and co-founder of Tyvac Nano Satellite Systems.
If you want more information about the available careers, it's tyvek.com slash careers.
That link will be in the show notes, along with the link to the CubeSat conference.
Although, cubesat.org is pretty easy to remember, so you can do that.
I would like to send a special thank you out to Stuart McAndrew for sending me some excellent questions.
Stuart has been working on his own CubeSat for a while now. It's an Arduino-based educational satellite. I have to say, there's nothing like sending something you've touched to space. More info on his microphone came from our supporters at Patreon. Thank you for making it easy for me to drop ship mics to interesting people. It makes my life much easier to just
make that decision. And whether you are a Patreon supporter or not, thank you for listening.
A final thought to leave you with, this time from one of my least favorite great literary figures, Henry David Thoreau.
You must live in the present.
Launch yourself on every wave.
Find your eternity in every moment.
Fools stand on their island of opportunities
and look towards another land.
There is no other land.
There is no other life but this.
He may be kind of a dweeb,
but he can write pretty well. If there are advertisements in the show, we did not put them there and do not receive money from them.
At this time, our sponsors are Logical Elegance and listeners like you.