Place of Origin: | Japan |
Brand Name: | Tamagawa |
Certification: | CE |
Model Number: | TS5246N158 |
Minimum Order Quantity: | 1pcs |
---|---|
Packaging Details: | carton |
Delivery Time: | in stock |
Payment Terms: | T/T, Western Union, MoneyGram |
Supply Ability: | 100pcs/week |
TAMAGAWA: | TAMAGAWA | TS5246N158: | TS5246N158 |
---|---|---|---|
Material: | Iron | Temperature: | 20-90 |
Color: | Black | Wire: | Wire |
Dimension: | 70mm | Japan: | Japan |
TS5246N158
Guang Zhou Lai Jie Electric Co.,LTD
Please contact with “Tommy” for the price
TS5003N632
TS5005N122
TS5007N122
TS5007N635
TS5208N500
TS5208N510
TS5208N530
TS5208N569
TS5208N576
TS5210N450
TS5210N453
TS5210N458
TS5210N530
TS5210N54
TS5210N553
TS3684N1E3
TS3684N2E6
TS3684N3E8
TS3684N11E3
TS3684N12E6
TS3684N13E8
TS3617N1E3
TS3617N1E1
TS3617N1E2
TS3617N2E4
TS3617N2E5
TS3617N2E6
TS3617N2E7
TS3617N3E8
TS3617N3E9
TS3617N3E1
TS3617N11E3
TS3617N11E1
TS3617N11E2
Wind_turbine.html: This is the HTML page that implements the display shown above, using AWP commands to access controller data. |
Wind_turbine.jpg: This is the background image that the HTML page uses. Use of images in user-defined pages is, of course, optional, and does require additional space in the CPU. |
Wind_turbine.css: This is the cascading style sheet that contains formatting styles for the | These files are not provided with your installation, |
HTML page. Use of a cascading style sheet is optional, but it can simplify the HTML page development. |
but are described as an exampleThe HTML page uses AWP commands to read values from the PLC (Page 523) for the |
display fields and to write values to the PLC (Page 524) for data coming from user input.
This page also uses AWP commands for enum type definition (Page 529) and reference
(Page 530) for handling ON/OFF settings.
The first part of the page displays a header line that includes the wind turbine number and
the location. The next part of the page displays atmospheric
conditions at the wind turbine. These fields are
supplied from I/O at the turbine site that provide
the wind speed, wind direction, and current
temperature.
Next, the page displays the power output of the
turbine as read from the . The following sections allow for manual control of the turbine, overriding the normal
automatic control by the . These types are as follows:
Manual override: enables manual override
of the turbine. The STEP 7 user program
requires that the manual override setting be
true before enabling the use of any of the
manual settings for turbine speed, or yaw or
pitch.
Yaw override: enables manual override of
the yaw setting, and a manual setting for the
yaw. The STEP 7 user program requires
that both manual override and yaw override
be true in order to apply the yaw setting.
Pitch override: enables manual override of
the pitch of the blades. The STEP 7 user
program requires that both manual override
and pitch override be true in order to apply
the blade pitch setting.
The HTML page includes a submit button to
post the override settings to the controller.
The braking user input field provides a manual
setting for a braking percentage. The STEP 7
user program does not require manual override
to accept a braking value.
In addition, the HTML page uses an AWP command to write the special variable (Page 527)
that contains the user ID of the user that is accessing the page to a tag in the PLC tag table.The "Remote Wind Turbine Monitor" HTML page uses numerous AWP commands for
reading data from the controller (Page 523) and displaying it on the page. For example,
consider the HTML code for displaying the power output as shown in this portion of the
example pageThe following excerpt from the "Remote Wind Turbine Monitor" HTML page displays the text
"Power Output:" in the left cell of a table row and reads the variable for the power output and
displays it in the right cell of the table row along with the text for the units, KW.
The AWP command :="Data_block_1".PowerOutput: performs the read operation. Note that
data blocks are referenced by name, not by data block number (that is, "Data_block_1" and
not "DB1"). %The "Remote Wind Turbine Monitor" HTML page uses enum types for the three instances
where HTML page displays "ON" or "OFF" for a Boolean value, and for where the user sets
a Boolean value. The enum type for "ON" results in a value of 1, and the enum type for
"OFF" results in a value of 0. For example, consider the HTML code for reading and writing
the Manual Override Enable setting in "Data_block_1".ManualOverrideEnable value using an
enum type: The following excerpts from the "Remote Wind Turbine Monitor" HTML page show how to
declare an enum type called "OverrideStatus" with values of "Off" and "On" for 0 and 1, and
then setting an enum type reference to OverrideStatus for the ManualOverrideEnable
Boolean tag in the data block named "Data_block_1". Note that for each AWP_Enum_Ref
declaration there must be a corresponding AWP_In_Variable declaration for the data block
tag or PLC variable if the HTML page writes to the variable through an enum type.
<!-- AWP_In_Variable Name='"Data_block_1".ManualOverrideEnable' -->
<!-- AWP_Enum_Def Name="OverrideStatus" Values='0:"Off",1:"On"' -->
<!-- AWP_Enum_Ref Name='"Data_block_1".ManualOverrideEnable'
Enum="OverrideStatus" -->
Where the HTML page includes a display field in a table cell for the current state of
ManualOverrideEnable. It uses just a normal read variable command, but with the use of the
previously declared and referenced enum type, the page displays "Off" or "On" rather than 0
or 1.
<td style="width:24%; border-top-style: Solid; border-top-width:
2px; border-top-color: #ffffff;">