This device cannot start. (Code 10)

[kptsolutions]

Hi,

I am puzzled by this problem and hoped someone here could help me out.  I have a Microchip PICDEMFS development board that uses USB communication.  I have been writing code and interfacing with this board in Labview via the VISA instrument control.  I orgionally used the VISA driver wizard to create the .inf file and all has worked well.  However, we are moving the development to a new computer system and now get a windows (XP) error "This device cannot start. (Code 10)", when we try to install the PICDEMFS (PIC18F4550) device.  All of the hardware (cables, etc) were moved with the PICDEMFS board so nothing has changed.  As a sanity check, we backed out all of the Labview windows driver information and installed the PICDEMFS, with the Microchip .inf file and all worked well.  So we are back to why does this not work using the Labview VISA driver?  As an additionall (and important) note, on the previous system, the device was listed as a com port device (i.e COM6).  On the new system, the device is listed as NI-VISA USB Devices.  For reference, I have attached the .inf files used on the previous sytem (18fxxxx.txt) and the new system (PIC18Fxxxx.txt).  We tried to use the previous version (18fxxxx.txt) on the new system, but had the aforentioned "code 10" error.  As such, we completely rebuilt the system (i.e. reformat and reload,... OMG,... beliving that would help,... lol) and generated a new .inf file (PIC18Fxxxx.txt) on that system.  So having rebooted, rebuilt and reloaded,... I am stumped,... I am sure it is some NI-VISA configuration issue,... but what?

Kim

[Makoto]

> This device cannot start. (Code 10)

Is this message shown at the Device Manager with a yellow exclamation icon? If so, it is a device driver problem.  I think your device is in conflict problem of driver between NI USB RAW and USB-COMM bridge driver. 

In the previous working system, what VISA address did your app use?  If "ASRLx::INSTR", it must use USB-COMM bridger driver.  If "USB::<vid>::<pid>::<serialno>::RAW", it must be NI USB RAW.

[kptsolutions]

Yes there is the yellow question mark in the device manager window.  I will need to look at the other items when I get back in the lab today.  How would I determine if there is a conflict between the USB RAW and USB COMM bridge driver?  Also, I am not sure how to idenyify the VISA driver addresss,... how would I accomplish this (device manager)?  Is this information in the .inf files or somewhere else?

[Makoto]

>How would I determine if there is a conflict between the USB RAW and USB COMM bridge driver? 

Normally, if the device itself has no problem but driver is in error, the device driver is probably not installed correctly.  This may happen when you have changed the installation of hosting driver at the Device Manager, or when  you have aborted the driver installation while it is in processing.    

> Also, I am not sure how to idenyify the VISA driver addresss,... how would I accomplish this (device manager)?  Is this information in the .inf files or somewhere else?

At your previous environment that correctly opearates your system, execute NI-SPY program (found in NI-MAX's menu) then capture the instrument control traffic.  Then you will see the VISA address in the SPY log.  If the VISA address is ASRLx::INSTR, the device is hosted by USB-COMM bridge driver because the device is ***logically*** at the serial port (but physically USB).  If VISA address is USB::XXX:XXX:XXX::RAW, the device is hosted by NI USB RAW (using custom INF file that was generated by NI USB driver wizard).

このメッセージは　07-07-2008 11:35 PMに Makoto が編集しています。

[kptsolutions]

Thanks for pointing me in the right direction.  I never really figured out why the NI-VISA did not work properly, but I was able to install the PICDEMFS board as a COM device and all is well.  Since we are only using this interface as a demo, this should work.