MATLAB DataPlugin for 64-bit LabVIEW

Where is the 64-bit LabVIEW support for writing Matlab .mat files? Or is the source code available for the 32-bit version (http://zone.ni.com/devzone/cda/epd/p/id/4178) so that someone can compile their own?
Thanks,
D

To clarify what Chris said, 64-Bit Operating Systems with a 32-Bit emulation (x86 directory) are certainly fine with 32-Bit LabVIEW. (this excludes Windows XP 64-Bit as it has no emulation layer)
Most general 32-Bit vs. 64-Bit LabVIEW questions are covered in this KnowledgeBase article.
To summarize, you'll have full LabVIEW functionality with the 32-Bit version.
The 64-Bit version of LabVIEW is really only recommended for Vision applications that need the additional resources for large image processing.
As another note, currently, most of our software also only supports 32-Bit versions of The MathWorks, Inc. Software.
MATLAB® is a registered trademark of The MathWorks, Inc.
Applications Engineer
National Instruments
CLD Certified

Similar Messages

How to create a dataplugin for DataFinder using LabVIEW

We want to use LabVIEW to create a dataplugin that will be used by DataFinder (My DataFinder). We have found on the NI web site the LabVIEW DataPlugin SDK - , a SDK that allow us to create a dataplugin. The SDK is for LabVIEW 8.6.
The dataplugin example code of the SDK work very well in the “For testing” section of the development project. We are also able to register it to use it through DataFinder. The dataplugin is available in the “Configure ...” window of DataFinder.The problem is that the dataplugin doesn’t work with DataFinder. We didn’t receive any kind of error message or code. We only get the value “eIndexedFailure” in the “Index status” property. After expectation, it seems those input parameters are different between a LV and a VBS dataplugin. And we think that can be the source of the problem. There is someone that can help us about that?
We also want to use LabVIEW 2009. The SDK example work under 2009, but we get the same problem with DataFinder.
Thanks
Solved!
Go to Solution.

Dear Kelly R, you're right I can’t open the file in DIAdem. The RegisterLabVIEWDataPlugin.ini file is correct. But I’ve just tried to rebuild the project and then use the Installer instead of just using the Deploy. Now it works, even with my own code. Now I can open the file in DIAdem without problem. The installer uses the “NI LabVIEW Dataplugin 1.0” package. It seems that the SDK installer has never install this package.I thank you all for your help.

Creating .mat files with Matlab dataplugin in LabVIEW

I am trying to create a .mat file in LabVIEW using the Matlab dataplugin. It appears to create a group called "Vector" without being told to, and it also concatenates group and channel names together. I have made an example to demonstrate this behaviour. I am trying to create a group called "Group" and inside it a channel called "Channel". What I get looks like a group called "Vector" and inside it a channel called "GroupChannel". What am I doing wrong?
Best Regards,
John Sackett
Solved!
Go to Solution.
Attachments:
write mat example.zip ‏54 KB

Hello John
Thank you for getting in touch regarding your issue. I am an applications engineer here at National Instruments, as I understand you are using the data plugin for Matlab within LabVIEW, but as shown with your code when you label the channel or group you get an outcome which you don't expect.
I have opened and had a look at your code and can see where the issue is arising. The functions you are using are normally used with TDM files, .MAT files are compatible but there are a few differences between the file formats, which is why you are getting the outcome we have seen. A TDM file has headers named channelgroup and channel, but Matlab does not have the channelgroup header in the file type and therefore the functions in LabVIEW merge the 2 strings to the available header.
I am not able to open your .MAT file so could you give me a brief description of what occurs inside Matlab?
Have you looked into using the script node to allow for .MAT file types in LabVIEW? Here is the help file
I have also found some resources which you may find useful.
LabVIEW to MATLAB
Convert file
Open .MAT in LAbVIEW
DataPlugin
Let me know if you would like any further information
Regards
Stephanie L
Applications Engineer
National Instruments UK and Ireland

Display value in MATLAB For loop on LabView

Hi guys,
I have a MATLAB script in my VI. The MATLAB script runs a For Loop. For each iteration of the For Loop, a variable say, count is incremented by 1.
From what I am experiencing, the MATLAB script only outputs the final value of count when the script is done running.
Is it possible to capture the value of count as each iteration is performed?
PS : Using a LabView For loop is not possible for my case. Running the MATLAB code is mandatory.
Thank you in advance!

When the Matlab script gets called, it's actually passing control over to the Matlab ActiveX server. Thus, LabVIEW has to wait until that's done before it can proceed. What you're asking for is interprocess communication. That doesn't come provided "out of the box". You have to create it yourself. Some ideas were suggested here: http://forums.ni.com/t5/LabVIEW/Labview-Matlab-Exchange-Data/td-p/1408054

Mathscript node: an internal mathscript error has occurred: 64-bit LabVIEW 2009

Hi Folks -
I have an installation now of
LabVIEW 2009 9.03f, Vision, and Advanced Signal Processing Toolkit, all
64-bit versions on a new computer so that I can convert some code from
32- to 64-bit.
I figure I will address errors
one-by-one and here's the first one. I have a VI with a mathscript
node and the VI, which loaded and ran fine in the 32-bit environment,
is now broken and giving the error "mathscript node: an internal
mathscript error has occurred." My main concern - is mathscript not
supported in 64-bit LabVIEW right now?
I am attaching the VI. Any ideas are appreciated. I need to get this working.
Also, NI, is there a special 64-bit forum that we should post to in the future, or create to post to?
Sincerely,
Don
Solved!
Go to Solution.
Attachments:
sort.vi ‏753 KB

From 2009 help
LabVIEW MathScript is a text-based language you can use to write functions and scripts. You can process scripts using LabVIEW MathScript in the LabVIEW MathScript Window or a MathScript Node. When you create a LabVIEW MathScript, you must use supported data types.
The MathScript syntax is an intuitive and logical
syntax predominantly based on standard mathematical and computer
programming terms, terms in widespread and common use, and/or
descriptive abbreviations, truncations and concatenations of standard
terms. The LabVIEW MathScript Window and MathScript
Nodes are able to process files you create using the current MathScript
syntax and, for backwards compatibility, files you created using legacy
MathScript syntaxes. The LabVIEW MathScript Window
and MathScript Nodes also can process certain of your files that use
other text-based syntaxes, such as files you created using the MATLAB® software. Because the MathScript RT Module engine is used to process scripts in the LabVIEW MathScript Window
and MathScript Nodes, and because the MathScript RT Module engine does
not support all syntaxes, not all existing text-based scripts are
supported.
(LabVIEW 64-bit) LabVIEW MathScript is not supported in LabVIEW (64-bit).

Using access with 64 bit labview

Hello,
I have 64 bit version of Labview, and I want to use an access database. I used the internal search for examples, and it showed an example in examples/comm/access.llb. Well, that does not exist with this install. (I did a 32 bit install, and they exist.)
Has anyone have success with 64 bit LV and access? Any links to where to start... Just need a nudge in the right direction.
-- brett

Thanks for that suggestion Ian.
I've looked through our documentation on 64-bit compatibility for LabVIEW and it looks like you are correct, that should not have installed. What I didn't realize was that the test machine I was using also had 32-bit labview, so the example finder located all of those examples.
Is there any reason you cannot use the 32-bit version of LabVIEW? At the moment, that is the best option we have for internal compatibility, as most toolkits have not been ported to the 64-bit version of LabVIEW, even though they can run on a 64-bit operating system.
Past that, I've taken a look at Ian's suggestion and it seems like a pretty solid thing to try, along with the API in the second post of that thread.. Let us know if it works for you.

SpaceX is looking for engineers with LabVIEW experience in Hawthorne CA (LA area)

SpaceX is looking for engineers with LabVIEW programming experience for our Launch group. Our responsibilities include:
Controlling launch pad equipment via PXI/LabVIEW
Commanding and monitoring our Falcon 1 and Falcon 9 rockets via a LabVIEW-based Vehicle control system
Commanding and monitoring our Dragon capsules via a LabVIEW-based Mission Operation system
Ocean recovery of Falcon 1 and Falcon 9 stages after liftoff and Dragon capsules after splashdown
Cargo configuration of Dragon capsules going to resupply the International Space Station
Maintenance of Mission Control Centers with the help of our IT department
With the exception of the launch pad equipment program, most of our LabVIEW programs do not interact with DAQ hardware (unusual, I know). The Vehicle control and Mission Operations software get their data via Ethernet from 'black boxes' that connect to NASA & Commercial RF ground stations. We also create several utility programs in LabVIEW that also don't interact with hardware. So, this is mostly a software gig, not a hardware/software gig.
Ideal candidates will have the following qualities:
CLD-level LabVIEW experience
A good understanding of basic computer networking (TCP/IP, UPD, firewalls, VPN)
Must be enthusiastic about space (What year did we land on the moon? How many men walked on the moon? How many Space Shuttles do we currently have? etc.)
Must be willing to travel. Common destinations include Houston (NASA Johnson Space Center), McGregor TX (test site), Cape Canaveral FL (launch site), Kwajalein Marshall Islands (launch site)
Must be able to work without supervision. We have a very flat management structure, no one will be telling you what you need to do. If you don’t know, ask. If you do know, get it done.
About the job:
Job is located in Hawthorne, CA in the Los Angeles area.
This is not a 9-5 job. There will be some late nights.
You won't be LabVIEW only. Everyone chips in as needed. Our group has done Javascript, C++, MATLAB, configuring of TELEX comm systems, cutting of metal with bandsaws, welding, Unigraphics CAD, etc. If we need it and you don't know it, grab a book and learn.
We are only hiring full time employees. Contractors need not apply.
To conform to U.S. Government space technology export regulations, SpaceX hires only U.S. citizens and U.S. Permanent Residents.
Apply at SpaceX.com. Click the Careers button and fill out the general application. Mention this posting in the cover letter field. Don’t reply to this forum. You need to go to SpaceX.com to get your information into our system.
Message Edited by Lavezza on 03-31-2010 03:59 PM

There is a job posting up now at SpaceX.com. Go to the careers tab and search for LabVIEW.
Look for the position called: Mission Control Software Engineers (LabVIEW).

No 64-bit long ints in LabVIEW 7? [Also: beta version of 64-bit LabVIEW?]

Is there no primitive data type in LabVIEW 7 that corresponds to a 64-bit long int? [I guess LabVIEW would call it either I64 or U64...]
Please, please tell me I'm wrong - if I'm right, this is an unacceptable state of affairs.
And, if I'm right - when will LabVIEW be upgraded to 64-bit-ness? Is there a beta version of 64-bit LabVIEW out there that I could get involved with? [I'd really, really like a 'for' loop that could take 64-bit ints as its counters.]
Anyone know anything about this?
Thanks!

