User`s guide

106 Deploying Freely Programmable Modules on a SmartServer
FPM Deployment Overview
After you write and compile an FPM application or driver, you can deploy it on your SmartServer.
This enables you to apply the algorithms defined in the FPM application or FPM driver to the data
points on the SmartServer. Deploying an FPM application entails uploading the FPM to your
SmartServer, adding a device representing the FPM application on the SmartServer, commissioning
the FPM device if you are going to bind the data points in the FPM application with LonWorks
connections, testing the FPM application, and then connecting the data point in the FPM device with
L
ONWORKS connections or Web connections. Deploying an FPM driver entails just uploading the
FPM to your SmartServer.
You can upload FPMs to one or more SmartServers that have an FPM programming license installed
on them using the i.LON SmartServer 2.0 Programming Tool. After an FPM application has been
uploaded to a SmartServer, you need to verify that you have selected a network management service
mode (LNS or Standalone) for running your L
ONWORKS network.
Once you have selected a network management service, you can create an FPM device on the
SmartServer. To do this, you add a new internal device to the LON channel in the SmartServer tree.
If you are integrating your FPM application with another LNS application such as the LonMaker tool,
the internal FPM device must use a static interface. To use a static interface for your FPM, you select
the device interface (XIF) file from the root/lonworks/import/<YourCompany> folder on the
SmartServer flash disk. This is the XIF file that you generated for your FPM with the i.LON
LonWorks Interface Developer tool (see
Chapter 4 for more information on creating XIF files for
FPMs).
If you are running your network with the SmartServer operating as a standalone network manager, the
internal device can use a static or dynamic interface. To use a dynamic interface, you select the
SmartServer’s v40 XIF from the root/lonworks/import/Echelon/iLON100 folder, and you then add a
dynamic functional block to the device that uses a UFPT representing your FPM application.
If you are running your L
ONWORKS network in LNS mode (LNS Auto or LNS Manual) and you plan
on using L
ONWORKS connections to bind the data points in your FPM application with the data points
on the internal SmartServer device, on another FPM device, or on the external devices connected to the
SmartServer, you must first commission your FPM device. You can commission your FPM device
with the SmartServer or with an LNS application such as the LonMaker tool.
You can test that the FPM application is functioning properly by adding the data points declared in the
FPM device to the View – Data Points Web page. You can then change the values of the input data
points and observe whether the output data points are updated accordingly. Note that if FPM
programming is not licensed on the SmartServer, the SmartServer will not process changes made to the
FPM data points, and the FPM data points will become unavailable in the View – Data Points Web
page.
Once you verify that the FPM application is working, you can connect the data points in your FPM
application with L
ONWORKS connections or Web connections. You can then use the View – Data
Points Web page, a custom FPM configuration Web page, or an LNS application such as the
LonMaker tool to test that the connections are updating the FPM data points accordingly.
After you have deployed FPM applications on a development SmartServer, you can deploy the FPM
applications you have developed on multiple SmartServers.
Notes:
• The full version of the i.LON SmartServer 2.0 Programming Tools must be installed on your
computer to upload an FPM to a SmartServer. The full version of the i.LON SmartServer 2.0
Programming Tools is included on the i.LON SmartServer 2.0 Programming Tools DVD. To
order the i.LON SmartServer 2.0 Programming Tools DVD (Echelon part number 72111-409),
contact your Echelon sales representative.