LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Most recommendable Labview version with Windows XP

Yeah, this is kind of a gruesome discussion because we are talking about a wildly UNoptimized scenario.  I believe we've given the OP a good sense of the available pathways, and the pros and cons of each.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 21 of 29
(2,142 Views)

@crossrulz wrote:

@billko wrote:

According to the chart, DAQmx was not compatible with labVIEW until LV 8.5.


That chart only goes back as far as DAQmx 9.1.5.  Trust me, there were plenty of DAQmx releases before that.  Prime example: DAQmx 9.0.  I specifically remember that release because that is when the TDMS streaming was introduced and saved me months of development.

 

Trust me, I remember from experience that there is a version of DAQmx that will work with LabVIEW 7.1.  I could not tell you what version though.


I've actually poked around a bit and found this, which shows that you are, indeed, correct.  Furthermore, I found this, which shows that Traditional DAQ is actually still compatible with LabVIEW even as far as 2015 (which could be just because the page hasn't been updated).

 

So I recall a big thing at a company I used to work for that we had to do a big conversion to DAQmx.  This was years ago.  Why would this be?  Do you think it was because of new hardware that Traditional DAQ did not support?  I'm just trying to remember why we had to transition and it was a big headache, is all.

 

Feel free to message me (or not) if we're drifting too far off topic.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 22 of 29
(2,139 Views)

@billko wrote:

According to the chart, DAQmx was not compatible with labVIEW until LV 8.5.


That chart just starts showing LabVIEW 8.5 and above.  They chopped off the older versions of LabVIEW.  (Not sure why because it is still valid data.  And still relevant as this message thread reveals.)

 

EDIT:

 


@billko wrote:

So I recall a big thing at a company I used to work for that we had to do a big conversion to DAQmx.  This was years ago.  Why would this be?  Do you think it was because of new hardware that Traditional DAQ did not support?  I'm just trying to remember why we had to transition and it was a big headache, is all.


Sorry, I didn't realize the other responses had been posted.  My browser window was stale and I was replying to the last message I saw.  It is very likely that newer DAQ cards were supported by Traditional DAQ.  It still worked for much later versions of LabVIEW, but not much support was being added to those older drivers.  Also, your big company push probably came because it would be easier logistically to have a systemic conversion of your code from old to new rather than trying to support legacy and new drivers at the same time.

Message 23 of 29
(2,136 Views)

@RavensFan wrote:

@billko wrote:

According to the chart, DAQmx was not compatible with labVIEW until LV 8.5.


That chart just starts showing LabVIEW 8.5 and above.  They chopped off the older versions of LabVIEW.  (Not sure why because it is still valid data.  And still relevant as this message thread reveals.)

 

EDIT:

 


@billko wrote:

So I recall a big thing at a company I used to work for that we had to do a big conversion to DAQmx.  This was years ago.  Why would this be?  Do you think it was because of new hardware that Traditional DAQ did not support?  I'm just trying to remember why we had to transition and it was a big headache, is all.


Sorry, I didn't realize the other responses had been posted.  My browser window was stale and I was replying to the last message I saw.  It is very likely that newer DAQ cards were supported by Traditional DAQ.  It still worked for much later versions of LabVIEW, but not much support was being added to those older drivers.  Also, your big company push probably came because it would be easier logistically to have a systemic conversion of your code from old to new rather than trying to support legacy and new drivers at the same time.


Thanks for your reply.  It was all kind of muddy back then because I was still at the bottom of the LabVIEW learning curve instead of the middle like I am now.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 24 of 29
(2,128 Views)

I meant to say newer DAQ cards were *NOT* supported by traditional DAQ.

 

My gut feel is that DAQmx started with LV 7.1, and LV 7.0 was still traditional DAQ only.  But I have yet to find anything that confirms that.

Message 25 of 29
(2,124 Views)

@billko wrote:

So I recall a big thing at a company I used to work for that we had to do a big conversion to DAQmx.  This was years ago.  Why would this be?  Do you think it was because of new hardware that Traditional DAQ did not support?  I'm just trying to remember why we had to transition and it was a big headache, is all.


Two main reasons I can think of: 1) wanted to use new hardware that Traditional DAQ did not support or 2) moved to a 64-bit OS (suppedly there was a way to get 64-bit to work with Traditional DAQ, but it looked like a pain),

 

I went through the pain of updating a system last year from Traditional DAQ to DAQmx.  Luckily, there was not much to the DAQ portion of that code, but it was still a pain figuring out what it was actually trying to do.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
Message 26 of 29
(2,117 Views)

My memory is that DAQmx was for sure *not* around at LV 6.1 (was that the one called "6i"?), and indeed was around for LV 7.1.  Not sure I ever hopped on at 7.0.

 

Soon after introducing DAQmx (if not right at introduction), new hardware products did not get development support for traditional NI-DAQ.  As I recall, the 62xx series MIO boards were among the early popular DAQmx-only cards.  I wanted some of the features (hw-timed DIO, 32-bit counters), that nudged me over into DAQmx world.  

 

For years though, I frequently still had to use traditional NI-DAQ simultaneously for an older PCI-4351 board that was never given DAQmx support.  Contrary to some statements I've read you *can* use both drivers simultaneously, it's just that any given board must be addressed through only one driver at a time.

 

 

-Kevin P

ALERT! LabVIEW's subscription-only policy came to an end (finally!). Unfortunately, pricing favors the captured and committed over new adopters -- so tread carefully.
Message 27 of 29
(2,114 Views)

I was digging through some old random files I have collected over the years and ran into the attached spreadsheet (NI-DAQmx LabVIEW Compatibility).  Apparenetly, LabVIEW 7.0 could use DAQmx 7.0!


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
Message 28 of 29
(2,082 Views)

LV 7.0 definitely supported DAQmx. I have VMs with code which still uses this combination. It was supported by multiple versions of DAQmx (since NI supports a couple of LV versions backward).


___________________
Try to take over the world!
0 Kudos
Message 29 of 29
(2,057 Views)