I am a Computer Engineering student and system builder focused on autonomous, embedded, and field-deployed systems.

My engineering background began with electronics and embedded production workflows — including PCB, BOM, Gerber, SMT, firmware testing, Linux/UART equipment, and hardware-software integration.

Today, I am expanding that foundation into:

• UAV / VTOL mission systems
• ROS2 / PX4 / MAVLink
• embedded and mission software
• telemetry and diagnostics
• GNSS / RTK
• field communication systems
• disaster-response platforms
• AI / edge vision
• system integration and verification

I am particularly interested in systems where software must operate together with:

flight controllers + onboard computers + sensors + communication links + networks + operators + real hardware

Requirement
    ↓
System Boundary
    ↓
Hardware / Interface
    ↓
Embedded / Communication
    ↓
Mission Logic
    ↓
Operator / GCS / Service
    ↓
Verification
    ↓
Evidence

My long-term direction is to grow from an engineer who can build and verify systems into a technical project / program leader capable of understanding the systems being led.

Software Architecture · Scenario Engine · MAVLink · Evaluation Evidence

Designed and implemented an internal software PoC for a vendor-independent UAV training and evaluation architecture.

Drone / Simulator
       ↓
Generic Adapter
       ↓
Common Drone State
       ↓
Scenario Engine
       ↓
Training Log
       ↓
Evaluation Evidence
       ↓
Rule Evaluation
       ↓
AAR / Evidence Bundle

• Common Drone State model
• movement-path extension
• SYSTEM / TRAINEE input separation
• generic MAVLink adapter
• decoded-stream pipeline
• live-input boundary
• 8-step internal scenario flow
• Common Training Log
• response-time evidence derivation
• rule-based evaluation adapter
• AAR Markdown generation
• Training Log / Evaluation JSON export
• requirements / ConOps / data-dictionary alignment
• automated regression testing

Boundary: Internal technical PoC only. It is not presented as an official military requirement implementation or hardware acceptance result.

Gateway Software · Interfaces · Field Test Preparation

Worked on a field gateway architecture for connecting devices, positioning systems, and backend services.

• serial auto-reconnect
• GNSS NMEA parsing
• NTRIP connection
• RTCM correction-data reception
• local buffering / resend
• backend status reporting
• CAN / RS485 / Modbus integration planning
• hardware acceptance-test preparation

Field Device
    ↓
Serial / CAN / RS485
    ↓
Gateway
 ┌───────────────┐
 │ GNSS / NMEA   │
 │ NTRIP / RTCM  │
 │ Local Buffer  │
 │ Status / Log  │
 └───────────────┘
    ↓
Backend / Control System

Component Review · Integration Planning · Verification

Worked on integrating GNSS / RTK components into a field gateway system.

• reviewed ZED-F9P-class GNSS / RTK components
• organized purchase items and test criteria
• designed gateway integration flow
• separated software/mock verification from hardware verification
• prepared NMEA / RTCM / RTK Fix field-test boundaries

A recurring principle in this work was to clearly distinguish:

Implemented
    ≠
Simulated
    ≠
Hardware Verified

Requirement Analysis · Technical Comparison · Test Design

Evaluated portable MANET / Mesh relay candidates for field communication environments.

• NLOS communication
• multi-hop operation
• throughput
• latency
• transmission distance
• power / battery
• weight
• environmental protection
• certification
• drone-carried / deployable relay constraints

• network deployment time
• position-update interval
• information-sharing success rate
• system availability

Supplier claims, confirmed specifications, engineering judgment, and unresolved items were tracked separately.

Repository → vtol-autonomy-lab

PX4 VTOL mission-verification framework exploring how autonomous mission responsibilities should be separated.

• MissionRaw / MAVSDK Action / Offboard responsibility separation
• Virtual FC
• mission state machine
• Failsafe Supervisor
• Command Guard
• fault-scenario verification
• mission consistency checks
• automated testing
• target-estimation experiments

Only work I personally participated in is described here. Company source code, credentials, customer / agency details, internal networks, and non-public requirements are intentionally excluded.

Frontend Restructuring · Integration Review · Documentation

• analyzed an existing integrated-control frontend
• redesigned a map-centered control-room structure
• resolved React / TypeScript build and merge issues
• reviewed backend API / DB integration boundaries
• documented implementation and verification status

Telemetry Troubleshooting · Network Analysis · Test Planning

• drone / controller / PC / GCS configuration review
• UDP / telemetry forwarding checks
• packet-level network troubleshooting
• external-network GPS Fix verification
• PC-side GCS connectivity boundary analysis
• acceptance-test checklist preparation

Requirement-Gap Analysis · Data-flow Design

Analyzed an end-to-end architecture connecting drone imagery with edge AI and XR visualization.

Drone / Camera
      ↓
Edge Vision
      ↓
Detection
      ↓
Realtime Bridge
      ↓
VR / XR

Work included:

• HW / AI / VR requirement mapping
• interface analysis
• end-to-end data-flow design
• confirmed / unconfirmed requirement separation
• implementation-gap documentation

System Concept · Requirement Review

• analyzed drone position / altitude / velocity / release-time relationships
• reviewed required technical inputs
• organized PoC architecture
• separated known inputs, assumptions, and unresolved criteria before implementation

Repository → skyedge_vtol

ROS2 / PX4-oriented UAV mission-system project.

• UAV mission flow
• ROS2 / PX4 integration structure
• telemetry and health monitoring
• guidance / waypoint concepts
• vision-assisted mission logic
• SITL-oriented verification

Outcome: 24th Korea Robot Aircraft Competition — 1st Preliminary Passed

Repository → mission-state-machine-cpp

Autonomous mission and failsafe logic implemented in C++.

• explicit mission-state transitions
• telemetry health checks
• failsafe behavior
• command validation
• mission-control structure

Repository → fieldops-embedded-diagnostic-suite

Embedded / field telemetry diagnostic toolkit.

• serial parsing
• GNSS monitoring
• telemetry inspection
• C-based scheduling logic
• log analysis
• field diagnostic workflow
• dashboard prototype

Repository → rescuemap-os

GIS-based disaster-response software.

• disaster map layers
• field information visualization
• vulnerable-user / missing-person response concepts
• failure-map reporting
• operational decision support

Repository → ghost-ant-handover

UAM communication handover optimization study.

• aerial-network handover
• signal strength / latency / load evaluation
• route-based scenarios
• optimization-oriented decision logic
• quantitative experiment logs

Repository → BioDockLab

Bio AI research and experiment platform.

• project planning
• system architecture
• prototype development
• experiment / analysis dashboard
• API-based result integration
• technical presentation and Q&A

🏆 Top Prize — 2026 Future Government Innovation Idea Contest

Repository → paejae-pick-2-app

Smart-campus student-life platform.

• service planning and development
• Flutter MVP
• campus information architecture
• department / club / cafeteria workflows
• real-device QA
• internal-test and release-scope management

🏆 Encouragement Award — 2026 Intelligent Innovation Idea Contest

Repository → verso-team/safe-search

AI safety-search concept for digital-crime victims.

• development planning
• service architecture
• risk-analysis flow
• AI-result integration
• privacy / sensitive-information handling
• Human-in-the-Loop structure
• multidisciplinary team coordination

Victim Input
    ↓
Sensitive Information Check
    ↓
Risk Classification
    ↓
Safe Query Generation
    ↓
Official Institution Guidance
    ↓
Confidence / Human Review

Repository → agriguard-aiot

Safety platform for elderly agricultural workers combining risk prevention, fall detection, and agricultural-machine safety.

• technical scope definition
• interface boundary definition
• sensor / GPS / edge / server / web integration
• FastAPI / WebSocket real-time architecture
• hardware / API / server / UI coordination
• development checkpoint management
• demo and presentation coordination

Student-led Interdisciplinary Project Lab Initiative

PAICHAI NEXUS is an initiative to connect students across majors through:

• real engineering problems
• multidisciplinary teams
• competitions
• research
• industry collaboration
• project-based portfolio development

Problem Discovery
      ↓
Interdisciplinary Team
      ↓
