Solidwork x64 and labview 32 bits compatibility?

Hello community.
I'm with a project where I want to make the connection with Labview 32 bit and 64 bit Solidwork to control motors with LabVIEW, I have been following many tutorials and I get to create everything you need but when you run the VI does not move nothing SolidWork thousand times and reviewed the steps and is desesperate. Ruling out any option and I wonder if these two shows are 32 and 64 bits can be the cause of not getting the communication with these two programs. I hope your help. regards
Es un placer echar una mano siempre( Base de una sana convivencia). Si mi respuesta te sirve por favor agradecemelo con un Kudo
Un especial saludo a mis hermanos latinos. Un mundo mejor es posible.

Does this help?
http://digital.ni.com/public.nsf/allkb/71E9408E6DEAD76C8625760B006B6F98
Q. Can I run an executable built with LabVIEW 64-bit on a 32-bit PC?
A. You cannot run the LabVIEW 64-bit Development System, Run-Time Engine, or executables on a 32-bit PC.
Q. Can I run an executable built with LabVIEW 32-bit on a 64-bit PC?
A. Windows can run 32-bit executables on a 64-bit PC. Therefore, the LabVIEW 32-bit Development System, Run-Time Engine, and executables can be run on Windows 64-bit.
Q. Can I have both LabVIEW 32-bit and LabVIEW 64-bit installed on the same 64-bit machine?
A. Yes.
Q. Can I build a 32-bit version of an executable from the LabVIEW 64-bit application builder?
A. There currently is not an option to create a 32-bit version of an executable from the LabVIEW 64-bit application builder.

Similar Messages

Fieldpoint and Labview 64 bit - why is the LabVIEW Support missing from MAX and the Measurement I/O Pallette?

I am running Labview 2010 on a Windows 7 virtual Machine, I have installed Fieldpoint 6.0.7 with all the appropriate support. The VIs are in vi.lib. BUT, MAX doesn't show the LabVIEW support as existing, and the Measurement I/O pallette doesn't have the Fieldpoint VIs linked into it.
Anyone out there with any idea what I might need to do to get these seen? I've uninstalled, re-installed, installed only sections, and so far - no sign of these VIs appearing.
So, any ideas?

Not quite. I can see Fieldpoint, but not the LabVIEW support section.
The first screenshot is from my 32-bit system, the second is the one from the 64-bit system.
Attachments:
Fieldpoint Screenshot 1.JPG ‏20 KB
Fieldpoint Screenshot 2.JPG ‏15 KB

LabVIEW 2009 x64 and application builder

Hi
My organisation has just got a site licence for LabVIEW so I have just installed 2009 x64.
My question is this:
If I build applications written using LabVIEW 2009 x64, will they only run on 64 bit computers? I would test this but both my computers are 64 bit machines. I have had a brief look through the build specs but there doesn't seem to be anything about 32/64 bit compatibility.
thanks.
J
Solved!
Go to Solution.

Does this help?
http://digital.ni.com/public.nsf/allkb/71E9408E6DEAD76C8625760B006B6F98
Q. Can I run an executable built with LabVIEW 64-bit on a 32-bit PC?
A. You cannot run the LabVIEW 64-bit Development System, Run-Time Engine, or executables on a 32-bit PC.
Q. Can I run an executable built with LabVIEW 32-bit on a 64-bit PC?
A. Windows can run 32-bit executables on a 64-bit PC. Therefore, the LabVIEW 32-bit Development System, Run-Time Engine, and executables can be run on Windows 64-bit.
Q. Can I have both LabVIEW 32-bit and LabVIEW 64-bit installed on the same 64-bit machine?
A. Yes.
Q. Can I build a 32-bit version of an executable from the LabVIEW 64-bit application builder?
A. There currently is not an option to create a 32-bit version of an executable from the LabVIEW 64-bit application builder.

SolidWorks x64 Edition up and running on Mac Pro

