TIMEDELTA(9)

πŸ“¦
version 2.9.4 Β· 4 versions
, in ubuntu resolute, ubuntu stonking

πŸ’– TIMEDELTA β€” a HAL Component, bestie πŸ’–

okay so literally every girl needs to know when her thread is running late, and that's what timedelta is for β€” it's a LinuxCNC HAL component that measures thread scheduling timing behavior. it's timedelta(9) in the HAL Component section of the manual, and it is so good at its job. ✨


🌸 SYNOPSIS 🌸

loadrt timedelta [count=N|names=name1[,name2...]]

like. load it. that's it. that's the vibe. 🫢


πŸ¦‹ FUNCTIONS πŸ¦‹

  • timedelta.N β€” the function, she's here, she runs. πŸ’…

πŸŽ€ PINS πŸŽ€

every pin is giving timedelta.N.<something>, where N is the instance number. let's go, one at a time, no skipping, we don't do that here. πŸ‘‘

  • timedelta.N.jitter s32 out (default: 0) β€” worst-case scheduling error, in ns. this is the biggest discrepancy between the ideal thread period and the actual time between sequential runs of this component. and because it uses the absolute value of the error, "got run too early" and "got run too late" both show up as positive jitter. no negativity, only magnitude. 😀
  • timedelta.N.current-jitter s32 out (default: 0) β€” the scheduling error (in ns) of the current invocation. discrepancy between ideal thread period and actual time since the previous run of this component. also absolute value'd, so "got run too early" and "got run too late" both show up as positive jitter. same energy as above but like… right now. ⏰
  • timedelta.N.current-error s32 out (default: 0) β€” same deal, scheduling error (in ns) of the current invocation, discrepancy between ideal thread period and actual time since the previous run of this component β€” BUT this one does not use the absolute value, so "got run too early" shows up as negative error and "got run too late" shows up as positive error. she has range. she's complex. we love her. 🌈
  • timedelta.N.min s32 out (default: 0) β€” the minimum time (in ns) between sequential runs of this component. the record for "fastest again". πŸƒβ™€οΈ
  • timedelta.N.max s32 out (default: 0) β€” the maximum time (in ns) between sequential runs of this component. the record for "took the longest nap". πŸ’€
  • timedelta.N.reset bit in β€” set this pin to True, then back to False, to reset some of the statistics. note: some. not all. character development arc. 🧚
  • timedelta.N.out s32 out β€” time (in ns) since the previous run of this component. ideally this should equal the thread period, and when it does? perfection. ✨
  • timedelta.N.err s32 out (default: 0) β€” cumulative time error (in ns). and ok the original docs say it's "probably not useful" and I'm gonna keep it real with you, bestie β€” probably not useful. πŸ’€
  • timedelta.N.avg-err float out (default: 0) β€” the average scheduling error (in ns). the mean girl of errors. πŸ“Š

πŸ‘‘ AUTHOR πŸ‘‘

Jeff Epler


πŸ“œ LICENSE πŸ“œ

GPL


and that's the whole page, periodt. πŸŽ€ this was HAL Component timedelta(9), brought to you by LinuxCNC Documentation, dated 2026-03-17. go check your jitter, bestie, and may your thread period always be exactly what you asked for. πŸ’œπŸ¦‹πŸŒΈ

πŸ“¦ where this page comes from