Control design and simulation palette

[alij]

dude messing up system files isnt such important for me 😄 i sometimes edit registry files too 😄  im ok with this .
by the way about dll files you mentioned there will be no  broken files .because the module is installed properly and i didnt use "cut" i used "copy" command .the Ni will use the main dll files which is into system folders  program files(x86) (not program file)  and document and settings settings and also use registry system which is ok when u install a progrm.
the broken files will be occured if i didnt install the module and tried to copy paste it (like portable programs from some where ) or when i wanna unistall the module i need to mannually delete the files i copied.
Thx , i did ttook my answer from this forum , i really know much than u think wht i know about windows or programming languages. i just offer a way to use it in 64 bit. if it wasnt compatible with 64bit why installation file module allowed me to install on 64 bit version of Ni?? it must not allowed me to install like "fuzzy" installion file i told in my last post it must said 32 bit needed.
as it was installed  properly it has not any incompatibility.
if u know much about the compatibility i mean the professional programming issue let me know why isnt supported

[Blokk]

"by the way about dll files you mentioned there will be no  broken files .because the module is installed properly and i didnt use "cut" i used "copy" command .the Ni will use the main dll files which is into system folders  program files(x86) (not program file)"

This is not correct, your LV x64 cannot use 32 bit dlls...

[alij]

can u give an example of a simple vi tha use that dlls ? so i can check it will work or not

[Blokk]

Sorry, right now I cannot pick any example, maybe someone can show you an example where you start to face such compatibility problems. As I see now, there is no point for further discussions, since you said you do not care about "messing with system files" and compatibility problems.

It was told you how you can work with LabView in a way which is officially supported. Of course you can play around and hack the things, but I do not see any advantage in this kind of "approach". There are certain rules because they work and make code developing easier and debuggable...specially if you have to cooperate with other LV programmers in a group...

[alij]

I didnt said hack the things , i use ediditing my regisry things for my own programs .
as im working i am facing some incompabilities , when i add control simulation loop the program will be executed suddenly :D:D so i think the only way is to install a 32bit at last
thx anyway

[altenbach]

LabVIEW makes extensive use of DLLs, e.g. for most VI's doing advanced analysis. These need to be in the correct bitness. Did you fully search the copied folder hierarchy for DLLs? Are you sure you did not miss any potential dependencies in other shared locations of the NI hierarchy? Are you sure all relevant registry entries point to the updated location? This entire discussion is a minefield and acting like the proverbial boar in the carrot patch by randomly digging and scattering stuff is insane. Good luck with the 32bit version. 🙂

[alij]

it doesnt need to updated location as i used copy not cut. the point is dll files for 64 bit is diffrent and cant be used for 64
i blame ni for letting me install module on 64 bit. im downloading 32 bit right now. a question is half of my project is done in 64 bit , can i convert it into 32 bit? can 32 bit open a 64 bit vi file ?

[Jacobson-ni]

Alij,

Should be able to open it right up.

http://digital.ni.com/public.nsf/allkb/71E9408E6DEAD76C8625760B006B6F98

The biggest problem we see when opening and running a VI made in 64 bit LabVIEW is errors that pop up because you can no longer access as much memory as your application needs

[Jeannie_Falcon]

There is a beta for LabVIEW 2016 Control Design and Simulation Module with 64-bit support for Windows, Mac, and Linux. You can sign up here: 

http://digital.ni.com/betaprogram/mainbetacust.nsf/main.htm

[a_v]

Hi 

I am working with labview 2017 evaluation version, in control and simulation sub pallet only PID and fuzzy is showing not other how to rectify it ?