LabVIEW Idea Exchange

Currently the "Bytes at port" property only applies to serial ports. If you are trying to write a generic driver or communications package that supports multiple connection types you cannot use the "bytes at port" since it will not work for anything but a serial connection. There is a related idea here which proposes the "Bytes at port" can be added to the event structure. It also suggests that this be expanded to other connection types. My idea suggests that at a minimum the VISA property node can be expanded.

This would be useful for variables whose value is not yet available at deployment time, and is filled later by some process.

Currently (LV2017.1f3), it is not even possible to input a non-numeric value in the inital value page in the variable editor. Attempting to do it programmatically like this:

produces a LabVIEW:  (Hex 0x8BBB0018) Invalid float value.

Whereas, blindly editing the lvlib file to 

<Property Name="Initial Value:Value" Type="Str">NaN</Property>

produces a "deployment failed (error: -1950678996, LabVIEW:  The variable configuration is invalid.  Edit the variable properties to correct the configuration.)." at deploy time.

'Database Variant To Data' cannot be placed in an inline enabled VI making it impossible to use in malleable VIs. 

It would be nice to be able to draw on the power of the 'Database Variant To Data' VI in malleable VIs so we could be more flexible when writing database related code.

Please make this possible or offer a workaround (like the polymorphic instances of the VI).

Hi,

This is not really specific to LabVIEW but I can find where to put this idea...

It will be nice to have a function to the dump the value of all shared variables (at least those of standard types) from a target into a file. 

It will really help debugging applications as we can ask customers to dump the values and send us the file when they report bugs.  Most of the time, they have restarted the application and we lost important information for debugging.