Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Summary

This change adds more info on the Gemini TX PCB designed by the EE team, used in the Ground System’s Control link.

Date

Status

SUBMITTED

Change Requestee

Farris Matar

Reviewers!

Mech: < list names >

EE: Michael Botros Nolan Haines Jerry Tian

EFS: Derek Tang

Auto: < list names >

Directors: Anthony Luo

Technical Details/Changelog

Listed additional info on the Gemini PCB, including:

  • Info on powering the PCB (nom. voltage + current consumption)

  • A wiring diagram showing how the PCB connects to other parts of the system during standard operation

    • Warning will be added to advise not to power the Gemini without antennas connected

  • Definitions for the RGB status LED

  • Link to Gemini PCB wiki page on Electrical space for info on programming the board

Content to be Added:

Wiring diagram of Gemini board during standard operation:

RGB LED Status indications (taken from ELRS wiki)

LED Indication

Status

Rainbow fade effect

Starting up

Green heartbeat

Web update mode enabled

Blue heartbeat

Bluetooth joystick enabled

Red flashing on/off every 100ms

Radio chip not detected

Orange flash every second

No handset connection

Solid single colour

Connected to receiver, colour indicates packet rate

Fading single colour

No connection to receiver, colour indicates packet rate

Link to Electrical space page on Gemini TX PCB (for guide on programming the board): ELRS Gemini TX - Programming the Gemini TX.

Arch doc implementation Info

Going in the RF + Peripherals section, under the Command subheading.

Reason for change

Provide clarity on the Gemini is implemented with the Ground System + how to use/connect it

Priority

Medium - Not urgent, but the sooner it is added the better to make the arch. doc as complete as possible for those who need the info

Impact of Not Responding to Change

Ambiguity on how to connect to & use the Gemini, could slow down testing & make it harder when transferring projects over/assigning new testers.

What Groups, People, Sub-Teams Need to be Notified?

  • Only the EE leads & the EFS lead who handled programming the Gemini, just to ensure information added is accurate. They have already been pinged as reviewers for this RFC

Approvals & Reviews

< space for reviewers to leave thoughts / approvals? >

Name

Approve/Deny?

Reason

  • No labels