will vb.net standard edition run mstudio PE

[stuman]

Can someone tell me if measurement studio PE will run in VB.NET 2003 standard edition? I only want to program in VB.NET, hence I dont need any other languages.

Thanks
Stuman

[stuman]

OK, I have just found out that it will work OK. My next question is I have a DAQPad 6070E, which states that it uses the traditional NI-DAQ driver. Will this present any problems in developing an application to log 2 channels at 600KHz each in VB.NET SE? Reason, I dont fully understand the difference between Traditional NI-DAQ and NI-DAQmx.

Thanks
Stuman

[George M.]

Hi Stuman,

First, since you are interested in programming in VB.NET, you will have to use the NI-DAQmx driver. Next, the 6070E can be programmed using both drivers, but the software is limited to programming with only DAQmx. The latest version of the driver is 7.3, and can be found here. Please note that version 7.4 is going to be coming out shortly. Nonetheless, 7.3 will do a great job.

Now, to explain the differences between the drivers, Traditional is the older of the two drivers. Traditional was the original DAQ driver, and has been updated by DAQmx. DAQmx came out with the advent of express vi's in LabVIEW 7.0. DAQmx is a much better driver, and is much easier to use. There is one set of functions for all of the different tasks (AI, AO, DIO, etc.) with DAQmx. Traditional had specific VIs for AI, AO, DIO, etc. It is a great idea to program with DAQmx, especially if you are just beginning.


I hope this clears up your confusion.

George

[stuman]

Ok still a bit confused. I followed your link and it says that the NI DAQPad-6070E uses version 7.3 T, which is the traditional NI DAQ driver only. The product data sheet for the DAQPad also states that it uses the NI DAQ driver as well. So you can see my confusion. Given what you said, can I program with VB.NET to the firewire DAQPad-6070E using NI DAQmx? ( I would rather not use activeX controls to achieve this ). This would make it a totally managed code solution contained within the .NET framework.

Thanks
Stuman

[George M.]

Hi Stuman,

Ok, sorry about the confusion. I was thinking about the PCI version of the 6070E. You are right that the DAQPad 6070E is Traditional only. Unfortunately, the VB.NET can only be programmed with DAQmx, so your only option to be able to program with VB.NET is get a DAQmx capable board. You could get one of the USB devices listed in that table, or even switch to a M Series PCI board.

Sorry about the confusion, but I hope this clears it up. Have a Great Day!

[drohacek]

---

@George M. wrote:
Hi Stuman,

Unfortunately, the VB.NET can only be programmed with DAQmx, so your only option to be able to program with VB.NET is get a DAQmx capable board.

---

You do have options for programming Traditional DAQ from VB.NET, it's just that National Instruments does not provide a native .NET library for doing it. Check out this discussion thread for information about your options.

[stuman]

Yeah I figured as much, I would have to use the active X controls and the like. This would not be a totally .NET native solution, but it is all I have to go by.

Question. If the PCI version of the 6070E is DAQmx compatible, then why is the firewire version not?
PS When will it be DAQmx complaint?

Thanks
Stuman

[Malcolm]

>> Question. If the PCI version of the 6070E is DAQmx compatible, then why is the firewire version not?
>> PS When will it be DAQmx complaint?

Unfortunately, there are no current plans to port the DAQPad-6070E and 6052E FireWire devices to NI-DAQmx. While the register set of the board is very similar, the additional overhead and infrastructure required for FireWire communication is very complicated. Support for the FireWire DAQPads is not going away anytime soon. We will continue to support it in Traditional NI-DAQ.

One option, if you are looking for a new device, is to use the DAQPad-6015 for USB. It's a slower than the 6070E (200kS/s v. 1.25 MS/s) but it is 16-bit and fully supported in NI-DAQmx.

Regards,
Malcolm Borgendale
Measurements Software

[stuman]

Your point about complicated firewire overhead may be true, but if it is still supported using Traditional NI-DAQ, then we can program it using ActiveX controls. If we can program it using ActiveX control, then there should be no problem programming it natively within the .NET framework using DAQmx. It only lacking in the will to make it happen.
Stuman