 |
| Place of Origin: | Japan |
| Brand Name: | Tamagawa |
| Certification: | CE |
| Model Number: | TS2058N21 |
| Minimum Order Quantity: | 1pcs |
|---|---|
| Packaging Details: | carton |
| Delivery Time: | 100pcs/week |
| Payment Terms: | T/T, Western Union, MoneyGram |
| TAMAGAWA: | TAMAGAWA | Material: | Iron |
|---|---|---|---|
| Japan: | Japan | Color: | Black |
| Temperature: | 20-90 | Wire: | Wire |
| Dimension: | 70mm | TS2058N21: | TS2058N21 |
TS2058N21EAA
| For example, if the folder structure shown here was at C:, the | for the default HTML page settingWhen you generate data blocks for your user-defined pages, STEP 7 creates a control |
| setting for HTML directory would be C:html, and if English were to | DB that it uses to control display of and interaction with the user-defined pages. STEP 7 also |
| be the initial page display, you would navigate to enlangswitch.html | creates a set of fragment DBs that represent the individual pages. Under normal circumstances, you do not need to know the structure of the control DB or how to manipulate |
Guang Zhou Lai Jie Electric Co.,LTD
Please contact with “Tommy” for the price
TS2025N471E69
TS3630N102E4
TS5017N60
TS5007N122
TS4502N1000E200
TS1983N146E5
TS3653N78E5
TS2014N181E32
TS3630N22E3
TS5108-N153-5V
TS5007N635
TS4502N1202E200
TS252N30E1
AU6270N103E63
TS3653N94E5
TS5208N141E78
TS3630N22E4
TS5146N10
TS5208N500
TS4502N2000E100
TS3503N11E43
TS3653N181E8
TS3684N1E3
TS3631N1E1
TS5146N11
TS5208N510
TS4503N1000E200
TS3062E3
TS3658N3
TS3684N13E8
TS3636N6
TS-5170-N20
TS5208N530
TS4503N1007E200
TS3092N11E12
AU6550N2062
TS3664N1E1
TS3617N1E3
it.
If you want to turn a application on and off, for example, or manipulate individual manual
fragments, you use the control DB tags and the instruction to do so.
Structure of the control DB
The control DB is an extensive data structure, and is accessible when programming your
STEP 7 user program. Only some of the control data block tags are described here.
Commandstate structure
"Commandstate" is a structure that contains global commands and global states for the
server.
Global commands in the "Commandstate" structure
The global commands apply to the server in general. You can deactivate the
server or restart it from the control DB parameters. The request table is an array of structures containing commands and states that apply to
individual fragment DBs. If you created fragments with the AWP_Start_Fragment (Page 532)
command of type "manual", the STEP 7 user program must control these pages through the
control DB. The request states are read-only and provide information about the current
fragment. You use the request commands to control the current fragment.Array of structures for individual
fragment DB control.
The server can process up to four
fragments at a time. The array index for
a particular fragment is arbitrary when
the server is processing multiple
fragments or fragments from multiple
browser sessions. Number of the current page
fragment_index UINT Number of the current fragment - can be
set to a different fragment
// Request Commands
continue BOOL Enables current page/fragment for
sending and continues with the next
fragment
repeat BOOL Enables current page/fragment for
resending and continues with the same
fragment
abort BOOL Close connection without sending
finish BOOL Send this fragment; page is complete -
do not process any additional fragments
// Request states The request states are read-only
idle BOOL Nothing to do, but active
waiting BOOL Fragment is waiting to be enabled
sending BOOL Fragment is sending
aborting BOOL User has aborted current request
Operation
Whenever your program makes changes to the control DB, it must call the instruction
with the number of the modified control DB as its parameter. The global commands and
request commands take effect when the STEP 7 user program executes the
instruction (Page 537).
The STEP 7 user program can set the fragment_index explicitly, thus causing the
server to process the specified fragment with a request command. Otherwise, the
server processes the current fragment for the current page when the instruction
executes. Possible techniques for using the fragment_index include:
● Processing the current fragment: Leave fragment_index unchanged and set the continue
command.
● Skip the current fragment: Set fragment_index to 0 and set the continue command.
● Replace current fragment with a different fragment: Set the fragment_index to the new
fragment ID and set the continue command.
To check global states or request states that might be changing, the STEP 7 user program
must call the instruction to evaluate the current values of these states. A typical usage
might be to call the instruction periodically until a specific state occurs.
Note
If the STEP 7 user program sets more than one request command, the instructions
processes only one in this of precedence: abort, finish, repeat, continue. The
instruction clears all of the request commands after processing.
Examples
The following example shows a STEP 7 user program that is checking for a fragment with an
ID of 1 to be in the waiting state, following a prior call to the instruction. It might also
wait for other application-specific conditions to occur. Then it performs whatever processing
is necessary for the fragment, such as setting data block tags, performing calculations, or
other application-specific tasks. Afterwards, it sets the continue flag so that the server
will execute this fragment. When the program calls the instruction with this modified control DB, the user-defined
page with this fragment can be displayed from the browser.Note that this is a simplified example; the fragment to check could be in any one of the four
requesttab structs in the array. The following IT considerations can affect your use of the server:
