►
From YouTube: ORI FPGA and Remote Labs Meetup 20 September 2022
Description
Jump Links:
0:30 Reports Begin
2:30 f4pga possible use in Remote Lab South and open source FPGA tools
5:40 Versatune and Downlink transmitter updates
7:30 Versatune as Ground Station if DVB-S was used
8:40 Ham Expo Roundup
11:50 Simple FSK Receiver update. Original repo here: https://github.com/mcupro/simple-FSK
15:38 HEO proposal at JAMSAT member meeting and upcoming JAMSAT Journal
18:38 Need more people!
20:37 Conversation Rick Hambly and Open Source tools possibilities and directions. MATLAB, Octave, Python, and more.
A
Greetings:
everyone
and
welcome
to
today's
stand-up
meeting
for
fpga
and
remote
Labs
at
open,
Research
Institute.
It
is
the
20th
of
September
if
you
can
believe
it
of
2022,
and
we
are
here
to
talk
about
what
we
did
over
the
past
week,
what
we're
doing
over
the
next
week
if
we
have
any
roadblocks
and
if
we
need
any
resources
and
hello
everybody
all
right.
Let's,
let's
go
around
and
and
see,
what's
up
all
right,
hey
Paul!
You
have
the
floor.
B
There
well,
we
wrapped
up
him
Expo
this
last
weekend
and
that's
consumed
a
fair
amount
of
horsepower
over
the
last
couple
of
weeks.
For
me
not
much
going
on
the
remote
lab,
I,
don't
have
any
immediate
roadblocks,
that's
about
about.
A
C
A
All
right,
thank
you,
so
much
all
right,
James
Let's.
Let's
hear
how
it's
going.
B
Not
too
much
to
report
here
either
we're
just
flipping
on
we're
continuing
more
work
on
getting
the
main
building
up
and
yeah.
That's
pretty
much
it!
Nothing
otherwise
made
to
report
everything's
been
going
well
here.
A
Yeah
he
says
that
nothing
is
going
on
or
very
little
is
going
on,
but
I'd
like
to
to
to
stick
up
for
that.
There's
a
lot
of
physical
plant
work
going
on
at
remote,
lab
South.
So
thank
you
so
much
for
everything
that
you've
been
doing
and
I've
been
I've,
been
talking
to
Keith
about
delivery
of
the
lab
supplies
and
what's
needed
in
terms
of
support.
A
A
So
this
lab
is
in
is
on
Arkansas,
which
is
actually
pretty
close
to
everything.
If
you
look
at
it
on
the
map,
what
we're
what
we've
learned
about
is
you
know
some
some
additional
ways
to
to
get
open
sourced,
fpga
design
done.
A
Tool
chains-
and
these
are
these-
are
things
that
I
I
should
probably
say
are-
are
not
yet
up
to
the
same,
maybe
level
of
performance
or
or
not
able
to
address
the
the
really
large
fpgas.
A
This
has
been
a
a
thing:
that's
gone
on
in
open
source,
fpga
design
for
many
years,
and
I'll
have
to
go
back
and
see
when,
when
Matt
ettis
at
Edis
research
addressed
this
himself,
someone
asked
him
in
public
if
he
would
why
you
know
why
didn't
Edis
research
use
open
source
tools
and
and
open
source
methodologies,
and
he
said
that
you
know
at
the
time
they
were
well
into
the
third
generation
of
usrps
and
that
the
open
source
fpgas
were
not
yet
up
to
the
usrp1
and
that
as
soon
as
that
happened
that
there
was
some
way
for
him
to
to
pull
it
into
to
the
collection
of
of
commercial
products.
A
He
would.
This
is
somewhat
of
an
unfair
thing
to
ask
open
source
Community
people
to
do
because
we
don't
get
a
lot
of
help
at
all
from
you
know
in
in
to
integrate,
and
obviously
we
wouldn't
because
this
is
a
com-
competition
a
competitive
deal,
but
we
we
have
a
rapidly
changing
landscape
in
in
fpgas
and
anything
that
we
can
help
open
source
work
and
fpga
design
move
forward.
A
We
should
so
over
the
next
week,
we'll
be
talking
a
lot
more
about
this
particular
tool
approach
and
there
might
be
a
way
to
provide
some
diversity
within
open,
Research,
Institute,
remote
Labs,
so
where
you
can
use
traditional
vivato
approach,
which
has
been
very
effective
for
us
and
is
industry
widely
supported
in
Industry
with
xilinx
parts
and
then
also
have
a
open
source
tools.
Option
as
well.
A
We've
gotten
a
steady,
steady
flow
of
comments
from
the
community
that
they
really
like
for
us
to
to
also
address
the
tools
side
of
the
house
and
not
just
the
product,
and
our
our
approach
has
generally
been
pragmatic.
We
use
whatever
the
right
tool
for
the
job
is
to
get
open
source
designs
out
there
into
the
public
and
we're
Unapologetic
about
it,
but
helping
the
tools
side.
A
Thank
you
so
much
James
and
and
Keith,
and
everybody
in
Arkansas
for
all
that
you're
doing
I
know
that
it's
been
challenging
and
at
the
weather
has
also
been
a
challenge
that
isn't
something
that
we
have
to
face
in
remote,
Labs
West
and
it's
less
of
something
that
is
a
challenge
for
remote
labs
in
the
UK
all
right
anshul.
You
have
the
floor.
B
Great
this
week,
I
made
progress
with
versatility
receiver.
Now
my
setup
is
ready
face
some
issues,
so
I
had
a
call
with
art
and
now
the
transmitter
part,
the
receiver
part
and
the
flow
of
stream.
Everything
is
working,
fine,
so
yeah
now
I
have
to
get
a
code.
I
have
to
get
code
from
Bob
and
compile
it
at
my
end
and
make
an
image
and
then
try
with
that
one
before
I
start
making
changes
into
it.
B
So
Bob
has
been
busy,
but
whenever
it
gets
time
he
will
provide
me
with
the
code
and
the
steps
for
doing
compilation
and
then
I
will
proceed
forward
on
encoder
side
I'm
trying
to
fix
the
issues
that
are
there
with
mqtt
control
and
basically
a
fixed
error
means
I'm,
trying
to
adapt
it
to
set
c706
rather
than
Pluto
board,
so
making.
A
B
No
I
think
earlier
last
week
when
I
gave
my
status
update,
I
was
confused
what
all
modules
or
binaries
baskets
need
to
be
executed
on
the
PS
part
and
what
all
need
to
be
executed
on
the
laptop,
so
I
think
the
Everest
chipped
in
and
he
provided
the
details.
So
it's
clear
now.
A
B
A
B
Yeah
right
absolutely
and
one
more
point:
I
want
to
add
it's
fpga
code
that
was
added
by
Charles,
it's
all
proprietary,
so
we
don't
have
access
to
it.
Vbs2
or
database
2X.
A
Okay,
yeah-
maybe
maybe
there's
an
opportunity
there,
we'll
we'll
talk
more
about
that
yep
all
right
thanks,
so
much
all
right.
So,
yes,
ham,
Expo,
a
large
amateur
radio
twice
a
year
show
happened
this
past
weekend
and
we
had
five
presentations
at
it.
We
had
three
project
exhibits.
Those
are
essentially
like
poster
sessions
at
a
at
a
academic
conference
and
they
were.
A
The
support
was
fantastic
for
that
you
had
a
q,
a
tab
on
your
browser,
so
you
could
answer
questions
that
people
had
at
the
that
left
at
the
poster
session
and
people
could
download
the
poster
as
a
PDF.
We
also
had
a
booth
with
lots
of
links
to
our
website
and
all
of
our
resources
and
our
YouTube
channel.
A
That's
a
really
fun
looking
booth
and
all
of
the
Q,
a
for
for
our
talks,
went,
went
pretty
darn.
Well,
the
the
response
was
constructive
and
positive.
So
out
of
all
the
shows
that
we've
gone
to
over
the
past
couple
of
years,
this
one
was
great.
This
one
was
good.
We
would
really
like
to
see
attendance
go
up
at
ham,
Expo
and
and
it
to
continue
so
so
we'll
we'll
be
we'll
be
sure
to
be
supporting
partner.
Moving
moving
forward.
A
All
of
those
recorded
presentations
will
be
available
for
the
next
month
for
the
next
month
on
the
platform
at
ham
Expo,
it
included
a
ribbit,
talk,
a
presentation
and
poster
from
the
Ribbit
team.
That's
UHF,
VHF
digital
Communications
without
any
extra
equipment
or
wires
just
through
an
Android
app
and
the
Android
app
plays,
plays
the
tones
of
SMS
over
any
HT.
A
So
we
intend
for
this
to
be
VHF
UHF
ham,
but
it
can
be
any
radio
that
has
a
microphone
can
then
be
turned
into
a
digital
Communications
device,
so
that
open
source
project
got
a
lot
of
traction
and
great
questions.
That
was
one
of
the
presentations
and
one
of
the
project.
Exhibits,
Paul
and
I
did
two
talks.
A
Each
Paul
did
opulent
voice
so
a
sort
of
a
explanation
and
the
background
of
of
all
the
the
ins
and
outs
of
digital
voice
codex
and
and
where
opulent
voices
new
and
exciting
for
very
high
bitrate
compared
to
the
other
Alternatives
and
then
also
did
authentication
and
authorization
for
amateur
satellites,
and
that
got
some
interesting
questions
and
very
technical
talk.
A
So
last
week
I
promised
my
I
was
hoping
that
I
would
actually
be
able
to
implement
the
verilog
FSK
demodulator
I
didn't
but
I
I
did
clean
up
the
drawings
and
do
some
documentations
of
that.
So
I'm
really
happy
to
be
able
to
share
that
with
you
all
today
and
I'll
I'll
put
it
up
on
the
screen
as
soon
as
I
can
find
it
there
we
go
okay,
so
this
is
from
the
let's
see:
yeah,
that's
a
good
place
to
start.
A
This
is
from
that
same
body
of
work,
the
the
the
open
source,
FSK
decoder,
demodulator
and
modulator
on
GitHub
that
I
talked
about
last
week,
and
so
what
I
did
is
kind
of
made
in
draw.
A
I
o
some
diagrams,
the
one
that
you
should
be
seeing
right
now
is
the
overall
top
block
the
fskd
modulator,
and
it
shows
that
there's
two
synchronizers
in
the
edge
detect
in
it-
and
this
is
showing
actually
what
the
edge
detect
does
with
a
correction,
to
a
mistake
that
I
had
last
week
where
I
didn't
have
the
the
clocks
lined
up
correctly
with
the
with
the
r0r1
R2
pause
and
neg.
So
now
this
is
I'm
com,
I'm,
more
confident
that
this
is
correct.
A
I
also
did
the
synchronizer
to
explain
a
little
bit
about
what
the
synchronizer
is
doing.
It's
just
to
get
the
guarantee
set
up
and
hold
time
for
for
the
limits
for
the
high
and
the
low,
which
is
the
zero
and
the
one
for
binary
FSK.
So
it
looks
like
this
design
is
set
up
to
have
adaptive
limits.
Comparisons,
for
you
know,
are
you
a
high
tone
or
a
low
tone?
A
That's
what
the
short
and
the
longer
are
aimed
for
so
not
necessarily
static,
and
here
is
actually
the
logic
from
the
demodulator,
and
so
you
can
see
this
orange
apologize
to
anybody.
That
has
challenges
with
with
color
blindness,
I'll
double
check
and
make
sure
that
these
are
good
colors
to
use.
A
But
you
can
see
the
orange
slant,
that's
the
that's
that
register
that
is
counting
up
and
it
just
Waits
until
it
gets
a
the
most
significant
bit
of
the
ADC
negative
going
and
then
it
makes
a
call
and
then
is
it
larger
than
the
upper
limit,
or
is
it
smaller
than
the
lower
limit?
You
can
see
left
and
right
two
examples
of
of
tones.
A
A
Our
development
station
and
remote
Labs,
eventually
I
think
that
we
will
not
want
to
have
Rely
Upon
a
Time
domain
interpretation
like
this,
but
this
will
get
us
up
and
running
and
it
does
provide
to
the
community
to
the
amateur
Community,
an
example
of
of
how
you
write
these
sorts
of
things
so
that
you
can
do
Communications
with
your
fpga
there's,
just
not
a
whole
lot
of
stuff
out
there
for
for
those
of
us
that
want
to
experiment
with
fpgas
and
with
the
prices
falling
all
the
time
and
with
so
many
sdrs.
A
A
You
know
with
high
resolution
in
in
the
repo
and
I'll
I'll,
put
a
link
out
to
the
to
the
mailing
list.
All
right.
Thank
you
so
much
this
is
it's
exciting.
We've
got
plenty
going
on
the
right
before
ham
Expo,
that
Saturday
morning
at
4,
30
I
presented
the
the
heo
project
to
the
general
membership
meeting
at
jamsat
they're,
going
to
have
the
entire
script
of
the
presentation
for
the
highly
elliptical
orbit
open
source.
A
Amateur
satellite
presentation
in
their
upcoming
Jam
sat
Journal
translated
to
Japanese
to
solicit
opinions
from
the
membership,
so
we're
hoping
to
be
able
to
collaborate
with
them
if
they
accept
the
proposal
and
then
we
start
adding
other
amsat
organizations
if
they
want
to
participate
other
open
source
groups
that
they
want
to
participate
in
Industry
partners
that
we
have
and
we'll
get
to
to
this
effort
to
get
a
heo
launched
and
it
went
really
well.
The
the
comments
and
questions
from
the
jamsat
membership
were
very
good.
A
I
am
highly
appreciative
of
the
leadership
of
jamsat
they've,
been
extremely
wonderful
and
I'm,
so
happy
that
they
have
people
that
can
translate
English
to
Japanese,
because
my
Japanese
is
extremely
limited
and
you
know,
but
this
is
a
a
wonderful
active
group,
so
that
went
well
and
we'll
we'll
know
more
soon.
A
We
also
sort
of
presented
at
least
online
to
Libra
Space
Foundation,
so
the
work
that
we're
doing
on
for
the
fpga
has
been
presented
to
a
variety
of
groups
over
the
past.
Just
few
days,
and
already
we
have
some
really
good
questions
from
both
Libra
Space
Foundation
and
from
from
jams
out.
So
the
editor
of
the
jamsat
journal
has
some
specific
questions
for
us
and
really
narrowed
down
a
few
things
in
the
presentation,
so
I'll
be
putting
that
out
on
the
list.
A
Just
to
keep
everybody
informed
about
about
what
we
need
to
do,
I'll
be
asking
the
propulsion
team
and
the
board
of
directors
of
of
Ori.
You
know
specific
questions
about
about
how
how
we
plan
to
continue
the
funding.
You
know
what
are
what
the
what
the
time
frames
are
for
a
lot
of
different
things.
So
plenty
going
on
just
over
the
past
week,
very
exciting
I
think
we're
gonna
need
more
fpga.
People
I
think
we'll
need
more
human
resources.
A
Maybe,
maybe
not
a
lot
more,
but
we
definitely
need
more
in
order
to
to
really
like
filter
out
and
to
to
to
really
get
the
the
integration
done,
and
it's
kind
of
an
open
question
here.
I
mean
we're
we're
using
our
our
earth-based
development
stations
and
we
know
that
we
have
a
path
to
to
radiation
hardened
offerings.
There
are
going
to
be
expensive,
but
we
know
we
have
a
path
but
I'm,
not
you
know.
We
don't
really
have
I
think
enough
folks
to
close
the
loop
as
rapidly
as
I'd
like.
A
That's
my
so
sort
of
my
my
superstitious
belief
that
it
doesn't
work
until
it's
working
over
the
air
really
like
to
see
the
downlink
transmitting
and
I'd
I'd
really
like
to
to
figure
out
how
to
turn
even
the
simple
FSK
into
to
working
receiver.
A
There
is
a
test
bench
in
the
FSK
code
that
we
have
and
I'll
leverage
that
pretty
hard
for
the
for
FSK
version
and
we
have
another
set
of
code.
That's
already
in
our
repository.
That's
on
the
pink,
the
p-y-n-k,
that's
a
zinc
based
board,
and
this
was
implementing
a
four
FSK
protocol
called
m17
It's,
not
finished,
but
it
is
very
far
along.
So
that's
the
next
set
of
code
that
I'm
going
to
sort
of
kind
of
give
the
the
treatment
to
and
and
try
to
document
and
get
working
on
our
Dev
station
all
right.
A
So
thank
you
all
for
listening
to
a
whole
lot
of
words,
really
fast.
I'm
gonna
stop
talking
now
and
listen
to
to
questions
and
comments,
and
anybody
that
wants
to
share
anything.
At
this
point,
please
do.
A
C
You
mentioned
the
some
concern
about
open
source
tools
and,
of
course,
the
open
source
tools
will
say
is
almost
an
impossibility,
but
I
did
see
a
very
interesting
attempt
to
do
something
like
that
on
the
VCC
presentations
this
past
weekend,
I'm
still
searching
through
those
to
see
what
I
might
be
interested
in,
but
the
guys
up
at
Scranton
we're
trying
to
eliminate
Matlab
as
a
requirement
for
some
heavy
lifting
ionospheric
work
and
the
method
they
used
to
pull
libraries
that
had
a
basis
in
very
deeply
in
open
source,
stuff
underneath
Matlab
and
to
pull
it
out
and
create
a
new
interface
that
python
could
use,
and
so
in
at
least
in
that
major
area
eliminate
Matlab
and
expensive.
C
You
know
Tool
as
well
worth
looking
at
their
presentation.
C
I
thought,
I
thought
I
was
quite
creative.
The
way
they
did
that,
and
you
can't
do
that
with
every
library
in
that
lab,
because
some
of
them
were
written
by
Matlab,
but.
A
Yeah
yeah
I
think
I'm
familiar
with
this
particular
effort.
Yeah
the
what
we
used
to
use
back
before
even
open
Research
Institute
was
a
formal
structure
we
used
octave,
which
is
the
open
source
alternative
to
Matlab.
We
used
it
a
lot
very
heavily
and
we
used
we
still
and
we
use
Python
extremely
heavily
at
Ori.
The
gap
between
octave
and
Matlab
seems
to
have
grown
and
not
closed.
C
A
C
Did
address
that
right
now,
I,
don't
remember
what
was
up
front
or
in
the
questions.
The
answers,
but
I
think
it
was
a
questions
and
answers.
Somebody
said
well:
why
did
you
go
to
all
that
trouble?
You
could
have
just
used
octave
and
the
answer
is
no.
Doesn't
work
yeah
they're,
so
excuse
me
yeah.
C
We
answer
more
and
more
often
these
days
so
and
python
I
I
can
tell
you
that
I
have
taken
a
project
that
I
have
here,
which
is
a
24
7
monitoring
system
for
GPS
parameters
that
collects
data
from
the
large
number
of
devices
every
second,
though
it's
huge
chunks
of
data
and
I
have
analyzed
it.
For
years
with
code
I
wrote
in
Matlab
and
about
six
months
ago,
I
started
converting
it
all
to
Python
and
the
end
result
is
better
yeah.
I
was
getting
from
Matlab
anyway,.
A
Yeah
python
python
is
a
real
amazing
tool
and
if,
if
you
had
to
pick
any
tool,
I
think
for
open
source
work,
you'd
want
to
pick
it
and
then
run
with.
C
A
C
Yeah,
at
least
in
the
case
of
Matlab
we've
depending
upon
what
you're
trying
to
accomplish
I
mean
I
found,
is
a
good
alternative.
Although
I've
seen
an
awful
lot
of
our
community
that
is
so
enamored
with
the
the
block
diagram
and
hook
up
the
wires
that
that
maybe
they
don't
want
to
do
the
heavy
lifting
underneath
but
yeah.
A
And
that's
kind
of
the
key
is
that
that,
if
you,
if
you
say
okay,
let's
go
with
python
instead
of
octave
or
instead
of
Matlab,
then
you
still
have
an
enormous
amount
of
work
to
do.
In
order
to
close
the
loop
to
close
the
link
between
what
these
proprietary
or
commercial
tools
can
do
and
where
python
is
because
python.
C
C
C
C
A
Even
on
you
know
even
scripts
like
like
python,
you
know
so
it's
it's
somewhat
better.
Really.
You
know,
but
then
again
Matlab
knows
what
it's
about
and
and
Pat.
You
know
python
wants
to
be
everything
to
everybody,
so
there
is
a
gap
still
there,
but
the
that
Gap
is
arguably
different.
It's
a
different
type
of
Gap
than
the
Gap
that
we
see
growing
between
Matlab
and
octave
and.
C
A
C
A
Yeah
for
those
of
for
those
people
that
are
listening
to
this
it's,
this
is
exactly
right.
This
is
this
is
the
one
of
the
biggest
challenges
with
Matlab.
Is
that
the
explosion
of
libraries
like
over
90
now
or
sorry
toolboxes?
That's
what
they
call
them.
A
You
can
get
this
license,
and
this
has
been
a
a
totally
amazing
thing
for
people
that
want
to
just
do
open
source
stuff,
non-commercial,
non-university,
non-academic
work,
and
then
all
of
the
toolboxes
that
you
need
are
also
priced
great.
Now,
the
the
big
drawback
for
the
home
license
from
Matlab
is
that
you
cannot
get
some
of
the
toolboxes
like
LTE
stuff.
A
A
You
can't
get
at
this
for
for
open
source
use,
and
so
I've
tried
to
talk
to
them
or
started
conversation
on.
Like
you
know,
if
you
just
say
it's
you're
not
going
to
provide
any
customer
support,
then
why
not
open
these
toolboxes
to
the
to
the
cheap
license
as
well,
and
that
would
help
open
source
work,
because
their
big
concern
is
that
you
know
HDL,
coder
and
GPU.
Coder
are
so
expensive
to
maintain
and
support
people.
There's
an
enormous
amount
of
tech
support
that
happens
with
these
toolboxes,
and
that
was
their
objection.
A
I'm
like
well
just
don't
give
it
just
say
it's
you're
on
your
own
and
you
guys
can
figure
it
out.
You
know,
and
so
so
that's
one
aspect.
The
the
other
thing
that
we've
learned
is
that
these
are
extremely
powerful
tools:
they're
very
quirky.
Yes,
they
they
will.
You
really
have
to
bring
your
A
game
and
you
have
to
prepare
your
your
Matlab
code
correctly
in
order
for
it
to
to
work
through
these
toolboxes.
But
it
gives
us
a
view.
A
direct
view
first-hand
view
into
what
is
the
open
source
tools.
A
Community
need
to
do
in
order
to
catch
up,
and
the
short
answer
is
a
lot
because
they're
very
powerful
the
user
interfaces
and
the
experience
is
not
great
because
it's
difficult
things
worth
doing
are
rarely
easy,
and
that
is
absolutely
true
with
like
HDL
coder
and
GPU
coder,
and
you
know
general
purpose
coding
toolboxes
in
in
Matlab.
So
we
can
sort
of
see
that,
like
python,
can
can
help
here.
A
But
you
need
to
have
people
that
have
direct
experience
with
what
these
toolboxes
are
capable
of
and
then
bring
it
over
to
the
open
source
Community
to
make
to
harness
the
power
of
like
a
python.
Now,
like
I
guess
a
number
of
years
ago,
I
would
say
to
harness
the
power
of
octave
I'm
I'm,
not
sure
that
that's
the
case
anymore,
because
you
know
I
see
this
growing,
Gap
and
I'm
very
concerned
about
it,
and
it
made
me
sad
because
I
used
to
be
used
to
use
octave
all
the
time.
I
think
now.
A
Up
in
an
open
source-
Community,
that's
just
a
guess:
I'm,
not
not
being
an
expert
here.
C
I,
don't
know
what's
going
on
with
with
active,
but
yeah
octave
is
great
benefit.
Is
this
block
diagram
and
hook
up
the
wires
and
stuff
and
the
underlying
libraries
or
toolboxes
or
whatever,
are
sort
of
hidden?
Unless
you
want
to
take
a
look,
then,
wouldn't
it
make
sense
to
merge
those
two
projects?
Python
and
active
and
you've
got
all
these
libraries
toolboxes
in
Python
and
you've
got
this
nice,
graphics
and
octave
yeah.
A
I,
don't
know,
that's
a
that's
a
really
good
question.
If
anybody
listening
knows
it
would
be
great
it'd,
be
great
to
get
a
an
education
on
the
the
current
potential
for
for
good
that
might
come
from
from
merging
these
two
projects,
because
yeah
I
think
it
would
be.
It
would
be
a
big
step
forward.
A
C
A
And
that's
like
the
biggest
challenge,
that's
that
that's
it
right
then,
and
there,
your
access
to
the
parts
that
you
want
to
use
is
very
limited.
The
ice,
storm
people
and
Ice
40
folks
have
done
such
amazing
work
and
that's
really
kind
of
the
best
example
so
far
and
those
are
relatively
small
parts.
So
that's
like
the
biggest
challenge
the
rest
of
it
is,
is
the
you
know.
A
So
that's
a
it's
apart
from
what
we're
talking
about
in
terms
of
of
being
able
to
to
bring
you
know
python
into
the
equation.
C
Well,
your
other
most
expensive
tool,
I
suspect,
is
the
IDE
compiler
or
whatever,
for
the
fpga
itself,
whether
it's
silinks
or
no
para
and
and
I'm,
seeing
I'm
wondering
if
there
isn't
a
correlation
between
the
fact
that
I
can't
seem
to
purchase
any
of
the
let's
call
it
under
a
hundred
dollar
or
under
200
fpgas,
and
that
the
xilax
is
telling
me
Oh,
but
just
buy
this
higher
priced
part.
It'll.
Do
everything
you
want
when
it's
nice
and
small
that
will
fit
in
your
project
yeah,
but
you
have
to
buy
the
compiler.
C
A
You're
right,
the
you
know
for
people
that
are
that
are
listing
the
voting
license
for
for
all
the
for
the
development
stations
that
we
have
at
Ri.
So
we
have
the
zc
706.
We
have
a
zcu
106
and
the
license
for
the
for
the
floating
license
for
vavado
is
nearly
it's
around
four
thousand
dollars,
and
you
know
it's
just
not
affordable
for
anybody,
except
for
Fairly
large
companies
and
organizations
like
ours
that
got
some
funding
to
get
it
and
then
that
license
locks
you
into
a
particular
age.
A
So
you
buy
it
once
and
it's
good
for
all
everything
up
to
some
some
to
point
in
time.
So
we're
still
pretty
good
with
this
single
purchase
of
a
license.
But
you
know
a
lot
of
companies
have
to
routinely
regularly
update
this.
This
license
and
buy
multiple
floating
licenses
for
large
teams,
and
you
can
see
where
it's
really
only
big
companies
and
proprietary
work.
That
gets
the
benefit
so
I,
don't
know.
Our
goal
is
to
try
to
figure
out
how
to
how
to
produce
well.
A
I
mean
our
goal
is
to
produce
open
source
designs
and
to
use
whatever
tool
that
we
need
to
use
in
the
process
and
if
that's
a
proprietary
tool,
that's
the
best
option.
Then
that's
what
we
use
you
know,
but
in
the
in
the
in
the
Arc
of
all
this
work,
we
we
then
know
firsthand
what
it
is
that
open
source
tools
need
to
do
in
order
to
compete,
and
so
that's
a
place
where
we
can
contribute
to
the
conversation
if
anybody's
listening.
A
A
You
know
so
it's
open
source
architecture
and
I
say,
but
but
lots
of
implementations
of
the
risk
five
processor,
a
lot
of
the
implementations
are
being
done
on
fpga
So,
Soft,
cores
of
an
open
source
instruction
architecture
and
an
open
source,
essentially
an
open
source
processor
being
done
in
the
fpga
world,
but
F4
PGA
looks
promising
and
there's
also
a
lot
of
work
being
done
still
using
Amazon's
F1
instances,
it
kind
of
gives
you
access
to.
You
know,
tools
and
the
equivalent
of
of
targets
through
through
AWS.
A
So
there's
stuff
happening,
it's
just
I
guess
we
would
like
for
it
to
happen
a
little
faster
and,
for
you
know,
companies
of
all
sizes
to
be
able
to
use
tools
that
are
affordable.
You
know,
I
guess.
My
bias
is
that
we
can't
have
the
tools
only
affordable
by
the
very
largest
companies.
We
we've
just
got
so
much
untapped
potential
in
terms
of
engineering
and
reconfigurable
Computing.
It
just
I,
don't
know
so
that's
my
that's
my
opinion
and
anything
that
we
can
do
to
kind
of
help.
Help
make
it
happen
better.
A
C
A
C
A
A
Thanks
yeah
I
think
yeah,
a
review
of
the
code
base
that
we're
working
on.
If
you
have
a
circuit
or
a
design
that
you
see
that
you
might
could
contribute,
that
would
help
like
a
block.
We
would
take
it
and
and
integrate
it
and
just
advice.
I
think
is
advice
and
and
actual
like
some
Sweat
Equity
from
time
to
time
is
what
we're
generally
in
need
of
I.
B
C
Hadn't
even
thought
of
really
and
I'm
I
keep
kicking
myself
because
for
three
years,
I
worked
for
the
Navy
at
the
Naval
Academy,
with
some
really
good
people
designing,
building
and
launching
a
satellite
that
was
the
the
design
was
created
from
the
head
of
Ron
Paris,
one
of
our
ham,
radio,
astronauts
and
NASA
employees
and
and
it
worked,
and
it
worked
for
two
years
and
then
it
stopped
working
and
everything
I
did
in.
There
was
wrong.
C
C
The
clock,
the
clock
regeneration
circuit
I
designed,
was
bogus.
It
was
terrible
so
many
things
that
we're
just
talking
about
today,
like
oh,
it's
no
big
deal.
You
just
do
this
this
and
this,
but
we
didn't
have
those
tools
at
the
pain.
A
C
At
my
very
first
project,
using
technology
that
is
relatable
to
what
you're
doing
now
was
in
I'm
trying
to
think
it's
about
late
70s,
ish
I'd
have
to
check
it.
Working
in
the
research
and
development
department
for
Harris,
RF
Communications
I
needed
an
fpga,
but
they
didn't
exist.
C
A
C
You
familiar
with
that
yeah
and
and
I
I
did
the
demodulator
for
a
44
tone,
qpsk
modem
that
ran.
That
was
intended
to
be
the
ideal
modem
for
for
high
annual
incidence
Communications
like
in
or
time
operations,
and
when
we
were
done,
we
were
able
to
communicate
at
2400
baud
on
frequencies,
like
80
meters
from
upstate,
New
York
to
Port
Huachuca,
with
100
milliwatts,
reliably
every
day
cool.
Now
that's
a
modem
yeah.
A
C
Irritated
me
was
a
few
years
later
that
modem,
which
was
a
5u
rack
mount
device,
as
you
can
imagine
that
slice
Hardware
is
big
and
and
brings
a
lot
of
power.
They
got
it
down
into
a
plug-in
board
for
a
tactical
HF
radio
for
the
for
a
Jeep.
So
I
went
from
a
five-year
unit
to
something
I,
guess
about
maybe
four
by
seven
inches
and
then
a
few
years
after
that
it
was
essentially
in
a
one-inch
Square
fpga
daughterboard
wow.
C
A
C
Were
we
were
sending
data
back
and
forth
from
the
from
the
Naval
Academy
to
NASA,
and
the
IP
police
said
wait
a
minute,
there's
no
fence
between
here
and
there
you're
sending
it
out
over
the
internet.
You
guys
are
crazy.
You
can't
do
that.
It's
against.
A
A
A
Learned
out
there
again,
because
these
things
are
enduring
and
it's
it's
at
the
very
least,
it's
good
to
it's
good
to
know.
Too
often
we
only
see
the
successful
final
outcome
and
then,
when
we
have
our
own
difficulties,
where
nothing
works
and
and
and
it
feels
hard,
it
can
feel
like
wow
I'm
such
a
colossal
failure,
so
I
mean
as
Engineers.
A
You
need
to
know
this
that
it's
hard
and
rough
and
weird
and
too
few
teams
and
organizations
and
companies
really
reveal
that
the
sausage
making
can
be
full
of
of
things
like
this.
The
road
can
be
really
Rocky.
C
Well
and
I
have
had
trouble
every
day
here,
because
I'm,
a
one-to-one
company
and
one
person
alone
designing
things
or
doing
test
procedures
or
whatever
we're
doing
I'm.
If
I
make
a
mistake,
it
sticks
so
I
started
hiring
people
who
are
physically
here,
but
just
to
have
some
another
point
of
view.
Looking
at
my
work,
you.
A
A
C
A
Thank
you.
That
means
a
lot
to
here:
cool,
okay,
let's
all
right
James
is
there
anything
from
remote
lab
South
in
particular,
you
want
to
add
or
or
bring
up
before
we
close.
B
Nothing
in
particular,
we've
covered
pretty
much
everything
for
that
regard
earlier
and
just
wanted
to
thank
you
for
all
of
the
faith
that
you
place
in
us.
Oh.
A
Of
course
it's
it's
well
earned,
and
you
know
we'll
we'll
keep
we'll
keep
working
it.
Okay,
Paul
any
last
comments
before
we
close.
A
That's
probably
a
fib,
but
thank
you
so
much
for
your
continued
support
and
help
and
and
all
the
things
you
do
for
remote
lab
West
all
right.
Let's,
let's
keep
working
and
then
we'll
have
a
report
at
the
end
of
the
week
about
all
the
stuff
going
on.
A
If
you,
if
you're
on
slack,
meet
us
there
and
if
you're
not,
please,
please
join
us,
there
drop
me
an
email
and
and
if
you're
invited
to
join
our
Technical
Community,
we
have
a
mailing
list
and
you
can
join
our
GitHub
to
follow
all
the
repos
yeah.
All
right
see
you
next
week.