fprime-fpp-navigation
Skill12k starsChanged 21 months agoApache-2.0View on GitHub
Answer questions about an F Prime component or topology from the FPP model instead of reading autocoded C++. Covers grep recipes for the `.fpp` keywords, the FPP-to-C++ naming table (handlers, commands, events, telemetry, parameters, tester base), where autocode lives, and codegen gotchas. Use before opening a `*Ac.hpp`, before guessing a handler or macro name, and when tracing wiring across a topology. Keywords: F Prime, FPP, grep, handler name, autocode, Ac.hpp, TesterBase, topology wiring, port type.
Trending
More talk lately.about the whole repository
Who's talking about nasa/fprime
- Vibernets Streaming“Linux on Mars - NASA Mars Helicopter (අඟහරු ගිය Linux)”YouTube · Mar 3, 2021 · 12k views
- Suck Less | Tym Rabchuk“You Can Actually Build a Spacecraft With This #nasa #space #diy”YouTube · Jun 30, 2026 · 1.7k views
- こぶたNEWS“宇宙で初めての火星ヘリコプター”YouTube · Apr 10, 2021 · 741 views
- Marcia en Desplegando Cloud“🇪🇸#5.17 - Python en Acción (Podcast Charlas Técnicas de AWS)”YouTube · Nov 5, 2024 · 281 views
- Gourcer“Gource visualisation: nasa/fprime on 2021-04-22”YouTube · Apr 22, 2021 · 179 views
The biggest 5 of 71 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 71
Talked about on GitHub, YouTube, Hacker News and the web (71 times).
On GitHub · 50
- Aug 19, 2026Add FPP (F Prime Prime) language — github-linguist/linguist15 reactions · 4 comments
- Sep 21, 2026Add New Darkmode UI Option — nasa/fprime-gds2 reactions
- Jul 31, 2025Deprecate serialize/deserialize in favor of [de]serialize[From/To] — nasa/fpp2 reactions · 1 comment
- Mar 19, 2026Add ConsoleNoWait — fprime-community/fprime-vxworks1 reaction
- Nov 22, 2025Merge release/v3.1.0a12 into release/v3.1.0 — nasa/fpp1 reaction
45 more on GitHub
- Oct 13, 2025Add ComAggregator for nasa/fprime#4264 — fprime-community/fprime-workshop-led-blinker1 reaction
- Dec 20, 2021FPP Visualization Automation — nasa/fprime-tools1 reaction · 5 comments
- Nov 10, 2026Svc/DpWriter: add processing override commands to force data product processing types on or off — lestarch-autobot/fprime0 reactions · 1 comment
- Oct 29, 2026Update for nasa/fprime#6174: add ComQueue drop-counter telemetry to packets — fprime-community/fprime-yamcs-reference0 reactions
- Oct 29, 2026Update for nasa/fprime#6174: add ComQueue drop-counter telemetry to packets — fprime-community/fprime-zephyr-reference0 reactions
- Oct 29, 2026Update for nasa/fprime#6174: add ComQueue drop-counter telemetry to packets — nasa/fprime-examples0 reactions
- Oct 28, 2026Update for nasa/fprime#6278: define FwTlmPacketizeOffsetType in TlmPacketizerCfg.fpp — fprime-community/fprime-zephyr-reference0 reactions
- Oct 28, 2026Restrict checkTimers and tlmWrite to having a single message on the q… — FireflySpace/fprime0 reactions
- Oct 24, 2026Upgrade to F Prime v4.4.1 — Open-Source-Space-Foundation/proves-core-reference0 reactions
- Oct 23, 2026TlmPacketizer: address lestarch-autobot review must-fix items (nasa/fprime#6144) — FireflySpace/fprime0 reactions
- Oct 16, 2026Include annotation for packets from FPP in dictionary — nasa/fpp0 reactions · 3 comments
- Oct 14, 2026Manual merge from nasa devel #5996 (pktType) — FireflySpace/fprime0 reactions
- Oct 12, 2026Svc/GenericHub: drop message with event and counter on allocation failure instead of asserting — JPL-Devin/fprime0 reactions · 1 comment
- Sep 30, 2026CI: fold workflow_dispatch runner/jobs inputs into the Ref and Framework matrices — JPL-Devin/fprime0 reactions · 1 comment
- Sep 22, 2026docs: import LED Blinker timeliness.md into website build — JPL-Devin/fprime0 reactions · 1 comment
- Sep 17, 2026Check C++ formatting — fprime-community/fprime-baremetal0 reactions
- Sep 14, 2026WasmSequencer: give the I32 host resume its own pause-check choice — JPL-Devin/fprime0 reactions · 1 comment
- Sep 11, 2026Fw/Types: serialize bool via U8 path and static-assert pointer size — JPL-Devin/fprime0 reactions · 1 comment
- Sep 1, 2026Rename LinuxUartDriver to PosixUartDriver with deprecated compatibility layer — JPL-Devin/fprime0 reactions · 2 comments
- Aug 22, 2026Feature: DFA-based structural health monitor app for telemetry channels — nasa/cFS0 reactions · 9 comments
- Jul 17, 2026Add TypeDemo component — fprime-community/fprime-yamcs-reference0 reactions
- Jun 22, 2026Add README.md and How-To guide for developing cFS F Prime applications — JPL-Devin/fprime_cfs_reference0 reactions · 2 comments
- Jun 16, 2026Use pr-xxxx pattern for GDS across Integration Test CI — JPL-Devin/fprime0 reactions · 3 comments
- May 29, 2026[#5159] ROSES - Student Review of Rule-Based Testing — lestarch-autobot/fprimesays it tested it0 reactions
- May 29, 2026[#5115] ROSES - Document how to decide between Active/Passive/Queued component - Student Review — lestarch-autobot/fprime0 reactions
- May 29, 2026[#5111] CCSDS Improvements — lestarch-autobot/fprime0 reactions
- May 29, 2026[#5099] DpCatalog Discards Status When Handling StateFile Database — lestarch-autobot/fprime0 reactions
- May 29, 2026[#5051] Add CI run exercising non-default FwType config values — lestarch-autobot/fprime0 reactions
- May 29, 2026[#5018] Replace hand-coded buffer and string classes with instantiated templates — lestarch-autobot/fprime0 reactions
- May 29, 2026[#4846] Add `fprime-util new --config-module` — lestarch-autobot/fprime0 reactions
- May 29, 2026[#4841] DpWriter always deallocates buffers to the same BufferManager — lestarch-autobot/fprime0 reactions
- May 29, 2026[#4806] Change fprime-gds serializable array type representation — lestarch-autobot/fprime0 reactions
- May 29, 2026[#4792] Consolidate Parameters ground scripts — lestarch-autobot/fprime0 reactions
- May 29, 2026[#4745] Update Core components to use FPP constants for string arguments — lestarch-autobot/fprime0 reactions
- May 29, 2026[#4711] fprime_test_api: Sometimes fprime_test_api does not connect to currently running fprime-gds session — lestarch-autobot/fprime0 reactions
- May 29, 2026[#4697] ROSES - Student Review of ISR pattern — lestarch-autobot/fprime0 reactions
- May 29, 2026[#4535] Configurable CPU Affinity for Subtopologies — lestarch-autobot/fprime0 reactions
- May 29, 2026[#4508] ROSES - Student review - Memory management — lestarch-autobot/fprime0 reactions
- May 29, 2026[#4454] VxWorks CI To Build All — lestarch-autobot/fprime0 reactions
- May 29, 2026[#4425] PrmDb filename in subtopology should be configurable — lestarch-autobot/fprime0 reactions
- May 29, 2026[#4324] Switch `FW_PACKET_COMMAND` enumerated value to non-zero value — lestarch-autobot/fprime0 reactions
- May 29, 2026[#4290] Clean up setup — lestarch-autobot/fprime0 reactions
- May 29, 2026[#4099] ROSES - Subtopologies (Working With) - Student Review — lestarch-autobot/fprime0 reactions · 1 comment
- May 29, 2026[#3662] ROSES - Add integration tests for fprime-examples repository — lestarch-autobot/fprime0 reactions
- May 29, 2026[#3565] Add local script to preview website rendering — lestarch-autobot/fprime0 reactions
On YouTube · 13
- Mar 3, 2021Linux on Mars - NASA Mars Helicopter (අඟහරු ගිය Linux) — Vibernets Streaming12k views · 50 comments
- Jun 30, 2026You Can Actually Build a Spacecraft With This #nasa #space #diy — Suck Less | Tym Rabchuk1.7k views · 2 comments
- Apr 10, 2021宇宙で初めての火星ヘリコプター — こぶたNEWS741 views · 3 comments
- Nov 5, 2024🇪🇸#5.17 - Python en Acción (Podcast Charlas Técnicas de AWS) — Marcia en Desplegando Cloud281 views · 2 comments
- Apr 22, 2021Gource visualisation: nasa/fprime on 2021-04-22 — Gourcer179 views
8 more on YouTube
- Feb 21, 2021Gource visualisation: nasa/fprime on 2021-02-21 — Gourcer157 views
- May 2, 2021Ferhell News 3 - Winget, WSL, Banimento da Universidade de Minessota e o Linux no Espaço! — Ferhell Linux & Techs117 views · 14 comments
- Jul 12, 2026GitHub - nasa/fprime: F´ - A flight software and embedded systems framework — GitHub Daily Trend AI Podcast95 views
- Feb 22, 2021Gource visualisation: nasa/fprime on 2021-02-22 — Gourcer70 views
- Oct 10, 2026NASA’s F Prime Turns Flight Software Into Components — Cochran Labs59 views
- Jul 2, 2026NASA fprime - A flight software — RandomTechAce37 views
- Jul 12, 2026nasa/fprime - Gource visualisation — Gourcer36 views
- Jul 4, 2026Почему эти 8 проектов уже изменили будущее? #Shorts — GitHub Находки3 views
On Hacker News · 6
- Feb 18, 2021The open source flight code that the NASA Mars drone is running68 points · 3 comments
- Feb 19, 2021Vue.js is powering NASA flight software4 points
- Jan 31, 2024NASA/fprime: F´ – A flight software and embedded systems framework2 points
- Jan 26, 2024F Prime – Flight software framework by NASA2 points
- Jan 21, 2024F': Ingenuity's Open-Source Flight Software Framework2 points
1 more on Hacker News
- Feb 1, 2024Fprime – A flight software and embedded systems framework by NASA1 point
On the web · 2
- Jul 12, 2026nasa/fprime: F´ - A f… - GitHub Daily Trend - Apple 팟캐스트 — podcasts.apple.com
- Jul 12, 2026nasa/fprime: F´ - A f... - GitHub Daily Trend — podcasts.apple.com
In this repository41 other files it gives its agents.
- AGENTS.mdAGENTS.md
- cmake/AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- agent-skill-authoringSkill
- ai-session-reportSkill
- ai-session-summarySkill
- ci-test-runtime-policySkill
- fprime-checklist-closeoutSkill
- fprime-checklist-designSkill
- fprime-checklist-implementationSkill
- fprime-cmake-build-systemSkill
- fprime-component-checklist-reviewSkill
- fprime-component-design-fppSkill
- fprime-component-developmentSkill
- fprime-component-implementationSkill
- fprime-component-integration-testSkill
- fprime-component-requirementsSkill
- fprime-component-unit-testSkill
- fprime-cpp-designSkill
- fprime-ground-input-tracingSkill
- fprime-hardware-input-tracingSkill
- fprime-issue-risk-evaluationSkill
- fprime-iterative-developmentSkill
- fprime-maintenanceSkill
- fprime-requirements-reviewSkill
- fprime-run-for-recordSkill
- fprime-system-test-designSkill
- fprime-system-test-harnessSkill
- fprime-test-oracleSkill
- fprime-topology-developmentSkill
- fprime-unit-testingSkill
- jpl-design-principlesSkill
- maintainer-lookupSkill
- post-inline-reviewSkill
- pr-diff-scopingSkill
- prompt-injection-precheckSkill
- re-review-stateSkill
- triage-classifierSkill
- write-system-functional-docSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 78
Look inside connections blocks and at the pattern specifiers (command connections instance CdhCore.cmdDisp, event connections instance …
- Very specific: line 150
Only deployment topology X autocodes <X>TopologyAc.*.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill: Querying the F Prime model
The .fpp file is the source of truth and is much smaller than the
autocode it produces. Every generated C++ name is a deterministic
function of the model, so read the model and derive the name; open the
generated header only for an exact signature you cannot derive.
A component's model is usually more than one file:
include "Commands.fppi"pulls in a fragment. Half ofSvc/keeps commands, events, telemetry and parameters in.fppifiles, so grep--include=*.fpp --include=*.fppiand follow everyincludeline.import Svc.Deframerinside a component pulls in an interface (Fw/Interfaces/,Svc/Interfaces/,Drv/Interfaces/, or the project's). Its ports belong to the component but are declared in the interface file, and interfaces can import other interfaces. Run the port recipes on the interface file too.- Inside a
topology,import CdhCore.Subtopologyis a subtopology, not an interface. $escapes a name that collides with a keyword ($health,$recv); the$is dropped in C++.
1. Grep recipes
FPP keywords are multi-word and event, telemetry, param also
start special-port lines (event port Log) and topology pattern
specifiers (event connections instance events), so anchor on what
follows the name. Patterns are grep -nE over *.fpp and *.fppi.
| Want | Pattern | ||||||||||||||||
| Input ports | `^\s*(async | sync | guarded) input port` | ||||||||||||||
| Output ports | ^\s*output port | ||||||||||||||||
| Commands | `^\s*(async | sync | guarded) command` | ||||||||||||||
| Events | `^\sevent +$?\w+\s(( | \ | severity | $)` | |||||||||||||
| Telemetry | ^\s*telemetry +\$?\w+\s*: | ||||||||||||||||
| Parameters | ^\s*(external )?param +\$?\w+\s*: | ||||||||||||||||
| Special ports | `^\s*((async | sync | guarded) )?(command (recv | reg | resp) | event | text event | telemetry | time get | param (get | set) | product (get | request | send | recv)) port` | ||
| Internal ports | ^\s*internal port | ||||||||||||||||
| Interfaces used | ^\s*import in a component file | ||||||||||||||||
| Everything in a component | `^\s*(async | sync | guarded | output | internal | command | text | time | external | param | product | event | telemetry | import | include | match | state machine)\b` |
The events pattern accepts the event Name \ line-continuation form.
The same keywords in a topology.fpp are pattern specifiers and
instance/connections lines, not declarations.
Port arrays are declared as port name: [N] Type; N is usually a
constant from default/config/AcConstants.fpp (or the project's
override), so follow the name there to get the number.
Across the tree (exclude build-fprime-* directories):
- Who uses a port type:
grep -rlE 'port +\$?\w+ *:.*\bPing\b' --include=*.fpp --include=*.fppi. Insidemodule Svcthe type is written unqualified (Ping, notSvc.Ping), and components that get the port through an interface only showimport <Module>.<Interface>; grep for that too. - Where a symbol is defined:
grep -nE '^locate \w+ Svc\.Ping ' build-fprime-*/locs.fpp(needs a build cache).fpp-locate-defs <file>lists what that file defines, not where a used symbol lives. - Who is wired to an instance: grep the instance name across every
.fppof the deployment and of the subtopologies it imports (Svc/Subtopologies/*/*.fpp, underlib/fprime/in a project). Look insideconnectionsblocks and at the pattern specifiers (command connections instance CdhCore.cmdDisp,event connections instance CdhCore.events,health connections instance CdhCore.$health, ...). A pattern connects every instance in the topology, including the named one itself. Subtopologies themselves carry no pattern specifiers.
2. Name mapping (model → generated C++)
<Comp> is the FPP component name, not the directory
(Svc/CmdDispatcher/ declares active component CommandDispatcher,
so the base is CommandDispatcherComponentBase). <Comp>TesterBase /
<Comp>GTestBase are the unit-test counterparts. Enum constants
upper-case the model name: event OpcodeRegistered is
EVENTID_OPCODEREGISTERED, command CMD_NO_OP is OPCODE_CMD_NO_OP.
Full signatures and semantics:
Autocoded Functions and Component Classes.
| Model | Implementation must define | Implementation may call | Tester side |
input port foo | foo_handler(FwIndexType portNum, ...), returning the port's return type if it has one; async ports may add foo_preMsgHook, and hook ports must add foo_overflowHook(portNum, ...) | invoke_to_foo(portNum, ...), connect_to_foo, isConnected_to_foo; doDispatch() drains an async queue | |
output port bar | bar_out(portNum, ...) (asserts on an unconnected or out-of-range port), isConnected_bar_OutputPort(portNum), getNum_bar_OutputPorts() | from_bar_handler(...) (returns the port's return type), pushFromPortEntry_bar(...), ASSERT_from_bar_SIZE(n), ASSERT_from_bar(idx, ...) | |
serial port s | s_handler(FwIndexType portNum, Fw::LinearBufferBase& buffer) | s_out(portNum, buffer) | from_s_handler(portNum, buffer) |
command CMD | CMD_cmdHandler(FwOpcodeType opCode, U32 cmdSeq, args...); async commands may add CMD_preMsgHook(opCode, cmdSeq) | cmdResponse_out(opCode, cmdSeq, Fw::CmdResponse), enum OPCODE_CMD | sendCmd_CMD(instance, cmdSeq, args...), ASSERT_CMD_RESPONSE_SIZE(n), ASSERT_CMD_RESPONSE(idx, opcode, seq, resp) |
event E (severity warning high) | log_WARNING_HI_E(args...), enum EVENTID_E. Severities spell FATAL, WARNING_HI, WARNING_LO, COMMAND, ACTIVITY_HI, ACTIVITY_LO, DIAGNOSTIC. throttle N adds EVENTID_E_THROTTLE and log_WARNING_HI_E_ThrottleClear() | ASSERT_EVENTS_E_SIZE(n), ASSERT_EVENTS_E(idx, args...) (only for events with arguments), ASSERT_EVENTS_SIZE(n) | |
telemetry T | tlmWrite_T(value, timeTag = ...), enum CHANNELID_T | ASSERT_TLM_T_SIZE(n), ASSERT_TLM_T(idx, value), ASSERT_TLM_SIZE(n) | |
param P | optional parameterUpdated(FwPrmIdType id); external param needs registerExternalParameters(Fw::ParamExternalDelegate*) at init | paramGet_P(Fw::ParamValid& valid), enum PARAMID_P. Each param also autocodes commands P_SET/P_SAVE (OPCODE_P_SET, OPCODE_P_SAVE; P_PRM_SET in the dictionary), numbered before the model's own commands | paramSet_P(value, valid), paramSend_P(instance, cmdSeq), paramSave_P(instance, cmdSeq) |
product container C, record R | dpRecv_C_handler(DpContainer&, Fw::Success::T) only with a product recv port | dpGet_C(size, container), dpRequest_C(size), dpSend(container), container.serializeRecord_R(...) | override productGet_handler(FwDpIdType, FwSizeType, Fw::Buffer&); ASSERT_PRODUCT_GET/REQUEST/SEND(...) |
internal port ip | ip_internalInterfaceHandler(args...); hook adds ip_overflowHook | ip_internalInterfaceInvoke(args...) | |
state machine instance sm of M | <M>_action_<a>(SmId smId, <M>::Signal signal, ...) and <M>_guard_<g>(...), where <M> is the fully qualified machine type with . replaced by _ (FppTest_SmInitial_Basic_action_a; a machine defined inside the component carries the component's name too) | sm_sendSignal_<sig>(...), sm_getState() |
Argument passing: primitives by value, enums/structs/arrays const T&,
ref arguments T&. Command string arguments are
const Fw::CmdStringArg&; event and port strings are
const Fw::StringBase& (sendCmd_* takes const Fw::StringBase&).
FwIndexType portNum is always first. Command handlers must end with
cmdResponse_out.
3. Where autocode lives, and when to read it
- The cache is
build-fprime-automatic-<toolchain>[-ut]/at the project root named insettings.ini(TestDeploymentsProject/forRef). Framework modules land underF-Prime/<module path>/; project and library modules under their path relative to the project root (build-fprime-automatic-native/LedBlinker/Components/Led/).fprime-util generateonly writeslocs.fpp;*Ac.*appear afterfprime-util build(--utforTesterBase/GTestBase). Never edit these files. fprime-util implwrites<Comp>.template.{hpp,cpp};--utwritestest/ut/<Comp>Tester.template.{hpp,cpp}and<Comp>TestMain.template.cpp. Each needs the matching (ut or non-ut) cache, as doesfprime-util fpp-check.- Resolved opcodes, event/channel IDs and enum values are in
<Deployment>TopologyDictionary.json, written by a normal deployment build underbuild-artifacts/;fprime-util fpp-to-dictfrom theTop/directory regenerates it. Use it for GDS and integration-test work rather than computingbase id+ local id by hand. fprime-util generaterefuses to run when the installedfppdoes not matchcmake/required.cmake; build the venv from the framework'srequirements.txt.
4. Codegen gotchas
- Pattern specifiers (
event connections instance X,telemetry connections instance X,command connections instance X) include the instanceXitself; a sink component's own events and telemetry are routed back into it. - Only
deployment topology Xautocodes<X>TopologyAc.*; a baretopologyblock (every subtopology) does not, and the dictionary also needsregister_fprime_deploymentin CMake. A scratchfpp-to-cpprun on a plaintopologycannot check pattern wiring. - Port numbers are compile-time constants: a port array of size
NrejectsportNum >= Nwith an assertion in the generated base class. - A project
config/directory shadows framework.fpp/.hppconfiguration files by basename (AcConstants.fpp,FpConstants.fpp,*Cfg.fpp); check there before trusting the framework default.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

