Drive Connect optimal usage

[aFouraker]

I have an application that is polling data from multiple drives and reading mutiple parameters from each drive at a rate of anywhere from ~100ms - ~1sec and see the CPU take a significant hit.  What is the best way to poll parameters from drives using the SIP protocol with drive connect so as to cause the lowest load on the system CPU use? Does subscribing produce a lower load? Does a batch read have lower overhead? What is the best practice? 

[MauroRiboniMX]

Which version are you using? Anyway you can easily activate the oscilloscope on the drive and take the data out of there!

[CodeShepherd]

Could you more specify what quantity of parameters you are talking about and what "a significant hit" means in numbers?

A subscription will internally also poll the data from the provider (in your case drive) so will create a similar load.

[aFouraker · Accepted solution]

I switched to a newer version of the app (1.20.2) and the problem was fixed.