Supplying fpms to customers, Files – Echelon i.LON SmartServer 2.0 User Manual
Page 178

164
Creating FPM Application Licenses
The FPM application license log file lists the following information:
• The date on which the FPM application license was created.
• Your company’s name and LonMark ID
• The customer information you entered in step 9.
• The FPM license data, which consists of your company’s name, the name of the FPM
licensed, the license type, lock type, lock ID, any options specified, and the license key
generated for the FPM application by the security DLL file.
Supplying FPMs to Customers
After you built a release version of your FPM application and have created FPM application licenses
for your FPMs, you can supply your FPM applications to customers. When customers order an FPM
application from your company, you need to provide the following files for them:
• Your company’s FPM resource file set in which you created the user-defined functional profile
template (UFPT) used by your FPM application. Your company’s FPM resource file set should be
stored in the LonWorks\Types\User\
.ENU, fmt, .fpt, .ls, and .typ files. These are the files you generated with when you created the
UFPT for your FPM with the NodeBuilder Resource Editor.
See Chapter 3, Creating FPM Templates, for more information on creating FPM templates and
generating your company’s FPM resource file set.
• The device interface (XIF) file (.xif extension) that you created for your FPM application. Your
XIF should be stored in the destination folder that you specified when you generated the XIF with
the i.LON SmartServer 2.0 LonWorks Interface Developer Tool.
See Chapter 4, Creating FPM Device Interface (XIF) Files, for more information on creating
model files and converting them to the XIFs with the i.LON SmartServer 2.0 LonWorks Interface
Developer Tool.
• The FPM executable module (with license validation enabled). This is the .app file that is created
and updated when you compile your FPM application with the i.LON SmartServer 2.0
Programming Tool. By default, your FPM application is stored in the