There is no native support for 64 bit ints. I don't expect to see that until Windows has support for 64 bits. For work arounds, see this posting.

How to generate and use Matlab(R2007) .dll's in Labview

Is there a step-by-step example on how to generate and use Matlab(R2007) .dll's in Labview.
Our experimenal hardware is LabView-controlled and we want to pass
images/2d intensity arrays to a more complex matlab program that will
return an array of extracted data which we want to use in LabView again.
Thank you
Carsten

I recommend having a wrapper created around the matlab dll that converts the datatypes for you. There is a lot of fooling around with pointers involved which is very difficult in LabVIEW. btw, this got much more complicated after Matlab 7. Essentially, you need to convert your inputs into mxArrays, and then add those mxArrays to an mxArray list that you pass by pointer into the matlab dll. You also need to create a mxArray list for the outputs from the dll which you will need to extract your data out of before converting it back into a LabVIEW supported datatype. It's a big hassle. We do this pretty often, but we have created a c library that handles all the conversions, so it is feasible for us. Unfortunately, I can't share the library, but hopefully this information will help you get where you want to be.
Like I said, it would be easier if you can just get a c developer to write a wrapper for you to keep it simple in LabVIEW. Alternatively, you might try getting your m-code to work in Mathscript.
Chris

64-bit Labview 2013 Ni-845x = ?????

