Additional NI Software Idea Exchange

When adding a Licensing server especially from FlexLM there is no confirmation message that a valid server has been added. This would be nice to avoid confusion of users connecting to this type of licensing Server.

NI License Manager is a really good tool to check in a visual way in which products are licensed and connecting to the Server License.

However, in case you need to request access from NI License Manager to the server through the "Manage" button on the Network License tab, you need to go specifically to each machine physically or set up a remote third party tool to request the access with that button.

Therefore, it will be a great solution to create certain options for the NI License Manager and set up some Master License Managers to make these requests from a few selected computers. Adding value to the security of the server as it will not be accessed very often.

Thanks.

Add option to Project Explorer->Tools->Options->Workspace for UI Manager and Workspace:

• Close on Undeploy [to automatically close one or both when project is undeployed]
• Open on Deploy [select whether to open or not on deployment - after Calibration is complete, I do not use Workspace again and would prefer that it would not open on future deployments.  I can open it manually from the Project Explorer window, if necessary.

Just want to share a calibration proposal for VNA.

Please note: this is just for one model Filter IC production test, different models or different ICs test may have different calibration approach.

Below is the calibration proposal flowchart:

When migrating to a new server with an updated license File I loaded a large backup files from a server with a 1000+Computer based licenses. The process of loading the back up took around 1 hour, which got me unsure if the process of restoring the backup was going correctly or not. It doesn't has a loading progression bar to see how much time left is needed for the backup to finish, or even just a progression bar of the percentage left. In the end the process was successful, but very stressing... I think having a progression bar would be an excellent feature to have.

Dear Colleagues,

customers need for directly importing the NI Veristand log files into third-party tools (as Vector CANanalyzer) and we found the following contrains:

- TDMS are very effective and open, but not directly manageable by other tools

- txt and cvs are potentially more suitable, but NI Veristand 2019 does not allow adding a native Time Channel, that's fundamental. I saw that System Time and Absolute Time are potential channels to add to a log, but there are no options to format the timestamp and to allow some kind of flexibility

Suggestion/requests:

- adding customizable time channels to txt and csv log options in NI Veristand (the limitation is still the files size bacause of ascii, but the multiple files option could help)

- whatever improvement are in the NI VS roamap logging?

- what about MDF4 support? It would be vey useful and well accepted: I recall it was in the roadmap evaluation but no news so far. In case, what MDF: signal and/or message format(s), BTW?

In case, concerning the roadmap, could you please contact me directly (davide.palandella@ni.com)?

Thank you very much

Best Regards

Currently error messages are quite vague - they say what failed, but don't say where. It might be fine in LabVIEW development, where error pops up in the exact location on the block diagram, but it's not well suited for Veristand, where all we have is the error message. Take this as an example:

I'm trying since 2 days to figure out which property is invalid - I have 4 CAN channels and 2 LIN channels in the SDF... If there was an information about the channel/value that causes the error, it'd be far easier to sort the problem out.

Aside from the fact that most of the errors are just pulled up from device drivers which makes them vague and not at all related to the actual VeriStand function happens (so part 1 of this feature request is an overhaul of our error reporting in VeriStand), it would be great if it actually logged these or gave you the option to save to a file. This means that you can then send this to NI Support for assistance or at the very least, document issues.

It would be great if you could write to a whole digital port rather than line by line when attempting to write numerics over digital lines with VeriStand DAQmx