diaggpsd 2026.11.8__tar.gz

diaggpsd-2026.11.8/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "{}"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright {yyyy} {name of copyright owner}
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

diaggpsd-2026.11.8/NOTICE

@@ -0,0 +1,33 @@
+diaggpsd: live GNSS from a cellular modem's DIAG stream to gpsd clients + RINEX
+Copyright 2026 Luke Jenkins
+
+This product includes software developed by Luke Jenkins
+(https://github.com/lukejenkins).
+
+Licensed under the Apache License, Version 2.0. See the LICENSE file
+for the full license text.
+
+------------------------------------------------------------------------
+Acknowledgements
+------------------------------------------------------------------------
+
+Reverse-engineering and documentation of DIAG GNSS log records
+was pioneered by projects including openpilot's qcomgpsd, QCSuper, and
+SCAT. diaggpsd does not incorporate their code: the GNSS log-record
+struct definitions it relies on live in the separate diaggrok library and
+were re-derived clean-room there. diaggpsd itself is a first-party
+orchestration layer, but it stands on the reverse-engineering those
+projects contributed to the community.
+
+diaggpsd feeds gpsd clients by speaking the gpsd JSON protocol; it is not
+derived from, and does not replace, the gpsd daemon.
+
+------------------------------------------------------------------------
+Dependencies
+------------------------------------------------------------------------
+
+No third-party code is incorporated into diaggpsd itself. At install time
+it depends on two sibling libraries — diaggrok (DIAG GNSS parsers) and
+diagmunge (DIAG transport) — and, for the live AT-port path, on the
+optional `serial` extra (pyserial). Those are distributed separately
+under their own licenses and are not included in this repository.

diaggpsd-2026.11.8/PKG-INFO

@@ -0,0 +1,203 @@
+Metadata-Version: 2.4
+Name: diaggpsd
+Version: 2026.11.8
+Summary: Live GNSS from a Qualcomm modem's DIAG stream — serves gpsd clients and writes RINEX
+Author: Luke Jenkins
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/lukejenkins/diaggpsd
+Project-URL: Source, https://github.com/lukejenkins/diaggpsd
+Project-URL: Changelog, https://github.com/lukejenkins/diaggpsd/releases
+Keywords: diag,modem,cellular,baseband,lte,5g
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: Science/Research
+Classifier: Intended Audience :: Telecommunications Industry
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Communications
+Classifier: Topic :: System :: Hardware
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: diaggrok>=2026.11.8
+Requires-Dist: diagmunge>=2026.11.8
+Provides-Extra: serial
+Requires-Dist: pyserial; extra == "serial"
+Dynamic: license-file
+
+# diaggpsd
+
+Live GNSS from a Qualcomm modem's **DIAG** stream — served to gpsd clients and
+written to RINEX. diaggpsd subscribes to a Qualcomm modem's GNSS DIAG log
+records, decodes them, and makes the fixes and raw measurements available three
+ways:
+
+- **gpsd clients** — a gpsd-compatible JSON server on TCP 2947, so `gpspipe`,
+  `cgps`, `xgps`, `gpsmon`, JOSM, and anything built on `libgps` just work.
+- **Raw JSON** — one packet per line on stdout or a plain TCP port, for logging
+  and custom tooling without the gpsd protocol overhead.
+- **RINEX** — observation/navigation files for post-processing pipelines.
+
+diaggpsd *feeds* gpsd clients by speaking the gpsd protocol; it is not the gpsd
+daemon and does not replace it. It reads the modem directly over DIAG, so it
+works where no kernel GPS driver or NMEA port is exposed.
+
+## Layout
+
+diaggpsd is one Python package, `diaggpsd`, under `src/diaggpsd/`. Its
+console commands (`diaggpsd`, `diaggpsd-diag-setup`, `diaggpsd-dlf-to-jsonl`,
+`diaggpsd-dump-pos-report`, `diaggpsd-gnss-compare`) are the supported way to
+run it; `python -m diaggpsd` starts the daemon too. The modules:
+
+| Module | Role |
+|--------|------|
+| `diaggpsd.py` | the live daemon — argument parsing, DIAG subscription, main loop, gpsd/raw output |
+| `gnss_packets.py` | thin re-export shim over the `diaggrok` GNSS parsers |
+| `at.py` | AT-command interface for GNSS engine setup (Quectel-oriented) |
+| `gpsd_server.py` | the gpsd JSON protocol server (TCP 2947) |
+| `diag_setup.py` | DIAG log-mask setup helper |
+| `dlf_to_jsonl.py` | offline: decode a DIAG capture to JSONL |
+| `dump_pos_report.py` | offline: dump position reports from a live/captured stream |
+| `gnss_compare.py` / `gnss_compare_ref_filter.py` | compare decoded fixes against a reference track |
+| `rinex_writer.py` | RINEX observation/navigation output |
+| `modem_profiles.py` | per-chipset NV/AT setup profiles |
+
+## Dependencies
+
+diaggpsd is first-party Python. At install time it pulls two sibling libraries
+that hold the reverse-engineered pieces:
+
+- **[diaggrok](https://github.com/lukejenkins/diaggrok)** — the DIAG GNSS
+  log-record parsers (imported through `gnss_packets.py`).
+- **[diagmunge](https://github.com/lukejenkins/diagmunge)** — the DIAG transport
+  core (`DiagClient`) and replay.
+
+The live AT-port path additionally needs **pyserial**, installed via the
+optional `serial` extra. DIAG capture, replay, decode, RINEX, and the gpsd
+server are all pyserial-free.
+
+From [PyPI](https://pypi.org/project/diaggpsd/):
+
+```bash
+pip install diaggpsd             # daemon + gpsd server + offline tooling
+pip install "diaggpsd[serial]"   # + the live AT-port path (pyserial)
+```
+
+diaggrok and diagmunge come from PyPI with it. Each PyPI version is the same
+code as the GitHub tag of the same number (`diaggpsd==2026.11.8` is tag
+`v2026.11.8`). From a clone, `pip install .` works the same way.
+
+Requires Python 3.11+.
+
+## Quick start
+
+Two steps: `diaggpsd-diag-setup` prepares the modem once (NV items, the GNSS
+session, AT commands), then `diaggpsd` streams. `diaggpsd` itself never sends AT
+commands, so the AT options (`--at-port`, `--no-at`, `--cold-start`) belong to
+the setup step.
+
+### USB-connected modem
+
+```bash
+# One-time setup: enable GNSS logging and start the engine over AT.
+diaggpsd-diag-setup --chipset sdx55 --diag-port /dev/ttyUSB0 --at-port /dev/ttyUSB2
+
+# Stream to gpsd clients.
+diaggpsd --diag-port /dev/ttyUSB0 --debug
+
+# In another terminal:
+gpspipe -w 127.0.0.1
+```
+
+`diaggpsd-diag-setup --list-profiles` lists the chipset profiles. Add
+`--cold-start` to delete cached assistance, or `--no-at` when the GNSS engine is
+already running or the AT path is unavailable. On QuecOpen builds the host-side
+AT port is bridged to an SMD device node by an AP-side service; if that bridge
+is stopped, AT commands can fail silently, so `--no-at` is the robust choice
+there.
+
+### Network-attached modem
+
+A modem that relays its DIAG stream over the network is read without a serial
+port. In the two passive modes the device sets the log mask and `diaggpsd`
+never writes one.
+
+```bash
+# The device pushes a DGE1-framed UDP stream (diagbarf):
+diaggpsd --diag-port udp-listen:0.0.0.0:12399 --debug
+
+# The device runs diag_socket_log and connects to this host:
+diaggpsd --diag-port tcp --debug
+#   on the modem: diag_socket_log -a <host_ip> -p 2500
+```
+
+## Transport modes
+
+| Mode | Invocation | Who sets the log mask |
+|------|------------|-----------------------|
+| USB / serial (default) | `--diag-port /dev/ttyUSB0` | diaggpsd |
+| TCP `diag_socket_log` | `--diag-port tcp` or `tcp:0.0.0.0:2500` | diaggpsd |
+| UDP, DGE1 framing (diagbarf) | `--diag-port udp-listen` or `udp-listen:0.0.0.0:12399` | the device |
+| UDP, QMDL2 chunks (`diag_udp_fwd`) | `--diag-port udp` or `udp:0.0.0.0:2500` | the device |
+
+When diaggpsd sets the log mask, it clears the mask again on exit with one
+LOG_CONFIG DISABLE, draining queued frames for up to 10 s while it waits for
+the ack. That also happens when the subscribe itself fails, for example when
+a slow `diag_socket_log` tunnel backs up until a mask ack never arrives (exit
+status 1). If no ack comes, the log says so; power-cycle the modem
+(`AT+CFUN=1,1`) and send a zero log mask before the next run.
+
+## Output modes
+
+- **stdout JSON** (default) — one parsed packet per line
+  (`PositionReport`, `GpsMeasurementReport`, `GlonassMeasurementReport`,
+  `OemdreMeasurementReport`, `OemdreSvPolyReport`). Suppress with `--no-stdout`.
+- **Raw TCP** — `--raw-port 5000` broadcasts the JSON lines to connected TCP
+  clients.
+- **gpsd server** (TCP 2947) — the standard gpsd JSON protocol. Disable with
+  `--no-gpsd`, move with `--gpsd-port PORT`.
+
+## Offline decoding: input formats for `dlf_to_jsonl`
+
+How a DIAG capture was produced determines how to decode it. Two on-disk formats
+both commonly carry the `.dlf` extension but are **not** interchangeable:
+
+| Source | On-disk format | Invocation |
+|--------|----------------|------------|
+| QCSuper (`--dlf`) | DLF records (per-record length/type header) | `dlf_to_jsonl capture.dlf out.jsonl` |
+| raw HDLC dump | 0x7E-delimited HDLC byte stream (no DLF envelope) | `dlf_to_jsonl --format bin --verify-crc capture.dlf out.jsonl` |
+
+Using DLF mode on a raw-HDLC file yields a near-zero parse rate (the 0x7E
+delimiters do not form a valid DLF record header). DLF mode on QCSuper output is
+correct and needs no `--verify-crc` (QCSuper validates CRCs at capture time).
+
+## GPS lock notes
+
+After start, the modem needs time to acquire satellites: typically 10–30 s
+outdoors with fresh XTRA assistance, 1–10 min on a cold start with clear sky.
+The first `PositionReport` with `pos_source=2` (Kalman fix) marks a usable
+position; the gpsd server begins pushing TPV at that point.
+
+## gpsd protocol subset
+
+`VERSION` (on connect), `WATCH` (subscribe/unsubscribe), `TPV` (from
+`PositionReport`), `SKY` (from GPS/GLONASS measurement reports), and minimal
+`DEVICES` / `POLL` stubs for client compatibility. `TPV.mode`: 1 = no fix,
+2 = 2D, 3 = 3D (Kalman).
+
+## Acknowledgements
+
+Reverse-engineering of Qualcomm DIAG GNSS log records was pioneered by projects
+including openpilot's qcomgpsd, QCSuper, and SCAT. diaggpsd relies on struct
+definitions re-derived clean-room in the `diaggrok` library and stands on the
+documentation those projects contributed to the community.
+
+## License
+
+Apache-2.0. See [LICENSE](LICENSE) and [NOTICE](NOTICE).

diaggpsd-2026.11.8/README.md

@@ -0,0 +1,170 @@
+# diaggpsd
+
+Live GNSS from a Qualcomm modem's **DIAG** stream — served to gpsd clients and
+written to RINEX. diaggpsd subscribes to a Qualcomm modem's GNSS DIAG log
+records, decodes them, and makes the fixes and raw measurements available three
+ways:
+
+- **gpsd clients** — a gpsd-compatible JSON server on TCP 2947, so `gpspipe`,
+  `cgps`, `xgps`, `gpsmon`, JOSM, and anything built on `libgps` just work.
+- **Raw JSON** — one packet per line on stdout or a plain TCP port, for logging
+  and custom tooling without the gpsd protocol overhead.
+- **RINEX** — observation/navigation files for post-processing pipelines.
+
+diaggpsd *feeds* gpsd clients by speaking the gpsd protocol; it is not the gpsd
+daemon and does not replace it. It reads the modem directly over DIAG, so it
+works where no kernel GPS driver or NMEA port is exposed.
+
+## Layout
+
+diaggpsd is one Python package, `diaggpsd`, under `src/diaggpsd/`. Its
+console commands (`diaggpsd`, `diaggpsd-diag-setup`, `diaggpsd-dlf-to-jsonl`,
+`diaggpsd-dump-pos-report`, `diaggpsd-gnss-compare`) are the supported way to
+run it; `python -m diaggpsd` starts the daemon too. The modules:
+
+| Module | Role |
+|--------|------|
+| `diaggpsd.py` | the live daemon — argument parsing, DIAG subscription, main loop, gpsd/raw output |
+| `gnss_packets.py` | thin re-export shim over the `diaggrok` GNSS parsers |
+| `at.py` | AT-command interface for GNSS engine setup (Quectel-oriented) |
+| `gpsd_server.py` | the gpsd JSON protocol server (TCP 2947) |
+| `diag_setup.py` | DIAG log-mask setup helper |
+| `dlf_to_jsonl.py` | offline: decode a DIAG capture to JSONL |
+| `dump_pos_report.py` | offline: dump position reports from a live/captured stream |
+| `gnss_compare.py` / `gnss_compare_ref_filter.py` | compare decoded fixes against a reference track |
+| `rinex_writer.py` | RINEX observation/navigation output |
+| `modem_profiles.py` | per-chipset NV/AT setup profiles |
+
+## Dependencies
+
+diaggpsd is first-party Python. At install time it pulls two sibling libraries
+that hold the reverse-engineered pieces:
+
+- **[diaggrok](https://github.com/lukejenkins/diaggrok)** — the DIAG GNSS
+  log-record parsers (imported through `gnss_packets.py`).
+- **[diagmunge](https://github.com/lukejenkins/diagmunge)** — the DIAG transport
+  core (`DiagClient`) and replay.
+
+The live AT-port path additionally needs **pyserial**, installed via the
+optional `serial` extra. DIAG capture, replay, decode, RINEX, and the gpsd
+server are all pyserial-free.
+
+From [PyPI](https://pypi.org/project/diaggpsd/):
+
+```bash
+pip install diaggpsd             # daemon + gpsd server + offline tooling
+pip install "diaggpsd[serial]"   # + the live AT-port path (pyserial)
+```
+
+diaggrok and diagmunge come from PyPI with it. Each PyPI version is the same
+code as the GitHub tag of the same number (`diaggpsd==2026.11.8` is tag
+`v2026.11.8`). From a clone, `pip install .` works the same way.
+
+Requires Python 3.11+.
+
+## Quick start
+
+Two steps: `diaggpsd-diag-setup` prepares the modem once (NV items, the GNSS
+session, AT commands), then `diaggpsd` streams. `diaggpsd` itself never sends AT
+commands, so the AT options (`--at-port`, `--no-at`, `--cold-start`) belong to
+the setup step.
+
+### USB-connected modem
+
+```bash
+# One-time setup: enable GNSS logging and start the engine over AT.
+diaggpsd-diag-setup --chipset sdx55 --diag-port /dev/ttyUSB0 --at-port /dev/ttyUSB2
+
+# Stream to gpsd clients.
+diaggpsd --diag-port /dev/ttyUSB0 --debug
+
+# In another terminal:
+gpspipe -w 127.0.0.1
+```
+
+`diaggpsd-diag-setup --list-profiles` lists the chipset profiles. Add
+`--cold-start` to delete cached assistance, or `--no-at` when the GNSS engine is
+already running or the AT path is unavailable. On QuecOpen builds the host-side
+AT port is bridged to an SMD device node by an AP-side service; if that bridge
+is stopped, AT commands can fail silently, so `--no-at` is the robust choice
+there.
+
+### Network-attached modem
+
+A modem that relays its DIAG stream over the network is read without a serial
+port. In the two passive modes the device sets the log mask and `diaggpsd`
+never writes one.
+
+```bash
+# The device pushes a DGE1-framed UDP stream (diagbarf):
+diaggpsd --diag-port udp-listen:0.0.0.0:12399 --debug
+
+# The device runs diag_socket_log and connects to this host:
+diaggpsd --diag-port tcp --debug
+#   on the modem: diag_socket_log -a <host_ip> -p 2500
+```
+
+## Transport modes
+
+| Mode | Invocation | Who sets the log mask |
+|------|------------|-----------------------|
+| USB / serial (default) | `--diag-port /dev/ttyUSB0` | diaggpsd |
+| TCP `diag_socket_log` | `--diag-port tcp` or `tcp:0.0.0.0:2500` | diaggpsd |
+| UDP, DGE1 framing (diagbarf) | `--diag-port udp-listen` or `udp-listen:0.0.0.0:12399` | the device |
+| UDP, QMDL2 chunks (`diag_udp_fwd`) | `--diag-port udp` or `udp:0.0.0.0:2500` | the device |
+
+When diaggpsd sets the log mask, it clears the mask again on exit with one
+LOG_CONFIG DISABLE, draining queued frames for up to 10 s while it waits for
+the ack. That also happens when the subscribe itself fails, for example when
+a slow `diag_socket_log` tunnel backs up until a mask ack never arrives (exit
+status 1). If no ack comes, the log says so; power-cycle the modem
+(`AT+CFUN=1,1`) and send a zero log mask before the next run.
+
+## Output modes
+
+- **stdout JSON** (default) — one parsed packet per line
+  (`PositionReport`, `GpsMeasurementReport`, `GlonassMeasurementReport`,
+  `OemdreMeasurementReport`, `OemdreSvPolyReport`). Suppress with `--no-stdout`.
+- **Raw TCP** — `--raw-port 5000` broadcasts the JSON lines to connected TCP
+  clients.
+- **gpsd server** (TCP 2947) — the standard gpsd JSON protocol. Disable with
+  `--no-gpsd`, move with `--gpsd-port PORT`.
+
+## Offline decoding: input formats for `dlf_to_jsonl`
+
+How a DIAG capture was produced determines how to decode it. Two on-disk formats
+both commonly carry the `.dlf` extension but are **not** interchangeable:
+
+| Source | On-disk format | Invocation |
+|--------|----------------|------------|
+| QCSuper (`--dlf`) | DLF records (per-record length/type header) | `dlf_to_jsonl capture.dlf out.jsonl` |
+| raw HDLC dump | 0x7E-delimited HDLC byte stream (no DLF envelope) | `dlf_to_jsonl --format bin --verify-crc capture.dlf out.jsonl` |
+
+Using DLF mode on a raw-HDLC file yields a near-zero parse rate (the 0x7E
+delimiters do not form a valid DLF record header). DLF mode on QCSuper output is
+correct and needs no `--verify-crc` (QCSuper validates CRCs at capture time).
+
+## GPS lock notes
+
+After start, the modem needs time to acquire satellites: typically 10–30 s
+outdoors with fresh XTRA assistance, 1–10 min on a cold start with clear sky.
+The first `PositionReport` with `pos_source=2` (Kalman fix) marks a usable
+position; the gpsd server begins pushing TPV at that point.
+
+## gpsd protocol subset
+
+`VERSION` (on connect), `WATCH` (subscribe/unsubscribe), `TPV` (from
+`PositionReport`), `SKY` (from GPS/GLONASS measurement reports), and minimal
+`DEVICES` / `POLL` stubs for client compatibility. `TPV.mode`: 1 = no fix,
+2 = 2D, 3 = 3D (Kalman).
+
+## Acknowledgements
+
+Reverse-engineering of Qualcomm DIAG GNSS log records was pioneered by projects
+including openpilot's qcomgpsd, QCSuper, and SCAT. diaggpsd relies on struct
+definitions re-derived clean-room in the `diaggrok` library and stands on the
+documentation those projects contributed to the community.
+
+## License
+
+Apache-2.0. See [LICENSE](LICENSE) and [NOTICE](NOTICE).

diaggpsd-2026.11.8/pyproject.toml

@@ -0,0 +1,71 @@
+[project]
+name = "diaggpsd"
+version = "2026.11.8"
+description = "Live GNSS from a Qualcomm modem's DIAG stream — serves gpsd clients and writes RINEX"
+license = "Apache-2.0"
+requires-python = ">=3.11"
+readme = "README.md"
+authors = [{ name = "Luke Jenkins" }]
+keywords = ["diag", "modem", "cellular", "baseband", "lte", "5g"]
+classifiers = [
+    "Development Status :: 4 - Beta",
+    "Intended Audience :: Developers",
+    "Intended Audience :: Science/Research",
+    "Intended Audience :: Telecommunications Industry",
+    "Operating System :: OS Independent",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3 :: Only",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Programming Language :: Python :: 3.14",
+    "Topic :: Communications",
+    "Topic :: System :: Hardware",
+]
+# Hard, import-time dependencies — both inward edges to already-public siblings:
+#   - diagmunge: the DIAG transport core (DiagClient + DIAG_LOG_F), imported at
+#     module scope in diaggpsd.py / diag_setup.py / dump_pos_report.py and via
+#     diagmunge.munge.replay in dlf_to_jsonl.py.
+#   - diaggrok:  the GNSS log-record parsers, imported at module scope through
+#     the gnss_packets.py re-export shim.
+# Edge direction is inward-only: diaggpsd -> {diagmunge, diaggrok}. Never the
+# reverse. Bare PyPI names, each floored at the sibling release this package's
+# full suite was verified against in an isolated venv; PyPI
+# rejects direct-URL deps. Release order: diaggrok and diagmunge must be on
+# PyPI before this package is uploaded.
+dependencies = [
+    "diaggrok>=2026.11.8",
+    "diagmunge>=2026.11.8",
+]
+
+[project.optional-dependencies]
+# The live AT-port path (at.py) imports pyserial lazily, inside the serial
+# adapter constructor — only talking to a real modem's AT port needs it. DIAG
+# capture, replay, decode, RINEX, and the gpsd server are all pyserial-free.
+# pyserial IS on PyPI, so it stays a bare name.
+serial = ["pyserial"]
+
+[project.scripts]
+# The live daemon: DIAG -> gpsd JSON server (+ optional RINEX).
+diaggpsd = "diaggpsd.diaggpsd:main"
+# Offline tooling shipped alongside the daemon.
+diaggpsd-diag-setup = "diaggpsd.diag_setup:main"
+diaggpsd-dlf-to-jsonl = "diaggpsd.dlf_to_jsonl:main"
+diaggpsd-dump-pos-report = "diaggpsd.dump_pos_report:main"
+diaggpsd-gnss-compare = "diaggpsd.gnss_compare:main"
+
+[project.urls]
+Homepage = "https://github.com/lukejenkins/diaggpsd"
+Source = "https://github.com/lukejenkins/diaggpsd"
+Changelog = "https://github.com/lukejenkins/diaggpsd/releases"
+
+[build-system]
+requires = ["setuptools>=77.0"]
+build-backend = "setuptools.build_meta"
+
+# The modules live flat in the source tree beside each other; the public carve
+# packages them under src/diaggpsd/ so a pip install adds one top-level name
+# (`diaggpsd`), not twelve generic ones like `at` and `nmea`. `gnss_packets`
+# is a thin re-export shim over the diaggrok parsers.
+[tool.setuptools.packages.find]
+where = ["src"]