I'm trying to use an E810 timecard with timebeat software.

I'm using the latest ICE driver/ddp, and all works fine with a ptp4l/etc based setup.

The issue i'm running into is that it's not obvious what protocol to use with /dev/gnss0 as the secondary source.

NMEA doesn't work because it's not a serial port. Strace says:
openat(AT_FDCWD, "/dev/gnss0", O_RDWR|O_NOCTTY|O_NONBLOCK) = 12

ioctl(12, TCGETS, 0xc00055f2c0) = -1 ENOTTY (Inappropriate ioctl for device)

ioctl(12, TIOCNXCL) = -1 ENOTTY (Inappropriate ioctl for device)

close(12)

IE Timebeat opens it, tries to treat it like a serial port, and when that fails, closes it and gives up.

Is it possible to make this work?

On a PTP client the only log entries of timebeat are: logging queue is full.
How can this be solved?

Setup:
Server: Raspberry CM5/Essential/.deb file installed
Client: Proxmox/.deb file installed

I recently completed a build using the Mini Timing Lite for my homelab. I am writing my output to files instead of storing it in Elasticsearch.

I looked around but couldn't find documentation or a schema that describes the various attributes and values in the NDJSON files.

My reasons for this information:
1. If I need to troubleshoot, I can at least review the logs to determine issues.
2. In the near future, I would like to get relevant data into Prometheus and Syslog/SIEM.

Thank you for any information you can provide.

I'm having trouble setting Timebeat up as an NTP server. I'm using a CM4 Module w/GPS as my hardware. My NTP config, under primary clocks, is as follows:

      - protocol: ntp
        serve_unicast: true
        interface: eth0
        server_only: true

I have hardware stamping enabled, and the service appears to be listening on UDP port 123. My windows machine times out with error: 0x800705B4, both with and without hardware stamping, and other Linux machines are only able to get time if hardware time stamping is enabled, otherwise it times out similarly to Windows.

Am I doing something wrong here? The LLMs have seemingly not ingested enough Timebeat documentation as they have hallucinated many, many yaml fields.

TIA!

Does license applies also for standalone PTP Grandmaster?

We were not aware of this licensing scheme at time of purchase...
We noticed there is 90 days free license - is there API to generate license automatically?

Can this support consuming various clocks, and be controlled which one to use by an external tool on-the-fly?

Also, there is note of the system supporting timestamping external events ("8 input for timestamping external events"), but I cannot find any documentation about how that works. Can you refer me to where the documentation for that feature is.

For that matter, I cannot find any documentation of what connectors the card even has, outside of the specsheet. Am I blind and missing something obvious?

I'm trying to configure a Mini PTP Grandmaster Clock with the G.8275.1 Profile but I'm having some problem, is there an example configuration i should start from?

After changing the default configuration a bit i was able to make it almost work but the ptp4l slave is giving me this error: "foreign master not using PTP timescale" and i was not able to solve it by changing anything in the timebeat config.

I attached the current ptp4l configuration but i need to fix this problem from the timebeat side (this ptp4l config works with 2 other GM that we have).

ptp.conf:
[global]
dataset_comparison G.8275.x
G.8275.defaultDS.localPriority 128
maxStepsRemoved 255
logAnnounceInterval -3
logSyncInterval -4
logMinDelayReqInterval -4
serverOnly 0
G.8275.portDS.localPriority 128
ptp_dst_mac 01:80:C2:00:00:0E
network_transport L2
domainNumber 24

Thanks