Benchtop Measurement and Test
Distributed Measurement and Control
Systems Engineering Software
Perspectives showcases how NI sees what’s next in the world of test and technology.
You can request repair, RMA, schedule calibration, or get technical support. A valid service agreement may be required.
Provides support for NI data acquisition and signal conditioning devices.
Provides support for Ethernet, GPIB, serial, USB, and other types of instruments.
Provides support for NI GPIB controllers and NI embedded controllers with GPIB ports.
I consider this idea complete by the introduction of Environments in 2016:
Why restrict to load the type pallets always from <user or NI>…Components\TypePalettes folder?
It will be very helpful I can configure my path to the load my custom type pallets, this will resolve the issue handling different type Palettes for different customers / projects / sequences.
Or even better, if given the option to associate the type pallet to sequence files / sequence model. Just like Edit -> Sequence File Properties -> Model Option -> Require specific model.
It would be nice to be able to associate type files with a project, (at least to the level that associating the type file with the project made it so that types file loaded into the types palette when that project was open, and double-clicking on the types file opened it in the types editor instead of notepad).
I think that requiring specific types files to be loaded in memory to **EDIT** a sequence file could be beneficial towards preventing type viruses, but I do NOT think it is good to require them to be loaded to execute a file. (associating types files to a sequence file could definitely help with this)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What do you need our team of experts to assist you with?
We'll be in touch soon!