LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Caution - LabVIEW 2019 VISA Runtime Engine is not available yet

Solved!
Go to solution
Highlighted

For those of you developing in 2019 version that depends on VISA platform. Be aware that NI hasn't released the 2019 VISA run time installer yet which can be installed offline. This will be a problem only if you release your software as EXE. Instead you can release it as an installer so that the installer will grab the necessary drivers and add-ons and install it (granted you have admin access) to support your application.

 

Meanwhile I do not think there is any other workaround for now. So keep working on 2018 version until you are absolutely sure that you will be able to download and install all other required add-ons for the latest version (especially if you do not have admin access) to the systems.

 

Also I am certain that installing any drivers of NI requires admin rights by default. You application can be used on a user profile but all the underlying drivers needs to be done with admin privileges. Especially since it will change your REGISTRY.

 

If anyone has any other alternatives. Please do suggest.

NI System Configuration:
- NI PXIe-1071, 4-Slot 3U PXI Express Chassis , 1 GB/Slot throughput, Part Number: 781368-01
- NI PXIe-PCIe8381,x8 Gen2 MXI-Express for PXI Express Interface,3m, Part Number: 782522-01
- PXIe-5160 PXI Oscilloscope, 500 MHz, 10 bits, 2.5 GS/s, 2 Channels, 64 MB, Part Number: 782621-01
- Astronics PXIe-1209 2-Channel, 100 MHz PXI Pulse Generator, Part Number: 785033-01
Message 1 of 29
(379 Views)
Solution
Accepted by topic author asukumari

I posted about the DAQmx runtime here, but it's the same conclusion you've found (build it yourself into an installer):

 

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z00000159txSAA&l=en-US

 

I hope this isn't the way forward, and DAQmx / VISA runtimes will continue to be published as separate, offline installers.




Certified LabVIEW Architect
Unless otherwise stated, all code snippets and examples provided
by me are "as is", and are free to use and modify without attribution.
0 Kudos
Message 2 of 29
(330 Views)
Yes I hope NI releases them as offline installers as well.
NI System Configuration:
- NI PXIe-1071, 4-Slot 3U PXI Express Chassis , 1 GB/Slot throughput, Part Number: 781368-01
- NI PXIe-PCIe8381,x8 Gen2 MXI-Express for PXI Express Interface,3m, Part Number: 782522-01
- PXIe-5160 PXI Oscilloscope, 500 MHz, 10 bits, 2.5 GS/s, 2 Channels, 64 MB, Part Number: 782621-01
- Astronics PXIe-1209 2-Channel, 100 MHz PXI Pulse Generator, Part Number: 785033-01
0 Kudos
Message 3 of 29
(307 Views)
Is there a way to get notified if NI releases these 2019 run time engines?
NI System Configuration:
- NI PXIe-1071, 4-Slot 3U PXI Express Chassis , 1 GB/Slot throughput, Part Number: 781368-01
- NI PXIe-PCIe8381,x8 Gen2 MXI-Express for PXI Express Interface,3m, Part Number: 782522-01
- PXIe-5160 PXI Oscilloscope, 500 MHz, 10 bits, 2.5 GS/s, 2 Channels, 64 MB, Part Number: 782621-01
- Astronics PXIe-1209 2-Channel, 100 MHz PXI Pulse Generator, Part Number: 785033-01
Message 4 of 29
(307 Views)

Any news on this? I see the NI-VISA installer but no Runtime installer. My .EXE is <9MB, I hope NI doesn't expect us to bundle a 993MB installer with each update......

 

EDIT: There is an update here, but it looks like it will only help if the PC in question has web access...

https://forums.ni.com/t5/Instrument-Control-GPIB-Serial/VISA-runtime-download-link/m-p/3955967/highl...

0 Kudos
Message 5 of 29
(191 Views)

Well you only need an "installer" for the initial installation to also install all of the dependencies like NI-VISA, NI-488.2, etc.

 

Once your target system has the runtime dependencies installed any updates to your LabVIEW executable should only require replacing the executable itself. You shouldn't need new runtime packages.

 

Unless of course you upgraded LabVIEW versions

-------------------------------------------------------------------
Unfortunately, most readers of this Forum, including some real Experts, have not mastered the skill of being able to read the code that Posters fail to post. If we cannot see "what you did wrong", we are unable to tell you how to fix it. (Bob Schor 28 August 2018)
0 Kudos
Message 6 of 29
(142 Views)

@RTSLVU wrote:

Well you only need an "installer" for the initial installation to also install all of the dependencies like NI-VISA, NI-488.2, etc.

 

Once your target system has the runtime dependencies installed any updates to your LabVIEW executable should only require replacing the executable itself. You shouldn't need new runtime packages.

 

Unless of course you upgraded LabVIEW versions


Agreed. But when we have a PC fail in the field, we need to send out the runtimes.

 

Also, I've seen NI multiple times recommend to build an installer package with the runtimes and executables all-in-one; I can't see any scenario where it make sense to do this unless you never plan to update the EXE...

0 Kudos
Message 7 of 29
(137 Views)

@iannicholson wrote:


Agreed. But when we have a PC fail in the field, we need to send out the runtimes.

 


Sure but in that case it would be a fresh install, so an "Installer" would be the best way to insure all of the dependencies were installed. 

-------------------------------------------------------------------
Unfortunately, most readers of this Forum, including some real Experts, have not mastered the skill of being able to read the code that Posters fail to post. If we cannot see "what you did wrong", we are unable to tell you how to fix it. (Bob Schor 28 August 2018)
0 Kudos
Message 8 of 29
(134 Views)

So I should be building a bare installer and a full installer with each EXE update? Sometimes I build 8 or 10 updates in a day! Seems like a lot of extra packaging for something that's rarely needed (but very important when it is).

0 Kudos
Message 9 of 29
(131 Views)

@iannicholson wrote:

So I should be building a bare installer and a full installer with each EXE update? Sometimes I build 8 or 10 updates in a day! Seems like a lot of extra packaging for something that's rarely needed (but very important when it is).


Again, no need to build an installer unless you are deploying to a new target that has none of the dependencies already installed. 

OR you updated LabVIEW or one of the dependencies (like NI-VISA) to a new version.

 

BTW: This is why I still have LabVIEW 2014, 2015, 2016 still installed on my development system. If I need to update something written in LV 2015 I use LV 2015. I don't upgrade everything to every new LV version that comes out, I don't have time for that.

 

-------------------------------------------------------------------
Unfortunately, most readers of this Forum, including some real Experts, have not mastered the skill of being able to read the code that Posters fail to post. If we cannot see "what you did wrong", we are unable to tell you how to fix it. (Bob Schor 28 August 2018)
0 Kudos
Message 10 of 29
(116 Views)