Skip to content

arf-subghz-full.md

Latest commit

 

History

History
60 lines (50 loc) · 3.05 KB

arf-subghz-full.md

File metadata and controls

60 lines (50 loc) · 3.05 KB
Raw

ARF Sub-GHz Full

ARF Sub-GHz Full is a lightweight external launcher. It provides one entry point for the stable core Sub-GHz app and isolated ARF tools without loading all their code into the same process.

The Desktop Sub-GHz entry opens this hub. Its Standard Sub-GHz item then launches the core firmware Sub-GHz app, so standard receive/transmit workflows remain one click inside the Tumoflip hub. The Desktop ARF Tools entry opens Module One Cockpit; the ARF Tools folder remains available from Apps, where the Full launcher, ARF Frequency Analyzer, Sub-GHz RAW Edit, and KeeLoq Keystore Decryptor are visible. Garage Door Remote is visible as a separate ProtoPirate-derived garage/gate tool. The RollJam entry inside ARF Sub-GHz Full opens the classic RollJam app packaged as a child module instead of exposing a second visible ARF Tools app. The Shield Receiver source remains in-tree as applications_user/rolljam_standalone, but it is not routed as the user-facing RollJam entry. The remaining child FAPs are stored in /ext/apps_data/arf_subghz_full/modules.

Included workflows

  • decoded and RAW receive through the core Sub-GHz app;
  • saved-signal browsing and transmit through the core Sub-GHz app;
  • manual signal generators through the core Sub-GHz app;
  • frequency analyzer through a dedicated visible FAP;
  • RAW .sub trimming and cleanup through Sub-GHz RAW Edit;
  • KeeLoq keystore decrypt/export through KeeLoq Keystore Decryptor;
  • garage/gate capture and emulate workflows through Garage Door Remote;
  • classic RollJam app through the RollJam child entry;
  • radio and external CC1101 settings through the core Sub-GHz app;
  • receiver settings and live Protocol Pack switching;
  • Protocol Pack Inspector;
  • RPC and file-launch handling.

RAM model

Full queues the selected child in Loader and exits. This gives each utility the available application heap instead of linking all Sub-GHz scenes and ARF workers into one FAP. A full standard Sub-GHz external backend exceeded available heap on hardware, so standard workflows stay in the core app. PSA, Counter, Car Emulate, ProtoPirate, classic RollJam, and Bruteforcer stay in separate child FAPs. The Shield Receiver source is kept in-tree for reference and broker experiments, but is excluded from reproducible updater packages.

Shared Sub-GHz helpers

ARF child apps may reuse pure helpers from lib/subghz when they do not import firmware-only state or radio lifecycle assumptions. The combined hopper uses the shared subghz_hopper_plan_next() helper only to calculate the next frequency/preset indexes; ARF still owns its RSSI timeout, preset reload, and child-FAP profile behavior.

Validation boundary

The system Sub-GHz application stays in firmware as the primary receiver and transmitter surface. It should not be replaced by an external FAP unless the Sub-GHz app is first split into a smaller service/client architecture that can be validated without heap exhaustion or navigation regressions. The repository tracks this as a deliberate architecture boundary in Sub-GHz Architecture.