When using VeriStand with Source Control SW paths for Real-Time Sequences in the Stimulus Profile Editor need to be customized on every check out because it’s not possible to use a relative path for a Real-Time Sequence in a Stimulus Profile Editor.
Even if the Real-Time Sequence is in the same folder like a Stimulus Profile itself it isn’t found and the path has to be be adjusted.
So it would be awesome if it would be possible in VeriStand 2017 to use relative paths for a Real-Time Sequences in a Stimulus Profile Editor.
We have dozens are targets that are deployed to by an automated system depending on test cases being run. However, we have no API (short of building our own system) to retreive what system definition a target is currently running. This would help us improve our test case speed by only deploying when needed, and also improve configuration management and traceability.
Currently the entire realtime sequence must be set to stop execution on fail or not. It would be better to allow each realtime sequence call the ability to generate an error message on fail and then allow the user to define if the appropriate action would be to notify only and continue, notify and give option to continue or abort, or to abort on fail and notify.
This attached file is a picture that shows the outcome of current drag and drop UI setup (above the box), and the desired drag and drop UI setup (below the box).
As you can see above the box, when I drag and drop each channel that a user could select for a single digital output, the controls are numerics by default. It would be quite tedious for a user to drag and drop each required channel, and then interpret the channel's function based on its name alone. Below the box, I right clicked a channel from the tree, and then selected a control based on the datatype that makes sense with respect to the channel's function. It makes sense that the controls are numerics by default because in the Set Channel Value.vi (part of Custom Device API library), the only accepted datatype is Double. However, it would be nice to be able to set a channel's datatype in a custom device's configuration VI. Channel, folder, and device properties can be set using a polymorphic VI that supports many data types. I propose that channel values could be handled in a similar way. Then in the VeriStand UI, when a channel is drag and dropped from the system definition tree, it could be recognized as Boolean, ring, numeric, etc...
Further desireable functionality would include a custom control which would allow the user to drag a single channel from the system definition tree. The custom control would be composed of multiple programmer-defined controls whose data would be passed to the driver in a cluster since there could be multiple datatypes. Using the attached file as a visual example, the custom control would programatically update its appearance based on the desired output mode (discrete, PWM, or encoder).
OK, I admit that I find keyboards a useful input device. And I like to keep my fingers on the keys instead of switching back and forth to the mouse.
This said, I should appreciate when I can use the <tab> key to navigate through dialogs. Such as the scaling dialog in MAX: If I mouse click into unscaled max, I can tab my way through unscaled min - scaled max, scaled min. But -Lord forbid! - not into scaled unit! why not? wouldn't this be the most natural dialog box behaviour? To be able to tab through all fields of interest? Given that LV has a great tool to select and organize tabbing behaviour of user interfaces - why have all MAX dialogs escaped this small improvement ever since (as far as my knowledge goes back to MAX 1.0)
Please give some programmer this half an hour and let him improve this detail.
Hello, I would like to suggest implementing software tools in which to objectively calcuiate audio/speech quality based on the industry standards (i.e. Perceptual Evaluation of Audio Quality (PEAQ), Telecommunication Objective Speech Quality Assessment (TOSQA) and Perceptual Speech Quality Measure (PSQM))
I've been working with LabVIEW for about 3 years, on the same PC.
All the time I've installed all the NI-Updates.
This time the LV 2016 update couldn’t be done, because of lack of memory space on my PC. I’ve deleted a lot of data, but 48 GB (!!!) still weren’t enough.
Then I’ve made an EXCITING DISCOVERY.
In the directory C:\ProgramData\National Instruments\Update Service\Installers there are several older (up to 2013) folders. Overall data volume of these was 131 GB! This is a half of my hard drive!!!
Why didn’t NI-Updater suggested to remove these old data before I have started to remove some MBs of my old documents?!! Is the data really essential for NI-SW? Is there ANY need for this data on my PC?
I’m really embarrassed by this issue. To overload clients PCs with such a trash data is not a good approach!
And regarding LabVIEW-Updates, I think the installer should ask the user if he/she wants to keep the old version of LV instead of always keeping it on PC.
What is the point on keeping the old version of LabVIEW anyway? Once opened with a new version, no VI can be opened with the older one.
I love being able to simulate DAQ hardware and write the program before ever connecting the hardware to actual instruments, but the default waveform that is generated from a simulated device is not always a great representation of the expected signal of the actual hardware. Right now I have to program in a way to select between signals from the simulated DAQ device using DAQmx Read or a Simulated Signal express VI. It would be great if the Simulated Signal express VI was built into MAX so that the signal from each simulated DAQ device could be modified from Max. This would simplify the LabVIEW code needed and allow me to easily test the code.
It would be extremely usefull and would save lots of frustration if the Veristand Sequence Editor (and all of verstiand for that matter) had undo and redo functions. It is surprizing that software of this caliber does not have such a basic function. I posted this in the main veristand forum and wanted to also make sure it made it into the Idea Exchange.
it would be a good feature, if it'll be possible to see directly in NI License Manager list of licenses, and expiration dates - all at once. If it'll be possilbe to export it, it would be really great, because then you can sort them, check what will expire first, and so on.
Because when sometimes we use trial keys for toolkits, activated at different time - it's a mess, because one needs somehow to track when trial license will expire, and when you need to ask for new one / to purchase final license, and so on...
It is very helpful if the expired signal of watchdog timer can be routed in the system as PXI Trigger, and so on. Users can use this function easily to increase reliability of their system without creating a Custom Device.
In certain circumstances it would be helpful to see exactly what license file ties to each piece of activated software within NI License Manager. This would be an additional field in the right hand pane of License Manager as shown below.
The Embeded Data Logger and Waveform Data Logger could have some sort of array (either two 1D array or one 2D array) allowing to create custom parameters to the TDMS file. The array could be defined in the SDF or during operation using a LabVIEW VI to pass data to it.