10-24-2006 09:54 AM
After installation of a new PCI-7340 motion-control board, measurement and automation explorer could not see it.
I was using
NI daq 6.9.3
NI motion 6
Measurement and automation explorer 3.02
windows XP SR1
Many previous installations were fine.
I then upgraded to NI Motion7.2 that came with the card, the 7304 was then visible and configurable
This also loaded Measurement and Automation V4.
Unfortunately whist I can see my multi-function a-d boards with the new measurement explorer I can no longer find them with my measurement studio V 6 active X controls. Existing programs run an error 'Could not load NI-Daq dll'
Could you please help?
I have tried this on two separate machines, with the same result
Simon
10-26-2006 10:36 AM - edited 10-26-2006 10:36 AM
Message Edited by Seamus C on 10-26-2006 10:38 AM
10-26-2006 04:07 PM
10-27-2006
10:30 AM
- last edited on
03-10-2025
03:00 PM
by
Content Cleaner
Hi,
the Measurement Studio isn't the link to the hardware, but the driver level is
https://www.ni.com/en/support/downloads/drivers/download.ni-motion.html
unless you're talking about using the Motion Control Module 6.0 (which admittedly does make life a lot easier):
The Motion Control Module for Measurement Studio provides a single ActiveX control (NIMotion) for developing motion applications that use your National Instruments motion controller and Microsoft Visual Basic. While the Motion Control Module was developed for the Visual Basic environment, you can use it in other ActiveX control containers.
To use the Motion Control Module, you will need the following:
The alternative is to use the DLL directly
In terms of the upgrade uptake (or adoption) of VB.net, yes it is a growing development environment, but there's some wonderful facts on a Microsoft sponsored site here :
http://www.devsource.com/article2/0,1759,1772040,00.asp?kc=DSRSS04029TX1K0000651
Just in case the link goes :
Last July (2004) , the company mounted a survey on its Web site, www.visual-expert.com, asking 11 questions about development activities. They got responses from 2,600 people in 100 countries, 44% of whom were from the United States.
The results may surprise you. Mom was right: "everyone" isn't using Visual Basic .NET. Yet. In fact, 78% of respondents still use VB 6, and only 19 percent have switched to VB .NET. The remaining few percentage points are held, believe it or not, by VB 5!
Shops of all sizes contributed to these results, though the sample was overwhelmingly weighted in favor of small teams. Almost half (48%) have VB teams of one or two developers, while only 8% had teams of 20 developers or more.
When asked when they were planning to migrate to .NET, one third of VB 5 or VB 6 developers said they would do so in the next two years, 42% didn't know, and 12% didn't waffle: they said "Never." The final 13 percent plan to migrate, but not in the next two years.
When asked for the benefits they see in a migration, 17% of the developers said "None"! The rest named the .NET Framework (25%), Web services (18%), ASP .NET (17%), and 14% just like to get their hands on a new development language.
This crew really does like its Visual Basic, though. On a scale from 0 to 10, respondents were asked to rate VB as a programming language; 68% rated it 8 or higher (it got a perfect 10 from 14%). Sixteen percent gave it a 7, and 16 percent rated it 5 or less.
Microsoft's VB support was greeted with somewhat less enthusiasm, with only 45% granting it a rating of 7 or higher, 30% allowing a middling grade of 5 or 6, and 19% turning thumbs-down with ratings of 4 or less.
.NET functionality — or lack thereof — was another complaint. Components and tools available in VB 6 were missing from VB .NET, claimed the developers. (Microsoft has taken so much flak over some of the debugger omissions that the features have found their way back into the next version of Visual Studio, Whidbey).
Respondents also cited cost, and the learning curve, as reasons to stick with the tried-and-true. It's just not worth the time and effort to migrate some projects. Some companies maintain the old code for the life of the product, but do their new development in .NET.
Admittedly, some of these results are skewed because of questionnaire design. For example, many respondents commented that they use both VB 6 and VB .NET, but that the language choice question only permitted one answer. Others plan to move away from VB entirely, migrating to C#, C++, or open source languages, and the questionnaire didn't allow for that, either. Novalys lists all of the respondent comments (in their original languages) on the survey result Web page, and they're interesting reading. You'll find the entire set of results here : (http://www.visual-expert.com/us/info/survey_vb_2004_results.htm)
Hope that helps
Thanks
Sacha Emery
National Instruments (UK)
Message Edited by SachaE on 10-27-2006 04:32 PM
Message Edited by SachaE on 10-27-2006 04:33 PM