Control design and simulation palette

[Jacobson-ni]

Alij,

I would have to know a bit more about your setup but the Control Design and Simulation Module is not supported on 64-bit LabVIEW so I am not surprised that the module installs under the x86 folder.

http://www.ni.com/white-paper/10383/en/

I would not expect copy pasting between those two folders to work but I have seen some strange behavior from our unsupported products.

[alij]

well, im so surprised now.

my windows is 7 (64 bit )and also im using NI labview 64 bit 2013 . I installed controll module using 2013CDSIM.exe from this site and activate it . now after checking your link  I understand it says not suported for 64 bit labview! now I wonder thats why it is installed on that folder!! (program files x86) 

i have to tell u i copy pasted the files (from program files x86) to the main folder of ni labview(program files) and then the module added to lab view perfectly , i dont know it will work in real but now for example i can add a pid with no error or i can add a  a transfer function in my projects ! before copying the files, the control design was empty.

i have to say last week i tried to add a module of control & simulation named "2013PIDFuzzy.exe" (about 80 mb)after downloading it says my labview isnt 32 bit and cant install this module on 64 bit but for 2013CDSIM.exe the module installed properly when my labview was 64 bit and didnt show me any error however it installed it in wrong folder.

so are u telling me if i use for example a pid controller in my project ( for example controlling a temperature) it wont work?it is only the shape of pid in ".vi" files? not the actiual pid?
i can add a picture of my labview controlling module  if u are intrested

thx for your reply

[Jacobson-ni]

---

@alij wrote:

i have to tell u i copy pasted the files (from program files x86) to the main folder of ni labview(program files) and then the module added to lab view perfectly , i dont know it will work in real but now for example i can add a pid with no error or i can add a  a transfer function in my projects ! before copying the files, the control design was empty.

---

You are in virgin territory now.  As an NI employee I will say that what you are doing is unsupported and has a strong potential to really mess something up. Basically if something goes wrong know that there is almost nothing we can do to help you out.

As an interested LabVIEW user I will say frankly that I'm shocked that what you did worked, tell us how everything works out for you.

[alij]

I DO not need labview supports man,it really takes more than a month for me to fix this. now i see says not supported for 64 bit , if i know that i wouldnt purchased this 64 bit program and also control module i would go for 32 bit . what i want is only work properly .if they wanna really support  they would make this module work for 64 bit instead of telling us about how much 64 bit faster or better...
 here is a attached picture for my labview control simulation

Alij
Electrical Engineer

[alij]

u must know , control and simulation module didnt have the same files compared to ni labview main program,  hence after copy pasting there is no file to overwrite in main folder  , as far as u dont owerwrite any files there will be no program issue 

[Blokk]

If it was just that simple if you do not overwrite files you are safe... This does not guarantee you would not have possible problems later.

And instead of complaining about compatibility issues, why do not you just download the 32 bit version of LabView? In general, the 32 bit version is just OK, unless you want to address memory above the 32 bit limit (~4 gigabyte).

FYI from a NI whitepaper:

Q. If I own a copy of LabVIEW 32-bit, do I need to purchase a separate license for LabVIEW 64-bit?
A. Every customer who purchases LabVIEW 2009 or later has a license for both the 32- and 64-bit versions.

Compatibilities:

http://www.ni.com/white-paper/10383/en/

[Jacobson-ni]

Alij,

You can even have both 32 and 64-bit LabVIEW installed on the same machine.  Usually I recommend using 32 bit unless you are developing a vision application (I am sure there are plenty of other good reasons as well) but currently our 32 bit support is just plain better which is why I use 32 bit on my machine.

[alij]

I just wanned to say module control could be supported in 64 bit with a little bit change in installation path only.

[Blokk]

I am sure there is a good reason why it is not supported. It has nothing to do with the path itself.

[altenbach]

---

@alij wrote:

so are u telling me if i use for example a pid controller in my project ( for example controlling a temperature) it wont work?it is only the shape of pid in ".vi" files? not the actiual pid?

---

Any part of the toolkit that is plain LabVIEW will just recompile and will work. Also everything will show up in the pallettes as you noticed. However, any part of the toolkit that relies on a dll will be broken. IF the toolkit could just be recompiled for 64bit, NI would have done it long ago and would fully support a 64bit version. The fact that they are not offering a 64bit version indicates that there are incompatibility issues, you just haven't bumped into them.

As mentioned before, the simplest (and correct!) solution is to install LabVIEW 32bit, then reinstall the toolkit. You are seriously messing up everything by manually copying stuff between system folders. Since you did not even know the important difference between the plain "program files" and the "...(x86)" version, I can guarantee you that if you continue on your current path, you'll soon have to reformat the HD and install the OS from scratch. You just don't mess with system folders. Period.