I have the 64-bit version of Solidworks running on my Mac Pro and it's a screamer!
I used Solidworks 2007 x64 Edition on Windows XP x64 Professional on my Mac Pro for a solid 3 hours today at work. I had no problems other than a slow SATA hard-drive issue that is well known and remains unfixed on my machine. However, once Windows has loaded the registry with the program guts it runs like a top, just don't expect it to load up a program for the first time blazingly fast and you'll be fine.
Be that as it may, even with all the hardware issues I still have, SolidWorks is AWESOME on the Mac Pro, even better than any other Intel boxes I've used previously. To be fair, I don't have any experience with SW 2007 x64 on real XP x64 box.
(I posted this on another thread earlier, but at the time I didn't know what I was doing. I felt this information would be of better use under this category.)
For those who want to do this and run the x64 version of XP here's the drivers and the drill:
My Windows software is sourced from a free download of x64 120 day trial version from Windows.
Interestingly enough, I called Microsoft and asked what happens after 120 days, the answer was...."I don't know"...
weird.
Anyway, for those who don't know how to get the format of the download file to be correct for Boot Camp to recognize it as a Windows CD, here's the procedure.
This is all done on the Mac Pro.
1. Download XPx64 from: http://www.microsoft.com/windowsxp/64bit/facts/trial.mspx
2. Open Disk Utility
2. Double click downloaded file: WS03SP1RTM_1830_PX6EN.iso (this will allow you to see it in Disk Utility)
3. In Disk Utility select the WS0...EN.iso file mentioned previously and click the "convert" button.
4. When the "Save as" box pops up set the location to wherever you want ( I named the file the same name w/o the .iso extension and put it on my desktop) and set the Image Format to "DVD/CD master", Encryption to "none"
5. After saving the file, it will show up with a new extension *.cdr. Double click this file in the Disk Utility drive list.
6. After Finder finishes launching the file, go back to Disk Utility and select your new *.cdr file and click the Partition button to the right.
7. Once in the partition window, select Options and set the partition scheme to "Master Boot Record", hit OK.
8. After getting back in the partition window, select Volume Scheme and set to "1 partition", The size should be around 558.62 MB (don't worry about the format set to mac OS extended and the other greyed functions)
9. Select the Burn icon, insert your CD-R, set your post burning options, and have a Coke and a smile. Verify the file format is ISO 9660 file system by selecting the "get info" on the CD under "Finder".
**TIP #1 - make sure you've printed out the e-mail from Microsoft outlining the setup instructions and including the CD-Key. Don't be like me and get 98% through the Windows setup where it asks you for CD-Key and have to power off the computer and get it out of OS X.**
**TIP #2 - Since you are using an Apple keyboard Windows doesn't seem to be able to use it on the blue screen portion of the install. My remedy (after assuming the install locked up 6 times in a row) is to go find a cheap-o usb keyboard and mouse lying around (probably standard Microsoft stuff in your closet) and plug it in to be back of your Mac Pro tower. You do not need to go through the Mac OS hardware setup thing that pops up.
10. After printing out your MS instruction e-mail and plugging in your keyboard and mouse (see above), launch Boot Camp (don't even try to use the driver CD it makes, it's useless for XP x64) and install XP x64.
11. Have a beer and a smile, you will need the alcohol in your blood from here on out.
**TIP #3 - go buy 2 or 3 magazines and get a comfortable chair.**
12. Install Windows, follow the Boot Camp Beta instructions carefully until you get to the part where you install the driver CD. It won't work.
13. Follow these links to get the x64 drivers:
Audio: http://www.realtek.com.tw/downloads/dlhd-2.aspx?lineid=2004052&famid=2004052&ser ies=2004061&Software=True&title=HD%20Audio%20CODECs
Nvidia Graphics driver for the 7300GT (remember, this is for Win XP x64 edition so it's not the same as the regularly posted 32 bit version):
http://www.nvidia.com/object/winxp64_91.47.html
LAN drivers (Be sure to get the x64 version):
Download PROEM64T.exe from the Intel website
13. Update Windows.
**NOTE: I am still having the same driver issues as others that have installed XP x64 on a Mac Pro, for example the Apple keyboard and mouse function, but the CtlAltDel and Eject CD disk remain non functional.**
14. Install SolidWorks 2007 x64 from the included DVD in your software update box that came in the mail last week.
15. GO TO BED...IT'S 4:30 am!!!
Mac Pro Mac OS X (10.4.7) Microsoft XP x64 Professional
Please correct me on any driver postings if they are in error or missing. These are the ones I used and they are working for me. I do not claim to be a guru (this is only my 7th day of using Macintosh in my entire life), I'm just a CAD guy that has a MacNut for a boss. It was either adapt or die, so I'm hapilly adapted.
Mac Pro Mac OS X (10.4.7) Microsoft XP x64 Professional

Alright CT, here's the deal.
You'll need to update windows first, they have the HD USB audio device driver update on Windows Update. After this, install the RealTek driver you downloaded earlier. Don't worry about windows saying it found a device but can't find the driver for it, that'll be fixed when you run the Realtek install program.
As far as the broken stuff in Device Manager, it's the usual stuff everyone has (be sure to go to "view", "show hidden devices" to see all the stuff) :
-USB human interface device
-Other device
-unknown device x3 (you will note there is also one unknown device on the Mac os)
-Intel(R) 5000 Series Chipset PCI Express x4 (Port 3 thru Port7)
As far as performance goes, BIG IMPROVEMENT! I did the slipstream fix using the 64bit drivers (obviously) and found out the hard way that you do infact have to use Boot Camp and delete and recreate the partition for a reinstall.
(tried to install on top of existing installation twice...failed twice. Suck!)
I used the picture guide located at:
http://st118.startlogic.com/~macproxp/index.html
I don't understand all the super-geek evaluation stuff when using the recommended evaluation SiSoftware Sandra, but it looks like the drive is listed as a:
ST3250824AS (P)ATA
I thought this driver was supposed to turn it into a SATA drive. Maybe it did and I'm just an idiot. So, I downloaded HD tune (give me a chart anyday over a bunch of gobbledy-gook numbers & letters) and installed it.
Here are the numbers after making about 40 copies of a 59.8 MB file on the desktop to the desktop (to try and tax the processor/hd):
HD Tune: ST3250824AS P Benchmark
Transfer Rate Minimum : 0.6 MB/sec
Transfer Rate Maximum : 66.9 MB/sec
Transfer Rate Average : 20.2 MB/sec
Access Time : 13.0 ms
Burst Rate : 152.4 MB/sec
CPU Usage : 1.5%
This is no where close to 3GB/sec, but a helluva lot faster than 35KB/sec like before, pretty dang fast nonetheless.
Hopefull someone smarter that me can figure out if I'm at the fastest I can go or not.
-MSW

Using both, LabVIEW 32-bit and 64-bit

Hi Guys,
I have a requirement where I have to interface with a camera using LabVIEW 64-bit (because the dll provided is for 64-bit system). At the same time, I have to communicate with several variables via OPC Server using LabVIEW DSC, which is only available in 32-bit. I was told that I cannot run one same program but utilizing LabVIEW 32 and 64 bit simultaneously. Hence, I would like some advice, especially on the architecture, on how should I approach this.
Advices are much appreciated.
Shazlan

Are you sure that you can't have a 32-bit compatible dll for your camera? It would really make your life easier.
Also if you only use the DSC module for the OPC function, maybe you could look for a different set of OPC functions that support 64-bit.
In the end if you really have not choice but to use DSC module and use the 64-bit dll for the camera, you will need to apps, one in LV32 and one in LV64 and you will have to decide which one is the main one and find a way to communicate between them, TCP comes to mind, also VIServer, I have never tried VIServer between a LV32 app and a LV64 app but my bet is that it should work seamlessly.
Good luck!
When my feet touch the ground each morning the devil thinks "bloody hell... He's up again!"

Have the installers for Flash x64 bit and Flash x32 Bit been combined?

Up until just recently there were always 2 different installers for Flash. The 32 bit version and the 64 bit version. Has Adobe now combined the two separate installers in to one? Or do I still need to find separate x64 and x32 bit installers? I seem to be able to find the installer for 11.3.300.265 but it no longer says it is for 32 bit or 64 bit.
I have been searching for some sort of a message or update put out by Adobe Flash announcing that they have combined the two installs, something that should be on the download page in big bold letters so that we know about the change and know we can stop keeping 4 separate installers and reduce it to two.
I am an IT support professional and one of my jobs is to keep up to date with the full installers for things like Flash, Adobe Reader, Shockwave etc so that we can supply our customers with the latest updates, no spam involved and no tricks to install additional UNNEEDED and UNWANTED junk ware such as the MacAfee Security Scan Plus or Google Tool Bar that they try to trick you into installing, by pre-checking it, AN EVIL THING TO DO TO UNKNOWLEDGEABLE USERS, and the main reason we have to find and download the FULL INSTALLERS sans the crap ware ourselves and cannot trust Adobe to provide us with Crap Ware Free installs etc. ( For Shockwave we have to manually install it ourselves, a very time consuming thing since it ALWAYS tries to trck the user in to installing EVIL CRAP WARE such as Google Tool Bar and Norton's Security junk. If these were not EVIL programs and crap ware then they would not need to pre-check their installation, but they must obviously be EVIL CRAP WARE since they have to resort to tricking usurers in to installing them via a pre-check.
Thanks,
Ralph Malph

Hi,
I would recommend posting this qiery in the Adobe Reader / Adobe Flash Player forum.
Thanks

LabVIEW 64-bit support for modules and toolkits

I've just finished installing the 64-bit version
of LabVIEW 2009 under 64-bit Windows 7 Professional. However as noted
above very few toolkits and modules are available for this
version. Some of those MIA include MathScript, VI Analyzer, Advance
Signal Processing Toolkit, etc. I realize development and testing takes
time but think it's reasonable to ask that NI put up a table or chart
of toolkits and modules clearly showing which ones are
available/compatible with 64-bit LabVIEW, as well as timelines for when
these will be available.
(Apologies for cross-posting from the Ideas Exchange but that board doesn't seem to get much traffic...)

Hi Magma,
The Vision Development Module is currently the only module available for 64-bit LabVIEW. We currently have not released a timeline for other modules, but we are working on other 64-bit support. The links below summarize the current functionality of LabVIEW 64 bit.
LabVIEW 64-Bit vs. 32-Bit Applications FAQ
http://digital.ni.com/public.nsf/allkb/71E9408E6DEAD76C8625760B006B6F98
Announcing 64-bit LabVIEW
http://zone.ni.com/devzone/cda/tut/p/id/10184
Nick Keel
Applications Engineering
National Instruments
Nick Keel
Product Manager - NI VeriStand and Model Interface Toolkit
National Instruments

Palm Pre and backwards Palm app compatibility? 64 bit OS - Vista or XP Pro -- compatibility -- ?

I am brand new to the board, so please bear with me if these questions have already been addressed elsewhere.
The announcement of the Palm Pre might have just retained me as a Palm loyalist. I was starting to look at BlackBerries, etc. for my next phone upgrade. And then along comes the Pre.....which looks to be a Very Good Thing. However, I have a couple of questions:
1. Will the Palm Pre be compatible with the apps that I currently have loaded onto my Palm TX? Will a simple transfer of apps / data from the TX to the Pre be possible?
2. Will I be able to sync the Pre with my Vista 64 bit laptop, or with my XP Pro 64 bit desktop? Or does the Pre still lack 64 bit compatibility? (Man, I hope that it will "do" 64 bit........)
To anyone who knows -- thanks.
Post relates to: Palm TX

Thank you for the responses in both cases, smkranz. It's greatly appreciated.
Yes -- my Palm TX has served me well for a few years. It's still functioning quite nicely. However, I'd hate to have to manually re-enter all of the data that's stored in it into another device. Plus I wouldn't want to give up several of the apps that I have installed on that device.
IMO, in many ways the TX 'anticipated' the Pre -- rotating screen (albeit manually set), and a list of other features. Heh -- but these days, if a device is six months old -- then it's yesterday's news. ;-) The TX is a circa 2005 era device, IIRC. So it's an ancient historical relic in today's world. But I still like it. A lot. Few electronic devices that I've ever had the pleasure of owning have been as useful to me as the TX has. That's why I hated the idea of switching brands......but I didn't see much choice, until now. The Pre looks to be a real shot in the arm for Palm. And for my continuing to use Palm's devices into the future. The BlackBerry Strom was a real disappointment. And I don't like iPhones. But I don't think that the Pre is going to disappoint. If the device lives up to its promise: then I think that we'll have a top-notch winner on our hands. A great replacement for my venerable TX.
Heh -- the first thing that I loved about the TX was the ability to download & read ebooks while traveling. One TX in the pocket is a lot easier to carry around than a suitcase full of hardback novels. The Pre looks to take that 'convenience factor' to a whole 'nother level..........
Now......if only I can get the legacy Palm OS apps to work with it, and it syncs up with my 64 bit PC's: then everything will be right with the world.........
Thanks again for the help.
Post relates to: Palm TX

Report Generation Toolkit Compatibility with Microsoft Office 2013 and LabVIEW 2012

Hello community,
on this page there is shown the Report Generation Toolkit Compatibility with Microsoft Office and LabVIEW.
In our company we use actually LabView 2012 and it works perfectly with MS Office 2010.
Has anyone ever tried the "Report Generation Toolkit" of LabVIEW 2012 with MS Office 2013? Does it really not work? Has anyone an emirical value for this topic?

Hi digital_badger,
as you sure have seen in the link it is not officially supported by NI, which means to you one of the following things:
1. You could upgrade your LabVIEW and your Report Gerneration Toolkit to Version 2014 and use MS Office 2013
2. You could just try it with MS Office 2013 which might work but if it's not working you don't get any support from NI.
Even if someone tried it already and it worked for him does not mean that it will work on your machines. It is possible that on some of your machines it could work but not on others. Their can be a lot of problems while playing around with unsupported setups.
3. You could leave your setup as it is and stick to your MS Office 2010.
I hope I could give you a good answer to your question

BasicTx and BasicRx daughter boards compatibility with USRP2920 and LabView

I want to know that BasicTx and Basic Rx daughter boards from Ettus research are compatible with USRP2920 and Labview or not.
Also do these boards supports variable gain or not? Please confirm
Thanks
JK
Solved!
Go to Solution.

They will work but you need to use property nodes to configure them. Ther is no LO so ther is no center frequency parameter. I and Q are separate channels so you will need to break them apart and treat them as such. There is no gain because the boards essentially provide access to the ADC.

Lenovo IdeaCentre A720 - Clean Installation Windows 8.1 Pro x64 and Office 2013 x64

GUIDE: Clean Installation Windows 8.1 Pro x64 and Office 2013 x64
Note: for a good performance is recommended to use a SSD for Windows with a minimal of 128GB and use the HDD for Data
Driver up to date - Sep 2014
First you need to download and have ready the following softwares:
Classic Shell V4.1: To get back the Start Button like Windows 7
http://www.fosshub.com/Classic-Shell.html/ClassicShellSetup_4_1_0.exe
Broadcom BT for Windows 7 (64-bit) - to enable dongle, Windows 7 Live DVD and USB Drive.
http://download.lenovo.com/consumer/desktop/h1100174.exe
Realtek Cardreader Driver Windows 8.1 (64-bit) V6.2.9200.29070. To be able to use the card reader
http://download.lenovo.com/consumer/desktop/h1101061.exe
NV VGA Driver for Windows 8.1 (64-bit) V340.52. Latest video driver for NVIDIA video cards
http://www.nvidia.com/content/DriverDownload-March2009/confirmation.php?url=/Windows/340.52/340.52-n...
Lenovo Silver Silk Keyboard Driver for Windows 8.1 (64-bit) V1.05. To be able to see when Caps Lock or Number Lock is press
http://download.lenovo.com/consumer/desktop/h1100842.exe
Yuan MC907 TV Tuner Driver for Microsoft Windows 7 (64-bit) V6.14.10.416. To be able to use the Yuan TV card
http://download.lenovo.com/consumer/mobiles/tvt129w8164.exe
OSD APP for Windows 8.1 (64-bit) V1.1.06. To be able to use UP or Down Volume for Touch keys in the screen.
http://download.lenovo.com/consumer/desktop/h1100547.exe
Windows 8.1 x64 Installation DVD and Office 2013 x64
Follow this procedure for the installation:
Install Windows 8.1 Pro x64 using the general or personal key
Just to avoid install an old Video Driver from windows update, disable the Wi-Fi or Interned connection
Install Office 2013 x64
Install the Video Driver “340.52-notebook-win8-win7-64bit-international-whql.exe” just let the setup to uncompress the files in “C:\NVIDIA” folder, do not continue to avoid the installation of other software that you may never use. Go to “Device Manager” and Right click properties in the display adapter, press “Driver” - “Update Driver” select browse my computer and give the path “C:\NVIDIA” press next and close after installation finish
Enable Wi-Fi and open Control Panel – Programs – Turn Windows features on or off and select “.NET Framework 3.5” hit OK, after the installation finish, reboot PC
Install “ClassicShellSetup_4_1_0.exe” follow instruction and configure the way you may like
Run file “h1101061.exe”, unselect “Install Realtek Card Reader Driver” and press finish. Path for driver is "C:\EXEBuild\Realtek Card Reader Driver”. Go to “Device Manager” and Right click properties in the unknown devices, press “Driver” - “Update Driver” select browse my computer and give the path “C:\EXEBuild\Realtek Card Reader Driver” press next and close after installation finish
Install “h1100842.exe” backup driver location is “C:\EXEBuild\Lenovo Silver Silk Keyboard Driver” after installation is done, go to “C:\Program Files (x86)\Lenovo\Lenovo Silver Silk Wireless Keyboard” and Right Click in the file ‘”skd8861.exe” properties – compatibility – change setting for all users and select run compatibility mode for “Windows 7” press OK and OK
Run “tvt129w8164.exe” unselect “Install TV Tuner” and press finish. Path for driver is “C:\drivers\TV Tuner (Geniatech, Yuan, AverMedia)”. Go to “Device Manager” and Right click properties in the unknown devices, press “Driver” - “Update Driver” select browse my computer and give the path “C:\drivers\TV Tuner (Geniatech, Yuan, AverMedia)” press next and close after installation finish
Run “h1100547.exe” unselect “Install A7 OSD APP now” and press finish. Path for driver is “D:\EXEBuild\A7 OSD APP”. Run the file “setup.exe” do not reboot the PC and ensure the folder been created during the installation “C:\Program Files (x86)\Lenovo\Lenovo BrgVolOSD” with this two files “BrgVolOSD.exe” and “CD_DLL.dll”, if this fail go to next step, if not, avoid next step. Normally a successful installation of this file depend of “.NET framework 3.5”
Go to control panel and uninstall “Lenovo OSD”, run the previous “setup.exe” and during the process of the installation, be ready to make a copy for the temporal file name “setup.msi” created in  “C:\Users\YOURUSERNAME\AppData\Local\Temp”, copy file “setup.msi” in “C:\” and run CMD in administrator mode and go to “C:\” using “CD \ + ENTER”, now use the following command “C:\msiexec.exe /a c:\setup.msi + Enter” the folder “C:\Program Files (x86)\Lenovo\Lenovo BrgVolOSD” with this two files “BrgVolOSD.exe” and “CD_DLL.dll” will be created
Create a shortcut “BrgVolOSD” and copy this in the startup folder “C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp”
Update Bluetooth driver using windows update if Windows detect the dongle, if not go to next step
If Bluetooth is not detected, mean that the actual hardware somehow is disabled. In order to enable, boot the PC with a Windows 7 live DVD with the USB drive installed in the PC. After PC been running with Windows 7 live, Install the file “h1100174.exe” previously copy in the USB drive. Use the USB drive also as installation path for the Bluetooth software, when the installation is done, look in the folder “X:\Program Files\Lenovo\Bluetooth Software” and run the file name “BTTray.exe”, press right click in the Red Bluetooth icon on the taskbar to enabled the Bluetooth dongle. Reboot PC in Windows 8.1 without any DVD media inside, this time Windows 8.1 will be able to recognize the Bluetooth and install the respective drivers.
     Another way, install the latest release from Broadcom BTW_12.0.0.9820 from the following link:
                                                                        BTW_12.0.0.9820.zip
    directly in Windows 8.1. Remember if the software is uninstall the Bluetooth will be disabled and
     Windows will not be able to see the device in the “Device Manager”
Last step, use your own Windows 8.1 Pro Key and Office 2013 key to register and activated your legal copy of the Microsoft software’s.
Final, enjoy.
This guide was creates for me to help peoples like me in this community.

bump

Teststand 4.1 and LabVIEW 8.6 taking more time to launch?

For lauching the LabVIEW 8.6 steps in TestStand 4.1 its taking almost 7 to 10 seconds to load or refresh the LabVIEW terminals. Everytime while clicking on the LabVIEW steps its taking the same time..... Its a kind of irritating to write code in TestStand. I dont know what happening inside.. but in TS 4.0 its pretty fast. Even I tried with using runtime engine option.... very little bit of changes I found... in this case I cant able to edit the LabVIEW code.
Is there any method to make it faster to repond. Or its because of LV 8.6 the way it loads.?
Vijay

There is a known issue with LabVIEW 8.6 and any version of TestStand that will cause a significant delay updating the display after selecting a LabVIEW step in the sequence editor. The issue is described in KnowledgeBase 4PH891T3: Known Compatibility Issues with TestStand and LabVIEW 8.6, and a patch is available.
Please try to install the patch for LabVIEW 8.6f1 and see if it fixes the behavior you are experiencing. If it does not, please let me know and we will agressively investigate the issue. It would be helpful if you could provide examples or instructions to reproduce the problem.
Thanks!
Josh W.
Certified TestStand Architect
Formerly blue

Reading fits files in labview 64 bit

I need to read fits data files in labview on a 64 bit machine. I developed an application in labview 2012 (32 bit version on a win 7 x32 machine). This vi will not run on a win7 x64 machine. The problem is with the gfitsio library I used to read the files (downloaded from http://heasarc.gsfc.nasa.gov/docs/software/fitsio/fitsio.html). It seems they will not work with labview x64. I installed labview 32 bit on the same machine & tried to run the vi with that, but no luck.
Any ideas would be appreciated,
Thanks,
Joe

It appears the FITS libraries are 32-bit, so they cannot be called from 64-bit LabVIEW. You should be able to call them from 32-bit LabVIEW on a 64-bit machine. The only difficulty you may run into is locating the DLL. 64-bit versions of Windows put DLLs in different places than 32-bit. Check you system path and make sure your DLL resides in the search path. You can also load the DLL explicitly using Windows Kernel32.dll calls before loading code which calls it. This is awkward, but works in some cases.
Since the source code is available, you may be able to create a 64-bit DLL that 64-bit LabVIEW could use. I am the wrong person to cousel you on how to do this, but it should be possible.
If you need more info, please ask.
This account is no longer active. Contact ShadesOfGray for current posts and information.

Labview 64-bit running with 32-bit addons

I ran into memory problem loading som data files, and I tried a workaround by installing Labview 64-bit, but found that the add-ons was not installed with it.
Now I needed to use sound and vibrations toolkit, so (being maybe a little too creative) I copied that toolkit over to the 64-bit Labview folder and everything seems to run.
I can load the files and do my data analysis with no errors.
Now the problem is that I don't really get how a 32-bit add-on can access the memory from the 64-bit core Labview. Does anyone have any ideas on why its running and why I don't get a memory access error.
The results looks ok, but I don’t really trust them, due to the above mentioned problem in accessing memory between 32-bit and 64-bit.
regards
Henrik
Solved!
Go to Solution.

Hi Henrik.
When using LabVIEW 32-bit on a 64-bit machine, all your VIs would run through the Windows-on-Windows emulation layer (WOW64) and this is also why we still have memory limitations on a 64-bit OS.
When you are using LabVIEW 64-bit, and using a 32-bit toolkit, what's actually happening is the 64-bit LabVIEW kernel is recompiling the 32-bit VI into a 64-bit VI. Doing this changes the inherent memory characteristics and performance of the Sound and Vibration VI's (and all 32-bit VIs, for that matter). The newly converted 64-bit VI's, then, are being executed in the native 64-bit LabVIEW kernel.
However, I would strongly advise you to install the toolkit the normal way. In the following document, you can see, that the Sound and Vibration Toolkit / Measurement Suite is in fact supported by a 64-bit version of LabVIEW.
National Instruments Product Compatibility for Microsoft Windows 7
After you install LabVIEW, you need to reinstall all your add-ons and drivers in order for that toolkit / driver to work with LabVIEW. When we install toolkits / driver, we only install support for the LabVIEW versions installed at that time.
I hope this helps.
Best Regards
Alex E. Petersen
Certified LabVIEW Developer (CLD)
Application Engineer
Image House PantoInspect

Do I need to install x64 and x86 versions of SQL Server 2012 SP2?

Hi,
I have installed x64 version of SQL 2012 SP2. Do I need to install x86 version of SP2 as well?
(I have some x86 components installed as well that came with various things like SSDT-BI and/or Visual Studio installations.)
When I click "SQL Server Installation Center (64-bit).lnk" shortcut and run "Installed SQL Server features discovery report", it says "Microsoft SQL Server 2012 Setup Discovery Report".
When I click "SQL Server Installation Center.lnk" shortcut and run same, it says "Microsoft SQL Server 2012 Service Pack 1 Setup Discovery Report".
Both reports say the same thing: the installed version is 11.2.5058.0, which is SP2.

Hi,
I have installed x64 version of SQL 2012 SP2. Do I need to install x86 version of SP2 as well?
(I have some x86 components installed as well that came with various things like SSDT-BI and/or Visual Studio installations.)
When I click "SQL Server Installation Center (64-bit).lnk" shortcut and run "Installed SQL Server features discovery report", it says "Microsoft SQL Server 2012 Setup Discovery Report".
When I click "SQL Server Installation Center.lnk" shortcut and run same, it says "Microsoft SQL Server 2012 Service Pack 1 Setup Discovery Report".
Both reports say the same thing: the installed version is 11.2.5058.0, which is SP2.
Hello,
No you dont have to install X86 version
SQL server 2012 installable will install SQL server as per process architecture of your machine. If it is 32 bit machine it will install 32 bit version and for 64 bit it will install 64 bit version. installable has facility for both
Even on 64 bit machines some files, which always work in 32 bit compatibilyt mode, will be installed as well andand they go to SQL server (X86) folder. BIDS, SSIS always by default works in 32 bit compatibility mode.
If report says version as 11.2.5058 it means component is patched to SP2
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

Solidwork x64 and labview 32 bits compatibility?

Similar Messages

Maybe you are looking for