Use of APT objects in 64-bit LabVIEW

I have created an APT motion control VI to control a translation stage using 32-bit LabVIEW. However, I have since had to move to 64-bit LabVIEW. I am trying to create a similar VI that will run on the 64-bit version. The problem is when I create my ActiveX container and try to use MGMotor control to connect to the motor, MGMotor Control is not in my list of creatable objects.
Is this because it is not possible to access this particular motor in 64-bit LabVIEW or am I missing drivers that I can download to update the list of creatable objects?
P.S. I am relatively new to LabVIEW but any help at all would be great!

Hi,
What is the reason you have moved to 64bit LabVIEW? It could be that this driver is not supported on 64 bit LabVIEW but this would have to be confirmed by looking at the driver's requirements. 64 bit LabVIEW currently does not support every thing that 32 bit does but this is being worked on. Can you provide some more details of this motor driver.
If you have recently installed your new version of LabVIEW then you will need to reinstall the driver again. If you can provide some more details on the driver then perhaps we can find out if it is compatible with 64 bit LabVIEW
Best regards
Matt Surridge
National Instruments

Similar Messages

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.

Random crashes when using 16 Labview with the 32 bit labview

I am using 2 versions of Labview at the same time, one is version 4 which has a camera and a weigh-in-motion scale attached to it. The second is either Labview version 4, 16-bit or Labview 3.0.1, 16-bit, i'm not sure. The sixteen bit has a data acquisition system attached to it. Its an optim electronics system and the 16-bit Labview drivers for the optim were provided by Optim electronics and so I am stuck with using the same system. When I use both these systems in tandem, the system crashes frequently, but both systems run fine independently. It usually just freezes up or says "Illegal operation performed. Contact program vendor". Its a windows error with a red cross.

So a guy goes into his doctors office and tells his doctor "Ya gotta
help me doc...it hurts when I run my head into the door like
this...OW!". Then the doctor says:
"DON'T DO THAT ANY MORE!!!"
(I promise to keep my day job...oops what job...and not go into
comedy..)
Why don't you convert all the old 16 bit code into 32 bit code and
create one application where the various parts all know about each
other? I don't think that there's any way to coordinate an old 16 bit
LV and a new 32 bit LV application so that they don't step on each
other driverwise like they appear to be doing. I don't think that the
two LabVIEW's even know that the other exists!
Alternatively, get a second computer to run the 16 bit code on and
make the two apps communicate with
each other using TCP/IP or serial.
Doug De Clue
[email protected]
cincidude wrote in message news:<[email protected]>...
> I am using 2 versions of Labview at the same time, one is version 4
> which has a camera and a weigh-in-motion scale attached to it. The
> second is either Labview version 4, 16-bit or Labview 3.0.1, 16-bit,
> i'm not sure. The sixteen bit has a data acquisition system attached
> to it. Its an optim electronics system and the 16-bit Labview drivers
> for the optim were provided by Optim electronics and so I am stuck
> with using the same system. When I use both these systems in tandem,
> the system crashes frequently, but both systems run fine
> independently. It usually just freezes up or says "Illegal operation
> performed. Contact program vendor". Its a windows error with a red
> cross.

How do I get an activeX object reference from a LabVIEW ActiveXContainer ref?

How do I get an activeX object reference from a LabVIEW ActiveXContainer ref?
I'm trying to control an ActiveX object (a Web Browser) from another VI and need to get the object reference programmatically. I can get the LabVIEW ActiveXContainer reference, but am lost on how to get the reference for the object _inside_ the container.

Hi Lee,
The reference to the container is actually also accessing the object inside the container. Use the Property Node and Invoke Node to access properties and launch methods for the object. I've attached a small example that passes the reference to a SubVI and invokes a method inside the SubVI.
- Philip Courtois, Thinkbot Solutions
Attachments:
WebContainer.zip ‏21 KB

How can I use a COM object that does not have a type library?

