Echelon i.LON SmartServer 2.0 User Manual
Page 259
i.LON SmartServer 2.0 Programming Tools User’s Guide
245
For Static FBs, you need to create a model file (*.nc extension) in which you declare all the data points
in the UFPT used by the FPM, and a functional block that implements an instance of the UFPT. You
then need to use the
i
.LON SmartServer 2.0 LonWorks Interface Developer tool to convert the model
file to a XIF file. When you create the internal device on the SmartServer, all the functional blocks
and data points specified by the XIF file will automatically appear under the internal FPM device in
the navigation pane on the left side of the SmartServer Web interface.
One advantage of using static FBs is that once you create the XIF file, it is easy to add new internal
FPM devices with the same feature set. A disadvantage of using static FBs is that they consume
resources on the SmartServer even if a FB or NV/CP is not being used.
If you are running your network with the SmartServer operating as a standalone network manager, the
internal device can use static or dynamic FBs. If the internal FPM device uses dynamic FBs then you
need to create an internal device that uses the SmartServer internal v40 XIF file. You then add
functional blocks to the internal FPM device for the FPM applications you want to instantiate.
One advantage of using dynamic FBs is that you only use SmartServer resources for those functional
blocks that you add. A disadvantage of using dynamic FBs is that when you want to add another
internal device with the same feature set, you must manually add all the FBs again.
9. Do I need to commission an internal FPM device?
You do if you plan on using L
ON
W
ORKS
connections to bind the data points in your FPM application
to data points on the SmartServer or to data points on external devices. You do not need to
commission an internal FPM device if you plan on connecting FPM data points with Web connections
(Web bindings).
Note that LonWorks connections are only supported in LNS Auto or LNS Manual mode. If you are
operating the SmartServer in Standalone mode, you can only use Web connections to bind your FPM
data points.
10. How do I create unique names for my FPMs to avoid collisions with other FPM manufacturers?
Each FPM must be identified by a unique namespace that consists of a Program ID and a Functional
Profile Template name (e.g., “8FFFFF46140A1E03[5].UFPTMath”). That is, no two FPMs on the
same SmartServer can have the same namespace. Using your company’s program ID in the
namespace prevents potential naming conflicts.
You can use Scope 3, 5 or 6. Scope 5 is recommended. If you don’t have a Manufacturer ID then go
to the LonMark website
and get a temporary Manufacturer ID.
11. Can I create network variables (NVs) for my FPMs?
Yes. You can create both input and output NVs for your FPM. You need to define your NVs in a
resource file set using the NodeBuilder Resource File Editor. The NVs are automatically declared in
your FPM code when you create a new FPM project based on a UFPT in your resource file set.
12. Can I use configuration properties (CPs) for my FPMs?
Yes, you can create CPs that are implemented as NVs. You need to define your CPs in a resource file
set using the NodeBuilder Resource File Editor. The CPs are automatically declared as CP NVs in
your FPM code when you create a new FPM project. If you plan on using static FBs for your internal
FPM devices, you also need to define the CPs as CP NVs in the model file.
CPs that are implemented in configuration files are not supported.
13. What is the NodeBuilder Resource File Editor and why do I need it?
The NodeBuilder Resource Editor is used to develop a user-defined functional profile template