Re: NI 6025 GPIO device under XPe - anyone done this?

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Bernie Fowler (bern_at_fowlerseng.co.uk)
Date: 10/06/04 

Date: Wed, 6 Oct 2004 20:50:13 +0100

More info...

The 'drivers' installation supplied by NI support a wide range of hardware -
NI tend to have a 'one solution for all' way of doing things - this further
complicates the issue. NI do not seem to be able to advise me of the minimal
h/w requirements for my card - I am amazed at how many DLLs (approx. 20) are
required to talk to the NI 6025. This card offers 32 dig I/O ports, 16 Anag.
In and 2 Anag Out.

Regards,

Bernie

"Slobodan Brcin (eMVP)" <sbrcin@ptt.yu> wrote in message
news:e1Do5rtqEHA.3744@TK2MSFTNGP10.phx.gbl...
> Hi Bernie,
>
> I can't understand why do you want to keep some files on server. Why not
> all XPe files or no files at all scenario.
> Also I have never seen this card, so I can only speak theoretically based
> on other hardware and driver experience.
>
> Ai)
> From Device Manager on your XP Prof you can see all files associated with
> driver itself.
> Also same info you can read from inf file. There is a section that list
> all required files and where they should be put.
>
> Aii) How many inf files is provided by this package?
> Anyhow if they are pure hardware drivers then you can safely make
> component that will copy them to inf folder on XPe image.
> If there are software drivers than you will have to preinstall them from
> your component.
> Type of driver can be determined easily by examining enum branches in
> registry or by look from Device Manager.
> Same thing can be determined by examining inf file itself and checking
> PnPID (VID/PID) numbers presence.
>
> Aiii,Aiv) Depending on what setup/wizard app configure you could be
> required to put some config values in registry from your
> component.
> Use regmon, and regedit to determine what values are used exactly by
> installation.
> Depending on config values used you might be required to write either your
> application or to modify inf file to set hardware device
> specific defaults.
>
> Av) For start try making it work locally. Or on XPP that pull files
> remotely.
>
> Best regards,
> Slobodan
>
> PS:
> Do not use CD inf file auto import option. But do things manually.
>
>
> "Bernie Fowler" <bern@fowlerseng.co.uk> wrote in message
> news:416289bf$0$44857$ed2619ec@ptn-nntp-reader02.plus.net...
>> The following is an e-mail I submitted to the NI support group to
>> summarise
>> what I am trying to achieve - hope this helps (?)
>>
>> I have developed a PC console application using Visual Studio.NET which
>> makes use of the NI 'Traditional DAQ' interface supplied as part of the
>> NI
>> CVI included in the NI Measurement Studio Package. This interface is used
>> to
>> interface to an NI 6025E GPIO board (Compact PCI version). The initial
>> development has been carried out using XP Professional on a Kontron CP304
>> based 'standard' cPCI PC system (Hard disk, Network, CD etc. etc.).
>>
>> My target system is (again) Kontron CP304 cPCI but configured as an
>> embedded
>> system with the following attributes,
>>
>> 256MB Compact Flash
>>
>> No Hard Disk or CD
>>
>> Ethernet link
>>
>> 512MB RAM
>>
>> XP Embedded operating system
>>
>> My design assumes that we have a mapped drive to a file server and all
>> files
>> (as far as possible) are stored on the server (this includes applications
>> and DLLs). The only files required on the target system (in my opinion)
>> are
>> the Kernel Device driver files (e.g. NIDAQ.SYS and XXXX.INF). I include
>> these files into the XPe Target Designer system which builds a
>> pre-configured O/S image with the drivers in place. I have used this
>> method
>> (with success) with another hardware cPCI card and associated drivers.
>>
>> I consider our requirements for the NI system are as follows,
>>
>> i) A list of the Device driver files (*.SYS) required for the NI6025E
>>
>> ii) A list of the Device driver information files (*.INF) required for
>> the
>> NI6025E
>>
>> iii) Any registry settings for the drivers/hardware
>>
>> iv) Confirmation that we do not need to run NIs Measurement Explorer to
>> setup the hardware
>>
>> v) A list of the DLLs required (on the server system) - we can probably
>>
>> establish this by
>>
>> trial and error if the information is not readily to hand.
>>
>> Regards,
>>
>> Bernie Fowler
>>
>>
>>
>> "Bernie Fowler" <bern@fowlerseng.co.uk> wrote in message
>> news:415e6b74$0$17928$ed2619ec@ptn-nntp-reader02.plus.net...
>> > Hi
>> > I am having difficulty installing device drivers for National
>> > Instruments
>> > 6025E hardware under XPe.
>> > Has anyone out there tackled this or a similar problem using NI
>> > hardware?
>> >
>> > Bernie
>> >
>> >
>>
>>
>
>

Relevant Pages