# Anyone else encountering this in live data plots?

**URL:** <https://opensourceleg.discourse.group/t/anyone-else-encountering-this-in-live-data-plots/162>\
**Category:** Software\
**Created:** [December 3, 2025, 10:04pm UTC](https://opensourceleg.discourse.group/t/anyone-else-encountering-this-in-live-data-plots/162 "2025-12-03T22:04:43Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sani\_Hasan](https://yyz2.discourse-cdn.com/flex036/user_avatar/opensourceleg.discourse.group/sani_hasan/32/56_2.png) [@Sani\_Hasan](https://opensourceleg.discourse.group/u/Sani_Hasan)\
**Post date:** [December 3, 2025, 10:04pm UTC](https://opensourceleg.discourse.group/t/anyone-else-encountering-this-in-live-data-plots/162/1 "2025-12-03T22:04:43Z")

</div>

Hey, So i was plotting live data on the osl pf just the ankle swing recording the following, Command degree, measured degrees, motor current and sample count, i am kind of worried about the steps as they are showing up, even when i try to send data to something else like simulink through an ethernet cable i experience constant jitters in the data, is this due to the pi being not real time and os task scheduling lag or something else. or is it like a combined delay of the UDP packets being sent by the pi and recieved by simulink and being unpacked.

 ![done](https://canada1.discourse-cdn.com/flex036/uploads/opensourceleg1/original/1X/d5c16a281b6bac848b1888a5fb658fd87b48e255.jpeg)

 ![run1 with sample count over time](https://canada1.discourse-cdn.com/flex036/uploads/opensourceleg1/original/1X/64552bd485cd5210846ed3a8c0608247b52c7015.png)

---

<div class="post-metadata">

**Author:** ![ldevillez](https://yyz2.discourse-cdn.com/flex036/user_avatar/opensourceleg.discourse.group/ldevillez/32/71_2.png) [@ldevillez](https://opensourceleg.discourse.group/u/ldevillez)\
**Post date:** [December 4, 2025, 3:16pm UTC](https://opensourceleg.discourse.group/t/anyone-else-encountering-this-in-live-data-plots/162/2 "2025-12-04T15:16:26Z")

</div>

Hi,

Are you logging anything during your test ? If yes what is your buffer size and which entry do you log ?

Do you have a MWE showing those issues ?

---

<div class="post-metadata">

**Author:** ![Sani\_Hasan](https://yyz2.discourse-cdn.com/flex036/user_avatar/opensourceleg.discourse.group/sani_hasan/32/56_2.png) [@Sani\_Hasan](https://opensourceleg.discourse.group/u/Sani_Hasan)\
**Post date:** [January 2, 2026, 3:03am UTC](https://opensourceleg.discourse.group/t/anyone-else-encountering-this-in-live-data-plots/162/3 "2026-01-02T03:03:25Z")

</div>

I am Logging multiple readings during my test, I am not using a buffer size as I was hoping for a ‘real - time’ system since what I am working on requires the timing constraints to be met strictly below 100 ms on the overall system.

I have an ethernet setup sending the live data in big eddian to a live simulink logging where I am collecting data and displaying it (first image)

the python script running on the OSL is separate; its left to let the ankle only swing freely on the setup as the Matlab just logs it in real time. I noticed samples were jumping and missing in most cases so i was asking about that.

---

<div class="post-metadata">

**Author:** ![ldevillez](https://yyz2.discourse-cdn.com/flex036/user_avatar/opensourceleg.discourse.group/ldevillez/32/71_2.png) [@ldevillez](https://opensourceleg.discourse.group/u/ldevillez)\
**Post date:** [January 3, 2026, 8:57am UTC](https://opensourceleg.discourse.group/t/anyone-else-encountering-this-in-live-data-plots/162/4 "2026-01-03T08:57:43Z")

</div>

Your timing constraints is for what ? If it is for your inner loop, it is plenty enough.

First I would do a check with only your hardware. Replace your communication with simulink/matlab with a python script running on the OSL just to save the data. With this setup look if you still see some data missing.