Need help trying to adapt LabView application that was using AT MIO-16XE-50 IO to a new input board PCI-6034E

[cubob]

I am trying to upgrade from a Windows 2000 PC using an AT MIO-16XE-50 IO board to a Windows XP PC using a NI-PCI-6034E PC board.  II am using the same analog input module (SSC-AI03 which resides in a SC-2345 singal conditioner module) and the same LabView 6.1 application.  When running the application on the new PC, we get an error - 10001 occurred at AI Group Config.  I ran the measurement and Automation software and configured the new PC board as closely to theolder one as I could and still gMt the same error.  When I compare the configuration of the older PC board and the new one I see a couple of things I am not sure about.  For information purposes the old PC has Measurement and Automation software version 2.2 and the new on has version 4.7.  When I check the configuration of the older board on the older PC I can see the board directly under Devices and Interfaces as AT MIO-16 XE-50 (Device 1), when I look at the system tab I can see an I/O range of 0X100 to 0X11F, an interrupt request of 5  and a Direct Memory Access of 5.  when I compare the new PC board to the older one, th enew one has a larger data range, an interrupt reuest of 16, and has a Direct Memory Access of 0.  These can not be changed on the new card.  Coudl this be the issue causing the application to not be able to access this new card?  Also the new card can be seen not directly under the Devices and Interfaces but in another folder Traditional NI-DAQ (Legacy Devices).  Do I need to modify the application to access this other location or is the Device name of Device 1 the critical part?  Basically, I am having trouble getting the new card configured to run on the older application. How do I do this?

[JÞB]

It sounds like a Driver issue.  What version of NI-DAQ is on the two machines? Driver Support for the 6034 devices started much later than the AT MIO-16.  and the original app may have been developed on a version that does not support it-  ALTHOUGH- your technology is over a decade old- the 6034 you are upgradeing to is facing obsolescence. 

[cubob]

Jeff thanks for your response.

The old PC is running NI-DAQ 6.9.2

the new PC is running NI-DAQ 7.4.1

[Kevin_Price]

Sounds to me like you might be able to resolve this through Meas. & Auto. Explorer (MAX).

First, check out this thread (and perhaps others) related to error code -10001.  The error

code suggests that your channel string may be invalid somehow.  I would also be sure

to verify your device # and perhaps even the 'group' designation.  Also check the code to

see whether it specifies a 'virtual channel' rather than a physical channel # string.

Armed with that info, now go into MAX and test out the ability to acquire from the channel(s)

in question.  Supposing that works, as is likely, you are probably well on your way to

solving the problem.  All things considered, I'm guessing maybe you need to set up

virtual channels in MAX to match the ones that had been set up on your older PC.

-Kevin P

[JÞB]

---

@cubob wrote:

Jeff thanks for your response.

The old PC is running NI-DAQ 6.9.2

the new PC is running NI-DAQ 7.4.1

---

http://ftp.ni.com/support/softlib/multifunction_daq/traditionalnidaq/7.4.1/readme.html

7.4.1 does not work with LabVIEW 6.1

[cubob]

So, it seems we need to upgrade our LabView?  Or is there a way to go back to an earlier NI_DAQ that would also be XP compatible?

[JÞB]

---

@cubob wrote:

So, it seems we need to upgrade our LabView?  Or is there a way to go back to an earlier NI_DAQ that would also be XP compatible?

---

you can download 6.9.3 here.  But, Yes, you should consider a modernization program.

[cubob]

Jeff:

Thanks for the help.

I uninstalled NI-DAQ 7.4.1 and installed NI-DAQ 6.9.3 but then when I ran th eLabView app, I got an error message

"application failed to start because nidaq32.dll was not found"  When I spoke with National instruments on Monday when this error happened, I was told to install NI-DAQ 7.4.1 which got rid of the not found nidaq32.dll, but the error 10001 persists.  So, right now I can go into Measurement and Automation.  I can see the board under the Traditional NI-DAQ (Legacy Devices) "folder", and can give it the same device number and configure it just like the other board is on the older PC.  But, the application in LabView can't recognize it.  Is it because it is LabView 6.1?  If we upgrade LabView is there a nice and easy conversion tool for taking the LabView 6.1 application and turning it into the later LabView version?

[JÞB]

Not really,  especially if you do not have the source code the application was built from.  This might be one of those times to speak to a LabVIEW developer that can guide you through evaluating what your specific needs are and help you develop a plan to get you where you wish to go.

[cubob]

I was starting to think along those lines.