Inner Circle Newsletter: Summer 2024

A Sizzling Summer Summary prepared just for you!

Read on for highlights from all our technical and regulatory open source digital radio work. ORI’s work directly benefits amateur radio, provides educational and professional development opportunities for people all over the world, and puts ethics and good governance first.

Opulent Voice Flying High

Opulent Voice is an open source high bitrate digital voice (and data) protocol. It’s what we are using for our native digital uplink protocol for ORI’s broadband microwave digital satellite transponder project. Opulent Voice has excellent voice quality, putting it in a completely different category than low bitrate digital communications products such as D-Star, Yaesu System Fusion, and DMR.

Opulent voice switches between high resolution voice and data without requiring the operator to switch to a separate packet mode. Opulent voice also handles keyboard chat and digital file transmission. Seamless integration of different data types, using modern digital communication techniques, differentiates Opulent Voice from any other amateur radio protocol.

Opulent Voice will fly on the University of Puerto Rico’s RockSat-X launch on 13 August 2024. It’s been a very positive experience working with the students and faculty at the University.

An implementation on FPGA for the PLUTO SDR is well underway, with a active international team delivering quality results. This implementation will not only turn your PLUTO SDR into an Opulent Voice transceiver, but it will have remote operation functionality.

Hear what Opulent Voice sounds like by following the links in an earlier update at https://www.openresearch.institute/2022/07/30/opulent-voice-digital-voice-and-data-protocol-update/

We’ve come quite a long way in less than two years! The FPGA implementation upgrades the modulation from 4-ary frequency shift keying to minimum shift keying, and increases forward error correction performance and flexibility.

HAMCON:ZION 2024 is This Week!

Please visit us at HAMCON:ZION 2024 this weekend, 12-13 July 2024 in St. George, Utah, USA.

The event website is https://www.hamconzion.com/

ORI will have a club booth at the event. We opened our space to QRZ.com (https://www.qrz.com/) and Deep Space Exploration Society (https://dses.science/). This combined exhibit is a one-stop shop for the best in community, technical, and citizen science amateur radio activity.

We have a volunteer presenting on Artificial Intelligence and Machine Learning in Amateur Radio. The talk opens with a brief summary of the history of our relationship with created intelligence and then explores case studies of the use of artificial intelligence and machine learning in amateur radio. Talk is 1pm on Friday in Entrada B.

Open Research Institute at DEFCON32

We will present an Open Source Showcase at DEFCON in the Radio Frequency Village 12-13 August 2024, with accessible exhibits and demonstrations. Here is the list of scheduled project demonstrations.

Regulatory Efforts: ORI works hard for open source digital radio work and moves technology from proprietary and controlled to open and free in intelligent and mutually beneficial ways. Our work on ITAR, EAR, Debris Mitigation, AI/ML, and Synthetic Aperture Radar will be presented and explained. Find out more at https://github.com/OpenResearchInstitute/documents/tree/master/Regulatory

Ribbit: this open source communications protocol uses the highest performance error correction and modern techniques to turn any analog radio into a digital text terminal. No wires, no extra equipment.. Learn how to use this communications system and get involved in building a truly innovative open source tactical radio service. Find out more at https://www.ribbitradio.org

Satellite: ORI has the world’s first and only open source HEO/GEO communications satellite project. All working parts of the transponder project will be demonstrated, from Opulent Voice to antenna designs.

The Dumbbell antenna: We have an HF antenna design based on a highly effective inductive loading technique first written about in 1958. Learn about this antenna and find out how to make your own. Repository can be found at https://github.com/OpenResearchInstitute/dumbbell

RFBitBanger: an HF QRP system and novel digital protocol called SCAMP. Kit information and updates will be available. Get your Batch 2 kit today at https://www.ebay.com/itm/364783754396

Radar: Our regulatory and technical work in synthetic aperture radar will be demonstrated. One of our volunteers will be giving a talk about open source synthetic aperture radar in the RF Village speakers track. Here is the abstract.

Synthetic Aperture Radar (SAR) is one of the most useful and interesting techniques in radar, providing high resolution radar satellite images from relatively small satellites. SAR is not limited by the time of day or by atmospheric conditions. It complements satellite photography and other remote sensing techniques, revealing activity on the Earth that would otherwise be hidden. How does the magic happen? This talk will explain the basics of SAR in an accessible and friendly way. That’s the good news.

The bad news? SAR is controlled by ITAR, the International Traffic in Arms Regulations, and is listed in the USML, the United States Munitions List. ITAR regulates the export of defense articles and services and is administered by the US State Department. This includes both products and services as well as technical data. Such as, catalogs of high resolution radar imagary. The articles and services regulated by ITAR are identified in the USML. If ITAR doesn’t get you, then EAR just might. The Export Administration Regulations (EAR) are administered by the US Commerce Department, and items are listed on a Commerce Control List (CCL). Commercial products and services and dual-use items that are not subject to ITAR could be regulated by EAR. Even if you are free of ITAR and EAR, you may still be regulated by yet another agency, such as the FCC.

Regulation of SAR chills commercial activity, creating costly and time-consuming burdens. But why does any of this matter to signals hackers? Because technology has overtaken the rules, and devices used by enthusiasts, researchers, students, and hackers are increasingly likely to have enough capability to fall into export-controlled categories. The penalties are harsh. Fear of running afoul of ITAR is enough to stop a promising open source project in its tracks.

Is there a way forward? Yes. ITAR has a public domain carve out. Information that is published and that is generally accessible or available to the public is excluded from control as ITAR technical data. That’s great in theory, but how can we increase our confidence that we are interpreting these rules correctly? How can we use and build upon these rules, so that our community can learn and practice modern radio techniques with reduced fear and risk? Can we contribute towards regulatory relief when it comes to SAR? We will describe the process, report on the progress, and enumerate the challenges and roadblocks.

RFBitBanger Batch 2 Kits Available

Kits are available at our eBay store at this link https://www.ebay.com/itm/364783754396

Be a part of the future with a prototype Batch 2 kit build of the RFBitBanger, a low-power high-frequency digital radio by Dr. Daniel Marks KW4TI. Presented by Open Research Institute, this kit is designed to produce 4 watts of power and opens up a new digital protocol called SCAMP.

SCAMP Is now available in FLDigi!

Source code and extensive instructions can be found at https://github.com/profdc9/fldigi

Your donation in exchange for this kit directly enables the further development of an innovative Class E amplifier based radio design. It has a display, button menu navigation, and keyboard connection for keyboard modes and keyboard-enabled navigation. This radio can be taken portable or used in a case. If you have a 3d printer, then Dr. Marks has a design ready for you to print in the repository linked below.

  • Built-in digital modes: CW, RTTY, SCAMP (FSK and OOK, multiple speeds)
  • Key jack supports straight keys and iambic paddles
  • Open Source hardware and firmware, Arduino UNO compatible https://github.com/profdc9/RFBitBanger
  • External sound-card FSK digital modes supported (including FT4/FT8)
  • Experimental SSB support
  • Serial port support (2400 baud) for send and receive in keyboard modes

SCAMP is a new protocol that allows keyboard-to-keyboard contacts with a digital protocol that has excellent connection performance. See Dr. Marks presentation about RFBitBanger at QSO Today Academy in September 2023 to learn more about SCAMP and the RFBitBanger project. Link below:

All surface mount parts on the main board are pre-installed at the factory. All the through-hole parts you need to complete the radio are provided for you to solder yourself.

Builder’s notes and photos of all the components to help you identify and install them can be found here:

https://github.com/OpenResearchInstitute/RFBitBanger-kit/tree/main/batch2

If you don’t know how to wind toroids or solder surface mount capacitors, this is an excellent kit to learn on. There are just six toroids on the main board, and two on each band pass filter board. You can build just one band pass filter board and operate on a single band, or you can build an assortment. We provide 12 filter boards, enough toroids to build any 9 filters, and a supply of capacitors that will let you build those 9 filters for 9 different HF ham bands. These capacitors are size 1206, which is the largest common size for SMT capacitors and the easiest to solder manually. All you’ll need is a pair of tweezers and your regular soldering iron and solder. We provide detailed instructions on winding the toroids and soldering the capacitors. You get spare filter boards to experiment with.

Friendly Support is provided through a dedicated Open Research Institute Slack channel.

Instructions on how to join this community are here:

https://www.facebook.com/openresearchinstitute https://www.instagram.com/open_research_institute/
https://x.com/OpenResearchIns

Opportunities This Week at ORI

Greetings all!

What do you need help with this week?

Here’s some opportunities at ORI.

1) Pierre and Ahmet are looking for people to help with mobile app design on Ribbit

The Ribbit Radio app is in both Android and Apple testing. The updates to Rattlegram are incorporated and the app is functional on both platforms. We have had excellent response for test teams and things are moving forward.

To make the app as great as it can be, we could use some additional human resources for UX/UI/code development. If this sounds like something you are interested in, please join #ribbit on our Slack or write to me directly and I’ll get you in touch with the team leads. 

2) DEFCON volunteers for the booth/exhibit. We’ve got just enough people to cover it. It’s a great event. We have solid support from RF Village and we advertise to Ham Radio Village. If you have been sitting on the sidelines waiting for a chance to do something for ORI, this is the best event of the year. 

https://defcon.org/ for details about DEFCON 10-13 August 2023
https://wirelessvillage.ninja/ for details about our Village, RF Hackers Sanctuary.

3) FPGA designs for Haifuraiya and Neptune. Want to use MATLAB/Simulink, VHDL, and Verilog to make open source digital communications designs for aerospace, terrestrial, and drones? These designs run on updated FPGA stations in ORI Remote Labs, and everything is on the microwave amateur radio bands. When you see microwave frequencies mentioned, then it’s good to also say that “we use these bands or lose them”. We’ve got plenty to do. Get in touch on #haifuraiya or #neptune on Slack or to any ORI director. 

4) Meander Dipole construction phase. Project Dumbbell explores an overlooked HF antenna design. There’s been strong interest in these designs from multiple people (some of which are on this list), clubs, and organizations. We need to build the designs that MATLAB says look pretty good. Time to make it work over the air and write up some construction and measured performance articles. 
As always, there’s plenty more going on, but these projects have some specific needs, today. 

Thank you to everyone that supports our work. I’d like to especially thank the IEEE and ARRL for being excellent partners to ORI. 

-Michelle Thompson

Inner Circle Newsletter February 2023

Greetings all! Welcome to the February 2023 issue of the Inner Circle Newsletter from Open Research Institute.

Join the Inner Circle

Sign up for this newsletter at http://eepurl.com/h_hYzL

Thank you so much for your time, attention, and support. We appreciate you, we welcome your feedback, and we are dedicated to serving the community to the best of our abilities. You can get in touch with the ORI board of directors directly at hello@operesearch.institute.

A Puzzle Just For Fun

Here’s a puzzle. Chicken Nuggets have been on the menu at the international fast food chain McDonald’s since 1983.

If Chicken McNuggets are sold in packs of 6, 9, or 20, then what is the largest number of nuggets that cannot be ordered?

Answer is at the end of this newsletter!

Projects

Our volunteer teams have been busy and successful, and our project lineup has grown.

Regulatory Efforts: ORI works hard to promote and defend open source digital radio work. We do all we can to help move technology from proprietary and controlled to open and free. Our work on ITAR, EAR, Debris Mitigation, and AI/ML are where we have spent most of our time over the past two years. We were a member of the Technological Advisory Committee for the US Federal Communications Commission in 2022, and co-chaired the Safe Uses of AI/ML Subworking Group. We have received consistently positive reviews for all of our work, and there has been increasing use of the results.

Ribbit: this open source communications protocol uses the highest performance error correction and modern techniques available to turn any analog radio into an efficient and useful digital text terminal. No wires, no extra equipment. The only thing you’ll need to use it is the free open source Android or IoS app on your phone. Learn how to use this communications system and get involved in building a truly innovative open source tactical radio service by visiting https://ribbitradio.org

Join Ribbit mailing lists at: https://www.openresearch.institute/mailing-lists/

Amateur Satellite: ORI has the world’s first and only open source HEO/GEO communications satellite program, called Haifuraiya. We will demonstrate all working parts of the transponder project at DEFCON 31, where broadband digital communications and open source electric propulsion will be featured. Find out how to support or join this and other teams at https://openresearch.institute/getting-started

AmbaSat for 70 cm: We’ve redesigned the AmbaSat board to move it from 915 MHz to 70 cm and it will be flown on a sounding rocket this year. With increasing interest in LoRa for both space and terrestrial use, this has proven to be a popular and useful project. The design has been adapted for applications in India and Japan.

Opulent Voice: a digital protocol that seamlessly combines high fidelity voice and data, using modern forward error correction, authentication and authorization, and efficient minimum frequency shift keying modulation. Opulent Voice will be flown on a sounding rocket this year and it is the native digital uplink protocol for Haifuraiya. Completely open with the high quality voice we deserve to hear. Due to the bandwidth requirements of the 16kHz OPUS codec, Opulent Voice can be used on 70cm and above ham bands, or anywhere else where the modest bandwidth requirements can be met.

Remote Labs: We have two remotely accessible workbenches for FPGA development, with Xilinx 7000 and Xilinx Ultrascale+ development boards as the focus. We also have several SDRs and radio utility devices available through virtual machine access. The 7000 series development board has an Analog Devices ADRV9371 radio system attached, and that has enabled a number of open source FPGA products to be published. This is a unique resource that has produced a lot of good work and is constantly being improved and updated. In addition to the development boards, the laboratory has a network accessible spectrum analyzer, an oscilloscope with logic analyzer extension, power supplies, frequency and power counters, and dedicated human resources available to help students, volunteers, or professionals contribute to open source work. Help it be more useful by spreading the word about ORI Remote Labs.

Equipment available: https://github.com/phase4ground/documents/tree/master/Remote_Labs/Test_Equipment
How to get an account: https://github.com/phase4ground/documents/blob/master/Remote_Labs/ORI-New-User-Setup.md
Using FPGA Development Stations: https://github.com/phase4ground/documents/blob/master/Remote_Labs/Working-With-FPGAs.md

