How do two fieldpoints with embedded VIs communicate with each other?

[nathand]

You should not need FP Open at all, nor FP Create Tag - just use FieldPoint IO Points (as you're already doing for the LED outputs).  I don't currently have the RT module nor FieldPoint installed on my machine so I can't fully open your project, but you probably need a FieldPoint configuration file (.iak) that matches the project name and is tied to the project.  Then when you "Deploy All" to your target it should copy over the IAK file as well.

[Gizmaa]

I've tried everything I could possibly think of for the FP I/O.  Attached are some images of my project, realtime startup vi properties, and the circuit diagram.

Mesocosm-05 is the host, 192.168.1.164

Mesocosm-01 is remote, 192.168.1.160

When embedded the program is suppose to turn an LED on for 60 seconds on both Mesocosm-05 and Mesocosm-01 however when it is actually run only the LED on Mesocosm-05 activates.

[nathand]

You need to add the second FieldPoint module to your project.

Also, check that there's another iak file in the same folder as your lvproj, with the same name as the project.  If so, that's the iak file that's tied to the project and is deployed to the FieldPoint units.  (If there isn't, try creating a new project, then add both FieldPoint units and your VI to it.)  You can remove "Mesocosm-01.iak" from your project; you don't need it and it's probably just creating additional confusion.

Message Edited by nathand on 08-14-2008 01:38 PM

[Gizmaa]

I removed Mesocosm-01.iak from the project and added Mesocosm-01 (the controller) to the project.  Afterwards I checked out the .iak file in the project directory and it showed both Mesocosm-01 and Mesocosm-05 only.  The VI works if I run it from the project.  It deploys and everything is as it should be but when I deploy it as a startup the remote controller doesn't do anything. 

[nathand]

You've probably done this already, but make sure you do "Deploy All" on the FieldPoint target to download the module configuration... other than that I don't have any more ideas.  Can you find out what the error is when you run the compiled application?

[Gizmaa]

No luck.  How would I go about determining the errors after deployment?

By the way, thanks for the prompt replies.  I really appreciate it.

[nathand]

One approach would be to use remote front panels... but I haven't taken the time to figure out how that works with FieldPoint targets.

A quick solution is to format the error into a string, write it to a temporary text file, and copy it off the FieldPoint module after the VI runs.  Just make sure you don't chain the error output from the FieldPoint Write to the error input on the Write to Text File.

EDIT  One other idea: have you tried writing to a digital output on one of your IO modules, rather than the onboard LEDs of the remote module?  Perhaps the LEDs aren't accessible remotely but other IO points are; I've never tried triggering the LEDs from a remote unit the way you're doing.

Message Edited by nathand on 08-14-2008 02:34 PM

[Gizmaa]

Writing to a file doesn't seem to work either.  It's quite odd considering I have done it successfully in the past.  Am I doing something wrong?

Image of block diagram attached.

[nathand]

It looks to me like that should work... do you know that your program runs at all?  Do you see the LED on the local FieldPoint turn on and off?  If not, perhaps you're not properly deploying the startup application.  Forgive me if you know all this, but you should right click and set the application for startup, then build, then deploy, and finally power-cycle the FieldPoint unit to force it to restart.

[Gizmaa]

Better safe than sorry, I did set it as startup and reboot it.  The LED on the local controller did turn on and off.  I am lost for ideas.