Dcom Acquiring property lag

Hello, I'm using dewesoft X and Dcom to develop a communication between visual basic 2015. At this moment using Dcom I'm able to open a sequencer, launch a task, start trigger from an external source and so on, nevertheless when Im trying to synchronize the visual basic program execution with the dewesoft aquisition, in the property Dewesoft.IApp.Acquiring there is a lag time between the value of this property and what its happening in real, in brief the acquiring property its true seconds before the dewesoft app starts the acquisition (wheter its storing data or not). Is there another property which tells to dcom the exactly moment of acquiring status? Where this lag its coming from?. Thanks in advance for your support

Dear Elkin,

We don't have an option to directly access the event but you can create a workaround. You should set your setup file to "Start storing automatically"

Then you should implement the event OnStartStoring. That way, you will be able to know the right time. Please let me know if this fits your requirements.

Best regards

@Matic Pevec hello , unfortunately the event OnStartStoring is not what we are looking for. The system runs the acquisition but stays “acquiring” till an external trigger (2.5V rising edge level) arrives. This trigger launches the start storing. We need to know the exactly moment when the system it’s on acquiring status but the current property (Dewesoft.IApp.Acquiring) is not accurate. We notice there is a lag, almost constant (5seconds), actually the problem it’s partially solved by consuming time in our side waiting for the real “acquiring status”. Thanks for your support.

Hi,

Since you are reading the external trigger I would suggest reading the time on the rising edge with "OnGetData" (Manual) as a workaround.