Rediculous....
If I have the following setup:
- Windows 7 64-bit
- Labview 2013 64-bit
- NI USB-8452
What driver do I use???????
v2.1.2 is 32-bit only...
v2.1 coverd 64-bits but not for Labview 2013, stops at 2012. Found this in a random compatibility chart no where near the damn driver or HW pages.
This is a maze of information, and digging for info like this should not be the norm.
My NI USB-8452 is glitchy when looking for it in NI Max. When I try to use the driver for I2C setup and immediately disconnects from USB (I hear the Window USB disconnect noise).
Has anyone had this problem? What driver do I use for Labview 2013 64-bit for the NI USB-8452.

My box is still not working.
I have:
NI USB-8451 (works fine)
NI USB-8452 (fails on ARG1 and I know it is right).
How can the same piece of cod work for one and not the other. It work previously, and now all of the sudden it's broken for the 8452 only.
See attached picture.
Please help me before I go insane.
Attachments:
WTF.png ‏19 KB

A source distribution created in 32-bit LabView 2009 says that VIs aren't executable when opened in 64-bit LabView 2009. How do I run the main VIs?

A source distribution was made for a VI using 32-bit LabView 2009. The distribution was verified to work on another machine that ran 32-bit LabView 2009. However, when opened on a 64-bit LabView 2009, the VI was broken as indicated by the attached error message. How do I make the VI executable?
Solved!
Go to Solution.
Attachments:
source dist error.JPG ‏70 KB