Versatune: amateur digital television next generation hardware and software product. It is open source and affordable. We have committed engineering resources to support Versatune and are very excited about how things are going. Some of the Versatune team will be at Hamvention 2023 in Xenia, OH, USA, and it will be represented at DEFCON in August 2023.

HF antennas: We have a novel foldable antenna design for space and terrestrial use. The hardware prototype will be demonstrated at DEFCON. This design manipulates radiation resistance to produce best-of-class results. Think you can’t do 160m without an enormous antenna? Think again.

HF QRP: Coming soon, an exciting HF QRP digital radio board and protocol. The hardware prototypes will be demonstrated at DEFCON. What might happen when we combine the HF digital radio with the novel foldable antenna? We think you’ll be delighted.

Battery Matching Curves: are you available to mentor a college student interested in learning how to match up charge and discharge curves from NiCd cells in order to create battery packs? These packs would then be tested and/or deployed in the field. Our student volunteer has collected the data and is looking to learn how to use Jupyter Notebooks to select the cells to create battery packs.

Logistics

We’re growing and adapting!

We will be changing our GitHub project name from Phase4Ground to Open Research Institute very soon. Phase4Space GitHub project will change to Haifuraiya, which is the program name for our HEO/GEO design. These changes better reflect the content and purpose of the 64 repositories that span everything from important historical archives to open source music to the most modern open source encoders available.

We have a very well-qualified applicant for our open board of directors position. We would like to invite interested community members to consider applying to ORI in order to expand the board beyond this filled position in order to take us from our current five members to seven. Given our continuing growth, a larger leadership team would ensure continued smooth operations. These positions are unpaid, engaging, and can be demanding. The most important skill set is a strong sense of ethics and service.

Fundraising and Grants

We’ve applied for the GitHub Accelerator Program (Remote Labs) and the IEEE Innovation Fund (Polar Codes in Ribbit). If you have a recommendation for ORI in terms of partnerships or collaboration, please let us know at hello@openresearch.institute

Support ORI financially directly through the website https://openresearch.institute. There is a PayPal donation widget at the bottom of almost every page. Donations can be directed to any project, or to general operations. ORI has a very low overhead, with most projects coming in under 5%.

Support our open source propulsion work and get a cool desk toy at https://us.commitchange.com/ca/san-diego/open-research-institute/campaigns/where-will-we-go-next

We’ve raised enough money to cover materials for machining the engine parts. The next step is to raise enough money to pay for the electronics. Please help spread the word!

Thanks to our wonderful community, we have employee matching in place at Microsoft and Qualcomm. If you have an employee matching program at your work, and you think ORI would fit in, please consider nominating us. Our EIN is EIN: 82-3945232

Events

Where can you meet up with ORI people?

QSO Today Ham Expo

We support and attend QSO Today Ham Expo, held online 25-26 March 2023. The theme of this event is “New License, Now What?” and focuses on people new to amateur radio.

Our page for QSO Today Ham Expo content is https://www.openresearch.institute/qso-today-ham-expo-technical-demonstrations/

IMS2023

Join us at the amateur radio social at the International Microwave Symposium (IMS2023) on Tuesday 13 June 2023 in San Diego, CA, USA at 6pm. It will be held in a beautiful outdoor venue with food and drink provided. The easiest way to register for this event is to purchase an exhibition badge and then sign up for the social. https://ims-ieee.org/ is the event website.

DEFCON

We are getting ready for our biggest event of the year. We have proposed an in-person Open Source Showcase to RF Village for DEFCON 31 in Las Vegas, Nevada, USA from 10 – 13 August 2023.

Our page for the event, with all the latest and greatest details, can be found at https://www.openresearch.institute/defcon/

Want to help at DEFCON? Please visit https://openresearch.institute/getting-started and let us know!

IWRC 2023

IEEE wants to bring together all participants to take full advantage of CHIPS Act funding. IEEE will have an Innovative Workforce Resources Conference in Little Rock, AR 13-14 September. There will be a reception at the Clinton Presidential Library, and attendees will enjoy the best BBQ in the country. The National Science Foundation requires that a certain percentage of funding has to be spent in states that don’t get their fair share of research money. The goal of this conference is to pull together small researchers from small business like ORI and do research, with Arkansas as a focus.

We couldn’t agree more. After all, we are putting a lot of time and energy into Remote Labs South, located just outside Little Rock, AR. Bringing innovative open source digital radio work to students, workers, and volunteers that need it the most simply makes sense. If you can attend IWRC 2023 and help represent ORI please get in touch. We will be reaching out to IEEE chapters in Arkansas as well.

Read about the CHIPS and Science Act here: https://en.wikipedia.org/wiki/CHIPS_and_Science_Act

Puzzle Solution

43 is the largest number of nuggets that cannot be ordered.

What is the largest number of McNuggets that you can’t buy with packs of 6, 9 and 20? After putting in their blood, sweat, and tears, the mathematicians found that the answer is 43. You cannot buy 43 nuggets with packs of 6, 9 and 20, but you can buy any amount larger than 43.

Please see Mike Beneshan’s excellent blog about this type of problem at https://mikebeneschan.medium.com/the-chicken-mcnugget-theorem-explained-2daca6fbbe1e

The other Non-McNugget numbers are 1,2,3,4,5,7,8,10,11,13,14,16,17,19,22,23,25,28,31,34, and 37.

Trivia: You can get 47 in two ways: 36+19+120 or 06+39+120.

We’ve used the McDonald’s version of the chicken nugget to present and frame this mathematical puzzle. Here’s a link about the history of this menu item: https://www.thrillist.com/news/nation/history-of-chicken-mcnuggets

Robert C. Baker invented the chicken nugget, among many other things. He was a true innovator of what can be fairly called “modern foods”. A brief wikipedia article about him can be found here: https://en.wikipedia.org/wiki/Robert_C._Baker

A song written about this remarkable inventor can be enjoyed at this link: https://youtu.be/OEa8wqv4QM0

Do you have an idea for an interdisciplinary puzzle for our next newsletter? We’d love to hear about it. Write ori@openresearch.institute

Until Next Time

Thank you so much for being part of our Inner Circle! You are the motivation for all of this work, provided to the general public for free. We believe it makes the world a better place.

HamCation 2023: Call for Open Research Institute Volunteers (booth/housing provided)

Greetings all!

If you are not familiar with the US amateur radio vendor fair HamCation, then please visit https://www.hamcation.com/

ORI has a booth in a very nice location right in front of the prize drawing area.

We have shown at HamCation for many years. In the past, we’ve collaborated with and supported exhibits and presentations from Society of Amateur Radio Astronomy (SARA), Tucson Amateur Packet Radio (TAPR), M17, DEFCON, GNU Radio, SBMS Beacon Project, and more.

We’ve organized four all-day forum sessions, recruited talks from all over the world, and welcomed people and projects that needed space to present their efforts to the large crowd in Orlando, FL. We’ve done a lot of demos, given out thousands of dollars of prizes and swag, and hosted several contests. The organizers have been deeply appreciative and delight to work with.

Aside from ARRL, ORI has fielded the most diverse and successful set of exhibits at HamCation in recent history.

It’s not a bad hamfest, as ham events go. Out of all of the ones in the US, this has been the best one for us.

Our plans were to show the Versatune project, which is a fantastic upgrade to a beloved ham DVB product, show Ribbit and Rattlegram, demonstrate Haifuraiya satellite work, introduce our sounding rocket work, and more.

Ribbit project team members cannot attend due to work and time conflicts. We’ll show through IEEE and potentially at Ham Expo.

Versatune has run into insurmountable delays and supply chain issues with Raspberry Pis. We looked at every possible alternative to get Versatune done faster with alternate parts, including rewriting the codebase for some very different off-the-reel parts that were available. We decided this was not a reasonable or achievable course of action. The original design is excellent and making progress – just not fast enough to show at HamCation in February 2023.

Haifuraiya (Open source HEO/GEO satellite) will show at QSO Today Ham Expo in March and through IEEE.

Sounding Rocket students cannot afford to come to HamCation, and we have similar supply chain problems there with Opulent Voice.

So – What do we have at HamCation?

We have a four-bedroom AirBNB very close to the fairgrounds reserved. Each room has a king sized bed. It has a large kitchen and very nice living room.

We have a booth at HamCation that is now completely open for anyone from ORI to use. I will do anything I can to help you showcase our work at HamCation. Do a shift at the booth, enjoy the very nice house, and promote our work.

More about this will be on Slack in the HamCation2023 channel.

Get in touch with me (cell phone number below) to take advantage. Deadline is 1 February.

If we have no staff, then we cancel and attempt to get the money back or donate the housing and booth space to a worthy group.

Please forward to anyone you think might be interested. What sort of work do we support? It’s outlined here:

https://www.openresearch.institute/your-project-is-welcome/

-Michelle Thompson
(858) 229 3399

Open Source COBS Protocol Design Document


Aside from the usual clk and rst signals, the only input to the entity is an AXI-Stream with a width of one byte. The data stream consists of frames encoded according to the rules described in Consistent Overhead Byte Stuffing by Stuart Cheshire and Mary Baker. These rules convert a known-length stream of bytes (a “frame”) with all values 0-255 into a slightly longer stream of bytes containing only values 1-255, allowing a byte with value 0 to be used unambiguously as a separator. It does this by dividing the stream into sequences of bytes. Each sequence must consist of zero to 253 non-zero bytes followed by a 0 byte or the end of stream, or 254 non-zero bytes. It is then encoded as the sequence length (1 to 254) followed by the non-zero bytes.

Read the rest at:

https://github.com/phase4ground/adi_adrv9371_zc706/blob/adrv9371-zc706-dvbs2-integ/design_docs/cobs_decoder/COBS_dec-Entity-Design.md

QoS: Call for Input

We’re moving into the challenge of multiplexing on the transponder with a goal of delivering Quality of Service (QoS) metrics and policies.

This is “how do the uplink packets get properly prioritized on the downlink, to make the most of limited resources”.

These resources are spectrum, power, and time.

QoS doesn’t make any of our communications channels go faster. This is a common misconception about QoS. Here’s some descriptions from conversations this week. I would like to hear more opinions about QoS in general, and any specific requirements that people on this list might have.

Kenneth Finnegan writes,

“In #networking it’s common to forget that QoS is mainly about deciding which packets you’d rather drop first.

If you don’t like that idea, then you just need to pony up and throw more capacity at the problem.”

Adam Thompson continues,

“In the presence of a pizza that’s not big enough for all the hungry people, QoS inhibits less-important pizza eaters. This lets more-important eaters-of-pizza get more pizza than their fair share, at the expense of the less-important eaters.

“In the presence of a pizza that’s not big enough for all the hungry people, QoS inhibits less-important pizza eaters. This lets more-important eaters-of-pizza get more pizza than their fair share, at the expense of the less-important eaters.

QoS never (ever!) makes the pizza bigger – if you need more pizza, you must still bake or buy more, or someone’s going to go hungry!

Complex QoS systems might let you differentiate between e.g. crust and topping and permit cutting the pizza into bizarre topographies/topologies, but still can’t make the pizza any bigger.

Finally, if there is enough pizza for everyone, QoS doesn’t do anything useful.”

If this last part sounds familiar, then you’re not alone. QoS often doesn’t do anything useful… in a resource rich environment. This may be the main reason that we sometimes hear that QoS is a “failure”, that it’s “never used”, or “why bother for hams since hams don’t care about this subject at all”.

It is true that most amateur communications are made with acres and acres of spectrum, with a very generous power limit (although you are supposed to use the minimum required power) and no time limits on how often you can try to make a contact.

When we talk about microwave broadband digital communications, it’s a different situation. And, with space channels, there are constraints. We have less bandwidth to work with because we’re on a sub-band. We have latency, which is non-trivial for GEO or beyond. We have power concerns and pointing requirements.

“Adaptive” QoS that does nothing until congestion forces some decisions, at which time we sort with respect to SNR, has been our baseline.

What we want to do when constraints are hit is what we need to better define. Right now, we have a whiteboard design (summarized above) and a paper about Adaptive Coding and Modulation (ACM) that was published in AMSAT-DL and AMSAT-UK Journals.

We have the implementation guidelines from GSE as well, which address QoS and show how to set up queues.

With a controllable downlink going out over the air, and a defined uplink protocol, now is the time to work on exactly how to multiplex the traffic. Evariste asked about this exact thing less than a week ago at the FPGA meetup.

Decisions about QOS heavily affect the central part of the design, so let’s get this right.

Do you have experience implementing QoS policies? Do you have experience with bad QoS policies as a consumer? Do you have an idea about what you want to see this design do?

Well, you’re in the right place, and we’d love to hear what you have to say about it.

Participate at https://openresearch.institute/getting-started

AI vs. Human: ChatGPT vs. ORI Open Source Designers

Greetings all,

You know that ORI has been active in a variety of regulatory work for several years now. One of those areas has been in AI/ML and the effect on communications. We served on the US FCC TAC in 2022, have presented and written on the subject, and are working towards an AI/ML Handbook for Amateur Radio.

You may have seen news about OpenAI GPT, or ChatGPT.

https://openai.com/api/

There’s a lot of people testing this chatbot out for reverse engineering and in writing software. There’s been some successes in cases where the model would have had access to code or documentation about protocols, observations, or technical behavior in order to train, and requests match up well with the models. 

For example, a friend asked the chatbot to create a Python script to access the webcam on their computer, and they shared a still image from the resulting feed. Another example from another friend resulted in better reverse engineering results than they had gotten with either IDA or Ghidra over many weeks.

So, how does ChatGPT handle VHDL?

We have something specific to compare against, since we just completed a COBS decoder in VHDL for our open source HEO/GEO transponder work for #Haifuraiya.

Let’s start off simple. Here’s the first dialogue with the chatbot, and the results.

-=-=-=-=-=-=-=-=-=-=-=-=-=-

Abraxas3d: Design a COBS decoder in VHDL

Sure, here’s an example of a COBS decoder in VHDL:

library IEEE;
use IEEE.STD_LOGIC_1164.ALL;

entity COBS_decoder is
  Port (
    input_data : in std_logic_vector;
    decoded_data : out std_logic_vector
  );
end COBS_decoder;

