LabVIEW Idea Exchange

Top Authors

User

Kudos

Post an idea

View All (1)

String/Time Stamp Conversion

LabVIEW currently has functions Format Date/Time String and Scan Value to convert between time stamps and strings. Unfortunately, these functions do not handle arrays of time stamps and strings. While this conversion can be handled using a For Loop, a specific function would be cleaner and probably faster. This functionality is currently available for other numerics and should be extended to time stamps.

I suggest modifying the Format Date/Time String function to handle arrays of time stamps, integers and floating point numbers as well as single values. An additional function Date/Time Sring to Time Stamp should be created to convert strings and array of strings to time stamps.

View All (3)

The new Profile buffer allocations function introduced in 2014 Service Pack 1 is a nice addition, but there are a couple of things that surprised me about it;

1. The graph at the bottom is very small (why not show it by default as well, makes it easier to notice for new users), and you cannot rescale it to make it easier to read. This should be simple enough to support (and as many ideas her eon the exchange suggests; such functionality should always be available).

2. The profiler does not update while monitoring. It would be much nicer to be able to actually see the allocations as they happen; to link the events to actions in the program...Instead we have to stop the trace, and then try to link the graph to past events...

3. Even though you can choose a size unit, the graph will always use bytes...It should use the same size unit as you have chosen for the table view, or have its own unit control.

Close build window when done

View All (1)

If you've ever tried to use the LV Web Service > Session VIs for sessios, authentication, user management, etc., then you'll quickly notice that they're lacking an important feature: the ability to detect when a user session times out (expires).

I can think of two important use cases as of why you'd care:

(1) The user/client is viewing sensitive information (served to him by a LV web service), and then decided to walk away from his computer as we do sometimes. Any Joe walking by might then get a glimpse of something he shouldn't.

(2) For logging purposes. It might just be nice to know when the user logged in and when the user logged out for your IT records.

With a securely built web service, you could detect the user isn't there anymore, and direct the web client (Chrome, FF, IE, etc.) to redirect the page and destroy the session.

There's a sister idea that goes along with this, but I don't think I'll post in a separate thread unless needed. So, another way to detect session timeout events would be to get the session ID cookie (from Create Session VI), store each cookie in memory somewhere, and essentially poll them in a background loop for session information (ie session still exists?).

Ho hum, maybe I'm the only one building web applications of this type, but it sure would be a helpful feature in my opinion.

Stop using IMAQ Create VI

When debugging LabVIEW code containing multiple loops, it would be helpful to be able to apply the breakpoint/highlight values/single step etc debugging operations to only one of the loops. Currently when the debugger hits a breakpoint in one loop, single stepping the code then executes one instruction at a time with the result that the execution point jumps between functions in the different loops. This is quite frustrating when it is only the code in one specific loop that is of interest.

Resolving an issue with calling MSSQL 2008 server side user stored_Procedures (or for that matter any other ADODB and user stored procedures) within Labview using the "LabVIEW DB Tools Create Parameterized Query VI."

This database toolkit vi will provide you the elements of a stored procedure provided you know the stored procedure name.

HOWEVER to get the list of stored procedure names for a db current requires user SQL coding and execution.

Could the functionality of the "LabVIEW DB Tools Create Parameterized Query VI." be extended to return the list (array) of the names of the held user stored_procedures..

See in code snippet

1. An example of the current method of getting list of user defined stored procedures

2. What I would like LabVIEW DB Tools Create Parameterized Query VI to provide is some command in (or set some flag) and return an array of user defined db stored_procedures names such as in the first code snippet from which I can then pragmatically select as input to code snippet 3

3. The current implementation by which the "LabVIEW DB Tools Create Parameterized Query VI." when given a stored procedure name returns a cluster of the parameter names and details of that stored procedure

Create two versions of the LabVIEW Run-Time Engine - 1 with dependencies (vi.lib, etc.) and 1 without dependencies. If a LabVIEW Run-Time Engine with dependencies were to be created, it would allow you to bypass the TestStand Deployment Utility when deploying test software created using TestStand. It would also simplify Application Builder because any native dependencies (code shipping with LabVIEW) wouldn't have to be packaged with a LabVIEW executable (only the user-created dependencies).

If maintaining two versions of the LabVIEW Run-Time Engine isn't acceptable, it would be nice to just include the dependencies in the LabVIEW Run-Time Engine. Disk space and broadband Internet connections have almost virtually eliminated the necessity for a LabVIEW Run-Time Engine with a small disk or installer footprint, particulalry when NI hardwire driver installers take up 100s or even 1000s of MB on disk.

Search for a different element

a possible improvement for the "search 1D function"

The current function searches for an element identical to the input element.
It would be useful to be able to do the opposite :

Search 1D Array : be able to search a different element

a new function or ...

the current function with an option to select : "the same element", or "a different element".

and why not (It would be also useful) an additional output with this different element.

TDMS Flush Time Based

When I am writing to a TDMS file I'm not actually writing to a file on disk. The TDMS Write function has some buffering and will only write to disk when the buffer is full which is convenient. You can even set this buffer size so that you can control how often it flushs.

During testing I want to make sure data is being flushed to disk at a minimum of some rate. Say I want to flush to disk every 5 minutes so if there is a power outage I only lose my last 5 minutes of data at most and not the whole day the test was running. I can try to find the buffer size that represents 5 minutes of data, but what I end up doing is write code that checks a timer and every 5 minutes perform a flush.

But what I think would be a useful feature is to have another property similar to setting the buffer size, and instead of setting the number of data points to be in the buffer to cause a flush, instead set an amount of time to elapse before performing a flush.

LabVIEW Idea Exchange

Path Type function should return a U16 and not an I16

To Ensure readability - Remove bundle and Unbundle from function palette ??

String/Time Stamp Conversion

Allow graph rescaling and real-time updates in the "Profile buffer allocations" window

Close build window when done

stop messing up format of new type def

Catch Web Service Session Timeout Event

Allow Dimension Selection on Auto-Indexing Tunnels for nD Arrays

system exec in French and other language with accents

Stop using IMAQ Create VI

Dynamically Update color of Wire for Errors [ Debugging mode ]

improved LinkedInputTunnel option

Debugging a specific loop in code with multiple loops

Using LabView programs with the Google Chrome OS

Parallel inspections in Vision Builder

LABVIEW native way to Generate a list of User DB Stored _Procedures (any ADODB Compliant db)

Create Another Version of the LabVIEW Run-Time Engine That Contains All Dependencies (vi.lib, etc).

Search for a different element

TDMS Flush Time Based

New in-place element structure option - class property node read/write - to ensure access to parent node private data is done in-place