06-16-2023 03:06 PM
I would like to limit the way a software is installed into my controller. (deploy through labview and opkg)
is there a way to prevent user from deploying through labview?
TIA
06-17-2023 04:53 AM - edited 06-17-2023 04:54 AM
That’s fairly vague. You can disable project access on the RT controller in Max. That prevents any deployment, interactive or as executable, from a project.
But why is that even an issue? Do you let your users run LabVIEW itself and if so how are they supposed to run the software if not by deploying? If you install a compiled RT app through OPK that should not be a problem.
06-19-2023 08:32 AM
Sorry, didnt mean to be vague.
The scenario i am in is, when you deploy program through LabView, control file is not updated. No one would know what version is installed.
with opkg, control file is created. I want to prevent my team from deploying software through LabView so there is no unversioned software in our controller.
06-19-2023 08:39 AM
i think you cant have OPKG installing software if the executable exists, ie. if the last is opkg install, you wont be able to deploy through LabView unless you do opkg remove first then do LabView deploy.
This might be it.