architecture Behavioral of COBS_decoder is
  — Declare a variable to keep track of the current index
  — in the input and output data streams
  variable current_index : integer := 1;
 
  — Declare a variable to store the length of the
  — run of zeros in the input data
  variable zero_run_length : integer := 0;
begin
  — Iterate over the input data
  for i in input_data’range loop
    — If the current input value is a zero, increment
    — the zero run length variable
    if input_data(i) = ‘0’ then
      zero_run_length := zero_run_length + 1;
    — Otherwise, the current input value is not a zero,
    — so we’ve reached the end of the zero run
    else
      — Set the decoded value at the current index to
      — the length of the zero run
      decoded_data(current_index) := conv_std_logic_vector(zero_run_length, 8);
     
      — Increment the current index and reset the zero
      — run length for the next iteration
      current_index := current_index + 1;
      zero_run_length := 0;
    end if;
  end loop;
end Behavioral;

This code decodes the input data using the COBS (Consistent Overhead Byte Stuffing) algorithm, which involves replacing runs of zeros in the input data with a single byte that indicates the length of the zero run. For example, the input ‘101001000’ would be decoded as ‘103101’.

This decoder iterates over the input data and maintains a variable zero_run_length that is incremented for each zero in the input data. When a non-zero value is encountered, the length of the zero run is written to the output data and the zero_run_length variable is reset.

I hope this helps! Let me know if you have any other questions.”

-=-=-=-=-=-=-=-=-=-=-=-=-=-

It knew what COBS meant. It produced code, with comments, and a brief “design document”, with examples.

The code produced is not licensed or cited.

Our open source HEO transponder project uses AXI-based blocks in the FPGA. So, let’s add AXI to the request.

-=-=-=-=-=-=-=-=-=-=-=-=-=-

Abraxas3d: Design a COBS decoder with AXI interface in VHDL

Sure, here’s an example of a COBS decoder with an AXI interface in VHDL:

library IEEE;
use IEEE.STD_LOGIC_1164.ALL;
use IEEE.NUMERIC_STD.ALL;

— AXI interface definitions
library unisim;
use unisim.vcomponents.all;

entity COBS_decoder is
  Port (
    AXI_IN  : in  AXI4Stream;
    AXI_OUT : out AXI4Stream
  );
end COBS_decoder;

architecture Behavioral of COBS_decoder is
  — Declare a variable to keep track of the current index
  — in the input and output data streams
  variable current_index : integer := 1;
 
  — Declare a variable to store the length of the
  — run of zeros in the input data
  variable zero_run_length : integer := 0;
begin
  — Iterate over the input data
  for i in AXI_IN.data’range loop
    — If the current input value is a zero, increment
    — the zero run length variable
    if AXI_IN.data(i) = ‘0’ then
      zero_run_length := zero_run_length + 1;
    — Otherwise, the current input value is not a zero,
    — so we’ve reached the end of the zero run
    else
      — Set the decoded value at the current index to
      — the length of the zero run
      AXI_OUT.data(current_index) := conv_std_logic_vector(zero_run_length, 8);
     
      — Increment the current index and reset the zero
      — run length for the next iteration
      current_index := current_index + 1;
      zero_run_length := 0;
    end if;
  end loop;
 
  — Set the valid and last flags in the output AXI stream
  AXI_OUT.valid <= ‘1’;
  AXI_OUT.last  <= ‘1’;
end Behavioral;

This code is similar to the previous example, but it uses an AXI (Advanced eXtensible Interface) interface for the input and output data. The AXI interface is a standard interface used in many FPGA designs, and it provides a way to stream data into and out of the decoder.

In this code, the input data is read from the AXI_IN.data port, and the decoded output is written to the AXI_OUT.data port. The valid and last flags are also set in the output AXI stream to indicate that the data is valid and that it is the last data in the stream.

I hope this helps! Let me know if you have any other questions.

-=-=-=-=-=-=-=-=-=-=-=-=-=-

It knows about the previous request and updated the design. No license.

Here’s a review of the COBS implementation from Paul Williamson KB5MU.

“I don’t know what this is, but it isn’t a COBS decoder with AXI interfaces.

It does seem at first glance to be some sort of thing with AXI interfaces, but it does not implement an AXI interface at all. It just relies on a (possibly imaginary) library type called AXI4Stream that somehow magically does AXI interfaces, in a way that’s both implausibly smart and inexplicably dumb. I think the classic phrase “not even wrong” applies here.

The AXI4Stream object apparently has a member .data that is an array of bytes, which might make sense if the entire AXI transfer is being treated as a single entity here. The code iterates through the input .data using the ’range attribute, as if the AXI4Stream object has a defined fixed transfer length.

Which it can’t have, if it’s a general purpose AXI stream implementation.

So, if this was ever anything real, it must have been a special purpose AXI implementation with a fixed transfer length. Assuming that the AXI4Stream .data actually works that way, the entity does
do some sort of transformation on the input data to create the output data.

We asked for that to be a COBS decoder, but the function that it actually implements bears only the slightest resemblance to a COBS decoder. What it actually does is output a stream of words that are the lengths of the runs of zeroes in the input data. Nonzero data does not get passed through at all.

Instead, a run of nonzero bytes gets translated into a run of zeroes, as if two adjacent nonzero bytes meant nothing but a zero-length run of zeroes.

Here’s an example of what this code seems to do:

  Input  .data:  1 2 3 4 0 0 0 0 1 2 3 4
  Output .data:  0 0 0 0         4 0 0 0

That’s certainly not a COBS decoder, or even anything useful at all.

Note that the output is variable length, but never longer than the input.
We had to assume that the AXI4Stream object had a fixed .data size to get this far, but now it has to have a variable data size for the output.

Supposing we had successfully suspended disbelief up to here, we now examine the final two lines of code in the Behavioral architecture. It sets the .valid and .last members of the AXI_OUT port to ‘1’.

That makes absolutely no sense if it’s supposed to encapsulate an entire AXI stream transfer. Those signals only make sense if we’re treating one word at a time, as you’d expect to see in a normal, general-purpose AXI stream object.

The extremely verbose commenting style in this code suggests that the original source material was from an introductory tutorial. Maybe the AI has been tuned to favor heavily commented code, and ends up picking up partially completed junk from the middle of tutorials?
Anyhow, this is not an example of automated programming in response to a high-level query. This is gibberish that succeeds only in having a superficial resemblance to the code requested.”

So, does this work?

Let’s try it out in the lab!

The first thing we notice is that there is an obvious syntax error with a missing semicolon. Aside from that, there is no AXI4Stream port type. It’s not recognized. Vivado appears to be disappointed in this file, and wants little to do with this code. This is where we should stop, but I spent some time looking to see if the ports were at least close to being declared correctly.

The model appears to have taken some custom or maybe enumerated type from somewhere, and come up with a custom AXI4Stream type. This is not recognized by the unisim library right off the bat, and that’s the sort of thing that automated code writing needs to get right.

Let’s look at the code written by humans from ORI. The decoder can be found here:

https://github.com/Abraxas3d/fpga_cores/blob/master/src/decoder.vhd

-=-=-=-=-=-=-=-=-=-=-=-=-=-

— Company: Open Research Institute, Inc.
— Engineer: Skunkwrx, Abraxas3d
— Design Name: COBS protocol decoder
— Module Name: decoder – Behavioral
— Project Name: Phase 4 “Haifuraiya”
— Target Devices: 7000 Zynq
— Tool Versions: 2021.1
— Description: COBS protocol decoder.

— Additional Comments: This work is Open Source and licensed using CERN OHL v2.0

library IEEE;
use IEEE.STD_LOGIC_1164.ALL;

use IEEE.NUMERIC_STD.ALL;

–Entity Declaration
entity decoder is
    Port ( rst      : in STD_LOGIC;
           clk      : in STD_LOGIC;
           s_tdata  : in STD_LOGIC_VECTOR (7 downto 0);
           s_tlast  : in STD_LOGIC;
           s_tvalid : in STD_LOGIC;
           s_tready : out STD_LOGIC;
           m_tdata  : out STD_LOGIC_VECTOR (7 downto 0);
           m_tlast  : out STD_LOGIC;
           m_tvalid : out STD_LOGIC;
           m_tready : in STD_LOGIC);
end decoder;

–Architecture
architecture Behavioral of decoder is

— internal copy of s_tdata
    signal input_data          : STD_LOGIC_VECTOR (7 downto 0);

    — s_tdata delayed by one clk where s_tvalid is high
    signal input_data_d        : STD_LOGIC_VECTOR (7 downto 0);

    — internal version of s_tlast
    — not used for anything
    — We create our own m_tlast from the COBS framing instead
    signal s_tlast_i           : STD_LOGIC;

    — internal version of input handshaking signal s_tvalid
    signal s_tvalid_i          : STD_LOGIC;

    — s_tvalid delayed by one clk
    — thus, a version of s_tvalid aligned with input_data_d
    signal s_tvalid_i_d        : STD_LOGIC;

    — s_tvalid delayed by two clks
    — thus, a version of s_tvalid aligned with output_data
    signal s_tvalid_i_d_d      : STD_LOGIC;
   
    — countdown of bytes in this sequence
    — loads from input_data_d when it represents the frame count
    —   as determined by signal counter_load
    — contains the count while m_tdata contains the implied 0 at
    —   the end of a sequence, or the next count that replaced it
    — counts down thereafter, to contain 1 when the last non-zero
    —   byte of the sequence is on m_tdata
    — allowed to count down to 0, but not beyond
    signal count               : STD_LOGIC_VECTOR (7 downto 0);

— enable to load count from input_data_d on this clk edge
— two cases detected:
—    * first valid non-zero byte after a frame separator
—    * first valid byte after count is exhausted
— allowed to be high for multiple cycles
    signal counter_load        : STD_LOGIC;

    — counter_load delayed by one clk where s_tvalid is high
    — used to identify the first valid data byte of any sequence,
    —   for purposes of computing m_tvalid (via pre_tvalid)
    signal counter_load_d      : STD_LOGIC;

    — detection of a valid frame separator (zero) byte in input_data_d
    signal frame_sep           : STD_LOGIC;

    — frame_sep delayed by one clk where s_tvalid is high
    — used to compute counter_load
    — used to compute rising edge of pre_tvalid
    signal frame_sep_d         : STD_LOGIC;
   
    — frame_sep_d delayed by an additional clk (not depending on s_tvalid)
    — used to find the first non-zero byte of the new frame
    signal frame_sep_d_d       : STD_LOGIC;
       
    — move the frame_sep signal that occurred during m_tready low
    — out to the first cycle when m_tready is high again
    signal use_saved_frame_sep : STD_LOGIC;

    — flag to remember that the frame count for this sequence was 255,
    —   to handle the special case that such a sequence does not have
    —   an implied zero byte at the end.
    — set when loading count with 255
    — cleared when the counter is reloaded with anything else
    signal case_255            : STD_LOGIC;

    — internal version of m_tdata output
    signal output_data         : STD_LOGIC_VECTOR (7 downto 0);

    — internal version of m_tlast output
    — high when the last byte of a frame is valid on m_tdata
    signal m_tlast_i           : STD_LOGIC;

    — delayed versions of m_tlast
    signal m_tlast_i_d         : STD_LOGIC;
    signal m_tlast_i_d_d       : STD_LOGIC;

    — intermediate result for m_tvalid.
    — high across all data bytes of each sequence on m_tdata
    — does not go low for bytes on m_tdata corresponding to
    —   bytes invalidated by s_tvalid.
    signal pre_tvalid          : STD_LOGIC;

    — internal version of m_tvalid output.
    — pre_tvalid with periods of low s_tvalid_d_d punched out
    signal m_tvalid_i          : STD_LOGIC;

    — internal version of m_tready input
    — also the internal version of s_tready output
    — passes through m_tready to s_tready with no clk delays
    signal m_tready_i          : STD_LOGIC;

    — constant byte value 0xFF, for comparison purposes
    signal all_ones            : STD_LOGIC_VECTOR(input_data’range) := (others => ‘1’);

    — constant byte value 0x00, for comparison purposes
    signal all_zeros           : STD_LOGIC_VECTOR(input_data’range) := (others => ‘0’);

begin

    — asynchronous assignments
   
    frame_sep <= ‘1’ when input_data_d = all_zeros and s_tvalid_i_d = ‘1’
                else ‘0’;
   
    m_tlast_i <= ‘1’ when ((frame_sep = ‘1’ and m_tvalid_i = ‘1’ and m_tready = ‘1’))
                else ‘0’;
   
    counter_load <= ‘1’ when (input_data_d /= all_zeros and frame_sep_d = ‘1’ and s_tvalid_i_d = ‘1’)   — start of frame
                          or (to_integer(unsigned(count)) = 1 and s_tvalid_i_d = ‘1’)   — start of next sequence in frame
                else ‘0’;
   
    m_tvalid_i <= ‘1’ when ((pre_tvalid = ‘1’ and s_tvalid_i_d_d = ‘1’    — usual case, if input_data was valid
                        and not (to_integer(unsigned(count)) = 1 and s_tvalid_i_d = ‘0’)) — defer last byte; might be m_tlast
                      or (pre_tvalid = ‘1’ and to_integer(unsigned(count)) = 1
                        and s_tvalid_i_d = ‘1’ and s_tvalid_i_d_d = ‘0’)) — pick up that deferred last byte
                else ‘0’;
               
   
    s_tready <= m_tready_i;
    m_tdata <= output_data;
    input_data <= s_tdata;
    s_tvalid_i <= s_tvalid;
    m_tready_i <= m_tready;
    m_tvalid <= m_tvalid_i;
    m_tlast <= m_tlast_i;
   
