LabVIEW Real-Time Idea Exchange

Post an idea

I do not know about most people use cases with RT system, but I have the reflex to click the run arrow to test all my VIs. When I am on site and I do have access to the hardware, everything is rosy. But, when I do not have access to the hardware, and depending on the system complexity, I now have to wait up to over a minutes before I can resume working. It would be nice if somehow once I realized my mistake I could notified LabVIEW (right away) to run my VI in the main application instance instead of attempting to deploy it on the missing target.

Alternatively, once I made the mistake once, LabVIEW could automatically run the VI in the main application instance.

I do not know what is the best approach to fix this, but I know that I am very annoyed every time I make that mistake.

View All (2)

I was replying to a message thread someone had about question marks showing up for the times in the I/O channels for a compact Fieldpoint system. While investigating, I notice on my system that I had timestamps for data that occurred later in the day than the current time. So I know those timestamps were from a day prior than the current day. Actually, the test stand had been idle for quite a few days, so I pretty much know those I/O channels had not been updated for a while. But I could not tell from the timestamp when exactly that data was from.

In the attached screenshot, the current time was about 1:44 pm. Some data shows it had just been timestampled. Some data was from 7am, other data from 2:19 pm or 4:19 pm. I know that that data had to have been from yesterday or older. The 7am could be from today or older, but there was no way to tell. Based on my usage of that test stand, I'm pretty sure all of that data is at least 3 days old, and perhaps 6 or 7 days old. That is okay and not a problem. But there is no way of knowing how old that data actually is based on this screenshot.

I think MAX should show the date as part of the timestamp when looking at the I/O data.