07-23-2013 10:14 AM
For this project we have a PLC connected to a PLC server and we are using KEPserver which is an OPC server program to interact with the PLC server. I am currently in the process of updating and fixing some features of the LabVIEW program that is sort of a user interface. This is my first time actually working with Network-controlled shared variables so this project is a bit of a learning experience. The program had several shared variables to begin with and we added a few to the server that I am having problems implementing inside the LabVIEW program.
When I added the new variables, I copied and pasted from variables that were previously made and of the same type. I then changed the name and used the same address that was used in the OPC server program. I verified all the settings were correct in the multiple variable editor. After compiling the program does not actually change the value on the shared variable and it doesn't cause an error either. The program is being ran off of a LabVIEW run-time engine on a different computer. The addresses the shared variables are being bound to are localhost addresses which for one of the variables I would like to add the address is: \\localhost\Rack\_OPC1.Rack.DL405.C.B1_Continuous. Off of the troubleshooting I have done, it seems like I am having a problem with deploying the new variables. When I try to deploy them I receive an error stating "Unable to resolve from current dialog" inside Conflict Resolution and for the Conflict message it states "Cycle detected: \\My Computer\Rack\B1_Continuous -> \\My Computer\Rack\B1_Continuous."
So I think this may be something simple I didn't know I had to do, but currently can't figure out. Thank you for any help you guys can provide in this. Please let me know if some screenshots would help, there are several screens I'm working with so I am not sure which ones would be usefull.
07-23-2013 12:37 PM
I created an exe with enhanced dsc enabled for the computer running the program and got the attached error, which has to do with the deployment of the variable.
07-24-2013 09:35 AM
I got this figured out. There was a small discrepancy in the network address that caused problems which wouldn't allow me to deploy in project manager. Then I needed to deploy the shared variables before executing on the test computer which the .exe was made for.