11-16-2010 02:30 PM
You simply don't get it. If you have a application in LabVIEW 8.2 using daqmx and you load labview 2010 and load daqmx, the 8.2 version application will no longer work. That means you need a separate machines to support your older applications if you want to use the newer software. If you have 20-30 different applications all over the world using the older version, it is not always feasible to upgrade all of them. No other hardware vendor I use does this to me. I guess I should load LabVIEW only and forget about the drivers, toolkits, etc that could corrupt whatever version of software that I am using. Basically, I, and my customers, want me to focus on writing programs for them. Not fighting driver issues or new bugs found in a newer LabVIEW version. If I have a working version, I don't want loading a newer version to change it in any way. Just my 3 cents.
11-16-2010
02:31 PM
- last edited on
01-30-2025
09:46 AM
by
Content Cleaner
Hi everybody,
I managed to find the old DAQ / LabVIEW Compatibility article, but I'm not sure exactly what happened to it--it looks like the DAQmx section is currently removed for some reason (the chart is still shown in the excel spreadsheet which is attached, although it mistakenly shows that DAQmx 9.1.5 is compatible with LabVIEW 8.2).
Until the KB is fixed, here's a corrected chart that you can use for DAQmx:
Green = Supported in LV and LV Real-Time
Yellow = Supported in LV only
Orange = Supported in LV Real-Time only
9.1.6 and 9.1.7 have the same LV support as 9.1.5.
9.2.1, 9.2.2, and 9.2.3 have the same LV support as 9.2 (which also has the same support as 9.1.5).
If ever in doubt, it's always a good idea to double-check the appropriate readme for the particular version of DAQmx that you are interested in.
Best Regards,
11-17-2010 07:38 AM
Hi John,
Thanks for posting the new version of the chart. However for me it comes to late. I installed 9.1.5 and now LabVIEW 8.2.1 does not work anymore.
I'm very disappointed that things are going this way. I must have the old versions of LabVIEW due to the fact that all those versions are running somewhere on some machines. It's not me to decide that users have to upgrade because I wanted to upgrade.
If I understand this all well, I'm forced to have separate PC's for each old version to be able to serve LabVIEW apps??
Regards,
Paul Rijkers
11-17-2010 09:28 AM
My two LabVIEW using co-workers have two PCs each because of this. I have three technically but very rarely need the 7.1.1 box. It would be great if multiple DAQmx versions could live on the same PC and only require a LV restart instead of a tedious software re-install to swap them.
I definitely agree that hobbling our productivity like this is not worth the new features that all these too little, too soon "upgrades" provide. Not to mention the extra cost!
Remember though, the easy answer is to not upgrade your hardware. Then you can stick with with whatever LabVIEW and DAQmx versions you like until an OS incompatibility forces the issue. It's tough to not get to play with the newest toys though.
I actually hate to even say this since LabVIEW is my first programming language and I love the quickness and ease with which I can write code using it. Trying to support massive legacy code bases with it is it's only major dissapointment for me. (IF, you don't count the Report Generation Toolkit. )
11-17-2010 01:51 PM
You guys might want to vote and comment on the following idea exchange suggestion:
Ability to have multiple and distant LabVIEW development versions installed
For what it's worth I do sympathize and agree that the current behavior leaves quite a bit to be desired. The idea exchange would be the best place to discuss any possible alternatives.
Best Regards,
11-19-2010
09:34 AM
- last edited on
01-30-2025
09:47 AM
by
Content Cleaner
Just to let everyone know, KB 3PIA89N5: NI-DAQ and LabVIEW Version Compatibility (for Windows) is fixed. I apologize for the inconvenience.
EDIT: Spoke too soon. NI-DAQmx 9.1.5 doesn't support 8.2. I'll have that fixed too. <head desk>
11-19-2010 10:04 AM
Also, please delete the two blank worksheets in the .xls file.
It is a pet peeve of mine when people leave Excel at the default of 3 blank worksheets for a new workbook.
When you have 3 sheet tabs showing, it looks like you have 3 sheets worth of data which is not the case. Only sheet 1 as any data.