Discussion
Loading...

#Tag

  • About
  • Code of conduct
  • Privacy
  • Users
  • Instances
  • About Bonfire
Keenan Tims
@ktims@nonexistent.ca  ·  activity timestamp last week

Today on adventures in precision time:

  • 🛠️ Fixed the DO/DI design error with some bodge wires
  • ✨ Amazingly to me, the eeupdate64e tool immediately worked to write both the flash image and the eeprom settings (mostly MAC address). nvmupdate64e didn't, and I tried that first, but never mind.
  • 🔗 After flashing an image and rebooting the machine, LINK IS UP 🤩.
  • 🦥 Unfortunately, only at 100mbit.
  • 🔎 Some examination with the magnifying glass, and a short between FFC connector pins was found and fixed.
  • 💨 Link is now up at 2.5Gbps.
  • ⏰ First experiments using the PPS from the GPS to sync the PHC on the NIC, and then PTP across the network are promising, at least with respect to NTP.

Aside from the bodges, it looks like everything is working.

#timenuts #electronics

A terminal window showing 3 panes.

Left half is a log generated by `ts2phc` on the test platform indicating that the incoming PPS pulses are consistently only a few ns offset from the PHC.

Right top shows the output of `chronyc sources` on another machine, indicating it is synchronized via PTP with the test machine, and a confidence of +/- 166us. Several internet-based servers show current offsets < 5ms, indicating agreement.

Right bottom shows the `cgps` output indicating the module has NO FIX, but can see 4 GPS and 1 Beidou satellites and is confident enough to produce a time output.
A terminal window showing 3 panes. Left half is a log generated by `ts2phc` on the test platform indicating that the incoming PPS pulses are consistently only a few ns offset from the PHC. Right top shows the output of `chronyc sources` on another machine, indicating it is synchronized via PTP with the test machine, and a confidence of +/- 166us. Several internet-based servers show current offsets < 5ms, indicating agreement. Right bottom shows the `cgps` output indicating the module has NO FIX, but can see 4 GPS and 1 Beidou satellites and is confident enough to produce a time output.
A terminal window showing 3 panes. Left half is a log generated by `ts2phc` on the test platform indicating that the incoming PPS pulses are consistently only a few ns offset from the PHC. Right top shows the output of `chronyc sources` on another machine, indicating it is synchronized via PTP with the test machine, and a confidence of +/- 166us. Several internet-based servers show current offsets < 5ms, indicating agreement. Right bottom shows the `cgps` output indicating the module has NO FIX, but can see 4 GPS and 1 Beidou satellites and is confident enough to produce a time output.
The test setup again, this time with two tiny blue wires criss-crossed over the EEPROM, and the 8P8C breakout attached with a Cat5e cable connected.
The test setup again, this time with two tiny blue wires criss-crossed over the EEPROM, and the 8P8C breakout attached with a Cat5e cable connected.
The test setup again, this time with two tiny blue wires criss-crossed over the EEPROM, and the 8P8C breakout attached with a Cat5e cable connected.
  • Copy link
  • Flag this post
  • Block
Log in

bonfire.cafe

A space for Bonfire maintainers and contributors to communicate

bonfire.cafe: About · Code of conduct · Privacy · Users · Instances
Bonfire social · 1.0.0 no JS en
Automatic federation enabled
  • Explore
  • About
  • Members
  • Code of Conduct
Home
Login