Prototype
      ↓
Verification
      ↓
Competition / Research / Industry
      ↓
Portfolio

Current work includes project-lab planning, project discovery, team formation, and external collaboration structure design.

Before and during university, I worked in environments involving both hardware and software.

• circuit / schematic review
• BOM management
• Gerber / PCB workflows
• SMT production
• hardware assembly and inspection
• firmware modification / testing support
• Linux / UART-based equipment
• i.MX6-based systems
• Zynq-based systems
• production troubleshooting
• cross-team technical communication

I also participated in aerospace / defense electronics production work within externally disclosable boundaries.

Specific customers, programs, subsystems, and circuit details are intentionally omitted.

This background strongly influenced how I approach software.

I prefer software that ultimately interacts with:

real hardware, vehicles, sensors, communication links, and field environments.

C · C++ · Python · Linux

ROS2 · PX4 · MAVLink · MAVSDK

UART · CAN · RS485 · Modbus

GNSS / RTK · NMEA · NTRIP · RTCM

i.MX6 · Zynq

PCB · BOM · Gerber · SMT

Hardware assembly / inspection / production workflow

OpenCV · YOLO

Kalman Filter — basic implementation

Telemetry Analysis

RAG / LLM Prototyping

FastAPI · REST API · WebSocket

Node.js · SQLite · PostgreSQL

Git · GitHub · Docker

pytest · Node Test Runner · GitHub Actions

Frontend and web technologies are used primarily when required for:

• GCS
• control interfaces
• operational dashboards
• visualization
• system integration

rather than as my main engineering identity.

Smaller repositories are used to strengthen low-level engineering fundamentals.

Some experimental repositories remain private while they contain unfinished or non-public technical context.

• 🏆 Top Prize — 2026 Future Government Innovation Idea Contest
• 🏆 Encouragement Award — 2026 Intelligent Innovation Idea Contest
• 🛩️ 1st Preliminary Passed — 24th Korea Robot Aircraft Competition
• 🛡️ TRAITHON — SAFE:SEARCH — AI Engineer / Development PM
• 🚜 National ICT Convergence AI Competition — AgriGuard AIoT — Technical PM
• 🏗️ LH Land Technology Competition — SiteLink
• 🚗 Future Mobility Industry Idea Competition — MobiThread-AI
• 🌍 Open Source Developer Competition — RescueMap OS
• 📡 UAM Olympiad — Ghost Ant Handover
• 🌲 Industry R&D — disaster communication / integrated-control systems
• 🧭 PAICHAI NEXUS — interdisciplinary project-lab planning

My preferred engineering process is:

Problem
   ↓
Requirement
   ↓
System Boundary
   ↓
Interfaces
   ↓
Implementation
   ↓
Failure Cases
   ↓
Test
   ↓
Evidence
   ↓
Documentation

I value:

• explicit system boundaries
• realistic hardware constraints
• reproducible testing
• failure / fallback handling
• interface documentation
• measurable evidence
• honest limitations
• clear distinction between implemented / simulated / unverified work
• communication between developers and non-developers

I am currently strengthening the fundamentals required for autonomous and embedded systems.

• Data Structures
• Operating Systems
• System Programming
• Robotics Fundamentals
• UAV Flight Software
• State Estimation / Sensor Fusion
• ROS2 / PX4 Architecture
• Real-time / Embedded Systems
• Communication / Networking
• Control and Mathematics for Autonomous Systems

My goal is not to separate theory from implementation.

I want to learn the theory required to:

understand → modify → verify → design → lead

real autonomous-system projects.

Electronics / Embedded
        ↓
Systems & Interfaces
        ↓
UAV / Robotics / Communication
        ↓
Mission Autonomy
        ↓
Multi-Unmanned Systems
        ↓
Technical Project Leadership
        ↓
Program / System Leadership

My long-term interest lies in systems that combine:

hardware + embedded software + robotics + communication + mission logic + AI + field operation

with a particular interest in:

autonomous aerospace, defense, and disaster-response systems.

• GitHub: https://github.com/gxmzung
• Email: leeyj4748@naver.com