►
From YouTube: FPGA Meetup for 25 October 2022
Description
Action packed!
A
B
D
C
Thank
you
for
tolerating
our
our
Halloween
Obsession
here.
Halloween
is
a
super
important
holiday
to
many
of
us,
and
it's
not
just
Halloween,
but
all
the
fall
Traditions
the
Autumn
of
the
year
is
an
important
time,
so
we
try
to
make
it
fun
anyway.
Thank
you
for
so
much
for
being
here
today.
I
think
we'll
go
around
real,
quick
and
do
a
stand-up
of
what
we've
done
over
the
past
week,
what
we're
doing
over
the
next
week
and
if
we
need
any
resources
or
have
any
roadblocks.
C
So
let's
take
care
of
that
first
and
I
think
everything
that
I
have
to
say
is
going
to
be
in
the
the
going
through
the
tuckle
script
and
figuring
out
how
to
get
the
encoder
working.
So
we've
been
working
kind
of
hard
on
this
and
lots
of
different
stuff
with
that
and
the
learning
rate
has
been
very
high,
which
is
always
good
and
I.
Think
we're
we're
close
and
all
that.
So
that's
that's!
E
E
F
F
A
A
F
D
C
Not
something
that
I'm
very
good
at
programming
or
using,
but
the
the
understand
the
concept
and
I
think
that
it's
a
very
powerful
thing
for
radios
and
and
that
it
will
make
it
super
easy
and
wonderful
for
us
to
use
so
yeah.
Please
proceed.
I
I,
don't
want
any
of
the
none
of
this
discussion
should
be
against
that
it's
not
either
or
you
know
so,
because
I
think
mqtt
probably
uses
the
same
sorts
of
calls.
C
The
same
sorts
of
Linux
calls
and
the
same
libraries
that
we're
trying
to
get
working,
and
you
know
so
it's
been
a
little.
So
it's
I,
I'm,
just
kind
of
I
I,
guess
I'm
a
little
I'm
like
wow.
This
has
been
kind
of
hard
to
get
it
up
and
running
and
now
I
think
we
we
might
be
more
on
to
it,
so
so
so
yeah.
C
So
what
we
should
probably
look
at
is
the
the
the
way
that
our
our
development
system
is
set
up
is
that
you
go
and
get
the
repository
that
anshul
owns.
This
is
the
ADI
adrb
9371
zc706
repository,
and
what
that
does
is
a
lot
of
clever
things.
So
when
you
clone
this
repository
and
then
run
make
what
it
does
is
it
pulls
in
a
lot
of
other
repositories,
and
so
what
we've
done
is
we've
said:
okay,
this
HDL
reference
design
from
ADI
for
our
hardware
for
the
development
system.
C
And
so
this
repository
is
pretty
cool
because
it's
two
sub
modules,
one
from
Analog,
Devices
and
one
from
a
contributor
and
then
so
Angel
is
like.
Okay,
we'll
need
to
integrate
all
of
this
work
for
for
a
device.
You
know
we
have
in
the
lab,
so
what
we
have
in
the
lab,
what
on
show
has
where
he's
located
and
what
we
have
at
remote
lab,
West
and
I?
Don't
think
this
exact
Hardware
exists
at
remote,
lab
South
James,
so
so
you
have
the
actual.
C
You
have
an
ultra
scale,
Plus
board
and
not
the
and
not
this
particular
one.
But
the
things
that
we're
dealing
with
here
are
things
that
you're
going
to
have
to
deal
with
there
when
you
get
it
up
and
running.
So
it's
it's
still
still
relevant.
So
what
we
have
is
a
zc706
board
from
from
side
links,
so
7000
series
fpga
and
a
really
cool
software,
a
system
on
chip
from
from
Analog
Devices,
the
9371
and
the
board.
The
name
of
the
board
is
the
adrb
9371.
C
So
when
we
keep
saying
that,
that's
what
we're
talking
about
and
these
two
boards
fit
together
with
this
a
huge
connector,
you
know
so
you
get
it
together
and
then
you
put
it
on
the
air
and
so
together
it's
an
fpga
and
a
rfic
system
on
a
chip
and
all
sorts
of
other
circuits.
There's
just
crazy
amount
of
components
here
that
we're
talking
about
and
once
you
kind
of
glom
it
together.
You
can
Target
this
and
make
a
radio.
C
So
what
I
can
do
is
share
the
screen.
This
would
be,
of
course,
easier
in
person,
but
I'm
going
to
go
ahead
and
share
the
screen
for
the
tackle
script.
So
TCL
stands
for
something
I
knew
this
yesterday,
but
tackle
is
a
sort
of
a
language.
So
it's
a
scripting
language
that
is
used
all
over
and
the
tackle
script
is
in
question
is
what
we
are
using
in
order
to
to
when
you
run
the
make
file.
C
Now
in
this
project,
then
you
can
see
that
that
really
amazing
a
system
block
diagram
that
we've
shown
from
time
to
time.
So
you
have
a
system
block
diagram
and
you
have
a
vivato
project
and
you
can
then
send
you
can
do
synthesis
implementation.
You
can
produce
a
bit
file
in
the
bit.
File
is
what's
really
important
for
for
programming,
pedal
Linux
to
get
the
the
general
purpose
processor
on
our
devs
Dev
station
up
and
running
and
to
make
sure
the
fpga
has
some
sanity.
So
this
is
lots
of
moving
parts.
C
We
have
all
this
documented.
Oh
thank
you!
It's
originally
tool
command
language,
but
now
it's
just
tackle
TCL,
okay,
so
tool
command.
Language
is
pretty
pretty
clear.
You
know
this
is
a
scripting
language
to
order
your
tools
around,
and
so
the
particular
file
in
question
has
already
been
modified
by
wonderful
people
like
Everest,
who
added
the
9361
on
the
Pluto.
C
All
the
code
required
to
get
this
to
work
on
the
Pluto,
and
then
we've
modified
it
several
times
to
to
automatically
integrate
our
encoder
into
this
reference
design
so
that
we
could
start
working
with
an
actual
hardware
and
get
things
working
over
the
air,
which
is
what
we
value
the
most
like.
We
need
it
to
work
over
the
air
to
show
that
we
know
what
we're
doing
and
to
move
on
to
the
next
step.
C
C
There
is
a
departure
in
the
way
that
the
data
is
sent
to
the
actual
transmitter
and
the
interface
in
question
is
it
went
from
a
much
more
clunky
old-fashioned
way
of
doing
it
to
something
called
justd
204b
and
that
I
think
might
be
the
problem
that
that
we've
identified
over
the
past
a
couple
of
weeks,
especially
and
it
probably
cropped
up
earlier.
So
when
we
talk
about
DAC,
fifos
and
encoders
and
dma
access,
I
was
assuming
that
that's
where
the
control
is
like.
We
control
our
entire
transceiver
from
from
that
perspective.
C
Okay,
so
this
turns
out
to
not
be
really
the
case
and
that
the
judge,
D
204b
interface
is
really
that
that
actually
is
super
important,
so
actually
knowing
how
the
lanes
and
and
all
of
this
works
is
probably
something
that
we
should
at
least
double
check.
And
that's
my
goal
for
today
is
to
look
at
our
tackle
script
and
figure
out
exactly
how
it's
setting
things
up
so
when
I
saw
I
looked
at
it
and
I'm
like
okay.
Well,
it's
an
expression
that
sets
up
the
bust
widths
for
the
encoder.
C
C
Who
knows
what
and
we're
figuring
out
what
to
do
there,
which
is
super
fun
and
and
a
big
Challenge
and
we're,
but
we're
getting
like
here
is
the
base
band
frames
for
the
down
link,
so
baseband
frames
when
we
talk
about
base
frame
frames,
we're
talking
about
dvbs2
and
S2X
frames,
and
we
have
a
variety
of
ways
to
do
this.
Yes,
you
can
do
it
directly
from
gnu
radio.
C
You
can
create
baseband
frames
from
there
and
we
know
that
we
can,
because
we,
we
meaning
Paul,
wrote
a
python
script
to
or
a
python
notebook
that
creates
BB
frames
from
from
Impact
from
transport
stream,
and
it
turns
out
there
they
perform
exactly
the
same
pass
all
the
test.
So
we
have
at
least
two
ways
to
create
these
files
that
are
directly
sent
to
the
encoder,
so
our
encoder
or
downlink
encoder-
and
this
is
a
big
step
forward.
So
now
we
have
some
ownership
over
this.
C
We
don't
have
to
depend
on
gnu
radio,
it's
not
that
we
hate
gnu,
radio
or
think
that
it's
bad.
It's
just
that
here
you
go.
You
have
a
python
notebook
way
of
doing
it.
You
can
also
do
it
in
good
new
radio,
if
there's
a
third
way
to
do
it
that
somebody
listening
to
this
wants
to
contribute
party
on
really
you
know
multiple
ways
of
of
producing
this
data
stream
are
super
important.
C
Once
we
get
these
BB
frames,
the
thing
that
we
need
in
our
system
is
that
all
you
need
to
do
is
have
a
word.
One
word
One
32-bit
word
that
tells
us
what
the
frame
type
and
the
the
mod
the
modulation
and
and
the
the
the
code
radar
okay.
So
so
those
that's
a
configuration
word
that
really
kind
of
like
sets
the
stage,
so
this
particular
frame.
This
baseband
frame
needs
to
be
transmitted
with
these
particular
aspects
in
in
DBS,
too,
and
also
S2X.
C
Although
we
haven't
added
all
of
that
and
that's
where
we
kind
of
tripped
over
our
own
feed-
and
it
just
doesn't
work
on
this
larger
fpga
system,
the
zc706,
but
it
does
work
on
the
Pluto,
so
the
big
difference
is
jsd.
204B
interface
is
used
on
this
on
the
on
the
zc706.
It's
not
used
on
the
Pluto,
it
uses
an
older
method
and
also
we
have
a
signal
that
does
not
exist
in
the
Pluto
working
code.
C
So
the
working
implementation
on
the
Pluto
doesn't
use
the
dma
transfer
request
line,
and
this
is
a
signal
that
goes
High
when
you
have
the
start
of
a
transfer,
axi
axi
transfer
and
this
particular
signal
is
actually
consumed
and
is
part
of
the
logic
of
the
DAC
fifo
it
for
the
9371
design
and
so
I
think
that
that's
something
that
we
need
to
take
care
of
and
I'm
not
sure
exactly
how
to
do
that
yet.
But
it
may
just
simply
be
that
we
need
to
pass
on
like
the
valid
signal
and
axi.
C
The
valid
signal
means:
hey,
I'm,
a
I'm,
a
transmitting
block
of
code
or
block
of
dot,
a
logic
and
everything.
That's
now
on
the
bus
is
valid.
That's
that's
actual
valid
Data
before
that.
If
I
say
that
it's
not
valid
I'm,
not
ready
yet
because
in
axi,
the
the
all
the
handshaking
and
the
control
for
all
these
buses
between
all
of
these
different
blocks,
axi
can
tell
you
yeah.
My
address
might
be
valid
and
everything
else
is
valid,
but
wait
on
the
data
not
yet
done,
processing
it.
C
C
Okay,
so
I
I
hope
that
I've
done
a
good
job
of
framing
the
past,
maybe
several
months
worth
of
work
and
I'm
going
to
stop
here
and
and
let
let
other
people
talk
about
about
what
we've
looked
at
and
accomplished,
because
I
haven't
even
touched
on
the
registers,
we
have
a
script
that
returns
registers
and
I'm,
not
the
main
one.
That's
worked
with
those
results,
I
think
it's
Paul
and
then
anshul
has
a
tremendous
amount
of
work
under
the
belt
here.
C
So
so
I'm
going
to
stop
and
and
turn
to
turn
the
floor
over
to
everyone
else
to
to
make
comments
on
this
and
then,
after
everybody
has
said
everything
they
need
to
say.
Then
I'd
like
to
go
ahead
and
move
to
the
tuckle
script
and
look
at
the
expression
for
the
bus
widths,
because
that
may
be
tripping
us
up.
That's
what
swato
and
and
also
Everest
I've
recommended
that
we
look
at
so
I'm
going
to
mute.
F
F
F
C
C
It's
the
same,
one
I
think
it
it.
Actually
it
turned
out.
It
was
in
the
the
the
image
from
last
week's
meeting
about
dma.
Well,
on
one
side,
it's
called
D
I
think
it's
called
dma
X
for
x,
f,
e
r
request
and
then
m
a
x.
I
transfer
something
on
the
DAC
fifo,
so
originally
in
the
in
the
reference
design,
the
the
dma
and
the
DAC
fifo
are
connected
directly
like
there's
nothing
in
between,
so
once
we
get
in
between
them.
Any
extra
signals.
It's
not.
C
So
it's
not
just
all
the
standard
axi
signals.
There's
this
one
extra
signal
and
it
it
goes
high
at
the
beginning
of
a
dma
transfer,
and
so
since
we're
not
giving
it
to
the
DAC
fifo
I
was
like
oh,
so
it's
never
and
it's
used
to
reset
the
DAC
5-0.
So
it's
just
sitting
there
waiting
for
a
reset
signal,
and
maybe
that's
why
we're
getting
all
these
timeouts.
C
D
C
You
know
I've
got
like
a
one
quarter
rate
like
okay,
one
bit
of
data
and
I
gotta
I
gotta
come
up
with
three
other.
You
know
priority
bits,
basically
yeah,
so
you
can
see
where
the
the
delay
is
variable
versus
a
low
code
rate.
That's
nearly
one!
You
know
you
might
beat
it
right
and
we
see
this
I
think
with
some
of
the
experiments
we've
done,
the
encoder
will
work,
fine,
it
actually
the
transmit
and
receive
it
it
clocks
along,
and
it
doesn't
have
that
weird
timeout
from
the.
A
C
So
my
I
guess
that's
that's!
So
that's
where
I!
That's.
Why
I
think
that
that
we
have
an
issue
with
this
particular
signal,
because
it's
still
hooked
up
and
it's
still
in
the
The
Tackle
so
and
okay.
So
now
we're
back
to
the
tackle
script.
This
tackle
script
actually
runs
the
show.
My
misunderstanding
was
that
the
block
diagram
that
you
get,
that
awesome
block
diagram
and
you
drag
and
you
drop,
and
you
hook
things
up
and
and
everything,
oh
dear.
So
none
of
that
matters.
C
You
can
change
things
in
the
block
diagram,
but
the
tackle
script
once
you.
If
you
hit,
make
or
make
clean
or
you
re,
it
will
overwrite
everything
unless
you
change
it
in
the
tackle
script
and
I
didn't
really
appreciate
that
until
I
guess
a
couple
of
months
ago
and
now
I've
been
reminded
that
yeah
you
you
need,
you
need
to
actually
programmatically
like
you
need
to
specifically
say
in
the
tuckle
script,
how
things
are
hooked
up
and
that
signal
is
still
hooked
up
in
the
tuckle
script,
and
so
we
have
to.
C
If
we're,
we
have
a
timing
problem
because
we've
inserted
a
huge
pipeline
delay
with
the
encoder
it's
consumed,
and
then
the
Pluto
works.
Fine.
This
the
signal
is
not
hooked
up
in
Pluto
at
all.
It's
disconnected
so
I
was
like
well,
we
should
disconnect
it
too,
but
the
Pluto
design
doesn't
have
a
DAC
fifo,
but
we
do.
We
have
a
DAC
fifo
and
it
needs
the
signal
in
order
to
reset
it
properly.
C
So
we
either
go
change
the
code
from
Analog
Devices,
which
sounds
dangerous
and
risky,
or
we
give
it
what
it
wants,
and
that
may
mean
just
tying
it
high.
You
know
like
we're
always
transmitting,
because
we
are
always
transmitting
because
we're
dvbs
too
so
I
mean
there's,
there's
kind
of
janky
ways
to
fix
it
like
we
can
just
tie
it
high
or
whatever
it
takes,
but
I
think
we
should
probably
look
at
like
actually
giving
it
what
it
wants
like
delivering.
C
A
signal
like
I
have
a
transfer
like
okay,
it's
not
a
direct
from
dma
transfer
anymore.
The
signal
this
particular
signal
goes
High
when
there's
a
yes
I'm
dma,
but
this
needs
to
come
from
the
output
of
the
encoder.
Somehow,
and
it's
like
the
encoder
is
now
ready
to
deliver
the
what
essentially
used
to
be
transfer
for
memory
and
now
is
transfer
from
it's
a
transfer
from
memory.
That's
been
modified
now
we're
giving
it
to
you
is
that
is
I'm,
not
sure.
If
that's
clear.
C
Does
that
make
any
sense?
What
I've
said?
Yes,
okay,
good
yeah,
so
I'm
not
sure
what
to
do
about
it,
because
we
could
and
I
really
don't
want
to
change
the
encoder,
especially
because
it
works
like
it
works
in
a
general
case
like
you
get
data
from
memory
and
it
produces
I's
and
q's,
and
at
that
point
we.
D
C
A
E
C
Let's
see
Paul
mentioned
the
Jupiter
notebook
referred
to
the
to
okay.
He
puts
a
Lincoln
chat
for
the
conversion,
notebook
for
going
from
Impact
transport
stream
to
BB
frames
and
he's
now
tagged
it
so
so
tagged
with
mode
words.
Okay,
so
they
put
the
link
the
direct
link
into
chat
and
and
Sasha
says
hello
and
has
audio
challenges.
Today,
hello,
Sasha,
I,
see
you
and
then
I
also
see
Richard
Hamby,
Rick,
Hambly
hi,
so
I
just
wanted
to
acknowledge
everybody
welcome
them
to
the
meeting
today.
C
F
C
C
Okay,
yeah
yeah.
The
issue
is
that
we're
getting
timeouts
yeah
for
on
when
we're
trying
to
use
the
encoder
on
this
particular
honored
honor
development
station,
okay,
so
yeah,
of
course
we
can
I,
think
we'll
we'll
this
will
take
at
least
another
week
to
fix
so
we're
not
gonna
We're
Not
Gonna
fix
it
today.
What
I
wanted
to
show
is
what
I
wanted
to
do
was
get
a
number
of
eyeballs
on
the
tuckle
script
today,
to
where
we
can
figure
out
what
the
expression
is
really
telling
us.
C
Yes,
we
will
continue
to
talk
about
this
and
and
let
you
catch
up
over
the
next
week,
so
so
no
you're
I'm
not
expecting
I,
don't
if
we
solve
it
today,
that'd
be
great.
If
somebody
sees
something
obvious
so
then
I
think
the
next
thing
I
would
like
to
do
is
just
show
where
this
expression
comes
from.
So
this
is
setting
the
bus
widths.
I
thought
was
just
oh
yeah.
C
It
was
pulling
64
bits
out
at
a
time
and
giving
128
to
the
next
block,
which
was
the
DAC
fifo
right.
I.
Think
that's
right:
okay,
so
64.,
because
we
have
64-bit
wide
memory,
okay,
sure
so
you're
taking
out
64
bits
at
a
time
and
then
you're
giving
128
bits
at
a
time
to
the
DAC
fipo.
The
DAC
fifo
consumes
the
128
bits
and
then
gives
120
bits.
C
We
want
on
the
Spectrum
analyzer
until
we
nail
this.
So
yes,
the
answer
to
your
question.
Can
we
put
this
off
of
week?
Is
yes,
but
let's
look
at
the
code
and
see
if
we
can
understand
the
tuckle
script
a
little
bit
better,
because
I
just
thought
that
I
thought
this
was
much
more
flexible
than
it
is,
and
just
changing
just
walking
in
there
and
going
commenting
out
this
expression
and
putting
in
the
number
32
and
going
woohoo
I
did
it
was
not
not
it's
okay!
C
D
C
So
if
we
can,
if
we
can
at
least
get
that
under
our
fingers
so
to
speak,
then
I
think
that
there
are
tests
in
remote.
Labs
can
actually
make
more
sense
like
we
know
what
we're
trying
to
feed
it.
We
thought
we
knew
what
we
were
trying
to
feed
it,
but
we
don't
okay,
so
I
will
look
at
my
desktop
and
I'm
going
to
make
it
to
where
anybody
can
share
if
they
want
to.
C
C
C
So
the
Jazz
D
stuff
actually
is
at
the
top
of
the
file.
This
tuckle
script
is
the
adrb
9371
board
file,
and
this
gets
called
in
the
make
process
when
we
make
our
vivato
stuff.
Our
vivato
project
is
where
the
bit
file
and
the
xsa,
which
is
a
xilinx
system
archive
file,
comes
from,
and
the
xilinx
system
archive
file
goes
directly
into
making
the
petal
Linux
build,
and
so
does
the
bit
file
with
bitfile
goes
to
the
fpga
directly.
The
xsa
handles
everything
else.
C
So
these
files
and
this
this
particular
file
are
kind
of
important
to
have
all
this
stuff
work
and
you
know
any
complicated
system
we
have.
Yes,
we
have
an
fpga
and,
yes,
we
have
a
a
awesome,
zinc,
processor,
and
so
that's
this
file
is
actually
in
charge
of
a
lot
of
stuff.
So
we
have
things
like
max
number
of
lanes
and
we
have
Max
received
number
of
lanes
and
the
OS
here
means
the
observational
receiver.
C
So
we
have
these
really
cool
things
in
the
9371
they're
observational
receivers
that
can
look
for
stuff
and
then
inform
our
system
of
hey.
You
have
a
signal
over
here
that
you
need
to
pay
attention
to.
We
haven't
really
exploited
that
yet
these
these
letters
here
for
jazzdmls
those
are
important,
I
know
from
from
reading
in
the
past,
so
you
can
see
that
this
stuff
is
set
up.
C
We
have
parameter
descriptions
and
we
set
the
number
of
lanes
for
jesd
interface,
and
you
know
I
never
really
paid
a
lot
of
attention
to
this,
but
we
have
the
samples
per
Channel
and
it's
an
expression.
So
we
have
the
number
of
lanes
times.
32
bits
number
of
converters.
We
have
another
l
and
an
m
and
an
n-
and
this
stuff
I
think,
is
the
key
to
what
we're
dealing
with
okay.
So
where
did
I
screw
it
up?
C
We
know
that
our
encoders
that
are
two
bits
wide
and
we
know
that
we
were
trying
to
insert
ourselves
into
a
into
a
128
bit
wide
bus,
and
it
looks
like
that
you
can
just
fix
everything
by
just
modifying
the
the
bus
widths
at
the
encoder,
and
that
is
not.
That
does
not
appear
to
be
the
case
here
is
where
we
actually
Source
our
dvb
modulator.
So
you
can
see
that
we
have
our
dvbs2
files
tackle
script
or
encoder
wrapper
vhd.
C
This
is
what
we've
been
documenting
in
the
draw
I
o
this
is
where
it
actually
happens,
so
we
Source
the
adding
the
files.
This
chuckle
script,
in
particular
figures
out
where
stuff
is
in
in
our
repo,
that
we're
adding
to
this
reference
design
and
here
is
the
resulting
wrapper,
and
then
we
set
the
instance
and
we
start
setting
properties.
C
What
I'm
looking
for
is
the
bus
width.
This
is
with
the
data
with
for
us,
so
you
can
see
we're
clearly
declaring
ourselves
as
a
32-bit
wide
thing
and
they're
32
bits.
So
16
bits
is
I
and
16
bits
of
Q.
Well,
actually,
the
input
data
width
is
not
in
Q
the
input
data
width
is
the
BB
Frame
data,
but
the
output
is
a
32-bit
wide
word.
That's
I
and
Q,
so
we're
just
putting
out
one
I
and
Q
at
a
time,
and
we
have
all
of
this
neat
stuff.
C
So
all
this
ADI
connect
stuff
where
we
go
from
the
transmit
DM
dma
to
the
encoder
and
from
the
DAC
fifo
to
the
encoder.
This
is
how
we
insert
ourselves
into
the
design,
so
the
rest
of
this
technical
script
is
all
of
the
other
stuff
that
comes
from
the
reference
Design
This
here.
This
is
how
we
insert
ourselves
into
the
design
and
it's
all
working
as
intended.
C
C
C
Then
that
expression
consumes
things
like
the
transmit
samples
per
Channel.
Okay,
so
there
it
is
the
something
here
it
is
okay.
So
when
we
set
the
DAC
dma
data
width
here,
this
says
DAC
dma
data
with
this
is
128
bits,
and
this
is
actually
what's
coming
from
the
dma.
This
exact
expression
is
used
in
several
places
and
what
I
did
is
I
commented
this
out
and
just
put
into
32.,
so
you
can
see
it
has
the
transmit
sample
width.
This
is
transmit
number
of
converters
and
it
has
a
transmit
samples
per
Channel.
Okay.
C
So
all
three
of
these
things
are
important.
These
all
come
directly
from
the
Jazzy
204b
interface
and
that's
what
I
claim
that
we
need
to
to
be
able
to
master,
and
we
need
to
be
able
to
understand
exactly
what
we're
interfacing
with
in
order
for
the
encoder
to
work
in
a
with
a
9371.
We
know
that
the
encoder
works
with
the
9360
one,
a
much
I'm,
gonna
I'm,
not
going
to
say
simpler
design,
but
but
one
that
has
a
a
not
so
maneuverable
and
not
so
amazing
interface.
Jesse
204b
is
really
amazing.
C
We
really
should
use
it.
We
should
not
back
off
of
this.
We
should
keep
attacking
it
and
we
should
Master
it
and
then
use
it
and
then
produce
this
design
as
you
keep
going,
and
we
should
also
publish
and
and
and
use
and
publicize
the
working
design
on
the
Pluto,
because
the
work
that
ever
East
and
onshore
and
others
have
done
and
that
Andre
is
enabled
with
this
encoder-
is
really
cool
for
the
for
the
Pluto
and
for
any
design
using
a
9361,
the
the
more
modern
interface,
the
jsd
204b
interface.
C
It
is
great,
but
we're
dealing
with
a
more
complexity,
and
so
this
particular
statement
right
here
the
one
on
your
screen
is
the
one
that
I
changed
and
I
think
that
derailed
everything.
So
over
the
next
week,
let's
go
on
slack
and
let
us
figure
it
out
either
we
need
to
back
off
and
we
need
to
say:
okay,
we're
going
to
go
down
to
32-bit
at
a
time
encoder
or
we
need
to
take
the
encoder
and
and
step
up
to
128
8
Bits
wide,
which
is
what
the
jsd
204b
interface
is
expecting.
D
C
It's
a
good
question,
Sasha
says:
do
we
have
a
working
example
with
just
d2frb,
even
if
it's
not
with
our
encoder
there's
just
something
add
this
thing.
Yes,
we
do
and
we
got
really
comfortable
with
it.
The
reference
design
that
we're
using
works
great
without
our
encoder
in
it
and
it
and
we
sent
lots
of
sine
waves.
C
In
fact,
the
ADI
does
a
great
job
of
shipping,
a
working
example,
a
hello
world
that
is
two
sine
waves,
so
you
send
a
two-tone
example
and
to
their
credit,
they've
actually,
given
us
I
think
everything
that
we
need
in
order
to
figure
out
what
we're
doing
it's,
just
maybe
it's
aimed
for
people
that
do
this
every
day
and
and
maybe
not
folks
that
are
coming
at
it
from
our
particular
direction,
which
is
a
different
one.
So,
yes,
we
have
those
working
examples
and
lots
of
videos
and
demos
of
us
of
us
using
it.
C
B
C
But,
unlike
other
designs,
that
I've
worked
on
the
interface
way
down
the
pipeline,
actually
propagates
back,
so
the
requirements
actually
propagate
all
the
way
back
to
to
where
we
are
and
what
I
assumed
was
flexibility
in
terms
of
of
fifos
and
stuff
and
buffers.
It's
it's
a
flexibility
in
with
respect
to
timing,
but
it's
not
a
flexibility
with
respect
to
the
format
of
the
of
the
IQs
that
we're
delivering
and
Sasha
asks.
C
Can
we
try
doing
something
simpler
with
just
putting
something
in
memory
without
the
dbb,
encoder
and
figuring
out
how
to
do
dma
and
yeah
we've
done
that?
That's
what
gave
us
that's
what
gave
us
the
confidence
to
drop
the
encoder
in
so
we
we
thought
we
knew
what
we
were
doing,
but
they've
made
it
so
easy
with
the
hello
world
and
the
the
stuff
we
have.
C
C
C
What
are
you
trying
to
and
they're
trying
to
show
off
their
the
bandwidth
and
the
capability
of
this
particular
system
is,
is
quite
remarkable
and
I
think
that
they're,
like
yeah
sure
you
know
we're
we're
gonna
fully
ventilate,
this
eight
cylinder
hot
rod
and
we're
going
to
show
you
what
what
some
good
valve
work
will
do
for
you.
You
know
and
you're
like
wait.
I
just
wanted
a
VW
I
just
wanted
a
32
bits
at
a
time,
and
it's
a
misunderstanding
on
our
part.
C
I
think
about
the
just
d204b
interface
is
probably
in
the
mix
here
and
also
not
understanding
that
when
you
insert
logic,
you
really
do
need
to
make
sure
that
every
that
there
that
there
are
signals
that
you're
taking
care
of
and
we're
not
taking
care
of
a
signal,
in
particular
that's
consumed
by
the
fifo
before
the
the
adak
50
is
what
they
call
it.
So.
C
In
fact,
going
back
to
those
examples
and
then
working
with
those
examples
with
their
example
code
and
their
this,
the
stream
that
we're
working
with
the
the
processor
side
code
that
we're
working
with
is
actually
one
of
their
examples.
That's
based
on
one
of
their
examples,
so
I
think
that
dropping
back
to
just
the
reference
design
at
this
point
and
then
going
in
and
manipulating
the
bus
widths
and
proving
that
we
can
send
a
sine
wave.
C
It's
a
very
simple
signals
and
fully
controlling
the
interface
closer
to
the
transmitter,
so
to
speak,
would
be
actually
very
valuable.
At
least
it
would
be
for
me,
so
you
know
not
being
as
brilliant
as
the
people
that
contribute
to
this
project.
It
would
really
help
me
figure
it
out.
So
I
think
that's
what
we'll
do
so
we
will
take
your
suggestion.
C
D
C
C
So
much
Sasha
for
for
pitching
in
here
and
I
think
that
we
have
some
other
people
that
might
be
interested
in
helping
I'll
try
to
reach
out
again
to
Dr
Bridges,
who
helped
put
together
the
architecture
in
the
first
place
back
in
2020
and
then
see
if
he
or
any
of
his
students
want
to
want
to
help
out
here
on
that
and
anybody
else
is
listening.
If
you're
interested
in
space
10
gigahertz
down
links
for
on
the
amateur
Bands,
then
we're
trying
to
build
some
prototypes
and
get
some
things
rolling.
C
A
A
G
He
worked
for
Hewlett-Packard
here
in
Colorado
Springs
among
other
places
and
has
a
140
foot
Tower
with
almost
nothing
on
it
at
the
moment.
All
his
antennas
are
in
the
in
design
and
short
masks
at
the
base
of
the
tower.
They've,
never
finished
these
designs
and
get
some
up
on
the
power,
but
his
designs
are
most
intriguing
and
I
mentioned
this
project
to
him.
G
I've
said:
wouldn't
it
be
nice
if
they
were
like
more
than
one
person
in
Colorado
Springs
interested
in
this
project,
so
that
we
could
like
maybe
even
put
up
and
transplant
a
couple
of
transpenders
and
talk
to
each
other,
and
he
thought
maybe
he
would
be
very
interested,
which
would
give
me
the
second
person.
Yes,.
G
G
He
he
got
upset
because
he
had
brought
in
Orion
2800
rotor
and
put
it
up
with
his
40
meter
beam
at
140
feet.
Now
you
might
ask
what
does
that
have
to
do
with
this
project?
Well,
he
made
the
mistake
that
I
did
not
pay,
but
I
did
almost
the
same
thing
in
Maryland,
I
bought
a
different
brand
of
rotor
controller.
The
green
heron
I
did
not
buy
the
controller
from
Orion,
because
I
knew.
That
was
not
a
good
idea,
but
he
bled
the
Orion
controller.
Sure
enough
had
failed.
G
A
A
G
G
And
put
it
in
a
box
and
program
the
programming,
it
is
the
important
part,
because
that
says
he
and
he
and
he
and
I
had
this
conversation.
He
thinks
like
Hardware
person,
not
like
a
software
person
suffering
people
often
have
a
hard
time
grasping
the
concepts
of
of
the
fabric
and
that
and
he
did
he
he
just
just-
and
he
didn't
like
go-
do
this
to
sell
it.
He
just
did
it
because
he
didn't
want
to
buy
another
controller
yeah.
C
G
Yeah
I
he
had
asked
me
for
a
a
lot
of
information
on
a
lot
of
subjects
which
I
then
spent
half
a
day,
compiling
and
emailing
an
email
to
him
with
links
to
all
the
different
things
like.
Why
should
he
saved
the
50-foot
space
on
his
tower
for
a
six
meter
beam
instead
of
his
tri-bander
I
said
no
you've
got
to
wait.
You
got
to
put
a
six
meter
beam
there
and
I
gave
him
a
link
to
Frank
Donovan's
presentation
on
sex
reader
and
punished.
G
I
don't
mean
to
sound
like
he's
an
odd
guy,
he's
a
very
normal
guy
totally.
Never
he
did
not
and
would
not
say
any
of
the
stuff.
He
said
to
me
at
the
meetings
he
he
had
come
to
one
of
our
Thursday
morning,
breakfasts.
In
other
words
he
doesn't,
he
doesn't
brag
about
what
he
does.
He
just
does
it
and
he
invented
some
things
that
in
past
history,
you
might,
you
might
have
run
across
like
the
various
buses
or
hard
drives,
including
the
50
and
110
parallel
buses
and
all
that
kind
of
stuff.
So.
G
C
C
G
I
was
out
for
a
drive
the
other
day,
we're
exploring
Colorado
we're
trying
to
find
places
because
moving
out
here,
we
want
to
know
where
it
is.
We
move
to
and
come
on
this
back
road,
nothing
Road
between
my
house
and
my
daughter's
house,
and
we
didn't
want
to
take
the
main
roads.
We
wanted
to
see
some
of
the
scenery
and
Grandma
all
of
a
sudden
me.
You
know
guard
Gates
and
big
red
lights
and
I
thought
wait.
A
minute.
G
C
C
C
C
No
no
wow!
Well,
this
is
really
cool,
I
hope,
I,
hope
this
continues
and
you
know
what,
if,
if
any
of
what
we
do
is
of
interest
to
anybody,
then
they're
welcome,
really
and
we'll
just
keep
we'll
keep
kicking
it
and
keep
working
on
what
we're
working
on
and
and
make
it
accessible
and
easy
to
easy
to
join.
That's
that's
what
we
do.
A
C
G
That
whole
business
of
vocoders,
when
I
was
actively
involved
in
amstat
and
I,
was
I,
was
being
pursued
over
these
vote.
Coders
trying
to
get
amsac
to
buy
in
and
I
wasn't
very
interested
because
they're
they're
seemed
to
be
much
more
interested
in
how
good
could
you
get
a
vocoder
to
work
in
a
very
narrow
bandwidth
and
I
said
msac's
not
interested
in
two
kilohertz
channels
and
now
I
see
from
what
you
said
that
whole
Evolution
took
place
anyway,
which,
of
course
it
had
to
for
it
for
this
satellite
project?
B
G
C
Thank
you.
We
appreciate
it
all
right,
we'll
do
it
again
next
week
and
until
then
we'll
be
on
slack
figuring
out
all
sorts
of
stuff
and
helping
people
to
learn.
So,
if
you're
watching
this
for
the
first
time
or
if
you're,
watching
this
and
want
to
get
involved,
then
just
go
to
our
website.
It's
open
research,
dot,
Institute,
open
research,
one
word
dot,
Institute
and
then
click
getting
started
and
join
up,
reach
out
and
start
the
process
of
of
learning
how
to
Grapple
with
all
this
stuff.
C
You
do
not
have
to
be
an
expert
to
join.
You
just
have
to
be
willing
to
become
a
little
more
of
one
along
the
way
and,
as
you
can
see,
there's
all
sorts
of
things
going
on
and
if
you
have
a
project
and
you
need
a
home
and
a
little
bit
of
just
a
little
bit
of
logistics,
support
or
a
little
boost
a
little
bit
of
formal
structure.
Then
then
that's
what
we're
here
for
all
right
see.