►
From YouTube: ORI Office Hours 30 May 2023
Description
Project roundup and Q&A
Summary of all the "big" projects at ORI.
A
A
Good
welcome
everybody
to
today's
stand-up
and
office
hours
for
Tuesday,
May,
30th,
2023
and
open
Research
Institute.
It's
great
to
have
you
here,
so
I
have
a
short
presentation
and
then
we'll
we'll
open
it
up
for
for
office
hours
plenty
to
talk
about.
Okay.
So
a
lot
of
what
we
do
is
oriented
towards
amateur
radio
use
or
or
use
as
amateur
radio
bands
in
order
to
prove
out
a
design
and
I.
Think
it's
a
good
idea
to
to
go
over.
A
You
know
like
what
we
what
we
do
this
for
you
know
and
why
it's
a
part
97
is
the
federal
regulations
that
govern
the
amateur
radio
services
and
there's
five
justifications
for
it,
and
these
are
emergency
communications,
International,
Goodwill,
to
increase
the
technical
core
in
the
United
States,
to
advance
the
radio
arts
and
for
public
service,
and
each
of
these
has
a
knock
down
effect
that
we
know
if
we're
sort
of
in
the
culture
of
amateur
radio,
but
if
we're
not
and
and
we're
we're
using
sort
of
amateur
radio.
Oh
thank
you.
B
B
A
C
A
C
A
B
Has
prevented
amateur
satellite
service
from
launching
science
missions.
A
Yeah,
the
justifications
are
not
really
enough,
they're
in
in
and
a
lot
of
in
in
conversations
with
people
that
have
been
around
the
block
and
and
know
about
regulatory
law,
the
the
set
of
justifications
that
set
out.
A
Why
we
do
this
and
why
the
amateur
radio
services
are
special,
there's
been
times
where
these
justifications
have
been
targeted
for
deletion,
that
they're
not
necessary
for
defining
what
we
do
or
or
kind
of
giving
context
for
the
Privileges,
because,
anytime,
that
you
have
something
that's
non-commercial,
it
needs
to
really
be
defended,
and-
and
you
know
you
have
to
put
some
put
your
back
into
it-
you
have
to
explicitly
say
why
it's
valuable
and
we
see
this
in
military
Federal
scientific.
A
We
see
this
in
other
services
as
well,
where,
for
example,
the
fact
that
we
have
a
quiet
place
for
Astro.
You
know
this
astronomy
for
radio
astronomy
is
only
because
of
of
a
tremendous
amount
of
effort.
The
fact
that
we
have
frequencies
set
aside
for
for
military
and
defense
is
because
of
a
lot
of
focused
effort
and
and
bringing
it
all
the
way
up
to
the
highest
level
of
government.
Over
and
over
again,
the
military
has
no
damage
over
us
and
that
there's
a
specific
sort
of
Need
for
National
Defense.
A
The
military
is
extremely
well
funded
in
the
United
States,
getting
roughly
half
of
our
budget
and
we're
a
relatively
decentralized
group
of
people
that
are
trying
to
do
something
that
is
altruistic
and
delayed
gratification
really.
So
here
we
are
with
our
service,
with
all
of
the
things
that
you've
said,
which
are
accurate,
it's
It's
Tricky.
It
needs
to
be
defended,
not
really
enough
of
us
doing
it,
and
these
are
the
reasons
that
we
do
it.
A
So
these
reasons,
a
lot
of
this
is
why
open,
Research
Institute
exists
and
and
why
we're
organized
the
way
that
we
are
and
why
we're
picking
the
sorts
of
r
d
subjects
that
we
that
we
pick
rather
than
just
gravitating
to
whatever
we
could
make
money
off
of
we're
all
volunteers
and
volunteering,
our
time
to
kind
of
Advance
the
radio
Arts
to
increase
the
technical
core
for
international
Goodwill.
We
care
about
emergency
communications.
We
have
at
least
one
or
two
projects
in
that
realm,
and
and
really
it's
all
about
public
service.
A
These
things
are
I,
think
they're
are
demonstrably
good
and
we
have
one
or
two.
If
you
want
to
you
know,
because
the
amateur
radio
service
and
the
amateur
satellite
service
are
distinct,
we
have
two
radio
services
in
the
United
States,
where
you
get
to
do
this
sort
of
stuff
and
not
a
whole
lot
of
advocacy
really
compared
to
the
good
that
it
that
it
gives
us.
So
that's
one
of
the
things
that
I
I
just
wanted
to
remind
us
of
what
we're
here
for
and
why
we
do
the
things
that
we
do.
A
So
there's
a
lot
of
untapped
designs
out
there.
This
slide
just
kind
of
touches
on
three
things
that
we've
been
been
looking
at
recently,
that
that
are
that
are
out
there
that
were
not
commercially
valued
in
some
way
and
that
we're
we're
trying
to
to
kind
of
revive
or
to
pay
attention
to
the
gtqm.
A
A
It
got
revived
a
couple
of
times
in
the
70s
in
the
80s
and
then
a
little
more
recently,
then
Paul
actually
he's
here
on
the
call
he
ran
across
a
project
archive
about
TMS,
320,
32010
DSP
project.
It
was
a
collaboration
between
amsat
and
Tapper,
with
a
reverse
engineered,
a
design.
This
is
from
1988.
A
and
a
bunch
of
remarkable
stuff
that
that,
according
to
to
Paul,
not
yet
really
followed
up
on
all
of
this
there's
some
interesting
things
about
this.
This
a
body
of
work
and
it's
unpublished
because
it
was
on
CompuServe
on
a
private
Channel
and
then
in
2008
there
was
an
ARL,
a
league
had
an
SDR
working
group
and
they
declared
in
2008
that
there
was
an
inexorable
march
to
software
radio
as
the
standard
for
radio
and
amateur
radio
circles.
A
So
now
to
so
we'll
skip
forward.
So
now,
after
this
article
from
1958
about
HF
antennas,
we
have
a
dumbbell
project
which
is
essentially
a
meander
dipole
and
there's
an
actual
simulated
result.
We
have
built
some
prototypes.
The
DC
crew
did
this
and
found
out
that
it
worked
and
we'll
just
March
forward
on
that
in
terms
of
DSP,
an
SDR
gnu
radio
is
widely
used
and
amateur
and
experimental
radio
so
we're.
A
We
are
seeing
a
lot
of
what
was
talked
about
in
in
the
80s
start
to
come
about
from
open
source
and
in
terms
of
software-defined,
radio
and
amateur
radio.
You
can
get
an
RTL
SDR
and
a
Raspberry
Pi
free
firmware
from
GitHub
and
for
100
bucks
or
so
you've
got
a
extremely
powerful
SDR
receiver.
That
can
do
almost
anything.
A
You
can
change
it
with
a
couple
of
keystrokes,
so
what's
the
problem
there's
been
all
of
this
advancement
in
in
over
the
past
couple
of
decades
and
from
from
so
from
an
individual
perspective,
it
looks
like
this
Rush
this.
This
River
of
Technology
rushing
by
and
things
are
progressing,
but
from
an
organizational
standpoint
looking
out
onto
the
world
right
now,
like
us,
you
know,
speaking
from
the
point
of
view
of
Ori
and
lots
of
other
clubs,
getting
the
word
out
about
what
you're
doing
it's
never
been
harder,
so
I
mean.
A
A
We
have
severe
Channel
fragmentation
in
that,
if
you're,
not
a
big
company,
your
your
Google
ad
is
not
going
to
get
anywhere
so
I'll,
just
name
off
some
channels
that
that
we're
active
on
we
post
on
Twitter,
Instagram,
Facebook,
researchgate.
A
You
know
our
own
web
page
GitHub,
I
o
web
page
and
and
on
and
on
IRC
channels,
Matrix
channels,
Discord,
servers,
slack
servers
and
when
you
go
into
Discord
and
slack,
that's
like
12
or
13
different
places
that
we
routinely
try
to
spread
the
word.
Does
it
do
any
good?
A
We
hope
so,
but
it's
an
enormous
amount
of
effort
and
all
these
channels
are
very
fragmented
and
you're
fighting
against
very
well-funded
automatic
algorithms
from
from
companies
when
you're
trying
to
spread
the
word
and
then
a
lot
of
times,
open
source
projects
or
open
source
groups
like
organizations.
Try
to
do
stuff
in
amateur
radio
really
do
make
a
fundamental
mistake
of
believing
the
source
code
or
schematic
will
speak
for
itself.
It
doesn't.
The
design
does
not
speak
for
itself.
A
You
have
to
explain
it
over
and
over
again
and
make
it
easy
to
use
well
beyond
what
you
think
might
be
easy
to
use,
and
everybody
has
limited
time
and
we've
all
run
into
this
at
Ori.
Amateur
radio
is
definitely
not
immune
from
some.
Some
isms
lots
of
censorship
and
harassment
and
exclusion,
racism
and
sexism
and
bigotry.
A
This
is
out
there
and
as
a
from
organizational
perspective,
we've
have
to
deal
with
it
and
you
know
we
really
don't
fit
in
as
kind
of
a
an
organization
we're
not
top
down
and
we're
not
authoritarian
and
our
attempts
to
collaborate
with
traditional
amateur
radio
organizations
that
are
top
down
and
are
authoritarian,
not
successful
and
I'm,
not
really
sure
what
to
do
about
that.
Maybe
anybody
listening
to
this
can
suggest
some
things
or
we
just
keep
doing
what
we're
doing
and
move
on.
A
So
if
you
go
back
to
1835,
Alex
Alexis
de
tocqueville
wrote
Democracy
in
America
and
he
wrote
about
how
prominent
voluntary
private
associations
were
in
the
organization
of
social,
political
and
economic
Affairs
in
the
United
States
he's
Outsider
looking
in
and
was
dumbfounded
at
how
amazing
and
how
much
stuff
was
going
on
1835
all
the
way
up
to
about
1900.
This
is
this
is
how
got
done
in
the
United
States
and
education,
entertainment,
socializing
and
credentials
were
all
handled
mainly
through
voluntary
private
associations.
A
Government
and
companies
didn't
really
do
a
whole
lot
here.
Formal
clubs
and
orgs
handled
it
all.
When
you
hit
the
age
of
commercial,
radio
and
people
started
getting
entertainment
and
news
at
home,
and
then
television
and
then
the
internet.
Then
these
functions
from
voluntary
private
associations
were
peeled
away,
one
after
another
after
another
over
many
decades,
and
so
now,
clubs
and
organizations
which
we
look
to
for
at
least
in
in
most
Hobbies,
ranging
from
you
know,
growing
roses
to
amateur
radio
to
Linux
groups,
to
whatever
these
groups
mainly
socialize.
A
They
allow
you
socialization
opportunities,
but
the
the
education
and
and
entertainment
and
the
credentials
are
you're
on
kind
of
your
own.
This
has
been
a
big
shift
in
in
how
we
do
technical
work.
You
know
if
you
were
interested
in
Steam
valves
in
1835.
The
way
that
you
learned
about
it
and
got
good
at
it
is
different,
fundamentally
different
than
the
way
you
do
it
today,
somebody
that
was
interested
in
learning
computer
science
50
years
ago.
You
know
very
different
than
today
in
in
how
you
would
you
get
involved
and
enjoy
it.
A
So
what
we've
seen
is
the
rise
of
ad
hoc
networks
and
responsive
clubs
or
responsive
organizations,
and
ad
hoc
networks
are
very
informal,
they're,
not
Incorporated,
and
they
don't
have
a
corporate
shield
and
that's
a
big
deal.
No
dues,
no
bylaws
they're
out
there
getting
things
done
and
you
can
find
them
and
there's
ways
that
you
can
find
them
in
the
list
them
here
but
like
what's
the
weakness
of
a
informal
group,
and
it
boils
down
to
like
things
like
liability
being
able
to
own
property
being
able
to
buy
stuff.
A
No,
it's
really
really
hard
to
do
that,
and
can
they
own
property
not
easily
and
then
can
they
protect
their
members
from
reliability
not
easily?
So
those
are
the
sorts
of
things
that
we've
chosen
to
provide
here
at
Ori
and
you
know
be
getting
the
word
out
about
like
yes,
you
can
take
advantage
of
this
stuff,
but
you
don't
have
to
put
up
with
the
things
that
that
may
maybe
were
kind
of
a
burden
or
turned
you
off
or
an
impediment.
The
getting
the
word
out
has
been
really
kind
of
difficult.
A
So
why
care
about
all
this
stuff?
It's
because
the
technical
is
social
before
it's
Technical
and
the
way
that
you
distribute
and
talk
about
tech
is
part
of
the
technology.
It's
really
not
possible
to
excise,
the
math
and
the
circuit
design
and
to
get
things
done
outside
of
maybe
you
yeah
at
your
desk.
You
know,
if
you
want
to
do
all
this
by
yourself
sure,
then
you
can
just
say:
oh
it's
just
technical.
It's
it's
immune
from
all
these
different
social
changes.
A
But
if
we
want
to
get
things
done
in
groups,
then
we
have
to
confront
it.
The
way
that
we
do
technical
work
has
evolved
because
everything
about
clubs
and
organizations
has
evolved,
especially
in
the
United
States.
So
the
good
news
is
that
we
have.
We
have
document
storage
available
from
almost
anywhere
at
any
time.
A
We
have
cheap
gain
and
cheap
Computing
and
cheap
pcbs
made
in
days
and
cheap
components
for
the
most
part,
even
though
the
supply
chain
stuff
has
still
been
kind
of
a
problem
when
we
look
at
like
contributors
to
to
projects,
there's
some
interesting
things
that
happen
this
graph.
If
you
notice
it's
logarithmic
scale
but
notice
the
linear
results
of
the
of
the
data,
this
is
all
free
and
open
source
software
projects,
so
most
amateur
radio
technical
projects
can
fit
into
this
model.
So
this
is
not
data
specifically
towards
amateur
radio.
A
It's
towards
free
and
open
source
software
Community,
because
there's
free
and
open
source
software
is
many
times
larger
than
open,
open
source.
Amateur
radio,
but
I
argue
that
there's
enough
overlap
here
to
where
these
results
actually
do
apply
to
us
and
so
I'm
going
to
propose
this
as
as
a
model
that
that
applies
to
us
as
well,
and
you
can
see
that
half
of
all
projects
have
one
contributor.
A
So
everything
out
there.
That's
that's!
You
know
all
this
technical
work
going
on
in
the
community.
It's
about
half
is
done
by
one
person.
Twenty
percent
have
two
and
so
on,
and-
and
this
is
a
kind
of
a
beautiful
result-
it
it
shows
up
in
a
attractive
graph
and
it
sort
of
cognitively
intuitively
makes
sense,
and
you
can
see
that
the
largest
view
of
like
100
committers
to
the
project
and
I
think
this
is.
A
This
is
just
out
of
human
psychology,
so
when
we
look
at
our
projects
at
orri,
most
of
them
have
multiple
people,
but
three
four
five
or
more.
So
we
really
are
kind
of
at
the
upper
end
of
the
scale
in
terms
of
complexity
and
and
performance,
we
do
have
some
some
Singleton
projects
at
Ori,
but
not
very
many.
Some
of
our
some
of
our
projects
have
quite
a
few
people
and
then
the
way
that
all
this
work
gets
done.
A
There's
the
on
the
left
there's
the
triangle.
This
is
the
three
things
that
almost
all
open
source
technical
work
has
there's
some
sort
of
document
repository,
there's
some
sort
of
mailing
list
or
a
forum
and
there's
some
sort
of
chat
room
for
instant
Communications
and
those
three
things
like
a
three-legged
stool-
and
you
can
see
this
over
and
over
again.
A
The
way
that
they're
governed
can
range
from
a
democracy
where
the
people
that
show
up
are
the
people
that
run
it
to
a
Founder
leader,
which
is
the
by
far
the
most
common
in
in
amateur
radio
technical
work,
whoever
founds
the
project
leads.
The
project
you
know,
organizes
the
work
and
it's
an
enlightened
despot.
A
Then
you
have
a
self-appointing
council
or
board,
and
this
is
to
where
you're
you're,
big
enough
to
where
you
have
to
have
a
group
of
people
splitting
up
the
work
and
you
have
to
like
start
naming
names
you
get
into
electoral,
where
you're
actually
formally
electing
people
to
to
a
you
know
like
a
club.
This
would
be
a
non-incorporated
club.
A
You
get
into
corporate,
backed
where
you
have
to
have
a
board
of
directors,
follow
some
sort
of
rules
you
you're
organized
enough
to
where
you
have
an
incorporation
and
then
Foundation,
backed
to
where
it's
some
sort
of
outside
foundation,
and
so
orri
Falls.
It
falls
into
the
Electoral
and
corporate
backed
sort
of
category.
A
A
So
here's
our
current
technical
lineup.
We
are
501c3
non-profit
r
d
firm.
We
directly
benefit
amateur
radio.
This
is
100
open
source
designs.
We
have
remotely
accessible
lab
benches,
diverse
and
active
board
of
directors
and
multiple
sources
of
funding.
We
have
an
open
source,
High,
Earth,
Orbiter,
geosynchronous,
orbit,
amateur
radio,
communication
satellite,
it's
a
transponder
and
electric
propulsion
Motors.
A
That's
the
focus
of
this
project
where
it's
the
communication
system
and
the
motors
there's
a
lot
of
other
stuff
that
goes
on
the
spacecraft,
that's
where
our
focus
is
and
make
in
progress,
but
we've
had
some
enormous
setbacks
here
and
some
of
some
of
which
have
been
entirely
political
but
still
steaming
ahead.
Half
of
the
remote
lab
West
is
devoted
to
the
the
transponder
project
here
and
good
works
coming
out
of
it.
A
Ribbit
radio
is
a
hfvhf
or
UHF
tactical
emergency
communications
mode,
and
it
is
you
have
an
app
that
creates
a
audio
signal
that
you
play
over
any
radio,
and
this
is
essentially
a
digital
SMS
messaging
using
the
most
advanced
Forward
Air
correction,
that
we
have
polar
codes
and
this
is
moving
forward.
The
big
win
here
is
that
these
apps
are
open
source
and
they
exist
on
both
Android
and
Apple.
A
It's
the
first
amateur
radio
application
that
we
know
of
on
either.
One
of
these
platforms
and
they're
both
open
source
applications
and
very
useful
over
this
over
this
summer,
coming
right
up,
this
is
going
to
be
demonstrated
and-
and
there
will
be
some
some
some
tests,
both
with
emergency
communications
groups
and
with
the
aprs
people.
So
there's
a
lot
of
folks
looking
really
hard
at
it,
and
the
incorporation
of
this
particular
mode
into
emergency
communications
would
be,
would
be
good.
A
You
get
digital
Communications
without
any
wires
or
any
extra
equipment
whatsoever
from
a
free,
app.
The
RF
bit
Banger
is
one
of
our
projects.
This
is
a
low
power,
HF
HF
kit,
radio,
and
it's
designed
to
be
built
from
your
junk
box.
That's
the
original
idea,
the
the
neat
thing
about
this.
It's
a
classy
amplifier,
which
not
a
whole
lot
of
people,
know
about,
but
is
a
really
cool
design.
A
A
The
most
recent
news
on
this
is
that
the
kit
there
may
be
a
variant.
That's
all
SM
surface
mount,
so
that's
kind
of
exciting
you
can.
You
can
either
get
a
traditional
through-hole
and
junk
box
style
or
with
with
smt
Neptune
is
a
point-to-point
digital
Communications
link
designed
for
drones
and
amateur
Aerospace.
This
is
lever
hard
leverage
on
LTE,
which
is
long-term,
Evolution
cellular.
So
it's
ofdm
and
if
you've
ever
been
curious
about
ofdm,
then
this
is
a
great
way
to
learn.
A
A
So
one
of
the
things
that
makes
this
interesting
is
that
this
directly
addresses
the
dominance
in
the
market
of
some
of
the
Chinese
drone
manufacturers
and
they're
closed
and
proprietary
Source
Communications
protocols.
This
will
work
over
five
gigahertz
amateur
bands
and
it
can
be
used
in,
like
we
say
in
in
amateur
Aerospace.
So
what
we're
hoping
is
to
prove
it
out,
terrestrially
and
that
it
will
also
be
useful
for
for
space
and
Aerospace.
A
This
is
using
the
other
half
of
remote
Labs
West
stations
and
it's
going
to
leverage
MathWorks,
HDL
coder
for
for
getting
things
done
and
then
opulent
voice.
This
is
a
high
fidelity,
digital
voice
for
70
centimeters
and
above
it
uses
16
kilobit
per
second
Opus
codec
and
can
transmit
data
or
Voice
without
having
to
switch
back
and
forth,
and
things
are
working
forward
every
day
is
a
new
adventure
with
challenges
and
opportunities.
This
is
the
native
digital
Uplink
for
the
high
flyer
or
the
the
transponder
for
for
amateur
space.
A
Dumbbell
antenna
is
the
HF
antenna
that
that
we
talked
about
briefly
from
the
1958
article,
highlighting
how
there's
tons
and
tons
and
tons
of
really
overlooked
interesting
things
out
there.
Just
if
you
look
at
amateur
radio
newsletters
alone,
so
just
going
through
all
of
the
PDFs
out
there
on
the
internet,
you
can
find
all
sorts
of
ideas
that
weren't
explored
for
various
reasons.
You
know,
and-
and
this
one
looks
like
it-
it
has
some
some
potential
so
like
the
slide
says:
amateur
radios
where
overlooked
techniques
and
underutilized
bands
get
new
lives.
A
A
So
what
we
get
a
lot
is,
but
I'm
not
technical
enough
to
contribute.
We
get
a
lot
of
that
when
we
invite
people
to
join
or
when
they
show
up
and
when
they
meet
us
in
person,
and
what
we
tell
them
is
that
you
do
not
have
to
be
an
expert
to
join.
You
just
have
to
be
willing
to
become
more
of
one
along
the
way.
We
have
said
that
a
lot,
but
we
mean
it
and
it
does.
This
deserves
to
really
be
heard.
A
All
these
open
source
licenses
and
the
open
source
mindset
cheap
Computing,
and
we
mean
gpus
and
fpgas
and
Asics
and
PCs
and
one
so
when
I
say
cheap
Computing.
Some
of
the
stuff
actually
is
still
really
expensive
like
when
we
order
a
Dev
board,
it's
thousands
of
dollars,
but
it's
not
tens
of
thousands
or
hundreds
of
thousands.
It's
just
low
thousands.
We
can
afford
it
and
make
it
available
to
people
to
use.
This
is
getting
within
the
realm
of
letting
people
directly
manipulate.
A
You
know
the
the
electromagnetic
spectrum
with
with
a
gigahertz,
you
know
power,
you
know
and
and
we'll
make
it
as
easy
as
we
can.
It
still
requires
some
seat
time
and
elbow
grease,
but
like
we
are
well
within
the
ability
to
to
allow
motivated
amateurs
as
much
power
as
as
many
companies
do,
and
this
is
really
exciting.
It's
just
like
I
said
it's
been
hard
to
get
the
word
out.
A
We
have
cheap
gain
yeah,
you
can
get
gain
for
for
relatively
cheap
there's
plentiful,
microwave
Parts
I
put
a
little
dollar
sign
there
because
they
are
still
kind
of
expensive,
but
5G
and
6G
have
really
changed
the
entire
Market
microwave
Parts.
You
can.
You
can
get
them
for
tens
of
dollars,
not
hundreds
or
thousands.
It's
it's.
A
You
still
have
to
be
a
little
bit,
picky
and
and
patient,
but
you
know
we're
we're
looking
at
a
a
big
step
forward
in
terms
of
microwave
there's,
there's
some
significant
regulatory
relief
like
we've
done,
some
other
people
have
done
some
and
we
have
modern
organizational
governments
models
that
really
welcome
people
and
let
them
participate
and
then
so.
What's
next,
that's
really
kind
of
the
question
here
we
need
to
get
past
this
weird
DT,
bindings
error.
A
We
need
people
to
build
and
test
the
RF
bit
Banger
designs
and
to
get
to
the
point
where
we
have
a
kit,
we
we
get
lots
and
lots
of
of
requests
for
kits
and
I
think
that
that
it
could
be
a
success
and
there's
lots
more
and
we
have
a
getting
started
page,
and
so
that's
the
presentation
today.
That's
where
I
wanted
to
kind
of
start
out
and
and
talk
to
everybody
and
now
I'm,
going
to
I'm
going
to
stop
sharing
and
come
back
to
the
screen.
A
Thank
you
everybody
for
for
being
here.
Let's,
let's
open
the
floor
for
any
sorts
of
discussion.
A
Or
any
questions
at
all,
I
have
a
couple
that
were
sent
to
me
that
I
can
share
from
people
that
weren't
able
to
be
here
today.
So
there's
there's
a
a
request
for
a
digital
spark
gap
project.
A
This
is
a
HF
nibis
project
that
uses
some
some
techniques
from
ofdm
and
artificial
intelligence
to
court,
to
kind
of
find
the
best
path
on
on
HF.
A
So
so
I
have
a
pile
of
of
things
to
write
up
to
to
summarize
and
kind
of
publish.
So
so
I'll
do
my
best
there.
So
we
call
it.
Dsg
is
the
shorthand
for
that
or
digital
spark
gap.
A
So,
if,
when
you,
when
you
hear
that
it's
an
HF,
nivus,
essentially
AIML
project
and
you've,
you
might
have
seen
the
polynomial
signal
representation
work
that
we're
that
we're
trying
to
do
so,
we're
trying
to
kind
of
grapple
and
get
around
get
our
arms
around
a
a
polynomial
signal
representation,
which
is
a
little
bit
different.
So
if,
if
you're
familiar
with
sampling
Theory,
what
you
usually
have
is
is
samples
in
time
voltage
samples
for
your
signal,
so
digital
signals.
A
A
You
know,
contribute
towards
there
being
some
actual
examples
that
people
can
look
at
and
say:
okay,
that's
demonstrated
over
the
air,
that's
a
even
if
it's
a
relatively
simple
transmission
that
you
can
then
show
live
with
actual
signals
and
and
code
and
math
or
or
what
have
you
this
actually
working,
rather
than
it
being
all
in
mathland.
B
On
one
of
your
slides,
you
mentioned
open
source
licenses
and
mindset.
Could
you
elaborate
a
bit
I
find
the
whole
subject
of
the
Myriad
of
Open.
Source
licenses
is
a
confusing,
and
sometimes
they
get
in
the
way,
rather
than
help
with
what
I
consider
to
be
real,
open
source
projects.
A
Yes,
that's
a
really
really
good
question
and
deserves
many
hours
of,
in
fact,
there's.
There
are
many
many
hours
of
discussion
and
presentation
about
this
and
there's
whole
conferences
and
organizations
devoted
explicitly
towards
open
source
licensing,
because
we're
talking
about
designs
we're
talking
about
actual
real
work
done
by
people
with
effort
it.
It's
not.
It
shouldn't
be
surprising
at
all
that
we
then
move
towards.
A
How
do
you
protect
the
intellectual
property
of
people
that
are
essentially
donating
their
work
to
the
to
what
they
would
consider
to
be
like
the
public
domain
or
the
or
the
greater
good
or,
or
you
know,
common
cause
or
whatever
and
from
a
very
you
know,
sort
of
sort
of
naive
and
and
maybe
basic
point
of
view.
It's
like
well
just
give
it
away.
Who
cares
what
happens
to
it
and
then
very
quickly,
people
find
out,
they
really
do
care.
A
What
happens
to
it
and
and
open
source
licenses
are
the
way
to
to
kind
of
grapple
with
us
and
to
kind
of
ensure
that
the
value
and
intent
of
your
work,
that's
not
being
done
for
commercial
purposes
is
honored,
and
this
is
why
there's
a
there's,
a
myriad
there's,
a
lot
of
different
open
source
licenses
in
order
for
it
to
really
be
an
open
source
license
in
general,
we
we
look
to
the
to
the
open
source,
Institute
or
RSI,
or
open
source
initiative,
and
the
OSI
people
are
the
ones
that
that
have
really
kind
of
pioneered
the
the
definition
and
enforcement
of
Open
Source
licenses
and
we're
a
a
member
Society
of
OSI,
and
we
sign
on
to
this
sort
of
mindset.
A
So
the
reason
why
there's
so
many
different
open
source
licenses
is
because
there's
so
many
different
ways
to
Define
and
use
work,
and
if
somebody
wants
to
work
on
something-
and
they
honestly
do
not
care
how
it's
used,
they
don't
they
don't
mind,
they
wanted
it
to
be
maximally
permissive.
Then
there's
a
license
for
that.
If
there's
a
desire
for
it
only
to
be
used
in
a
narrow
or
particular
way,
then
there's
a
license
for
that.
A
A
There's
there's
a
few
licenses
that
are
consistently
picked
by
the
community
over
and
over
again,
so
so,
there's
a
few
licenses
that
are
very
popular
for
for
fpga
work
in
particular,
since
there
there
wasn't
a
whole
lot
of
work
here
for
for
a
while,
the
CERN
licensed
the
open,
Hardware
license
has
kind
of
stepped
up,
especially
the
2.0
version.
There
was
a
1.0
version,
lots
of
feedback
about
that,
but
this
are
an
open,
Hardware
license
version.
A
2.0
is
the
one
that
we
use
is
default
for
firmware
and
Hardware,
because
it's
it's
really
quite
good,
then
there's
the
for
software
licensing
there's
a
there's
much
more
available,
so
software
has
a
much
stronger
tradition
of
of
Open
Source
mindset
and
practice.
So
there's
there's
a
bigger
variety
of
licenses
there
and
we
use
GPL
version
version
3.0
as
a
default.
What
we
do
at
Ori
is
we
say
whatever
license
that
you
that
you
and
your
team
want
for
your
project
that
that
meets
your
needs.
A
You
should
use
that
that
we
offer
the
defaults
only
as
like
here's
the
starting
point.
This
is
what
we
think
is
good
and
here's.
Why?
But
you
get
to
pick
what
we
really
discourage
is
no
license
at
all,
because
that's
not
great
for
anybody-
and
you
know
you
really
do
have
to
kind
of
put
put
some
time
into
figuring
out,
which
one
is
the
one
to
use.
A
I,
guess
that
the
the
way
that
I
view
it
is
that
because
there's
a
diversity
of
licenses
that
this
kind
of
shows
that
there
is
a
active
and
productive
debate
about
the
details
of
how
to
manage
intellectual
property
and
and
it's
a
good
sign
in
general,
for
for
open
source
work.
The
downside
of
this
is
that
you're
exactly
right.
A
It
can
be
tremendously
confusing
to
figure
out
which
one
is
the
right
one
for
your
project
and
sometimes
you're,
going
to
need
to
talk
to
to
an
expert
and
thank
goodness,
OSI
exists
and
that
they
are
there
and
they're
extremely
helpful
and
responsive.
A
If
that's
not
good
enough,
then
there
are
an
increasing
number
of
of
lawyers
and
experts
that
are
out
there.
That
can
give
you
really
good
advice.
There's
a
number
of
of
firms
that,
like
organizations
like
eff,
another
fantastic
resource
for
this
that
can
recommend
and
and
a
lot
of
those
will,
will
give
you
advice
for
very
little
amount
of
money.
A
For
example,
space
and
satellite
work,
that's
kind
of
that
it
has,
in
the
past,
been
tricky
and
restrictive.
We've
gotten
a
lot
of
regulatory
relief
because
of
ori's
work,
but
you
still
really
kind
of
need
to
guard
your
work
with
some
sort
of
license
that
will
allow
you
to
share
it
easily
and
well,
and
so
that
I
hope
that
answers
it
a
little
bit
in
general,
it's
it's
as
confusing
as
it
has
to
be,
and
possibly
a
little
bit
more
confusing
than
it
needs
to
be.
A
Yeah
OSI
is
they're.
A
B
That's
they're.
B
A
Yeah
MIT
license
is
a
big
player.
Gpl
licensed
is
a
is
a
big
one.
Creative
Commons,
if
you're
familiar
with
that,
that's
a
whole
whole
collection
of
licenses
of
different
levels.
You.
A
Cern
has
three
levels:
we
we
recommend
the
most
permissive
just
to
make
it
as
easy
as
possible
for
the
work
to
to
be
reused.
A
But
you
know
I
mean
when
you're
talking
about
engineering
work
and
design
work
artwork
all
of
these
sorts
of
things,
that
and
and
when
you
want
it
to
be
open,
open
source,
there's
a
there's,
a
lot
of
Shades
of
Gray.
So
it's
good
that
we
have
the
the
variety
that
we
have
and
it's
it's
kind
of
evidence
of
the
the
level
of
activity
and
and
and
how
important
open
source
has
become.
A
The
flip
side
of
that
is
exactly
as
you
say,
it
can
be
quite
daunting
to
look
at
this
list
and,
and
and
like
you
might
be
wondering
like
if
I
choose
the
wrong
open
source
license,
is
something
horrible
going
to
happen
to
my
work
or
me,
you
know,
am
I
am
I
going
to
look
like
an
idiot
for
choosing
Creative
Commons
license
or
am
I
going
to
prevent
somebody
from
using
my
work,
if
I
choose
say,
for
example,
GPL
2.0
versus
3.0,
and
you
know
it,
it
does
require
some
some
of
your
time
to
to
figure
it
out
and
to
figure
out
what
is
the
right
level
for
you.
A
A
Yeah
OSI
the
open
source
initiative.
People
are
amazing,
we're
really
happy
to
be
part.
You
know
to
be
to
be
a
Community
member
and
to
get
to
get
their
help
and
support
and
advice.
It's
it's
the
right
organization
to
look
look
towards
for
for
licensing
your.
A
Yeah,
we'll
just
but
we're
not
we're,
not
experts
in
licensing
we
try
to
be
as
as
responsive
and
good
and
as
possible
about
about
creating
open
source
work.
So
we
rely
very
heavily
on
on
OSI
to
you
know,
for
advice
on
on
licensing
and
to
put
into
practice
what
they
what
they
say.
A
So
it's
an
excellent
place
to
go.
Eff
is
another
one.
That's
helped
us
out
repeatedly,
so
the
Electronic
Frontier
Foundation
is
has
a
very
clear
visceral
understanding
of
of
what
it
means
to
to
put
open
source
work
out
there
to
defend
it
and
to
to
increase.
You
know,
freedoms
when
when
it
comes
to
to
design
and
sharing
and
communicating
so
so
eff
and
epic
is
another
organization,
that's
that's
worth
worth.
A
Looking
at
I've
had
a
lot
of
Direct,
Communications
and
experiences
with
both
eff
and
OSI,
and
it's
been
been
very
good
and
helpful.
I,
don't
think
we
would
be
where
we
are
today
at
all,
without
either
eff
or
OSI
helping
us.
A
A
So
you
really
do
have
to
kind
of
like
look
out
for
folks
and
to
make
it
easy
for
them
to
participate.
Open
source
licenses
are
a
big
part
of
that.
You
know
licensing
the
work
and
then
you
know
sometimes
it
can
can
come
across
as
as
grumpy
and
ticky,
for
example,
when
it
comes
to
the
free
software
foundation
for,
for
instance,
this
is
a
venerable
long-term
player
in
open
source,
free
and
open
source
software,
or
actually
free
software
free
software
Foundation.
A
And
if
you
wanted
to
be
part
of
the
free
software
Foundation
like
a
good
new
project,
gnu
project,
then
you
had
to
fill
out
paperwork
and
every
time
that
you,
you
know,
made
a
major
sort
of
deal
with
them
or
wanted
to
to
set
up
a
project.
Then
then
you
would
have
to
fill
out
all
this
paperwork
and
and
sign
over.
A
You
know
explicitly
sign,
sign
rights
and
things
like
that
and
over
time
you
know
the
sort
of
the
the
the
impact
of
this
faded
like
it's
like
okay,
this
is
this
is
actually
something
that
people
are
doing
in
order
to
to
coalesce
together
in
sort
of
a
union
to
protect
their
work,
their
free
work,
and
then
it
became
over
time
perceived
more
and
more
as
onerous
sort
of
chore
and
that
what
are
we
getting?
You
know
by
signing
over
all
this,
these
doing
all
this
documentation
and
jumping
through
this
Hoops.
A
What
are
we
getting
for
this,
and
so
you
know
it's
sort
of
a
lesson
in
it
it
over
time.
We
we
take
things
from
start
to
take
things
for
granted
that
big
Innovations
in
things
like
licensing
or
or
banding,
together
to
kind
of
protect
your
work
over
time
they
can
become
taken
for
granted
and
over
time.
Organizations
that
provide
these
Services
can
get
comfortable
and
and
maybe
start
to
to
look
at
at
this
as
more
of
a
way
to
control
things
rather
than
to
enable.
A
A
D
Here
we
go
lost
my
window,
nothing
not
really
that
on
the
DSP
10
project,
that's
ancient
history
from
Tapper
and
amsat
reverse
engineering
was
a
very
small
part
of
it.
D
D
It
never
really
took
over
the
world.
I,
don't
guess,
but
stuff
did
come
out
of
that
project
and
it
was
I
think
you
have
to
call
it
a
a
modest
success.
It
did
not
become
the
next
TNC,
although
that
was
one
of
the
main
topics
for
discussion
back
in
those
days.
D
Whether
they
wanted
to
be
the
next
CNC
or
not
so,
there's
a
lot
of
really
interesting
stuff
that
was
going
on
and
it
would
have
been
wonderful
if
it
had
been
more
open,
but
in
those
days
infrastructure
really
wasn't
there
that
the
best
way
we
could
get
real
time
or
near
real-time
collaboration
over
the
internet
was
to
go
to
CompuServe,
because
there
was
no
internet
that
was
available
to
most
people.
D
A
Yeah
I
think
we
probably
underestimate
how
dramatically
different
things
are
and
that
hadn't
have
been
multiple
times.
I
think
we're.
If
you
look
back
to
1988
and
looked
today
to
2023
that
there's
multiple
essential,
multiple
Revolutions
in
in
the
way
that
we
organize
work,
you
know
I
think
we're
now
kind
of
dealing
with
the
the
aftermath
of
the
walled
Gardens
for
for
communication
and
the
kind
of
the
rise
of
or
re-rise.
You
know
it's
a
Revival
of
of
old
school.
A
You
know
open
open
platforms
that
were,
at
the
time
an
answer
to
things
like
CompuServe
I,
distinctly,
remember,
Prodigy
and
CompuServe,
because
I
had
to
deliver
tech
support
for
apiary
Incorporated,
who
I
worked
for
at
the
time
over
these
these
services
and
and
it
was
kind
of
a
a
revolution
for
IRC
to
come
along
so
I
think
we've
all
seen
in
like
web
forums,
kind
of
get
overtaken
by
by
things
like
Facebook
and
groups
and
groups
I
o
and
and
now
there
there
may
be
a
shift
again.
A
So
the
way
that
we
talk
is
the
way
that
we
communicate
really
kind
of
affects
the
organization.
The
structure
of
projects
and
the
structure
of
projects
affects
the
work,
so
the
work
itself
is
never
independent
from
the
social
structure
and
we
have
had
some
significant
Transformations,
especially
in
amateur
radio
and
in
Engineering
in
general.
A
All
of
this
stuff
has
has
some
some
pretty
big
repercussions,
so
I
guess
one
of
our
jobs
or
is
to
try
to
figure
out
what
the
best
way
is
to
to
get
the
word
out
and
allow
people
to
participate
with
as
little
friction
as
possible
and
I
gotta
tell
you
it's
not
an
easy
thing
to
keep
going
just
got
to
keep
trying
and
and
be
open
to
new
ways
of
doing
things.
A
It
would
be
really
neat
if
the
all
the
discussions
about
the
the
DSP
10
project
could
could
be
published,
but
I
understand
that
they
were.
They
were
intended
to
sort
of
be
private,
so
kind
of
dumping
them
on
the
Internet
would
be
maybe
unfair,
not
not
the
best
way
to
do
it,
but
as
a
case
study
of
of
really
Innovative
and
fun
work
and
amateur
radio.
A
A
So
I
don't
know
the
plenty
plenty
to
think
about
that's
and
plenty
to
to
tackle
like
over
the
next
week.
The
just
the
just
the
small
list
of
things
that
we
need
help
with
is
enough
to
keep
a
bunch
of
people
busy
for
it
for
the
entire
week
and
then
we'll
we'll
come
up
here
pretty
shortly
on
a
on
a
week
where
we
have
a
big
show
to
do
and
then
later
in
the
summer.
A
Another
big
show
you
know
so
we'll
we'll
shift
back
and
forth
from
from
Outreach
and
talking
with
new
people
and
presenting
work
to
trying
to
get
the
work
done
in
the
first
place,
and
all
of
that
you
know
worked
through.
All
of
that
is
is
trying
to
spread
the
word
and
and
get
more
folks
involved,
because
I
think
it's
fair
to
say
that
we
have
a
lot
more
work
than
people
at
any
time.
A
Really
you've
been
very,
very
fortunate
to
have
the
response
that
we've
had
and
the
wonderful
teams
that
we
have
you
know,
but
you
you
have
to
continually
do
Outreach
and
welcome
new
people.
A
You
know
turnover
in
most
open
source
teams
is
as
a
particular
style,
a
particular
shape,
oftentimes
there's
a
few
people
that
are
the
dominant
contributors
and
then
a
very
high
turnover
for
the
rest
and
I,
just
just
as
a
very
biased
point
of
view,
I'd
like
to
tilt
it
more
towards
you
know,
welcoming
people
and
making
making
them
making
it
possible
for
them
to
stick
around
for
for
a
while
and
and
really
kind
of
develop
skills
and
get
something
out
of
it.
A
There's
a
reason
that
that
sort
of
structure
exists
in
the
world
it
does.
It
does
work
for
certain
projects
and
I.
Look
at
our
lineup
and
I
think
that
that
what
we're
doing
is
maybe
not
as
easily
divided
up
that
that
it
does
require
a
little
more
seat
time.
The
things
that
we're
doing
are
are
maybe
more
more
complicated
sort
of
longer
longer
term
in
terms
of
time.
D
Had
we
changed
anything
since
last
week,
I,
don't
think
so.
We've
we've
got
the
two
systems
all
set
up
the
way
they're
supposed
to
go
and
have
made
some
progress
on
getting
them
working
on
the
different
software
configurations,
but
been
a
lot
of
other
things
going
on
this
week.
A
Yeah
I
think
the
the
new
hardware
went
better
or
integrating
the
new
hardware
better
than
I
thought.
It
still
took
a
lot
of
time
and
effort,
but
but
I'm
happy
with
the
new
Direction
and
the
new
new
hardware.
I
think
the
only
toe
stubbing
that
has
happened
to
me
is
that
the
the
two
radio
boards
or
or
names
very
similar
so
there's
the
9002
and
the
9009
and
I've
gotten
several
several
times
almost
gotten
confused
between
the
two
when
documenting
or
or
working
with
them.
So
that's,
that's.
A
That's
been
my
only
complaint
and
it'll
get
better
it'll
get
better
over
time.
But
if,
if
I'm
having
trouble
keeping
it
straight,
then
that's
a
that's
kind
of
a
red
flag
to
to
watch
out
for
for
for
people
joining
up.
You
know.
D
It's
a
little
bit
unusual
to
have
to
two
different
boards
in
the
same
level
of
stage
of
of
integration
and
development
in
the
lab.
Usually
you
know
some
components,
engineer
or
some
engineer
tasked
with
picking
the
next
component
is
the
only
one
has
to
worry
about
that,
and
then
everybody
just
uses
the
radio
and
the
board,
and
here
we
have
multiple
things
in
flight
at
once,.
A
Yeah
yeah,
that's
true,
the
naming
them
could
could
help
the
the
baseboards
are
pretty
different
too
one's
a
7000
series
xilinx
and
the
other
is
an
ultrascale
plus
and
those
are
they're,
not
not
the
same.
You
know
they're
they're
different
enough,
so
so
it
sort
of
looks
like
oh,
there
are
two
different
radios
on
top
of
essentially
the
same
Dev
board,
and
that's
not
exactly
right.
A
So
it's
a
it's
subtle
and
if
it's,
if
it's
difficult
for
us
in
any
way,
then
it's
going
to
be
many
times
more
difficult
for
a
new
person.
So
in
terms
of
documentation,
I
think
we've
got
a
lot
to
do.
We've
got
just
a
lot
to
catch
up
with
on
building
the
the
embedded
version
of
Linux
for
for
both
of
the
boards
for
build
root.
Like
we
said
last
week,
there's
three
different
ways
to
to
you
know:
to
communicate
with
those
three
different,
embedded,
Linux
versions
for
these
systems
at.
D
A
At
least,
and
that
these
three
have
each
have
distinct
advantages
and
disadvantages
they're
all
fairly
close
and
that
they
all
use
the
same
reference
design
from
Analog
Devices
for
the
PGA,
but
they
all
are,
they
all
are
done
differently
and
and
from
different,
essentially
ecosystems
or
different
companies,
with
different
emphasis
and
and
different
advantages.
So
it's
been.
A
It's
been
an
adventure
kind
of
picking
through
all
the
these
three,
these
three
offerings
and
we're
having
a
lot
we're
still
having
trouble.
Building
the
one
from
MathWorks
and.
D
A
Well,
I
would
say
that
we
can
document
the
the
build,
especially
for
math
works
up
to
the
point
where,
where
it's
totally
working
for
the
baseboard,
so
that
is
true-
we've
been
able
to
build
the
the
MathWorks
build
root
version.
So
if
you
want
to
use
Matlab
and
simulink
with
our
Dev
boards,
this
is
supposedly
the
right
answer.
This
is
this
will
give
you
some
advantages
and
those
builds
existed.
A
They
finally
worked
with
some
patches
and
some
some
additional
libraries
and
all
and
and
getting
that
written
down,
is
good,
adding
in
the
DTs
files
for
the
device
tree
for
the
for
the
radio
cards
on
these
Dev
boards
has
not
been
straightforward
or
easy
and
I've
been
somewhat
surprised
by
that,
because
you
know
math
MathWorks
really
wants
to
enable
SDR
work
and
all
this
digital
Communications,
toolboxes
and
all
this
stuff
and
all
this
activity
and
and
they're
they're
in-house
experts
are
like
died
you're
far
beyond
where
we
can
help
you
I
was
like
that's
not
great,
that's
not
good,
so
I
think
we've
we've
given
it
a
week,
you
know
and
and
all
and
we're
gonna
have
to
go
back
out
and
do
another
round
of
like
really
like
figuring
it
out
and
Publishing
it.
A
So
where
are
the
lines
like
the
lines
between
the
radio
card
and
the
bass
and
the
bass
Dev
board?
You
know
the
the
fpga
dev
board.
That's
a
obvious
line
like
Analog
Devices
makes
the
radio
card
xilinx
makes
the
dev
board
MathWorks
claims
to
address
it
all,
but
their
their
build
of
build,
build
root
works
up
to
the
point
where
you
have
to
start
customizing,
the
the
the
build
of
Linux
for
the
for
the
radio
card.
A
A
It
looks
like
those
two
Targets
are
the
only
ones
that
that
they
that
went
all
the
way
with,
but
they're
really
excited
about
the
9000
Series
stuff
that
we
have
so
I'm
I'm,
hoping
that
that
things
will
evolve
over
the
next
week
and
we'll
maybe
find
the
find
more
people
or
figure
out
what
we're
what
we
need
to
do
if
we
document
the
snot
out
of
it
and
and
then
look
really
hard
at
like
okay.
A
What
what
what's
enabled
by
all
of
this
work
like
you
now,
can
address
everything
and
handle
everything,
and
you
can
put
your
fpga
station
in
the
loop
and
and
do
a
lot
of
radio
work
and
make
it
easy
for
people
wow
things
get
really
exciting
very
quickly
and
that
you
know
that's
kind
of
the
goal,
but
but
right
now
we're
stuck
in
a
particular
spot,
we're
way
way
far
along
in
the
process,
but
we
have
to
be
able
to
build
the
device
tree.
A
So
the
right
answer
may
be
to
just
pop
on
over
to
Pedal
Linux
and
build
up.
You
know
an
OS,
an
embedded
OS
that
includes
the
the
dev
board
and
and
go
back
to
trying
to
code
everything
in
Nim
vivato
and
also
try
to
see,
if
that,
if
all
the
benefits
from
HDL,
coder
and
and
Matlab
and
simulink
still
work
with
a
with
a
petal
Linux
build
they.
A
What
what
we
got
from,
what
we
got
from
MathWorks
was
no
don't
do
that
that
we
have.
We
have
Special
Sauce,
you
know
worked
into
the
build
root
version,
but
if
it's
impossible
or
really
really
hard
to
get
the
device
tree
working,
that's
a
big
drawback.
So
so
maybe
we
can
contribute.
A
Other
people
have
done
this.
You
know
you
can
see
evidence
of
their
of
their
work
on
various
web
forums
and
and
in
questions,
but
in
reaching
out
to
these
people
they're
very
cagey
about
how
they
did
it.
So
not
a
not
a
great
sign,
but,
like
you
know,
it
means
it's
possible
and
the
recipe
is
a
little
obscure
and
you
know
liberating.
That
sort
of
knowledge
is
what
we're
after
so
that's
that's
the
status
on
that.
A
Hopefully,
by
next
week,
we'll
be
able
to
report
that
we
have
easily
addressing
the
devices
in
in
our
stations
from
from
the
lab
and
and
remotely
that
everything
is
working
over
the
air
and
and
all
that
independent.
A
Yeah
petal
Linux
is
free,
it's
yeah,
it's
it's
neat,
that's
what
we
were
using
with
the
9371
when
and
the
the
zc706,
and
you
build
up
a
you
use,
petal
Linux
to
to
and
The
Petal
Linux
tool
chain.
It's
all
free
and
open
source.
So
no
there
isn't
any
licensing
issue.
A
There
is
really
isn't
a
licensing
issue
with
any
one
of
these
from
Analog
Devices.
You
can
get
the
Kuiper
build
from
it's
a
Kuiper
build.
Is
there
their
image
their
version
of
Linux
and
it
has
iio
industrial
input
output
and
it
uses
the
it?
You
know
it
uses
their
HDL
reference
design
and
we've
used
it
successfully.
Petal
Linux
also
uses
IO
industrial
input,
output
Library,
it
also
uses
The,
Analog
Devices
HDL
reference
design
and
petal
Linux
does
not
have
any
licensing
issues
that
I'm
aware
of
at
all
and.
B
A
A
You
have
to
know
where
to
put
the
DTs
files,
which
is
the
device
tree
stuff
so
building
in
the
device
tree
you
go
and
you
get
the
device
tree
source
files
from
Analog,
Devices
you're
building
for
the
baseboard
and
the
pedal
Linux
process
gets
past
the
problem
that
we're
having
with
the
Matlab
image,
which
is
how
do
you
get
the
device
tree
to
compile
correctly
for
MathWorks
build
route
for
like
the
9002
and
the
9009
on
these
supported
boards?
So
petal
Linux
has
been
good.
A
The
downside
to
Petal
Linux
is
like
once
you
get
it
built
then
well,
HDL
coder
looked
at
it
and
went
I
can't
put
you
in
the
loop.
You
can
Target
it
for
for
HDL
code
or
work,
but
we
weren't
able
to
get
it
to
do,
live
iterations
and
then
the
MathWorks
people
said:
oh
yeah,
you
got
to
use
our
build
route
for
it.
For
that.
So
that's
one
of
the
reasons
why
we're
spending
time
looking
at
the
the
math
Works
build
route.
A
It
may
be
that
we
we
go
back
to
Pedal
Linux
to
get
the
stuff
done
and
we
give
up
using
fpga
in
the
loop
as
part
of
our
process,
but
I'm
I'm.
Not
yet
to
the
point
where
I
want
to
give
up.
You
know,
because
having
live
fpga
in
the
loop
would
would
really
speed
up
a
lot
of
the
testing
and
and
make
the
you
know
demonstrating
over
the
air
a
lot
easier.
A
But
yeah
thanks
for
pointing
out
there's
I
I,
think
I
vaguely
remember
petal
Linux
being
a
licensed
like
you
had
a
just
like
a
lot
of
things
like
the
license
might
be
free
for
the
asking,
but
you
still
have
to
go
get
it,
which
is
still
a
hoop
that
you
have
to
jump
through.
You
know
so
I,
don't
remember
I,
don't
remember
if
you
had
to
pay
for
petal
Linux
or
not.
A
I
know
things
in
general,
have
kind
of
progressed
towards
being
more
accessible
and
more
open,
which
is
good.
You
know,
especially
for
Tool
chains,
it's
like
if
you're
a
company
I,
think
I'm
I'm,
biased
in
the
direction
of
you
need
to
to
guard
and
and
to
to
kind
of
like
keep
proprietary
things
that
that
differentiate
you
as
a
business
and
the
rest
of
it
giveaway.
You
know.
In
the
end,
it
will
help
you.
A
Okay,
any
last
questions
or
comments
for
office
hours.
A
Okay,
thank
you.
Yeah
James
had
to
to
take
off
for
school
and
is
looking
forward
to
next
week
and
we'll
have
lots
more
updates
during
the
week
There's
plenty
going
on.
Thank
you,
everybody
for
for
coming
and,
if
you're,
if
you're
watching
this.
Thank
you
very
much
for
watching
and
you're,
more
than
welcome
to
kind
of
join
the
fun
we're
open,
Research,
Institute,
and
if
you
go
to
openresearch.institute
and
click
on
getting
started,
then
that's
the
best
way
to
get
in
touch
with
us
and
to
get
involved
in
our
slack.
A
Our
mailing
list
or
GitHub
accounts
and
and
meetings
like
this
all
right,
everybody,
I'll,
I'll,
shut
down
and
I
will
see
you
all
next
week,
it'll
be
exciting.
That'll
be
the
last
meeting
before
IMS
2023,
the
international
microwave
Symposium,
which
is
here
in
San
Diego.
So
we'll
we'll
have
a
if
all
goes
well,
we'll
have
a
live
report
from
IMS
about
about
all
of
our
activities
and
presentations
and
all
the
amazing
things
going
on
there.
So
it
will
be
plenty
coming
up
in
June.