Wait until next ms multiple in microseconds

[alaio_3]

Hi, I use this time for my project but I should need the time in microseconds. Is there any possible way that I can adjust the timer or use something else ?

[smercurio_fc]

You didn't provide any information as to what you're using this timing for, but as far as that function is concerned, you can't set the resolution in microseconds. Nothing based on software timing will give you that accuracy due to OS restrictions. For that you need hardware timing, and how you do it is based on what you're trying to accomplish and what you've got, as well as what you're willing to do and/or can do.

[alaio_3]

for my project I need to mesure a signle, and between every mesurements, my program needs to wait 8µS

Someone told me that I could do that with hitime32.ocx, i've found the ocx but don't have a clue how i can use it in labview 7.1

[shoneill]

So basically, you want to measure a single witha  frequency of 125kHz, right?

If you're using an ADC card then you can simply set the measurement frequency to 125kHz and the card will basically do the rest.

So the question is: Are you sampling an analog source?  If so, the answer is easy, if not it's a bit more difficult.

Shane.

[alaio_3]

it's digital... all I need is a microseconds timer, it should be working with the hitime32.ocx file but I don't get it how I can get it to operate.

[shoneill]

Sorry, no experience with this OCX timer.

Shane.

[smercurio_fc]

That seems to be an ActiveX control, so it would be used like any other ActiveX control. It's made by Mabry software. However, the documentation says its resolution is 1 msec, so I don't see how this is going to solve your problem. Bottom line: You can't get that degree of accuracy with a software based solution.

Message Edited by smercurio_fc on 02-14-2006 08:43 AM

[altenbach]

What kind of data acquisition hardware do you have?  You just need to setup a hardware timed aqcuisition, there are plenty fo example available.

[alaio_3]

all I need is something that creates a delay of 8 µS between 2 steps

[Kevin_Price]

alaio_3,

I see you're kind of new here, so please accept this as friendly advice.  You seem to have a technical grasp on what you need so I think you're likely to benefit.

As I read through the thread, it seems that the responses are generally better organized and clearer than your questions and comments.  I personally tend to run from such threads rather than get sucked into what can become a long series of back-and-forth partial progress because too little info is disclosed upfront.  Reasonable responses are given, but turn out not to be useable because of other constraints not previously mentioned.  And so on. 

Speaking for myself, I don't enjoy feeling like I'm putting in more effort than the person with the original question.  At this point in the thread, several people have suggested hw-clocked measurement with a DAQ board -- is there a reason you can't or prefer not to do this?  Why do you want to use that ActiveX control, especially now that someone even looked up docs on it for you and found that it doesn't seem capable of doing what you're expecting?

Again, I mean this as friendly advice.  I have a feeling that some folks approach these forums as though it's instant-messenging while others approach it more like an e-mail list.  I'm very much one of the latter, and reserve the right to be a grumpy old coot about IM-style writing.  Your mileage may vary.

-Kevin P.

"you kids get off my lawn!"