►
From YouTube: ORI FPGA Stand-up Meeting 19 April 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
B
Good
morning,
or
whatever
time
it
is
for
everybody
morning
for
me
and
I'm
half
asleep
still,
we
made
some
progress
on
getting
an
sr1
based
test
environment
working
in
the
remote
lab.
The
sr1
is
a
device
from
hayeka.
I
believe
they
pronounce
it
that
way
which
receives
ddbs
to
understands
gse,
and
it's
intended
for
data
applications.
B
And
also
through
an
ethernet
port,
two
ethernet
ports,
actually
one
for
management,
which
does
what
a
serial
port
can
do,
plus
other
things,
and
then
a
traffic
port
then
has
two
rf
inputs,
and
these
can
be
hooked
up
on
demand
to
any
rf
source
that
we
have
in
the
lab
in
the
if
frequency
range.
I
think
it
covers
something
like
950
to
2000
megahertz.
B
Beginning
radio
flow
graph
for
transmitting-
and
this
is
working
which
puts
us
back
into
where
we
were
in
about
2018.,
so
we
now
have
and
once
again
the
ability
to
test
dbb
s2
transmit
from
new
radio
through
this
commercial
device.
But
now
we
can
do
it
completely
in
the
remote
lab
and
I'm
working
on
a
a
demonstration.
Video
of
this,
hopefully
in
the
next
few
days,
we'll
be
able
to
see
exactly
how
that
works
from
a
fully
remote
lab
perspective.
B
We've
put
other
commercial
devices
online.
I
think
we've
already
talked
about
the
the
deck
tech
boards,
one
of
which
is
in
a
in
a
vm
and
the
other,
which
no
one
is
an
aperture.
One
is
in
hello,
kitty
two
standalone
windows
machines
because
they
support
it.
Hardware
is
windows-based,
maybe
one
of
those
will
move
back
into
the
vm
once
we're
convinced
that
we
know
what
we're
doing,
because
the
problems
turned
out
not
to
be
vm
related
as
we
suspected
they
were
when
we
moved
into
a
special
machine.
A
All
right
next
on
the
list
is
anshul
makar.
You
have
the
floor.
D
Thank
you.
For
this
week
I
was
trying
to
integrate
adi's
reference
design
and
firmware
along
with
dbps2
so
and
I'm
taking
help
from
whatever
is
healing
f5
oeo,
so
he's
helping
me
and
yeah
so
taking
the
reference
script
of
what
has
been
done
for
bluetooth
design
and
integrating
it
for
set
c706
facing
some
issues,
resolving
them
and
moving
forward.
Apart
from
this
involved
with
some
other
of
some
of
the
other
ori
activities
like
codec2
and
one
more
project,
so
yeah,
that's
my
week.
A
C
Hi
hi,
so
last
this
past
week
I've
been
trying
to
identify
an
issue
that
everest
found
that
basically
the
when
he's
changing
the
consolation
around
it.
Sometimes
the
the
encoders
don't
sometimes
get
stuck,
and
I
think
I
found
the
the
reason
it's
something
in
the
in
the
consolation
mapper.
I
did
not
catch
because
reasons,
essentially
the
I
to
minimize
resources.
C
I
chose
to
only
provide
like
one
table
for
qpsk
one
for
eight
psk,
one,
you
know
and
so
on
so
forth,
but
for
16
and
32
aps
k
the
amplitude
changes
with
the
code
rate,
so
I
just
left
okay,
you
know
I
can
do
one
of
each,
but
you
know
the
it's
one
table
for
16
and
one
for
32.,
so
the
test
would
write
the
the
table
if
needed,
and
that
sort
of
masked
the
issue
of
going
back
and
forth,
because
obviously
you
need
to
stop
so.
C
I
plan
to
fix
well
this
issue
that
that
gets
the
the
encoder
stuck
and
allows
supporting
more
or
all
the
the
all
the
combinations.
C
A
Yeah,
that
makes
sense,
that's
a
that's,
a
critical
trade-off
for
for
a
lot
of
what
we're
dealing
with
and
looking
at.
Thank
you
all
right.
So
so
do
you
need
any
additional
resources
or
are
everything
yeah.
A
A
Okay
yeah,
just
if,
if
anything
you
need
please
let
us
know.
C
D
Thanks
so
what
a
few
questions
so
I'm
using
fibaro
2020.2
to
integrate
dvds
too,
so
I
think,
will
that
be
fine
or
do
I
need
to
upgrade
to
2021.
C
D
Okay
got
you
yeah,
it
did
complain
and
I
just
asked
it
to
ignore
the
yeah.
C
C
A
Yeah,
thank
you
both
okay,
any
other
any
other
comments
or
or
questions
or
needs.
A
Okay,
everest:
do
you
have
the
floor.
E
Yeah,
okay,
so
last
week
the
main
the
main
work
was
to
to
try
to.
E
E
E
Call
it
but
how
to
send
with
io
exactly
dmi
size
and
how
to
handle
it
from
the
ps
perspective
to
the
pl.
So
right
now
it's
very
clear.
So
it's
it's
good!
The
next
step,
I
think,
would
be
to
integrate
the
transport
stream
first
and
then
the
gs
after
that.
So
thanks
support
to
set
up
all
the
all
the
testing
equipment,
as
we
can
be
ready
to
test,
hopefully
soon.
E
A
So
we
have
an
opportunity
to
show
this
off
and
record
and
and
and
publish
on
the
a
minor
event
at
university
of
san
diego
on
the
26th
of
april
and
then
ieee
meeting
in
the
4th
of
may
so
I'll
talk
on
slack
about
that
a
little
bit
more
because
this
opportunity
to
show
this
stuff
working
over
the
air
in
person
and
to
publish
the
the
results
you
know
on
to
the
repo
and
all
of
our
channels.
A
So
it
sounds
like
we
have
some
things
to
show
and
it's
that's
a
wonderful
place
to
be.
E
So
well,
there
is
already
something
to
show
which
means
that,
as
soon
as
we
are
working,
we
try
to
test
more
and
more
features.
E
But
some
basic
features
like
having
well
just
swapping
from
mod
codes
at
qpsk
or
eight
psk
is
working,
which
means
that
I
think
that
we
can
already
demonstrate
some
adaptative
channels.
E
But
yeah,
I
think
that
there
is
already
something
to
show.
A
Agree:
yeah,
I'm
very
excited.
This
is
extremely
good
news,
so
I
will
we'll
coordinate
on
slack
and
figure
out
how
to
how
to
present
it
show
it
and
also
everest.
I
think
there
was
an
opportunity
for
you
to
present
at
friedrichshafen
in
this
coming
summer
at
the
sdr
forum.
E
Yeah
yeah,
so
I
already
send
them
just
a
title
and
they
are
very
exciting
to
to
accept
it,
and
they
want
to
to
have
more
details
on
that.
Okay,
yeah
yeah.
E
That's
not
my
task
but
yeah.
I
know.
A
B
A
We
can
do
to
to
help
you,
please
let
us
know,
and
on
at
friedrichshafen
we
do
have
a
booth,
so
the
m17
and
open
rtx
teams
have
a
booth.
I
I
don't
know
if
you're
going
to
be
there
in
person
or
if
you're
going
to
present
virtually.
E
No,
I
would
be
even
I
think
that
I
I
would
send
them
a
video
okay.
Unfortunately,
at
this
time,
so
I
don't
know,
I
don't
know
if
they
need
that.
I
have
to
well
virtual
conversations
who
zoom
for
questionnance,
but
at
this
time
I
have
already
a
full.
Well,
I'm
not
available,
so
I
don't
okay
or
not,
but
maybe
if
there
is
another
well,
I
have
to
check.
But
if
there
is
another
person
who
can
try
to
answer
the
question,
it
could
be
good.
A
Okay,
yeah
I'll
see
what
I
can
do
yeah
if
but
yeah,
we'll
we'll
also
spread
the
word
at
the
event
about
the
your
presentation.
Thank
you
so
much
for
doing
this.
I
think
it
will
be
very
well
received
and
you'll
get
a
lot
of
very
positive
feedback
from
from
the
effort.
It's
good
work.
A
E
A
E
Html,
so
there
is
on
already
a
component.
I
do
on
my
own
github,
which
could
be
go
to
ri
and
then
after
that,
have
a
complete
firmware
which
could
be
easy
to
integrate
for
people
who
want
to
to
test.
A
Okay,
yeah,
we
will
fix
it,
we'll
make
it
happen.
Okay,
yeah,
thank
you,
okay,
and
so
for
just
briefly.
On
my
end,
the
so
I
have
not
yet
figured
out
how
to
get
hdl
coder
to
do
the
last
easy
part,
all
the
hard
part
works
for
taking
matlab
scripts
and
and
bringing
them
all
the
way
through
to
our
our
remote
lab.
So
I'm
a
little
bit
baffled
so
we'll
I'll
keep
working
on
that.
A
I've
got
the
point
where
I'm
gonna
reach
out
to
to
both
mathworks
and
xilinx,
and
try
to
figure
out
what
exactly
is
the
issue
with
it?
Refusing
to
work
at
the
last
easy
part
of
it's,
the
device
is
actually
being
programmed
by
matlab,
which
is
calling
vivado
command
line.
Scripts
should
be
easy,
but
I
think
we'll
figure
it
out
and
then
we'll
be
able
to
test
over
the
error
with
the
uplink
side.
A
So
this
work
in
matlab,
hdl
coder,
is
is
using
the
m17
protocol,
for
you
know,
to
to
process
and
to
to
present
to
the
to
the
remote
lab
work,
roommate
lab
equipment.
A
We
have
another
opportunity
for
both
the
codec
to
work
and
m17
protocol.
M17
uplink
that
the
the
work
that
we're
doing
to
take
the
m17
9600
bit
per
second
version
and
move
it
to
to
microwave,
because
that
may
involve
some
some
changes
to
the
the
protocol.
So
all
of
that
work
is
going,
is
going
on
and
is
going
to
be
presented
on
the
4th
of
may
we
have
a
joint
meeting
between
the
amateur
radio
community
and
ieee
on
the
4th
of
may
so
so
there'll
be
a
recording
of
that
presentation.
A
The
slides
are
in
progress
and,
and
there
will
be
a
lot
of
written
work.
A
side
effect
of
this
is
that
the
m17
protocol
really
needs
a
justification
document
or
a
document
that
describes
like.
Why
do
you
do
this?
Essentially
an
implementation
guide
and
I'm
pleased
to
report
that
there's
an
awful
lot
of
momentum
and
work
in
that
direction?
There's
several
volunteers
both
at
ri
and
at
m17
that
are
working
on
this
and
somebody
from
the
community
who's
very
interested
in
working
on.
A
A
A
So
all
of
that
stuff
is
also
going
on
and
will
only
benefit
the
the
downlink
and
the
the
transponder
and
downlink
side,
because
if
you
have
quality
stuff
bolted
up
to
your
system
as
an
uplink
and
you're
able
to
interface
with
it
at
a
high
level
and
to
you
know
to
control
the
flow
of
information
in
the
right
way,
then
your
system
has
all
of
the
ingredients
to
be
more
successful.
A
So
these
are
the
things
are
going
on
and
they'll
be
going
on
all
the
way
through
throughout
april
and
may
the
the
eventual
goal
we're
looking
forward
to
august
to
present
a
working
as
working
as
possible
over
the
air
end
and
demo
at
defcon,
which
is
an
extremely
large
event.
A
You
know
we're
expecting
mid
20,
000
people
and
almost
all
of
them
would
be
impressed
and
and
engaged
in
the
work.
So
that's
kind
of
the
the
goal
that
I'm
I'm
trying
to
organize.
The
work
for
events
that
are
in
this
category
are
friedrichshafen,
which
is
coming
up
much
much
sooner,
and
you
know
there's
a
few
others
around
the
calendar.
A
So
so
that's
the
perspective
from
from
where
I'm
sitting
and
and
what
I'm
trying
to
enable
in
order
to
showcase
the
work
that
you
all
are
doing.
That's
really
quite
wonderful,
so
thank
you
very
much
for
all
of
your
efforts
and
attention
and
please
let
me
know
if
there's
anything
I
can
do
to
help
all
right,
any
last
comments
or
questions
before
we
close
for
the
day.