annulla
Visualizzazione dei risultati per 
Cerca invece 
Intendevi dire: 

instrument drivers

when I try to download instrument driver from ni instrument driver finder ,I encountred this error 

"" exists.

The destination folder for this instrument driver already exists. Click "Install" to continue the installation and overwrite any existing files. Click "Cancel" to abort this installation.

Can smeone help me 😉 

Thanks in advance

Messaggio 1 di 11
4.076Visualizzazioni

Hi Meriem,

 


@Meriem2610 wrote:

when I try to download instrument driver

 

The destination folder for this instrument driver already exists. Click "Install" to continue the installation and overwrite any existing files.


Which steps are between "try to download" and "Click Install"?

How does your error message fit to the downloading process???

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Messaggio 2 di 11
4.038Visualizzazioni

thanks for your reply 🙂 

Meriem2610_2-1623234422478.png

 

I search for the instrument 

Meriem2610_1-1623234340863.png

 

when I choose the instrument and click Install 

Meriem2610_0-1623234292869.png

I face this error ! 😕 

 

Messaggio 3 di 11
4.031Visualizzazioni

Hi Meriem,

 

when I hear "instrument driver download" then I think of the InstrumentDriverNetwork (ni.com/idnet): here you can download any device drivers from the NI website.

When you cannot install that driver due to the shown error you might try to download the driver package from the website and try to install that package!

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Messaggio 4 di 11
4.020Visualizzazioni

Hi GerdW, 

you mean I try to download the driver from IDnet for exapmle ?

 the problem that when I change the pc I encountered this error 😕 before I could download any driver that's why I m triying to resolve this error ..

Best regards,

0 Kudos
Messaggio 5 di 11
4.017Visualizzazioni

I'm facing this exact same issue with a new installation of Labview 2020.

In fact, I manually installed the drivers I wanted first, but the installation doesn't recognize them.

phota_1-1625012685418.png phota_0-1625012844588.png

 

Trying to install the new drivers (whether I have removed the manual driver directories or not) results in the same error message.

phota_0-1625012611365.png

Cheers,

Matt

0 Kudos
Messaggio 6 di 11
3.860Visualizzazioni

The best ways to get LabVIEW instrument drivers are in this order

 

  1. Go to the instrument manufacturers website and search for them
  2. Go to the NI Instrument Driver Network (IDNet)  and search for them
  3. Ask on the LabVIEW Support Board if anyone has made a "driver"
  4. Break out the instrument's programming manual and write your own
========================
=== Engineer Ambiguously ===
========================
0 Kudos
Messaggio 7 di 11
3.830Visualizzazioni

That is a shame. I installed LV 2020 on a different computer and cannot install any drivers. A different bug was in 2017. Thinking of it, 2015 was the last version that had no bugs when installing the instrument drivers.

And without the drivers I have no way of using the exciting labview.

Oh well - one more reason to use Python...

0 Kudos
Messaggio 8 di 11
3.670Visualizzazioni

@ncherkasov wrote:

That is a shame. I installed LV 2020 on a different computer and cannot install any drivers. A different bug was in 2017. Thinking of it, 2015 was the last version that had no bugs when installing the instrument drivers.

And without the drivers I have no way of using the exciting labview.

Oh well - one more reason to use Python...


Well you know most LabVIEW Instrument "Drivers" are nothing more than a set of VI's that someone else wrote using the instruments SCPI commands.

 

If you can use SCPI commands in Python, then you can write your own LabVIEW "drivers".

 

Or you can just use VISA Write and SCPI commands, pretty much exactly as you would in Python.

========================
=== Engineer Ambiguously ===
========================
0 Kudos
Messaggio 9 di 11
3.667Visualizzazioni

just had the same problem - the instr.lib folder under Program Files was set to read only for whatever reason.

0 Kudos
Messaggio 10 di 11
525Visualizzazioni