You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The SLSC API has some limits to how fast you can read a property and it can take some time to execute. If you use the SLSC EDS to read every channel in the card, that can lead to take a considerable amount of time to read all properties (which also make the "writing" properties slow, by default). However, although the writing properties are done on "value change", reading only has the option to "not" read (and remove the channel) or read all channels with the same speed. To improve performance, we can introduce two other "features" to the EDS:
we can separate the writing channel from reading and run on a "faster" loop rate, so the latency to changes would not be too large (and allow the SLSC EDS to apply changes faster):
we can introduce the concept of "decimation" in the reading channels, since not necessarily you need to read every channel with the same speed.
and for "read-only" channels or properties that are constants, we can introduce the concept of "read once" at the beginning that will make the reading process more optimized.
The text was updated successfully, but these errors were encountered:
The SLSC API has some limits to how fast you can read a property and it can take some time to execute. If you use the SLSC EDS to read every channel in the card, that can lead to take a considerable amount of time to read all properties (which also make the "writing" properties slow, by default). However, although the writing properties are done on "value change", reading only has the option to "not" read (and remove the channel) or read all channels with the same speed. To improve performance, we can introduce two other "features" to the EDS:
The text was updated successfully, but these errors were encountered: