Okay, here's a summary of the provided transcript in a self-contained bullet list format, including timestamps, important details, and key takeaways:

ORI FPGA Meetup and EVE Link Budget Discussion - Summary

• 0:10 Dwingeloo Telescope Tour: The meeting opens with a brief tour of the Dwingeloo radio telescope's control room, showcasing the equipment and observation setup.

• 1:32 Meeting Start: The Open Research Institute (ORI) meeting focuses on FPGA-based work and open-source digital radio for amateur bands.

• 2:34 Aaron's Update:

  • Discusses experimenting with Libre SDR and AntSDR E200 platforms.
  • Highlights their capabilities (Zinc 7020, Gigabit Ethernet, clocking interface with 12-bit DAC).
  • Plans to replicate a dvbs2 GSC end-to-end experiment.
  • Mentioned finding inexpensive FPGA (7020 for $30) and transceivers (89 363 for $45).

• 10:51 Paul and Matthew's Update (Opulent Voice Progress):

  • Discuss challenges in getting separate PlutoSDRs (transmitter and receiver) to communicate reliably using msk.
  • Recent success: Achieved zero bit error rate with separate transmitter and receiver Plutos using the same clock source.
  • Mystery: Tracking loops still show frequency offset even with a shared clock.
  • Next steps: More experiments with varied frequency errors and integral gain.
  • Mention of integrating a lock detector circuit and testing new frequency compensation circuit.

• 20:36 Earth-Venus-Earth (EVE) Project Introduction:

  • The goal is signal bouncing off Venus, extending practices of Earth-Moon-Earth communication.
  • Collaboration: Working with the Deep Space Exploration Society and European groups, including Dwingeloo.

• 22:54 Thomas Tamp's Update (Dwingeloo):

  • Reports successful tests bouncing signals off the Moon, coordinated with the Stocker telescope in Germany.
  • Collected a unique dataset, including transmit/receive data and cross-polarization signals.
  • Data is open and available online.
  • Used 30 different waveforms.
  • Mentioned a communications protocol based on Zadoff-Chu sequences, but notes potential patent issues.

• 25:58 Link Budget Discussion:

  • Michelle presents updates to the EVE link budget, including a roadmap, site data classes, and link budget calculations.
  • Focus on worst-case Doppler shift and rate of change, especially when Venus is closest.
  • New: Doppler spread analysis and its impact on signal bandwidth.
  • Mode Analysis: Evaluated amateur modes (Q, Whisper, FT8, CW, SSB, RTTY, PSK31, and FST) to determine which can close the link.
  • 41:50 Results, considering Doppler Spread: No modes close the link.

• 42:45 Zadoff-Chu Transmission Proposal:

  • Discusses using Zadoff-Chu sequences for ranging/synchronization (but can also be used for communications).
  • The approach considers Doppler rate of change to determine the longest tolerable integration time.

• 44:51 Pete's Feedback on Zadoff-Chu Proposal:

  • Presents a table summarizing the relationship between Doppler spread, coherent integration time, and required transmission duration for a 13 dB detection SNR.
  • Key takeaway: Signals need to be very long (hours) to achieve the desired SNR.
  • Highlights the tight coupling between C/N0 and Doppler spread.
  • Notes difference in non-coherent averaging assumptions (5 log n vs. 10 log n).

• 52:10 Discussion on SNR Target:

  • Questioning the 13 dB SNR target; JPL work often used a lower threshold.
  • Lowering the SNR target significantly reduces required transmission duration.

• 54:11 Coherent Integration Time Discussion:

  • Michelle used maximum Doppler rate of change to calculate maximum integration time (1.34 seconds, worst case).
  • Pete uses varying Doppler spreads (1 Hz, 2 Hz, 10 Hz, and 20 Hz) to calculate coherent integration times.

• 57:18 Non-coherent Averaging Clarification:

  • Pete noted that 5 log n should be used at low SNR, not 10 log n, impacting signal duration calculations.
  • Michelle agreed to change to 5 log n.

• 58:12 Frequency Assumption:

  • The current calculations assume 1296 MHz; 2304 MHz is also possible next year.

• 58:37 Validation with Moon Bounce:

  • Suggestion to validate assumptions by using Moon bounce data.

• 1:00:00 Wrap-up:

  • Acknowledgment of progress and contributions.
  • Plan for continued work and another meeting next week.