LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Darren's Weekly Nugget 10/23/2006

 
While working on my current project, I developed some Custom Probes to help with my debugging, and I posted them on the NI Community website here:
 
 
You can get a complete description of my History Probes at the link above, but basically, they allow you to see a history of values that have passed through a wire.  I created History Probes for all scalar numeric datatypes (excluding U64 and I64, since I wrote these in LabVIEW 7.0), as well as strings, paths, and Booleans.  These really helped me when debugging situations where I had a For Loop that ran a certain number of times, and I needed to see the sequence of values that passed through certain wires during each iteration of the loop.  I hope other LabVIEW developers find these useful.
 
-D

P.S. - Check out past nuggets here.



Message Edited by Support on 04-29-2008 09:17 AM

Message 1 of 22
(15,945 Views)
That's really cool ! Great probes Darren, I can think of many project where they could have helped me Smiley Surprised

Maybe one nugget a week is not enough Smiley Tongue, anybody agree with that ?



We have two ears and one mouth so that we can listen twice as much as we speak.

Epictetus

Antoine Chalons

0 Kudos
Message 2 of 22
(15,916 Views)
Great use of custom probes!
 
(A quick and dirty way to do this without custom probes is to probe with a chart (numerics only, of course)). 🙂
0 Kudos
Message 3 of 22
(15,898 Views)
Very nice, Thank you Darren



Joe.
"NOTHING IS EVER EASY"
0 Kudos
Message 4 of 22
(15,837 Views)
Two thumbs up!  Very useful.
Matthew Fitzsimons

Certified LabVIEW Architect
LabVIEW 6.1 ... 2013, LVOOP, GOOP, TestStand, DAQ, and Vison
0 Kudos
Message 5 of 22
(15,840 Views)
Great man... !
 
Regards,
Partha.
- Partha ( CLD until Oct 2024 🙂 )
0 Kudos
Message 6 of 22
(15,531 Views)

Darren,

Is there a limit to the number of points that this history probe can contain??

Dev

0 Kudos
Message 7 of 22
(15,501 Views)
The only limit is the maximum size of a 1D array, which is about 2 billion.  But I imagine your system would bog down way before then.  🙂  That's what the "Reset on Next Run" button is for...it clears out the history you've acquired up to that point and starts over.
 
-D
0 Kudos
Message 8 of 22
(15,426 Views)
I've created similar probes, but I like the look of yours better (I didn't use a table, just a normat array indicator). I also added a "stats" tab that shows min, max, average and median and a conditional tab with lots of options to pause execution. I think I also have some that keep the timestamp of each value and provide an option to save to a tab-delimited file. I don't have a full set (never seem to use EXT or I8 🙂 I find that custom probes are one of the great unused features in LabVIEW. Why not throw in a bunch of historical probes for the next release?
0 Kudos
Message 9 of 22
(14,449 Views)

Thanks for the feedback...we'd have to do a bit of work to ship these History Probes with LabVIEW.  For one thing, I was using them the other day to debug a race condition, and discovered they were quite slow (so slow, in fact, that simply using the History Probes eliminated the race condition)...this is probably because of the thread switching associated with frequent calls to the listbox property node to update the probe display.  I prototyped a similar History Probe using the array control, but with a vertical scrollbar (new feature in LabVIEW 8.0, I think I mentioned it as a nugget earlier this year)...anyway, the array History Probe was much faster, since there were no Property Node calls.  Nevertheless, I do recognize that these would be good to ship with the product, and I also agree that Custom Probes are one of the coolest features that came out in LabVIEW 7.0 (*almost* as cool as right-clicking a loop tunnel and choosing "Replace with Shift Register").

-D

0 Kudos
Message 10 of 22
(14,152 Views)