ISPSoft User Manual
ISPSoft User Manual ISPSoft User Manual
Chapter 9 Function Block Diagram (e) One node represents a symbol whose data type is WORD/DWORD/LWORD, and the other node represents a symbol whose data type is INT/DINT/LINT. The data length of the output node must be larger than or equal to the data length of the input node. (f) Both nodes represent symbols whose data types are REAL/LREAL/STRING. The data lengths of the nodes must be the same. (g) If an input node has multiple output nodes, the output nodes must conform to the rules listed above. 32 output nodes at most form a group. After users add an output node rightward, they can create another group of output nodes. • Graphical representation • Example Example 1: The state of the contact M0 is sent to M1. Example 2: The data in D0 is sent to D1. Example 3: There are three groups of output nodes. The first group begins with M100, the second group begins with M200, and the third group begins with M300. 32 output nodes at most form a group. After users add an output node rightward, they can create another group of output nodes. There is no limit on the number of output nodes which can be added rightward. Example 4: Some incorrect examples are listed below. Incorrect example Description The data type of the input node must not be different from the data type of the output node. The data length of the output node must not be less than the data length of the input node. The value of a symbol whose data type is REAL can not be sent to a D device. If the input node represents a symbol whose data type is REAL, the output node must represent a symbol whose data type is REAL. If the input node represents a symbol whose data type is LREAL, the output node must represent a symbol whose data type is LREAL. The data length of the input node representing a symbol whose data type is STRING and the data length of the output node representing a symbol whose data type is STRING must be the same. 9-7
ISPSoft User Manual Incorrect example Description The value of a symbol whose data type is TIMER can not be sent to a symbol whose data type is DWORD, but can be sent to a symbol whose data type is WORD. The value in a HC device can not be sent to a symbol whose data type is WORD, but can be sent to a symbol whose data type is DWORD. The multiple output nodes must conform to the rules listed above. The example is incorrect because the data length of the output node representing a symbol whose data type is INT is less than the data length of the input node. • Inserting an output node (1) Select a position into which an output node will be inserted in the working area. Users are allowed to insert output nodes into the positions marked with red frames in the figure below. (2) In addition to the structure in the figure above, users may be allowed to insert an output node into another structure. If users are allowed to insert an output node into the position selected, on the toolbar can be clicked. After is clicked, an output node will be inserted. An output node can be inserted in the following structures. Inserting an output node into an input pin of an AND/OR block Before After 9-8
- Page 258 and 259: Chapter 7 Function Block In view of
- Page 260 and 261: Chapter 7 Function Block itself. As
- Page 262 and 263: Chapter 7 Function Block • DVP se
- Page 264 and 265: Chapter 7 Function Block Function b
- Page 266 and 267: Chapter 7 Function Block HC_POINTER
- Page 268 and 269: Chapter 7 Function Block program in
- Page 270 and 271: Chapter 7 Function Block The functi
- Page 272 and 273: Chapter 7 Function Block Please ref
- Page 274 and 275: Chapter 7 Function Block After the
- Page 276 and 277: Chapter 7 Function Block Open the w
- Page 278 and 279: Chapter 7 Function Block Obviously,
- Page 280 and 281: Chapter 8 Ladder Diagram Table of C
- Page 282 and 283: Chapter 8 Ladder Diagram Local symb
- Page 284 and 285: Chapter 8 Ladder Diagram Selecting
- Page 286 and 287: Chapter 8 Ladder Diagram (4) After
- Page 288 and 289: Chapter 8 Ladder Diagram (b) ‣ Bo
- Page 290 and 291: Chapter 8 Ladder Diagram Users can
- Page 292 and 293: Chapter 8 Ladder Diagram (2) Select
- Page 294 and 295: Chapter 8 Ladder Diagram (2) Click
- Page 296 and 297: Chapter 8 Ladder Diagram The steps
- Page 298 and 299: Chapter 8 Ladder Diagram 8.2.10 Sym
- Page 300 and 301: Chapter 8 Ladder Diagram The networ
- Page 302 and 303: Chapter 9 Function Block Diagram Ta
- Page 304 and 305: Chapter 9 Function Block Diagram Lo
- Page 306 and 307: Chapter 9 Function Block Diagram T
- Page 310 and 311: Chapter 9 Function Block Diagram In
- Page 312 and 313: Chapter 9 Function Block Diagram Ex
- Page 314 and 315: Chapter 9 Function Block Diagram fo
- Page 316 and 317: Chapter 9 Function Block Diagram fu
- Page 318 and 319: Chapter 9 Function Block Diagram Ex
- Page 320 and 321: Chapter 9 Function Block Diagram Ex
- Page 322 and 323: Chapter 9 Function Block Diagram an
- Page 324 and 325: Chapter 9 Function Block Diagram
- Page 326 and 327: Chapter 9 Function Block Diagram If
- Page 328 and 329: Chapter 9 Function Block Diagram Ri
- Page 330 and 331: Chapter 10 Instruction List Table o
- Page 332 and 333: Chapter 10 Instruction List The ope
- Page 334 and 335: Chapter 10 Instruction List • As
- Page 336 and 337: Chapter 10 Instruction List If user
- Page 338 and 339: Chapter 10 Instruction List Users
- Page 340 and 341: Chapter 10 Instruction List 10.2.4.
- Page 342 and 343: Chapter 11 Structured Text Table of
- Page 344 and 345: Chapter 11 Structured Text A comple
- Page 346 and 347: Chapter 11 Structured Text Data for
- Page 348 and 349: Chapter 11 Structured Text However,
- Page 350 and 351: Chapter 11 Structured Text Example
- Page 352 and 353: Chapter 11 Structured Text Example
- Page 354 and 355: Chapter 11 Structured Text Example
- Page 356 and 357: Chapter 11 Structured Text 11.2.5 L
Chapter 9 Function Block Diagram<br />
(e) One node represents a symbol whose data type is WORD/DWORD/LWORD, and the other<br />
node represents a symbol whose data type is INT/DINT/LINT. The data length of the output<br />
node must be larger than or equal to the data length of the input node.<br />
(f) Both nodes represent symbols whose data types are REAL/LREAL/STRING. The data lengths<br />
of the nodes must be the same.<br />
(g) If an input node has multiple output nodes, the output nodes must conform to the rules listed<br />
above. 32 output nodes at most form a group. After users add an output node rightward, they<br />
can create another group of output nodes.<br />
• Graphical representation<br />
• Example<br />
Example 1: The state of the contact M0 is sent to M1.<br />
Example 2: The data in D0 is sent to D1.<br />
Example 3: There are three groups of output nodes. The first group begins with M100, the second<br />
group begins with M200, and the third group begins with M300. 32 output nodes at<br />
most form a group. After users add an output node rightward, they can create another<br />
group of output nodes. There is no limit on the number of output nodes which can be<br />
added rightward.<br />
Example 4: Some incorrect examples are listed below.<br />
Incorrect example<br />
Description<br />
The data type of the input node must not be different from<br />
the data type of the output node.<br />
The data length of the output node must not be less than<br />
the data length of the input node.<br />
The value of a symbol whose data type is REAL can not<br />
be sent to a D device.<br />
If the input node represents a symbol whose data type is<br />
REAL, the output node must represent a symbol whose<br />
data type is REAL. If the input node represents a symbol<br />
whose data type is LREAL, the output node must<br />
represent a symbol whose data type is LREAL.<br />
The data length of the input node representing a symbol<br />
whose data type is STRING and the data length of the<br />
output node representing a symbol whose data type is<br />
STRING must be the same.<br />
9-7