From f8e8057d48c4eaf1cf512eccf7ae644f931ac005 Mon Sep 17 00:00:00 2001 From: Davide Iafrate Date: Tue, 28 Jan 2025 12:51:19 +0100 Subject: [PATCH] Clarification for timestamp in JSON interface --- libraries/SITL/examples/JSON/readme.md | 1 + 1 file changed, 1 insertion(+) diff --git a/libraries/SITL/examples/JSON/readme.md b/libraries/SITL/examples/JSON/readme.md index 47b4a85674c53d..306fb0abf55972 100644 --- a/libraries/SITL/examples/JSON/readme.md +++ b/libraries/SITL/examples/JSON/readme.md @@ -58,6 +58,7 @@ This is a example input frame, it should be preceded by and terminated with a ca {"timestamp":2500,"imu":{"gyro":[0,0,0],"accel_body":[0,0,0]},"position":[0,0,0],"attitude":[0,0,0],"velocity":[0,0,0]} ``` The order of fields is not important. +Note that the timestamp is the absolute physics time, not the timestep. It is possible to send optional fields to provide data for additional sensors, in most cases this will require setting the relevant sensor type param to the SITL driver.