Echelon i.LON SmartServer Podręcznik Użytkownika Strona 174
- Strona / 266
- Spis treści
- BOOKMARKI
Oceniono. / 5. Na podstawie oceny klientów
160 Creating FPM Application Licenses
char msg[100];
sprintf(msg, "FPM license key is invalid: file
\"%s\"\n", taskCallBlock.pFilePath);
taskCallBlock.pGeneric = (void*)msg;
LICMGR_TaskCall_LogLicenseError(&taskCallBlock);
}
}else
{
char msg[100];
sprintf(msg, "FPM license not found: file \"%s\"\n",
taskCallBlock.pFilePath);
taskCallBlock.pGeneric = (void*)msg;
LICMGR_TaskCall_LogLicenseError(&taskCallBlock);
}
// free the license data, if any
LICMGR_TaskCall_FreeLicenseData(&taskCallBlock);
}
Step 5: Implementing the License Validation Call Mechanism
After you have written your license validation algorithm, you need to implement some mechanism in
your FPM application that results in the license validation routine being called. This can be done in a
variety of ways using the pre-defined code and routines in your FPM application; however, you are
solely responsible for designing and implementing this mechanism.
Step 6: Compiling the Licensed FPM Application
Once you have created the license validation call mechanism, you can compile your licensed FPM
application. To compile your FPM, click File and then click Save. If your code has any errors, they
will be listed with any warnings in the Problems view at the bottom of the document window. You
can click on the errors and warnings listed in this view to debug your FPM. If the build is not
performed, click Project and then click Build Project. You can then click Project and select Build
Automatically so that your FPM applications are built automatically when you save them.
Building the Release Version of a Licensed FPM Application
After you enable license validation in your FPM application and compile it, you can build the release
version of your FPM application that you will make available to customers. Building the release
version entails removing the internal-only symbols from your FPM executable module (.app
extension). Stripping the internal-only symbols greatly enhances the security of your licensing
scheme, as it obscures the location of the routines and data in your code.
To remove the internal-only symbols from your FPM executable module, follow these steps:
1. Open a Command Prompt window.
2. At the command prompt, change the directory to the path of your FPM executable module.
For example, you type the following (without the break):
cd C:\LonWorks\iLON\Development\eclipse\workspace.fpm\
9000010000000000[3].UFPTHVACController/Release
3. Use the set path command to set the path to the directory containing the GNU strip utility
(strip.exe). This utility is located in the
C:\LonWorks\iLON\Development\eclipse\plugins\com.echelon
.eclipse.ilon100.fpm_0.9.0\compiler\3.3.2-vxworks-6.2\x86-win32\i586-wrs-vxworks\bin
directory.
For example, you type the following (without the breaks):
- SmartServer 2.0 1
- Table of Contents 3
- Preface 8
- Hardware Requirements 10
- SmartServer Requirements 10
- Related Reading 11
- Content 12
- Introduction 15
- FPM Types 16
- Creating and Deploying FPMs 16
- Quick-Start FPM Exercise 20
- 14 Introduction 28
- Programming Tools 37
- Importing FPM Projects 44
- Creating FPM Templates 55
- Creating a Model File 70
- Declaring Functional Blocks 72
- Using Include Directives 73
- Example Model Files 73
- Saving your Model File 76
- Other Command Switches 78
- Creating FPMs 79
- Creating FPMs Overview 80
- Creating New FPM Projects 81
- Creating an FPM 82
- Using UFPT Local Variables 89
- Writing an FPM Application 90
- Starting Timers 91
- Using the Start() Method 91
- Reading Data Point Values 95
- Reading Scalar Data Points 95
- Writing Data Point Values 97
- Writing an FPM Driver 100
- { 102
- Compiling an FPM 103
- Using Non-Latin Characters 104
- Debugging FPMs 105
- Using Wind River Workbench 106
- Using SNMP Support 116
- ONWORKS network. It 119
- FPM Deployment Overview 120
- Deploying FPM Applications 125
- Deploying FPM Drivers 125
- ONWORKS network 126
- ONWORKS connections 126
- ONWORKS connections, or 126
- ONWORKS 126
- ONWORKS channel, and then 128
- Commissioning FPM Devices 134
- Recommissioning FPM Devices 135
- Testing FPM Applications 136
- Connecting FPM Data Points 136
- ONWORKS Connections 137
- Creating Web Connections 141
- Updating FPMs 152
- Updating Device Interfaces 153
- Licensing Overview 160
- ONMARK ID 161
- Creating a Security DLL File 163
- Verifying the Lock ID 170
- Verifying the License Key 172
- Supplying FPMs to Customers 178
- Interface 181
- Translating Property Files 199
- Appendix A 217
- FPM Programmer’s Reference 217
- Overview 218
- Template Files 218
- Routines 218
- Initialize() 219
- Work() 219
- OnTimer() 220
- FPM Application 221
- FPM Driver 221
- Methods 222
- Changed() 223
- NotifyOnAllUpdates() 224
- Propagate() 224
- Write() 225
- ResetPriority() 225
- SetDpProperty (UCPTpriority) 230
- SetDpProperty(defOutput) 230
- UFPT Local Variables 231
- Timer Methods 235
- Expired() 236
- Stop () 237
- StopAllTimers() 237
- IsRunning() 237
- Reboot Method 238
- RS-232 Interface Methods 239
- RS-485 Interface Methods 243
- ONWORKS directory 244
- File Access Methods 247
- if(iTemp) 248
- Appendix B 251
- Checklist 251
- ONWORKS channel 253
- Appendix C 255
- FPM FAQ 255
- SmartServer FPM FAQs 256
Powiązane produkty i podręczniki dla Serwery Echelon i.LON SmartServer
(443 strony)Powerfix WINDOW SECURITY BRACKET manuals
Owner’s manuals and user’s guides for For Home Powerfix WINDOW SECURITY BRACKET.
We providing 3 pdf manuals Powerfix WINDOW SECURITY BRACKET for download free by document types: User Manual
Komentarze do niniejszej Instrukcji