— processes

    set_case_255 : process (rst, clk)
    begin
        if rst = ‘1’ then
            case_255 <= ‘0’;
        elsif rising_edge(clk) and m_tready_i = ‘1’ then
            if counter_load = ‘1’ and input_data_d = all_ones then
                case_255 <= ‘1’;
            elsif counter_load = ‘1’ and input_data_d /= all_ones then
                case_255 <= ‘0’;
            end if;
        end if;
    end process set_case_255;

   
    delay_s_tvalid : process (rst, clk)
    begin
        if rst = ‘1’ then
            s_tvalid_i_d <= ‘0’;
            s_tvalid_i_d_d <= ‘0’;
        elsif rising_edge(clk) and m_tready_i = ‘1’ then
            s_tvalid_i_d <= s_tvalid_i;            
            s_tvalid_i_d_d <= s_tvalid_i_d;
        end if;
    end process delay_s_tvalid;
   
   
   
    create_pre_tvalid : process (rst, clk)
    begin
        if rst = ‘1’ then
            counter_load_d <= ‘0’;
            pre_tvalid <= ‘0’;
        elsif rising_edge(clk) and m_tready_i = ‘1’ then
            if s_tvalid_i_d = ‘1’ then
                counter_load_d <= counter_load;
                if (frame_sep_d_d = ‘1’ and frame_sep_d = ‘0’)            — normal last byte of frame
                or (counter_load_d = ‘1’ and frame_sep_d = ‘0’)           — normal first byte of a sequence
                then      
                    pre_tvalid <= ‘1’;
                end if;
            end if;
            if frame_sep = ‘1’
            then
                pre_tvalid <= ‘0’;
            end if;
            if counter_load = ‘1’ and case_255 = ‘1’ then
                pre_tvalid <= ‘0’;
            end if;
        end if;
    end process create_pre_tvalid;
     
     

    delay_m_tlast_i : process (rst, clk)
    begin
        if rst = ‘1’ then
            m_tlast_i_d <= ‘0’;
            m_tlast_i_d_d <= ‘0’;
        elsif rising_edge(clk) and m_tready_i = ‘1’ then
            m_tlast_i_d <= m_tlast_i;
            m_tlast_i_d_d <= m_tlast_i_d;
        end if;
    end process delay_m_tlast_i;

    set_counter : process (rst,clk)
    begin
        if rst = ‘1’ then
            count <= (others => ‘0’);
            frame_sep_d <= ‘0’;             frame_sep_d_d <= ‘0’;         elsif rising_edge(clk) and m_tready_i = ‘1’ then             frame_sep_d_d <= frame_sep_d;             if s_tvalid_i_d = ‘1’ then                 frame_sep_d <= frame_sep;                 if counter_load = ‘1’ then                     count <= input_data_d;                 elsif count /= all_zeros                 then                     count <= STD_LOGIC_VECTOR(unsigned(count) – 1);                 end if;             end if;         end if;     end process set_counter;                 create_output : process (rst, clk)     begin         if rst = ‘1’ then             output_data <= (others => ‘0’);
        elsif rising_edge(clk) and m_tready_i = ‘1’ then
            if counter_load = ‘1’
            then
                output_data <= all_zeros;
            elsif s_tvalid_i_d = ‘1’ then
                output_data <= input_data_d;                
            end if;
        end if;
    end process create_output;
   
 
   
    selective_delay_of_input_data : process (rst,clk)
    begin
        if rst = ‘1’ then
            input_data_d <= all_zeros;
        elsif rising_edge(clk) and m_tready_i = ‘1’ then
            if s_tvalid_i = ‘1’ then
                input_data_d <= input_data;
            end if;    
        end if;
    end process selective_delay_of_input_data;
   

end Behavioral;

-=-=-=-=-=-=-=-=-=-=-=-=-=-

This codebase doesn’t include just the source code, but also a testbench file, a design document, timing diagrams, a Python notebook that creates test vectors, and Python code that compares results produced by the testbench that uses the test vectors.

None of this sort of thing is produced by ChatGPT.

There is code in some languages for some functions that can be correctly written by AI at this point.

This is a situation similar to algorithmic musical composition. Algorithms can come up with useful ideas, motifs, sketches, or traverse a search space more quickly than a human. They can help a composer, but do not replace one. Algorithms can produce some sparkling gems of ideas. These are fresh cuts and views. This is mixed in with a lot of music that is just plain wrong.

If your programming job happens to be in a well-defined area that is easily automated, then you do have something to worry about today.

All jobs are a target for eventual automation with AI/ML. Yes, all of them. As AI/ML becomes more capable, it will automate even things like testbench writing (HDL Coder already does something like this) and support code (like a Python notebook that creates a solid set of test vectors for a testbench) and design documents. All of us should be aware of what we do being replaced by an algorithm some number of tomorrows in the future.

That day is not yet “today” with Chat GPT, when it comes to writing #VHDL.

What do you think? We’re interested in your experience and opinions with AI/ML writing code.

DEFCON 30 Activity Report

Open Research Institute’s amateur radio open source showcase at the annual hacker convention DEFCON was located in RF Village (RF Hackers Sanctuary) in The Flamingo Hotel. A volunteer crew of seven people from three US states staffed the exhibit that ran from Friday 12 August to Sunday 14 August 2022.

RF Village hosts a very popular wireless Capture the Flag (CTF) event. It is a top tier contest at DEFCON and the winners are recognized at closing ceremonies. RF Village also has a peer-reviewed speaking track. See previous talks in the YouTube playlists here: https://www.youtube.com/c/RFHackersSanctuary

RF Village generously offers space for exhibits from the community. For 2022, the exhibits included Open Research Institute, Kent Britain PCB Antennas, Alexander Zakharov (ALFTEL Systems Ltd.), and Starlink (SpaceX). Starlink brought two stations and allowed visitors to experiment with network and physical security.

Total attendance at DEFCON 30 was estimated at 27,000. Conference events were held in the new Caesar’s Forum + Flamingo, Harrah’s, and Linq convention centers.

Open Research Institute’s exhibit had multiple parts. The entry to the exhibit was a poster session. Posters presented were ITAR/EAR Regulatory Relief for Amateur Satellite Service, Libre Space Foundation’s Manifesto, Authentication and Authorization Protocol for Amateur Satellites, and the Ribbit Project Introduction and Architecture. Ribbit allows an amateur operator to type in SMS messages on an Android app. Each SMS message is converted to digital audio tones. The tones are played out the phone’s speaker into the microphone of an amateur radio handheld or mobile rig. This can turn any analog HT into part of a digital messaging network. The app can do point-to-point communications and also has a repeater mode. More open source implementations are planned. 

All posters were enthusiastically well-received. Specific technical feedback was received on the Authorization protocol that will improve the design. There will be a presentation about the Authorization and Authentication protocol at the September 2022 QSO Today Ham Expo.

Visitors understood the purpose and potential of Ribbit and could download the free open source Android app from a QR code on the poster. The code was also on the Ribbit stickers handed out at the booth. All 300 of the Ribbit stickers were handed out by Sunday morning. 

Find the Ribbit “Rattlegram” application here: https://play.google.com/store/apps/details?id=com.aicodix.rattlegram

There will be a Ribbit presentation at the September 2022 QSO Today Ham Expo.

The ITAR/EAR Open Source amateur satellite regulatory relief poster garnered a lot of attention. A very large fraction of DEFCON attendees are familiar with ITAR/EAR, which are a set of regulations that govern the way we design communications satellites in the USA. People that read the poster at DEFCON understood and appreciated the value of the work, which provides long-awaited regulatory relief for the amateur satellite service. The poster presentation led to an invitation to Policy Village Sunday afternoon for a panel session hosted by the Office of the National Cyber Director. Summary of that session can be found in ORI’s 19 August 2022 project report. The ITAR/EAR poster will be part of the Projects Exhibits at the September 2022 QSO Today Ham Expo.

Foot traffic flowed past the posters and into the live demonstrations.

