skills.rest
OpenSkyHawk
OpenSkyHawkOFFICIAL
Explore all skills by this author →
GitHub

full-stack

Trace cockpit control signal flows from hardware through CAN bus to DCS-BIOS.

3|Updated Apr 29, 2026
Search Tags:#integration#firmware#can-bus#dcs-bios#avionics#openskyhawk
One-click install
npx skills add https://github.com/OpenSkyHawk/OpenSkyhawk --skill full-stack-openskyhawk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: full-stack
Source: https://github.com/OpenSkyHawk/OpenSkyhawk/tree/main/.claude/skills/full-stack
Command: npx skills add https://github.com/OpenSkyHawk/OpenSkyhawk --skill full-stack-openskyhawk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill resolves ambiguity in the OpenSkyhawk hardware-firmware-software stack by providing a unified map of how physical cockpit controls communicate with DCS.

Core Features & Use Cases

  • Signal Tracing: Trace a control input from the physical switch through the PCB, CAN bus, and PanelBridge to the DCS-BIOS output.
  • Layer Ownership: Clarify which domain (CAD, PCB, Firmware, or Mapping) is responsible for specific system behaviors or debugging tasks.
  • Use Case: When a switch on the Center Console fails to trigger an action in DCS, use this Skill to determine if the issue lies in the PCB wiring, the CAN protocol dispatch, or the DCS-BIOS configuration.

Quick Start

Use the full-stack skill to trace the signal path for the armament panel switches from the physical hardware to the DCS-BIOS interface.

Frequently Asked Questions about full-stack

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I trace a physical cockpit control input to DCS-BIOS?▼

To trace a physical cockpit control input to DCS-BIOS, you map the signal path from the physical switch through the PCB, CAN bus, and PanelBridge architecture to the final DCS-BIOS output. This clarifies which domain owns the behavior.

Why does my Center Console switch fail to trigger an action in DCS?▼

When a Center Console switch fails to trigger an action, use signal tracing to determine if the issue originates in the PCB wiring, the CAN protocol dispatch, or the DCS-BIOS configuration. This isolates the exact layer causing the failure.

How does the CAN bus PanelBridge architecture connect physical avionics nodes to DCS?▼

The CAN bus PanelBridge architecture connects physical avionics nodes to DCS by routing physical cockpit control inputs through a hardware-firmware-software stack. It requires adherence to defined UART, CAN, and HID communication standards for all nodes.

Do I need specific communication standards for avionics node integration with DCS-BIOS?▼

Yes, avionics node integration with DCS-BIOS requires strict adherence to defined UART, CAN, and HID communication standards. These standards ensure physical cockpit control inputs correctly communicate with the DCS simulation environment.

What is the best way to debug cross-layer hardware-firmware-software signal flows?▼

The best way to debug cross-layer hardware-firmware-software signal flows is to clarify layer ownership across CAD, PCB, Firmware, or Mapping domains. This determines which specific domain is responsible for the system behavior or debugging task.

Related Skills

Explore More Software Engineering Skills→
feasibleonefeasibleone
1

blong-codec

Implement and compose HTTP and TCP communication protocols in Blong applications.

Official
Advanced
OpenSkyHawkOpenSkyHawk
3

panel-mapping

Convert DCS-BIOS control mappings and model coordinates into hardware specifications.

Official
Advanced
pjcaupjcau
2

design-intent

Validate GPIO mappings and signal paths across firmware, schematic, PCB, and datasheet sources.

Community
Advanced
beriberikixberiberikix
59

connectivity-usb-can

Bridge USB device classes and CAN controllers in Zephyr RTOS.

Community
Advanced