Echelon FTXL Bedienungsanleitung Seite 62
- Seite / 261
- Inhaltsverzeichnis
- LESEZEICHEN
Bewertet. / 5. Basierend auf Kundenbewertungen
50 Creating a Model File
file. The API uses this table to access the network variables when the application
runs. In addition, the application can query the data in this table at runtime.
Important: This example is not interoperable because it does not use functional
blocks to define the purpose of these network variables. However, this type of
declaration can define a functioning device for an initial test application.
Functional Blocks without Configuration Properties
The following model file describes a similar meter application as in the previous
example, but implements it using functional blocks to provide an interoperable
interface:
• A node object based on the
SFPTnodeObject
functional profile to manage
the entire device
• An array of three meters, each based on the same user-defined
UFPTenergyMeter
profile, implementing three identical meters.
Configuration properties are not used in this example.
// node object:
network input SNVT_obj_request nviNodeRequest;
network output polled SNVT_obj_status nvoNodeStatus;
fblock SFPTnodeObject {
nviNodeRequest implements nviRequest;
nvoNodeStatus implements nvoStatus;
} NodeObject external_name("NodeObject");
// UFPTenergyMeter
// Implements the meter from the previous example.
network input SNVT_amp nviAmpere[3];
network input SNVT_volt nviVoltage[3];
network input SNVT_angle nviCosPhi[3];
network output SNVT_power nvoWattage[3];
network output polled eeprom SNVT_elapsed_tm nvoUsage[3];
fblock UFPTenergyMeter {
nvoWattage[0] implements nvoWattage;
nviAmpere[0] implements nviAmpere;
nviVoltage[0] implements nviVoltage;
nviCosPhi[0] implements nviCosPhi;
nvoUsage[0] implements nvoUsage;
} Meter[3] external_name("Meter");
Because functional blocks only provide logical grouping of network variables and
configuration properties, and meaning to those groups, but do not themselves
contain executable code, the functional blocks appear only in the self-
documentation data generated by the LonTalk Interface Developer utility, but
not in any generated executable code.
- FTXL User’s Guide 1
- Welcome 3
- Audience 3
- Related Documentation 3
- ONWORKS System 4
- Table of Contents 7
- Introduction to FTXL 13
- Neuron-hosted 15
- ONWORKS Device 16
- Servers 17
- ShortStack Device 18
- ONWORKS 19
- ONWORKS network 19
- ONWORKS networking to a high 19
- FTXL Device 20
- Devices 20
- ONWORKS Devices 21
- Using Direct 22
- Memory Files 22
- Development Tools for FTXL 23
- FTXL Architecture 23
- The FTXL Developer’s Kit 25
- Getting 26
- Started with 26
- ONWORKS events 28
- ONWORKS network by 28
- ONWORKS network tool 28
- Getting Started with FTXL 29
- ONWORKS network connector 30
- Hardware Requirements 31
- Software Requirements 31
- DBC2C20 Software 32
- FTXL API Files 32
- 22 Getting Started with FTXL 34
- Model File Overview 36
- Choosing the Data Type 38
- Defining a Functional Block 39
- Declaring a Functional Block 40
- Defining a Network Variable 40
- Defining a Resource File 41
- Variable 42
- ONMARK Standard Program ID 43
- Using Direct Memory 45
- Value Changes 46
- static nciOffset 47
- Declaring a Message Tag 52
- NodeBuilder User’s Guide 54
- LonMaker User's Guide 54
- Anonymous Top-Level Types 55
- Legacy Neuron C Constructs 56
- How Authentication Works 57
- Address Table 59
- Alias Table 59
- Domain Table 60
- Example Model files 60
- Using Types 61
- SFPTnodeObject 62
- UFPTenergyMeter 62
- SNVT_address 65
- Using the LonTalk Interface 67
- Developer Utility 67
- Specifying the Project File 68
- Configuring the Buffers 70
- Configuring the Application 70
- ONMARK Standard Program 71
- Specifying the Model File 72
- Developer Files 73
- NodeBuilder Errors Guide 73
- Copied Files 74
- FtxlDev.h 75
- FtxlDev.c 75
- Bit Field Members 77
- Enumerations 78
- Floating Point Variables 78
- Declarations 80
- The Network Variable Table 83
- Network Variable Attributes 83
- The Message Tag Table 84
- FTXL User’s Guide 73 85
- Using the FTXL LonTalk API 86
- Host Application 87
- Application Framework 87
- Transceiver 87
- Callbacks and Events 88
- The FTXL Operating 89
- System Abstraction Layer 89
- Restoring Non-Volatile Data 90
- Writing Non-Volatile Data 91
- Initializing the FTXL Device 93
- MaxPacketRate 94
- InputBufferCount 94
- ONWORKS devices by 95
- FTXL Application 96
- FTXL LonTalk Protocol 96
- Stack and API 96
- LonEventPump() 98
- LonNvUpdateOccurred() 98
- Network 100
- Variables 100
- Validating a Type Change 101
- Processing a Type Change 102
- Processing a Size Change 103
- Rejecting a Type Change 104
- Messages 105
- Handling Management Commands 106
- Handling Reset Events 107
- Querying the Error Log 107
- Working with ECS Devices 107
- Using Direct Memory Files 108
- The DMF Memory Window 109
- LON_DMF_WINDOW_START 110
- LON_DMF_WINDOW_USAGE 110
- File Directory 111
- Working with the Nios II 113
- Development Environment 113
- Development Tools 114
- Setting up the Nios II IDE 115
- Example FTXL Applications 116
- II Operating System 118
- Running the 119
- Application 119
- Running the Application 120
- Debugging the Application 121
- FTXL Hardware Guide 122
- LonTalk Interface Developer 123
- Command Line Usage 123
- Overview 124
- Command Usage 124
- Command Switches 125
- Specifying Buffers 127
- Creating a Model File 131
- C-string-const 134
- Functional Block Syntax 138
- Keywords 138
- Examples 140
- Network Variable Syntax 144
- The Network Variable Type 146
- Information 147
- Authentication 149
- FTXL LonTalk API 159
- Introduction 160
- FTXL LonTalk API Functions 161
- Functions 161
- Extended API Functions 163
- FTXL Event Handler Functions 164
- Managing Critical Sections 170
- Managing Binary Semaphores 170
- Managing System Timing 171
- Operating System 172
- Specifying Task Priorities 173
- Maximum Number of Tasks 177
- StackTasks 178
- AppTasks 178
- Other µC/OS-II Settings 179
- Event Flags 181
- Semaphores 183
- Mailboxes 184
- Memory Management 185
- Miscellaneous 185
- Maximum Number of Event 186
- Control Blocks 186
- Task Management 187
- Time Management 188
- Timer Management 189
- Managing the Service Pin 191
- Managing Interrupts 191
- Determining Memory Usage for 193
- FTXL Applications 193
- Total Memory Use 194
- Memory Use for Transactions 195
- Memory Use for Buffers 195
- ONWORKS Resources 196
- Memory for Non-Volatile Data 197
- Node_SD_length 198
- NV_SD_length 198
- Memory Usage Examples 199
- Over the Network 203
- Application Download Utility 205
- Example Application Files 208
- Main Function 210
- Application Task Function 210
- Event Handler Function 211
- Model File 212
- Callback Handler Function 213
- Creating a Model 214
- Application-Specific 214
- Utility Functions 214
- Event Handler Functions 217
- Applications 227
- Using a Device 233
- Running the Simple Example 234
- Virtual Functional Block 238
- The Micrium Software License 239
- Error and Warning Messages 241
- Error Messages 242
- Neuron C Reference Guide 246
- [LID#50] 248
- Warning codes 249
- Hint codes 251
- Glossary 253
Verwandte Produkte und Handbücher für Hardware Echelon FTXL
(191 Seiten)Yamaha KMA-1080 manuels
Manuels d'utilisation et guides de l'utilisateur pour Karaoké Yamaha KMA-1080.
Nous fournissons des manuels en pdf 1 Yamaha KMA-1080 à télécharger gratuitement par type de document : Manuel de l'utilisateur
Kommentare zu diesen Handbüchern