The first live demonstration visitors encountered was from OpenRTX (https://openrtx.org). This demonstration used a tablet computer running OpenWebRX to display modified MD-380 transmissions. Visitors could use headphones to hear live transmitted signals. Posters at the table explained the modifications required to implement the M17 protocol on the MD-380 and described the motivation and value of the work, with an emphasis on the use of the free and open CODEC2 voice codec. The use of CODEC2 in M17 replaces the proprietary AMBE codec found in every other digital voice protocol for VHF/UHF ham radio. There was strong interest in both the M17 and the DMR work from OpenRTX, broad understanding of why proprietary codecs are not ideal, and consistently positive feedback. 500 OpenRTX business cards were printed with QR codes for the OpenRTX website and nearly all of them were handed out.

The second demonstration was Opulent Voice. This is a high bitrate open source voice and data protocol. It’s designed as the uplink protocol for ORI’s amateur satellite program. The Authentication and Authorization fields are built in and sending data does not require a separate packet mode. The baseline voice codec for Opulent Voice is OPUS at 16 kbps. Higher bitrates are a build-time option. For the DEFCON demonstration, Opulent Voice was transmitted from an Analog Devices PLUTO SDR and received on an RTL-SDR/Raspberry Pi. Visitors could use headphones to listen to the received audio. The modulator and demodulator code can be found at https://github.com/phase4ground/opv-cxx-demod. 300 custom art stickers for Opulent Voice were ordered and all were handed out.

The two demonstrations compared and contrasted voice quality (3.2 kbps vs 16+ kbps), regulatory limitations (VHF/UHF vs. microwave), and approach to framing (P25 style vs. COBS/UDP/RTP).

The next station had stickers, buttons, patches, ORI’s Tiny CTF, Haifuraiya proposal printouts, and a Trans-Ionospheric badge display.

ORI’s “Tiny CTF” was a hidden web server, accessible from the wifi access point located at the OpenRTX demonstration. The access point allowed people to view the OpenWebRX display directly on their connected devices. Participants that found the hidden web server and then blinked the LEDs on a certain piece of equipment at the booth received a prize.

Haifuraiya (High Flyer) is an open source highly elliptical orbit communications satellite proposal. Microwave amateur band digital communications at 5, 10, and 24 GHz are proposed. Transmissions are frequency division multiple access Opulent Voice up, and DVB-S2/X time division multiplexed down. A presentation about this proposal will be at the September 2022 QSO Today Ham Expo.

Based on the feedback about the amateur radio themed Trans-Ionospheric badge, ORI will update and build another round of these badges. Round one of the Trans-Ionospheric badge was a very successful open source project fundraiser. The badges have been enduringly popular in the community, and they can serve as radio peripherals that display radio link and payload health over bluetooth. The artistic design of the badge is based on the front panel of the Zenith Trans-Oceanic radio. Find out more about the Trans-Ionospheric badge here: https://www.openresearch.institute/badge/

There were very high levels of interest, enthusiasm, and positive feedback throughout the weekend. Friends from Ham Radio Village and Aerospace Village visited the exhibit and shared their experiences. The organizational support from RF Village leads was excellent. ORI will return to DEFCON in 2023 with another round of open source digital radio demonstrations. 

Amateur radio experimenters and their projects are welcome at Open Research Institute. Individuals can join for free at https://www.openresearch.institute/getting-started/. Projects can apply at https://www.openresearch.institute/your-project-is-welcome/

Opulent Voice – digital voice and data protocol update

This Opulent Voice sticker is available from ORI at events around the world.

Opulent Voice is an open source high bitrate digital voice (and data) protocol. It’s what we are using for our native digital uplink protocol for ORI’s transponder project. Opulent Voice is also looking pretty darn good for terrestrial.

Here is an audible example of the Opulent Voice audio quality under ideal conditions. Each file is about 37 seconds long. It starts with a short musical intro, and the rest is the beginning of the audio track from one of Michelle’s conference talks. These were originally recorded with mid-range podcasting studio gear. The recording was converted to a signed 16-bit PCM raw file, which has been re-converted to a standard WAV file so you can play it easily, MDT-short.wav

Original recording


This file was then run through opv-mod to create a file of baseband samples, which was then piped to opv-demod, which created an output file of signed 16-bit PCM. That file was converted to WAV file MDT-short.demod.wav

Original recording modulated and then demodulated through Opulent Voice.


We expect to present a nice demo at DEFCON in August 2022 and at the QSO Today Ham Expo in September 2022.

We’ll be using COBS protocol within Opulent Voice. If you’re unfamiliar with COBS, please read about it here: 

https://en.wikipedia.org/wiki/Consistent_Overhead_Byte_Stuffing

Authentication and authorization is built in and optional. There is no separate “packet mode”. Things are designed to “just work” and get out of your way whether or not you’re sending voice or data. 

Opulent Voice is designed to where you can use even higher bitrate OPUS codecs if you wish. This will most likely be a build option and not a run-time option, but if a run-time option is something you want to work on, speak up! Let’s see what we can accomplish.

Originally based on Mobilinkd codebase that implements M17, the Opulent Voice development implementation can be found here:

https://github.com/phase4ground/opv-cxx-demod

Initial demos will be on a HackRF/PortaPack on the 1.2 GHz ham bands. 

Thank you to OpenRTX for help with troubleshooting the audio quality on the PortaPack. In order to have a good demo, basic FM transmit from the microphone needs to work. The audio quality is pretty bad (this was a surprise) with the stock application, so we’ve been spending some time with the Mayhem codebase, the microphone transmit app, and the driver for the audio codec in order to get it sounding like it should. This needs to happen before we publish an app for the PortaPack. 

Synthesized audio from the HackRF/PortaPack sounds clear and wonderful. It’s just the microphone that is splattery and overdriven. 

ORI’s Slack channel can be found at https://phase4ground.slack.com/

The authentication and authorization work is in #aaaaa
Opulent Voice work is in #opulent-voice

Thank you to everyone supporting the work!

-Michelle Thompson

Video of Working Meeting on Higher Bitrate M17

Specification of M17:

https://spec.m17project.org/

P4DX architecture document:

https://github.com/phase4ground/docum…

M17 is P4DX native digital uplink protocol.

There are at least three use cases of M17.

One, 9600 bps voice for VHF/UHF.

Two, the idea of 9600 bps data or packet mode, also VHF/UHF.

Three, higher bitrate mode for microwave.

There is a data type specifier in the current specification. Reserved protocol types are RAW, AX.25, APRS, 6LoWPAN, IPv4, SMS, and Winlink.

What we’re talking about today is what, if anything, needs to be added to the specification in order to enable high bitrate operation for microwave, and also to figure out if anything needs to be done for IP over M17 or M17 over IP.

From Slack:

Ron

What needs to be defined is how to do IP over M17. In the M17 specification, there’s a protocol identifier for IPv4, but that’s it.

And here is a review of the conversation from 2021. This was the starting point for the conversation in this video recording.

Ron

M17 supports IPv4, but I’m not exactly sure how. The M17 specification seems pretty vague on that particular point

Howie

Assume we consider M17 stream mode operating in an FDM manner with a receiver for each uplink channel. Each channel can be given a GSE label that could map to an uplink center freq. The 4FSK modulated data is demodulated but not decoded. Instead, the data streams are clocked into individual buffers and used to generate the GRE frames. The idea is to keep the M17 frames intact so that on the ground earth station the demodulated data is identical to the uplinked frame which can be processed by the existing M17 decoder software. You listen to a channel by selecting the label for the stream you want to listen to. The limiting factor becomes how fast you can assemble the uplink channels into GRE frames.

I don’t think there is any need or desire to use anything other than native M17 on the uplink. While GSE is normally used for IP transport I think we could put the M17 frames into the GSE data field. At that point the only overhead is on the downlink with the addition of the GSE headers and LSF management. I have not looked closely at the sizes of the required fields are or how much processing it would take to multiplex multiple uplink streams into a composite downlink. At this point I am just brainstorming.

Anshul

looks like we don’t need IP as an intermediate step. I agree with @ab2s that there is no need to use anything other than native M17 on the uplink. GSE should encapsulate M17 frames and produce BBFRAME as it normally does for IP packet.

It implies we will be not using any IP stream/packets on uplink. Everything uplink will be M17 based.

Do you see any concerns here . Else, I will proceed with implementation of GSE block in firmware keeping this decision in mind.

Consensus on:

  1. Validity of use case for higher bitrate M17 for P4DX uplink.
  2. IP over M17 could use an example (as could all the types in this field), but the type field indicating IPv4 is sufficient for carrying IPv4 within M17. M17 packet is small enough to where IP fragmentation will probably occur.
  3. M17 over IP is defined in the appendix, it works as implemented in the reflector network, and did not appear to need any additional work.
  4. P4DX could provide a spigot of M17 uplinks over IP, using the protocol in the appendix, as a Groundsat feature. This would not affect the air interface.
  5. We discussed the XOR with random data aspect (covert SPARROW channel here? Yes/maybe if there’s a known message)
  6. Discussed asking for a P4 Type Field Indicator. Smart receivers won’t need this, but it would allow people to move between 9600 bps M17 and higher bitrate M17.

HamCation 2022 Report

HamCation 2022 Report

Paul Williamson (Remote Labs), Douglas Quagliana (P4DX), Michelle Thompson (ORI), Ed Wilson (M17), and Steve Miller (M17) represented the breadth of projects from Open Research Institute at HamCation 2022.

ORI’s “Tonight’s The Night: SDRs are HOT” booth made its first appearance in nearly two years. Available at the booth were stickers, pins, patches, shirts, consulting, and project updates. ORI’s “extra chair” seating area was appreciated by volunteers and visitors alike. Booth visitors heard about the successful DVB-S2X modem work from ORI and progress on the end-to-end demo of the entire satellite transponder chain. At Open Research Institute, it doesn’t work until it works over the air. Due to the efforts of a truly wonderful international open source team, the custom FPGA code is coming together very well, and Remote Labs continues to evolve. The Phase 4 Digital Multiplexing Transceiver project is on budget, on track, and highly likely to succeed. The return on investment is high. The team isn’t anywhere near done innovating, publishing, and enabling high-tech space aand terrestrial amateur radio work. If you want to be a part of this, or just follow along, visit https://openresearch.institute, go to “Getting Started”, and sign up for the Phase 4 Ground mailing list. This is “home base” for announcements from ORI.

Right beside ORI’s booth was the “future of amateur radio”, the M17 Project. Ed and Steve from M17 brought working hardware, firmware updates, and also demonstrated several different software implementations throughout the weekend. M17 held their weekly net on Friday live from the booth, gave away stickers, magnets, and pins, and captured the hearts of all who visited. You can get involved with this project at https://m17project.org

AmbaSat re-spin was a frequent topic of conversation. The five AmbaSat boards from ORI, which operate at 70cm, have been distributed to the firmware team, and they have begun development and are seeing success in university and hobbyist labs. The goal is to create a compelling application, put the hardware on a sounding rocket, apply for a launch license, and send this project to space in a way that makes the amateur community proud. While “AmbaSat Inspired Sensors” is ORI’s smallest received grant, it has by far the highest capability return on investment of any ORI project.

ORI and M17 booths were located in the North Hall. While the other buildings are larger and many consider them to be higher profile, booths in the North building are what you must walk by to get to the Information Booth and Prize Booth. Since the vast majority of participants visit this part of the show, it is, in our humble opinion, the best possible location.

Michelle Thompson (W5NYV) presented about Digital Communications Technology at the ARRL Expo Technology Track held on Thursday at a conference center near Seaworld. There were four tracks of presentations at the Expo: Contesting, Handbook, Technology, and Emergency Communications.

Michelle reported a positive, enthusiastic, and engaged audience for her ARRL Technology Track talk, and has high hopes that ARRL will continue doing events like this moving forward. She discussed ORI’s Polar Code initiative, successful regulatory and legal work, why open source LDPC work is so important to amateur radio, the four fundamental components to digital communications, and why the M17 protocol was selected as ORI’s satellite uplink protocol for the P4DX transponder project. Michelle invited M17 principals to speak about their work, and opened the floor for questions and comments from the many highly competent and curious technical hams that were in attendance. Subjects covered ranged from asynchronous computing to concatenated coding. The rumors about toilet paper being a fundamentally important part of this presentation are entirely true.

ORI organized a Friday forum track for Clearspan Tent #1 that ran from 11:15am until closing. HamCation was extremely generous in giving us time to present work from a wide variety of people. Here’s our lineup for 2022.

11:15 am
Understanding and Changing Amateur Radio Regulation / Open Source Digital HTs are Real! by Bruce Perens (K6BP)

12:30 pm TAPR – TangerineSDR Update, or How to build an SDR without any parts by

Scotty Cowling (WA2DFI)

1:45 pm M17 Project by Ed Wilson, Steve Miller (N2XDD, KC1AWV)

3:00 pm GNU Radio work at ORI / FreeDV HF Voice Update 2022 by Douglas Quagliana, Mel Whitten (KA2UPW, K0PFX)

3:00 pm Society of Amateur Radio Astronomy SARA by Tom Crowley (KT4XN)

At both the Expo and HamCation, ARRL set the pace this year for satellite talks and satellite demonstrations, with a video (please see https://www.youtube.com/watch?v=fhyUbC_o1JM&ab_channel=ARRLHQ) providing practical examples of amateur satellite operations. Patrick Stoddard (WD9EWK) gave a tutorial on satellite operations at the ARRL Expo in the Handbook Track. Amateur satellite was very well supported from ARRL this year, and we have heard this will continue to strengthen going forward.

With some optimism, ORI looks forward to returning to in-person events. The next planned in-person event is DEFCON (https://defcon.org/). Last year, DEFCON was held in person. Proof of vaccination was required. Masks were required. It was a highly successful and enjoyable event. This year, for 2022, ORI will be represented in DEFCON villages and activities. We are looking at applying for M17 to be part of Demo Labs, multiple radio links between villages to demonstrate a wide variety of technology, and presentations about the R&D that we do.

If you would like to be a part of this, and we do need you, then please join the Slack channel for DEFCON planning. Quite a bit of work is underway already. The goal for DEFCON 2022 is over the air demonstrations, outreach, fun, swag, and supporting our friends at all the villages we’ve been involved with over the years.

DEFCON is run very differently from traditional amateur radio conventions. The most significant practical difference is that DEFCON has a written code of conduct, and those written community standards and policies are enforced. It has a very diverse and very interdisciplinary attendance. Unlike many technical or hobby conferences, participation in the DEFCON community is possible year-round through participation in local groups that meet monthly.

DEFCON is a very large event, with attendance of over 30,000.

DEFCON is devoted to a very broad spectrum of experimental, commercial, and open source work. Participation by the government, industrial, information security, hacker, hobbyist, and scientific communities has steadily grown over the past 30 years.

The next virtual event for Open Research Institute is Ham Expo, 12-13 March 2022. Andre Suoto will have an excellent talk about our open source LDPC encoder for FPGAs and ASICs. This is in the main track. We will have a wide variety of work and projects represented at our booth, which is in the vendor hall. Open Research Institute is a non-profit sponsor of Ham Expo. We’ll have friendly and accessible “office hours” during the event.

2021 Retrospective

Greeting all, and welcome to the close of 2021 at ORI.

For a high-level summary of what Open Research Institute is and what we have been up to, please watch the very short video presented at Open Source Cubesat Workshop 2021. The recording of the talk is here: https://youtu.be/VG9-Mc1Hn4A

If you would like to keep up with what we do, then subscribing to our mailing list and YouTube channel helps in several ways. More people find out about what we do because our work will get recommended more often to new people, and you get notifications of new content when it’s published.

Please visit https://www.youtube.com/c/OpenResearchInstituteInc/featured and subscribe to YouTube.

Please visit https://www.openresearch.institute/getting-started/ for information on joining the mailing list and Slack.

Join Phase 4 Ground Trello board:
https://trello.com/invite/b/REasyYiZ/8de4c059e252c7c435a1dafa25f655a8/phase-4-ground

Join Phase 4 Space Trello board:
https://trello.com/invite/b/GRBWasqW/1336a1fa5b88b380c27ccf95d21fec79/phase-4-space

We have other social media accounts as well (Twitter, Instagram, FaceBook) and we gratefully accept help and support there too. Want to be part of the social media team? Write ori at openresearch dot institute to apply.

https://twitter.com/OpenResearchIns
https://www.facebook.com/openresearchinstitute
https://www.instagram.com/open_research_institute/

Here are our challenges and successes from the past year and what we’re looking forward to in 2022. There’s a lot going on here and some of the things we are facing are not fun. Some of the discussion is political and tedious. We have some decisions that have been made and some big ones to make for 2022 and beyond. Your opinions matter. Comment and critique welcome and encouraged.

First and foremost, we thank the individuals and organizations that have made our work possible. Funding comes from YASME Foundation, ARRL Foundation, ARDC Foundation, Free Software Foundation, our Trans-Ionospheric and JoCo Badge projects, proceeds from the Gold Medal Ideas ORI store, and people like you.

2021 Retrospective

We are a research institution. We are not a ham radio club. Our primary focus is to carry out open source work for the amateur radio space and terrestrial bands. We expect this work to be used by amateur radio groups that execute and operate designs in space and on earth. This expectation has not been met in some of the ways we anticipated, but we have a broad path forward, a lot of things going very well, and we are going to take full advantage of all the positive developments over the past year in every way we can.

This next part is not the most fun story to write or read, but there’s a lot of very good lessons learned here, and it needs to be put in one place so that our amateur satellite volunteers know about it and can find it.

One can skip ahead (by clicking here) to “Successes in 2021” further down the page to get straight to technical progress.

When we say we expected our work to be used by amateur satellite groups, we assumed this meant AMSAT. Primarily AMSAT-NA, but we are also here to serve AMSAT-DL, AMSAT-UK, and so on. ORI is an AMSAT Member Society, and has showed preparation, enthusiasm, and experience through continued contributions to the amateur satellite community. ORI volunteers have professional, academic, and amateur experience with collectively at least a couple dozen payloads in orbit, ranging from GEO commercial to LEO amateur. A very large fraction of our volunteers are new to amateur radio. They have never volunteered for AMSAT or any other legacy satellite group before. Other volunteers have experience with AMSAT but no current role because of the politics of AMSAT-NA GOLF. I can say without any reservation that there is no loss of capability to any AMSAT organization from ORI activity. We have always encouraged volunteering for and membership within whatever AMSAT organization is nearest to you. It’s not just supportive words, but actions as well. We have sold AMSAT-NA memberships at numerous events over the years. We have actively promoted TAPR, AMSAT, ARRL, and other amateur groups at every opportunity. We’ve happily worked with TAPR and ARRL to great positive effect.

We have achieved some truly significant wins in the regulatory sphere with ITAR/EAR and Debris Mitigation, have groundbreaking success in P4DX comms development, and have one of the very few functional advanced communications research remote access lab benches in existence. We have expanded the AmbaSat Inspired Sensors project to move the AmbaSat to 70cm in anticipation of sounding rocket and space tests, have fully supported M17 Development and Deployment, and have proposed an employment program to ARDC to directly confront the problem with open source burnout in DSP/FPGA open source amateur designs.

We really do not suck.

However, despite all this good work, AMSAT-NA leadership, including senior officers, have consistently and publicly described ORI as “grifters” and “thieves” and “frauds”. Officers of AMSAT-NA have said we are “undeserving of any community support” and have taken actions to try and make this opinion a reality. It hasn’t worked, but these aggressively provocative and negative public posts from AMSAT-NA officers and members about ORI are clearly intended to harm. The attacks date back to 2018. ORI has not responded to any of this. However, ignoring it doesn’t make it go away, and participants in ORI need to know what’s being said and done.

ORI has had work censored from AMSAT publications and events. An ITAR/EAR update article submitted in October 2021 was removed before publication. According to the editor, this was the first time ever an article had been censored in the AMSAT Journal. The article had been requested by the editor and is in the draft of that issue of the Journal. It was personally squashed by the AMSAT President after the draft Journal was sent out. Several presentations and some papers were ordered to be eliminated at the last minute from 2020 AMSAT Symposium. The work had been welcomed by the submissions chair. This exclusion was unprecedented as well.

This sort of bizarre censorship has no place in amateur radio. Our disappointment with these decisions has been communicated to the editor of AMSAT Journal and the submissions chair for AMSAT Symposium.

For 2021, ORI co-hosted a half-day conference in collaboration with IEEE. This Information Theory Space and Satellite Symposium was successful, got great reviews, and IEEE has asked several times if ORI would be willing to organize something like this again. This gave us a chance to present some of the sort of work that we think should be part of AMSAT Symposium.

You can find the event recordings here: https://www.youtube.com/playlist?list=PLSfJ4B57S8DnhlrRya50IxGP90_uGpiho

Why do we care about any of this grumpy opposition? Why be concerned about censorship from a relatively small event or newsletter?

Because AMSAT-NA is presumed to be the primary advocacy group for amateur satellite activity in the United States. Because we want all AMSAT organizations to be successful. Because AMSAT and ARISS-USA have claimed that they are gatekeepers for amateur radio access to NASA. Because AMSAT-NA currently controls access to things like IARU committees for Region 2. Because AMSAT-NA gets irate when anyone else meets with the FCC on behalf of the amateur satellite service, but will not present anything outside of internal AMSAT-NA interests.

We care about this because ORI showed up and contributed within the AMSAT framework in good faith.

AMSAT-NA is, to be blunt, supposed to help us do exactly what we are doing. We are not a “threat”. We are not “thieves”. We are not “grifters”. We are not “frauds”. We don’t “siphon technical members away”. We are not “an embarrassment”. We deserve absolutely none of this sort of thing. We have invited AMSAT-NA to participate in every single major endeavor that we have carried out and accomplished. This inclusive and cooperative spirit has not been reciprocated.

Tacit acceptance of this sort of behavior is the real embarrassment.

For 2022, we will (of course) continue to utilize the amateur radio bands. All radio work will directly benefit amateur radio terrestrial and space. There will be no loss of opportunities or restrictions of goals for technical work. However, our associations and attention moving forward will focus on communities and organizations that share basic values with ORI. There will be some changes as we adapt, evolve, and grow. We can’t afford to spend time trying to work with organizations completely out of step with open source amateur satellite work, no matter how famous, wealthy, or historical they happen to be.

Successes in 2021

There is a lot of good news here.

Both the San Diego Microwave Group and the San Bernardino Microwave Society have been actively supportive and provided material assistance, volunteer time, and expert advice that we simply would not have received anywhere else. We would not have had a successful meeting with the FCC about Debris Mitigation without the support from members of these two radio clubs. Members generously offered their time, input, and guidance. All the regulatory work can be found here: https://github.com/phase4ground/documents/tree/master/Regulatory

Based on this meeting, we had a series of Orbit Workshops in November 2021. Recordings posted to the debris mitigation channel on our Slack.

The ITAR CJ Request work was funded through a grant from ARDC. The EAR Classification, successful Advisory Opinion Letter from Commerce, FAQ, and “How to use this work” flow graph were paid for with a loan to ORI. The process to fundraise to pay back this loan is underway. The final amount for EAR/Advisory Opinion/FAQ/Flowgraph is $14,425.00 Similar to the ITAR CJ Request work, this amount is substantially less than initial estimates. Credit goes to excellent counsel at Thomsen and Burke LLP and a motivated volunteer team at ORI that handled as many of the preparations as possible. Active sustained involvement reduced costs and increased competence and awareness of the many legal issues we were dealing with.

For 2022, we have two legal efforts that we are considering becoming involved with. Fundraising for those efforts will happen in advance of the work. This is a change from how we did the ITAR/EAR legal work, where fundraising was done after the legal work was completed.

We would not have had a successful multi-media beacon demonstration without support and advice from Kerry Banke and Ron Economos. A video presentation of this work can be found at https://youtu.be/vjfRI1w_dSs?t=609 and documentation can be found here: https://github.com/phase4ground/documents/tree/master/Engineering/Transmitters/DVB-S2-Multimedia-Beacon

This work is presented as a terrestrial beacon, but is also the default digital download for the P4DX transponder payload.

The payload work is currently focused on producing an FGPA-based end-to-end over-the-air demonstration. There are multiple repositories. The best way to get an overview of this work is either through the README.md files in the repos at https://github.com/phase4ground and https://github.com/phase4space.

If reviewing source code and block diagrams is not your thing, then watch the introduction of this video: https://youtu.be/fCmzS6jBhHg followed by the most recent Technical Advisory Committee meeting here: https://youtu.be/V2BlIp7XYMM

Thomas Parry is the Primary Investigator and lead the TAC meeting. Wally Ritchie (SK) was the previous and founding Primary Investigator, and he presented the overview in the design review linked above.

P4DX is our digital multiplexing microwave amateur band transverter. The native digital uplink is M17 FDMA and the downlink is TDM DVB-S2/X. A high-level architectural paper can be found here: https://github.com/phase4ground/documents/tree/master/Engineering/Requirements/Architecture

One of the current roadblocks with the end-to-end demo is a necessary expansion of capability in Remote Labs West. In order to use the Analog Devices ADRV9371 RFIC development board, we can get by with using an SD card image in the FPGA development station. However, this requires a lot of manual intervention, so booting the filesystem over NFS is an obvious improvement. This turned out to be impossible because the kernel from Analog Devices does not appear to support NFS. So, we’re fixing it and will (assuming success) submit whatever capabilities we add to the kernel back to Analog Devices. In the meantime, integration of the various bodies of FGPA code continues. Immediately following the NFS boot addition is DVB-S2/X verification station bring-up, in anticipation of being able to test what comes out of the ADRV9371. That’s just one example of the type of work that has had to happen all year in order to get things done.

Remote Labs have become much more than a “wear item” along the way. Once it became clear that the internet-accessible lab benches had potential to support a much wider variety of projects than just P4DX, volunteers started putting time into making sure they were as easy to use as possible. You can find out more about what Remote Labs are and how they work by going here: https://github.com/phase4ground/documents/tree/master/Remote_Labs

Remote Labs East (Florida) equipment has been moved to Remote Labs South (Arkansas). The move was necessary due to the untimely death of Wally Ritchie in July 2021. The new site will need additional funding to complete that Florida did not require. A grant application was made to ARDC in late August 2021 for this work. Remote Labs South will also have additional capabilities for bacteriophage and interferometry work. Both are open source efforts.

There is a backup bridge funding plan to get the lab bench at Remote Lab South operational. We can temporarily divert funds allocated to P4DX for FPGA software licenses, as the floating license approach has worked out well for us. The original budget planned for 10 node-locked licenses as those were the type of licenses we have received as an organization in the past. With only 1 floating license required for work so far, this leaves some margin in the budget. This is enough margin to develop Remote Labs South infrastructure while waiting for a response about funding from ARDC, without further delaying deployment of this lab.

Remote Labs are a good example of the frugality, public science orientation, and opportunistic spirit of ORI volunteers. We look forward to many years of making the equipment available to the open source community. We could use your help in spreading the word about this asset.

HamCation and Ham Expo have been invaluable. The staff and volunteers have been friendly, supportive, and creative. We are looking forward to HamCation 2022. If all goes well this will be our first in-person event most of us have been able to attend in quite a while. We have a booth in our usual spot. M17 Project and TAPR are on either side, and the large Society for Amateur Radio Astronomy booth is on the other side of TAPR. DATV is in the same row. ARRL will have a large presence. We have a lot of forum time and plenty to talk about. Returning to in-person events is a big step and there is extra stress, risk, and planning involved. If you are willing to be part of HamCation, please get in touch and we will add you to the planning spreadsheet and discussions.

IEEE Computer Society, Information Theory Society, and Signals and Systems have been incredibly supportive. As mentioned above, in 2021, ORI co-hosted a half-day conference in collaboration with IEEE. This Information Theory Space and Satellite Symposium was successful, got great reviews, and IEEE has asked several times if ORI would be willing to organize something like this again.

You can find the event recordings here: https://www.youtube.com/playlist?list=PLSfJ4B57S8DnhlrRya50IxGP90_uGpiho

We have received a lot of positive feedback from IEEE section, region, and national executive teams. The biggest challenge with IEEE is that they are not the best or easiest way to publish open source or open access work. They are honestly not set up for public access papers. IEEE is split between academia and industry members, and that’s the constituencies more or less served. Despite the big differences between a tiny open source non-profit and a gigantic professional development organization, there is a substantial amount of interaction and genuine mutual support. IEEE does not exist without volunteers. Therefore, what we are doing is recognizable as a thing of value by everyone in any role any of us comes into contact with. We also benefited from having access to the salary survey results, anonymized membership statistics, and a targeted member survey in order to help construct the Engineers General grant proposals to ARDC. Is there a possibility of funding through IEEE? Yes, although there are a lot of limitations.

We have solid relationships with a number of Universities. Working with academic institutions is not simple as a non-profit, but we have transcended these difficulties several times and are part of the process of getting space “done better” for students wherever we can. Our most recent involvement is getting AmbaSat at 70cm, the DVB-S2/X microwave band work, and M17 equipment on board sounding rockets and in the running on several LEO platforms. Is there a possibility of funding through Universities? Honestly, no. They expect funding from us, in order to do anything with us. That is just the way the current engineering academy operates. Students are not “free labor” now and never really have been in the past.

We have brought a small grant to a University, with the professor as the Primary Investigator (AmbaSat Inspired Sensors). We would be willing to do that again, if we were fortunate enough to get a professor of the same motivation, experience, and availability, and fortunate enough to get enough grant money to ensure student time. In general, the overhead customarily demanded at a University, and the costs of getting significant seat time from enough students, require much larger grants than we have pursued to date. If you know of an opportunity or have an idea, get in touch with ORI board and let’s see what we can achieve.

AmbaSat Inspired Sensors has redesigned the AmbaSat board to move from 915 MHz ISM LoRaWan to 70cm amateur radio satellite band. Thank you to Vidya Gopalakrishna and Jay Francis for making this happen. LoRa with integration to both SatNOGS and The Things Network through bridging is prototyping now. The first hardware with the 70cm part has been received and works. There were other changes to improve power and ground and routing. All of the details can be found in the kicad-conversion branch at https://github.com/phase4space/AmbaSat-1/tree/kicad_conversion/Release

This past year has been a significant step forward for the M17 Project. The protocol has been strengthened, the number of development boards in the community has increased, the amount of hardware that M17 can work on has increased, and the lab on the East Coast of the US is moving forward. There have been numerous successful public outreach efforts resulting in a steady increase in name recognition, awareness of the communications mode, and participation on the M17 Discord. A large amount of lab equipment has been earmarked by ORI for M17. This purchase opportunity came from Open Lunar Foundation and will put M17 lab into a highly capable category from the start. All of us associated with M17 would like to recognize the OpenRTX project. This team is a vital part of the M17 ecosystem and has done a significant amount of highly technical work to enable M17 on the MD-380 HT. OpenRTX has contributed a lot of engineering work, verification, validation, and lab tests for M17.

https://m17project.org/

https://openrtx.org/#/

Open Lunar Foundation and ORI collaborated on an SBIR grant application for funding targeting LunaNet in January 2021. While our application for funding was not successful, the feedback from the reviewers was positive and very constructive. The process for applying was clear, the technical work in preparing the application lined up with all of ORI’s goals for P4DX, and the teamwork with OLF was excellent.

https://www.openlunar.org/

We attempted to apply for a STTR with Tek Terrain LLC for opportunistic positioning and ranging using LEO signals in mid-October 2021, but we were not able to complete the application in time. We look forward to the next opportunity to work with a for-profit on something like this, as there are dozens of opportunities through a variety of government agencies for research and development. This particular project would have put some significant work into the public domain during Phase 1 of the grant.

We have an opening on our board of directors. Our co-founder Ben Hilburn has stepped down from the board. Thank you very much to Ben for helping found and build ORI. We welcome you to a (much less demanding) senior advisor role.

If you have a recommendation for someone to invite, or you would like to volunteer for this role, then get in touch to start the process. There are a few IRS limitations on who can be on the board to prevent conflicts of interest. No relatives of current board members, for example.

Current board is listed at: https://www.openresearch.institute/board-of-directors/

Our open source workers/employment initiative is called Engineers General. Two grant proposals were made to ARDC after a series of productive meetings with their staff. The initiative got a lot of positive feedback. All of ARDC’s feedback was incorporated into a set of revised grant requests that were re-submitted in October 2021.

We have 6 additional resumes that have been submitted to us. We have received a very large amount of interest in this initiative. Information from IEEE salary surveys, informational interviews with open source workers, and combing through peer reviewed papers resulted in the hypothesis of Engineers General, and all of this information was communicated to ARDC in support of the grant requests.

ORI board has the capacity, capability, and experience to manage contracted workers, and there is a population of highly qualified people that want to work in open source.

We do not have a timeline on when we will hear back from ARDC. P4DX took 11 months to approve. The ITAR legal work funding wasn’t pressing since the funding application followed completion of the work. The AmbaSat Inspired Sensors grant application was folded into P4DX at some point during its review process.

Rent-a-GEO was submitted in October 2019, and there has not been a final answer from ARDC about that proposal as of today. Rent-a-GEO is now down to ~2.5 years left on the offer of 5 years discounted rental of the transponder. This is closer to 2 because the team assembled for Rent-a-GEO would have to be rebuilt.

For those unfamiliar with this project proposal, it would enable a variety of GEO development work over useful space channels with a footprint that covers the continental United States. We did obtain a private pledge of funding for the rental due to the urgency with the lifetime of the resource coming to an end, and we have communicated this pledge of funding to the vendor handling the transponder rental. However, there are substantial contingencies with this funding source, and the vendor has a lot of challenges that they are dealing with. Negotiations are slow. I’ll keep working on this until EchoStar9 is turned off. In the meantime, we have had a series of successful experiments in Europe.

We are headquartered in California, USA. According to Cal Non-Profits, a 501(c)(3) dedicated to helping California 501(c)(3)s, they really do not know of any other organizations like ORI (or Open Lunar Foundation). We are quite rare. The vast majority of non-profits in CA (and across the US) are devoted to health and human services. Non-profits heavily dominate “last mile” services delivery in the US, and there’s a wealth of information about them and advice on how to operate. We have taken advantage of as much as we can all the advice given by Cal Non-Profits, and will continue to rely upon them for guidelines and checklists and statistics about the non-profit sector.

Almost all of the science and technology non-profits are private foundations. Almost all of the research institutes in this category have a single very large source of money, have paid staff, and are clearly dedicated to a mutually beneficial relationship with commercial consumers. This is a very different way of operating from ORI, which is registered as a public charity.

And, the way we have been funded directly impacts this status as a public charity. 501(c)(3)s like ORI are required to have diverse funding. We have to comply with what’s called a “public support test” that kicks in after our fifth year of operation. We’ve been around three years and have two more to go before this test is applied. While we did come very close to passing this test in 2020, we will not pass it for 2021. The specific test is that 33.3% of our funding must come from what are called public sources. Technically this means at least 33.3% of donations must be given by donors who give less than 2% of the nonprofit’s overall receipts. That 2% test means that each non-profit’s donation numbers will be different, depending on the overall receipts.

With ARDC being our primary funding source, all of the other sources amounted to at most 30% in 2020. In 2021, the vast majority of funding came from ARDC, putting the percentage from other sources down much further. A quick calculation today shows other sources of funding coming in at most 24%. Given the 2% rule, that number is in reality lower.

If we had just one unusually large grant from ARDC in our financial history, then that would be ok. The IRS lets you ignore one unusually large grant. You can punch that one out of your public support test calculations.

One can argue that all of the money from ARDC should count as unusually large, and all recipients out there doing tower trailers and buying equipment for mesh networks and university club shacks shouldn’t have to worry about this at all.

The amateur community has never sourced or sunk large amounts of money like this. Hams have a reputation for being tight-fisted with money. Frugality is a virtue that we ourselves value and employ, as described earlier in this letter in the way we’ve extracted several “extra” features from the P4DX grant money that a less motivated organization would not bother to do.

A step function of money of the magnitude that ARDC has, showing up in the amateur radio community, cannot easily be matched or diluted. ARDC principals have heard this from community members with philanthropic experience from the get go.

For almost any amateur radio organization, outside of the very largest, diverse sources of money on the order of an ARDC grant simply do not exist. This means that ham non-profits can take one large grant from ARDC without much trouble or effect on their status, but that’s it. The vast majority of ham clubs and organizations file nothing more than a postcard with the IRS every year. Above $50,000 in gross receipts and then they have to file the full 990. A large influx of money on an ecosystem of organizations that have never had access to it before includes both negative and positive effects.

For organizations like ORI that fully intended to work with ARDC for the long haul, this puts a huge additional fundraising burden on the leadership. Since ORI has ruled out selling memberships, the fundraising alternatives are even more challenging in an environment where a highly successful ham club auction raises $400.

So what happens when your public charity fails the public support test? Well, actually, nothing too horrible, but only if you are prepared for it. You are, after a process that does have a subjective component, converted from a public charity to a private foundation. The downside is that you have to re-file all your taxes as a private foundation going back all five years. There are some upsides. Private foundations do not have to follow some of the rules that public charities are required to comply with.

As soon as we figured out we were well on our way to being converted into a private foundation, which was mid-May 2021, we told ARDC. This was “news to them”. After talking it over with ARDC staff, we then hired a non-profit law specialist for advice (at ORI expense), wrote everything down, and came up with a plan. ARDC could either fund ARDC service programs that ORI would execute, and it would not “count against us”, or ORI could simply plan on becoming a Private Operating Foundation associated with ARDC. These options were proposed to ARDC staff. There was email back and forth and several zoom calls. The answer was eventually “no” on ARDC running Service Programs, but “yes” on ORI becoming a Private Operating Foundation associated with ARDC.

Problem solved! We had a party to celebrate. The feelings of IRS doom are kind of a big deal for a relatively new non-profit. We viewed this as being “hired”, in a way, by ARDC.

This solution held until October 2021. It was no longer clear that ARDC wanted this type of relationship. Both the “run Service Programs that ORI executes” approach and the “Private Operating Foundation associated with ARDC” approaches require a lot of communication and work. ARDC was not set up for either of these solutions. ARDC operates very differently from ORI. It does not have the same management structure or style, and it does not communicate like we do. Despite our best efforts, we couldn’t “impedance match” to make up for these differences. It’s unreasonable to expect them to change.

So, in November of 2021, the board of ORI and other senior advisers with non-profit and foundation experience recommended reversing the “conversion plan”. This means raising enough money to bring the ratio back up above the public support test limit to stay a 501(c)(3). The fundraising goal, as of today, is $150,000. This money has to come from diverse and much smaller sources. This must be raised over the next two years. It will be substantially more administrative and executive work to remain independent, but it’s how we were founded and how we have operated all along. The path forward is clear enough. The series of decisions during this process took a large amount of time and energy from May until November, but it was well worth the effort. Decisions about what type of non-profit organization ORI is or becomes have enormous impact on what we do and how well we are able to do it.

$150,000 (or more) is a large amount of money to raise in small amounts, especially within the amateur radio community. Have some advice? Want to get involved raising the money? Have another solution? Welcome aboard.

The fact that we exist and are successful in amateur radio communications R&D is very unusual. This means that we are vulnerable and it means we have more work to do, every year, to remain operational. Your support is vital for success.

Thank you to everyone that is pulling for us to succeed! We are looking forward to 2022 and welcome your ideas, time, talent, treasure, and advice.

-Michelle W5NYV
CEO ORI

ORI participation at OSCW 2021

Recording, transcript, and slides of Open Research Institute’s presentation at Open Source Cubesat Workshop 2021.


Hello everybody! I’m Michelle Thompson W5NYV and I’m here to tell you all about what Open Research Institute is and what we have been doing.

Open Research Institute (ORI) is a non-profit research and development organization which provides all of its work to the general public under the principles of Open Source and Open Access to Research. As we all know, these mean particular things, and those things have to be defined and they have to be defended.

Open Source is type of intellectual property management where everything you need to recreate or modify a design is freely available. As a baseline, we use GPL v3.0 for software and the CERN Open Hardware License version 2.0 for hardware. All we do is open source work, primarily for amateur radio space and terrestrial, but also some other fields, as you will see.

So who are we?

Here is our current board, and our immediate past CEO Bruce Perens. We have one opening on the board, as Ben Hilburn, one of our founders, very recently retired from being an active Director at ORI. He remains as one of our senior advisors. We are looking for someone to join ORI board that supports what we do and wants to help make it happen. It’s an active role in a flat management structure. Board members are are experienced in management, engineering, operations, and technology, and three out of the current number of four are from underrepresented groups in STEM.

As a board, it is our mission to serve our participants, developers, and community members. We now have at least 535 that participate in what we call the Open Source Triad: our mailing list, Slack, and GitHub. All work is organized in independent projects or initiatives.

We have some affiliations and we proudly ascribe to the Open Space Manifesto from Libre Space Foundation. We work with radio organizations, several universities, and have worked with a variety of for-profits.

What do we do?

Here’s a visual summary of top level projects and initiatives. The vertical axis is risk. Higher risk projects are at the top, lower risk projects are at the bottom. Maturity increases left to right. Maturity may indicate schedule, but the score is also influenced by complexity or difficulty. The color of the shape indicates how much stress that project is under or what the risk level is at this time. The size of the shape is the budget estimate. By far, the largest budget, riskiest, and least mature work is in the AquaPhage project, which is open source bacteriophage research and development. Bacteriophage are viruses that attack and destroy bacteria. This is biomedical and not amateur radio. This project was halted by COVID and has not yet resumed.

Our digital multiplexing payload project is called P4DX, and it’s in the middle in green. This is a multiple access microwave digital regenerating repeater for space and terrestrial deployment.

Channels divided in frequency are the uplink. The uplink is on 5 GHz. The processor on the payload digitizes and multiplexes these signals and uses DVB-S2/X as a single time-division downlink. The downlink is on 10 GHz. The system adapts to channel conditions and handles things like quality of service decisions. For example, low and high latency digital content. The uplink is divided up using a polyphase channelizer, based on the open source work done by Theseus Cores.

For the current prototype, we are only using MPEG transport stream, but generic data is the goal. The prototype beacon signal is 5 MHz wide and we are using one modulation and one error coding (yet). We are not yet rotating through all the allowed combinations in DVB-S2 (yet).

Our prototype work can also serve as a terrestrial multimedia beacon. Work was demonstrated to groups with mountaintop spaces in October 2021, and deployment will be as soon as possible.

M17 project is an open source VHF/UHF radio protocol. Think open source digital mode HTs and repeaters. This project is only slightly more stressed than P4DX, but it’s further along in maturity because it’s narrower in scope. We believe M17 Project will be very successful from current development to scaling up to commercial product launch. The M17 protocol is the native digital uplink protocol, with some modifications for 5GHz, for P4DX. We are working hard to get M17 on and through more satellites and more sounding rocket tests today.

Engineers General is our initiative to hire highly competent open source workers to reduce burnout and increase quality in open source work important to amateur radio. We have one contractor currently, eight resumes, and have applied for funding for two more. We are actively looking for funding for the remaining five.

The “birdbath” is a large dish antenna at the Huntsville Space and Rocket Center. This was used in the past, but has been parked for decades. It took two years of negotiation, but ORI has the support of the museum and permission to begin work renovating this dish for citizen science and amateur radio educational use. Work parties from earlier this year were rescheduled due to COVID.

Upper right there are two completed projects. One is ITAR/EAR Regulatory Work. It took over a year, but we received a determination from the State Department that open source satellite work is free of ITAR, from Commerce that it is free of EAR, and we obtained an advisory opinion that publishing on the internet counts as publishing under the regulations. This is a huge step forward for not just amateur radio, but anyone that wants to contribute to open source space work.

Debris Mitigation Regulatory Work took 10 months to complete. The process culminated in a highly successful meeting with the FCC Wireless Telecommunications Board, the Office of Engineering Technology, and the Satellite Bureau in late October 2021.

Lower right is Battery Matching, a project that matches NiCd cells for very durable batteries in the style that used to be done in amateur satellites, and puts the methods and documentation in the public domain.

AmbaSat Inspired Sensors used to be on the bottom right but now it’s bumped back a bit in maturity level is higher risk. This was supposed to be a project done by students at Vanderbilt university, but no students materialized, primarily due to COVID. We had one kick-butt professional volunteer who was working on a 10GHz beacon that went into the sensor connector on the main board, but the project was moving slowly, and ORI decided to provide additional operational support. Additional volunteers joined the team, we reviewed the finances, and then took some actions. We updated the main board to move it from the illegal ISM band it was in to the legal 70cm ham band. We improved power and ground and addressed some other design concerns. The boards are back as of last week and software and firmware development is underway. The 10 GHz sensor “beacon” work is proceeding quickly as well. AmbaSat is an excellent educational platform, but the ISM band decision isn’t the only problem with it. It’s very small.

We decided to look at combining the 70cm AmbaSat with another open source satellite board to make a combined spacecraft design. I reached out to Pierros Pappadeus at Libre Space, and we are moving forward with using the SatNOGS Comms project. We look forward to contributing to the FPGA codebase and flying both AmbaSat and SatNOGS Comms designs as early and as often as possible, starting with sounding rockets and ending up in space.

All of these projects are open source and all work is published as it is created.

When?

We have timelines! We were incorporated in February of 2018, got our 501c3 in March of 2019, and we hit the ground running and haven’t stopped since.

We’ll distribute a copy of the slides so you can see our wins and losses along the along the way. There’s a lot going on in here.

Here’s what’s been going on since March, and the future plans we know about.

We use Agile framework for management, and most of us have some sort of formal certification either completed, or in process. This is the Agile manifesto and it is the foundation of how our board decides things and how it supports project leads and volunteers. Note the second item, and put in the word hardware instead of software, and that’s one of the reasons we demonstrate early and often and incorporate the feedback quickly.

Where are we?

Here’s the locations of the concentrations of current major contributors and participants. When we say international, we mean it. Our participants have a wide range of ages, are generally educated in engineering, come from a variety of backgrounds, but do tend to be relatively young and male.

We have some physical locations that are important for carrying out the work we do. Remote Labs are lab benches connected to the internet that allow direct access to advanced lab equipment and two different large Xilinx development boards and DVB-S2/X gear. We have relocated our second Remote Lab equipment from Florida to Arkansas, and have added a three-dish interferometry site for amateur radio and public science use. Remote Labs are here for you all to use. If you need large FPGA resources and test equipment up to 6 GHz, then we have your back.

We bought Open Lunar Foundation’s satellite lab. It’s in storage waiting for the M17 project lab construction to conclude, and then the equipment will go there to pack that lab full of wonderful test equipment, materials, and supplies.

Why do this?

We believe that an open source approach to things like amateur digital communications, bacteriophage research, and sticking up for the non-commercial use of space will result in the best possible outcomes for the good of humanity.

We have a lightweight agile approach to doing things. We keep our overhead very low, we are radically participant-focused, and the work must be internationally accessible.

You can see that public demonstrations and regulatory work are given a high priority. Working code and working hardware are highly valued. Working means working over the air.

Thank you to everyone at Libre Space for the support and opportunity to present here today.

https://www.openresearch.institute/wp-content/uploads/2021/12/OSCW-2021-W5NYV-ORI-1.pdf

Engineering Report 20 November 2020

## Phase 4 Weekly Report for 20 November 2020

#### Virginia Tech Industrial Advisory Board Meeting Report
Open Research Institute attended our first Virginia Tech Industrial Advisory Board Meeting on 20 November 2020. The meeting was attended by over 40 representatives from industrial, academic, amateur, and open source communities. The goal of the Industrial Advisory Board is to improve Virginia Tech’s ability to educate students for roles in space exploration, science, technology, regulation, and management.

The first part of the meeting was a description and orientation of the re-dedication of the Industrial Advisory Board lead by Scott Bailey. The second part of the meeting was a curriculum review lead by Dr. Jonathan Black. The next meeting will be in the Spring.

**Action items:** prepare 2-3 slides about ORI and our mission on the Industrial Advisory Board. Open source regulatory advancements, positive effect on commerce when used appropriately, and the improvement in educational outcomes are the communications goals for the slide deck.

#### High-Level Discussion on Thermal and Radiation
We had a high-level discussion about thermal and radiation requirements and work on 19 November 2020. The goals of the meeting were to introduce volunteers with experience in these areas to each other, and to generate any action items necessary to clear roadblocks for future work. Initial list of action items:

Screen Shot 2020-11-20 at 2 44 34 PM

**Meeting Minutes**

Attending were Michelle Thompson, Mike Murphree, Thomas Savarino, Alan Rich, and Nick KN6NK.

We use FlexLM for our Vivado license server, generously donated by KN6NK, and we will be able to use this server for Thermal Desktop. This is limited to one user, Thomas Savarino, but we are satisfied with this work plan. Thomas will also need Parallels and Autodesk. Invoices requested.

Alan Rich provided valuable advice about thermal engineering. Junction temperature and thermal cycling are of primary interest. We need to expect to do a layer analysis and treat the board like a structure. Concerns for radiation were discussed which align with previous work by Wally Ritchie, Thomas Parry, and Suoto.

Mike Murphree requested a mission plan and expectations on the radiation environment as soon as possible.

Mike Murpree requested resource utilization of the Xilinx parts in order to compare against other potentially more radiation tolerant families of parts.

Michelle to provide documentation on the block diagrams and architecture documentation.

*Priorities? Get the Thermal Desktop software up and running so Thomas Savarino can train on it and then start characterizing the 1U circuit cards for the communications payload.*

###### Open Research Institute sponsors the M17 Project
Open Research Institute is proud to sponsor M17, an open source digital radio protocol, code, voice codec, and hardware project.
Learn about and get involved at

https://m17project.org/

M17 has been added to the list of Open Research Institute Projects at

Projects

#### Trello Boards up and running
We are using Trello for task management. Plenty going on!

Join Phase 4 Ground Trello board:
https://trello.com/invite/b/REasyYiZ/8de4c059e252c7c435a1dafa25f655a8/phase-4-ground

Join Phase 4 Space Trello board:
https://trello.com/invite/b/GRBWasqW/1336a1fa5b88b380c27ccf95d21fec79/phase-4-space

#### AmbaSat Inspired Sensors
Phone conference with Dr. Alan Johnston on 2 November 2020 to answer questions and set up a tentative schedule. Work is expected to commence December 2020 through May 2021. This work is funded by an ORI grant. Project kickoff report here: https://www.openresearch.institute/2020/11/12/ambasat-inspired-sensors-project-kick-off-in-december-2020/

#### Remote Labs
Equipment has begun to arrive for the Remote Labs project. Access protocols have been drafted and tested. Feedback has been received and incorporated. Report and link to overview video here: https://www.openresearch.institute/2020/10/24/remote-labs-equipment-review/

Tracking document will be moved to the GitHub Wiki, but the current draft is here: https://docs.google.com/document/d/1EG_anaUNWxluriktrDBUa1MnIdIlOe9_hMCkNFj3Tc4/edit?usp=sharing

#### Ham Expo 2021 Participation
ORI will present at and be part of an exhibit at the Ham Expo 2021. Details about the event here: https://www.qsotodayhamexpo.com/
**We will be using this event as a deadline for transponder work.** We will demonstrate functionality complete by March 2021 at the show.

#### HamCation 2021 Participation
We will participate in HamCation 2021. This is a virtual event. We have 45 minutes available for presentations. HamCation wants unique, fun, engaging, interactive events. This is a wonderful opportunity for us. Message from organizers after we committed: “We don’t have a schedule yet. Plan on 45 minutes for the webinar with a 15 minute break between. Please provide a topic for the presentation with short description that will be posted. Thank you for offering.”

Topics for presentation and short descriptions need to be drawn up. We could do a competition, quiz bowl, live demo, technical presentation, contest, or anything of the sort.

#### Regulatory Presentation
We will present to the FCC, accompanied by ARRL counsel, in the next small number of months. This presentation will emphasize how open source technologies and policies strengthen the Amateur Radio Satellite Service. The presentation will show how the Amateur Radio Satellite Service can fully comply with Debris Mitigation, how it can and will continue a rich history of providing quality public service communications, and how it will be a full participant in the New Space Age.

#### Ed Friesma Needs Help
One of our volunteers, Ed Friesma, writes

“We’re submitting a proposal here at UNLV to get a Cubesat off the ground and I’m in charge of the communications team (both hardware and software) We are submitting our base proposal for review but I will have to get a team of students together. A mentor would really help here. Especially when it comes to building the ground station. but also testing the comms link and the ground station software.

Do you know anyone

a) with some good experience setting up communications with Satellites and also boradcasting to satellites over UHF.

b) who would be interested in occasionally speaking with and answering questions from our team.

They don’t necessarily have to be in the area but at least be open to using Zoom or Discord to chat with us.”

Ed has the right experience to put this team together, but would like to run things by someone that’s been there before. It would really help to sort out what must happen over the next few months.

Are you willing and able to mentor Ed’s team? Get in touch with me at w5nyv@arrl.net and I’ll get you in touch with Ed if you don’t already have his email.

Remote Labs Equipment Review

Transcript of Introductory Remarks

Greetings all,

Welcome to the Open Research Institute Remote Labs Equipment Review.

Open Research Institute (ORI) is a non-profit research and development organization which provides all of its work to the general public under the principles of Open Source and Open Access to Research.

Remote Labs are two physical lab benches. They have equipment for advanced digital communications design work. This equipment will be accessible online to anyone, anywhere that wants to work on open source amateur radio satellite service or open source amateur radio terrestrial engineering development.

The primary focus of the equipment list reviewed today is to support the design, verification, and test of the DVB family of links. DVB-S2, S2X, and T2 are all commonly found in amateur radio. DVB-S2X is the protocol family used by Phase 4 Ground and Space.

Remote Labs is a part of an extremely important process of re-establishing free and open international collaboration with groups such as AMSAT-DL, JAMSAT, and AMSAT-UK, and to increase and amplify collaboration with Libre Space and other open source groups. This is possible for ORI to do by using the open source carve-outs in the US export control regulatory framework. These controls have impeded international cooperation on amateur satellite work for a long time.

A significant amount of regulatory relief was achieved over the summer by ORI for amateur radio satellite work, and more work is going on right now to build upon this success. Please see the Open Research Website news section for more details on that. Today’s discussion is not about satellite technology, but about the equipment and resources required.

We are fortunate to have the advice and input of people that make a living by using remote labs at work. The advice received so far has been heard and acted upon. Python, HTML5 plus Javascript, and command line access will be the initial methods upon to provide secure access to the equipment.

We will not be writing or using a heavy or complex software framework for the Remote Lab. We will be authorizing and authenticating users. It is highly likely that we will use the same authentication and authorization approach that we intend to use for payload communications access, in order to get more experience with that design. In other words, you may be authenticated and authorized for Remote Labs the same way that you will be authenticated and authorized for the payload communications system.

We will definitely be documenting how to use the lab. We will be responsive to feedback about accessibility and ease of use.

There will be someone physically present at the Remote Labs. The equipment is not installed in racks at an unattended site. If a function needs on-site setup, or a test plan can only be done with someone physically at the bench, then that’s how the work will be done.

Remote Labs is offered as a community resource. Therefore, the review process must include community feedback. Thank you for your time here today to discuss and review the equipment list.

As an example, Thomas Parry has provided the following feedback.

1) The initial list had no power supply listed.

