Description
Return speed*latency and speed*latency+acceleration*latency²/2; use m/s and m/s² for distances in metres.
Telemetry latency can displace a recorded observation from the position of a moving machine. Constant-speed and constant-acceleration terms use different assumptions, and signed motion can reverse a displacement. A nominal distance contribution differs from an observed positioning error.
Return speed*latency and speed*latency+acceleration*latency²/2; use m/s and m/s² for distances in metres.
When to use this tool
Use Farm Telemetry Latency Distance Term when checking the stated latency-distance term.
How to use the tool and how it works
- Enter latencySeconds, speedMetersPerSecond, acceleration. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read constantSpeedDistance, acceleratedDistance. Use the output convention below.
Require nonnegative latency in seconds. Return speed*latency and speed*latency+acceleration*latency²/2; use m/s and m/s² for distances in metres.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| latencySeconds | Latency Seconds | Required. Finite number; minimum 0. |
| speedMetersPerSecond | Speed Meters Per Second | Required. Finite number. |
| acceleration | Acceleration | Required. Finite number. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| constantSpeedDistance | Constant Speed Distance | Required. Finite number. |
| acceleratedDistance | Accelerated Distance | Required. Finite number. |
{
"input": {
"latencySeconds": 2,
"speedMetersPerSecond": 3,
"acceleration": 1
},
"output": {
"constantSpeedDistance": 6,
"acceleratedDistance": 8
}
}Limitations and assumptions
- These are constant-speed and constant-acceleration terms, not measured telemetry error or a safe stopping-distance model.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.
Alternative or Complementary methods
Use synchronized calibrated trajectory and sensor records with a complete motion/error model for positioning accuracy or equipment operation.
References
Similar or alternative tools
- Farm Event Source Delay
Normalize eventTime by subtracting sourceOffset.
- Farm Task Clock Source Flag
Compare clock-source labels literally.