Message Edited by Travis G. on 08-09-2006 05:24 PM
Hope this isn't hijacking this thread, but it seems pretty close to what I'm puzzling over. This seems like it should be pretty straightforward, but I'm still semi-stuck. If someone could tell me a 'best practices' approach to the following use case, I'd be grateful:
I have multiple FP-2015's which have identical module configurations. I have one LVRT application which I want to deploy and run, unmodified, on each of them. That is to say, I'd like the FPtag constants on the BD to not change since each application instance is only reading its local resources.
Whenever I try to configure the nodes using MAX, it seems that each node gets a uniquely-named FP configuration under its respective Data Neighborhood, which matches the ones which accumulate under my PC's local Data Neighborhood. Clearly, I'm not getting the point here of how this should be managed. What should the FPtag constants on the BD look like?
Is using MAX just the wrong approach? The other messages in this thread would imply that the LV8 project interface (yup, I'm running LV8 now) would help untangle this.
Grateful for all advice,