I’ll inspect the project’s part metadata, look for any missing official datasheet links, update the Datasheet URL where needed, then compare symbol/footprint/pins against the datasheet and summarize mismatches.
Found the official u-blox datasheet URL on u-blox content hosting; I’m checking whether the current part project can read it directly before comparing pins/footprint.
Description: High-accuracy timing GNSS module, professional grade
Package: LGA module, 17.0 x 22.0 x 2.4 mm typical
Pin/pad count: 102 pads in the project; datasheet lists functional pins 1-54 and identifies the remaining central pads as ground pads
Supply: VCC 2.7-3.6 V, typical 3.0 V
V_BCKP: 1.65-3.6 V
V_USB: max 3.6 V
Operating temperature: -40 to +85 °C
Typical current: 85-90 mA VCC, 130 mA peak acquisition
Cross-check result:
Symbol pin names/numbers match the datasheet for the visible functional pins reviewed.
Footprint has 102 pads, consistent with the project context and the ZED-F9T LGA footprint structure.
No open part-review or missing-footprint issues were reported by checks.
Minor metadata gap remains: the project did not previously expose manufacturer/package/description as formal part properties; the datasheet URL is now present, but the property system reported it as a non-standard project-level property rather than a standard part-level field.