Seems you have a problem with the installation of the Advanced Analysis Library (AAL) or the Intel Math Kernel Library that is used by the AAL on that 64 bit machine. Can't say for sure if these are already supported on 64 bit LabVIEW. At least a repair installation of LabVIEW seems to be in place.
The other error is from the HSD component not working. Again I can't say if this should even work on 64 bit LabVIEW. If it should a repair installation should be most probably done.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Excel spreadsheet control for 64 bit windows OS

Hi all,
I'm looking for a way to use excel (or something equivalent) in a 64 bit labview application. I've been using OWC11 in a 32 bit application to allow users to take advantage of most excel functions and build a table that is used by the application to run a test. I'd like to keep using it but it can't run in a 64 bit application. I haven't been able to find anything similar for 64 bit, so unless someone knows of something, perhaps someone could suggest another method?
Solved!
Go to Solution.

Hi gharris,
I have included a link that shows how to perform basic tasks in excel using ActiveX in LabVIEW. Is this something that would work for your application?
Using LabVIEW and AcitveX to Perform Basic Tasks in Microsoft Excel
Justin D.
Applications Engineer
National Instruments

NI-RIO 4.0 not compatible with 64-bit LabVIEW?

Hi,
I have a 7841R multifunction RIO card. I'm currently installing the evaluation version of LabVIEW to test it out. I've got 64-bit LabVIEW successfully installed and I had installed NI-RIO 3.6 (which was on the disk that came with the card). In the process of installing other features (I believe the C interface for FPGA or something) I discovered that I needed NI-RIO 4.0. I uninstalled NI-RIO 3.6, downloaded NI-RIO 4.0 and now I'm attempting to install it. I get the following message a few steps into the process:
Important note about NI-RIO support for LabVIEW (64-bit Versions)
A 64-bit version of LabVIEW was detected on your system. This version of the NI-RIO driver does not support 64-bit versions of LabVIEW. However, this version of NI-RIO is fully compatible with 32-bit versions of LabVIEW installed on 64-bit operating systems.
Is there a version of NI-RIO 4.0 that supports 64-bit versions of LabVIEW? If so, could you point me to it?
Or should I install the 32-bit version of LabVIEW?
Thanks for the help!
Cheers,
tom
Solved!
Go to Solution.

Hey Tom,
Unfortunately we do not have a RIO driver that is compatible with our 64-bit LabVIEW Development software. If you need to use the RIO driver, you should install the 32-bit version of LabVIEW and build your applications in that development system. Sorry for the confusion initially during the installation process!
Ben N.
Applications Engineering
Certified LabVIEW Developer

64-bit LabVIEW - still major problems with large data sets

