►
From YouTube: ORI FPGA and Remote Lab Meeting 27 September 2022
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Start
in
one
minute,
there's
a
lot
going
on
all
right:
it's
ten
woohoo,
hello,
everybody
we'll
go
ahead
and
start
I
know
that
onshole
has
been
very
busy
posting
and
contributing.
So
so,
if
he
joins
us
great,
but
I
have
have
some
updates
from
what
he's
shared
already.
So
this
is
our
stand
up,
we'll
do
our
stand-up
for
fpga
work
first,
and
what
we
do
is
talk
about.
We've
done
over
the
last
little
bit
in
our
case,
it's
a
week.
A
Yes,
I
know
that
this
is
not
traditional,
stand-up
style,
which
is
daily.
You
know,
but
we
do
what
we
can.
So
we
talk
about
what
we've
done
over
the
past
week,
what
we're
gonna,
what
we
have
planned
to
do
over
the
next
week,
if
we
have
any
roadblocks
and
that's
kind
of
the
the
key
function
here
is
to
figure
out.
A
So,
in
terms
of
like
fpga,
stand
up,
let's
go
ahead
and
do
a
Roundup
and
I
think
I'm
going
to
say:
I,
don't
have
any
substantial
progress
since
the
last
we're
we're
working
on
understanding
how
to
do
the
Uplink
receiver
and
no
I
have
not
gotten
it
working
on
our
in
our
Dev
board.
But
we've
we've
done
a
huge
amount
of
of
research
into
figuring
out.
If
we
actually
have
a
right
right,
understanding
of
minimum
frequency
shift,
keying
turns
out.
We
we
do
and
we'll
keep
digging
in.
A
A
So
I
guess
when
I
say,
there's
lots
going
on.
There's
lots
going
on,
but
it's
not
yet
visible
in
the
in
the
development
board
or
fpga.
Lab
I'm
really
really
excited
about
this.
So
thank
you
very
much
to
Paul
and
all
the
other
people
that
have
helped
us.
That's
a
that'll,
be
a
big
step
forward.
A
We've
had
a
big
step
and
with
demonstrations
over
the
air,
with
just
essentially
the
bear
Opus
stuff
with
a
header
file
all
and
and
seeing
that
working
and
presenting
it
to
the
community
and
getting
a
good
response
was
fantastic.
A
The
next
part
is
to
finish
the
protocol
and
then
implement
it
on
it
on
HDL
the
what
I
showed
last
week
or
two
was
a
frequency
shift
keying
in
the
time
domain,
in
a
HDL
implementation
in
verilog
that
was
working
on
a
smaller
processor
and
there's
been
some
good
discussion
on
slack
over
especially
over
the
past
week,
and
one
of
the
interesting
things
is
that
one
of
the
modules
is
the
synchronizer
which
it
takes
in
two
values:
the
high
and
the
low,
because
this
is
binary
FSK,
so
you
have
either
a
zero
or
one
and
it's
either
high
or
low
frequency,
so
highs
and
lows
and
zeros
and
ones
are
connected.
A
That
actually
got
some
criticism
from
some
experienced
Asic
designers
from
two
of
them.
Thomas
Perry
flagged
it
correctly
as
a
clock
domain
challenge
that
that's
odd
to
do
that,
and
and
has
some
risk
that
you
might
update
some
of
the
bits
in
the
value
and
not
others
and
and
Qualcomm
volunteer
said
the
same
thing.
So
it
was
interesting
choice.
A
It
looks
like
that
the
designer
which
I
have
yet
to
confirm,
but
it
looks
like
the
designer
of
this
particular
open
source
repo,
really
wanted
to
be
very
flexible,
wanted
there
was
a
clock
domain
crossing
here,
meaning
that
you
have
results
or
your
your
limits.
What
does
a
zero
and
what
is
a
one
with
your
FSK,
which
might
have
Doppler,
which
might
have
noise,
might
be
some
some
other
things
might
be
changing
and
they
wanted
it
to
be
adaptable.
A
That's
our
interpretation,
but
those
things
are
coming
from
outside
of
the
clock
domain.
In
the
rest
of
the
logic
and
anytime,
you
have
a
domain
crossing,
that's
a
big
red
flag
for
you
to
fix.
So
when
we
implement
it,
we
might
just
drop
that
entire
module
and
that
it's
interesting,
because
the
module
is
from
Edis
research
and
is
neat
and
good
and
looks
like
it's
been
around
for
a
while.
A
But
but
maybe
we
don't
need
it
or
we
we
figure
out
a
way
to
use
it
or
or
to
have
the
same
sort
of
functions
without
a
clock
domain
Crossing.
So
anyway,
that's
that's
kind
of
the
update
there
I
know.
A
Onshold
has
been
been
working
on
the
mqtt
control
for
the
downlink
transmitter,
I've,
not
seen
anything
in
the
lab
yet,
but
they're
still
working
on
it
and
he's
been
also
engaged
with
updating
and
and
getting
the
versatoon
receiver,
which
is
a
wonderful
project
that
we
will
be
featuring
at
hamcation
next
year.
A
Okay,
so
that's
that's
it
for
me.
That's
my
report,
I'm
going
to
hand
it
over
to
to
James
and
then
James.
You
can
hand
it
over
to
Paul.
C
Hello,
everyone,
I'm
James
I
work
with
the
Ori
remote
lab
South
I,
take
care
of
some
of
the
equipment
here
and
get
some
of
the
lab
running,
not
too
much
a
report
from
mermaid
lab
South.
This
past
week,
we've
just
been
keeping
on
getting
more
work
done
on
repairing
the
main
building
that
will
be
holding
up,
holding
and
hosting
a
lot
of
our
equipment,
but
not
too
much
to
report
there
Beyond
just
the
work
that
we
keep
doing
so
I'll
go
ahead
and
pass
that
on
to
Paul.
B
B
This
adds
a
substantial
amount
of
overhead,
so
we'll
have
to
adjust
the
the
bitrate
on
the
channel
and
so
on.
This
should
be
non-disruptive,
because
we've
tried
to
parameterize
everything,
but
it's
always
dangerous
word
to
use,
should
so
I
had
nothing
further
for
the
fpga
part
of
the
meeting
and
nothing
going
on
in
the
remote
Labs
either.
All.
A
Right,
hey!
Thank
you.
So
much
for
all
the
protocol
work
yeah.
It
should
be
something
that
we
can.
We
can
adjust
the
existing
design
to
and
parameterizing
it
in
the
HDL,
as
well
as
the
general
purpose
code.
I.
Think
we'll
we'll
do
do
us
good,
I'm,
still
still
interested
in
looking
at
at
maybe
a
runtime
adaptation
for
the
bit
rate,
but,
like
we
talked
about
yesterday,
if
it's
just
build
time,
then
I
think
that's
that's
quota
busting
in
and
of
itself
all
right,
oh
hello,
angel
I,
know
you
you've
been
quite
busy.
D
Yeah,
starting
with
encoder
part,
so
mqtt
I
was
able
to
remove
all
the
hard
coding
or
all
the
customization
that
was
related
to
Pluto
I,
adapted
it
to
zc706..
D
But
it
looks
like
still.
Some
more
changes
needs
to
be
done
where
we
are
getting
voltage.
Frequency
device
ID,
so
still
more
changes
need
to
be
in
mqtt
streaming
is
the
file
is
the
binary
where
some
more
changes
are
required,
so
I'm
working
on
that,
but
in
the
meantime,
I
just
thought
of
removing
the
complexity
of
mqtt
and
just
work
on
a
simple
application
that
will
just
get
the
context
IO
context
and
do
some
transfers
that
worked.
D
I
got
three
iterations
of
e
x
and
RX,
but
of
course,
in
those
in
that
when,
when
those
transfers
were
done,
our
encoder
was
not
involved.
So
if
I
run
my
script
to
check
the
registers
to
let
to
PB
Scrambler
and
everything
all
the
components
of
encoder,
those
all
show
zero,
but
I
see
that
TX
and
RX
being
done
so
that
gave
that
has
given
me
confidence
and
now
I
will
go
back
to
mqtt,
adapt
it
further,
and
my
aim
here
is
when
I
should
run
the
register
status
file.
D
It
should
give
me
how
many
packets
are
in
transit.
That
will
give
us
assurity
that
encoder
is
working
properly.
That's
on
that
front
on
versatile
in
front.
You
can
see
that
picture.
That's
versatile
running
on
another
monitor,
I
got
the
code.
I
got
the
code
compiled
today.
Bob
was
busy
with
some
other
work,
but
yeah
he
shared
steps,
so
I
got
the
code
compiled
and
run
I
am
able
to
execute
that.
Also,
there
is
another
software,
that's
long
grind
or
something
and
that's
the
base.
D
One
I'm
able
to
compile
that
code.
Also
now
I
will
progress
on
that
of
basically
I
will
start
working
on
the
actual
task,
that's
needed
so
I'm
going
to
have
discussion
with
art
and
Bob.
With
regards
to
that
yeah,
that's
me.
A
Well,
that's
a
tremendous
amount.
Thank
you
so
much
very
exciting
to
see
all
of
this
happen
and
and
if,
if
anybody
wants
to
follow
along
or
help
the
the
versatoon
project,
then
please
get
in
touch
with
anshul
and
yeah.
Well,
we're
looking
forward.
We
plan
on
this
being
at
ham
occasion
and.
A
Yeah,
so
if
you
can
support
that,
if
you're
interested
in
volunteering
for
that,
then
let
me
know
groovy.
Okay,
we
have
a
lot
of
things
that
are
going
to
be
published
soon
for
the
transponder,
so
our
open
source,
heo
Geo
transponder
work,
is
going
to
appear
in
the
Jam
Set
Journal.
So
this
is
a
another
place
where
the
same
sort
of
presentation
from
Ham,
Expo
and
Defcon
will
will
appear,
and
this
is
a
membership
and
an
organization.
A
That's
been
really
vital
in
giving
us
good
feedback
and
that
we
hope
to
partner
with
to
make
this
a
reality
for
for
getting
into
space
at
any
level.
I
think
that
it's
up
to
the
community
us
included
to
put
together
a
functional
Consortium
of
organizations
that
can
get
this
into
space.
In
the
meantime,
we
have
all
sorts
of
things
going
on
terrestrally,
so
the
the
work
for
the
Uplink
protocol
can
also
be
used.
A
Trust
really
we're
making
lots
of
progress
with
several
groups
and
several
implementations
and
we'll
have
a
demo
in
November
at
the
San
Bernardino
microbe
Society.
So
that's
our
next
opportunity
to
show
off
all
this
stuff
working
the
power
bus
side
of
the
house
is,
is
getting
in
into
into
shape
so
providing
power
to
all
of
these
things.
A
Fpgas
can
can
draw
some
amount
of
power,
so
we
need
to
be
able
to
provide
Power
for
the
the
digital
board,
for
the
ttnc
and
for
all
of
the
RF
components,
and
so
those
budgets
and
an
actual
bench
top
you
know,
design
and
and
prototype
or
underway,
and
we're
building
Motors
as
well.
So
all
of
this
stuff
feeds
into
the
communications
which
will
be
enabled
by
fpga
work.
A
So
plenty
coming
up.
I
think
that
our,
but
our
major
shows
for
the
for
our
kind
of
season
tends
to
be
kind
of
late
summer
fall
that
is
over.
So
we
will
have
more
uninterrupted
time,
which
is
the
thing
that
we
all
view
as
the
true
currency
of
volunteer,
Source
or
a
volunteer
and
open
source
work
is
uninterrupted
time.
I
think
we
could
all
probably
use
more
of
that.
A
Okay,
any
other
questions
or
comments
or
any
resources
that
you
might
need
that
we
can
help
with
or
any
roadblocks
I
think,
let's
go
ahead
and
speak
up
if
you
have
them
or
or
any
last
advice
or
comments
for
the
for
the
upcoming
week,.
A
That'll
be
hyperaria
bus,
there's
also
a
little
bit
in
the
propulsion
channel
on
slack,
but
just
a
little
bit.
The
propulsion
is
about
the
trying
to
build
the
Prototype
propulsion
in
and
and
that,
of
course,
then
then
is
related
to
the
bus
work,
but
hyper
Raya
bus
is
where
the
the
power
consumption
stuff
is
is
going
on.
A
A
You
really
need
to
figure
out
the
power
dissipation
and
the
power
consumption
as
soon
as
possible,
along
with
the
mass
and
and
all
that,
but
the
the
power
consumption
is
really
kind
of
critical
because
we
think,
based
on
the
Delta
V,
which
we
do
have
a
more
challenging
orbit
than
in
the
past,
because
we
have
a
higher
the
the
lowest
altitude.
We
want
it
to
be
1250
kilometers
and
that
is
going
to
increase
the
Delta
V,
which
increases
all
sorts
of
other
stuff,
and
so.
D
A
At
the
electronic
propulsion,
the
estimate
right
now
is
18
to
24
little
teeny
engines
in
arrays
and
well,
that's
that's
plenty
of
power.
So
so
now
we
need
to
to
go
through
and
and
actually
build
something
and
see
see
what
we
can
do
so
it'll
be
by
comparison
to
to
maybe
flight
Hardware.
This
is
fast
and
cheap.
So
what
we're
going
to
do
is
bring
out
all
those
nickel
metal
hydride
cells
that
we
have
go
ahead
and
do.
A
Matching
curves
and
that
will
be
the
re
that
will
stand
in
for
the
rechargeable
source,
which
may
end
up
being
lithium
ion
in
space,
because
that's
what
most
people
use,
but
the
those
batteries
will
be
pulled
out
of
the
fridge
and
put
together
into
into
batteries,
and
we
now
know
that
there
are
plenty
of
super
caps
that
we
can
get
to
put
for
the
super
capacitor
part
of
this
design,
because
that
is
looking
like
a
good
thing
to
have
for
the
electric
propulsion.
A
It's
a
good
match
and
then
solar
panels,
and
so
some
sort
of
solar
panel,
simulator
or
solar
panel
or
actual
solar
panel
to
stand
in
and
then
we'll
have
this
on
a
bench
and
and
basically
make
it
work
really
hard.
And
that's
that's
going
to
be
the
basis
of
our
of
our
bus.
A
We
do
have
a
good
tool
from
Libra
Space
Foundation.
They
have
a
power,
consumption
or
power
management,
python
framework,
and
that
is
linked
in
the
slack
Channel.
A
A
All
right.
Thank
you,
everybody!
It's
been
quite
the
week.
We
got
plenty
going
on
across
the
board
in
all
sorts
of
projects,
and
thank
you,
everyone.
So
much
for
your
time.
It's
invaluable
and
deeply
appreciated.
All
right
see
you
on
slack,
see.