Compiled source code protection encryption on NI RT targets

[DucT]

Hello, 

What type of protection is there on a compiled code from labview RT, to prevent access to the source code from compiles .rtexe files?

Is there any type of encryption standard used during compilation to prevent any reverse design of the code, going from an .rtexe file in a controller (namely a sbrio controller). 

For example, I could see that the 'enable debugging' check box on the build property allows to read the source code on a debug context, from the built .exe, or .rtexe file. Would there be any other way that a customer could access IP code from the built files on an RT target?

Thanks for your replies.

[ZYOng]

By default, the block diagram of the EXE or RTEXE is removed during the compilation, unless Enable Debugging option is enabled. That's the best way to prevent IP access.

The removal of the block diagram is not limited to only EXE. You can do the same to VI when distributing the library.

Effects of Removing Block Diagram From LabVIEW VI

Security of LabVIEW VI Password Protection vs. Removing VI Block Diagrams