Labview Deployment succeeds, but doesn't actually do anything

Question

Hello everyone, I've got a few questions regarding Labview deployment issues. I was brought on to an already existing project and after a few weeks, successfully finished updating the existing code to how it was expected. From that point, the goal was to deploy that code onto a Windows XP computer (Does not have any Labview components installed on it) that was hooked up to our PLC via Ethernet cable. Unfortunately, this deployment is causing me headaches.
As I understand it, once we are finished with a project, we then create an executable and installer file through the build specications option, which I have done. Then, we install the file onto the target computer along with any other dependicies it has. This all SEEMINGLY goes well, I get no error messages or anything of that nature. However, upon running the program, it simply doesn't work. Ideally, from this program, we can control and monitor all of the various valves, sensors and whatnot connected to the PLC, along with recieving notifications in certain instances. None of this is functional when running it from the target computer.
One thing to note is that we are using various .NET components to email these notifications, but the PLC doesn't support any wire/nodes that use .NET. To make sure that alone wasn't the issue, I reverted back to older code without the notifications implemented and still nothing worked. This brings me to my questions:
1) Is there something I'm missing that could be causing these issues in the deployment process?
2) How can I use .NET features if the PLC doesn't support them? Or is that I will just have to find another way to do this?
Thank you all for your help!

Answer 1

nathand wrote:
Do you know which Fieldpoint module you are using?  Some modules are actually self-contained computers which can run code; others are simply IO units (and the "smart" units can act as IO units without running any code).  You'll need to know how you're using the module.  Does a Fieldpoint module show up as a target in the project explorer?  If so, and you have code that runs on it, you can create a separate build specification for that application, then build and deploy it from the project explorer.
You mentioned that you took over and updated an existing project.  Was the original project written in an older version of LabVIEW?  If so, the target PC might have an older version of the Fieldpoint tools, and if you do have a smart Fieldpoint unit, you may need to upgrade it as well (you can do this within measurement and automation explorer).
Without having more knowledge of the details of your system, it's difficult to provide specific advice.  From your questions it sounds like you're not too familiar with the LabVIEW project environment and working with other targets.  It would help a lot if you could get an identical Fieldpoint setup on your desk to troubleshoot deployment and communication.
I believe we are using a cFP-2220 fieldpoint module, which does indeed show up as a target. So, from your advice, I would a create separate build application for the fieldpoint module, using the same VI I have used for executable on the PC. After creating the build application, I must then build and deploy it from within the project explorer. If that's the case, that all makes sense to me and I believe there shouldn't be any further issue.
As for the original project, no, it was all done within the same version of Labview. Regardless, I plan to update the Fieldpoint tools module as well, just to make sure everything's good.