Hi,

I would like to have a probe with a timestamp to see when the data passes. Then I can evaluate what parts of my code take the most time. Now I'm always messing around with 'tick count.vi' before and after and have to delete it afterwards. Any ideas?

Thanks in advance,

Manu.

This post has been edited by psychomanu: Oct 11 2004, 12:04 PM

OOh! This sound like a cool challenge. Anyone got this coded yet?

Not quite a code challenge, I'v already done something like that, with quite some statistics (haven't the code anymore present, must have lost when I last changed job )



You'll still have to wire them into your code, but less complicated than with sequences. If you make the icon footprint small (e.g. a small clock, 8x8pixel), it won't disturb your code too much.

Didier

I was hoping more for a custom probe a la LV7.0...

Exactly, a custom probe would be great,altough the previous suggestion is already helpful, I will try to make such a small footprint icon. Already much more convenient then what I do now. Thanks for the suggestions.

Manu.

It seems that LabVIEW makes a temporary copy of CustomProbe (which you create) when you place one, and than deletes when you remove a probe from diagram. So, if you place Probe tvice in the same diagram, there is tvo SEPARATED reentrant probes, but where them stores, i did not find.. Therefore, you cannot place SAME probe on tvo places in the same time, therefore simple "delay" vi would not work. So, probes must to share one resource, file or pipe. It is a tricky one. Or, when you place two probes, you need to "rename" (in memory? ) one of them, so both have same name.. (Talking about two instances with the same name )
Any ideas? /ProximaBleu

Sorry for being not up-to-date, I'm still using Lv6.1

Hi All
using cut and paste (what else)
have strung a probe example together using Danny and Helen's previous coding.
It provides a sound when probe recieves data and also recordes actual time to text log.
It is necessary to generate you own text log before hand for it to function.
Have funny & modify to suit your own appls.

chow
xseadog

Soory all it appears had time out on upload.
Will try again

BTW, I have did some probes project, for debugging applications, using Queries. It is working fine, have "console" debuging window, and works in DevSys as well in RunTime.. i had posted it in OpenG, but nobody was interested. Does someone will want to look at it? Works in LV6.1 too.
/PB

This post has been edited by proximableu: Oct 12 2004, 01:27 PM

here it is..

 LVDEBUG.zip ( 240.1K ) Number of downloads: 248

Here is a custom time probe I created to help me see how much time a vi used up.
the first one attaches to an error cluster and the second uses a variant to attach to any data
type.

The probe has a enum selector with 3 choices Start, Time and Cycle
Start: starts the timer
Time: takes a time reading
Cycle: takes a time reading and restarts the timer

The probe will use a different timer for every ID number used.
(see demo.png).

The Probes contributed above are great.

I think it would be good to combine some of this with the Universal Probe that Jim Kring developed:

http://www.openg.org/tiki/tiki-index.php?p...iversal%20Probe

Combining timestamping with universality and a queued logging mechanism would be very useful.

On another thread in the forums we ended up getting into some of the same stuff here. I don't like to cross-post, but I felt it might help a few more people see and also avoid some duplication.

Is there anyway to consolidate two topics into a single topic if their material has started to converge significantly? (Good question for the other Michael)