Leo generated the vendor part with easyeda2kicad (C5120257) -> Drogheda-v6.kicad_sym / .pretty / .3dshapes, now registered in sym-lib-table and fp-lib-table. CROSS-CHECK: the EasyEDA/LCSC symbol independently CONFIRMS the datasheet transcription - pads 1-54 match the u-blox pin assignment function for function, and the 21 Reserved pads are identical. Pads 55-102 are 48 extra GND pads (the ground array under the module), which our symbol was missing; T3a2 adds them stacked on the pin-1 coordinate so one GND label serves all. Symbol is now 102/102 pins, footprint = Drogheda-v6:LCC-LGA-102_L22.0-W17.0_FM660. Block N as wired (verified by rebuilding connectivity from label-on-pin geometry): GNSS_TX U16.16 + U18.43 GNSS_RX U16.17 + U18.42 DOUT_4G U18.26 (RXD2, RTCM in - modem end lands in T4) USART1_RX U16.43 + Rdfu1.1 + U18.27 (TXD2 uplink; K1.1 also on this net per the PCB) GNSS_RESET_N U16.53 (PC12) + U18.49 + R105 10k pull-up to 3V3_GNSS GNSS_TIMEPULSE U16.23 (PA7) + U18.53 GNSS_ANT_DETECT U16.9 (PC1) + U18.4 GNSS_ANT_SHORT_N U16.10 (PC2) + U18.6 GNSS_RTK_STAT U16.11 (PC3) + U18.20 <- hardware answer to are-corrections-being-used 3V3_GNSS = U21.5 + U18.33/34 + C120-C124 + R105; U21 fed from SW_5V (stays MCU-gated) V_BCKP = U18.36 on the UNGATED 3V3 so ephemeris survives a power-cycle 33 no-connects: the 21 reserved pads plus V_USB, USB_DM/DP, ANT_OFF, SDA, SCL, TX_READY, D_SEL (open = UART mode), SAFEBOOT_N, EXTINT, GEOFENCE_STAT and the LDO NC/NR pin. T3c fixes two coordinates the generators emitted as 3.552713679e-15 (i.e. zero); KiCad is not guaranteed to accept exponent notation. See the script header for the lesson: a first attempt used a bare numeric regex over the whole file and corrupted 264 UUIDs, because segments such as 895e-4153 parse as scientific notation. Reverted from backup and redone scoped to (at ...) forms only, with a UUID-integrity guard. Verified 2298 UUIDs, 0 malformed, 0 exponent coordinates. STILL OPEN: the PCB has no U18/U21/passive footprints yet - that is a KiCad Update-PCB-from-Schematic. And confirm the -04B datasheet pin assignment on paper. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YJ4eAB6zjQT49RVwpgfKdt |
||
|---|---|---|
| _brand | ||
| .claude/skills/project-drogheda | ||
| 00-Project-Management | ||
| 01-Requirements | ||
| 02-Architecture-Software | ||
| 03-Architecture-Hardware | ||
| 04-Source-Code | ||
| 05-Analytics-Reports | ||
| 06-Testing-Validation | ||
| 99-Archive | ||
| Marketing | ||
| mcpmarket-me | ||
| scripts | ||
| .gitignore | ||
| .gitmodules | ||
| CLAUDE.md | ||
| mcpmarket-plugin-me.zip | ||
| README.md | ||
Project Drogheda (GPS RTK)
Helgen Technologies' HBOX RTK GPS tracker fleet for Hutchison Ports heavy
equipment (ICAVE / TIMSA / EIT / LCT) — centimetre-class position over 4G, streamed to the
Helgen backend (retranslator → Wialon/Traccar → VERONICA), built to survive a hot, salty,
high-vibration port environment.
New here? Read
00-Project-Management/Engineering-Handover.mdfirst. It is the deep context: product, failure analysis, fixes, repo map, open items, glossary. This README is the 2-minute orientation;CLAUDE.mdis the terse machine index.
Where we are (2026-06-20 · updated 2026-07-02)
2026-07-02: backend deployed + stable; thermal chamber run done; 3-board protoboard campaign in flight (units to ICAVE 7-jul). Watchdog v3 PROD schematic is complete (ERC 0) — LTC4040 battery-backup sized to the 12 Ah pack, fail-safe Modo-B relay bypass — and the PCB is now a 120×100 carrier board: Blackpill + simpleRTK2B Pro (UNO-shield sockets) + 4G NTRIP Master (on-board XBee socket) all on female headers. Layout in placement review; fab gate = proto bench validation. Canonical:
03-Architecture-Hardware/watchdog-electrical-design-state.md.
We deployed a first batch of HBOX trackers on ICAVE machines in Veracruz. They worked "ish," then failed. We are mid-crisis, hardening for scale — target 30 units by August. The failure is three independent fronts, fixed in parallel:
- Backend (confirmed in code) —
retranslator.pyhead-of-line blocks the whole fleet on slow upstream, and an anti-jump filter can permanently black-hole a healthy unit. - Thermal — an ASA case (UV-stable, ~95–100 °C — adequate) sealed in a sealed IP67 cabinet that also holds the heat-generating Mean Well PSU, in full sun → nested heat trap for the battery / boost / modem (not the case).
- Prototype hardware — Dupont + hand-wiring + 18650/PowerBoost; fragile under vibration.
Units: all pulled — 4 in hand (3 dead, 1 working-ish) in Veracruz; team in Querétaro → remote debug. Field firmware is v1 (no thermal log).
Free triage: a unit ONLINE in htracker but OFFLINE in Wialon is a backend victim, not dead hardware. Check that before condemning a radio.
The product in one breath
Rover (HBOX) on the machine + Base Station (Ardusimple AS-PRO-CORS, 110/230 V) publishing RTCM3 corrections over NTRIP. The rover gets corrections over the 4G modem, not the GNSS → recover a dead link by power-cycling the 4G stack, never a GNSS reset. HBOX core: simpleRTK2B Pro (ZED-F9P) · 4G NTRIP Master · STM32F411 watchdog · Mean Well SD-15B-05 (24→5 V) · PowerBoost + 18650 · GX16-5 to the cabinet. 24 V is the production variant.
Invariants (never violate)
- Power-off is the safe state. 2. Never vanish, never loop. 3. Corrections ride the 4G modem, not the GNSS. 4. No material that softens below ~80 °C (PLA-class) in the thermal path — the ASA enclosure complies; design to measured cabinet temperature. 5. Backend forwards without head-of-line blocking; anti-jump never locks out a healthy unit. 6. No secrets in the repo (the committed MSSQL password is a live violation to rotate).
Repo layout
00-Project-Management (plan, ethos, financials, handover, Drive tooling) ·
01-Requirements (SRS, product spec, tracker) · 02-Architecture-Software (backend review) ·
03-Architecture-Hardware (cabinet/HBOX, BOM, PCB brief, watchdog, manual) ·
04-Source-Code (firmware/ · htracker/ · notifications/) ·
05-Analytics-Reports (SQL views — placeholder) · 06-Testing-Validation (RCA, diagnostics) ·
Marketing (datasheet, brochure) · _brand (LaTeX style) · 99-Archive (raw inputs).
Quick start
# Branded docs (XeLaTeX; League Spartan + MADE Evolve Sans):
cd 01-Requirements/HBOX-Ficha-Tecnica && latexmk -xelatex main.tex
# Firmware (own repo 'hbox-firmware', at 04-Source-Code/firmware):
# open blackpillrtkcode_v2/blackpillrtkcode_v2.ino in the STM32duino toolchain.
# ⚠ Bench-test before any field flash — the sandbox cannot build STM32.
# Backend: 04-Source-Code/htracker (ssh://git.helgen.dev:6611/htracker, feature/test500unidades)
Storage model (one home per artifact)
This repo = working source of truth (editable .md/.tex, code). Google Drive
Drogheda (GPS RTK) = finalized exports (branded PDFs, native Docs/Sheets). Second Brain
vault = distilled decisions/lessons. Author in repo → export final to Drive → distill to
vault. Drive upload how-to + mapping: 00-Project-Management/Drive-Upload/README.md. Never
change Drive sharing — that's Leo's call.
Go deeper
- Deep context / onboarding →
00-Project-Management/Engineering-Handover.md - Current priorities →
00-Project-Management/PLAN.md - Machine index →
CLAUDE.md - Failure analysis →
06-Testing-Validation/RCA-2026-06-field-failures.md