added eps hardware troblueshoot guides

Author: balotofi

_site/index.html

@@ -21,75 +21,8 @@ time to complete: 7 mins
 </details>
 
 
-
-
-``` mermaid
-flowchart LR
-
-  subgraph Power_Lines
-    RAW[RAW POWER]
-    DCDC1[DC/DC → 3.3V #1]
-    DCDC2[DC/DC → 3.3V #2]
-    DCDC3[DC/DC → 5.0V]
-    DCDC4[DC/DC → Unreg #1]
-    DCDC5[DC/DC → Unreg #2]
-    RAW --> DCDC1 --> MAIN_PIC
-    RAW --> DCDC2 --> COM_PIC
-    RAW --> DCDC3 --> RESET_PIC
-    RAW --> DCDC4 --> START_PIC
-    RAW --> DCDC5 --> BURNER
-  end
-
-  subgraph OBC_Module
-    MAIN_PIC[MAIN PIC]
-    COM_PIC[COM PIC]
-    RESET_PIC[RESET PIC]
-    START_PIC[START PIC]
-    MAIN_FM[MAIN FM]
-    COM_FM[Shared COM FM]
-    MSN_FM[Shared MSN FM]
-    MUX1[MUX 1]
-    MUX2[MUX 2]
-  end
-
-  MAIN_PIC -- SPI --> MUX1
-  MUX1 -- SPI --> MAIN_FM
-
-  COM_PIC -- SPI --> MUX2
-  MUX2 -- SPI --> COM_FM
-
-  MAIN_PIC -- UART --> COM_PIC
-  MAIN_PIC -- UART --> RESET_PIC
-  COM_PIC -- UART --> START_PIC
-  RESET_PIC -- UART --> START_PIC
-
-  MAIN_PIC -- SPI --> MSN_FM
-  COM_PIC -- UART --> OLD_TRX
-  COM_PIC -- UART --> NEW_TRX
-
-  subgraph External_Components
-    CPLD[CPLD]
-    FAB_PIC[FAB PIC]
-    MSN_BOSS[MSN BOSS]
-    BURNER[BURNER CCT]
-    UHF[UHF TRX]
-    OLD_TRX[OLD TRX - ADDNICS]
-    NEW_TRX[NEW TRX]
-  end
-
-  MSN_BOSS -- UART --> MAIN_PIC
-  CPLD -- UART --> MSN_BOSS
-  FAB_PIC -- UART --> MAIN_PIC
-  MAIN_PIC -- UART --> BURNER
-  BURNER -- Power --> UHF
-```
-
-
-
 In designing the mission circuit of the Birds system, what are the conditions for the supplied voltages and signal inputs and outputs? 
 
-
-
 {: .label} 
 eps 
 
@@ -281,6 +214,13 @@ Such a power meter is available, but currently, BIRDS-5 is in the FM stage and i
      - Quickly begin the second charge-discharge test after recording all physical parameters (OCV, mass, diameter, length).  
      - Record and compare results for consistency.  
 
+
+
+
+
+
+
+
 **61. Details on Setting Cells in the Chamber for Testing**  
 
 - **Question:** Can the cells be set individually instead of bundling them with Kapton tape? For example, could Eneloop plastic cases be used, and if so, should the top of the case be opened to maintain the same pressure for all cells?  

eps-members/eps-faq.md

