CUMBRIACQ — AI HAM RADIO PROMPT PACK Source-checked editorial guide: 17 November 2026 https://cumbriacq.com/ai-ham-radio/ https://cumbriacq.com/ai-radio-programming/ https://cumbriacq.com/ai-ham-radio-tools/ These are templates, not tested radio configurations, legal advice, firmware or a codeplug. Replace bracketed placeholders with verified information. Do not include passwords, API tokens, private access codes or other people's personal information. Keep the radio disconnected during offline review. 1. EXPLAIN ONE MANUAL SECTION Act as a documentation assistant, not a radio controller. Country of operation: [country]. Radio: [exact model, hardware revision if known, firmware]. Using only the official manual excerpt below, explain [one setting/task]. Separate what the source states from your interpretation. Cite section names/page numbers that actually appear in the source. Identify missing information and stop rather than invent menu items, frequencies or permissions. Do not suggest a transmission, firmware upload or hardware modification. SOURCE: [relevant official excerpt] 2. REVIEW A CHIRP FIELD MAPPING Review, do not program. I will supply the exact CSV header exported by my CHIRP version, a verified source table labelled RADIO RX and RADIO TX with units/dates, and my exact radio, firmware, software and country. First return a field-mapping table and unresolved items. Do not generate a candidate CSV until I approve the mapping. Preserve values/identifiers exactly. Do not infer offsets, tones, modes, power, band limits or transmit permission. Blanks/zeroes are not safe substitutes for unknowns. Flag duplicate locations and target-specific settings not represented by the CSV. Do not access a radio, serial port, live-mode image or upload tool. 3. AUDIT A DMR PROGRAMMING PLAN Audit this as an offline reviewer. Do not modify a binary codeplug. Do not invent talkgroups, IDs, colour codes, time slots, routing or frequencies. Check referenced contacts, channels and zones exist. Separate definite structural errors from questions for the keeper/network operator. Output: item | old value | proposed value | evidence | unresolved question. Do not claim CPS/radio compatibility without supplied current documentation. 4. REVIEW A SMALL FIRMWARE PATCH Official repository and pinned commit: [verified URL/commit]. Exact supported hardware revision: [target]. Proposed change: [one non-RF behaviour]. First identify relevant code and existing tests; explain assumptions before proposing a minimal diff. Do not change PTT, band limits, calibration, power control, EEPROM layout, bootloader or safety checks. Do not invent flash addresses, recovery commands or hardware support. Keep build/test work offline. Do not invoke a flasher. List remaining human review and bench-verification requirements. 5. PLAN A READ-ONLY LOG REPORT Help write a local report against a COPY of my log; do not upload or modify the original. Input format/version: [documented format]. Desired statistic: [one defined measure]. First explain parsing assumptions, units, UTC/local-time handling, duplicates, portable suffixes and missing fields. Use a proper parser where required. Keep unknown/error records visible. Test known small examples and reconcile counts with the original export. Do not invent QSOs, callsigns, signal reports, countries/entities or propagation conclusions. 6. REASON ABOUT A FAULT WITHOUT GUESSING Radio/software and exact versions: [details]. Observed symptoms and actual measurements: [facts, units, test conditions]. Relevant manual excerpt: [source]. Separate evidence from hypotheses. Rank plausible causes and propose one low-risk, non-transmitting observation to distinguish them. Explain what each outcome would establish and what it would not. Do not invent measurements, replace components or provide mains/high-voltage/tower work instructions. STOP CHECKLIST - Exact hardware/firmware support unknown: stop. - Original backups or a realistic recovery route missing: stop. - Sources conflict or a required field is missing: resolve before writing. - A proposed action changes scope, transmits or flashes unexpectedly: stop. - A CSV opens or code compiles: format/build evidence only, not RF verification. - Another chatbot agrees: not independent proof. - Always check the regulator and operating privileges at the station's location.