# Logging delay at start of scenario

**URL:** <https://learn.safran-navigation-timing.com/t/logging-delay-at-start-of-scenario/322>\
**Category:** Skydel Discussion\
**Created:** [January 5, 2022, 3:15pm UTC](https://learn.safran-navigation-timing.com/t/logging-delay-at-start-of-scenario/322 "2022-01-05T15:15:16Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jaemin.powell](https://avatars.discourse-cdn.com/v4/letter/j/b5ac83/32.png) [@jaemin.powell](https://learn.safran-navigation-timing.com/u/jaemin.powell)\
**Post date:** [January 5, 2022, 3:15pm UTC](https://learn.safran-navigation-timing.com/t/logging-delay-at-start-of-scenario/322/1 "2022-01-05T15:15:16Z")

</div>

Why does it talk ~500ms before logging shows up in the CSV files?

---

<div class="post-metadata">

**Author:** ![Grace](https://avatars.discourse-cdn.com/v4/letter/g/f17d59/32.png) [@Grace](https://learn.safran-navigation-timing.com/u/Grace)\
**Post date:** [January 5, 2022, 6:55pm UTC](https://learn.safran-navigation-timing.com/t/logging-delay-at-start-of-scenario/322/2 "2022-01-05T18:55:02Z")

</div>

Hi Jaemin,

the latency of 500 ms in the Skydel logging files is a propagation time between the satellite and the receiver during which there is no data. We decided to round this latency to around 500ms for the logging files.

Grace