Aerospace, Defense, & Government
Academic & Research
Benchtop Measurement and Test
Distributed Measurement and Control
Systems Engineering Software
You can request repair, schedule calibration, or get technical support. A valid service agreement may be required.
Provides support for NI data acquisition and signal conditioning devices.
Provides support for Ethernet, GPIB, serial, USB, and other types of instruments.
Provides support for NI GPIB controllers and NI embedded controllers with GPIB ports.
WARNING! Before installing the newest version please remove the old version. Otherwise two versions might install side-by-side.
This tool allows users to easily create multiple timers for controlling the timing of their code, measuring or benchmarking.
By Reference Example
Created by Piotr Kruczkowski
And does it support overflow?
What do you mean by that? It does not handle overflow in any special way. The VIs are open so you can look inside how tey work.
I think he's talking about the overflow that can happen on the ms counter VI, so that if you are subtracting a rolled over value from a non rolled over value, you'll end up w/ some huge delta between times.
However for @WG- I think he's thinking more typically about counters rather than timers that suffer primarily from this issue; timers are not free from this potential error however.
Hi, I need to make a timer similar to elapsed time Express VI in my FPGA target.
Very nice work!
Very elegant and simple, one request (i did modify mine but it would be nice to modify yours so i can use your package.
I have added the possibility to change the goal time upon reset.very usefull for things that have incremental timing.
In this case you might just stop the old timer and create a new one. Would that be a solution? I understand that in some cases restart with new target would be good but it could be confusing.
Well it would be a solution, but personally i would not find it the most elegant one,
Codewise it's calling more VI's, the above just gives it a bit more flexibility.
RuudWessels, i added the function you requested 🙂
Thanks PrimaryKey, it's become a very usefull tool indeed!
Nice! Question: why in the VIPM (2018 with LV2018) we only get the version 184.108.40.206? At this community doc, your latest version is 220.127.116.11...
Just this can cause confusions to people...
Thanks for letting me know. I will try to fix that as soon as possible.
Seems like there is something wrong with the package on VIPM. The version says it's compatible for LV>=2016, but the install aborts saying it is in 2017 and higher. Could you please fix that?
what a good tools，THS！！1
Abvenk, you need to update your package manager 🙂 Thats it.
What do you need our team of experts to assist you with?
We'll be in touch soon!