Skip to content

Propose timestamp broadcasting - #241

Open
bruno-f-cruz wants to merge 4 commits into
mainfrom
proposal/timestamp-broadcasting
Open

bruno-f-cruz wants to merge 4 commits into
mainfrom
proposal/timestamp-broadcasting

Conversation

@bruno-f-cruz

@bruno-f-cruz bruno-f-cruz commented Oct 11, 2026 •

Copy link
Copy Markdown
Member

Summary

Add TimestampBroadcasting.md as a proposal for broadcasting the Harp whole-second time to non-Harp acquisition systems, allowing their recordings to be aligned with the Harp time base during post-hoc analysis. Related to #128.

Motivation

Recording a digital signal carrying the Harp time provides a common reference across acquisition systems with independent clocks. Standardizing the signal format supports interoperability between Harp and non-Harp devices. Devices requiring online clock synchronization should use the Harp Synchronization Clock.

Detailed Design

The proposal uses the repository's RFC 2119 requirements language and defines an optional timestamp broadcasting output:

  • An idle HIGH, 8N1 signal carrying four consecutive Little-Endian bytes of whole-second Harp time, without a header, fractional timestamp, or checksum.
  • One packet per whole second, with the first falling edge of the first byte marking the encoded second and a recommended timing error of less than 32 microseconds.
  • Fixed or configurable baud rates, with the active rate documented or exposed through a readable register included in register dumps.
  • Device interface guidance for output documentation and device-specific configuration, without assigning a new core register address.

An example logic trace reuses assets/SyncLogicTrace.png and explains the AUX UART broadcasting signal alongside the native CLKOUT synchronization signal. The document also includes a packet layout and a transmission-duration example at 1 kbps.

Relevant Discussions

@bruno-f-cruz bruno-f-cruz added the proposal Request for a new feature label Oct 11, 2026
@bruno-f-cruz
bruno-f-cruz marked this pull request as ready for review October 11, 2026 20:52
@bruno-f-cruz bruno-f-cruz added this to the 2.0.0 milestone Oct 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

proposal Request for a new feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants