Installation Automatique driver HID VISA

Bonjour,
Un wizard labview permet de créer un drivers VISA à partir d'un driver HID propriétaire
http://www.ni.com/white-paper/4478/fr
Nous avons réalise des modules de communication à partir de microcontroleur PIC Microchip en utilisant la fonction USB HID.
Nous disposons d'une vingtaine de module connecté sur des HUB sur un PC.
Une fois connecté, Windows XP les détecte comme interface HID standard. Nous devons re-installer les drivers de tous les modules un par un.
Et si jamais, nous changeons de port de connections sur le PC pour la liaison avec les HUB, nous devons tout recommencer.
Il y a t-il une procédure afin que windows installe directement le driver HID propriétaire VISA de labview ?
Ou un utilitaire que le permettrait
Merci

Recharger le pilote , comme expliqué dans le wizard :
http://www.ni.com/white-paper/4478/fr partie : 2.2. Installation des fichiers INF et du matériel USB
- Aller dans le panneau de configuration ,
- Icone Systeme
- Onglet Materiel,
- Gestionnaire de peripherique
- Retrouver mon materiel parmis tous les peripheriques HID
- Clic de droit, mettre à jour le pilote, avec le drivers VISA de mon peripherique.
Bref pas tres pratique .....
De plus, j'ai une dizaine de ressources identiques branchées sur un Hub USB, je dois faire cette manip, pour les 10 ressources , alors qu'elles utilisent toutes le meme drivers VISA.

Similar Messages

HT203242 I've tried all of the suggested solutions, but I still can't get my cd drive recognised. If I delete the driver and rebot, the cd drive appears, but as soon as the driver automatically installs, the driver disappears into the Q: drive

I've tried all of the suggested solutions, but I still can't get my cd drive recognised on my laptop. If I delete the driver and reboot, the cd drive appears, but as soon as the driver automatically installs, the driver disappears into the Q: drive, which is not accessible and neither is the CD drive

I had the same or similar problem after installin iTunes 11 on my Acer Laptop with Vista. The new iTunes ran but I
completely lost access to my CdRom/DVD drive. Error Code 19 was displayed in Windows Device Manager. Found out
this is more widespread of a problem than expected. After trying several forum recommended fixes, the Only thing that gave me back my CdRom drive was doing a Windows Restore to a date prior to iTunes 11 install. I got my drive back but it also restored me to the prior 10.0.7.21 vers of iTunes which no longer worked due to missing files. iTunes help
recommended a Reinstall. I am reluctant to do that for several reason. That's where I am at for now until I find out if there are any other risks for using iTunes 11 vs. Registry Errors vs. Losing access to my CdRom drive. Brad

Issue regarding Thin Installer and driver packages

Hello everybody,
I have recently started to work for a new company and have been tasked with creating a new Windows deployment solution.
My company are using Lenovo desktop and laptop and my installation image use Thin Installer to deploy drivers to our workstations during Windows deployment.
I have been having some difficulties getting everything to work and I want to write about it here to hopefully help someone in the same situation as me and call out for better quality control at Lenovo.
Here are the command line I call to start Thin Installer from the local computer:
START /WAIT thininstaller.exe /CM -search A -action INSTALL -repository \\wds\lenovo -noicon -showprogress -IncludeRebootPackages 1,3,4 -noreboot
Hers the issues I have expirienced:
1. Sometimes packages downloaded with Update Retriever will be set to "Reboot type: Forces a reboot" as default. This causes the Thin Installer to reboot reguardless of the -noreboot switch.
Its possible to change reboot type "Requires a reboot" in Update Retriever and than the updates installs fine.
This causes problem with scripted installs where you cannot have the system reboot "out of order".
Updates should never be default "forces a reboot".
2. On my Thinkcenter e93z (10B8) the Intel Displaydriver (v 9.18.10.3220) wont install because the PnPID is not listed in the XML file. (my PnPID is VEN_8086&DEV_041E&SUBSYS_309C17AA (309D17AA is listed tho)). Manualy editing the XML files to include my PnPID solves the problem.
Lenovo should really have better qualitycontrol here.
3. On a t440s machine i have the Synaptics UltraNav Driver (v. 17.0.12.60) wont install automatically with Thin Installer.
This is because the machine i installed failed the "BIOS test" in the XML file of the update package. I manually edited the XML file and replaced the "BIOS TEST" with one from another update that worked on that system and now everything installs automatically and works fine.
Its possible that Lenovo has detected some kind of problem with my BIOS version and the Synaptics driver but everything seems to work fine for me.
I hope this post will help someone in the future
EDIT: Other people have called out some problems with the information provied in this post. You should read the whole thread before making any changes to your systems.
Kind Regards,
2bi

2bi,
Thanks for posting your findings. I will investigate and escalate the missing PnP id issue for the Display Driver issue. We absolutely need to avoid these kinds of escapes.
For you ThinInstaller command line I would recommend not using the -showprogress parameter if you are using in a scripted deployment scenario with something like MDT and/or SCCM. These solutions typically will not allow TI to interact with the desktop during deployment which is what -showprogress will cause.
Also, you are telling TI to include packages that will automatically reboot your system (type 1), requires a reboot which can be delayed (type 3), will shutdown the machine automatically (type 4). We have very few type 4 packages anymore; however we definitely have type 1 and type 3. As sclexman mentioned, the -noreboot will only apply to the type 3 packages which leave the execution of the reboot up to TI. So -noreboot tells TI that even if it installs updates of type 3, it should not reboot when finished.
Changing the Reboot Type value in Update Retriever only changes how TI sees the package and does not alter how the package itself executes. So if a package is designed to always automatically reboot, changing it to type 3 in UR will have no affect. We have recently had a display driver released by Intel that will automatically reboot if the driver installer detects that it is upgrading an older version of the driver. In a clean deployment scenario, the automatic reboot will not happen so in this case it is safe to change the type to type 3.
This leads to another point. All of our content that is available through Update Retriever is also intended for consumption by System Update which is the utility aimed at individual consumers to help them keep their drivers up to date. Therefore this becomes our lowest common denominator that we have to support. This leads to situations that may not be ideal for the deployment scenario. If we had an army of resources we might be able to manage all of our content for both consumers and enterprise deployments; in effect doubling our efforts. Unfortunately this is not the case and we are trying to do the best we can.
Regarding the UltraNav update for T440s, I see that the XML has a _BIOS section under the Dependencies. However it is defined such that any BIOS level will work because the first level listed is a wildcard asterisk (*). This BIOS section is actually included for a completely different solution which also uses the XML. It is not intended to control the targeting of the update for System Update or Thin Installer. Perhaps there was a mistake made initially and the XML was released without the * and has since been fixed.
(from the current UltraNav driver package: )
<_Bios>
<Level>*</Level>
<Level>GGET*</Level>
<Level>GFET*</Level>
<Level>GHET*</Level>
<Level>GIET*</Level>
<Level>GJET*</Level>
<Level>GLET*</Level>
<Level>GMET*</Level>
<Level>GNET*</Level>
<Level>GRET*</Level>
</_Bios>

Erreur après l'installation du driver NICAN 2.1.3

Apres l'installation du driver NICAN 2.1.3 pour carte NI serie 1 PCI, j'ai un message d'erreur au reboot :
J'ai le message : "Une erreur s'est produite lors de l'installation du périphérique
Le fichier spécifié est introuvable "
Si je clique sur OK, l'installation automatique du périphérique recommence et échoue à nouveau et ainsi de suite indéfiniment.
Par contre, la carte NI fonctionne correctement avec mes applications et le self test sous MAX fonctionne correctement également.
Comment résoudre ce problème d'installation ?

Ne vous embêtez plus pour trouver la réponse, je l'ai eu sur un autre post et je vous la colle ci dessous :
"This sounds like a registry problem. Some times a deinstallation or upgrade of NI drivers deletes a special registry key called RunOnce.
The result is the problem you wrote about.
Check in your registry for the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\RunOnce
If you could not find the RunOnce key, you have to create this one.
good luck"
Autrement, j'ai résolu le problème tout seul en faisant une mise à jour de mon windows 2000 ce qui a je suppose réparé mon installation.

While installing Acrobat XI Pro, the installation automatically rolls back and I get the message "The wizard was interrupted before Adobe Acrobat XI Pro (11.0.07) could be completely installed. Your system has not been modified. To complete installation a

While installing Acrobat XI Pro, the installation automatically rolls back and I get the message "The wizard was interrupted before Adobe Acrobat XI Pro (11.0.07) could be completely installed. Your system has not been modified. To complete installation at another time, please run setup again." How to resolve it.
How do I modify the system.

Hi Rgardezi,
The only reason why Acrobat installation fails and throw this error message is when there are some services running in the background causing the installer not to complete the installation. My take is try the following steps and suggest if you were able to install the products or not :
1) Navigate to control panel and confirm that there is no line Item that talks about Acrobat. If you see Acrobat XI listed there, please remove them.
2) Perform a selective Start up using the steps mentioned in this link.
Please suggest if the above mentioned steps were able to resolve the query for you or not.
Cheers,
Kartikay Sharma

HT4407 When installing Windows 7 using Bootcamp, I get message: "Need 64-bit Windows Installation USB drive or DVD." I thought my install disk was for 32 or 64 bit. What does this mean?

When Installing Windows 7 using Bootcamp, I get message: "Need 64 bit Windows installation USB drive or DVD." What does this mean?

It means you need the 64 bit Version of Windows on a USB stick or DVD.

Make the installer for my executable run the DAqcarddriver and runtime engine installer automatically

*Hi
I would like to know how to make the installer for my executable run the DAqcarddriver and runtime engine installer automatically
I would like to include run time engine and the drivers of my daqcard(AI16XE50),( and maybe Ni daq or anything else needed?) in order to make my application portable for other computers on OS win98 and winXP .
How can I do that
thank you in advance
Olivier

Olivier,
What version of LabVIEW are you using to build your application? On a remote computer you should only need the drivers you are using and the Run-Time Engine. You can attach installers to LabVIEW 8 installers, but for previous versions you will have to add it by opening the installer configuration page, configuring your installer and then configure the Advanced properties. This will allow you to attach a EXE to the installer which you can run. Also depending on the version of LabVIEW will affect the OS version that you will be able to install the RTE on. LabVIEW 7.0 is the last version that can be installed on Windows 98.
Please let me know if you have any further questions and please include the version of LabVIEW you are using. Thanks!
Andy F.
National Instruments

E-73 Automatic driver install any option?

Is there any option for automatic driver install in desktop or laptop, If it is exists please inform me.

Good day.
ThinkCentre systems are supported by ThinkVantage System Update, which can be downloaded from your support pages: http://support.lenovo.com/us/en/products/desktops-and-all-in-ones/thinkcentre-e-series-desktops/thin...
It should do a decent job of recommending available driver updates for your system. If it doesn't catch a few things, you should be able to find them in the master list linked above. One thing that I do not let TVSU do is BIOS updates. When I decide to do those, I do them completely separately as a single task.
Hope this helps.
Regards.
English Community Deutsche Community Comunidad en Español Русскоязычное Сообщество
Community Resources: Participation Rules • Images in posts • Search (Advanced) • Private Messaging
PM requests for individual support are not answered. If a post solves your issue, please mark it so.
X1C3 Helix X220 X301 X200T T61p T60p Y3P • T520 T420 T510 T400 R400 T61 Y2P Y13
I am not a Lenovo employee.

How do I change where reader installs, ie drive/dir

how do I change where reader installs, ie drive/dir
it won't install cause it thinks it is installing on a network dive that no longer exists

I think this is not about the install drive, but one of your other folders. Commonly MY PICTURES is moved to an external drive. (You can check this).

I make RAW USB driver by VISA i'm stuck in MAX detect my device

according to USB Instrument Control Tutorial i'm trying to make a driver by VISA
NI-MAX doesn't detect my device and i stuck here please help me

It is often a big mistake to try and create your own driver. What is the device? Did the vendor not provide a driver for you to use? How does the device appear in windows device manager?

During installation of the NI-VISA 2.01 driver I get an error that tells me that my file (NICVISA.DPT) doesnt look like a tar archive. How can I make it look like a tar archive or is that not the solution to the problem?

I am trying to install the NI-VISA 2.01 driver I downloaded from the NI website on a HP-UX 10.2 platform, but it keeps giving me the following error:
tar: /var/spool/sw/NICVISA.DPT: This doesnt look like a tar archive.
I also get errors telling me that files can't be loaded because their missing from source media. What could be causing this? Some of the files are msgrt4.txt,ni7seg24.bdf,ni7seg26, etc... Can these needed files be downloaded anywhere or is the problem linked to the tar archive scenario..

The files were corrupt. Originally I had downloaded the driver files to my PC and used FTP to transfer them to my UNIX machine.
Your tech support rep. suggested I download the driver files via ftp.ni.com to my UNIX machine vs. the PC...this worked great. I am now communicating with my instrument

Creating Runtime Installer for VI with VISA Read VI

Greetings Fellow Users,
Please let me know which 'ADDITIONAL INSTALLERS' the LabView RunTime engine requires in order to run a VI that reads from the built-in serial port (COM 1) of a Windows XP PC. For instance, I include LabView Run-Time engine 8.0.1 to creat an installer for the VI. If I want to load and run this .exe on a PC that has no other NI software, do I need to include any of the following as 'ADDITIONAL INSTALLERS':
->NI-SERIAL 1.8?
->NI-VISA RUNTIME 3.4?
->NI-DAQmx 8.0?
What does the NI-VISA RUNTIME do anyways? Also, when I do include some of these, I have to dig out my LanVIEW installations CDs and they are loaded from teh D:\. What is the cleanest way to load these onto my HDD so that LabView will select these automatically.
Thank you.

FLT CTRL 6 wrote:
Greetings Fellow Users,
Please let me know which 'ADDITIONAL INSTALLERS' the LabView
RunTime engine requires in order to run a VI that reads from the
built-in serial port (COM 1) of a Windows XP PC. For instance,
I include LabView Run-Time engine 8.0.1 to creat an installer
for the VI. If I want to load and run this .exe on a PC that has
no other NI software, do I need to include any of the following as
'ADDITIONAL INSTALLERS':
->NI-SERIAL 1.8?
->NI-VISA RUNTIME 3.4?
->NI-DAQmx 8.0?
What does the NI-VISA RUNTIME do anyways? Also, when I do
include some of these, I have to dig out my LanVIEW installations CDs
and they are loaded from teh D:\. What is the cleanest way
to load these onto my HDD so that LabView will select these
automatically.
Thank you.
->NI-SERIAL 1.8?
This is the driver used for serial port controller boards and
interfaces from NI. You do not need that software when trying to access
built in serial ports or ports on interface cards from other
manufactureres than NI.
->NI-VISA RUNTIME 3.4?
This is the software LabVIEW uses to talk to all kinds of IO interfaces
including serial ports. This is what you will need. Runtime means it is
a stripped down version without LabVIEW, C, VB, Delphi and whatever
development bindings and examples etc.
->NI-DAQmx 8.0?
This is the software driver for NI data acquisition devices (analog IO, digital IO, counter , timers).
These are all to be considered drivers and (very maybe apart from
NI-VISA) it is usually not a very good idea to include drivers into the
application installer. If you use them your user is likely to have
bought his own kind of hardware and no matter if he happens to have
bougt the newest SuperPCI interface board with 256 ultra-high-speed
serial ports over wireless connections or an old standard PCI board
with 2 RS-232 interfaces they both will have come with a CD that is
appropriate for that device, whereas the NI-Serial driver you included
is only appropriate for NI serial boards that are still AND already
sold at the moment when that driver was released. The same applies for
any other driver software.
NI_VISA being able to connect to standard built-in serial ports could
be considered different but it isn't really. I have included NI-VISA on
application installers in the past only to find out that the included
NI-VISA version did not run or not run reliably on newer machines with
new OS versions, so we had to point the customer to the NI site to
download the newest version anyhow, or even burn a new CD with updated
NI-VISA versions and express ship it.
Basically including any kind of driver software in the application
installer may seem like a good idea but will usually cause lots of
additional support after some time due to incompatibilities with newer
OS versions, new hardware, etc.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Tektronix 3xx Driver: Missing VIs

After installing and starting the NI-Device-Driver-VI for Tektronix 3xx Devices, I get error messages due to missing VIs like "TKTDS Read.vi" or "TKTDS Start-Stop Acqui.vi". No dokumentation available with the driver. Working with LabVIEW 6.02.
Any idea?
C. Wennmacher

I downloaded the dktds3xx.zip file from NI's instrument driver download site. I unzipped the file and it created two llb's in two different folders. They were tktds3xx.llb and tktdsxxx.llb. The files you are missing are in the tktdsxxx.llb. To solve your problem you have a couple options.
1) When the VI prompts you for the location of the missing VIs just navigate to the llb and select the appropriate VI.
2) Better Way - Move both llb's into your instr.lib folder which is probably in your c:\Program Files\National Instruments\Labview 6 directory. The necessary VIs will automatically be found since this directory is automatically included in the VI search path.
Matt Kisler
Applications Engineer
National Instruments
http://www.ni.com/ask

Prevent Mountain Lions Installer Automatic Delete

I want to do a clean reinstall of Mountain Lion on my MacBook. I recently learned how to do it, yippee! However, in following the instructions that supposedly an 8 year old could follow, I hit a brick wall. I could not find the application/installer. I searched and searched banging my head in frustration. Then I discoverd that, after download, it is automatically deleted. Anyway, I apparently need to re-download the app from the app store. Is it that simple first? Second, how do I ensure it is not automatically deleted upon download. I hope that makes sense. It is my intent to first, make my current MacBook Pro back to original settings. Second, it is my intent to create a boot disk with a flash drive to install Mountain Lion on two other MacBooks (it is my understanding I can use it on up to 5 of my machines). Thanks in advance.

BigSky13 wrote:
Anyway, I apparently need to re-download the app from the app store. Is it that simple first?
Correct. As you purchased it in the past, you can download it as many times as you want for free, from App Store or starting into Recovery (pressing Command and R keys while your Mac is starting). If you want to download the installer, you have to download Mountain Lion from the App Store.
BigSky13 wrote:
Second, how do I ensure it is not automatically deleted upon download. I hope that makes sense. It is my intent to first, make my current MacBook Pro back to original settings.
It's only deleted when you upgrade OS X, but if you download the OS X Mountain Lion installer and you don't install it, you won't get it deleted
BigSky13 wrote:
Second, it is my intent to create a boot disk with a flash drive to install Mountain Lion on two other MacBooks (it is my understanding I can use it on up to 5 of my machines). Thanks in advance.
To do it, first download OS X Mountain Lion from the App Store. Then, use Lion Diskmaker to create the USB drive with Mountain Lion > http://liondiskmaker.com
You can upgrade to OS X Mountain Lion all your Macs without any problem, so you don't have to worry about paying OS X Mountain Lion again to install it in your other Macintoshes

Leopard installation hard drive issues

I recently bought a iBook G4 (2005 model) on eBay under the impression it was just missing an OS. Armed with a copy of Leopard (yes I bought it ) I tried to boot it up for the first time.
The first time I was faced with the Open Firmware screen, and errors that seemed consistnat with a faulty airport connection. I took it all apart and removed the airport card, then while booting I pressed Option to get the list of boot options. Booted to the Leopard DVD and after a disk check it seemed like it was working fine.
However just as it was about to begin the actual install process it cacked out with a massive Installation Failed! message. The install log said the error "Could not unmount" was to be blamed. Tried using the disk utility to verify the drives but it spent ages doing nothing. Repair wouldnt work and neither would erase, they gave me the same issue.
So that was it for the night. Gave up to try another day. Next morning trying to do the same thing after changing nothing, I was faced with the "You must restart your computer" message just after the language select screen on the install DVD. Why did this suddently change?
Took the harddrive out to check the connection was ok, seemed fine so put it back (didnt get the chance to plug it into my pc like I hoped, was missing the right adapter). Now with everything back in place, if I press Option on boot I dont even get a list of harddrives/cd drives anymore... just the two arrows and other than that a blank screen.
If I try to hold C while I boot to go straight to the disk then it shows the white loading page with the apple logo, but after an hour it hadnt moved on from there. The whole time the hard drive is making a loud clicking noise.
It seems each move I make I go backwards a little. Who has some suggestions that dont involve paying a spotty berk in the local shop $300 just so he can crack open Google, find this support post and fix it for me at a profit
I believe the HDD may be fried, but dont know how to check. It seemed to recognize it in the Disk Utility the time I got that far, but dont know why it no longer recognizes it.
Message was edited by: pjsturgeon

For us it was Versions cannot be switched off (decreases security). No "Save As" in many Apps, no Bounce in Mail. 10.7 felt “dumbed down” to us. We will try later, (10.8 maybe).
This is what we did in our office, from Kappy:
To switch from Lion to Snow Leopard:
1. Boot from your Snow Leopard Installer Disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu.
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Partition tab in the DU main window.
3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the partition scheme to GUID then click on the OK button. Click on the Partition button and wait until the process has completed.
4. Quit DU and return to the installer. Install Snow Leopard.
This will erase the whole drive so be sure to backup your files if you don't have a backup already. If you have performed a TM backup using Lion be aware that you cannot restore from that backup in Snow Leopard (see below.) I suggest you make a separate backup using Carbon Copy Cloner 3.4.1.
If you have Snow Leopard Time Machine backups, do a full system restore per #14 in Time Machine - Frequently Asked Questions. If you have subsequent backups from Lion, you can restore newer items selectively, via the "Star Wars" display, per #15 there, but be careful; some Snow Leopard apps may not work with the Lion files.

Installation Automatique driver HID VISA

Similar Messages

Maybe you are looking for