Timed loop bug

[RavensFan]

I'm past 40,000 on the size and it still hasn't stopped.

What is interesting on your screenshot is that while you stopped at size 20,828, the found zero was much earlier in the array at element 1529.  Why wouldn't it have found the zero back then?  Rather than a zero having been added to the array at that time, it's like it was changed from something else to a zero.

[smercurio_fc]

---

@TPoint wrote:

The 'search array' is only to detect the zeros!

---

I know precisely what it's doing. You're missing the point. Search 1D Array performs an EQUALITY operation. You should not use EQUALITY ON FLOATS unless you have very specific conditions that will guarantee it will work. Period. I'm not telling this is the cause of your alleged bug, which so far neither I nor Ravens Fan have been able to reproduce. What I'm telling you is something you don't seem to want to understand. Try this: Change the format and precision for the array indicator so you can see out to, say, 15 decimal places.

[SynergyMike]

Chiming in with a wild guess...

I haven't tried your VI (only have LV7.1 and not on the email machine), but based on your graph I'd say you have some issues with time formatting; I was getting that myself this week - reading data formatted as "01/01/2011 4:59:30 PM" and converting to a format compatible with XY Graph, the YEARS wound up all over the place because I didn't handle the HOURS correctly, resulting in bad data being fed to the XY Graph.

Regards,

Michael Tracy

Synergy Microwave