2) A computer controlled coax switch matrix would be very useful to control where the signals are going between test gear, DUT, etc. without physical intervention

3) Some form of general purpose digital/low frequency IO device like an analog discovery would be pretty useful for controlling things remotely

4) A way to get arbitrary RF in and out of the PC, ie. an SDR, would be very useful

5) And please remember cabling.

Wally Ritchie responded with an updated list that includes coax relays controlled from a USB relay board(s), and the other items.

Our practice will be validate and measure any cables we make in-house, buy, or obtain as surplus or donations.

I can answer your questions about budget, operation, and policy at the close of the review, or via email.

Please welcome Wally Ritchie who will lead todays Remote Labs Equipment Review.

P4XT (Phase One) Workshop Design Review

Learn about our work on the digital microwave broadband transponder for amateur radio.

https://www.youtube.com/watch?v=QXiWCgo10lg

All work is donated to the general public as open source.

This digital multiplexing transponder is a regenerative design, taking full advantage of a wide variety of cutting edge technology, intended for amateur radio use in space and terrestrial deployments.

This review focuses on decisions made for the prototype board set that implements the transmitter side of the payload.

Comment and critique welcome and encouraged.

Yasme Foundation Generously Awards Grant to ORI

Yasme Foundation Generously Awards a $30,000 Grant to Support the Open Research Institute (ORI) Amateur Radio Satellite Service Research and Development Program