@@ -0,0 +1,161 @@
+---
+title: EPS Hardware
+layout: default
+# permalink: "/faq"
+lang: en
+---
+
+# EPS Hardware
+
+
+# Guide to the Electrical Power System (EPS) on the BIRDS Platform
+
+{: .no\_toc }
+
+**Estimated time to complete:** 7 minutes
+{: .label}
+
+This guide provides practical insights and frequently asked questions (FAQs) related to the **Electrical Power System (EPS)** used in the BIRDS satellite platform. It is aimed at new EPS team members who are onboarding or seeking clarity on implementation and testing practices.
+
+---
+
+<details markdown="block">
+<summary>Table of Contents</summary>
+
+* [System Overview](#system-overview)
+* [Power Line Configuration](#power-line-configuration)
+* [Fuse Configurations and LED Indicators](#fuse-configurations-and-led-indicators)
+* [Testing and Debugging Practices](#testing-and-debugging-practices)
+* [Sensor Behavior and I/O Behavior](#sensor-behavior-and-io-behavior)
+* [Tips from Past Missions](#tips-from-past-missions)
+* [Additional Q\&A](#additional-qa)
+
+</details>
+
+---
+
+## System Overview
+
+The EPS module is central to distributing regulated power to all satellite subsystems. It includes multiple **DC-DC converters**, **fuses**, **analog-digital converters (ADCs)**, and **microcontrollers** that help manage power delivery and monitoring.
+
+EPS typically interfaces with four microcontrollers (PICs):
+
+* **MAIN PIC** — core controller
+* **COM PIC** — communications controller
+* **RESET PIC** — responsible for satellite resets
+* **START PIC** — used at startup
+* Other components include: **burn wires**, **MUXes**, **shared flash memories**, and **external interfaces (e.g., UART, SPI)**
+
+---
+
+## Power Line Configuration
+
+```mermaid
+flowchart LR
+
+  subgraph Power_Lines
+    RAW[RAW POWER]
+    DCDC1[DC/DC → 3.3V #1]
+    DCDC2[DC/DC → 3.3V #2]
+    DCDC3[DC/DC → 5.0V]
+    DCDC4[DC/DC → Unreg #1]
+    DCDC5[DC/DC → Unreg #2]
+    RAW --> DCDC1 --> MAIN_PIC
+    RAW --> DCDC2 --> COM_PIC
+    RAW --> DCDC3 --> RESET_PIC
+    RAW --> DCDC4 --> START_PIC
+    RAW --> DCDC5 --> BURNER
+  end
+
+  subgraph OBC_Module
+    MAIN_PIC[MAIN PIC]
+    COM_PIC[COM PIC]
+    RESET_PIC[RESET PIC]
+    START_PIC[START PIC]
+    MAIN_FM[MAIN FM]
+    COM_FM[Shared COM FM]
+    MSN_FM[Shared MSN FM]
+    MUX1[MUX 1]
+    MUX2[MUX 2]
+  end
+
+  MAIN_PIC -- SPI --> MUX1
+  MUX1 -- SPI --> MAIN_FM
+
+  COM_PIC -- SPI --> MUX2
+  MUX2 -- SPI --> COM_FM
+
+  MAIN_PIC -- UART --> COM_PIC
+  MAIN_PIC -- UART --> RESET_PIC
+```
+
+The diagram above illustrates how **RAW power** is distributed to different voltage rails and used to power various microcontrollers and functional blocks.
+
+---
+
+## Fuse Configurations and LED Indicators
+
+* **Fuses** are placed on each regulated power line to prevent damage during overcurrent conditions.
+* The **LED indicators** next to each fuse are useful for visually identifying which lines are live or broken.
+* Use a **multimeter in continuity mode** to test fuses and trace broken power lines.
+* Fuses are surface-mounted; replacement or bridging should be done cautiously.
+
+---
+
+## Testing and Debugging Practices
+
+### Using External Power Supplies
+
+* During board-level testing, it is often better to use **bench power supplies** with current limiting features instead of satellite batteries.
+* Apply power to the `RAW` or `VBAT` pin with a regulated 8–12 V source.
+
+### Ground Station Test Environment
+
+* Ground Station programs are often developed using **Visual Studio Community** (free). The paid **Professional version** is not required.
+
+### RF Shielding for Command Testing
+
+* In some cases, a metal (aluminum) box is used to shield antennas during integration testing to simulate realistic RF conditions.
+
+---
+
+## Sensor Behavior and I/O Behavior
+
+### Battery Temperature Sensor Behavior
+
+* The **temperature sensor** in the battery box outputs a voltage that **decreases with increasing temperature**.
+* The **heater control** works such that:
+
+  * `RD0 = 1` → heater ON
+  * `RD0 = 0` → heater OFF
+
+### Signal Interrupts on the FAB
+
+* For signals like `DEPSW4` that seem interrupted at connectors like `J15`, this is **intentional by design**.
+* In many cases, **jumper pins or manual soldering** are added post-fabrication for continuity.
+
+---
+
+## Tips from Past Missions
+
+### Communication Between COM PIC and Reset PIC
+
+Although the **circuit diagram** shows a UART connection between COM PIC and Reset PIC, this is not functionally implemented in the firmware.
+
+* The UART connection exists on the schematic for **debugging and flexibility**, but was not needed for the flight version.
+* `RB6` and `RB7` on the Reset PIC are reserved for UART during development to send data directly to a PC for debugging, bypassing the Main PIC.
+
+### Software Update Limitations
+
+> **How were software updates and patches handled for BIRDS satellites after launch?**
+> *Software updates were not possible after launch due to hardware constraints. Therefore, robust testing was performed before launch to reduce the risk of in-orbit issues.*
+
+---
+
+## Additional Q&A
+
+We continue to update this guide as new experiences are gained across missions.
+
+If you have additional questions, please contact your EPS mentor or refer to the EPS debug manual.
+
+

eps-members/eps-hardware.md

@@ -0,0 +1,118 @@
+---
+title: EPS Troubleshoot
+layout: default
+# permalink: "/faq"
+lang: en
+---
+
+# EPS Troubleshoot
+
+### 🛰️ EPS Troubleshooting and Design Guide for BIRDS Satellite Platform
+
+This guide is derived from frequently asked questions and technical insights about the Electrical Power System (EPS) of the BIRDS satellite platform. It is intended for engineering students, subsystem leads, or technical partners working on nanosatellite development using BIRDS heritage.
+
+---
+
+## 1. 🔌 Understanding Battery Heater Control and Temperature Sensing
+
+**Controlling the Battery Heater**
+
+* The battery heater is controlled via the RD0 signal line.
+* Logic level interpretation:
+
+  * `RD0 = 1` → Battery Heater ON
+  * `RD0 = 0` → Battery Heater OFF
+
+**Temperature Sensor Output Behavior**
+
+* Inside the battery box, the temperature sensor's voltage output decreases as temperature increases.
+* This analog signal allows the OBC to determine temperature thresholds and activate the heater accordingly.
+
+---
+
+## 2. 🔍 Analyzing DEPSW4 Signal Behavior
+
+**Circuit Observation**
+
+* The DEPSW4 signal is visually disconnected at jumper `J15` on the FAB board.
+* As a result, it does not reach transistors Q9 and Q10 unless continuity is restored.
+
+**Clarification from Kyutech**
+
+* This is not a mistake — it is part of the design.
+* A **jumper pin** is used to bridge this disconnection manually, if needed.
+* This design choice adds flexibility during integration testing.
+
+> 📎 Refer to the schematic: `87_BIRDS BUS Board_Jumper Pin.png`
+
+---
+
+## 3. 🧠 Software Updates Post-Launch: Limitations
+
+**Key Insight:**
+
+* Software updates are **not possible** after launch due to hardware constraints.
+* This places **enormous importance** on ground-based validation of software.
+
+**Best Practices:**
+
+* Perform exhaustive simulation and hardware-in-the-loop (HIL) testing pre-launch.
+* Include redundancy in logic for EPS decision-making.
+* Ensure watchdog timers and failsafes are functional.
+
+---
+
+## 4. 🛠️ UART Communication Between COM PIC and Reset PIC
+
+### Circuit Design vs Implementation
+
+* The BIRDS5 schematic shows a UART connection between Reset PIC and COM PIC.
+* However, this UART is **not active** in the firmware.
+
+**Explanation:**
+
+* UART functionality was reserved as a feature but not implemented.
+* Therefore, while the lines exist in the schematic, there is no data exchange at runtime.
+
+### Purpose of RB6 and RB7 UART Lines
+
+* These lines on Reset PIC were likely meant for:
+
+  * **Direct debugging**
+  * **Standalone verification** of Reset PIC firmware
+* During normal debugging, access to Reset PIC is through Main PIC.
+* If debugging fails, it’s unclear whether the Main or Reset PIC is at fault.
+* Direct UART enables bypassing this dependency.
+
+---
+
+## 5. 🧪 Ground Testing Setup
+
+**Aluminum Box Testing**
+
+* For RF tests, an **aluminum box** is used to house the antenna and isolate signals.
+* This prevents unintended radiation and interference.
+
+**Community Request:**
+
+* Teams often ask for specs or photos of the aluminum box setup for replication.
+* Suggest documenting the testing environment in integration manuals.
+
+---
+
+## 6. 🖥️ Development Environment for Ground Station Software
+
+**Visual Studio Version**
+
+* Visual Studio is used for ground station software development.
+* The **free Community version** is sufficient.
+* There is no technical need to use the paid Professional version unless you require additional enterprise features.
+
+---
+
+## 🔚 Final Notes
+
+* The BIRDS EPS design is compact, modular, and tested in multiple flight missions.
+* Small changes in jumpers, debug ports, and unused lines are **intentional**, often driven by the need to balance flexibility and reliability in educational missions.
+* Understanding these nuances ensures smoother subsystem integration and better troubleshooting during your satellite project.
+