►
From YouTube: ORI FPGA Standup 31 May 2022
Description
Encoder integration on the downlink, additional human resources, plans for Remote Lab South, uplink simulator and higher data rate operation, and more.
A
B
A
Okay,
yeah
looking
forward
to
that,
we'll
continue
to
work
on
making
it
a
a
special
place,
so
remote
lab
south
will
have
almost
all
the
same
equipment
from
that
remote
lab
west
has
for
dsp
fpga,
but
we're
looking
at
also
putting
a
bacteriophage
or
wet
lab
there
as
well.
So
lots
of
outreach
will
have
to
happen
and
support
from
ipath
here
in
san
diego
and
from
possibly
from
uams
in
arkansas,
so
we're
we're
looking
looking
towards
towards
that
in
the
future.
C
D
A
And
everything,
but
I
think
that
you
know
pressing
a
little
harder
and
doing
a
lot
more
more
hands-on
work
might
might
help
over
the
summer,
so
I'm
all
in
and
we
have
an
additional
resource.
So
ken
easton
has
joined
our
team,
he's
a
asic
and
fpga
designer
from
qualcomm
and
finally
has
enough
time
to
spend
on
the
project.
So
I
think
that
we're
in
pretty
good
shape
for
for
the
summer
other
people
there's
a
resume
that
I
have.
That
was
handed
to
me
for
someone.
C
A
D
C
Yeah,
I
think
now
it
makes
sense.
Now
we
have
all
the
code
in
it's
just
need
to
get
the
product
working.
Last
week
I
tried
to
reach
everest,
but
he
was
also
busy.
So
I
couldn't
get
my
meeting
time
with
him.
So
you
you
have
experience
in
this
domain.
I
can
code
fbj,
but
this
is
the
first
time
I'm
doing
this
communication
thing
so
yeah,
that's
where
maybe
we
both
can
sit
and
make
it
work.
Yeah.
A
A
Yes,
yeah,
that's,
I
agree,
couldn't
agree
more
so
yeah,
we'll
there'll,
be
lots
of
I'll,
have
lots
of
dumb
questions
because
my
you
know
I'll
have
to
come
up
to
speed
on
modern
vivato,
for
instance,
you
know,
but
there's
other
things
that
I
know
how
to
do
and
it's
it's
actually
I'm
very
confident
that
we
can.
We
can
pull
this
off
so
very
much
looking
forward
to
august
and
and
then
beyond.
So
that's,
that's
that's
what
that's
what
I
think.
A
Yeah,
that's
yeah
the
make
failed
for
me
for
on
the
code
for
from
from
you,
which
makes
sense
and,
and
it
followed
pretty
much
the
same
path
as
ever
east's
pluto
code.
We
do
have
the
bitstream
from
that,
we're
not
sure
how
to
test
it.
Yet.
So
I
asked
him
like
what
was
your
test
setup
and
what
should
we
expect
to
see
and
and
how
can
we
prove
that
it's
working
on
the
pluto,
the
same
ip
in
the
pluto.
C
A
C
A
C
C
A
He
did
not
so
there
wasn't
any
instruction
with
like
okay
do
you
know
now,
then,
do
anything
with
the
processor
side,
but
the
bitstream's
on
it.
So
I'm
what
I'm
hoping
to
do
is
to
be
able
to
just
okay.
So
if
I
force
feed
it
samples,
you
know
and
make
it
transmit,
then
I
should
see
the
evidence
of
the
encoder
working.
I
think,
unless
it
absolutely
requires
it
to
be
configured,
you
know
told
what
to
do
through
through
the
connections.
A
A
C
Yeah,
the
the
way
I
implemented
is
I
loaded
the
linux.
I
used
petalinx
config
to
include
the
bit
stream
along
with
the
linux,
and
then
I
loaded
it
so
that
if
I
have
to
do
a
dma,
because
ultimately,
the
packets
will
go
from
the
processor
side
dma
through
the
bit
stream
to
the
rdl,
and
then
it
should
forward
the
packet
over
the
air.
So
that
was
the
path
I
follow
so
yeah
we
just
have
to
mix
and
match
and
let's
see
what
one
works.
C
C
E
E
E
E
So
taking
a
step
back
and
trying
to
figure
out
what
that
looks
like,
or
maybe
some
kind
of
prototype
at
least
approximates
what
it
will
look
like.
So
we
can
start
mocking
up
some
multi-channel
tests
of
that
sort,
which
will
make
a
fun
demo
too
so
that'll
be
essential.
I
think
to
qualifying
the
spacecraft
software
with
the
multi-channel
receiver
on
it.
E
A
Thank
you,
yeah,
the
the
the
work
with
the
pluto.
What
we
started
out
doing
with
the
with
that
was
to
make
sure
that
we
knew
how
to
restore
it
back
to
a
configuration
that
could
be
used
by
by
anybody
for
any
purpose,
and
we
think
we
know
how
to
do
that.
We
know
how
to
restore
the
firmware
and
we
know
how
to
restore
the
stock
bitstream
that
goes
in
the
fpga
and
everything
seemed
to
work.
A
Okay
and
then
we,
we
also
learned
a
little
bit
more
about
how
to
operate
hardware
with
simulink
from
matlab
and
it's
extremely
similar
to
gnu
radio
and
that
you
drag
and
drop
blocks
and
you
connect
up
the
blocks
with
wires
and
if
it's
a
flow
graph,
it
has
its
own
quirks
and
learning
curve.
So
so
that's
also
been
going
on
and
yeah,
that's
that's.
The
focus
there's
the
uplink
simulator
is,
is
exciting
and
necessary
and
then
having
having
both
parts,
the
transmitter
and
then
the
receiver
receiver
part.
A
I
don't
think
we've
done
a
whole
lot
of
work
on
at
all,
but
we
should
turn
our
attention
to
that
as
soon
as
we
get
the
transmitter
in
any
state
where
it
can
deliver
the
things
that
we
send
it.
So
as
soon
as
we
get
the
processor
side,
direct
memory,
access
and
baseband
frames
doing
anything
reasonably
reliably.
Then
the
time
that
time
is
is
the
point
where
we
then
go
okay.
A
So
anyway,
things
are,
things
are
going
pretty
well,
and
my
hope
is
that
by
by
addition,
with
additional
resources
and
by
by
really
increasing
the
amount
of
time
that
some
of
us
are
spending
on
it,
that
we
will
start
to
start
to
see
all
of
this
code,
the
disparate
chunks
come
together
and
and
actually
work
over
the
year.
So
again,
the
goal
is
looks
like
mid-august,
which
is
going
to
come
up
really
really
soon,
and
you
know
every
every
week
should
have
progress,
good
progress
towards
that
all
right.