ORI, a 501(c)(3) dedicated to open source research and development in amateur radio, has been awarded a $30,000 grant from the Yasme Foundation. This grant completes the Phase 1 fundraising campaign and allows ORI’s communications prototype work for geosynchronous and interplanetary amateur radio satellites to proceed.

Combined with the ARRL Foundation’s recent maximum grant of $3,000, the $14,000 in proceeds from ORI’s successful Trans-Ionospheric electronic badge fundraiser, and many deeply appreciated individual donations, a total of $51,490 was raised for Phase 1 of the Digital Multiplex Transponder research and development program.

A project that will directly and immediately benefit from this work includes the Amateur Radio Exploration (AREx) project, brought to you by Amateur Radio on the International Space Station (ARISS).

AREx is devoted to designing and building amateur radio equipment for the Lunar Orbiting Platform Gateway project. This lunar orbiting station will have open source broadband microwave amateur equipment and affordable open source ground stations. AREx is not limited to Gateway, as there are many other opportunities under consideration that can re-use all of the work.

All work completed by ORI is made available to the general public at no cost.

The Yasme Foundation is a 501(c)(3) not-for-profit corporation organized to support scientific and educational projects related to amateur radio, including DXing (long distance communication) and the introduction and promotion of amateur radio in developing countries. Yasme supports various projects relating to amateur radio, with an emphasis on developing amateur radio in emerging countries and encouraging youth participation in amateur radio.

