How do MAX configurations get saved on cFP?

Question

I need to find out how the MAX configuration gets saved on a cFP-2200 module so I can read from it dynamically. I need to do this in order to make installations of my software more generic, allowing dynamic reading of input channels without having to know things like the DNS name ahead of time. I already understand how to create dynamic paths with LabVIEW but it seems that changing the DNS name to something other than what the original install was under makes any paths using the new name useless. I am using RT "Get target info" to dynamically see the target's name. Working this name into the path for looking up input on the cFP-AI-102 channels only seems to work if the name stays the same as it was originally.

Answer 1

I am connected to the cFP-2200 over a LAN. I can have several of these at a given site which is why the name needs to be flexible. I also use the name in some VIs for various purposes, such as configuring dynamic TCP listeners on a server application.
When I say "DNS name," I'm referring to the "RT Get Target Information.VI" under the RT toolkit's output cluster and specifically, the element "IP Settings.DNS Name." This is also the name I would set for the target in max and when I do this, the output of "IP Settings.DNS Name" changes with it. Also, when I click "find devices" on the cFP in max, the default comm resource name for the device in the iak file is whatever I had set for the "name" at the time.
The "FP Create Tag.VI" which I am using to create paths to the inputs of the target has an input called "comm resource name." Since this was set to the same thing as the "name" in max, my expectation was that changing the name for a device in max would also change its comm resource name. However, my example above shows my expectation does not match what is actually happening. While the DNS Name is tied to the name set in max, the "comm resource name" is not even though during the initial creation of the iak file in MAX, they are the same.
To make a long story short, I am able to get my software to work by making sure that the comm_resource_name is hard coded to the value originally set in the project which created the build. This solution is adaquate but not optimal because I would rather be looking this up dynamically for the sake of maintainability. If the comm_resource name and DNS Name are separate entities, that is fine. There just needs to be a way to look both up dynamically if they are separate.
I guess this has become more of a suggestion than a problem I'm reporting... unless of course the behavior I'm describing is not what NI intended, in which case it's a bug.