Hi Folks -
I have LabVIEW 2009 64-bit version running on a Win7 64-bit OS with Intel Xeon dual quad core processor, 16 gbyte RAM. With the release of this 64-bit version of LabVIEW, I expected to easily be able to handle x-ray computed tomography data sets in the 2 and 3-gbyte range in RAM since we now have access to all of the available RAM. But I am having major problems - sluggish (and stoppage) operation of the program, inability to perform certain operations, etc.
Here is how I store the 3-D data that consists of a series of images. I store each of my 2d images in a cluster, and then have the entire image series as an array of these clusters. I then store this entire array of clusters in a queue which I regularly access using 'Preview Queue' and then operate on the image set, subsets of the images, or single images.
Then enqueue:
I remember talking to LabVIEW R&D years ago that this was a good way to do things because it allowed non-contiguous access to memory (versus contigous access that would be required if I stored my image series as 3-D array without the clusters) (R&D - this is what I remember, please correct if wrong).
Because I am experiencing tremendous slowness in the program after these large data sets are loaded, and I think disk access as well to obtain memory beyond 16 gbytes, I am wondering if I need to use a different storage strategy that will allow seamless program operation while still using RAM storage (do not want to have to recall images from disk).
I have other CT imaging programs that are running very well with these large data sets.
This is a critical issue for me as I move forward with LabVIEW in this application. I would like to work with LabVIEW R&D to solve this issue. I am wondering if I should be thinking about establishing say, 10 queues, instead of 1, to address this. It would mean a major program rewrite.
Sincerely,
Don

First, I want to add that this strategy works reasonably well for data sets in the 600 - 700 mbyte range with the 64-bit LabVIEW.
With LabVIEW 32-bit, I00 - 200 mbyte sets were about the limit before I experienced problems.
So I definitely noticed an improvement.
I use the queuing strategy to move this large amount of data in RAM. We could have used other means such a LV2 globals. But the idea of clustering the 2-d array (image) and then having a series of those clustered arrays in an array (to see the final structure I showed in my diagram) versus using a 3-D array I believe even allowed me to get this far using RAM instead of recalling the images from disk.
I am sure data copies are being made - yes, the memory is ballooning to 15 gbyte. I probably need to have someone examine this code while I am explaining things to them live. This is a very large application, and a significant amount of time would be required to simplify it, and that might not allow us to duplicate the problem. In some of my applications, I use the in-place structure for indexing
data out of arrays to minimize data copies. I expect I might have to
consider this strategy now here as well. Just a thought.
What I can do is send someone (in US) via large file transfer a 1.3 - 2.7 gbyte set of image data - and see how they would best advise on storing and extracting the images using RAM, how best to optimize the RAM usage, and not make data copies. The operations that I apply on the images are irrelevant. It is the storage, movement, and extractions that are causing the problems. I can also show a screen shot(s) of how I extract the images (but I have major problems even before I get to that point),
Can someone else comment on how data value references may help here, or how they have helped in one of their applications? Would the use of this eliminate copies? I currently have to wait for 64-bit version of the Advanced Signal Processing Toolkit for LabVIEW 2010 before I can move to LabVIEW 2010.
Don

M.Tech and Research scholar with 2.5 year LabVIEW experiance looking for profile as LabView Developer

I am M.tech Biomedical enginer and working as research scholar with 1 year experiance and having 2.5 years experiance of labview,vision builder and vision assistant.
Looking for the position of labview developer in good organization..
Mail ID:[email protected]

Hello I wanted to bump this thread up.
I fell time has come time to once again embark on a job search quest for me.
What has changed since the opening thread?:
My CLD has expired, but I intend to recertify using the CLD-R and very quickly once again to CLA. ( plan is to do it in march ).
During my last 2 years I've worked predominatnly in LabVIEW on very high speed DAQ with insane data-rates.
Learned how to do proper multi threading in LabVIEW and work with ginormous data -sets in the hundreds od GB,
Learned how to do proper 64-bit labview apps, and use memory efficiently.
Got experience working on Oil and Gas stuff. Gained Team Lead Experience.
What am I looking for:
Software Architect, Team Lead or Software Manager positions.
I'm also trying to get canadian residence, which should take me approx 10 moths to sort out, but if a job offer came sooner this could boost me.
So Canadian offers are of my particuar interest.
US jobs, unfortunately I do not have a work permint in US, which excludes me from 90% of the jobs on this forum, if any employer has the ability to sponsor please contact tme.
I'm an EU citizen and I do browse the EU offers all the time, but if my profile is interesting to you please don't hesitate and contact me and I'll send you my resume.
Regards,
WibJ

MATLAB DataPlugin for 64-bit LabVIEW

Similar Messages

Maybe you are looking for