Hello,
I've created a com server in python for which I do not have a type library. I am able to call functions for this application in Python, TCL, I'm sure VB, etc. without the type library.
Must I have a type library registered to use this COM object with Labview? I was hoping I could simply supply the name to the refnum (or the GUID) then call functions by passings strings to the invoke node. This does not seem to be possible - am I missing something?
In the event that I cannot use a com server without a type library. Any recommendataions on how to create one? I'm wondering if I can use the same GUID and create a shell in LabWindows which generates the IDL/TBD file I need for Labview to see my
com server.
Any help is greatly appreciated.
73,
Timothy

Timothy Toroni wrote:
> Thanks for the info, however their example is labview server and
> python client. I'm going the other way. It's good to know about
> LabPython though...
>
> As of now, it seems to be there is no way to use a COM object without
> a type library from inside LabView.
Yes that is true. LabVIEW needs that to configure the Property and
Methode Nodes correctly. Otherwise it would need to have a special
Property and Method Node with a configuration dialog similar to the Call
Library Node, but a LOT more complicated. Not sure many people could
make use of that, and it would be a very tiring experience trying to get
things setup in that way, by going through the edit, test, and crash
cycle over and over again.
Rolf Kalberm
atter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

How can I write to a Siemens S7-300 PLC tag from OPC Server.vbai page by using a Knob object ?

I am using NI OPC Server and I can read Siemens S7-300 PLC tags such as thermocouple values from the PLC. Additonally I can write manually a constant value to that tag by selecting it in the NI Distributed System Manager. And I can read the written value from NI Distributed System Manager or from NI OPC Server. But I can not write any value to the S7300 PLC tags such as by using a knob object at the NI Vision Builder AI Inpection (.vbai) page.
Any help is welcomed. Thanks in advance.
Attachments:
manual_writing_to_plc.png ‏298 KB

The tutorial at the following location explains how to use Vision Builder AI as a OPC server.
https://decibel.ni.com/content/docs/DOC-18647
http://www.ni.com/white-paper/13574/en
To allow VBAI to connect to an OPC Server (i.e. act as an OPC client), you need to purchase and install the DSC Run-time System.
Once installed, you can create an OPC I/O client using the Distributed System Manager, create variables bound to OPC tags, then create VBAI network variables that are bound to these variables.
Another possible technical solution to connect to OPC Servers supporting Data Access 2.0 is to use the datasocket API in a Run LabVIEW step.
http://forums.ni.com/t5/Machine-Vision/Read-and-Write-with-OPC-through-NI-Vision/m-p/2048278/highlig...
Hope this helps.
-Christophe

Calling 64-bit TestStand Engine from 32-bit LabVIEW

I am creating my own TestStand user interface in 32-bit LabVIEW but I want to use the 64-bit TestStand Engine. I can't find a way to specify this. The read-only API property "Engine.Is64Bit" is coming back false when I run from my UI, but when I run from the Sequence editor, it comes back true. How is this determined and set at startup???

I dont think you can build a 64 bit TestStand interface using a 32 bit Labview.
FYI the the 32 bit User interface code is stored at :
C:\Users\Public\Documents\National Instruments\TestStand 2014 (32-bit)\UserInterfaces\Full-Featured\LabVIEW
The 64 bit user interface code is stored at :
C:\Users\Public\Documents\National Instruments\TestStand 2014 (64-bit)\UserInterfaces\Full-Featured\LabVIEW
You have build a 32 bit TestStand user interface and the is64bit is properly showing as false.
Try building the same project using 64 bit Labview (which should automatically pickup 64 bit TestStand components)
When you say that you run from seqeunce editor - i think you mean 64 bit sequence editor.
Ofcourse once you build your 64 bit user interface you can call a 32 bit vi (only in adapter mode set to dev and not run time).
Hope this helps.
Ravi

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

64 Bit Labview

