reading data takes 2 seconds

[Dennis_Knutson]

You have a 1 second delay on both the read and write of the FWB6010. You need to actually look inside the VIs. Did you ever run the Application Example by itself? That's the sort of basic troubleshooting you could have done and that would have isolated the problem.

[Hadiq]

Yes, I run the application that contacts with the device and it gives me the actual reading that is shown on the device screen. I forgot to place it in a loop to see if there is a delay because I was focussing on determing if there is a communication with the device. Alternatively, I put it in the large code and removed the sequence structure but there is a long delay (2.5 sec). Hope this is what you meant.

[Dennis_Knutson]

I don't know why you would want to put it in a loop. The function you are calling (FWB6010 Application.vi), takes 2 seconds to run. That is the way it has been programmed and that is something you can change. Be aware that the default run time of two seconds may be a limitation of the instrument.

[Hadiq]

Hi Dennis,

Please show me how to do this. I could not edit the green function (FWB6010Flux Query) in the middle of the application you meant.

Many thanks

[Dennis_Knutson]

Both of the circled functions in the FWB6010 Flux Query.vi have a delay input. One is called Write Delay and the other is called Read Delay. Both are set to a default of 1000ms. Wire a different value to them and see if the VI still works.

[Hadiq]

Hi Dennis,

Thank you very much indeed for your help. Both functions are not shown in the application and replaced by question mark

icons and this was the source of the confusion. I hope it will be better in the lab computer. I'll try your suggestion tomorrow and hope it ends this problem.

Many thanks,

[Hadiq]

Hi Dennis,

I changed the time delay from 1000 to 100  (read and write) but it does not make any difference I'm afraid. Is there any other ideas?

Many thanks,

[Dennis_Knutson]

You are saying that you edited FWB6010 Flux Query, ran it, and it still took 2 seconds to run?

[Hadiq]

Yes, I did that. I changed the setting as you suggested and saved it (I did not make it a default value) and it still takes 2.5 seconds to reading the data  in the third loop.

[Dennis_Knutson]

Attach the VI you changed.