| Register | FAQ | Calendar | Search | Today's Posts | Mark Forums Read |
|
#1
| |||
| |||
| Hello, I know this is a common error but I'm unable to find a solution looking through these forums and other websites. I am trying to convert a program wrote on an old computer running LabVIEW 6 to a new computer (with newer hardware) running LabVIEW 8.5. I've resolved all issues that have came up so far (installing the traditional legacy drivers and such). The only error I am getting now is a run-time error that pops up and reads: "Error 10401 occurred at AI Group Config" and "Error 10401 occurred at AO Group Config" I've already run the Measurement and Automation Explorer (MAX) and that did not help. I'm using Windows XP and my hardware is a NI PCI-6281 M series DAQ. Do I have to re-write the sub-VI's, or is this fixable? Is there an easier way to convert a program? If anyone can provide any help or insight what so ever it is greatly appreciated. Thanks, Alex |
|
#2
| |||
| |||
| Yes, you have to rewrite your program. The M series of boards is only supported with the newer DAQmx driver. |
|
#3
| |||
| |||
| Thanks for the quick reponse. Will I be able to get away with just re-writing the areas where it is aquiring input or sending output (where the problem exists) and interfacing that to the rest? Or do I need to re-write the entire thing? Alex |
|
#4
| |||
| |||
| Just re-writing the DAQ part should be enough. However, that might be quite a bit of re-writing. See <a href="http://forums.ni.com/ni/board/message?board.id=170&thread.id=338208" target="_blank">this</a>as an example of some of the changes you may need to make. Message Edited by Dennis Knutson on 07-08-2008 10:03 AM |
|
#5
| |||
| |||
| Alex, <a href="http://zone.ni.com/devzone/cda/tut/p/id/4342" target="_blank"> This Developer Zone article</a> may also be of some help to see the differences between Traditional DAQ and DAQmx for the most common tasks. |
![]() |
| Thread Tools | |
| Display Modes | |
In an effort to better serve ads to our visitors, cookies are used on objectmix.com. For more information, check out our Privacy Policy.