I saw on the NI website that LAB view 2009 9.0F3 will run on Windows 7 64 bit OS, so thanks. But my question is this, we currently have version 9.OF3 running on 32 bit version of LabView, and we are upgrading the OS to Windows 7 64 bit. If we continue to use the current 32 version of LabVIEW will the program be limited to the amount of RAM it can use? We will be using 16GB of RAM.

The 32 bit versions of labview do have a RAM limitation. I believe it is 2-4 GB. (Source)
You need to use the 64 bit versions of LabVIEW in order to use more RAM, but I've heard that there are some other downsides to that.

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

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

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).

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

Bad use of NSCondition object ?

Hi everyone.
I'm trying to use Cocoa conditions to block/unblock threads but I'm a bit stuck at the moment. Here is what I want to do :
I'm working on a server program with a server class having a -start method. I want this method to return the error code of the server launching, so it cannot return before launching failed or succeeded. The point is the server is run on another thread, thus I can tell it to stop from the main thread without being stuck.
To do so... I use a NSCondition object. In the main thread, the condition is locked, the server thread is started and then a wait for the condition to be signaled. In the server thread, once it reached a consistent state, the condition is signaled. But what I don't understand is that sometimes the main thread keeps blocking on the -wait call.
Here is the start method in the main thread :
// Launch the server and blocks until launching succeeded or failed
- (CSServerStatus)start
if (![self isRunning]) {
[m_conditionConsistent lock];
m_isConsistent = NO;
[m_serverThread start];
while (!m_isConsistent)
[m_conditionConsistent wait];
[m_conditionConsistent unlock];
return ([self isRunning]) ? CSServerLaunched : CSServerStopped;
The server method in the second thread :
// The method in wich the server thread is run
- (void)threadRunner:(id)userInfo
NSAutoreleasePool *p = [[NSAutoreleasePool alloc] init];
[m_conditionConsistent lock];
[self threadTask];
[self didReachConsistentState];
[m_conditionConsistent unlock];
[p release];
// The method in wich the server thread is run
// Subclass it to do your own processing
- (void)threadTask
[self didReachConsistentState];
And the signaling method, called from the server thread :
// Called by the server thread to notify that launching has been done
// (both success and failure)
- (void)didReachConsistentState
m_isConsistent = YES;
[m_conditionConsistent signal];
When debugging, I can see the condition has been signaled, and m_isConsistent is set to YES, but the main thread is still waiting...
Does someone have any idea ?
Thanks,
Ceylo

I haven't actually used the NSCondition class. It is new. There is an older NSConditionLock class that I have used before. Still, they are both based on pthreads conditions, which I just detest - all the locking and implicit unlocking. There are a number of other threading APIs on MacOS X. In theory, they are all based on pthreads, but I'm not sure if I believe that. Look up "MPWaitForEvent" and see if that API is more to your liking. My official recommendation would be to look at Blocks for parallel tasks and stick to processes for coarser grained multiprocessing.

How to get all previous versions page contents of a publishing page using SharePoint Client Object Model 2010

How to get all previous versions page contents and other field values of a publishing page using SharePoint Client Object Model 2010?
Thanks,
Osmita

Hi Osmita,
Greetings.
Here are the links that helps you. It has code attached to it.
http://social.technet.microsoft.com/Forums/sharepoint/en-US/a0d2ab40-99ba-4368-8505-1dc559ef6469/get-content-of-previous-version-of-page-sharepoint-2010?forum=sharepointgeneralprevious
http://social.technet.microsoft.com/Forums/sharepoint/en-US/faaf419f-997e-4150-9911-48cc375c3b46/how-to-get-previous-published-versions-of-publishing-pages-in-sharepoint-2010?forum=sharepointdevelopmentprevious
Please remember to click 'Mark as Answer' on the answer if it helps you

Use of APT objects in 64-bit LabVIEW

Similar Messages

Maybe you are looking for