The Yasme Foundation makes supporting grants to individuals and organizations providing or creating useful services for the amateur radio community. Regardless of originality or novelty, Yasme supports these programs in order to further the development of amateur radio around the world.

The global perspective and commitment to authentic, accessible, and sustainable amateur radio training and experience puts Yasme Foundation into the rare category of organizations that provide true and broad public benefit.

Find out more about the Yasme Foundation here:
https://www.yasme.org/

ARISS is the home for AREx. ARISS can be found on the web at
https://www.ariss.org/

JAMSAT supports AREx and has partnered with ORI to work on the Gateway Ground Station, which also directly benefits from this grant. JAMSAT can be found on the web at
https://www.jamsat.or.jp

Open Research Institute supports AREx and open source amateur radio research & development, primarily microwave.

Find ORI on the web at
https://openresearch.institute

Documentation about the Phase 1 transponder program can be found on the ORI website at the following links:

Overview:
https://openresearch.institute/2019/09/27/open-research-institute-phase-4-space-grant-application-overview/

Technical proposal:
https://openresearch.institute/2020/01/10/p4xt-digital-multiplexing-transponder-project-program-proposal/

Phase 1 statement of work can be found at the summary document linked below.

Summary:
https://openresearch.institute/2020/02/21/summary-proposal-open-research-institute-phase-1-p4xt/

Digital Multiplexing Transponder Workshop Guide and Link to Audio

DMT-workshop-mp3-guide

The document linked above is a Guide to navigating the Audio Recording of the P4XT Digital Multiplexing Transponder Workshop.

The workshop was held Sunday 9 February 2020 (3PM – 7PM) at Starter Studio’s Conference room in downtown Orlando, 4.5 miles from the HamCation venue.

A full audio recording (330MB MP3) is available at https://www.dropbox.com/s/9k065i5kqj3i49w/200209_1316.mp3?dl=0.

American Radio Relay League (ARRL) Awards Grant to ORI

Good news!

American Radio Relay League (ARRL) has Generously Awarded a $3,000 Grant to Support the Open Research Institute (ORI) Amateur Radio Satellite Service Research and Development Program

ORI, a 501(c)(3) dedicated to open source research and development in amateur radio, has been awarded a $3,000 grant from the ARRL Foundation. This grant, the maximum amount, will be immediately applied to Phase 1 of the Digital Multiplex Transponder research and development program. This grant allows hardware prototypes for broadband microwave digital payloads to proceed much more quickly. All work completed by ORI is made available to the general public at no cost.

A project that will directly and immediately benefit from this work is the Amateur Radio Exploration (AREx) project, brought to you by Amateur Radio on the International Space Station (ARISS). ARISS is a project sponsored by the Amateur Radio Satellite Corporation (AMSAT).

AREx is devoted to designing and building amateur radio equipment for the Lunar Orbiting Platform Gateway project. This lunar orbiting station will have open source broadband microwave amateur equipment and affordable open source ground stations. AREx is not limited to Gateway, as there are many other opportunities under consideration that can re-use what is designed and built.

Documentation about the transponder program that this award supports can be found on the ORI website at the following links.

Overview:
https://openresearch.institute/2019/09/27/open-research-institute-phase-4-space-grant-application-overview/

Technical proposal:
https://openresearch.institute/2020/01/10/p4xt-digital-multiplexing-transponder-project-program-proposal/

Phase 1 statement of work can be found at the summary document linked below.

Summary:
https://openresearch.institute/2020/02/21/summary-proposal-open-research-institute-phase-1-p4xt/

Established in 1973 by the American Radio Relay League, Inc. (ARRL) as an independent and separate 501(c)(3) organization, the ARRL Foundation administers programs to support the Amateur Radio community.

Funded entirely by the generous contributions of radio amateurs and friends, ARRL Foundation administers programs for Amateur Radio award scholarships for higher education, award grants for Amateur Radio projects, and award special Amateur Radio program grants for The Victor C. Clark Youth Incentive Program and The Jesse A. Bieberman Meritorious Membership Program.

Find out more about the ARRL Foundation here: http://www.arrl.org/the-arrl-foundation

Here are some of the organizations that will appreciate your time, energy, effort, and enthusiasm.

ARISS is the home for AREx. ARISS can be found on the web at
https://www.ariss.org/

AMSAT North American is the home for ARISS. AMSAT is active in AREx in multiple roles and can be found on the web at
https://amsat.org

JAMSAT supports AREx and has partnered with ORI to work on the Gateway Ground Station. JAMSAT can be found on the web at
https://www.jamsat.or.jp

Open Research Institute supports AREx and open source amateur radio research & development, primarily microwave.

Find ORI on the web at
https://openresearch.institute

P4XT Digital Multiplexing Transponder Project Program Proposal

Greetings all,

This is our P4XT Digital Multiplexing Transponder Project Program Proposal. It’s the result of multiple revisions and a lot of work.

We recognize Wally Ritchie WU1Y for taking on the majority of the writing duties. He has crafted quality work from a wide variety of input, commentary, argument, and critique. He has clarified our intentions and ambitions into a quality proposal.

It is ready for publication and distribution.

Current version can be found at:
p4xt_proposal