Jim,
There are a number of possible reasons for what you are seeing. Let me rule out a couple of things for you first.
The FP Open.vi has an input called IAK file path. When a LabVIEW program is running either targeted at a FP-20xx or built into an exe on a FP-20xx, the IAK file path is ignored as we do not directly download an IAK file into the FP-20xx. Having the IAK file path wired will not adversely effect the program.
Likewise, the Comm Resource Input of the FP Create Tag.vi is ignored when embedded as it is not relevant to a vi running on a FP-20xx.
There are several likely causes of the 32810 error. The first possibility is that you have not downloaded the "IAK" into the FP-20xx. I put "IAK" in quotes because, technically speaking, the FP-20xx does not have and IAK file. Instead, we download a specialized INI file that contains the needed addressing information (the IAK provides this to LabVIEW and has extra data that is only used by FieldPoint Explorer). By default, whenever you save an IAK, we will download this file into the FP-20xx, but this can be disabled. In FieldPoint Explorer, you can choose OPTIONS>>Download Configuration On Save. Alternatively, if you right click on the FP-20xx, you can choose Download Configuration.
Another possible cause is the IA Control Environment failing to load. This may be caused be corrupted or missing firmware, or if the module was booted up in Safe Mode. Since you are capable of reading the data from FieldPoint Explorer, then the firmware exists and is probably not corrupted (I included this option for thoroughness).
Another possible cause would be damage or corruption of the file fplvmgr.dll in the FP-20xx. There are two versions of this file, one is designed for the host computer and resides (typically) in labview 6\vi.lib\fieldpoint\subvis. The other resides on the FP-20xx and will also be under program files\national instruments\rt images\fieldpoint\1.0.21\ . This latter one is the one that should reside on the FP-20xx. Normally, when you are building an executable to embed on the FP-20xx, there will be a dialog box saying that the target OS has it's own copy of the dll and it will not be downloaded. This normally makes over-writing of the dll unlikey but this does not prevent a user from over-riding the warning and downloading the wrong file. I have also seen a case where a customer ftp'd the wrong file into the module.
If none of the above suggestions works, try reinstalling the firmware on the module as it may have become corrupted in another way. If it still fails, add a note suggesting the additional things that you have tried and I will provide any additional assistance required.
As for more information, I suggest the NI KnowledgeBase (there are several articles already with more being created) and NI Developer Zone, both are available at www.ni.com.
Regards,
Aaron